TCP_IP_ADDR
Original instructions
About us
Function Description
The TCP_IP_ADDR block enables the input of TCP/IP addresses for the READ_REG, CREAD_REG, WRITE_REG, and CWRITE_REG blocks. The address is transferred in the form of a data structure.
EN and ENO can be projected as additional parameters.
NOTE: When programming the TCP_IP_ADDR function, you must be familiar with your network’s routing procedures.
Symbol
Block representation:
Parameter Description
Description of parameters:
Parameter
Data Type
Meaning
Map_Idx
BYTE
Map-Index
MBP on Ethernet Transporter (MET) mapping index
Slot_ID
BYTE
slot ID
slot of the NOE module
Ip_B4
BYTE
byte 4 (MSB) of the 32-bit destination IP address
Ip_B3
BYTE
byte 3 of the 32-bit destination IP address
Ip_B2
BYTE
byte 2 of the 32-bit destination IP address
Ip_B1
BYTE
byte 1 (LSB) of the 32-bit destination IP address
AddrFld
WordArr5
data structure used to transfer the TCP/IP address
Elementary Description for WordArr5
Elementary description for WordArr5:
Element
Data Type
Meaning
WordArr5[1]
WORD
high value byte: Slot of the NOE module
low value byte: MBP on Ethernet Transporter (MET) mapping index
WordArr5[2]
WORD
byte 4 (MSB) of the 32-bit destination IP address
WordArr5[3]
WORD
byte 3 of the 32-bit destination IP address
WordArr5[4]
WORD
byte 2 of the 32-bit destination IP address
WordArr5[5]
WORD
byte 1 (LSB) of the 32-bit destination IP address
Map_Idx
The MBP on Ethernet Transporter (MET) mapping index is given at the Map_Idx input. That is, if MET is 6, the value appears as follows:
Slot_ID
If an NOE in the rack of a Quantum controller is addressed as destination node, the value at the Slot_ID input represents the physical NOE slot. That is, if the NOE is plugged in at Slot 7 of the rack, the value appears as follows:
NOTE: When using an integrated Ethernet CPU module such as the 140 CPU 651 x0, the slot ID must be 254 (FE hex) regardless of the CPU slot.
AddrFld
If an NOE in the rack of a Quantum controller is addressed as a destination node, the value in the High value byte represents the physical slot of the NOE and the Low value byte represents the MBP on Ethernet Transporter (MET) mapping index. That is, if the NOE is inserted in slot 7 of the rack and the MET mapping index is 6, the first element of the data structure looks as follows:
High value byte Slots 1 ... 16
Low value byte MBP on Ethernet Transporter (MET) mapping index