ID
|
TOPIC
|
PROBLEM FIXED
|
12700
|
Alarm Management
|
The TimeStamp relating to the Alarm for a threshold set to True with the "AlarmThresholdCmdTarget" VBA interface's "DateTimeFromTimeStamp" propertyh would continuously report data incorrectly ('29/12/1899 23.00.00').
|
13070
|
Alarm Management
|
The Variables set in the Commands on Event properties of Alarm Thresholds would not go into use when connected to the field in Output the commands would have no effect.
|
12573
|
Alarm Management
|
The Alarm Dispatcher would not send Child project alarm notifications correctly in Parent-Child project situations if the Child was 'Executable' and in 'Auto Run' (module).
|
13462
|
Basic Scripts
|
The GetSynopticInterface() function from the "PmeDocCmdTarget" interface would fail and issue the "Interface not registered"(0x80040155) error in Windows Vista operating system with "UAC ON". To Work-Around this problem, Movicon had to be started up at least once with the "Run as Administrator" open even though with UAC ON.
|
12767
|
Basic Scripts
|
The "SaveImageToFile()" function from the "SynopticCmdTarget" would ignore the parameter relating to the saved image's Quality therefore all the files that were generated had the same size and depth in Bit.
|
13648
|
Comm.Drivers
|
When selecting the SNMP Driver from the Driver list, its description incorrectly stated that no activation code was needed.
|
13451
|
Data Loggers Management
|
In some cases the Data Logger would drop tables when not necessary to do so.
|
12488
|
Design
|
Applying the Zoom Off by dragging the Mouse on the Trend would raise an exception in Movicon. This problem was worked around by disabling the option for loading data in background with a separate thread.
|
12417
|
Design
|
"Activation context generation failed" errors would appear in the Windows Application event log relating to the localization dll (eg. *LOC.DLL) for both Movicon 11.3 and 11.4.
|
10396
|
Design
|
When using the MySQL ODBC the variable 'ODBC Link' functionality would not insert or update records in the RTVar table and it would not alert errors in the DBMS Log.
|
10296
|
Design
|
The Movicon login of Windows domain users belonging to the 'Users' group would get associated to the Movicon Windows 'Guest' group by error.
|
13574
|
Design
|
Changing screens using the 'Commands on Pressed Button' option would not work. This problem began happening when modification for the Multitouch in build 1150 were implemented.
|
12769
|
Design
|
The project's Tool Upload reported an incorrect alert in the log when logging in to the TCP upload remote Server failed.
|
12979
|
Design
|
In cases when zooming in on a symbol, ungrouping it and then zooming out the management responsible for the properties used for positioning symbol components would not return them back their previous positions.
|
12983
|
Design
|
When a symbol's 'Back Color' Animation was activated with the "Tag is an Alarm Area" property and its list of colors were changed, Movicon would raise an exception when inserted in the Symbol Library.
|
13251
|
Design
|
A Trend object animated with visibility would not update the chart's curves when the visibility switched from Off to On. This problem was worked around by inserting a Refresh instruction in the Trend's "OnTimer" VB timer.
|
12483
|
Design
|
When starting up Movicon with a synoptic adapted to full screen size without status bar, the window frame would appear limiting the screen borders to show at full size.
|
13129
|
Design
|
When the "Sound Duration Button (ms)" property was set to '0', the sound would not stop when clicking on a button in a Pop Up opened in Modal mode that executed the 'Screen' command set with the 'Close and Return Back' action.
|
12795
|
Historical Log Management
|
The UNICODE characters would not get saved correctly in the logs because the conversion function has not been included in the Insert query.
|
13633
|
iOS
|
The iOS applet displayed a blank white page after rotated 180° by tipping the device backwards and forwards. In this case a request was not made to the Server for the screen page because it did not recognize it had changed size when rotated at 180°.
|
12569
|
Networking
|
The "Nr. Attempts to Connect" and "Attemps Interval" setting would not get set in the tranports created for Client communication with Server.
|
12670
|
Networking
|
Using a Client MoviconRuntime in a Parent/Child application towards a redundant Server Movicon would raise an exception during the application shut down phase after a certain time in runtime.
|
12386
|
ODBC
|
Movicon would go into 'Out of Memory' and then raise an exception when the amount of data to be recorded became excessive. This problem would manifest when the variables of various data logger tables changed very quickly. This problem has been fixed so that data in the ODBC Cache is flushed when exceeding the cache's size multiplied by 10. When this limit is exceeded Movicon flushes data onto a support file and issues an error message in the log.
|
13658
|
OPC Communication
|
Instead of creating OPC groups for structure variable members linked to OPC Items, just one unique group is created for all members for the time being due to difficulty in optimizing the activation management of various groups.
|
13160
|
OPC Communication
|
In cases where the data type or value passed from the Movicon OPC server to the OPC client might have been incompatible with the Movicon variable it would not be reported in the log even when enabling the OPC Client trace.
|
13087
|
OPC Communication
|
A Movicon project set as OPC Server was viewed by OPC Clients as DA 3.0 compatible. In reality the Movicon OPC Server only supports the 1.0 and 2.0 interfaces.
|
12797
|
OPC Communication
|
The 'Synch OPC Server..' command would no work correctly in certain situations.
|
1263
|
Redundancy
|
Synchronization with the Primary would take a long time to complete when a great number of variables, alarms or historical data changed continuously. This has been fixed so that if the synchronization operation does not terminate within the Time = (Redundancy Timeout * Num.Attempts), a message is printed in the Log stating that synchronization went into timeout and will resume after Startup.
|
12758
|
Redundancy
|
Updating variables on the Secondary side would take time when a great number of variables on the Primary side changed at the same time.
|
12642
|
Redundancy
|
Progress was slow in creating NET variables in a Client project containing a great quantity of variables due to searching for a valid name while creating a dynamic variable.
|
12542
|
Redundancy
|
The Secondary could not write a variable on the Primary side when it had a consistent number of variables that changed continuously. In addition, this would block other operations such as synchronizing historical data from the secondary towards the primary (data which the primary had not yet recorded), or executing script on the secondary.
|
12576
|
Redundancy
|
The Primary was unable to empty the historical data cache when a great quantity of alarms or variables changed continuously.
|
13138
|
Screen Management
|
The Screen contained in an 'Embedded Screen' object in which a dynamic variable was used for changing the displayed screen would stop updating or the application would freeze upon displayed screen change.
|
13282
|
Screen Management
|
When using the "Zoom To" command in a screen already activated with a zoom factor, the zoom would reset to 100% before using the command. This problem manifested when the zoom factor in either case resulted inferior or superior to 100%.
|
13271
|
Screen Management
|
Opening the same screen with the same coordinates set in the command but with two different Modal and Frame modes the screen would open in a different INCOMPATIBILITY position: the screen would open in a slightly different position in projects that had been already created.
|
13697
|
Screen Objects
|
Combo boxes would not display properly in the 'Alarm Window' object from the Web Viewer Library used by Web Clients when other Text objects were present.
|
12955
|
Screen Objects
|
When the 'Enable Button Sound' was enabled and when clicking on a Display with an active "Show Pad" property, the sound would repeat continuously until the Numeric or Alphanumeric Pad was closed.
|
12650
|
Screen Objects
|
It was not possible to use variables that had been created in runtime in Color Threshold Animation expression control.
|
12746
|
Screen Objects
|
The Zoom would not reset when Trend returned to Run mode after a zoom-in operation.
|
7127
|
Screen Objects
|
Due to a Windows CE platform problem the Trend object would send MovCE into exception for consuming memory when the set font was used to determine the height of pen check boxes in a legend containing 6 pens: this problem has been fixed by drawing push buttons when the check box in the legend is too small.
|
13695
|
Screen Objects
|
The cursor in Slider Objects did not have the right styles, for instance the vertical cursor was used in horizontal sliders while the horizontal cursor was used in vertical sliders.
|
13208
|
Screen Objects
|
The "SetSamplesValue()" function from the "TrendCmdTarget" would not function if the Trend was loaded as "Always in Stop" and therefore without recording samples in its buffer.
|
12609
|
Screen Objects
|
When a Parent project screen contained an Embedded Screen object which displayed a Child project with a Data Analysis or Trend object, the child project's datalogger or trend object would not show the pen historicals.
|
13260
|
Setup
|
The COMM References to the driver dlls were recorded with the wrong descriptions while installing Movicon.
|
12941
|
Setup
|
The information relating to the Progea URL relating to the Movicon application had not been updated in the Windows 'Control Panel - Programs and Features'. In addition the electronic signature had expired in February 2014.
|
13629
|
Setup
|
The 11.4.1150 version setup installed the 11.3.1105 version's CAB x86 files.
|
10342
|
Setup
|
The .movprj file would not get associated with 'MoviconRuntime.exe' when installing the Movicon Runtime component only.
|
12694
|
Tools
|
The TCP Client Service Upload vulnerability has been fixed concerning the missing authentication towards the TCP Server Upload during a version request for that server.
|
13698
|
User Interface
|
The meters in the toolbox window were indicated as "Gauges" instead of "Meters".
|
13486
|
WebClient
|
Problems occurred when connecting to the sever without displaying the startup screen when the "Static Object in Background" option both in the project properties and in Android and iOs app screen properties were enabled.
|
12989
|
WebClient
|
The Web Client Java Applet was not signed therefore a security error would occur and block the Applet from running when using the same Java Machine 7.0 or later versions.
|
13200
|
WebClient
|
The iOS App would raise an error attempting to display a page with large background images due to the fact that the iOS devices requested the Server for a page twice the size of those supported by the device's screen size.
|
12922
|
WebClient
|
In 4s iPhones the screen image loaded at the iOS app startup had a low quality resolution and clicks on objects were not executed in the corresponding position on the Server page.
|
12912
|
WebClient
|
When setting the 'Keep Connected' option to enable several error screens would show in the iOS App in cases where the connection session was restored after a connection error had occurred or when the terminal started up from stand-by mode.
|
12914
|
WebClient
|
Several connection error windows would open when maximum number of licenses in the iOS App was reached. This problem also concerned other error windows which reported messages such as incorrect user name and nonexistent screen.
|
13592
|
WebClient
|
The iOS App would disconnect from the Server when used after it had been left connected to the for some time.
|
12699
|
WinCE OS
|
The "_SysVar_:ActiveScreen" system variable reported the ID of the previous screen. This problem started occurring with the Movicon 1102 build.
|