Skip to Content

SiePortal

The integrated platform for your product selection, buying and support workflow - bringing together Industry Mall and Online Support.

SiePortalDeutsch

Search

Home
Support Support
{{(apiData.Support | filter:{'rank':1}:true)[0].title}} Support
- Menu temporary not available
- Menu temporary not available
- Menue temporary not available
- {{item.title}}

Products & Services
- Menu temporary not available
- Menue temporary not available
- {{item.title}}
Support Support
{{(apiData.Support | filter:{'rank':1}:true)[0].title}} Support
- Menu temporary not available
- Menue temporary not available
- {{item.title}}
MySiePortal MySiePortal
{{(apiData.MySiePortal | filter:{'rank':1}:true)[0].title}} MySiePortal
- Menu temporary not available
- Menue temporary not available
- {{item.title}}
Cart ({{apiData.CartCount}})

Navigation

Open communication with the 315 2 PN/DP

Created by: ashvir at: 6/25/2009 9:18 AM (24 Replies)

Rating (1)

Thanks 0

Result pages:: |; 1 | 2 | 3; |

25 Entries

Entries per page: 10 | 20 | all

6/25/2009 9:18 AM	Rate (0)
ashvir Posts: 28 Rating: (0)	Hi All I have achieved Modbus communication from my third party device and the PLC I have used the Modbus open communication software. I have also achieved open communication to a third party device and the PLC. The problem is I can’t get both comms running at the same time. They only work individually. How do I get this to work together.
ashvir Posts: 28 Rating: (0)
Suggestion To thank Quote Answer

6/25/2009 9:26 AM	Rate (0)
Wüstenräuber Gold Expert Joined: 10/3/2008 Last visit: 8/28/2024 Posts: 961 Rating: (124)	Hi ashvir, sorry, I'm afraid I don't understand your problem. Do you want to establish a connection between your PLC and a third party device via ModbusTCP and additionally an open connection between this partners without ModbusTCP? What is the problem exactly? Do you get errorcodes on modbus block? Wüstenräuber

Suggestion To thank Quote Answer

6/25/2009 3:51 PM	Rate (0)
ashvir Posts: 28 Rating: (0)	I would like to establish more than one Modbus connection. Eg I have two third party deviceshaving two different ip addresses and I need to establish comms with both. For now I can only establish comms with one device at a time.
ashvir Posts: 28 Rating: (0)
Suggestion To thank Quote Answer

6/25/2009 3:56 PM	Rate (0)
ashvir Posts: 28 Rating: (0)	Beside establishing more than one modbus connection I would also like to establish more than oneconection to a normal third party device. I have achived this using the Fb 63 FB64 FB65 blocks but for one device only. I cant seem to change the communication ID for the Third party device. This ID remains 1. I can change the comms ID for the PLC but this doesnt do anything.
ashvir Posts: 28 Rating: (0)
Suggestion To thank Quote Answer

6/25/2009 4:13 PM	Rate (0)
Wüstenräuber Gold Expert 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

Suggestion To thank Quote Answer

6/25/2009 4:27 PM	Rate (0)
ashvir Posts: 28 Rating: (0)	I did try that and I am using the wizard as well, but failed, In the example code Fb 102 is used and DB 102.I tried creating anotherinstance db for FB 102 eg Db 103,and when I called Fb 102 in an FC withDb 103 the comms fails. So if I am not able to create another instance Db successfully I wont be able to get comms to another Modbus device I figured. Also using the wizard onlycommunication Id 1 is working as soon as I chnage this to another ID comms fails.
ashvir Posts: 28 Rating: (0)
Suggestion To thank Quote Answer

6/25/2009 8:23 PM	Rate (0)
Wüstenräuber Gold Expert Joined: 10/3/2008 Last visit: 8/28/2024 Posts: 961 Rating: (124)	Hi, you have to add a second connection in the connection DB (e.g. ID = 2) with the ModbusTCP Wizard. After that you have to call the FB102 in OB100 and in OB1 with instance DB 102 (for ID = 1) and with instance DB 103. Which error occurs (errorcode on parameter STATUS_MODBUS and STATUS_CONN)? Attach your project and I will check it. Wüstenräuber

Suggestion To thank Quote Answer

6/26/2009 8:53 AM	Rate (0)
ashvir 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. Attachment modbus.zip (853 Downloads)
ashvir Posts: 28 Rating: (0)
Suggestion To thank Quote Answer

6/26/2009 9:26 AM	Rate (0)
Wüstenräuber Gold Expert Joined: 10/3/2008 Last visit: 8/28/2024 Posts: 961 Rating: (124)	Hi, I had a look at your program and found the problem. But firstly: You needn'tset the initialization parameter in OB1. E.g. the paramters ID and DB_PARAM are init parameters and they are used in OB100 only. The best is to delete these parameteres in OB1, because it's misleading. The problem are the same addresses for the communication partners. You parameterize the ip address 10.0.1.11 and port number 502 for both connections. This is not possible because the connection node is not unique. Either you have to change the ip address or you have to change the port number to communicate via 2 connections. Wüstenräuber

Suggestion To thank Quote Answer

6/26/2009 10:11 AM	Rate (0)
ashvir 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. Attachment modbus.zip (824 Downloads)
ashvir Posts: 28 Rating: (0)
Suggestion To thank Quote Answer

|

Share this page:

Share this page on...

Related topics by keywords:

ModbusTCP

Follow us on