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

S7-1516-3PN/DP and TIA V13 Sp1, Modbus TCP Error

Created by: U_1c822d44-dd9d-4b17-9986-71d9030358c3 at: 10/26/2015 4:18 AM (7 Replies)

Rating (0)

Thanks 1

8 Entries

10/26/2015 4:18 AM	Rate (0)
U_1c822d44-dd9d-4... Posts: 1 Rating: (0)	Hi, Subject: Regarding Modbus TCP/IP Communication I'm using S7-1516-3PN/DP CPU and Siemens TIA Portal V13 Sp1 software for my application. My System is an intermediate among other systems. My system communication is through Modbus TCP with other / 3rd party system. I already made a Communication Setup, Using your sample program (Modbus Client and Server Configuration) . That helps me a lot. Now the Communication is estabilished between Server and Client. My requirement is to read 5000 Words (between 40001 to 49999) using Modbus Client (using same connection with server). Modbus Client, allows to fetch 125 Words per call. First 125 Words call are fetching, Remaining Call are getting Error. Regards, Vinoth R ------------------------------------------------------------------------------------------ Split from TOP Links for S7-1500.
U_1c822d44-dd9d-4... Posts: 1 Rating: (0)	Last edited by: Min_Moderator at: 10/26/2015 2:35:08 PM New subject after splitting
Suggestion To thank Quote Answer

10/26/2015 4:59 PM	Rate (0)
Kaulquappe Posts: 3093 Rating: (323)	Hello Vinoth, which error do you get? Regards, Kaulquappe
Kaulquappe Posts: 3093 Rating: (323)
Suggestion To thank Quote Answer

10/27/2015 1:39 AM	Rate (0)
vinothr2007 Posts: 3 Rating: (0)	Hi, Thank you for your swift reply. Error: 80A3 Regards, Vinoth
vinothr2007 Posts: 3 Rating: (0)
Suggestion To thank Quote Answer

10/27/2015 4:19 PM	Rate (0)
Kaulquappe Posts: 3093 Rating: (323)	Hello Vinoth, error 80A3 means that your try to establish a connection, which is already established or you try to terminate a connection, which is not established. TCON/TDISCON are called inside the Modbus block. For each connection ID only one call of MB_CLIENT can be active. I guess that you did not interlock the different calls properly. Regards, Kaulquappe
Kaulquappe Posts: 3093 Rating: (323)
Suggestion To thank Quote Answer

10/28/2015 7:21 AM	Rate (0)
vinothr2007 Posts: 3 Rating: (0)	Hi, Thank you for your great support. Yes you are right, same definition (Error: 80A3) also in TIA Portal Help Information. Please advise me how should i interlock for multiple call using MB Client with Single Connection ID. Please kindly provide if you have any sample program. Regards, Vinoth R
vinothr2007 Posts: 3 Rating: (0)	Last edited by: vinothr2007 at: 10/29/2015 3:11:08 AM
Suggestion To thank Quote Answer

10/30/2015 2:56 PM	Rate (0)
zenerz Regular Member Joined: 2/27/2014 Last visit: 2/10/2020 Posts: 3 Rating: (1)	vinothr2007 Hi, Thank you for your great support. Yes you are right, same definition (Error: 80A3) also in TIA Portal Help Information. Please advise me how should i interlock for multiple call using MB Client with Single Connection ID. Please kindly provide if you have any sample program. Regards, Vinoth R Hi, This is not a proper solution. With S7-1500 you will have a lot of open communication resources (have a look to your CPU1516 technical details for open communications over Ethernet) It is much better idea to keep connections in parallel (active connections) rather than using the same resource (same instance -ID) for your communication jobs as long as you are asking to same MB TCP server. So one gold rule of thumb, is to use different IDs (different MB_Client) for each communication partner, and you change modbus addresses dynamically by program. Siemens Technical Support Javier
	Last edited by: zenerz at: 10/30/2015 2:57:18 PM
Suggestion To thank Quote Answer
This contribution was helpful to 1 thankful Users vinothr2007

11/5/2015 3:55 AM	Rate (0)
vinothr2007 Posts: 3 Rating: (0)	Hi Javier, Do you mean one MB Server ID can communicate to Different MB Client ID? Is there any sample program available? Regards, Vinoth R
vinothr2007 Posts: 3 Rating: (0)
Suggestion To thank Quote Answer

11/9/2015 3:21 PM	Rate (0)
Kaulquappe Posts: 3093 Rating: (323)	Well Javier, I do not fully agree with your idea. There are a lot of small devices (e.g. energy meters), which are not capable to hold several connections. And even some smaller PLCs have got a limitation about 8 or 16 connections. And the Modbus device is not always the only device which is connected. Another point you should take care about, is the timing. When you write a holding register and read it back, you can only be sure that the write request was executed when you get DONE=TRUE. Then you can also modify the inputs or call the next FB instance. So why wasting connection ressources? When you know what you are doing and how the devices interact, you can use several connections. But it can`t be a general suggestion for a beginner. Regards, Kaulquappe zenerz It is much better idea to keep connections in parallel (active connections) rather than using the same resource (same instance -ID) for your communication jobs as long as you are asking to same MB TCP server. Javier
Kaulquappe Posts: 3093 Rating: (323)
Suggestion To thank Quote Answer

|

Share this page:

Share this page on...

Follow us on