Chimeno
The serial terminal is not exported to the kernel device tree
(/dev/ttyX), as opposed to the ethernet terminal. You have to implement
a protocol around your stream within your application and deliver it to
the terminal as it requires. There is a 22 byte Tx and Rx buffer
augmented by a control and status word to tell the slave when valid data
is to be transmitted or to indicate that input data is available.
Although serial data is a stream which should blend well with the stream
orientated nature of EtherCAT, it is the difference in transmission
rates that forces you implement some kind of synchronization around your
data stream.
So to sum it up, it is not a remote TTY under /dev, but it allows you to
attach sensors or actuators connected via a serial cable to an EtherCAT bus.
- Richard
------------------------------------------------------------------------
Am 26/11/2020 um 08.50 schrieb Sebastien BLANCHET:
Hi,
Actually Serial-Over-EtherCAT works only in kernel mode with IgH
EtherCAT master.
The file "examples/tty/serial.c" calls several functions defined in
"include/ectty.h" and implemented in "tty/module.c"
These functions exist only in kernel mode.
If you try to call them in user mode, you will get undefined symbols for
ectty_create, ecctty_free, ectty_tx_data, ectty_rx_data
If you really want to use Serial-Over-EtherCAT you have to rewrite your
application to run in kernel mode.
Regards
---
Sebastien BLANCHET
Le 22/11/2020 à 21:50, Albert Chimeno garcia a écrit :
Hi, I am starting to use el6001, I tried the example that has igh
ethercat and adapted for the EL6001 and it works very well, I wonder
if anyone has been using it with linuxcnc-ethercat and ec-debianize, I
have undefined symbols "ectty_tx_data" I guess I need modify config
file for compilation, but can anyone give me a hint? thanks Chimeno
--
Etherlab-users mailing list
Etherlab-users@etherlab.org
https://lists.etherlab.org/mailman/listinfo/etherlab-users
