FORUM CTRLX AUTOMATION
ctrlX World Partner Apps for ctrlX AUTOMATION
Dear Community User! We are updating our platform to a new
system.
Read more: Important
information on the platform change.
a month ago - last edited a month ago
So We're working on a project, and i've come across something that i've never seen before.
Basically We use a CtrlX Core With NodeRed and EtherCAT Master apps. Have been working fine for some months, no issues, but today the machines went haywire.... I couldn Acess the CtrlX-CORE Web-app....
But if i directly put in NodeReds Path it could go into there and Check stuff...
According to NodeRed it was some issue with EtherCAT communication, it could not get the slaves and I got ERROR: Socket Hangup with alot of Error: Number of Requests too High... But that i can explain.
What i know is the Customer did a Database Server Maintenance Last Two Days... Could that have somehow caused this to happen to the Machines or Communication Protocol? Has anyone Experienced it before and maybe figured out WHY?
NOTE: this was resolved with a simple Power Off and after a few seconds Power On.
4 weeks ago - last edited 4 weeks ago
@LeoSsurahyaseen pdf wrote:So We're working on a project, and i've come across something that i've never seen before.
Basically We use a CtrlX Core With NodeRed and EtherCAT Master apps. Have been working fine for some months, no issues, but today the machines went haywire.... I couldn Acess the CtrlX-CORE Web-app....
But if i directly put in NodeReds Path it could go into there and Check stuff...
According to NodeRed it was some issue with EtherCAT communication, it could not get the slaves and I got ERROR: Socket Hangup with alot of Error: Number of Requests too High... But that i can explain.
What i know is the Customer did a Database Server Maintenance Last Two Days... Could that have somehow caused this to happen to the Machines or Communication Protocol? Has anyone Experienced it before and maybe figured out WHY?
NOTE: this was resolved with a simple Power Off and after a few seconds Power On.
It sounds like the database server maintenance might have indirectly impacted the network or resources the CtrlX Core was using, potentially causing disruptions in communication with the EtherCAT slaves. High error rates and issues like “Socket Hangup” and “Number of Requests too High” could arise from network congestion or resource conflicts, especially if network configurations changed or if there was increased demand during the maintenance.