Technical Support Information No. 202c September 2013

Transcription

1 Customer Focus Page 1 of 14 Release of Maxum Workstation Software Patch Versions and Earlier this year as decision was made to reintroduce the Workstation Patch program providing users with quicker updates to serious issues deemed too important to wait for the normal software release schedule. Two Maxum Workstation Software Patch versions have been released since the initial release of version in January In June 2013, the first Workstation Patch version was released to the website followed by Patch release in. All updates for are included in the patch currently on the Siemens website. All changes for these two releases are outlined in the following. For a complete listing of changes, refer to the ReadMe file located on the website mentioned below or refer to ReleaseNotes_5.10.x.pdf located in the /Maxum System Manager/Upgrade 5.10 folder. If you already have Maxum Workstation 5.10.x installed on your PC, select the Maxum GCP Workstation Patch and Embedded Maxum Software and Patches link located at Then install either the _SM_GCP_Update for GCP and System Manager fixes, or the _SM_Only_Update for System Manager fixes only. Note: A new patch will be released in October 2013 for users not currently at Workstation It will include all fixes for Workstation 5.00 and earlier. Description: Update for Gas Chromatograph Portal This update contains the following fixes: 1) Fixed: StatMon ArgumentOutOfRangeException after setting Action to -1 (empty binaries). 2) Allow user to provide an ID for new application On creating a new application in Gas Chromatograph Portal the new application ID was always the highest configured application ID increased by one. In many cases this behavior is not adequate. Now the user can provide a new application ID in the context of Add Application (part of Analyzer Overview ). OLD:

2 Customer Focus Page 2 of 14 NEW: 3) Added: sim_clock was missing required for Timer Applications The flag sim_clock wasn t available in Gas Chromatograph Portal. This flag is important for the configuration of timer applications. This has been added and grouped together with the other two timer application settings: OLD:

3 Customer Focus Page 3 of 14 NEW: 4) Problem: MicroSAM devices of specific database versions (2.07, 3.00, 3.10, 3.20) were not identified properly in the context of upgrading an analyzer. Symptom: An error message was displayed at the beginning of the upgrade process. Resolution: These errors have been fixed. 5) Problem: Windows 7 compatibility issues concerning the FTP file transfer in the context of upgrading an analyzer. Symptom: Timeout and error message when upgrading an analyzer (using Gas Chromatograph Portal Network View) Resolution: The FTP transfer code has been hardened in a way that it will work properly under Windows XP and Windows 7. 6) Problem: The Windows 7 firewall did block important communication between analyzer and workstation in the context of upgrading an analyzer (System Components, BIOS/Loader). Symptom: Gas Chromatograph Portal Network View did fail when attempting to update the BIOS/Loader component. Resolution: Added two inbound firewall rules (port ). 7) Problem: Gas Chromatograph Portal Network View wasn t able to receive broadcast messages from connected analyzers. Symptom: The analyzer status displayed in Gas Chromatograph Portal Network View did miss status information sent by the analyzer. Resolution: Added one inbound firewall rule (port 3004).

4 Customer Focus Page 4 of 14 Notes 1) If the patch is applied, the contained Windows Firewall exception rules are added to the current configuration even if these were not selected previously. If this set of exception rules isn t desired it has to be deselected again after the installation of the patch (available in Control Panel\Programs\Programs and Features, Gas Chromatograph Portal - Context Menu: Change ). 2) Communication with analyzers connected through a Public network interface isn t supported. Therefore it is necessary to have the analyzers connected through an interface which is at least configured as a Domain network or Work network (available in Control Panel/Network and Internet/Network and Sharing Center): Description of Maxum Update Operating System: 1) Problem: Maxum does not always power up with the most recently saved Database. Symptom: Changes made to a Maxum database and restored/saved to flash may not be loaded on the next reset. Resolution: The selection algorithm that determines which Database to load at startup was corrected. 2) Problem: Color Display Touchscreen controller chip on the CIM board does not always hold the touchscreen configuration. Symptom: After a reset, the active touch area may have changed which prevents the user from selecting items on the display correctly. (Other symptoms can be observed also with this problem.) Resolution: The software is updated to support the new controller chip that is being used on the new CIM boards. Database: 1) Problem: Program run did not always work for all remote requests. Symptom: Program run did not work when requested by a Modbus Master. Resolution: Modbus program run fixed. 2) Problem: Modbus readme flags occasionally time out too soon. Symptom: The readme flag will periodically only stay on for a second or two instead of the specific time period. Resolution: Timeout problem corrected to consistently time out at the specified time.

5 Customer Focus Page 5 of 14 HMI: 1) Problem: Alarm text not consistent for in-service and out-of-service messages. Resolution: Text was made consistent between the in/out states. 2) Problem: Pressure Program flow calculator was not working properly. Resolution: Problem corrected. 3) Problem: Times displayed on the HMI were 12 hr format instead of 24 hr. Resolution: Changed the display times to 24 hour clock format. 4) Problem: Alarm text incorrect for alarms Symptom: Text for these alarms came up unknown. Resolution: Fixed alarm text for each alarm to match the alarm numbers. 5) Problem: If timeserver gets set to dhcp, the HMI does not have a way to set it back. Resolution: Modify the HMI display to allow the user to turn off dhcp only if set to 1 on system_setup screen. (If dhcp is not set, the option to control this flag is not visible. This change allows the user to turn off dhcp if set, since dhcp is not a valid Maxum setting.) 6) Problem: Temperature and Pressure screens do not show enough resolution in the number displayed. Symptom: Only one decimal place was visible. Resolution: Increased the number of decimal places on the temperature and pressure screens. 7) Problem: CAN cards cannot be added using the HMI. Symptom: The serial number was being entered/displayed in scientific notation. Resolution: Fixed display/entry of CAN serial number. 8) Problem: Bios version is often incorrect on the system setup screen. Resolution: Remove Bios version from the HMI system setup screen since some versions do not pass this information. DBConverter 1) Problem: MicroSAM databases did not end up with a working serial port configuration following a conversion. Resolution: Add custom conversion for MicroSAM serial settings to leave the original setting format in the system_control table. 2) Problem: After file conversion Results were not tied to their appropriate EUHI. Resolution: Fixed the EUHI reference link with the associated Results. 3) Problem: After a file conversion the date and time values did not always convert to a correct datetime format in the Modbus map. Symptom: The values would not show up in the database even though they were in the map. Resolution: Fixed datetime conversion to handle both DATETIME and separate DATE and TIME entries in the map.

6 Customer Focus Page 6 of 14 Description of Update for GC Portal / GC Network 1) Problem: GCN: MicroSAM update issue Symptom: Flashed MicroSAM (2.8, 3.x) cannot be upgraded with GCP Resolution: Upgrade of flashed MicroSAM (2.8 and 3.x) with GCP 5.10 fixed. 2) Problem: GCP: (Online) Sequence issue with gaps in the sqid field of the sequence_entry table. Symptom: Deleting an entry in the sequence table results in a sequence that will only run to the gap in the analyzer and will then process the first pair in the sequence next. Resolution: With this fix GCP will update the sequence entry index in order to avoid gaps. 3) Problem: GCN/GCP: Confusing states during Data Logger configuration. Symptom: Datalogger cannot handle duplicate or missing serial numbers. Resolution: Both missing and duplicate serial numbers are now handled properly and highlighted. The serial number column highlights these problems for the Data Logger. 4) Problem: Change numbering of group id to make it identical to EZChrom. Symptom: Peak group IDs are automatically defined in GCP to start at one instead of zero and cannot be renumbered. Resolution: Make group ID of each detector start from zero as in EZChrom so that existing result index and MaxBasic programs that rely on this group ID convention can work without modification. 5) Problem: Loading a method from file can produce a duplicate entry. Symptom: Loading a method from file can produce a duplicate entry when overwriting an existing running method. Resolution: Duplicate method entry is prevented by waiting to load the method until the cycle completes. 6) Problem: Remember MBM file path after loading or saving an MBM method. Symptom: Each time a method is saved the directory path has to be retyped. Resolution: The directory path used previously will be the default path the next time a method is saved or loaded. 7) Problem: There is no way to reload a method from source (MBM file/ Ax method). Symptom: After modifying a method, it is not possible to discard the changes and reload the method. Resolution: Added context menus on the method tree node for reloading a method from its source (MBM file or analyzer method). Description of Maxum Update Database: 1) Problem: SNE did not correctly process I/O not on the I2C network that was used as a cycle event. Symptom: A DO designated as a cycle event does not work. Resolution: The SNE message for cycle events was corrected to indicate that the DO control for this I/O was to be done by the Database, rather than the SNE.

7 Customer Focus Page 7 of 14 2) Problem: Automatic parameter lookups for DIs and DOs were incorrect. Symptom: The value passed to the MaxBasic program is incorrect. Resolution: Automatic parameter lookup for DIs and Dos was corrected. 3) Enhancement: Turn off debug messages for DCS writes to modbus map. Symptom: Serial and LogMonitor shows excessive debug messages Resolution: Debug Messages were turned off 4) Problem: PrintService was not always working correctly. Symptom: Printout to serial port or debug port was wrong for standard report logs and reports from MaxBasic. Resolution: Standard report and MaxBasic printing was fixed. 5) Problem: The status on remote I/O is set to normal (0) every 5 minutes to regardless of the actual state. Symptom: Every 5 minutes remote I/O status is set to normal (0) until the remote I/O poll occurs and returns the status to the actual state. Resolution: Change remote I/O failsafe status to not init (-1) rather than normal (0) Fixes interaction with PrintService 6) Problem: If an analyzer has a problem responding correctly to only the currently defined slave address, loading 5.10 does not fix the response to previously defined slave numbers. Symptom: An analyzer that responds to more than one slave address does not correct itself when 5.10 is loaded. Resolution: Fixed typo in check slave mechanism for Modbus so that once is loaded into an analyzer the Modbus slave table is corrected properly by deleting unused slave addresses. 7) Problem: The db_load_file attribute in the system_info table gets set to the last filename saved by the automatic database save function. Symptom: This attribute would rotate between DB0.dat, DB1.dat and DB2.dat. The workstation tools were expecting it to always be the target filename to be used when a database was restored from the workstation. Resolution: Control naming of file when loaded from PC, by making the db_load_file always db.dat. Use cmd_file in system_info for incremental saves 8) Problem: MaxBasic debug statements do not show floating point parameter values. Symptom: MaxBasic debug statements show floating point parameter values as 0 instead of the actual value passed to program execution. Resolution: Changed debug for program execution to properly get the float parameter values 9) Problem: 0-20 ma Analog Outputs can post an alarm that values have been clamped when clamping did not occur. Symptom: Analog Outputs post an alarm when the value is at the low end of the scale even though clamping was not needed and did not take place. (Example: 0 value could generate a clamping alarm. Resolution: I/O values at the low end of the range no longer give an alarm unless clamping really takes place for 0-20 ma outputs.

8 Customer Focus Page 8 of 14 10) Problem: The db_load_file attribute in the system_control table was not always set to point to db.dat. Symptom: After a file conversion the db_load_file attribute was left at its previous setting which could be db0.dat, db1.dat or db2.dat. Resolution: DBConverter was modified to insure that the parameter was set to db.dat after a file conversion. 11) Problem: Parameter Table display of DI and DO values were inconsistent. Symptom: The DI and DO values were displayed as 1. in one case and 1.0 in the other. Resolution: Both DIs and DOs now display as ) Problem: The warning DO state did not always match the state of the Maxum alarm LEDs. Symptom: If a warning alarm occurred and then was cleared, the Warning DO state would remain set. Resolution: The handling of the warning DO specified in the system_control table was fixed to clear when the warning alarms were all cleared. 13) Problem: Pulse DO s do not work correctly with CAN cards. Symptom: A pulse DO using a CAN card address will pulse local Syscon I/O instead. (example: If a pulse DO is set for a CAN card address such as 0: , when the pulse activates it will be seen on DO 0: instead. The CAN node number of 11 in this case is ignored and the local 4.2 address is used.). Resolution: In the above example, 0: will now pulse correctly. HMI 1) Problem: The Workstation HMI does not work for PCs set to some European countries. Symptom: The workstation HMI crashed when opened on a PC that was set for a country that used a, instead of a. for a decimal point. (example: Germany) Resolution: This problem was corrected. 2) Enhancement: Improve the Chinese text in the HMI. (workstation HMI touchscreen version only) Symptom: Chinese translation had many errors in the 5.10 version. Resolution: Chinese translation was improved for the HMI screens and on-line help. (Note: Chinese text for alarms will be improved in a later release.) 3) Problem: The Result and Chromatogram storage had access problems for PCs set to some European countries. Symptom: Once a PC was localized for a country that uses commas in the time/date format the Workstation HMI could not display results or chromatograms. Resolution: This problem was corrected. DBConverter 1) Problem: Fixed db text load of serial_settings table Symptom: When a text file was loaded into an analyzer an invalid entry was created. The result was what appeared to be a blank table in GCP. Resolution: The text file load was corrected to prevent the invalid record.

9 Customer Focus Page 9 of 14 2) Problem: DBConverter was updating the screen text when 4.x files were converted. Symptom: After a conversion some of the buttons would show bad label instead of the correct label. Resolution: DBConverter no longer replaces screen text during 4.x conversions. (To correct a previously converted file you must reconvert the file with the new DBConverter.) 3) Problem: Scaled Modbus values were scaled incorrectly and ended up being transmitted as a zero value. Symptom: The Modbus Host would see zero instead of the correct value. Resolution: Modbus loads were corrected to handle EUHI entries so that they are linked properly to results and calculated the scaled value correctly. Description of Maxum Changes Operating System: 1) Problem: Maxum does not always power up with the most recently saved Database. Symptom: Changes made to a Maxum database and saved to flash may not be loaded on the next reset. Resolution: The selection algorithm that determines which Database to load at startup was corrected. 2) Problem: Networks with frequent errors can result in a LAN driver reset that leaks memory. Symptom: When enough memory is lost, the analyzer can reset. Resolution: Memory leak in this situation was fixed. 3) Problem: Networks with very frequent errors can result in applications not running. Resolution: Error reporting was modified to prevent very frequent errors from blocking applications. Description of Changes for Syscon 2 Database: 1) Problem: SNE did not correctly process I/O not on the I2C network that was used as a cycle event. Symptom: A DO designated as a cycle event does not work. Resolution: The SNE message for cycle events was corrected to indicate that the DO control for this I/O was to be done by the Database, rather than the SNE. 2) Problem: Automatic parameter lookups for DIs and DOs were incorrect. Symptom: The value passed to the MaxBasic program is incorrect. Resolution: Automatic parameter lookup for DIs and Dos was corrected. 3) Enhancement: Turn off debug messages for DCS writes to modbus map Symptom: Serial and LogMonitor shows excessive debug messages Resolution: Debug Messages were turned off

10 Customer Focus Page 10 of 14 4) Problem: The status on remote I/O is set to normal (0) every 5 minutes to regardless of the actual state. Symptom: Every 5 minutes remote I/O status is set to normal (0) until the remote I/O poll occurs and returns the status to the actual state. Resolution: Change remote I/O failsafe status to not init (-1) rather than normal (0) Fixes interaction with PrintService 5) Problem: The db_load_file attribute in the system_info table gets set to the last filename saved by the automatic database save function. Symptom: This attribute would rotate between DB0.dat, DB1.dat and DB2.dat. The workstation tools were expecting it to always be the target filename to be used when a database was restored from the workstation. Resolution: Control naming of file when loaded from PC, by making the db_load_file always db.dat. Use cmd_file in system_info for incremental saves 6) Problem: The db_load_file attribute in the system_control table was not always set to point to db.dat. Symptom: After a file conversion the db_load_file attribute was left at its previous setting which could be db0.dat, db1.dat or db2.dat. Resolution: DBConverter was modified to insure that the parameter was set to db.dat after a file conversion. 7) Problem: Parameter Table display of DI and DO values were inconsistent. Symptom: The DI and DO values were displayed as 1. in one case and 1.0 in the other. Resolution: Both DIs and DOs now display as ) Problem: Pulse DO s do not work correctly with CAN cards. Symptom: A pulse DO using a CAN card address will pulse local Syscon I/O instead. (example: If a pulse DO is set for a CAN card address such as 0: , when the pulse activates it will be seen on DO 0: instead. The CAN node number of 11 in this case is ignored and the local 4.2 address is used.). Resolution: In the above example, 0: will now pulse correctly. DBConverter 1) Problem: Fixed db text load of serial_settings table Symptom: When a text file was loaded into an analyzer an invalid entry was created. The result was what appeared to be a blank table in GCP. Resolution: The text file load was corrected to prevent the invalid record. 2) Problem: DBConverter was updating the screen text when 4.x files were converted. Symptom: After a conversion some of the buttons would show bad label instead of the correct label. Resolution: DBConverter no longer replaces screen text during 4.x conversions. (To correct a previously converted file you must reconvert the file with the new DBConverter.) 3) Problem: Scaled Modbus values were scaled incorrectly and ended up being transmitted as a zero value. Symptom: The Modbus Host would see zero instead of the correct value. Resolution: Modbus loads were corrected to handle EUHI entries so that they are linked properly to results and calculated the scaled value correctly.

11 Maxum Workstation Version numbers Customer Focus Page 11 of 14 Maxum Patch Version Information (Modules updated from original 5.10 CD release are shown in Bold Type) SYSCON: Bootloader version: OS version: DB version: B/W HMI version Touchscreen HMI TEXT version: SNE: OS version: 0004.f16 APP version: 0004.e16 Workstation Software: Gas Chromatograph Portal: EZChrom: System Manager: Touchscreen Workstation HMI: Workstation HMI: Other Software: APC: MaxBasic: SimDis.dll Statmon Printclient DbConverter Formula Note: To verify the correct version for the Workstation, go to Maxum System Manager\Upgrade5.10\versions.txt and verify the versions match above information. To verify the latest version is loaded into the NAU or analyzer, go to the HMI and select Configure Menu => System Setup => Version Info and verify the versions match above information.

12 Customer Focus Page 12 of 14 Maxum Version Information: (With Workstation Patch Release) (Modules updated from original 5.10 CD release are shown in Bold Type) SYSCON: Bootloader version: OS version: DB version: HMI version: SNE: OS version: 0004.f16 APP version: 0004.e16 Workstation Software: EZChrom: System Manager: Touchscreen Workstation HMI: Workstation HMI: Other Software: APC: MaxBasic: SimDis.dll Statmon Printclient DBConverter Note: To verify the correct version for the Workstation, go to Maxum System Manager\Upgrade5.00\versions.txt and verify the versions match above information. To verify the latest version is loaded into the NAU or analyzer, go to the HMI and select Configure Menu => System Setup => Version Info and verify the versions match above information.

13 Customer Focus Page 13 of 14 Maxum 4.40 Version Information: (With Workstation Patch Release) (Modules updated from original 5.10 CD release are shown in Bold Type) SYSCON: BIOS version: (Mar 18, 2005) OS version: V4.4.0 (Oct 2012) DB version: B/W HMI version version for DM Touchscreen HMI TEXT version: SNE: OS version: 0004.f16 APP version: 0004.e16 Workstation Software: EZChrom: System Manager: Touchscreen Workstation HMI: Workstation HMI: Other Software: APC: MaxBasic: SimDis.dll Statmon Printclient DbConverter Note: To verify the correct version for the Workstation, go to Maxum System Manager\Upgrade4.40\versions.txt and verify the versions match above information. To verify the latest version is loaded into the NAU or analyzer, go to the HMI and select Configure Menu => System Setup => Version Info and verify the versions match above information.

14 Customer Focus Page 14 of 14 CD Version Details Maxum Workstation Version (December 2012) Gas Chromatograph Portal 5.10 Maxum System Manager Maxum EZChrom 5.0 Simulated Distillation MaxBasic Editor Maxum OPC Note: System Manager remains at version 5.00 and is NOT able to backup and restore 5.10 databases. GCP is now at version 5.10 and is required to upgrade any Syscon2 to 5.10.