Specifications

MBX Bridge Help
Cyberlogic Technologies Inc. - 17 -
Source
Device Slave Path Filter
Destination
Device Network Type Routing Timeout
0
1
*.*.0.*.*
1
Ethernet
IP = 84.0.21.MB4
DI = MB5
5000
0
1
*.*.1.*.*
1
Ethernet
IP = 205.167.7.MB4
DI = MB5
5000
0
1
*.*.2.0.*
1
Ethernet
IP = 10.0.0.10
DI = MB5
5000
0
1
*.*.2.1.*
1
Ethernet
IP = 10.0.0.15
DI = MB5
5000
1
1-64
*.*.*.*
0
Modbus Plus
DI.0.0.0.0
5000
1
65-128
*.*.*.*
0
Modbus Plus
2.DI-64.0.0.0
5000
1
129-192
*.*.*.*
0
Modbus Plus
3.DI-128.0.0.0
5000
To see how this routing works, we will examine two typical cases.
Case 1 - Modbus Plus to Ethernet Routing
In this case, the 984 controller at node address 20 on the Modbus Plus network sends a
message to the Quantum controller at IP address 205.167.7.2 on the Ethernet network.
1. The originating node at address 20 sends a message with routing array 5.1.1.2.0.
The first two routing bytes (MB1, MB2) address the message to the PCI-85 in the
MBX Bridge system at node address 5, using slave path number 1.
2. The value of 1 in the third byte (MB3) causes the message to pass the Source Filter
for the second routing record.
3. The Bridge routes the message to its destination. The routing record specifies that
the message is to be sent to Ethernet MBX Device 1. The fourth Modbus Plus routing
byte (MB4) sets the value of 2 for the last byte in the destination IP address and the
fifth Modbus Plus routing byte (MB5) sets 0 as the destination index byte value. This
results in a routing of IP address 204.167.7.2 with destination index 0.
4. The message is delivered to its destination. It is processed and the reply is sent back
to the MBX Bridge, which passes it over to the original node at Modbus Plus address
20.
Note