Change Notes FW V1200 TP3xxxx GEN3 EN

Download as pdf or txt
Download as pdf or txt
You are on page 1of 7

Change Notes

15.03.2016

Firmware-Version: FW_SB7ECS-VISUPLUS-1200

Valid for: TP 3057Q 2400452


TP 3057V 2400453
TP 3xxxS 24004xx (xx = 55, 56, 58)
TP 3xxxW 240xxxx (xxxx = 0454, 2630)

Background: Systemstep 3.2

Components of the firmware:


- XLoader: BL7ECS-XLDRNAND-0320
- Bootloader: BL7ECS-EBOOTND-0320
- Image: IM7ECS-VISUPLUS241-0320
- Visu+-Runtime: Version 2.41.1154.1
- OPC Server: Version 2.2.0.97

Bug fixes related to the HMI image


1. After leaving the screensaver or switching on the backlight the Visu+
application disappears
Applicative frame conditions:
In Visu+ appears a pop-up-menu, while the Screensaver is activated or the backlight
switched off.

Bug description:

When the screensaver will be deactivated or the backlight switched on by a touch on


the touchscreen the pop-up-menu becomes visible. After the pop-up menu is
acknowledged and closed the Visu + application disappears. The system is still
executing the application but she is no longer visible for the user. Instead of this the
desktop of the device is displayed.

Bug fix:
The bug was fixed inside the Visu+ Runtime. The Visu+ application will not disappear
at the described use case.
2. Web browser access to the webserver of the device
Bug description:
It is not possible to reach the webserver of the HMI device with a web browser or the
Visu+ generated file „VisuPlusWebClient.jar“ and to display the application.

Bug fix:
The bug was fixed inside the Visu+ Runtime. Displaying the application with a web
browser or the “VisuPlusWebClient.jar” is possible now.

3. Loss of the OPC communication at appearing Visu+ warnings


Bug description:
Visu+ warnings are triggered by a double use of variables (tags) in the OPC server.
These warnings interrupt the OPC communication between PLC and device.

Bug fix:
This behavior is changed inside the OPC server so that appearing Visu+ warnings
will not interrupt the OPC communication. In respect to screen changing and
response time of the application it is recommend in any way to avoid a double use of
variables (tags) in the OPC server.

4. Preview of the display orientation doesn’t work properly inside the Cockpit
Bug description:

 Changing the orientation in the menu "Display" and confirm it with "Apply", the
Cockpit doesn´t center the displayed contents.
 If the settings are not confirmed in the specified time or by termination, the
screen orientation changes automatically to the original, but the preview of the
display orientation is not restored to its original orientation.

Bug fix:

 The bug was fixed inside the configuration menu “Cockpit”. If the changed
settings of the display-orientation will confirmed with “apply” then the contents
will displayed centered according to the settings.
 If the setting will not confirmed the display orientation of the preview changes
back to the previous states.
Bug fixes related to the Visu+ visualization software affecting the
HMI behavior
5. Usage of the IMDB-Function causes a memory increase
Bug description
If the „In Memory DB-Manager (IMDB)” is activated, the logging of the data packages
will be setted up with the default setting „0“. This causes that every alarm and
historical event will be saved on the “FlashDrv“. The main memory gets allocated as
well.

Applicative solution
If the „In Memory DB-Manager (IMDB)“ is activated, the number of logged data
packages must be limited. If the number of logged data packages is limited, for
example to “1” the buggy behavior does not occur. The number of allowed logged
data packages depends on the number of alarms which can appear in a certain
period of time. This in turn is depending on the application. So the number of logged
data packages can be setted up higher or smaller.

6. Delay while displaying a large number of alarms


Bug description:
The default value of the event cache setting is „1024“. Displaying this large number of
alarms causes the delay up to 30 seconds. The behavior can be solved in the
application by reducing this default value.

Bug fix:
Up to now (Visu+ 2.4) in the visualization software the described settings will be set
on „0“ and the function deactivated. By using the Event-Cache, the max number of
alarms should be detected, to reduce the utilization of the device.

7. Visu+-RT crash by using the L&T-Operation (IL-Logik) in Visu+


Applicative frame condition:
A variable from a PLC will be loaded in the IL-Logic area and then written back to
another PLC-Variable.

Bug description:
A durable L&T-Operation in the IL-Logic causes a stop and crash of the IL-Logic after
max. 2 days.

Bug fix:
The bug was fixed in Visu+.
8. Loss of the OPC communication by using the InUse Manager in Visu+
Applicative frame condition:
In the general variable list the setting „InUse Manager“ is activated. At the same time
the setting „if not in use deactivate“ in the OPC client properties is deactivated.

Bug description:
The combination of the settings causes the stop of the communication with the PLC if
the user switches to a screen without a reference to a variable. If the user then
switches back to the screen before, the value of the variable will not be updated
because the OPC communication is lost.

Applicative solution
The behavior can be solved applicative by deactivating the “In Use-Variable
Manager” setting and activate the “If not in use deactivate” in the OPC-Client-
Settings.

Bug fix:
Up to now (Visu+ 2.4) in the visualization software the described properties will be
set as default.

Picture 2: Up to now the property „InUse Manager“ will be deactivated

Picture 3: Up to now the property „Deactivate if not in use“ will be activated


9. Loss of the Modbus-RTU Communication via RS485
Bug description:
An interrupt of the protocol driver by a higher prioritized process causes that some
parts of telegram packages get lost.

Bug fix:
The bug can be fixed by increasing the prioritization of the protocol driver. Therefore
the settings of the communication driver have been expanded with the necessary
adjustment (see Picture). Internal tests confirm that the behavior no longer occurs
when the priority is set on 108.

Picture 4: Drivers priority

10. Settings in the SuetronHWAccess-Driver


Bug description:
Opening the register “Station” in the SuetronHWAcess-Driver window causes an
error message.

Bug fix:
The register “Station“ has been removed from the driver window.
Picture 1: Window of the SuetronHWAccess driver

Functional improvements
11. Improved memory management
The operating system has an automatic mechanism that detects defective flash
sectors and corrects them. The error-correction-mechanism of the old firmware was
able to detect and correct only one error per data block. If two or more flash sectors
are defect the device isn´t able to operate after booting.

The automatic error-correction-mechanism of the operating system is changed, to


have a higher data security in the flash memory. Because of the changed process it
is possible to detect and correct eight errors per data block.

12. Starting the „TCP Upload Servers“ after booting the operating system
The ”TCP Upload Server” must be executed to be able to download a Visu+
application on the HMI. Up to now the TCP Upload Server starts after the automatic
close of the configuration menu Cockpit. This happens when the configuration menu
has not been entered.

The linear-sequential behavior has been changed. The „TCP Upload Server“ starts
immediately after the system start. So the application can be downloaded
independently of the use of the configuration menu.

13. Pop-up of the entry field in the configuration menu


The software input panel in the current FW-version appears when a configuration
menu with an edit-box gets open even when the user doesn’t want to make any
changes. This behavior has been changed. The software input panel only pops up by
a „click“ on an particular edit-box.
14. HMI System variable

 After turn on the system variables „SET_ BRITHNESS_VALUE“ and


„SET_ALARM_BRITHNESS_VALUE“ shows there current real value.
Before the variable „SET_BRITHNESS_VALUE“ has shown the value „0“
after turn on. This was confusing because it was not the adjusted value for the
brightness. The same applies to the value of the system variable
"SET_ALARM_BRITHNESS_VALUE".
 While an Alarm is active it is not possible to adjust the brightness over the
system variable „SET_BRITHNESS_VALUE“.

Functional enhancements
15. New Menu „customer-customization“
The functions „changing the background-image“ and „changing the screensaver-
image“ are added to the configuration menu Cockpit. Until now this feature was just
possible by manual copying of those files into the flash.

The new functions plus the function „changing the startup-image“ are summarized in
the new menu called „Customization“. Before now the function was placed in the
menu “Administration”.

16. Edition of the OPC-Server-Version


In the sub-menu “System” of the configuration menu “Information” the current OPC
server version is displayed. This Information was not included before.

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy