7/11/2014 6:28 AM | |
Joined: 11/21/2007 Last visit: 9/25/2024 Posts: 2325 Rating: (308) |
HelloKRS2008104567 A CP 341 can be used with its integrated Communication Drivers or Special "Loadable" Drivers. CP-341 has several integrated Drivers e.g. ASCII , 3964R , etc . In case these drivers have been used, then you can just remove the existing CP-341 and plug in the new CP-341. However several loadable drivers are also available for CP-341 e.g. In case of loadable drivers, after replacement of the CP341, the driver has to be downloaded to the module. Pl follow the following procedure : Remove the existing module. Remove the Blue Colored Hardware Dongle at the back of the old module Plug the dongle into the new module. Install the new module into the Rack. Download the Relevent Driver from the corresponding link provided above ( Pl check the version ) Download the Driver to the CP-341 ( Procedure provided in the manuals available on the above links ) Hope this helps Cheers Navnag |
There is no such thing as the last bug in a program |
|
This contribution was helpful to2 thankful Users |
7/11/2014 9:06 AM | |
Posts: 24 Rating: (0) |
PLC Firmware Version: V2.0.11 CP341 Old Module Firmware Version: V1.0.2 CP341 Replacement Module Firmware Version: V2.1.1 Thank you. Regards. |
7/11/2014 9:45 AM | |
Joined: 11/21/2007 Last visit: 9/25/2024 Posts: 2325 Rating: (308) |
HelloKRS2008104567 If there is no Dongle it should be 100% plug-and-play, right?- Absolutely right for compatible Firmware Versions. In your case Old Firmware and new Firmware do seem to have an issue. Pl Check : As per this Update : The new firmware version V2.1.0 optimizes the data throughput of the CP341-V2: To be able to utilize the higher performance you require the "Configuration Package for Point to Point Communication“ with version V5.1 incl. SP11 (see entry ID 27013524). The parameterization data for the CP341-V2 (FW version V2.1.0 and higher) must be newly generated with PtP-Param V5.1.11 for this purpose. Therefore you should regenerate the PtP Parameters for this CP341 and download to the CPU. Alternatively you can downgrade the firmware version ( I would however not recommend this ) Hope this helps Cheers Navnag |
There is no such thing as the last bug in a program |
|
7/11/2014 10:07 AM | |
Posts: 24 Rating: (0) |
I agree. I am currently downloading this drivers. CP PtP parametrization software http://support.automation.siemens.com/WW/llisapi.dll/csfetch/27013524/Setup_PtP_V5114.exe?func=cslib.csFetch&nodeid=81303630 ) Modbus slave drivers http://support.automation.siemens.com/WW/llisapi.dll/csfetch/27774276/Modbus-Slave319.exe?func=cslib.csFetch&nodeid=64128597) . But the mystery is, how come the previous replacement worked simply as plug-and-play while the later does not. Anyway THANK YOU VERY MUCH! for your assistance. Regards. |
This contribution was helpful to1 thankful Users |
7/15/2014 10:08 AM | |
Posts: 24 Rating: (0) |
No the modules does not have a Dongle. IsPtP param V5.11 SP 14 ok to use for this firmware? This version was suggested by our OEM. Thanks. |
7/16/2014 7:48 PM | |
Posts: 3093 Rating: (323)
|
Hello, it depends on the application, there is no "standard". Regards, Kaulquappe |
This contribution was helpful to2 thankful Users |
7/20/2014 1:16 PM | |
Joined: 11/21/2007 Last visit: 9/25/2024 Posts: 2325 Rating: (308) |
HelloKRS2008104567 You should check the following with a Modbus Master / Slave Simulator software like : I assume that you are communicating on RS485 / RS422 as you are having a Daisy chain. You will beed a Serial/USb to RS485 convertor for checking the communication. You can check if your CP 341 is communicating as a Modbus Slave by Setting up the Modbus Simulator as a Modbus Master and the CP as Slave. Also you can check if DCS is communicating properly by Monitoring the DCS telegrams using a Serial Port Monitoring software ( e.g. Docklight) or by configuring the Modbus Simulator as a Slave. This way you will be able to identify the problem point. One you have identified the problem point, pl post your observations here for further advise, Hope this helps Cheers Navnag
|
There is no such thing as the last bug in a program |
|
This contribution was helpful to1 thankful Users |
7/20/2014 4:31 PM | |
Joined: 12/1/2009 Last visit: 10/27/2024 Posts: 672 Rating: (147) |
Dear KRS2008104567, it is difficult to say what could be the problem without deeper analysis. Using "ASCII" setting at the CP's explains why you don't have anydongle plugged in your CP's. Unfortunate this setting does not tell us about the protocol used fordata exchange. Maybe you can find that out from some documents. It is possilbe that a PLC software uploadwill supportus finding that out but thats not guaranteed. If nothing can be foundin the softwarea trace of thereceived data by the PLC's need to be done. That tracehas to match with the protocol description. As already written byNavnagyou will needproper hardware/software and knowledge of using these tools tobe able to localize the problem. It could be anywhere: PLC's, DCS, wiring....... Best of luck! |
Give us your feedback and show us your respect! |
|
7/21/2014 9:18 AM | |
Joined: 12/1/2009 Last visit: 10/27/2024 Posts: 672 Rating: (147) |
Dear KRS2008104567 , your OREMseems to know much more than us and his suggestions areright. Listen to him ! In worst case bring him to your site to solve yourproblem. Best Regards. |
Last edited by: TIBI68 at: 7/21/2014 9:19 AMGive us your feedback and show us your respect! |
|
This contribution was helpful to1 thankful Users |
7/21/2014 10:04 AM | |
Joined: 11/21/2007 Last visit: 9/25/2024 Posts: 2325 Rating: (308) |
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 to1 thankful Users |
7/21/2014 1:19 PM | |
Joined: 11/21/2007 Last visit: 9/25/2024 Posts: 2325 Rating: (308) |
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: 10/27/2024 Posts: 672 Rating: (147) |
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 to2 thankful Users |
9/5/2014 3:29 AM | |
Posts: 24 Rating: (0) |
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 (222 Downloads) |
This contribution was helpful to1 thankful Users |
9/5/2014 5:56 AM | |
Joined: 11/21/2007 Last visit: 9/25/2024 Posts: 2325 Rating: (308)
|
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: 10/27/2024 Posts: 672 Rating: (147) |
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: (323)
|
Hello, the changes including bug fixesare reported with the firmware update. Firmware update for CP341 Regards, Kaulquappe |
This contribution was helpful to1 thankful Users |
Follow us on