OPC90 Server
10 Troubleshooting Hints
This section is provided to help the user identify and correct problems that may
arise as a result of incorrectly setting up the OPC90 Server interface. It is
provided as a general guide to allow the user to decipher normal and abnormal
operation. If this does not help, OPC90 Server can be enabled to post additional
error messages to OPC90 Server log files using the DEVICE block DEBUG_LOG
attributes. To change these attributes right mouse click on the Device block and
select or deselect Show Receive, Show Send, Show Errors and/or Show Events.
Note these flags can be changed in runtime. Remember to save the configuration
if these flags are to be saved. Use these DEBUG_LOG attributes to track down
tough problems and discover hard to find configuration errors. Afterwards
remember to disable all of its options (except Errors), since leaving them enabled
can consume large amounts of disk file space.
After installing the OPC90 Server for the first time and thereafter when it is then
started up in Monitor mode or when an OPC Client connects to it, the OPC90
Server DEVICE block will automatically begin talking with the Bailey interface.
The startup pattern will vary based on the type of Bailey interface being utilized.
The first thing you should notice is the Bailey interface serial processing card
LEDs begin to sequence. Shortly thereafter you may hear the loop interface
termination unit relays click on and off several times as the driver is identifying
the Bailey interface type. Just prior to downloading the OPC90 Server block
database to the Bailey interface, it will be restarted, and the loop interface
termination unit relays will click off isolating it from the communication loop. Next
you should observe the Bailey interface serial processing card LEDs sequence at
a steady rate as the OPC90 Server block database is being downloaded. Upon
completing the database download, the Bailey interface will be commanded on-
line, at which time the loop interface termination unit relays will click on and the
loop interface card LEDs begin to count loop messages. Thereafter, the Bailey
interface serial processing card LEDs will sequence steadily based on the
exception report poll interval setup by in the DEVICE block and individual OPC90
Server POLL blocks (when utilized).
If you experience problems with establishing communication between the OPC90
Server and the Bailey interface, if possible, it is a good idea to verify the setup by
trying to communicate using the Bailey TXTEWS software. Generally if this
software functions OK, you should not experience problems with OPC90 Server.
All Bailey interfaces have a series of four or eight red LEDs on the hardware
module that processes serial communication and manages its database. Don't
confuse this card with the module that handles the interface with the Bailey
communication loop which also has a series of LEDs. An indication that
communication with the BAILEY interface is occurring can be determined by
looking at the serial processing card LEDs. (Hereafter, these LEDs will be
referenced as Bailey interface LEDs.) The Bailey interface LEDs count
The RoviSys Company Version 7.0 Page 135
To Next Page
Loading...