Hello everyone,
I'm facing an issue establishing a proper connection between Sepasoft and the PLC. Essentially, I need the PLC to receive the Command_Number and respond with a State_Number.
Previously, I managed this using a script. The script would write the new value on the 'Value Changed' event. This worked. However, I thought a direct link might simplify things?
Linking from Sepasoft to the PLC works instantaneously. The other way around... sometimes? At random, long intervals it seems.
I've configured the State_Number as shown in the image above. Although the displayed value is the value from the PLC, Sepasoft doesn't interpret it everytime.
This is also shown in the image above. At a certain moment the handshake and state_number were received from the PLC.
Am I approaching this the wrong way?
Any insights or advice would be greatly appreciated. Thanks in advance!
You might have more luck submitting a support ticket directly with Sepasoft
2 Likes
I also have a similar problem. In my recipe, when a batch is running, sometimes a phase goes to an 'internal fault' state. I've noticed that this happens during the transition from the resetting state to the running state, but from the PLC, the state change is being done correctly. I think the module itself doesn't recognize the state changes, and after spending too much time in the resetting state, it goes to the internal fault state. Have you been able to solve your problem? If so, could you please share your solution?
Hey Alfonso,
We've never pinpointed the exact cause, but we suspect it might be related to the OPC connection.
Within the gateway, try to drill down (Status --> Tags) to the Command_Number and State_Number tags to check if the quality is good. While the phase itself might appear good, the underlying tags could be problematic.
We were using TIA controllers, which have limitations in terms of OPC connection, possibly causing the issue.
Additionally, you mentioned the error occurs when transitioning from resetting to running. This might be normal, as the state model expects a starting command to go from Idle to Running. And before the batch engine can give that start command, it has to recognize the Idle state.
I hope this helps! You can also submit a support ticket with Sepasoft, as Amy mentioned.
Kind regards,
Ben
