ProLinx 6202-WA-DFNT-DFCM3, Руководство пользователя

Страница: 28 / 190

6202-WA-DFNT-DFCM3 ♦ ProLinx Gateway Configure the Module
Wireless EtherNet/IP to DF1 Master/Slave-3 ports
Page 28 of 190 ProSoft Technology, Inc.
February 2, 2009
ƒ
Consumer Set DB to 0 On RF Error
ƒ
Consumer Set DB to 1 On RF Error
DB Reg
The DB Register field defines the starting database register in the module where
data sourced (produced data) or placed (consumed data) is determined by the
value entered in the DB Reg column. This parameter can have a value of 0 to
3999. The validity of the entry is dependent on the number of registers (Reg
Count) to be produced or consumed. The sum of the two values cannot exceed
4000, as this would be outside the range of the module's database.
Reg Count
Number of database registers to transfer/accept in message.
Swap Code
0, 1, 2 or 3
The Swap Code field sets byte and word swapping of data produced or
consumed. Swapping of words and/or bytes in the message may be required for
different protocol and operating systems as their representation of multi-byte
values may not be the same as that of the DFNT protocol.
Swap Code Description
0 None - No Change is made in the byte ordering (1234 = 1234)
1 Words - The words are swapped (1234=3412)
2 Words & Bytes - The words are swapped then the bytes in each word are
swapped (1234=4321)
3 Bytes - The bytes in each word are swapped (1234=2143)
P/C Time
The P/C Time field defines the number of milliseconds between productions of
the exchange data and for consumed exchanges. This value defines the number
of milliseconds to wait for a produced exchanged before a timeout condition is
present.
ƒ
For a producer exchange it defines the number of milliseconds between
consecutive producer exchanges.
ƒ
For a consumer exchange it defines the number of milliseconds to wait for a
produced message before a timeout error is set. It is suggested to use a
value at least four times greater than the value used in the producer
exchange.
For consumed messages, set this value to approximately 4 times the produced
time of the exchange on the other device. This will prevent the exchange from
constantly timing out on a busy network. If this parameter is set to zero, the
message will not be produced.