Schneider Electric none Modbus Address Map, Table Location Modbus Address Five±Byte Routing Path

3.4.8Modbus Address Map

The B￿85 maintains four internal ￿odbus Address ￿ap tables for routing the ￿odbus messages received at its four ￿odbus ports. Each port has a table that can hold up to 64 entries that you specify during configuration.

Vthe location in the table at which you want to place the entry

Va one-byte ￿odbus address in the range 1 ... 255 decimal

Va five-byte routing path.

Each table entry specifies how you will want a ￿odbus address received at the ￿odbus port to be converted into a five-byte routing path to the destination device in your application. Routing can be made to a ￿odbus Plus node on the local network or on a remote network. ￿essages can also be routed to a device on another port of the B￿85.

When a ￿odbus message is originated from a device at one of its ￿odbus ports, the B￿85 searches the ￿odbus Address ￿ap table for that port to find a match between the message's ￿odbus address and a ￿odbus address stored in the table. The actions taken if a match is found, or if a match is not found, are described below and on the following pages.

If a Match is Found

If a match is found, the five bytes of mapped routing from the table entry will be applied to the message, and it will be sent out using that routing. Here are five examples of how the ￿odbus Address ￿ap table can be used to develop routing paths for ￿odbus messages:

Table Location	Modbus Address	Five±Byte Routing Path
01	47	8	0	0	0	0
02	182	20		14	0	0	0
03	27	20		22	5	0	0
04	33	0	3	0	0	0
05	125	0	4	99		0	0

VEntry 01 is an example of routing to node 8 on the local ￿odbus Plus network. If the ￿odbus message contains the destination address 47, a match is found in the table. The B￿85 will apply the routing path 8, 0, 0, 0, 0 to the message. The message is acted upon by the application program in the device at node address 8.

36 Configuring the Modbus Models 31007492