I am facing some challenges setting up WinCC Flex Runtime to communicate with a PLC via Ethernet on a PC. It seems that integrating the Flex project in Step7 may have unnecessarily complicated things. Despite everything appearing correct in the Communication settings of Flex, one anomaly is the expansion slot being listed as 2 while the CP is actually in Slot 4. However, since the connection Partner is the CPU and the CP is the node, it should be fine. I am unable to find a way to change the Slot number in NetPro. Another issue that came to mind is the disappearance of the Runtime license during the license swapping process between different PCs. Could this be the reason for the Ethernet communication failure? While communication via MPI is working, it is crucial to get the optically isolated Ethernet connection operational due to a previous incident with a blown USB adapter. If anyone has any suggestions or solutions, I am open to hearing them. Additionally, I caught a rapidly disappearing error message with the Print Button and managed to copy it into paint. The error message reads "General connection error 0x384" (translated from German).
When using an S7-300, the slot number is always 2, regardless of whether a CP343-1 is being used as an intermediary. Even in cases where there may be licensing issues, the RT will still function properly, albeit with occasional nag screens. In the WinCC Flexible project, is the communication pathway via S7ONLINE? It is important to avoid using softbus unless Simatic Net has been installed and properly configured. Make sure you can successfully ping the CP343-1 from your PC. Check if the PG/PC Interface is set to S7ONLINE=Ethernet(TCP/IP) and confirm that S7ONLINE=Ethernet(TCP/IP) is assigned to the correct NIC.
Update: For additional assistance, I was able to capture a fleeting error message with the Print Button, translating to "General connection error 0x384" in English. A helpful tip is to create a page for message viewing, including system messages to easily catch such error messages. This is crucial for capturing VBS error messages.
Thank you Jesper for your input. Progress is being made in understanding the communication path in Flex, which primarily involves Softbus. Despite this, I am unable to find a way to modify this setting in NetPro. The "Type" is currently identified as "S7 connection" in NetPro. The PG/PC interface is configured as "S7ONLINE (STEP7) --> TCP/IP -> Allied Telesis AT-2701...". I am able to successfully download from the PC to the PLC and access the program online, confirming that the physical connection is functioning correctly.
Here's a step-by-step guide on how to resolve a complex issue in Simatic Manager for WinCC Flex HMI configuration. First, navigate to the Configuration settings in Simatic Manager and select the WinCC Flexible RT index. In the HW Config section, remove all components except for the WinCC Flexible RT index. Then, access the Station Properties from the menu and double-check that S7RTM is unchecked. Save your changes and compile the settings. Next, configure the connection properties by specifying S7ONLINE, Ethernet, and the IP addresses of both the PC and PLC, with rack=0 and slot=2. Save and compile the changes. If you encounter error messages regarding symbols, simply ignore them. Transfer the RT to the target PC and restart the system. This process may help resolve the issue and optimize the performance of your HMI system.
I have attempted to make adjustments in the HW-Config, which were successful. However, in Flex, the Communication driver appears orange and I am unable to modify the Network setting from MPI in the Parameter field. The Partner is still set to 313C in the Connection Field, but the Node box is empty. The "HMI device" box indicates the Access point is configured as S7ONLINE, indicating progress halfway through the process.
It sounds like you’re dealing with a pretty tricky setup there! It’s good that MPI is working for you, which suggests the basics are functional. For the slot number issue, have you tried checking the Module Properties in NetPro to see if there's an option for adjusting the slot assignment? Sometimes a simple refresh or restart of the software can also prompt it to recognize the correct configuration. As for the runtime license, if it’s not properly recognized on the new PC, that definitely could cause communication breakdowns. Make sure you are using the correct license file and also confirm that the license is activated on that machine. As for the error 0x384, it usually hints at a connection issue—perhaps double-check your IP settings and ensure nothing in the network settings changed during your swap. Good luck, and I hope you get everything up and running smoothly!
It sounds like you're dealing with a few frustrating issues! First off, the slot discrepancy can sometimes be a red herring, especially if everything else is configured correctly; just make sure that the configuration in WinCC Flex corresponds to your actual hardware setup. Regarding the disappearing Runtime license, this could definitely impact your Ethernet communication, as licensing issues often limit functionality. I'd recommend checking if the license is properly installed and whether it needs to be reactivated after the PC change. For the "General connection error 0x384," it often points to network configuration problems, so double-check your IP settings, and ensure that the firewall isn't blocking your connections. Hang in there, and hopefully, you’ll get it resolved soon!
✅ Work Order Management
✅ Asset Tracking
✅ Preventive Maintenance
✅ Inspection Report
We have received your information. We will share Schedule Demo details on your Mail Id.
Answer: Answer: Troubleshooting Ethernet communication issues can involve checking settings in both WinCC Flex and the PLC, ensuring correct slot configurations, addressing potential license-related problems, and identifying and addressing error messages like "General connection error 0x384."
Answer: Answer: Changing the slot number in NetPro may involve reviewing the configuration settings for the CPU, CP, and expansion slots to ensure proper communication setup.
Answer: Answer: The disappearance of a Runtime license during license swapping between PCs could potentially impact Ethernet communication. It's important to ensure that the appropriate licenses are active and correctly configured for each system to avoid communication issues.
Join hundreds of satisfied customers who have transformed their maintenance processes.
Sign up today and start optimizing your workflow.