Romet Troubleshooting

General Troubleshooting

 Review the General Troubleshooting page for basic tips and getting help.

Troubleshooting Topics

The following troubleshooting scenarios will continue to expand with each document release.

Scenario #1: Invalid Access Code

Problem: Unable to poll or collect history from device due to sign-on failure.

TX,asiRometAdem,Romet Lab RTU,TX:  [01]SN,33336[02]vqAA[03]B9F9[04]
RX,asiRometAdem,Romet Lab RTU,RX:  [01]27[03]07A4[04]
Error,asiRometAdem,Romet Lab RTU,ERROR Response: start 0: length 9
Error,asiRometAdem,Romet Lab RTU,Status Response from Device - Code 27: Invalid access code error
Error,asiRometAdem,Romet Lab RTU,Sign-on failed.
Error,asiRometAdem,Romet Lab RTU,Message did not receive a good response.

Meaning: The access code used in the sign-on message was rejected by the device.

Corrective Action: Find the correct access code, re-configure the device in ACM, and try again.

Scenario #2: Invalid Sign-On Code

Problem: Unable to poll or collect history from device due to sign-on failure.

TX,asiRometAdem,Romet Lab RTU,TX:  [01]SN,33333[02]vq12[03]455C[04]
RX,asiRometAdem,Romet Lab RTU,RX:  [01]20[03]9E33[04]
Error,asiRometAdem,Romet Lab RTU,ERROR Response: start 0: length 9
Error,asiRometAdem,Romet Lab RTU,Status Response from Device - Code 20: Signon error
Error,asiRometAdem,Romet Lab RTU,Sign-on failed.
Error,asiRometAdem,Romet Lab RTU,Message did not receive a good response.

Meaning: The sign-on code used in the sign-on message was rejected by the device.

Corrective Action: Find the correct sign-on code for this particular type of instrument, re-configure the device in ACM, and try again. Normally, the sign-on code property in the device's ACM configuration is left blank so that the known default value is used.

Scenario #3: Invalid Site ID

Problem: Unable to poll from device because of SITEID error.

Error,asiRometAdem,Romet Lab RTU,Site ID mismatch! Configuration 1 = 17194223, RTU 1 = 17194223; Configuration 2 = 12345678, RTU 2 = 00000000

Meaning: Site ID1/2 uniquely identify the end device you are trying to communicate with. The Site ID in the configuration does not match what was returned from the device.

Corrective Action: Verify ACM is connecting to the correct device using the correct connection parameters. If the device's ID has been changed, change your ACM configuration to match this Site ID.

Scenario #4: Unable to publish upload data because of missing archive object.

Problem: Unable to publish upload data.

Error,asiRometAdem,Romet Lab RTU,Audit 1 is enabled for collection but does not have an Archive Object assigned. Verify configuration.

Meaning: An upload type is enabled in your Romet device object but no Archive object is assigned to it.

Corrective Action: You must create and assign an archive object for each type of upload you want your Romet device to collect. 

Scenario #5: Audit upload does not work correctly, or published data is incorrect, after making audit configuration changes on the RTU.

Problem: Audit upload publish data is incorrect or incomplete.

Meaning: ACM reads the device's audit configuration and publishes data based upon internally stored data tables. Because of a configuration change on the RTU, ACM and the device are not in sync.

Corrective Action: On the Command tab of the device in ACM, issue the 'Retrieve Audit Log Config During Next History Poll' command. Next issue the 'Move Audit Pointer Back' command and select the time of the last known good record, or issue 'Reset Audit Pointer' if no good records have been uploaded. Issue the command to 'Retrieve History'.

Scenario : Item's OPC status is 'Bad - Configuration Error'

Problem: No data is returned for item after polling.

Meaning: The item address specified is not valid on the device.

Corrective Action: Use the OEM's documentation to determine which item addresses are valid for the device type.