Hello everyone, we utilize a SIMOCODE to control the operation of key pumps within our factory. This system communicates via PROFINET and is programmed using the TIA Portal software. We monitor and adjust settings using an HMI. While the starting and stopping functions are functioning flawlessly, we are facing an issue regarding maintaining the command state in the event of a communication failure. Specifically, we want the pump to continue running even if there is a communication fault, ensuring that operations are not disrupted. Despite trying various solutions provided by Siemens support, such as disabling watchdog features and enabling external fault settings linked with bus faults, we have not found a successful resolution. If anyone has encountered a similar challenge and has successfully addressed it, we would greatly appreciate any guidance. Thank you in advance for your assistance.
The Simocode is crucial for maintaining the command status in the event of communication faults. Thank you in advance for your assistance. When a communication fault occurs, is it between the HMI and the PLC, or between the PLC and the drive? While it seems unlikely for communication faults to occur between the PLC and the drive, I am open to correction from experts in motion technology. Join the forum to learn more.
What occurs when attempting to deactivate non-redundant command mode? In this case, the system should await an "OFF" command rather than abruptly halting when the start signal decreases. It is essential to ensure that the Programmable Logic Controller (PLC) program incorporates ON and OFF bits for a smooth operation of the pump in typical scenarios.
When troubleshooting non-maintained command mode, consider disabling it and ensuring the PLC program utilizes both ON and OFF bits to control the pump. This will allow the pump to stop when an "OFF" command is received, rather than halting when the start signal goes low. Communication issues between the PLC and the motor can be resolved by ensuring proper communication is established. If you're interested, I can share the solution on the forum later. Thank you for the responses, everyone!
Thank you for sharing that you have found a solution to your problem. It's great to hear that everything is sorted out.
Pisoj mentioned that there was no issue with the normal ON-OFF function, as it was functioning correctly. He clarified that the communication loss problem occurred between the PLC and the motor, and not with the drive. The issue has been resolved, and if anyone is interested, he will share the solution on the forum. Thank you to everyone for the responses. Feel free to share the solution as we are experiencing the same problem.
Hi there, we faced a similar issue in our factory some time ago. The solution that worked for us was to change the programming of our fail-safe outputs in the TIA Portal. By writing a program for the fail-safe module to catch any possible PROFINET communication error, and thus maintaining the output state as it was prior to the communication failure. You might want to monitor the communication status and in case of failure, your program should force the output to stay on. I know it sounds a bit complicated but this workaround ensures that even if there is a communication failure, the pumps will keep running as intended. I hope this helps you address your issue.
It sounds like you're on the right track addressing this problem. One solution could be a fail-safe setup where the pump defaults to the 'ON' state in case of a communication failure. However, this has its own drawbacks, especially in emergencies where you'd want to shut off the machine. Another common approach to handle such scenarios is by introducing redundancy within the system. You could have a redundant communication path that the system would switch to in case the primary path fails. Nonetheless, the best solution would largely depend on the specifics of your setup. Has Siemens suggested any hardware or software modifications to achieve this, or is their solution solely based on the current configuration?
I've dealt with a similar issue before where I needed to ensure continuity during communication faults. One approach that worked for us was implementing a local control mode that allows the pump to run based on pre-set conditions if the PROFINET signal is lost. You might also want to look into configuring the SIMOCODE for a ‘fail-safe’ state, where it defaults to continue operation if it detects a loss of communication, instead of stopping. I recommend revisiting the configuration settings for your HMI as well; sometimes adjusting those can help retain the last good state. Good luck, and I hope you find a solution soon!
It sounds like you're dealing with a frustrating situation! Have you considered implementing a local logic control solution that would allow the SIMOCODE to maintain the run command based on the last received valid state? It might involve using a memory bit or a timer to hold the last valid command before the communication issue. Additionally, checking the firmware version and ensuring all components are up to date could help, as there might have been patches released that address communication robustness. I hope this helps, and 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: Answer: To ensure that the pump continues running during communication failures, you may need to adjust settings related to watchdog features and external fault settings linked with bus faults. However, if these solutions have not been successful, further troubleshooting may be required.
Answer: Answer: Common troubleshooting steps may include checking network configurations, verifying communication settings in the TIA Portal software, ensuring proper HMI functionality, and examining hardware connections for any issues.
Answer: Answer: Siemens may have specific guides or resources available that offer detailed troubleshooting steps for addressing communication faults and maintaining command state with SIMOCODE pro V PN. It is recommended to reach out to Siemens support or consult their documentation for further assistance.
Join hundreds of satisfied customers who have transformed their maintenance processes.
Sign up today and start optimizing your workflow.