Problems fixed with version: 11.6.1201

 

Build: 11.6.1201
Release Date: 16th May 2019

ID

TOPIC

FIXES

23784

Design

Movicon would raise an exception the moment a symbol from the Symbol Library was displayed containing a 'Historical Log Window' object with the Print button enabled.

 

22795

OPC Communication

The OPC UA Client would generate a Memory Leak using a OPC Server such as the UA Server CPP Demo for example.

 

22934

Web Client

Opening a HTML5 Web client session would occupy too much Movicon process memory if the name of the Screen displayed contained special characters and was frequently updated.

 

23240

Web Client

Movicon CE would inadvertently close in Windows CE when the Websock's 8088 port closed at the end of a Web Client HTML5 session.

 

 

Minor Problems

ID

TOPIC

FIXES

23141

Design

When a screen opened as a Modal Popup on a Multi Touch Monitor, it would not respond when tapped if opened from within a basic draw object.

 

23432

OPC Communication

The "OPCUABrowseMaxOperation" registry key has been added to the "General" section to set a custom limit on the number of reads per operation requested by OPC UA Browser to the OPC UA Server while Browsing Tags. The value range is 1-65536.  Values that are 0 or greater than 65536 are reset by the SDK for default 65536.  This key is ignored when the OPC UA Server exposes a read limit for operations.

 

23079

Redundancy

The Primary Server and Secondary Server synchronization would fail when the Primary Server started up in a configuration which had Redundant projects.

 

23847

Screen Objects

The 'Language' attribute management has been added to the "OnCallDutyManager" Symbol from the "Utility" Symbols Library so that messages are sent in the language set in the property of the User changing shift.  

 

22909

Setup

The Movicon "Alarm Generator" and "Import/Esport Alarm" Tools would search for a .visalr file type and a .visrealtimedb project type respectively instead of a .movalr file type and .movrealtimedb project type.

 

23476

Web Client

No message would show in the Networking Log when the "Web Client autologoff" time expired in a HTML5 Web Client session.

 

22976

Web Client

When using the Browser to startup a HTML5 Web Client session, pages would not load and would remain white with a red frame.  

 

22623

Web Client

Using the zoom repeatedly in a HTML5 Web Client  session would compromise the quality of images of objects displayed on screen.  

 

22662

Web Client

An error reporting an unfound resource would return if the Screen happened to be in a folder when starting up the HTML5 Web Client.

 

22792

Web Client

Alarms would not give off warning sounds in a HTML Web Client session as would happen in a Java Applet Web Client session.

 

23475

Web Client

The HTML5 Web Client session would expire after 10 seconds if the value input box had been left open after editing a variable from a Display type object.

 

22667

Web Client

Screens with names containing special characters would not open with HTML5 Web Client.