6. Configuring the Gateway
8)Configuring the DeviceNet master PLC outputs: In RsNetWorx, establish a new correspondence between the data transmitted to the gateway and the PLC outputs, according to the requirements of your application (see chapter 4.2.7 Configuring Outputs Intended for the Gateway, page 30). The various possibilities offered by RsNetWorx for establishing a correspondence between the data transmitted to a DeviceNet subscriber and the PLC outputs will not be covered here. Please see the documentation for this software application to find out more about this step in setting up a DeviceNet master PLC.
In this guide, we will be using the “AutoMap” command to establish a “raw” correspondence with all of the data transmitted to the LUFP9 gateway. We then get the correspondence shown below, derived from the one used with the gateway’s default configuration. The changes in relation to the default configuration are shown by a
Service | PLC output | Description | ||
Bit 0......................Bit 7 | Bit 8 ...................Bit 15 | |||
Managing the downstream Modbus | O:1.1 |
| DeviceNet master command word | |
network |
| (MSB Æ 16#xx••) | (LSB Æ 16#••xx) | |
|
| |||
| O:1.2 | Value of the motor starter c command register | ||
Periodic communications | O:1.3 | Value of the motor starter d command register | ||
O:1.4 | Value of the motor starter e command register | |||
— | O:1.5 |
| Free memory location | |
Controlling | O:1.6 |
| Value of the motor starter g command register | |
TeSys U motor starters | O:1.7 | Value of the motor starter h command register | ||
| O:1.8 | Value of the motor starter i command register | ||
| O:1.9 | Value of the motor starter j command register | ||
Aperiodic communications | O:1.10 |
| Slave no. | Function no. (16#03) |
|
| Address of the parameter to be read | ||
— | O:1.11 |
| ||
| (MSB Æ 16#xx••) | (LSB Æ 16#••xx) | ||
Reading the value of a |
|
| ||
|
| Number of parameters to be read | ||
motor starter parameter (QUERY) | O:1.12 |
| ||
| (MSB Æ 16#00••) | (LSB Æ 16#••01) | ||
|
|
| ||
Aperiodic communications | O:1.13 |
| Slave no. | Function no. (16#06) |
|
| Address of the parameter to be written | ||
— | O:1.14 |
| ||
| (MSB Æ 16#xx••) | (LSB Æ 16#••xx) | ||
Writing the value of a |
|
| ||
|
| Value of the parameter to be written | ||
motor starter parameter (QUERY) | O:1.15 |
| ||
| (MSB Æ 16#xx••) | (LSB Æ 16#••xx) | ||
|
|
| ||
Aperiodic communications | O:1.16 |
| Read parameter | Write parameter |
(“Trigger bytes” for the queries) |
| query counter | query counter | |
|
| |||
Periodic communications | O:1.17 |
| Value of the “Command Register” | |
Monitoring of TeSys U motor starter f | O:1.18 |
| Value of the “2nd Command Register” | |
9)Transferring the DeviceNet scanner configuration: Following the changes made to the list of DeviceNet scanner exchanges, it needs to be transferred to the DeviceNet scanner. Please see chapter 4.2.9 Transferring the DeviceNet Scanner Configuration, page 32.
57
