Technical Support Request: Service Error in MCX-OS Production Mode

jsh

am writing to request technical assistance regarding MCX-OS.

I attempted to run MCX-OS in Production Mode, but encountered a "service error" as shown in the attached photo.

Specifically, this issue occurs when I establish the PDO link for the motor drive via EtherCAT (ECAT).
(Note: The error does not occur when the link is disabled, but the motor fails to operate in that state.)

A notable point is that while the motor encoder values are visible in the Desk, they are not being output (displayed) in the Grid.

Coen_Smeets

Hey,

The linking of the device is incorrect. You should add links to where the data needs to go. For example, Controlword should be linked to root/DriveLogic/driveControlWord. You can view 'Axis-01' as reference:

Hopefully, that resolves the issues.

The following documentation page can also be of use to check if the device is correctly configured:
https://docs.motorcortex.io/docs/frequently-asked-questions/ethercat/faq-ecat1/

Coen

philippeH

Coen_Smeets

Hi jsh,

Please link the ECAT as described here.
Start with a a Slave which is in OP, and add linking.

In your etherCAT configuration, you linked inputs to inputs. and outputs to outputs, this is not allowed.
This is the reason why the application does not start.

I can also help with a headstart if you fetch your etherCAT configuration to the portal:

On the right side -> create package -> press fetch config.

Let me know once you have done this, so i can provide you with an correct example for your EPOS4 50/5 Drive.

jsh

I am unable to access the Grid. It appears there is an issue with the EtherCAT (ECAT) configuration.
I have switched both the Axes and the MCX to Production Mode.
For the hardware, I am using an Intel-based ASUS industrial PC

Coen_Smeets

Hey,

Could you show the result of mcx-lastlog in the terminal of Cockpit. Here, you can see warning and errors that potentially could have led to the Grid not working. It shows the live log since motorcortex restarted. So, to find an issue like this it would be a good idea to:

First restart Motorcortex: sudo motorcortex restart
Check the log: mcx-lastlog

Without the log it is hard to figure out the problem, but from the screenshots my guess is that have defined 6 machine axes, but in the ethercat you only have 1 axis configured. You can do 1 in production and the other 5 in simulation. if you only want to check the first axis.

Hopefully, the log clears up what the source of the issue might be.

Coen

jsh

I have re-performed the entire process from scratch, leaving the PDO links unassigned. As a result, the system successfully switched to OP mode, and I confirmed that the encoder values are being output correctly.
However, an error occurred while loading the process to execute operations in the Machine App Grid.

Afterward, I enabled the PDO links in ECAT, but the issue of failing to transition back to OP mode recurred.