LinMot E1400-GP Series Manual page 30

Request: Get Next UPID
Byte Value Description
Offset
0 01h Fix ID Telegram start
1 11h Destination node ID
2 05h Telegram length
3 02h Fix ID start data
4 0Bh Message Sub ID (Get Next UPID)
5 05h Message Main ID (Parameter Configuration)
6 00h Not used, don't have to be transmitted
7 00h Not used, don't have to be transmitted
8 04h Fix ID telegram end
Configuration Response: Get Next UPID
Byte Value Description
Offset
0 01h Fix ID Telegram start
1 11h Destination node ID
2 0Ah Telegram length
3 02h Fix ID start data
4 5Bh Message Sub ID (Cfg Read ROM Value)
5 00h Message Main ID (Response)
6 00h Communication state
7 A2h Found UPID Low Byte
8 13h Found UPID High Byte
9 09h Address Usage low byte of found UPID
10 00h Address Usage high byte of found UPID
11 00h Parameter Type low byte of found UPID
12 00h Parameter Type high byte of found UPID
13 04h Fix ID telegram end
The following example shows the principle of reading the UPID List of a SW instance, if generating a
configuration out of this list all UPIDs with the 'ROM write' address usage bit set have to be read out with the
get ROM value command.
Tx: 01 11 05 02 0A 05 00 20 04
Rx: 01 11 0A 02 5A 00 00 00 20 00 00 00 00 04
Tx: 01 11 05 02 0B 05 00 20 04
Rx: 01 11 0A 02 5B 00 00 08 20 0D 00 0A 00 04 ; UPID 2008h,
...
Tx: 01 11 05 02 0B 05 00 20 04
Rx: 01 11 0A 02 5B 00 00 36 21 01 10 03 00 04
Page 30 of 62
; start Get UPID List Intf SW layer
AU: 000Dh Type: 000Ah
; UPID 2136h,
AU: 1001h Type: 0003h
NTI AG / LinMot