1 August 20, 2013 Maxum Workstation 5.10.10 Update Release Notes Requirements Maxum System Manager will operate best on computers equipped with a Pentium-166 or faster CPU, using at least 64 MB RAM. For installation, Maxum System Manager needs up to 250 MB of free disk space. It is possible to install and run Maxum System Manager on slower computers with less RAM. You must log in with Administrator privileges. This will ensure unrestricted access to the system registry. Otherwise, the installation will fail. Internet Explorer 6.0.2900 or higher must be installed. Maxum System Manager has been tested successfully with the following operating systems: Windows XP (Professional and Home Edition), Service Pack 3 Windows 7 (32 bit and 64 bit) Note: Windows 7 requires a patch from the following hot link: www.usa.siemens.com/gcdownloads The patch (Maxum Workstation Patch for Windows 7 Operating System) will load operating system libraries that Microsoft did not include with Windows NOTE 1: If you already have Maxum Workstation 5.10.x installed on your PC use the Maxum Workstation Update v5.10.10 update on the software download website (www.usa.siemens.com/gcdownloads). This update contains all of the changes for previous 5.10.x updates. Description: 5.10.10 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 ).
2 OLD: 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 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 then attempting to update the BIOS/Loader component. Resolution: Added two inbound firewall rules (port 920 + 1290).
4 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). 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 5.10.10 Update for Syscon 2 / Modular Oven 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.
5 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. Resolution: The software is updated to support the new controller chip that is being used on the new CIM boards. Database: 1. Problem: MicroSAM serial settings moved to the serial settings table. Symptom: MicroSAM serial port setting was not correct. Resolution: The serial setting is left intact in the system_control table. 2. 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. 3. 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. 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..
6 4. Problem: Alarm text incorrect for alarms 4120-4124. 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.
7 3. Problem: After a file conversion the date and time values did not always convert to a correct datetime format in the Modbus map.. Resolution: Fixed datetime conversion. Description of 5.10.02 Update for GC Portal / GC Network 1. Problem: GCN: MicroSAM update issue Symptom: Flashed MicroSAM (2.8, 3.x) cannot be upgraded with GCP 5.10. 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: GCN shows column Serial Number. This column is used to highlight problems for the Data Logger. Shown problems might be (a) no serial number or (b) duplicate serial numbers. Resolution: Both missing and duplicate serial numbers are now handled properly and highlighted. 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.
8 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 method from source (MBM file/ Ax method). Symptom: After modifying a method, if you decide to discard the changes and reload the method to start over are not able to. Resolution: Added context menus on the method tree node for reloading a method from its source (MBM file or analyzer method). Description of 5.10.02 Update for Syscon 2 and Modular Oven 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 4. Problem: PrintService was not always working correctly.
9 Symptom: Printout to serial port or debug port was wrong for standard report logs and reports from MaxBasic. Resolution: 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 5.10.02 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
10 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 8. 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. 9. 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 it s previous settting 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. 10. 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 1.0. 11. 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.
11 12. 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:0.11.4.2, when the pulse activates it will be seen on DO 0:0.0.4.2 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:0.11.4.2 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.
12 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 5.10 Changes for Syscon 2 and Modular Oven Database: 1. Enhancement: Added formula capability to result table. The Formula Editor assists in adding and testing formulas to the result table and is accessed through GCP. 2. Enhancement: Changed debug levels to be more consistent and provided a document describing what each level turns on. See rtbuglevels.xls 3. Enhancement: Implemented startup values for AO and DO that can be used optionally. When defined, the analyzer AO or DO will return to the startup values after a reboot. 4 Enhancement: Reset SNE (I2CDB) when simulation is changed. Symptom: SNE does not recognize a change in simulation mode. Resolution: Changing simulation attribute now resets SNE. 5. Enhancement: Implemented lastused in printer and host and lastreceived in modbus_addmap (informational attributes) Symptom: Certain tables have no field to display time or date stamps. Resolution: Date and time stamp is processed at the end of each cycle and displayed as an informational attribute. 6. Enhancement: Informational attributes were requested for the method table. Last download time and last accept cal time attribute fields are now implemented in the method table. 7. Fix: Corrected connection of 5.0/5.1 Database to 4.x unit.
13 Symptom: When using a connection infrequently (a modbus_addmap DOSET address used occasionally to start validation on a remote 4.x unit), the connection is lost and is not able to be reconnected. Resolution: removed cleanup of connection table so that the connections remain over time. 8. Enhancement to ModbusTCP handling of closed connections to improve reusability of TCP connections in the case of problem networks. 9. Fix to connections from Syscon2 to Syscon1/plus units for remote I/O, transmission of results. Problems were identified when 5.0 GC transmitted values to a 4.x unit on problem networks where the connection was closed HMI 1. Description: Allow add and delete of CAN cards for version prior to 5.0 Symptom: No way to add CAN cards and cards that are already included cannot be deleted. Resolution: Can cards can be added or deleted for earlier versions. 2. Description: Fixed functionality on all screens for versions 4.0 and above. Symptom: Some screens show inconsistencies between software versions. Resolution: Functionality was tested thoroughly through all software levels to ensure a smooth transition. 3. Enhancement: Added support for Maxum Touchscreen door for Syscon 2 4. Enhancement: Redesigned calibration and validation screens Symptom: No uniformity between Calibration and Validation screens. Resolution: Run, Hold and Stop buttons were repositioned. (Also added warning screens) 5. Fix to modification of temperature or pressure program on the Method screens. Fixed the adjustment of the time and setpoint. 6. Fixed truncation of initial character in analyzer name at the top of the screen when the analyzer name was greater than 16 characters. 7. Fixed occasional HMI hang up at reset where a message box popped up with Version 0 message. DBConverter 1. Enhancement: Added features for conversion to and from emsne hardware IDs Symptom: DBConverter needs to recognize emsne hardware. Resolution: DBConverter check box is available in DB converter table to convert Applicable hardware IDs to emsne.