6/25/2009 4:13 PM | |
Joined: 10/3/2008 Last visit: 8/28/2024 Posts: 961 Rating: (124) |
Hi, for a second modbus connection, you have to create a second connection in the connection DB, e.g. ID 2. The best way to do this is with the ModbusTCP Wizard (http://support.automation.siemens.com/WW/view/en/31535566). After that you have to insert a second modbus instance (with a new instance DB for the modbus block) with the second ID. Wüstenräuber |
6/26/2009 8:53 AM | |
Posts: 28 Rating: (0) |
Thanks for the help thus far. I have attached the program. I am using instance DB 102 in OB 1 which has DB5 as the modbus parameters that was configured with the wizard and this has a connection id of 2. In OB 1 InstanceDB 103 is then used with ID 1 and a call of Modbus DB 2. I am calling the instance db's in OB 100 as well.
Attachmentmodbus.zip (809 Downloads) |
6/26/2009 10:11 AM | |
Posts: 28 Rating: (0) |
Dear Wuestenraeuber I Have made the changes you sugested but I still dont achieve comms to both devices, is there maybe another problem. Attachmentmodbus.zip (782 Downloads) |
6/26/2009 10:13 AM | |
Posts: 28 Rating: (0) |
Hi I have made the changes you suggested but I still dont achieve comms to both devices, Is there maybe another problemthat I have. Attachmentmodbus.zip (446 Downloads) |
6/26/2009 10:25 AM | |
Posts: 28 Rating: (0) |
Yes I did, |
6/26/2009 12:39 PM | |
Joined: 10/3/2008 Last visit: 8/28/2024 Posts: 961 Rating: (124)
|
I think you have the english syntax: JC sec Try this and if it doesn't work then I will send you the OB100. Wüstenräuber AttachmentSerial_3.zip (515 Downloads) |
Last edited by: Wuestenraeuber at: 6/26/2009 12:43 PMadded the changed project Last edited by: Wuestenraeuber at: 6/26/2009 12:40 PMNot BEC but JC |
|
Follow us on