PLC-5 A.I. Series Message Instruction example

A message is generated in a PLC-5 A.I. Series by programming a Message Instruction. Refer to a PLC-5 programming manual for help on how this instruction is programmed. The Message instruction requires several fields to be programmed properly for it to function properly. These fields are as follows:
Communication Command : PLC-5 Typed Write
PLC-5 Data Table Address : N7:10 Ignore if Timed-Out : 0 TO
Size in Elements : 1 To be Retired : 0 NR
Local/Remote : Local Awaiting Execution : 0 EW
Remote Station : N/A Continuous : 0 CO
Link ID : N/A Error : 0 ER
Remote Link Type : N/A Message Done : 1 DN
Local Node Address : 72 Message Transmitting : 0 ST
Destination D.T. Address : N7:10 Message Enabled : 0 EN
Port Number : 1A
In this example, a message instruction is configured to send one word, N7:10, to a KT card configured by RSLinx Classic as station number 72. The PLC-5 is a 5/20 and the message is going to be sent out channel 1A, which is configured as a DH+ port. The Message instruction requires several fields to be programmed for it to properly function. These fields are as follows:
  1. The Communication Command field must be set to PLC-5 Typed Write (the PLC-5 is writing data to another station).
  2. The PLC-5 Data Table Address must be set to the starting address of where you want the data to be read from.
  3. The amount of data to be transferred must be entered into the field called Size In Elements. In this example this is 1.
  4. The Local/Remote addressing must match the addressing actually used on your DH+ link.
  5. The Local Node Address must be the station of the RSLinx Classic driver/device that the message is going to be sent to.
  6. The Destination Data Table Address is variable, and this is where the complexity of this method comes into being.
  7. The Port Number is set to the port of the PLC-5 that the message is sent out. In this example this is 1A. This setting only applies to the New Platform PLC-5 when using an MG data type as the control.
Provide Feedback
Have questions or feedback about this documentation? Please submit your feedback here.
Normal