Summary of 4.10c Patch 3 Changes

Transcription

1 MAXUM 4.10c Patch 3 Read the Summary of 4.1c Patch 3 section to determine if you need Patch 3. The Maxum 4.1c Patch 3 Upgrade Procedure section describes how to upgrade your workstation and individual Maxum units. The "Maxum 4.1c Patch 3 Version Number section lists the software versions that will be installed. GC or NAU software versions should be checked against this list following a GC or NAU upgrade. The Maxum Performance Optimization Procedures section describes further optimizations that are recommended for improving performance. Summary of 4.10c Patch 3 Changes Database & MMI Changes 1. Moved creation of validation alarm before the transmit of results for the last stream in a validation sequence. This allows the status for Modbus to reflect a failed validation. 2. Fixed status on some I/O. A uninitialized status was being reported for some I/O, when it was operating normally. In most cases this was not important, but for ADV + configured detectors, it was a problem. 3. Fixed modbus status for validation when manual cal is previously run. 4. Fixed creation of Currentstream modbus addresses in the address range 5. Fixed delete of pulse for remotely accessed DOs 6. Improved reliability of startup for DO and DI remotes used in Modbus Syscon OS Changes 1. Fixed excessive time to run certain MaxBasic programs 2. More debug available to detect failures in communication and memory problems 3. Added hourly timestamp on debug port 4. "NETSTAT -s" displays additional information about errors and problems 5. Improvements were added to guard against an overload of external TCP messages 6. Improvements were made in memory buffer handling to guard against overloaded communications SNECON Changes

2 1. Fixed problems with lost communication between the Syscon and the SNE that was causing SNE resets 2. Added new MEM command showing the content of selected memory regions (option -DB, -D1 and -D2) 3. Improvements for SNE debug 4. Fixed SimDis D86 result. 5. Fixed math calculation that was causing peaks to not be recognized if they were right on the edge (ExpectedRtTime +- width/2). 6. Fixed Modbus failures at DCS when Modbus serial communication was interrupted due to low level Ethernet communication warnings. 7. Fixed transient Buffer Overflow(1094) alarm. MAXUM 4.1c Patch 3 Upgrade Procedure Note: If your Maxum is NOT at version 4.1c you must load 4.1c prior to installing this software patch. Check for Upgrades: It is a good idea to check the Siemens Applied Automation Software Download Website for the latest 4.1c software updates. ( A readme file on the website will explain the reasons for the update. It is generally recommended that users stay current with the latest available patch if possible. As long as the workstation is updated to the latest download from the website prior to running this procedure, the analyzer will be updated to the latest software using the procedure listed below.. A. Upgrade the Workstation 1. If your Maxum System Tools are not at 4.1c, install EZChrom and System Manager from the 4.1c- 1 Maxum System Tools CD. Note: When you encounter a screen with choices to Modify, Repair or Remove you should use the default selection Repair. 2. Check the Siemens Applied Automation Website for potential 4.1c updates. ( 3. Download and Install the latest 4.1c patch. (From the website in step 2 or a Maxum System Software Patches CD)

3 B. UPGRADE SYSCON and SNE Software Note: Analyzer names cannot contain the following characters or windows will be unable to save the.amd file: \ / : *? " < >. If the analyzer name has one of these characters, the database must be backed up manually to a valid filename prior to performing the step B. (System>Unit Backup/Restore> Select analyzer from list > Enter the directory/filename you would like to use for the new.amd file >Open>Backup the analyzer 1. Place all application in HOLD for the unit being upgraded.. 2. Go to Maxum Utilities>Tools>Upgrade Unit. 3. Select Analyzer to be upgraded and press OK. 4. Enter Login & Password 5. Press OK. This will save the DB.amd file. Next it will upgrade SNEs as needed and upgrade Syscon BIOS, OS, DB and DM as needed. (The.amd is automatically backed-up as \Advance System Manager\TempUpgrade\xxx.amd or \Maxum System Manager\TempUpgrade\xxx.amd where xxx is the name of the analyzer being upgraded.) C. Restore Database 1. Use System Manager to restore the.amd file backed-up in step B: System>Unit Backup/Restore> Select analyzer from list > Select the.amd file from \Maxum System Manager\TempUpgrade directory or \ Advance System Manager\TempUpgrade directory > Restore the analyzer Note: The analyzer will be reset after the.amd file is restored to the analyzer. After the load is complete, allow 3-4 minutes for the analyzer reset to complete before proceeding to step D. D. Add New Text for Alarms 1. Use Maxum Utilities >Loader>Load MMI Language Files > Select analyzer from list >Enter Login and Password> Select Directory >Maxum System Manager or Advance System Manager\Upgrade4.10\newlang>OK (This step should take 6-7 minutes to complete.) E. Save New Text to Flash and Update Workstation Backup File 1. Use System Manager to save the text to flash and backup the new.amd file to the Workstation.: System>Unit Backup/Restore> Select analyzer from list > Enter the directory/filename you would like to use for the new.amd file >Open>Backup the analyzer

4 Maxum 4.1c Patch 3 Version Numbers: SYSCON: BIOS version: (Mar 18, 2005) OS version: V4.2.1 (Dec 16, 2005) DB version: DM version: TEXT version: SNE: OS version: 0004.j15 (Dec 19, 2005) APP version: 0004.c16 (Dec 16, 2005) Workstation Software: EZChrom: System Manager: Other Software: APC: MaxBasic: SimDis.dll MAXUM Performance Optimization Procedures September 13, 2005 The following performance improvements will significantly improve operation of Maxum by reducing information that is typically not used. The analyzer should be at 3.2b Patch 2, 4.0b Patch 4, 4.1c or later for these optimizations. It is recommended that you read through each of the procedures prior to implementing them.

5 A. Procedure to Remove Excess Gating on Unused Detectors: Unused detector channels need to be turned off for the entire cycle in order to optimize system performance. (Unused channels that do not have the integration turned off can cause a significant processing load even though the information is not used.) 1) Load the method to be optimized into EZChrom on the Workstation. 2) Select the first unused detector. 3) Select (Method>>Integration Events) 4) Add an Integration Off entry with start and stop times that bracket the full cycle. (Typically 8 to Cycle End) 5) Repeat steps 2-5 for all unused detectors. 6) Go to Procedure B step 3 to optimize performance parameters prior to saving the method. B. Procedure to Turn Off EZChrom Performance Parameters: EZChrom performance parameters that are not typically used can have the calculations turned off (example = theoretical plates, baseline noise etc.). This procedure will reduce SNE processing requirements at the end of each cycle. 1) Open EZChrom Instrument on the Workstation for the application being modified. 2) Import the method from the analyzer if the current method in the workstation does not match the method in the analyzer. 3) From the Menu Bar select: Method>>Advanced, then select the Column/Performance tab. 4) At the bottom of the "Advanced Method Options" window, uncheck all of the calculation methods that are checked. 5) At the bottom of the "Advanced Method Options" window, uncheck Calculate performance parameters for this channel. 6) Select the next detector channel at the top of the main screen and repeat steps 4-5 for each channel.

6 7) Export the method to the analyzer. (Go to Procedure C step 3 to export the method with maximum performance improvements.) 8) Save the method on the Workstation (File>>Method>>Save or Save As) 9) Repeat steps 1-8 for each Analyzer Application to be modified. Note 1: Procedure B. should not be used on analyzers with the Total Sulfur application since this application requires one of the performance parameters that would be turned off. Note 2: If performance parameters such as theoretical plates and peak asymmetry are monitored using the Maxum OPC Server the performance parameters must be left ON. C. Procedure to Minimize EZChrom Data Unpacking: The Minimum Data Procedures will reduce Syscon processing at the end of each cycle. When implemented, the analyzers will unpack only compact results into the database. (Concentration values plus peak details used by OPC) All data will still be viewable in EZChrom on a workstation when data is imported. Minimum Data Procedure using 4.1 Workstation 1) From EZChrom select (File>>Method>>Import) 2) Highlight the first method in the pop-up window and select Import. 3) From EZChrom select (File>>Method>>Export) 4) After the Method export window pops up, open the list box in the lower right hand corner. 5) Select Compact results only from the list box. 6) Check the Save settings box at the bottom of the window. This will cause your default method export to use the Compact results only setting by default the next time you export a method to this application. 7) Press (Export). 8) Highlight the same method imported in step 1 and press Export. 9) Repeat steps 1-8 each application. Minimum Data Procedure using 3.2b or 4.0b Workstation 1) From EZChrom select (File>>Method>>Import) 2) Highlight the first method in the pop-up window and press Import. 3) From EZChrom select (File>>Method>>Export) 4) After the Method export window pops up uncheck Create Secondary Results in the lower

7 right hand corner. 5) Check Save settings as default at the bottom of the Method export window. This will cause the Create Secondary Results box to be unchecked by default, the next time you load a method to this Maxum application. 6) Press (Export). 7) Highlight the same method imported in step 1 and press Export. 8) Repeat steps 1-7 for each application. Note: Procedure C. should not be used on analyzers with the Total Sulfur application since this application requires one of the performance parameters that would not be unpacked to the database. D. Procedure to Minimize Unnecessary I/O: The Syscon performance can be improved by disabling scanning of analog and digital inputs that are not required. The recommendation will still leave the measurement value scanning for display purposes. AI Reduction: 1) From System Manager under the first application select (Application IO) then select (AI). 2) Uncheck the Enable box and then press the Update AI button for each of the analog inputs listed. 3) Repeat steps 1-2 for each application. 4) Go to the System tables and select (Sys AI). 5) Uncheck the (scanenable) column (0 for all entries). 6) Go back to the first application and select (Application IO) 7) Check the Enable box and then press the Update AI button for each of the analog inputs required by the application. (Typical analog inputs left on are component data from continuous analyzers as well as the Measurement values for temperature and pressure controllers.) 8) Repeat step 7 for all applications. DI Reduction: 1) From System Manager under the first application select (Application IO) then select (DI). 2) Uncheck the Enable box and then press the Update DI for each of the digital inputs listed. 3) Repeat steps 1-2 for each application. 4) Go to the System tables and select (Sys DI). 5) Uncheck the (scanenable) column (0 for all entries). 6) Go back to the first application and select (Application IO)

8 7) Check the Enable box and then press the Update DI button for each of the digital inputs required by the application. 8) Repeat step 7 for all applications.