PI Interface for Bailey Infi90 73 PI Configuration Problems If a PI point for the BaInfi90 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 system 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. Monitor mode conflict This is primarily for point type 19, RMSC block. The CIU cannot be in Monitor Mode when you want 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. You can 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.