Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

WAGO PFC200 / VACON NX EtherCAT communication problems #20

Open
joakimgisto opened this issue Jan 31, 2025 · 1 comment
Open

WAGO PFC200 / VACON NX EtherCAT communication problems #20

joakimgisto opened this issue Jan 31, 2025 · 1 comment

Comments

@joakimgisto
Copy link

Hi,

I am trying to communicate with 4 pcs of WAGO 750-354 remote I/O racks and 5 pcs of Vacon NX VFDs equipped with OPT-EC cards (V005) over Ethercat. I am using an Omron GX-JC03 junction slave to split the Ethercat bus into two branches and a WAGO PFC200 (750-8212 Gen 2) running the Codesys Ethercat Master. The station aliases are set manually in the Vacon drives and configured accordingly in the Master settings. The desired cycle time for the Ethercat task is 10 ms.

When starting the system the Ethercat master cannot establish communication to the slaves and the Master log returns a lot of errors, e.g. "SDO access timeout" / "Invalid input / output configuration". However, when disabling the OPT-EC slaves, the Eethercat communication starts working. When logging the CPU load using Putty, I noticed that the OPT-EC slaves are pretty CPU heavy (up to 80%) for some reason. Also, when increasing the cycle time for the Ethercat task to 20 ms or above, the communication works.

Has anyone encountered similar problems?

Setup used:

Image

Master settings:

Image

Similar slave settings are set in all OPT-EC slaves:

Image

@Ekristoffe
Copy link

Hello,
Could you also create a post here: https://www.wago.community/
You may have faster help from the worldwide community.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants