PROTOCOL COMMUNICATION
PT10789220
pag. 3/22
3. User Communication PLC - NEMO 96HD
On the application layer (PLC), the telegrams from and to the Profibus module of NEMO 96HD are shaped from 32 bytes
of the output- and input periphery. These telegrams consist fundamentally of a header, which uses 4 bytes and 28 bytes
user data for measured values.
Output Telegrams PLC - NEMO 96HD
Periphery – Output Address Meaning / contents Value
Header byte 0,
Base address output periphery - offset =
0
Telegram - or block number of the segment to
be requested
1..MAX decimal
Header byte 1
Base address output periphery - offset =
1
Reserved, not used at this time
Header byte 2
Base address output periphery - offset =
2
Bits for controlling the internal communication 8 Bit binary
Header byte 3
Base address output periphery - offset =
3
Reserved, not used at this time
Data byte 0..27
Base address output periphery - offset =
4..31
28 user data byte, not used at this time
Input Telegrams NEMO 96HD - PLC
Periphery – Input Address Meaning / contents Value
Header byte 0
Base address input periphery - offset = 0
Returned Telegram- / Block-number of the
requested block
1..MAX decimal
Header byte 1
Base address input periphery - offset = 1
Reserved, not used at this time
Header byte 2
Base address input periphery - offset = 2
Reserved, not used at this time
Header byte 3
Base address input periphery - offset = 3
Status messages 8 Bit binary
Data byte 0..27
Base address input periphery - offset =
4..31
28 bytes user data for measured values WORD, DWORD
For the transfer of all measured values form NEMO 96HD to the PLC, seven (7) telegrams are necessary.
