Setting Up a Xuri Wave on Chronicle

What you will need

• A fully installed and tested Xuri Wave.
• A Chronicle gateway installed on the same ethernet network, see Installing the Chronicle Gateway Software
• An email with the Chronicle gateway configuration file or a Chronicle admin account for the relevant organization.
• The Field Service password for the Xuri instrument

Obtain the gateway configuration

1. If you have been provided with a gateway configuration file already, you can skip this section.
2. Otherwise, create a new instrument record for the Xuri if one does not already exist, making sure to select "Xuri Wave" from the dropdown box for "Device Type".
3. Now you can export the gateway configuration for this instrument by checking the box next to it in Production->Instruments and then selecting Export gateway config.

Altering the Configuration of the Xuri

Tools->System Properties

Tools-

Tools->System Properties->Options

Tools->System Properties->Edit->Advanced settings

Ensuring OPC security settings will allow remote access

Details on how this can be configured can be found in this article: Configuring OPC connectivity for Unicorn Devices (Xuri Wave and Äkta)

Ensure gateway is authorised for remote access

If the Chronicle gateway and the Xuri rocker are part of the same Windows domain, then no further action is required. If they are not part of a domain then it is essential that both the Xuri rocker and the Chronicle gateway have independently defined the same Crispo user with the same password. The Chronicle gateway LogUploader service should be configured to run as this user.

You can find out the whether your computer is part of a workgroup or domain from this screen:

Testing

As soon as Xuri connects successfully Chronicle will begin to capture a 'Daily log' showing the real time status and history of the Xuri sensors. Verify that a daily log with today's date is listed in the data records for this instrument. Verify that applying gentle pressure to the Xuri tray causes the reported mass to increase.

Troubleshooting

How to access DCOM error messages

Detailed information on errors caused by incorrect DCOM configuration is logged in the Windows event log. Add the following Windows registry entries to enable this logging.

CMD -> regedit

Below the key

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Ole\

Add the following DWORD values

ActivationFailureLoggingLevel 1
CallFailureLoggingLevel 1

After a reboot you will be able to see OPC error messages in the Windows Event log

How to independently test OPC access

Matrikon provide a free testing tool which can browse OPC tags. Try installing this on the same machine as your Chronicle gateway and see if you can browse any OPC tags.

https://www.matrikonopc.com/products/opc-desktop-tools/opc-explorer.aspx