From: Wolfgang Grandegger <wg@domain.hid>
To: rolandtollenaar@domain.hid
Cc: Xenomai-help@domain.hid,
EML users <ethercatmaster-users@domain.hid>,
Jan Kiszka <jan.kiszka@domain.hid>,
rtnet-users <rtnet-users@domain.hid>
Subject: Re: [Xenomai-help] [Ethercatmaster-users] EML conflict with RTCAN? low_level_input framebuilding failed.
Date: Wed, 15 Aug 2007 12:30:28 +0200 [thread overview]
Message-ID: <46C2D5C4.2010407@domain.hid> (raw)
In-Reply-To: <46C2CC73.9080807@domain.hid>
Roland Tollenaar wrote:
> Hi,
>
> Some more interesting findings (no i-pipe trace yet though).
>
>> Hmm, this doesn't convince me yet. Such skews during startup may as well
>> be triggered by unusual load during runtime (non-RT activity or new RT
>> components). Did you put your system under adequate non-RT load as well
>> while measuring the outputs?
> Running latencytest with my application shows an average latency of
> about 40 and a max of 200ns. This was rather shocking so I turned off
> rtcan in my application. Now the max latecy is 60ns. Turn off EML and
> turn on rtcan, max latecy is 230ns. How is that for strange? But since I
> can see the scope output bobbing with 200ns during the latency test, I
> can also see that if I run my application without the latency test the
> huge max latency disappears entirely. Maybe it is time for the trace but
> then again I am still using CAN over the parallel port so will see what
> it does on a machine with a PCI CAN adaptor first. Because I think I
> know what happens: Due to the external loading the CAN recv interrupt
> triggers the Rx ISR briefly before the 1ms task period ends. Due to the
> priority of the ISR (huge debate over this) and its atomicness (if I
> remember correctly) the reading out of the slow hardware delays the
> start of the new task period.
>
> Just thought it was interesting to mention. Btw when the latency appears
> there are no overflow messages or anything like that which support the
> theory I have about the cause.
>
> Btw2 the 200ns latency spikes do not cause the scope to loose lock on
> the saw-tooth so whatever causes that problem is of a different nature
> still.
s/ns/us/ ?
Wolfgang.
next prev parent reply other threads:[~2007-08-15 10:30 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-13 9:45 [Xenomai-help] EML conflict with RTCAN? low_level_input framebuilding failed Roland Tollenaar
2007-08-13 11:41 ` Wolfgang Grandegger
2007-08-13 12:41 ` Roland Tollenaar
2007-08-13 13:03 ` Wolfgang Grandegger
2007-08-13 13:11 ` Roland Tollenaar
2007-08-13 14:00 ` Roland Tollenaar
2007-08-13 14:51 ` [Xenomai-help] [Ethercatmaster-users] " Jan Kiszka
2007-08-13 15:55 ` Roland Tollenaar
2007-08-13 16:57 ` Jan Kiszka
2007-08-13 17:40 ` Roland Tollenaar
2007-08-13 17:57 ` Jan Kiszka
2007-08-13 18:17 ` Roland Tollenaar
2007-08-13 18:30 ` Jan Kiszka
2007-08-14 13:56 ` Roland Tollenaar
2007-08-14 14:47 ` Klaas Gadeyne
2007-08-14 18:03 ` Roland Tollenaar
2007-08-14 19:17 ` Jan Kiszka
2007-08-15 6:11 ` Roland Tollenaar
2007-08-15 8:24 ` Jan Kiszka
2007-08-15 8:37 ` Roland Tollenaar
2007-08-15 9:50 ` Roland Tollenaar
2007-08-15 10:30 ` Wolfgang Grandegger [this message]
2007-08-15 10:30 ` Roland Tollenaar
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=46C2D5C4.2010407@domain.hid \
--to=wg@domain.hid \
--cc=Xenomai-help@domain.hid \
--cc=ethercatmaster-users@domain.hid \
--cc=jan.kiszka@domain.hid \
--cc=rolandtollenaar@domain.hid \
--cc=rtnet-users@domain.hid \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.