Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Code Block
languagetext
themeConfluence
titleProblem - Log Samples
16:19:00.576,TX,asiTCPIP,ControlPort,"Control" S:asiRometAdem,Romet Lab RTU,TX:  [01]SN,3333233336[02]vq04vqAA[03]60ABB9F9[04] 
16:19:00.626,RX,asiTCPIP,ControlPort,"Control" R:asiRometAdem,Romet Lab RTU,RX:  [01]27[03]07A4[04]

16:19:00.627,Error,asiMERCURY,ControlasiRometAdem,Romet Lab RTU,ERROR Response: start 0: length 9

16:19:00.628,Error,asiMERCURY,Control,asiRometAdem,Romet Lab RTU,Status Response from Device - Code 27: Invalid access code : 27 
16:19:00.629,Error,asiMERCURY,Controlerror
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

...

Code Block
languagetext
themeConfluence
titleProblem - Log Samples
16:24:31.706,TX,asiTCPIP,ControlPort,"Control" S:asiRometAdem,Romet Lab RTU,TX:  [01]SN,33333[02]vq01vq12[03]273F455C[04]

16:24:31.757,RX,asiTCPIP,ControlPort,"Control" R:asiRometAdem,Romet Lab RTU,RX:  [01]20[03]9E33[04] 
16:24:31.759,Error,asiMERCURY,ControlasiRometAdem,Romet Lab RTU,ERROR Response: start 0: length 9 
16:24:31.760,Error,asiMERCURY,Control,Signon error: 20 
16:24:31.762,Error,asiMERCURY,ControlasiRometAdem,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.

...

Corrective Action: Find the correct sign-on code for this particular type of instrument, re-configure the device in ACM, and try again. The most commonly shared code is vq99. Sign-on codes for specific devices may vary depending on firmware version (consult Honeywell or Honeywell documentation to be sure).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

...

Code Block
languagetext
themeConfluence
titleProblem - Log Samples
13:53:29.016,Error,asiMERCURYasiRometAdem,MercuryRomet Lab Protocol2RTU,Site IdID mismatch: configuration! Configuration 1 = 17194223, RTU 1 = 0000000117194223; device 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:  The correct Site ID is printed in the error message. Change your 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.

...

Code Block
languagetext
themeConfluence
titleProblem - Log Samples
13:40:51.879,Info,asiMERCURY,Control,History due: CFG=0; AUD=1; ALM=0; EVT=0; HYP=0 
13:40:51.879,Error,asiMERCURY,Control,Audit Upload Terminated. Failed to get properties for archive object (ID=0). 13:40:51.883,Error,asiMERCURY,Control,Task: history request issued/detected but no poll messages were found. Please check active items and/or deviceError,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 Mercury 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 Mercury Romet device to collect. This archive object can be empty (defaults) but you must assign an archive object for each type of upload. 


Scenario #5:

...

Problem: Unable to collect or publish events.

Code Block
languagetext
themeConfluence
titleProblem - Log Samples
13:27:45.446,TX,asiMERCURY,Mercury Protocol2,TX: [01]RE[02]002[03]5D3E[04] 
13:27:49.457,Error,asiMERCURY,Mercury Protocol2,Communication time-out

Meaning: The protocol is timing out because the device does not support events.

...

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.