Specifications

MBX Bridge Help

Cyberlogic Technologies Inc. - 12 -

Slave Path Field Entry

Slave Paths Used

SP2

1-4

SP 1, SP2, SP3, SP4

Any slave path

This table shows examples of some Slave Path field values and the slave paths they

specify for use.

Slave Path numbers for the Ethernet source devices are based on the destination index

numbers sent with each message. In the default configuration, a Slave Path number is

directly mapped to the destination index value. For more information refer to the

Ethernet MBX Driver help.

Slave Path numbers for the Serial MBX Slave source devices are based on the destination

address sent with each message. For more information refer to the Serial MBX Driver

help.

Source Filter

The Source Filter consists of one to five fields, and each field corresponds to a byte in

the routing array that is part of each received command message. The fields can each

contain a number, a number range or an asterisk (*). When a command message is

received that matches the Slave Path filter criteria, each byte in its routing array is

compared against the corresponding Source Filter field. If the filter field contains a

number, an exact match of a corresponding byte is required. For a number range, the

corresponding byte must fall within the selected range. An asterisk in a filter field

indicates that any value is acceptable.

Source Filter

Routing Addresses That Pass

2.1.0.0.0

2.1.*.0.0

2.1.0.0.0 to 2.1.255.0.0

2.1.0-63.0.0

2.1.0.0.0 to 2.1.63.0.0

2.1.*.*.*

2.1.0.0.0 to 2.1.255.255.255

*.*.*.*.*

Any routing address

This table shows examples of some Source Filter entries for a Modbus Plus source device.

Note

Ethernet and Modbus source devices use the same type of Source Filter expressions as

used for Modbus Plus. However, the received routing array contains different address

information.

In the case of Ethernet, you can filter on the four-byte IP address. For Modbus, there is

only one routing byte to filter, the destination node address.