[etherlab-users] Making the LED stay on in the "user" example

[Jeroen Van den Keybus]

There's a watchdog that's kicked by every successful access to a Sync
Manager. If the dog expires, the slave leaves the Operational state.
Strictly speaking a slave will continue to accept inputs and provide
outputs in that case, but there's hardware in these devices that only
enables the outputs when the device is in the Operational state.

Be careful when designing a system: the safe output state is zero. Monitor
the slave operational state in your program so that your program, if it
starts working again, doesn't suddenly turn things back on.


J.


2014-02-20 19:10 GMT+01:00 Allan Brighton <Allan.Brighton at t-online.de>:

>
> Hi all,
>
> I'm new to EtherCat and EtherLab and I modified examples/user/main.c to
> work with the devices I have for testing: (EK1100, EL2202, EL1252, EL2252).
> Everything works and the LED I attached to the EL2202 turns on and off,
> however the code is using a timer and constantly setting the output value
> to 1 or 0 (on or off).
> Why can't you just set the value to 1 once and have the LED stay on? Even
> if I wait until the slave reaches the operational state, the LED just
> blinks once when set to 1,
> but doesn't stay on, unless the value is constantly updated.  What am I
> missing?
>
> Thanks,
> Allan
>
> _______________________________________________
> etherlab-users mailing list
> etherlab-users at etherlab.org
> http://lists.etherlab.org/mailman/listinfo/etherlab-users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.etherlab.org/pipermail/etherlab-users/attachments/20140220/21d0ed6f/attachment-0004.htm>