SiePortal

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

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

MODBUS TCP/IP communication error A008 and A01E

12/27/2012 4:15 AM	Rate (0)
Shailendra Experienced Member Joined: 6/10/2009 Last visit: 1/16/2026 Posts: 46 Rating: (1)	Dear all, Our system: PCS7 V8.0 AS - 414-5H with CP EX20 We are using MODB4H block for communicating with 3rd party modbus. But we are getting error code A008 and A01E. In netpro connection is showing established. On the other side there is a customized modbus software. This sw is communicating with MODSCAN, we are getting data on modscan. But with our block we are not getting an data in PLC DB. On the other hand we are also getting data inPLC using MODSIM software. With the kind of error weare in impression that there may be some mismatch in frames being send and received. So we traced out the frames (Please find attached). Kindly guide us if there is any problem in the frames. And whats wrong. Attachment Traffic screen shot.jpg (398 Downloads)

Suggestion To thank Quote Answer

12/27/2012 1:44 PM	Rate (0)
Kaulquappe Posts: 3093 Rating: (324)	Hello Shailendra, the combination of error A008 andA01E leads to the thinking that the time MONITOR is too short. Which time do you use? How long takes it until the server answers a request? I recommend to increase MONITOR. Regards, Kaulquappe
Kaulquappe Posts: 3093 Rating: (324)
Suggestion To thank Quote Answer

1/1/2013 4:42 AM	Rate (0)
Shailendra Experienced Member Joined: 6/10/2009 Last visit: 1/16/2026 Posts: 46 Rating: (1)	Dear Kaulquappe , Thank you for your reply. The problem is resolved. There was a mismatch in the header code recieved from 3rd party. They modified there code and it is resolved.

Suggestion To thank Quote Answer
This contribution was helpful to 2 thankful Users S_Moderator umencho

Share this page:

Share this page on...