Skip to Content

Register Login

Industry Online Support

Technical Forum

Navigation

OpenModbus/TCP Error 16#2524

Created by: JamesH at: 9/7/2012 3:23 AM (11 Replies)

Rating (0)

Thanks 5

Result pages:: |; 1 | 2; |

12 Entries

Entries per page: 10 | all

9/7/2012 3:23 AM	Rate (0)
JamesH Posts: 7 Rating: (0)	Hi, I have set up a S7319 as a modbustcp server using FB102 MODBUSPN. The PLC is communicating however I receive the above error. If I remove the call to FB102 from OB35 the error clears. Attached are the screenshots for the Module Information showing the error. Attachment S7 Error.jpg (554 Downloads)
JamesH Posts: 7 Rating: (0)	Last edited by: JamesH at: 9/11/2012 1:59 AM
Suggestion To thank Quote Answer

9/7/2012 3:24 AM	Rate (0)
JamesH Posts: 7 Rating: (0)	Another error message Attachment S7 Error2.jpg (542 Downloads)
JamesH Posts: 7 Rating: (0)
Suggestion To thank Quote Answer

9/7/2012 7:15 AM	Rate (0)
manmeet Gold Member Joined: 1/3/2006 Last visit: 2/19/2024 Posts: 726 Rating: (71)	@S7error.jpg --> Press 'Open Block' button and it will take you where the error is. @S7error2.jpg --> Insert OB121 in your program. With this when programming error will occur CPU will look for OB121, when found it will execute it and will not goto Stop mode, if OB121 is not found then CPU will goto Stop mode when such error occurs.

Suggestion To thank Quote Answer
This contribution was helpful to 1 thankful Users JamesH

9/8/2012 4:49 AM	Rate (0)
JamesH Posts: 7 Rating: (0)	Hi, I removed OB121 to see where the error was. As you can see it is caused by FC10 which is an inbuilt Siemens Block "EQ_STRING". FC10 is being called by FB102 "MODBUSPN" also a Siemens block. So I know where the error is occurring but I cannot do anything about it because I cannot open the blocks. Attachment FB102.jpg (548 Downloads)
JamesH Posts: 7 Rating: (0)
Suggestion To thank Quote Answer

9/8/2012 6:16 AM	Rate (0)
fritz Diamond Member Joined: 10/7/2005 Last visit: 11/16/2024 Posts: 3027 Rating: (1057)	Hello JamesH Question: Did you obtain a license for the MODBUSPN Block and applied it? If not, it will still work in Demo mode and can be used for evalution purposes, but it will flood the Diagnostic Buffer with messages and lead to OB121 calls (which are the symptons that you have, see also the manual for more). It should in this case also enter W#16#A090 entries to the Diag Buffer, which are notshown in your screendump though, so perhaps you have a different problem. Please check anyhow and let us know what you find.
	Cheers fritz The advice and opinion given in this thread is that of the author and does not necessarily reflect the views of I S Systems Pty Limited. To find out how I S Systems can help you with your automation needs please visit www.issystems.com.au.
Suggestion To thank Quote Answer
This contribution was helpful to 1 thankful Users JamesH

9/8/2012 9:33 AM	Rate (0)
manmeet Gold Member Joined: 1/3/2006 Last visit: 2/19/2024 Posts: 726 Rating: (71)	Interesting error !Check for license details as mentioned by Fritz. Also make a fresh program with only modbus blocks in it. Pick these blocks from sample program. See if you still have same error. Also update us.

Suggestion To thank Quote Answer

9/9/2012 10:17 AM	Rate (0)
JamesH Posts: 7 Rating: (0)	The block is definitely licensed, if I remove the license I do get the A090 error. I am also getting error 80C4 at the STATUS_CONN output which is generated by the TSEND and TRCV blocks.
JamesH Posts: 7 Rating: (0)
Suggestion To thank Quote Answer

9/11/2012 4:07 PM	Rate (0)
Kaulquappe Posts: 3093 Rating: (323)	Hello James, which version of FB102 do you use? Do you call FB102 in OB121? Is FC10 in your project EQ_STRNG of the standard library? Did you check the IDB whether it is corrupted (just delete it and generate it again). Regards, Kaulquappe
Kaulquappe Posts: 3093 Rating: (323)
Suggestion To thank Quote Answer
This contribution was helpful to 2 thankful Users fritz JamesH

9/12/2012 3:47 AM	Rate (0)
JamesH Posts: 7 Rating: (0)	Thanks for all the responses, I did a full download of the PLC and the error has resolved. I am still getting the W#16#80C4 error from the TSEND and TRCV blocks but it does not affect the diagnostic buffer.
JamesH Posts: 7 Rating: (0)
Suggestion To thank Quote Answer
This contribution was helpful to 1 thankful Users fritz

9/12/2012 10:09 AM	Rate (0)
Kaulquappe Posts: 3093 Rating: (323)	Hello James, which local port number do you use at the S7? Some old firmware versions of the CPUdid not support local port numbers smaller than 2000. Does your CPU support the port number you are using? A port number which is not support by the CPU may lead to error 80C4. Regards, Kaulquappe
Kaulquappe Posts: 3093 Rating: (323)
Suggestion To thank Quote Answer

|

Share this page:

Share this page on...

Related topics by keywords:

ModbusTCP

Follow us on