XM Firmware Revision 3

Release Notes XM Firmware Revision 3 What s in These Release Notes These release notes provide the following information. For information about See page Revision 3 Enhancements 1 Special Issues When Upgrading to a New Major Revision 3 Revision 3 Corrected Anomalies 5 Revision 3 Enhancements This section describes the new features in major revision 3. General Revision 3 Enhancements Configurable I/O Poll Response In Revision 3, you have the ability to configure the content and size of the I/O Poll response. You can select from multiple Assembly Object instances, which pre-arrange the Poll data in different orders. Furthermore, you can set the size of the Poll response to truncate unneeded data from the end of the selected Assembly structure. This feature is added to the XM-12x and XM-36x firmware. 1

2 XM Firmware Revision 3 XM-12x Revision 3 Enhancements Synchronized Measurements with Tachometer Pulses > 1 Revision 3 permits synchronous sampling in conjunction with multiple tachometer pulses per revolution. However, phase (vector) alarms are still prohibited with multiple tachometer pulses per revolution. Improved Alarm Behavior In Revision 3, the alarm behavior has been improved as follows. For alarms with a Speed Range enabled, the alarm status transitions to Disarm (instead of Normal as in revision 2) while the measured speed is outside the alarm s defined Speed Range. If the Speed Range is disabled, a tachometer fault condition will not cause an alarm associated with the Overall, Gap, Smax, or gse measurement to transition to Tachometer Fault status regardless of whether synchronous sampling is selected for the corresponding channel. This is because these measurements are not dependent on the tachometer. Alarms with a Speed Range enabled will transition to Tachometer Fault status when there is a tachometer fault because the alarm is dependant on the tachometer. New Default Settings The default value of the DC Bias Time Constant parameter has changed from 11.0 to 1.769. The default value of the Sum Harmonics Start Order parameter has changed from 1 to 4. XM-320 Revision 3 Enhancements Channel Names Revision 3 supports a new Name parameter for each channel. New Default Settings The default value of the DC Bias Time Constant parameter has changed from 11.0 to 1.769.

XM Firmware Revision 3 3 XM-440 Revision 3 Enhancements Support for Any Firmware Revision of Existing Measurement Modules In Revision 3, the XM-440 module can operate with any existing revision of measurement module firmware. It should continue to work with any future firmware revisions for existing measurement modules as long as the format of the measurement module s COS message does not change. Stop Scanning in Program Mode In Revision 3, the XM-440 stops scanning its slaves when it is put in Program Mode. This closes the Poll connection, making it possible to reconfigure the slave s I/O Poll response. Module Status Flashes Red for Configuration Errors In Revision 3, the XM-440 firmware flashes either the Network Status LED or the Module Status LED red depending on the communication problem. If the communication problem is due to an absent slave or the slave is not responding, the Network Status LED flashes red to indicate a communications timeout condition. But if the communication problem is due to the slave being a different device than what is expected, the Module Status LED flashes red to indicate the master is not configured correctly. New Default Settings The default value of the Interscan Delay parameter has changed from 80 to 400. The default value of the Expected Packet Rate parameter has changed from 160 to 200. Special Issues When Upgrading to a New Major Revision Consider the following special issues before upgrading your firmware to a more recent major revision. If a particular module or major revision is not listed then there are no special issues to consider.

4 XM Firmware Revision 3 General Considerations If you use the XM Serial Configuration Utility, you will need to install and use the version of the XM Serial Configuration Utility that corresponds to the new firmware s major revision. You can download the appropriate XM Serial Configuration Utility from the XM Firmware Update page at the following URL: http://support.rockwellautomation.com/ If you use Enterprise Online Configuration Utility or RSNetWorx with your XM modules, you will need to download and register the EDS files that correspond to the new firmware s major revision. You can download the appropriate XM EDS files from the following URL: http://www.ab.com/networks/eds. General purpose master/scanner devices such as the XM-500 and 1756-DNB typically use the slave's major revision as one of the keys used to identify the slave module. So if you update the slave's firmware to a new major revision then you may need to update the configuration of any master/scanners that own this slave. Note that the XM-440 Master Relay module does not use the slave's major revision as an identification key so you won't need to update the XM-440's configuration for this reason. XM-12X Firmware Upgrade Considerations Upgrading XM-120 Revision 1 to Revision 2 or Greater Any saved configuration will be lost and the factory defaults will be restored. The 23.8 Hz high pass filter that existed in the Series A hardware is no longer supported. If you have Series A hardware, the 23.8 Hz filter will be identified by the configuration software as a 40 Hz filter. DO NOT USE THIS FILTER because it will produce incorrect data. The other high pass filter selections are fine.

XM Firmware Revision 3 5 The size of the I/O Poll Response message increases from 56 to 120 bytes. This means: If you are using an XM-440, then you need to upgrade the XM-440 to Revision 2 firmware or greater. The scan list of any XM-500 or any other Master/Scanner besides the XM-440 will have to be reconfigured to support the larger Poll message size. Any ladder logic programs that rely on the mapping of the scan list data may have to change to reference the new mapping in the modified scan list. Any PanelView monitor that may be listening for a 56 byte Poll Response message from the XM-120 will have to be changed to expect a 120 byte message. Upgrading XM-12X Revision 2 to Revision 3 or Greater If you have an XM-440 and plan to change the size of the XM-12X I/O Poll Response message from its default size of 120 bytes, you must also upgrade the XM-440 firmware to Revision 3 or greater. XM-440 Firmware Upgrade Considerations Upgrading from Revision 1 to Revision 2 If you have any XM-120 slave modules, you need to update them to Revision 2 firmware as well. Revision 3 Corrected Anomalies This sections describes anomalies corrected in recent firmware revisions. The corrected anomalies are organized by the firmware revision that corrected them. XM-120/121 Firmware Revisions Known The Relay object's Class level (instance 0) Reset service does not function properly and can lead to a reset/lock-up of the module if executed. The XM software tools do not provide an interface for resetting all relays, just individual relays. So this anomaly would be encountered only if you exercised this service manually (e.g. Class Instance Editor).

6 XM Firmware Revision 3 XM-120/121 Revision 3.017 Table 1 Corrected Anomalies Possible offset error in the Overall and Time Waveform measurements. Phase measurements not working properly. If there was an external DC bias applied to the input signal at the moment the module was powered up with a saved configuration, an offset error may have been introduced into the Overall and Time Waveform measurements. This offset error was most noticeable when IEPE power was configured to be on for the channel s transducer. Phase measurements did not work properly when more than 1 pulse per revolution was selected for the transducer. XM-120/121 Revision 3.015 Table 2 Corrected Anomalies Product Service Advisory Measurement values stopped updating after 131.7 days of continuous operation. Failed firmware update via Ethernet. All measurement values stopped updating after 131.7 days of continuous Run Mode operation if the tachometer was disabled (Number of Pulses per Revolution set to zero). The overall measurement stopped updating after 131.7 days of continuous Run Mode operation regardless of whether the tachometer was enabled. Refer to Product Service Advisory ICM 2004-07-001 for more information. A firmware update conducted over Ethernet via an XM-500 module would fail if the XM-500 was simultaneously scanning the module. The XM-120/121 module would require a reset after the failure. This revision eliminates the need to remove the XM-120/121 from the XM-500 scanlist before attempting to update the XM-120/121 firmware via Ethernet. XM-120/121 Revision 3.014 Table 3 Corrected Anomalies Possible erroneous measurement values for spectrum related measurements (band, vector, etc.). The module might have produced erroneous measurement values for the spectrum related measurements (band, vector, etc.) when synchronous sampling was selected and the measured speed changed relatively fast.

XM Firmware Revision 3 7 XM-120/121 Revision 3.013 Table 4 Corrected Anomalies Issues with the tachometer (speed) measurement. The following improvements have been made to the tachometer (speed) measurement. Auto trigger will work down to 0.1 Hz. Improved recovery from tachometer fault at low speeds after tach input resumes. Improved Auto trigger to handle larger low frequency noise (e.g. noise from shaft movement when the tachometer has multiple pulses per revolution). The manual trigger threshold is no longer affected by the trigger slope selection. Improved the transducer DC Bias measurement. XM-120/121 Revision 3.011 Table 5 Corrected Anomalies Possible incorrect Not 1X measurement. Speed measurement might not update smoothly on coast down. The value of the Not 1X measurement was incorrect if the Number of Spectrum Lines was configured to be equal to the Fmax. The Speed measurement value did not always update smoothly on coast down if synchronous sampling was selected. XM-122 Firmware Revisions XM-122 Revision 3.021 Table 6 Corrected Anomalies Possible offset error in the Overall and Time Waveform measurements. Phase measurements not working properly. Reset service did not properly reset all the relays and could have led to a reset/lock-up of the module. If there was an external DC bias applied to the input signal at the moment the module was powered up with a saved configuration, an offset error may have been introduced into the Overall and Time Waveform measurements. This offset error was most noticeable when IEPE power was configured to be on for the channel s transducer. Phase measurements did not work properly when more than 1 pulse per revolution was selected for the transducer. The Relay object class level (instance 0) Reset service did not properly reset all of the relays and could have led to a reset/lock-up of the module. The XM software tools do not provide an interface for resetting all relays, just individual relays. So this anomaly would have been encountered only if you exercised this service manually (e.g. Class Instance Editor).

8 XM Firmware Revision 3 XM-122 Revision 3.019 Table 7 Corrected Anomalies Product Service Advisory Measurement values stop updating after 131.7 days of continuous operation. Failed firmware update via Ethernet. All measurement values stopped updating after 131.7 days of continuous Run Mode operation if the tachometer was disabled (Number of Pulses per Revolution set to zero). Refer to Product Service Advisory ICM 2004-07-001 for more information. A firmware update conducted over Ethernet via an XM-500 module would fail if the XM-500 was simultaneously scanning the module. The XM-122 module would require a reset after the failure. This revision eliminates the need to remove the XM-122 from the XM-500 scanlist before attempting to update the XM-122 firmware via Ethernet. XM-122 Revision 3.018 Table 8 Corrected Anomalies Possible erroneous measurement values for spectrum related measurements (band, vector, etc.). The module might have produced erroneous measurement values for the spectrum related measurements (band, vector, etc.) when synchronous sampling was selected and the measured speed changed relatively fast. XM-122 Revision 3.017 Table 9 Corrected Anomalies Issues with the tachometer (speed) measurement. The following improvements have been made to the tachometer (speed) measurement. Auto trigger will work down to 0.1 Hz. Improved recovery from tachometer fault at low speeds after tach input resumes. Improved Auto trigger to handle larger low frequency noise (e.g. noise from shaft movement when the tachometer has multiple pulses per revolution). The manual trigger threshold is no longer affected by the trigger slope selection. Improved the transducer DC Bias measurement. XM-122 Revision 3.016 Table 10 Corrected Anomalies Poor recovery from tachometer faults. Previously, if either channel was configured for synchronous sampling, then a tachometer signal frequency greater than 10 Hz was required in order to recover from a Tach Fault condition. Now tachometer signals as low as 1 Hz can remove a Tach Fault.

XM Firmware Revision 3 9 XM-122 Revision 3.015 Table 11 Corrected Anomalies Possible incorrect Not 1X measurement. Speed measurement might not update smoothly on coast down. The value of the Not 1X measurement was incorrect if the Number of Spectrum Lines was configured to be equal to the Fmax. The Speed measurement value did not always update smoothly on coast down if synchronous sampling was selected. XM-320 Firmware Revisions Known Anomalies Firmware updates to this module that are conducted over Ethernet, through an XM-500, may fail if the XM-500 is the master of the module and scanning it. The module will need to be reset after the failure. You should remove the module from the XM-500 scanlist before attempting to update the module's firmware through the XM-500. The Relay object's Class level (instance 0) Reset service does not function properly and can lead to a reset/lock-up of the module if executed. The XM software tools do not provide an interface for resetting all relays, just individual relays. So this anomaly would be encountered only if the user exercised this service manually, perhaps with a Class Instance Editor tool. XM-320 Revision 3.005 Table 12 Corrected Anomalies Module unable to automatically clear Major Unrecoverable Fault. The XM-320 firmware performs a power supply voltage check on power up and when transitioning from Program Mode to Run Mode. In previous firmware revisions, if the power check failed then a Major Unrecoverable Fault was indicated (MS LED solid red). It was necessary to cycle power to clear this fault. In this revision, a failed power check results in a Major Recoverable Fault indication (MS LED flashes red) and the fault will clear automatically when the correct power supply voltage is applied. It is not necessary to cycle power when this fault occurs.

10 XM Firmware Revision 3 XM-360/361/362 Firmware Revisions Known Anomalies Firmware updates to this module that are conducted over Ethernet, through an XM-500, may fail if the XM-500 is the master of the module and scanning it. The module will need to be reset after the failure. You should remove the module from the XM-500 scanlist before attempting to update the module's firmware through the XM-500. The Relay object's Class level (instance 0) Reset service does not function properly and can lead to a reset/lock-up of the module if executed. The XM software tools do not provide an interface for resetting all relays, just individual relays. So this problem would be encountered only if you exercised this service manually (e.g. Class Instance Editor). XM-36x Revision 3.013 Table 13 Corrected Anomalies Channel 1 measurements possibly affected by noise. There was an uninitialized variable that made it possible for the channel 1 measurements to be affected by noise. XM-36x Revision 3.011 Table 14 Corrected Anomalies Possible low temperature readings in the XM-361. Possible measurement saturation in XM-361. Incorrect value in the 10 Cu RTD table. 4-20 ma Output parameter might have been incorrect. Under the following combination of circumstances, the XM-361 produced low temperature readings: Using RTDs without any leadwire resistance. Channel has a negative offset calibration. It was possible for XM-361 measurements to saturate at less than full scale if the various channels were configured for a wide variety of thermocouple types and ranges. 40 deg C was incorrect in the 10 Cu RTD lookup table. The actual current output was correct. The corresponding parameter value read via DeviceNet or the serial port may have been wrong.

XM Firmware Revision 3 11 XM-36x Revision 3.009 Table 15 Corrected Anomalies Sensor Range parameters were always interpreted as degrees C. Unsatisfactory accuracy for XM-362. Sensor High Scale Limit and Low Scale Limit parameters were interpreted as degrees C even when degrees F was selected as the temperature units. Improved measurement accuracy for XM-362. XM-440 Firmware Revisions Known Anomalies Firmware updates to this module that are conducted over Ethernet, through an XM-500, may fail if the XM-500 is the master of the module and scanning it. The module will need to be reset after the failure. You should remove the module from the XM-500 scanlist before attempting to update the module's firmware through the XM-500. XM-440 Revision 3.013 Table 16 Corrected Anomalies Relay status bits in the COS Assembly (instance 100) did not clear. When the XM-440 transitioned into Program Mode, any activated but unlatched relays deactivate as expected, but the corresponding relay status bits in the COS Assembly (instance 100) did not clear like they should have. This gave the mistaken impression that the relay was activated when in actuality it was not. If the relay was disabled while in Program Mode then the relay status bit in the COS Assembly would remain set even after returning to Run Mode. XM-440 Revision 3.011 Table 17 Corrected Anomalies Module Status LED might not have functioned properly. Under certain circumstances, the Module Status LED could get stuck flashing red when it was supposed to be green. XM-440 Revision 3.010 Table 18 Corrected Anomalies No support for the XM-120 Eccentricity module. Added support for the XM-120 Eccentricity Module.

XM is a registered trademark of Entek IRD International, a Rockwell Automation company. DeviceNet is a trademark of the Open DeviceNet Vendor Association (ODVA). www. rockwellautomation.com Corporate Headquarters Rockwell Automation, 777 East Wisconsin Avenue, Suite 1400, Milwaukee, WI 53202-5302 USA, Tel: (1) 414 212 5200, Fax: (1) 414 212 5201 Headquarters for Allen-Bradley Products, Rockwell Software Products and Global Manufacturing Solutions Americas: Rockwell Automation, 1201 South Second Street, Milwaukee, WI 53204-2496 USA, Tel: (1) 414 382 2000, Fax: (1) 414 382 4444 Europe/Middle East/Africa: Rockwell Automation SA/NV, Vorstlaan/Boulevard du Souverain 36-BP 3A/B, 1170 Brussels, Belgium, Tel: (32) 2 663 0600, Fax: (32) 2 663 0640 Asia Pacific: Rockwell Automation, Level 14, Core F, Cyberport 3, 100 Cyberport Road, Hong Kong, Tel: (852) 2887 4788, Fax: (852) 2508 1846 Headquarters for Dodge and Reliance Electric Products Americas: Rockwell Automation, 6040 Ponders Court, Greenville, SC 29615-4617 USA, Tel: (1) 864 297 4800, Fax: (1) 864 281 2433 Europe/Middle East/Africa: Rockwell Automation, Herman-Heinrich-Gossen-Strasse 3, 50858 Köln, Germany, Tel: 49 (0) 2234 379410, Fax: 49 (0) 2234 3794164 Asia Pacific: Rockwell Automation, 55 Newton Road, #11-01/02 Revenue House, Singapore 307987, Tel: (65) 6356 9077, Fax: (65) 6356 9011 12 Copyright 2005 Rockwell Automation, Inc. All rights reserved. Printed in the U.S.A.