11/02/2010

A new release 4.71 of Visionic is now available for the Visionic Premium users.

Category: Visionic

Please find below advantages with this new release. Below the list of changes from the version 4.60 to the new.


The new Setup asks first to uninstall the previous version before an upgrade, what is strongly recommended.


Device Driver Isolation in Exe:
It is possible to ISOLATE any device driver in a separate EXE file. To enable this, on the server machine, set the following registry key:

HKEY_LOCAL_MACHINE\Software\Intorel\Visionic\DDRTE\UseProxyDrive

Set this to 1 to use isolation. Isolation will also use multiple cores more efficiently.


The summary alarm MAINTENANCE state is not visible from the VBscript

The VBScript (client-side) could not access / determine the MAINTENANCE state of a digital input. Point fixed

AlarmCenter: Changes to allow using layouts for colors and not paining. Depending on the computer the method can save up to 10% of the used memory and improve speed.

SetExternalAlarm might bring Visionic down if alarm was not defined as a tag. A security has been added to prevent this possibility.

The Runtime setups (client and server) made more robust. 

No errors when installing client and server runtime - previously on fresh machines VisRUDP.DLL could not be registered.

10% of memory usage less in average for the Visionic System

Remote Visionic Station element - list of ignored alarms mistake is now fixed

Visionic Client startup speed is now improved

Remote Visionic Station element has list of ignored alarms. These alarms from the remote station will not be reported

Macro recorder pops up several times incident is now resolved

When executing macro from another macro, variables were lost upon return, this point is now resolved

Changed MODBUS setup: a user can now specify MODBUS IP port

Indicators on second page were not updated, this point id now fixed

DigitalOutput cannot be set if there is no switch element on the schematic. This point is now corrected.

TabStripEx: not correct state report when some elements in maintenance point is resolved

Generic crash:  it might happen with large apps. This point is fixed

SNMP Driver changed / Setting Maintenance state result. In custom dialogs, when setting maintenance state Visionic reports an error, but the state is set OK.

The CrObjUtil object is now compatible with Windows 7

OutputWindow: it did not read if the log place was not default and it does not reflect the log file if the lof place is moved to another (non-default) directory. This point is corrected

Changed DDRTENotifEx / crash of MCHost3 application

A VisProxy3 bug is now resolved

Bipol switch bug about the FB case 5944

SNMP subsystem bug about the FB case 5876

VCMP3 import fails bug corrected about the FB case 5551

The remote alarm station which could be a list of ignored alarms is now resolved about the FB case 5938

Print