Re ethercat.
I had the opportunity to speak to Martin Rostan President of the Ethercat
Technology Group when he visited Australia a couple of years ago.
Here is the current situation I've been able to implement with collaboration by
others.
1. To be a member of the ETG (which is free) you need to be a company and
LinuxCNC is not.
2. The amazing foundational work by Sascha Ittner on the linuxCNC Ethercat
driver is now managed (with his consent) on a new extended repository by Scott
Laird at https://github.com/linuxcnc-ethercat/linuxcnc-ethercat
3. The etherlab master from IgH is now hosted on its own repository
https://gitlab.com/etherlab.org/ethercat
4. With Sascha's consent, Scott Laird's linuxcnc-ethercat driver is
distributed from the IgH repository.
5. Github workflows on the linuxcnc-ethercat repository automatically push
changes to the IgH Repository
7. The IgH Repository is installed by the Linuxcnc 2.9x ISO but no software is
installed because of Item 1 above.
I believe to finalise this we need to:
1. Migrate the Ethercat installation instructions in stickies on the forum
(mostly authored by me) to the LinuxCNC documentation
2. Include a script that installs the IgH repository and then installs the
linuxcnc-ethercat driver
I think this provides sufficient distance between linuxCNC and the ETG (who are
very supportive of LinuxCNC)
Please record this current state in your Meeting minutes
On 2025-12-09 00:32, Robert Schöftner <[email protected]> wrote:
> Am Montag, dem 08.12.2025 um 10:17 +0000 schrieb andy pugh:
> > On Sat, 6 Dec 2025 at 11:38, Steffen Möller via Emc-developers
> > <[email protected]> wrote:
> > >
> > >
> > > Hello again,
> > >
> > > We now have a small streak of "every second Sunday" video calls.
> > > And tomorrow, same venue, same time, is the next.
> >
> > Sorry, this completely slipped my mind last night. Can anyone
> > summarise what was discussed?
> >
>
> "We" was rene_dev, nico, steffen and me.
>
> We discussed brad collette's email how FreeCAD is using github and
> organizing developer meetings, followed by how to deal with github-
> issues in a more efficient way proceeded to do some janitorial github
> stuff like creating a 2.10 github-project and associated
> labels/workflow and discussed buildbot and CI issues (in our opinion we
> should mostly rely on github CI and not on any manual steps or
> infrastructure that isn't maintained).
>
> There was a discussion of what to put into 2.10 and how and if it is
> possible to help andypugh with "doing a release".
>
> There was a short mention of the QTVCP / QTPYVCP situation and if we
> should/could/should not add packages of qtpyvcp stuff to the linuxcnc
> debian repository.
>
> We also discussed some "big picture" stuff (maybe for version 3.0) and
> some pain points.
>
> some version 3 ideas that were mentioned:
>
> * build system, reorg of source code, possibly split the GUIs into own
> repositories.
> * overhaul of backplot widget
> * replace NML with something that is maintained and supported by
> currently relevant languages
> * make GUIs independent of HAL
> * port/integrate new tormach TP
>
> we also discussed ethercat, why it's not included (tradmark issues?)
> and if these reasons are valid, possibilty of a corporate sponsor for
> things like ethercat assoc membership.
>
> tormach pathpilot and some forks of linuxcnc were discussed briefly
> (opencn)
>
> that's about it. we try to meet again before christmas, if possible.
> this time it was only german-speaking people, it would be nice if more
> people could join. To that end somebody (steffen?) will post a doodle
> or equivalent some time soon to find a suitable date/time.
>
>
> --
> Robert Schöftner <[email protected]>
>
>
> _______________________________________________
> Emc-developers mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/emc-developers
_______________________________________________
Emc-developers mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/emc-developers
