User Manual

Data Sheet / User Manual RB-TW-2400
DataUserManual FCC_05.doc PHOENIX CONTACT
22/3
0
5.3 Operation
In order to operate the RC it needs a valid configuration. A default configuration is loaded at boot up,
nevertheless a unique node ID must be configured after every boot up. After the RC was configured it
is ready to be started by the user, this is done by setting the RC to normal operation mode. During
normal operation the RC is ready for application message exchange.
5.4 Configuration
Before the RC is functional it needs to be configured to suite the users needs. A default configuration
which is described in the next subsections is loaded at boot up. The default configuration does not
contain a node ID. The node ID always has to be assigned by the user.
Configuration is done with the help of a special command described in the next subsection.
Configuration Command
GET / SET Config Command
The GET and SET Config commands are used to transfer configuration data to and from the RC-
Module. The command structure is depictured in the following figure:
7
6
5
4
3
2
1
0
Command Byte
1 = ACK, 0 = NACK
0001: GET Config, 1001: SET Config
Length
x
x
x
x
x
x
x
x
Parameter Adr Hi
x
x
x
x
x
x
x
x
Parameter Adr Lo
x
x
x
x
x
x
x
x
Data (Optional) x x x x x x x x
The command byte is used to choose whether a parameter should be read or written.
In case of a read request, the response will have the ACK bit set when the parameter address was
valid. The response to a write request will have set the ACK bit only when a valid parameter address is
given and the length for the addressed parameter is correct.
The length byte is used to indicate the length of the parameter data. It is only used in a write-request or
in a read-response. In write-response and read-request it can be set any value.
A length value of ‘0’ indicates that the parameter length is 1 byte, but is transferred in the optional
data field. The maximum length for a configuration parameter is 64 bytes.