3/4/2019 7:03 AM | |
Joined: 1/21/2018 Last visit: 6/5/2024 Posts: 12 Rating: (0) |
Hi Everybody. I am writing because I have a problem with a new CP that I must install and establish communication to an old PLC S5. The old communication module from the CP was a CP1613 (V5.0 from WinCC) and the new communication module is a CP1623 (V7.2 from WinCC). Everything seems to be OK concerning the installation and configuration of the new module but the problem is I cannot reach a successful communication with the new module, so I have 3 questions to try to solve my problem. I also attached some images (Questions) so that you can see the configuration. Question 1: To configure the old communication module CP1613, on picture A I can configure some Net Parameters such as Duplex Mode, Media Type and Transmission Rate. However, to configure the new communication module CP1623, on picture C I cannot see those parameters. Where do I find those paramaters? I can't find anything neither in the interface PG/PC nor in the Communication Settings. Notice that on picture B and D I had to configure the same MAC Address. Question 2: On WinCC Explorer, by checking the connection properties in the drive "S5-Transport (CP1413-1)" on picture A, I realize some tags are configured as Local and Remote TASP (PC and PLC) and the Ethernet Address concerning the PLC as well. I wrote the same configuration for the new version (Picture B). The question is: Is there any place in the WinCC Explorer (V7.2) where I should write the word "PC" in order to match the configuration with the word written in TSAP?. Question 3: On WinCC Explorer (V5.0), The "Set Interface PG/PC" had an access point called "CP_H1_1:--->CP1613(ISO)". See picture A. As a consequence, the system parameters on WinCC have got as a device name the same legend (/CP_H1_1:/CP1613(ISO)). See picture B. Nowadays, On WinCC Explorer (V7.2), the "Set Interface PG/PC" has an access point called "CP_H1_1:--->CP1623.ISO.1". See picture C. So, the the system parameters on WinCC have got as a device name the same legend (/CP_H1_1:/CP1623.ISO.1). See picture D. Is this configuration correctly written in order to match and make it compatible with the new module? Is this enough to reach a successful communication? Thank you in advace for your answer. AttachmentQuestions.zip (60 Downloads) |
3/18/2019 9:39 AM | |
Joined: 12/12/2011 Last visit: 12/30/2020 Posts: 821 Rating: (41)
|
Hi, would recommend to use this service: https://support.industry.siemens.com/cs/de/en/sc/4650 B.R. |
Grundkurs/Systemkurs WinCC V7: |
|
Follow us on