EasyManua.ls Logo

RoviSys OPC90 - Appe Ars T O B E Communicating B U T N O Data Is Bein G Received; Not All B Locks a R E Receiving D Ata

Default Icon
146 pages
Print Icon
To Next Page IconTo Next Page
To Next Page IconTo Next Page
To Previous Page IconTo Previous Page
To Previous Page IconTo Previous Page
Loading...
OPC90 Server
10.4 Appears To Be Communicating But No Data is Being Received
If the Bailey interface LEDs sequence at a very steady and periodic rate this
means the server is connected to the Bailey interface but the OPC90 Server
DEVICE block communication parameters might not be set correctly. These
settings are determined by the DEVICE block’s Primary and Secondary port
properties. Note that these attributes can be changed while the driver is on-line.
1.) Verify the baud rate settings match between the Bailey interface and
COM port the OPC90 Server DEVICE block driver is using.
2.) Verify the parity (usually none) and stop bits (usually 1) match between
the Bailey interface and COM port the server is using.
3.) Verify the Bailey interface has checksuming enabled.
If the Bailey interface LEDs are not sequencing but the server indicates good
communication status (DEVICE PRI_STATUS or SEC_STATUS is zero).
1.) Verify the COM port associated with the DEVICE is not a modem port.
2.) Verify the pin outs on the serial cable or Bailey interface termination
dipshunt settings do not have the TX and RX lines pinned together.
10.5 Not All Blocks Are Receiving Data
1.) Verify the Bailey block addressed by the OPC90 Server block exists
and their types match.
2.) Verify “BLOCK ADDRESS ALREADY USED BY ANOTHER BLOCK” is
not posted in the MESSAGE attribute in any of the OPC90 Server
blocks not receiving data. If such a message is found, you have two or
more OPC90 Server blocks pointing to the same address within Bailey.
Eliminate the duplication.
3.) Verify “EXCEEDED OPC90 Server POINT LICENSE” is not posted in
the MESSAGE attribute in any of the OPC90 Server blocks not
receiving data. If such a message is found, you have exceeded the lite
version block capacity. Purchase the non-lite version.
5.) Make sure none of the Bailey controllers have addresses less than
two.
6.) Indices or memory capacity of the Bailey interface has been exceeded.
It is unlikely that you will encounter this error unless your application
has a very large number of OPC90 Server blocks and the Bailey
The RoviSys Company Version 7.0 Page 138

Table of Contents