Pepperl+Fuchs IC-KP-B17-AIDA1, Руководство пользователя

Страница: 81 / 128

IC-KP-B17-AIDA1
Commands
2014-
02
81
Write read only code IPC11 and IDC-..-1K
"Read-after-write" operating mode is not used.
Tags IPC11 can be programmed to behave like the IPC02 read only tag. To do this, use the
commands SX and EX . The code is read when tag type '02' or '11' is set with the commands SF
and EF .
Tags IDC-...- 1K can be programmed to behave like the ICC read only tag. This programming
occupies the first 8 bytes in the tag and occurs when the tag type '50' is set with the commands
SX or EX .
This code is read when tag type '52' is set with the commands SF or EF . If you use the
command SF or EF when tag type '50' is selected, the 4-byte read only code of the tag is
issued.
single write fixcode (SX)
Command:
Response:
The length of the read only code that is output depends on the tag type. See table "Supported
Tag Types" on page 60.
Byte Contents Bit no.
7
6 5 4 3 2 1 0
Byte 0
1)
Telegram length, high byte 0 0 0 0 0 0 0 0
Byte 1
1)
Telegram length, low byte 0 0 0 0 1 0 1
1
2)
Byte 2 Command code (1Fh) 0 0 0 1 1 1 1 1
Byte 3 FixLen/Channel/Toggle bit <FixLen> <Channel> <T>
Byte 4 FixType <FixType> (high byte)
Byte 5 FixType <FixType> (low byte)
Byte 6 Data 00h ... FFh <Data>
Byte 7 Data 00h ... FFh <Data>
... Data 00h ... FFh <Data>
Byte N
3)
Data 00h ... FFh <Data>
1)
This byte is only used with the TCP/IP and MODBUS TCP/IP protocol.
2) The telegram length depends on the read only code length of the tag.
3)
N = <FixLen> + 5; Ethernet/IP: N = <FixLen> + 3
Byte Contents Bit no.
7
6 5 4 3 2 1 0
Byte 0
1)
Telegram length, high byte 0 0 0 0 0 0 0 0
Byte 1
1)
Telegram length, low byte 0 0 0 0 0 1 1 0
Byte 2 Command code (1Fh) 0 0 0 1 1 1 1 1
Byte 3 FixLen/Channel/Toggle bit 0 1 0 1 <Channel> <T>
Byte 4 Status <Status>
Byte 5 Reply counter <ReplyCounter>
1)
This byte is only used with the TCP/IP and MODBUS TCP/IP protocol.