Hello! I am encountering a new issue with my GE CPE100 unit. LAN2 is configured as ProfiNet, with multiple Turck TBEN-L4-16DIP modules and a Numatics Valve Stack. The ProfiNET DCP tool indicates that all devices are communicating correctly, without any errors or diagnostic messages. The PLC is successfully controlling the valves without any problems. While the inputs to the Turck blocks show state changes on the block itself and on the block's webpage on the network, the inputs are not changing state in the PLC program. I have tried reconfiguring the blocks twice using different GSDL files, but there has been no improvement. Any insights or suggestions on this matter would be greatly appreciated. Thank you. -ABJECT
Hello, based on the information provided, it is difficult to determine the root cause of the problem you are experiencing. It would be helpful to set up a mirroring port with a switching hub to capture Wireshark traces of the network traffic between the GE CPE100 controller and the TBEN-L4-16DIP modules. By examining the statuses of the individual slots, we can conduct a more thorough analysis. Although I am not familiar with the GE CPE100, it may be possible to troubleshoot the issue using TIA Portal instead of Wireshark.
Believe me, I did not willingly opt to use the CPE100. Ever since the transition to Emerson branding, I have been surprised by how they managed to make GE products even harder to use. Nonetheless, if anyone can overcome this challenge, it's GE. I agree with your opinion that using Wireshark is the most promising solution unless others have encountered this issue too. Optimism remains high. Thank you for your input.
I am confident that you can solve this issue. I would be more than happy to examine the Wireshark traces. Additionally, there is a lesser-known feature in the PROFINET IO add-in for Wireshark that is maintained by Profinet International. This feature is installed seamlessly alongside Wireshark and allows users to create a folder for storing GSDML files used in the application. When the initial messaging for connection allocation is transmitted and the device ID is included in the traffic, the add-in decodes the trace up to the higher layers of the application if it finds the device in the registered GSDML files folder. This enables users to view the slot name and, in the case of alarms and diagnostics, parse and display the information contained in the GSDML files in the captures. This feature is both impressive and free of charge, making it a valuable resource. Just like this post, it offers valuable insights and functionalities for users.
Hi ABJECT! It sounds like you're dealing with a frustrating issue. Since the Turck modules are showing state changes but not reflecting in the PLC, I'd recommend double-checking the mapping of the inputs in your PLC configuration to ensure they are correctly assigned and that there are no mismatches. Sometimes the status bits may need to be specifically defined in the PLC program for them to be recognized. Also, consider looking at the communication settings and confirming that the data is being read in the correct format. If all else fails, reviewing logs or diagnostics from the PLC itself might offer more insights. Best of luck!
Hey ABJECT, it sounds like you’ve got a solid setup but are hitting a frustrating snag! One thing to check is whether the input data size in the PLC is configured correctly to match the Turck modules. Sometimes, the issue can be as simple as a mismatch in data types or sizes. Additionally, make sure to verify the mapping of your inputs in the PLC program; sometimes they can get overlooked during configuration. If everything checks out, maybe try rebooting the PLC or even power cycling the Turck modules, as this can sometimes resolve communication glitches. Good luck!
✅ 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: 1. Why are the inputs from Turck TBEN-L4-16DIP modules not changing state in the PLC program despite indicating correct communication in the ProfiNET DCP tool? - This issue could be related to the configuration settings or compatibility between the Turck modules and the PLC. It is recommended to verify the GSDL files, network setup, and ensure proper communication protocols are being used.
Answer: - Troubleshooting steps may include checking cable connections, verifying device configurations, confirming network settings, updating firmware, and checking for any reported diagnostic messages or errors in the ProfiNET DCP tool.
Answer: - To ensure proper communication, it is important to check the wiring connections, device compatibility, configuration settings, and network communication protocols. Verifying that the PLC is able to control the valves successfully can help in diagnosing the issue further.
Answer: - When working with multiple Turck modules, it is essential to ensure that each module is properly configured, connected, and compatible with the PLC system. Checking for any address conflicts, communication delays, or configuration errors can help in troubleshooting communication issues.
Join hundreds of satisfied customers who have transformed their maintenance processes.
Sign up today and start optimizing your workflow.