Rating 
Thanks 15
| 7/21/2014 10:04 AM | |
Joined: 11/21/2007 Last visit: 3/31/2025 Posts: 2326 Rating:
|
Hello TIBI68 is right , you need to listen to your OEM. They seem to have used their own Modbus Library for CP341 so obviously they would know, how to troubleshoot the same. Cheers Navnag |
|
There is no such thing as the last bug in a program |
|
This contribution was helpful to
|
|
| 7/21/2014 1:19 PM | |
|
Joined: 11/21/2007 Last visit: 3/31/2025 Posts: 2326 Rating:
|
Hello You can view how to use Modscan32 by clicking on "Additional Information"-> Modscan32 from : http://www.win-tech.com/html/modbus1.htm Also if you install the software, you can go through the Built in Help. Cheers Navnag |
Last edited by: Navnag at: 7/21/2014 1:20 PMTypo corrected ! There is no such thing as the last bug in a program |
|
| 7/25/2014 8:00 AM | |
Joined: 12/1/2009 Last visit: 2/9/2025 Posts: 672 Rating:
|
Dear KRS2008104567, as Navnagalready mentioned youcan monitor & record the the traffic between DCS andeach PLC witha PC/Laptop with RS485/422 interface and a monitoring software. Just simply disconnect all PLC's andmonitor the traffic from DCS at each PLC point. Thattraffic report you send to your OEM. He is able to understandthat report. If the traffic report is correct the problem isat PLC's side. If the traffic report is incorrect the problem is in wiring or at DCS side. In order to verify that you connect your PC/Laptop as Modbus Master to the PLC and simulate the DCS by tryingto communicate with the PLC. Good luck! |
|
Give us your feedback and show us your respect! |
|
This contribution was helpful to
|
|
| 9/5/2014 3:29 AM | |
|
Posts: 24 Rating:
|
Good day guys! For your reference. Thank you for all the supprt and assistance. Attached is the troubleshooting procedure we conducted to restore serial communication. We downloaded and initialized the Data Block (Data Block for serial communication) from the original/commissioning logic program to eachnon-communicating PLCs. Do know what could be the possible cause of the failure in the first place? Surge is our suspect but how come it affected the software? Thanks and Regards, Karl AttachmentPFCCU PLC Serial Communication to DCS Restoration Procedure.pdf (283 Downloads) |
This contribution was helpful to
|
|
| 9/5/2014 5:56 AM | |
|
Joined: 11/21/2007 Last visit: 3/31/2025 Posts: 2326 Rating:
|
Hello KRS2008104567 I would strongly doubt that a "Surge" would corrupt one particular Data Block in each PLC. Cannot say for certainty, as I do not have access to your software, but I feel It is due to some bug in thecommunication software which causes the communication to "Hang" under certain specific conditionand restart when DB is initialised. If this is true, then problem is likely to occur again if same conditions occur again Hope this helps Cheers Navnag |
|
There is no such thing as the last bug in a program |
|
| 9/5/2014 9:34 AM | |
|
Joined: 12/1/2009 Last visit: 2/9/2025 Posts: 672 Rating:
|
Dear KRS2008104567, if I remember correctly there were some bugs in older versions of the communication function blocks. Check yours and update them if required. Secondly check the correct initialisation of the communication in the startup OB's as described in the manual. Best Regards. |
|
Give us your feedback and show us your respect! |
|
| 9/17/2014 10:45 AM | |
|
Posts: 3093 Rating:
|
Hello, the changes including bug fixesare reported with the firmware update. Firmware update for CP341 Regards, Kaulquappe |
This contribution was helpful to
|
|
Follow us on