Hi Graeme,
thanks for the detailed reply!
With my now modified cycle, I get a difference of about 4.45 cycles. As I
now receive the current position before I send out the next target
position (while it was the opposite way before), it makes sense it is one
cycle more. But I compare the
Hi Graeme, hi Gavin,
wow, thanks for the great, detailed and quick replies!
This was extraordinarily helpful!
I like Graemes suggestion for the cycle very much. I can cope with the
delayed PDO sending much better than I could cope with a fixed, rather
long wait in my cycle.
I modified my
Hello,
I am progressing quite well with EtherLab and am currently working on
synchronizing outputs/movement with the Master time. We are using the
Master 1.5.2 from the 1.5.2 branch, ec_generic driver with PREEMPT RT
(kernel 4.14.28).
In our application, we need to be synchronized to the real
Hello,
I am currently experimenting with the Cyclic Synchronous Position mode of
ELMO drives. I am using EtherLab 1.5.2 from the 1.5.2 branch with
ec_generic on a PREEMPT RT system (kernel 4.14.28).
If I compare the current position the drive reports in the frame I receive
after I send a
Hello again,
after sleeping over the issue, I did some more tests.
In fact, the function that takes the long time is ecrt_domain_process (and not
ecrt_domain_queue). However, if I do no longer the call to ecrt_domain_queue,
then the ecrt_domain_process will not take long (that is what got me
Hello,
I successfully got the IgH EtherCAT Master running on an IEI board using Gentoo and the 4.14.28-rt23 PREEMPT kernel.
Now, I switched to a self-made, yocto-based distribution, using the same kernel (I tried both the kernel built by our yocto recipe and my own "hand-built" kernel with
Hi Gavin,
<> Have you issued an mlockall at the start of your process? It can also
<> help to explicitly prefault your stack so that you don't get a page
<> fault later if your stack depth grows.
Yes, I am using the mostly unmodified ec_user_example. I just adapted the
PDO setup for the
Hi all,
we are currently investigating spurious increments of the E_PUEC that happens about every 30 minutes (but not regularily). The E_PUEC is incremented on ALL slaves and simulatenously, also the E_FREC is incremente on all slaves and ports (e.g. P[0] on slave 1..n and P[1] on slave n-1 ...