[etherlab-users] Logging & Trigger functionality

[Florian Pose]

Hi,

On Mon, Mar 31, 2008 at 02:26:43PM +0200, Nureddin Bennett wrote:
> for a test rig i need to have a logging functionality with short
> latency trigger functionality. I am experimenting with a Opensuse box,
> realtime process and data logging service are running on the same box.
> However the results i get when triggering show different latency
> times.  Also, what i'd like to have is a new logging file for every
> time the trigger is activated, logging should continue until trigger
> is unset.

The DLS needs a short time to react on the trigger signal, because it
has to request the continuous data streams. Setting the trigger a few
seconds in advance will help.
> 
> I could switch on / off the trigger from within the simulink model
> using a constant. The value of the constant i changed through the
> testmanager interface. For some reason i didn't get it to start/stop
> when i used a Signal in the model as a trigger.

The DLS currently only supports triggering via an MSR parameter,
triggering via signals will be supported when the DLS will be ported to
the RTCom library (currently it has its own implementation of the MSR
protocol).

The approach we usually use is letting the dlsd run continuously (but
with a quota) and later exporting only the time ranges, that are
"interesting".  For that you also could use a signal to indicate, which
data are actually interesting. Moreover you won't have the problem to
set the trigger in advance.

-- 
Best regards,
Florian Pose

http://etherlab.org