Bailey Infi90 Interface to the pi system
Download 0.78 Mb. View original pdf
|
- Navigate this page:
- PI Configuration Problems
- Bailey Infi90 Interface to the PI System
| Bad Input and then no more events, the problem is most likely caused by an upset in the Bailey loop communication. For older versions of the Bailey loop communication module, the module does not reestablish the exception report routes after an upset, especially for routes across a network bridge. The CIU module has to reestablish the point in order for the PCU to resume sending exception report. The user can force the CIU tore- establish the point either by restarting the interface or by changing one of the nonessential attributes (i.e., typical value) on the problematic PI point. PI Configuration Problems If a PI point for the Infi90 Interface is not configured correctly, the CIU module will not establish the point and the interface will write the reason for the failure to the log file. The PI point's snapshot value will remain at the same value and timestamp as before the interface startup. Typical errors are Block already established as another point The user is trying to read the same attribute for the same Bailey block with more than one PI point. The easiest way to find the other PI points reading the same Bailey block is through the PICONFIG utility. Setup a PICONFIG file to look for all tags with the same Location, Location, Location 3, Location, and PointSource attributes Number out of range Most likely, one of the address parameters is out of legal range. For example, the module number cannot be less than 2 for all point type except the module status points. Bailey Infi90 Interface to the PI System 67 Monitor mode conflict This is primarily for point type 19, RMSC block. The CIU cannot be in Monitor Mode when the user wants to read RMSC block. The CIU monitor mode can be turned off only with the Talk utility through the diagnostic port of the CIU. Unsupported N point type The specified point type (location 5) is not supported by the interface. Occasionally, a configuration error may prevent a point from being established on the CIU. For example, if an input block is configured in a Bailey PCU to read from the CIU at an index number, this index number is then reserved for output in the CIU. The interface cannot establish any input point on that index. Accordingly, the interface reports this index when the CIU replies "index already established by another PCU". Furthermore, the interface marks this index number as unusable so that future addition of a point will not have the same problem. The user can then search all Bailey PCUs for an input block reading that CIU index number. The appropriate output point should then be created on the PI Server to send an output to the PCU. |