Bailey Infi90 Interface to the pi system
Download 0.78 Mb. View original pdf
|
| 0 Configure 1 Failed 2 Error 3 Execute The block number (Location) should be 0 for this point type. RCM Read (N90 point type An RCM (function code 62), device driver (function code 123), or multi-state device driver block (function code 129) can be read in several ways. It is possible to save the output value, the alarm state, the set permissive bit, or an integer containing all of the bits in the first two status bytes of an RCM report. Use point type 15 to save all of the bits into a PI Server integer point. The first byte of the status is the high-order byte and the second byte is the low-order byte in the resulting integer value. To readjust the output value, set Location to 24. The PI point should be defined as type Digital or Int. The block output (bit 0 of status byte 1) is saved by the Interface. The value is set to BAD INPUT if the quality is bad. When communicating with the CIU, the Interface sets this point type to Bailey point type For the alarm state or the RCM set permissive bit, set Location to 25 or 26, respectively. These point types are also converted to point type 15 when the Interface communicates with the CIU. These pseudo-point types are used so that it is possible to have more than one PI tag fora single CIU index. The alarm state and set permissive bit points can be either PI Digital or Int. The interface supports user-defined bitmap processing on RCM and device driver blocks. For the user bitmap points, the value of Location is 27XXXXX where XXXXX is the bitmap ranging from 1 to 32767. The Interface masks the Net90/Infi90 status word with the user bitmap and puts the result into the PI point. See Appendix C for the meaning of the Bailey status word and example of the bit mask. Note that the maximum value of the mask is 32767, which excludes the quality bit of the N status word, because with the quality bit set, the PI value is automatically set to Download 0.78 Mb. Share with your friends:
|