The disconnected Raco Catalyst Interface does not communicate directly with the Raco Catalyst system. Instead, the interface reads in OPSDATAXML files that have been generated by a Collector Utility that reads the LOG data files. Every hour the Collector reads in data and writes a new OPSDATAXML file. Each file contains data for one hour. Once OPSDATAXML files are generated, the Interface will import the data into Hach WIMS.
Although it is possible to run the Collector and Interface on the same machine this version of the Interface was designed to have the Interface and Collector on seperate machines. This Interface deals with the situation in which the Interface is not able to communicate directly with the Raco Catalyst LOG files.
To start the Collector you need to double click on the file Q12543.exe. Clicking on this file brings up the Interactive Screen.
The Collector will not start collecting data until it has been configured (notice the ERROR in the above display). Click on the Configure button to configure your settings. The Proxy Setting screen will appear to configure some basic Collector settings.
The proxy screen contains needed information on how you plan to run the Collector. You will want to check Use Standalone configuration and Start as Windows Tray Application. Click the Configure Collector button to continue configuring the collector's settings.
In the configuration screen you have two tabs of configuration settings. The General Settings tab contains information on how you want the Collector to run.
In the Source Configuration tab you configure the connection to the Raco Catalyst LOG files. "Tag" names will appear if there are any LOG files available. A "Tag" name consists of Filename:Channel #. So if you have a file CAT50.LOG and you want data from Channel #1, the "Tag" name in Hach WIMS client would be CAT50:1
When you launch the Collector it will either start as a Windows Tray Application (default) or in NT Service View and Control mode. The standard screen is below.
If the status bar shows "RUNNING" then the Collector is scheduled to run and collect the data. If the status is "PAUSED" you need to configure the connection to the source data and click the START button (which will change to PAUSE if successful).
If you start the collector and it does not appear on the screen then you can find it in the Windows System Tray (by default the Collector is hidden when it is started unless errors occur during startup). You can double click on it's icon in the System Tray to make it visible.
When the Collector is installed to run as a service you are presented with the following screen when starting the application.
From here you can see if the Service is running, configure it, stop it, start it, and view the activity log files.