Hello, I try to communicate my PI2 with OTB SCHNEIDER TCP / IP Modbus card.
OTB config: 1st module: OTB 1E0DM9LP - V2.xx 2nd module: OTB TM2AMI4LT - V2.xx
Config CoDeSys: Modbus_TCP_slave_1 IP: 192.168.1.11 Unit_ID: 127 reading code 23: read address: 2000 Writing address: 2100
Modbus_TCP_slave_2 IP: 192.168.1.11 Unit_ID: 1 code reading 3: read address: 2001
When I want to write an output map (2100) no problem The problem is that I can not at all to read the analog channel 2001
In Advantys, the first card is on UNIT_ID: 127 and the next is on UNIT_ID: 1
Does someone has already tested CoDeSys 3.5 SP6 Patch 1 with material SCHNEIDER OTB? What way can we configure OTB cards SCHNEIDER CoDeSys ??????
Thank you for your help Ludo
Hi, I finally found the solution. As the cards do not have the same ID_unit , we must separate the reading frames See attached image
Log in to post a comment.
Hello,
I try to communicate my PI2 with OTB SCHNEIDER TCP / IP Modbus card.
OTB config:
1st module: OTB 1E0DM9LP - V2.xx
2nd module: OTB TM2AMI4LT - V2.xx
Config CoDeSys:
Modbus_TCP_slave_1
IP: 192.168.1.11
Unit_ID: 127
reading code 23:
read address: 2000
Writing address: 2100
Modbus_TCP_slave_2
IP: 192.168.1.11
Unit_ID: 1
code reading 3:
read address: 2001
When I want to write an output map (2100) no problem
The problem is that I can not at all to read the analog channel 2001
In Advantys,
the first card is on UNIT_ID: 127 and the next is on UNIT_ID: 1
Does someone has already tested CoDeSys 3.5 SP6 Patch 1 with material SCHNEIDER OTB?
What way can we configure OTB cards SCHNEIDER CoDeSys ??????
Thank you for your help
Ludo
Hi,
I finally found the solution.
As the cards do not have the same ID_unit , we must separate the reading frames
See attached image