Wonderware DASABTCP communicating with Digi One IAP to two SLC 5/03 (one SLC 5/03 on each serial port)
So far there is no problem to use Wonderware DASABTCP to pool date from any SLC 5/03 on any of Digi One IAP serial port as long as there is a route in the destination table to direct protocol address “0” to serial port. From what port Wonderware DASABTCP pools data depends on number of serial port listed as first with protocol address “0”. I do not see any way to set destination table to force Wonderware DASABTCP to pool data from both PLC at the same time.
The only parameter to set on Wonderware DASABTCP side is IP# number
There is a way to assign an alternate IP# to Digi One IAP. That could help but it seems that there is no way to assign those IP# to any particular port.
Well, you can set an “alternate IP” so the DOIAP appears as 2 different IP addresses - there is even an application note on the support site where we use this to fool RSLinx into talking to 2 ports. So if the DOIAP has the two IP 192.168.1.23 and 192.168.1.24 and these are in “station index” 2 and 3, then DOIAP treats these as for destination address 2 and 3 in the routing table.
The problem is the DOIAP today doesn’t have the ability to detect or adjust routing based on which IP is used. So even with 2 incoming IP, since your driver still calls each destination #0 the distinction is lost.
The only solution I can see would be to create 2 message sources on 2 different TCP ports. But I am not sure that the Wonderware driver supports this. Some allow changing the TCP port, but the change is Global & thus it cannot talk on 2 ports at once.
So you’d have (partial config):
set ia master=1 protocol=abethernet ipport=2222 table=1
set ia table=1 route=1 protaddr=0-1 port=1
set ia table=1 route=1 protaddr=2 port=2
set ia master=2 protocol=abethernet ipport=2223 table=2
set ia table=2 route=1 protaddr=0-2 port=2
Thus any AB/Enet (or CSP) request coming in on TCP port 2222 goes to port 1 unless DST=2, then it goes to 2nd port. This allows WW to call this PLC 0 and RSLinx can still select either port. Any AB/Enet (or CSP) request coming in on TCP port 2223 (not 2222) goes to 2nd port.