Hello Florian,
Thank you for your answer, but i can't understand you, you mean
--enable-sii-asign at configure time?, it's not an option of configure.
What do you mean?
Thank you for your time, regards
A 2014-05-21 18:07, Florian Pose escrigué:
Hello!
On Wed, May 21, 2014 at 04:21:58PM +020
Which time you use doesn't matter so much as long as it's stable and you get
minimal jitter.
With RTAI on startup Linux calculates a cpu frequency and calibrates the timer
against it. Between cold starts Linux will generally get the same value, but
if you do a soft restart it will often calcu
Hello!
On Wed, May 21, 2014 at 04:21:58PM +0200, Carlos Jiménez Leal wrote:
> Anyone have any idea what I can try?
Did you --enable-sii-assign?
--
Best regards,
Florian Pose
http://etherlab.org
___
etherlab-users mailing list
etherlab-users@etherlab.
Hello,
I tested with the latest version of the master but still fails in the
same way, I have activated the debug mode to get more traces.
[ 1306.804022] EtherCAT 0: Link state changed to DOWN.
[ 1306.808089] EtherCAT ERROR 0-1: Failed to receive AL state datagram:
Datagram error.
[ 1306.812
Interestingly, the master thinks it sends 5000 datagrams per second, as the
"ethercat master" command shows.
I took timestamps using debug level 2, and the scheduling is correct,
sometimes the delta between datagrams is 203us, but the next delta is 197
then. Average is a nice 200us.
It turned out
Hello Henry, thank you for your answer,
I am not using the latest version, I use the 1.5.2. I'll be down the
latest version and try again
Regards
A 2014-05-20 18:59, Henry Bausley escrigué:
Are you using the latest version of the stack? I believe this was
related to writing a 1 to address 0
