I need to configure my Portserver TS 16 to support multiple modbus ASCII (Telvent) network masters. There will be multiple serial slaves, also modbus ASCII devices.
Each master needs to be able to poll each slave.
I don’t understand how the tables work. Do I need a table for each network master to a serial port mapping?
I am just not sure exactly how to do this.
You only need to set up one table. Use the IA wizard under Applications/Industrial Automation and set up a network master (source) speaking Modbus ASCII, and then set up each of the slaves on the appropriate serial ports. There is information here in the Modbus Bridging application guide: http://ftp1.digi.com/support/documentation/90000638_a.pdf
Don’t worry that it says Digi One IAP on it–the IA engine in the Portserver TS 16 has the exact same Modbus support.
So I would just create three network masters, one for each of my three network masters, using different TCP ports for each master.
Then I would configure the destination table to map the protocol address to the proper serial slave port.
Since all of the examples use DIGI one devices it is difficult for me to ensure that I have the proper understanding how to implement this on a multiport device.
You can create three network masters but really you only need to create one. The PortServer will balance the incoming requests from the three masters the same way regardless of whether they are coming in on three different ports or all the same port.
And yes, then you create a destination for each individual serial port.
Do we even have to configure a Network Master? The manuals states The network connection doesn’t require configuration unless the master requires Com port redirection.
Also can you setup multiple non-contiguous modbus addresses going to the same serial interface in the destination table? This is my ia table. It looks good I’m just not sure it will work.
set ia table=1 name=Table1
set ia table=1 addroute=1 active=on protocol=modbusascii protaddr=14
set ia table=1 route=1 type=serial port=1
set ia table=1 addroute=2 active=on protocol=modbusascii protaddr=17
set ia table=1 route=2 type=serial port=2
set ia table=1 addroute=3 active=on protocol=modbusascii protaddr=179
set ia table=1 route=3 type=serial port=3
set ia table=1 addroute=4 active=on protocol=modbusascii protaddr=15
set ia table=1 route=4 type=serial port=4
set ia table=1 addroute=5 active=on protocol=modbusascii protaddr=192-193
set ia table=1 route=5 type=serial port=5
set ia table=1 addroute=6 active=on protocol=modbusascii protaddr=202
set ia table=1 route=6 type=serial port=6
set ia table=1 addroute=7 active=on protocol=modbusascii protaddr=73
set ia table=1 route=7 type=serial port=6
set ia table=1 addroute=8 active=on protocol=modbusascii protaddr=75
set ia table=1 route=8 type=serial port=7
set ia table=1 addroute=9 active=on protocol=modbusascii protaddr=20
set ia table=1 route=9 type=serial port=8
set ia table=1 addroute=10 active=on protocol=modbusascii protaddr=146-147
set ia table=1 route=10 type=serial port=8
set ia table=1 addroute=11 active=on protocol=modbusascii protaddr=200
set ia table=1 route=11 type=serial port=9
Actually yes, you need to set up a network master so that the Portserver knows what port to listen on for what protocol. The sentences “The network connection usually does not require configuration. The only exception is if the master requires COM port redirection.” are unclear but I think they are referring to the the network side of the port profile settings.
As for your destination table, it looks good. I am pretty sure we can’t assign non-contiguous protocol ids to one serial port, though.