-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
working counter missmatch #23
Comments
We did some more debugging. We got the PDO mapping working correctly for the Sercos drive. But looking at a tcpdump trace (dump_2.zip), we found that some frames have a working counter mismatch. Looking into the frame shows that when a wkc of 8 occurs, the output data of the sercos drive is 0. So something goes wrong in the slave. For now we ignore the wrong wkc in the pd callback (6b0af7b). |
i think the slave 4 is still not in OP state. It may also be that something goes wrong setting to OP the first time because it took so long for that slave. i'll check that.. edit: is it possible to move the drive? |
We have now found the problem. libosal uses Line 1880 in 9108db1
Reading S-0-0029 had high increasing values before the dc time fix, but with the fix it stays low. So I think it was a timing issue. I can provide a PR to have function ec_send_distributed_clocks_sync_with_rtc(ec_t *pec, osal_uint64_t rtc) or similar.
I think the slaves not going to OP in the log is caused by not enabling intermediate circuit voltage. Our electrical system is designed in such a way that the voltage must be enabled manually and the drives check the voltage status. |
Just re-opened to keep track of it until PR is merged |
Hi Robert,
I get a
2024-09-03T13:33:12.017Z ERROR [libethercat_rs] MASTER_RECV_PD_GROUP: group 0: working counter mismatch got 8, expected 9, slave_cnt 5, mismatch_cnt
.Does this mean I have a wrong PD configuration and the slave ignores my cyclic process data?
Here is the full log:
out_pd_wk.log
The text was updated successfully, but these errors were encountered: