Den 2022-03-02 kl. 18:31, skrev Arvid Brodin:
On 2022-03-02 18:20, Nicklas SB Karlsson wrote:
Den 2022-03-02 kl. 12:28, skrev Arvid Brodin:
1) Etherlab's ethercat master
(https://gitlab.com/etherlab.org/ethercat). This software
communicates with the ethernet layer and provides a programming api
for EtherCAT communications, as well as a command line utility to
interact with the bus. This software is completely independent from
LinuxCNC. The code is licensed under GPLv2, but as can be seen on
the linked gitlab site it has (unclear to me) restrictions on usage:
Looked at this before I started with SOEM. There was some kind of
problem, think maybe it was rtai kernel was needed.
Found the problem. Etherlab master i implemented as a kernel module,
most probably had problem to get this loaded.
Could not come up with any really good reason Ethercat master have to be
in a kernel module. Exclusive access to Ethernet port is a however most
probably a good idea, there is no good reason to send out ARP request or
any other similar traffic usually on a Ethernet network on the Ethercat
network though usually it does not interfer to much in a small network.
Ordinary real time thread should be good enough.
If there is no license issue get master into an ordinary real time
thread might be a good option. Time triggered sending of Ethernet
message is probably the ideal solution.
Nicklas Karlsson
_______________________________________________
Emc-users mailing list
Emc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-users