-
Notifications
You must be signed in to change notification settings - Fork 687
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
EL1252 Latch time missing, but input is working #873
Comments
The problem is that the sync/latch unit is not enabled in the slave.
The standard function ecx_dcsync01() is not suited for this. But you can manually do this in the pre-op to safe-op hook:
This will enable the sync/latch unit, which is disabled by default. |
Thanks a lot @ArthurKetels! Few times I managed to get a bit different behavior with updated latch times in EL1252, but in next run it goes back to the issue before. run with latch times:
Most runs:
What I noticed - Input size is different. with 100ms cycle time I can get stable runs without disconnected slaves:
I moved to minimal setup, so slave info looks like this now:
My updated test code: Maybe somebody sees what am I doing wrong? |
Good day all!
I'm a beginner with SOEM, so sorry if it is a stupid mistake.
I'm trying to read input and its latch time from EL1252 module.
My simple test app connects and gets the input itself correctly:
so first input byte is correct and later on module should update the Latch time too, but it does not change.
My slave info:
Tried the same HW setup with TwinCat and it works properly and LatchPos2/LatchNeg2 updates properly.
I see that random slaves got lost in simple_test:
From https://infosys.beckhoff.com/english.php?content=../content/1033/el1202_el1252/7223406347.html&id= I see that I should assign 0x1A15 to SM2, but Twincat does not have this, and even after I tried to do that, nothing changed.
Could this be DC synchronization issue?
Maybe somebody has an idea what to check and what could be wrong?
The text was updated successfully, but these errors were encountered: