On 01.03.22 23:35, Rod Webster wrote:
The reason why I put this on the agenda is that I observed that the debian
project uncovered a number of licenses which we had to include in our
copyright statement that deviated from the standard GPL licence. I was
quite surprised at this. I would defer
On Tuesday, March 1, 2022 4:20:42 PM EST Nicklas SB Karlsson wrote:
> Den 2022-03-01 kl. 21:39, skrev Bari:
> > On 3/1/22 14:25, Nicklas SB Karlsson wrote:
> >> Den 2022-03-01 kl. 21:17, skrev Bari:
> >>> On 3/1/22 13:20, Nicklas SB Karlsson wrote:
> Already have a simple implementation of an
The reason why I put this on the agenda is that I observed that the debian
project uncovered a number of licenses which we had to include in our
copyright statement that deviated from the standard GPL licence. I was
quite surprised at this. I would defer to Steffen on license issues and
Le mar. 1 mars 2022 à 22:22, Nicklas SB Karlsson a écrit :
>
> >
> > https://github.com/OpenEtherCATsociety/SOEM/blob/master/LICENSE
>
>
> Line below seems like a problem.
>
Exactly
___
Emc-developers mailing list
Den 2022-03-01 kl. 21:39, skrev Bari:
On 3/1/22 14:25, Nicklas SB Karlsson wrote:
Den 2022-03-01 kl. 21:17, skrev Bari:
On 3/1/22 13:20, Nicklas SB Karlsson wrote:
Already have a simple implementation of an Ethercat driver with
hardcoded configuration but read something about the license
Le mar. 1 mars 2022 à 21:40, Bari a écrit :
>
>
> https://github.com/OpenEtherCATsociety/SOEM/blob/master/LICENSE
I don't understand how the last sentences could be compatible with GPL?
>
___
Emc-developers mailing list
On 3/1/22 14:25, Nicklas SB Karlsson wrote:
Den 2022-03-01 kl. 21:17, skrev Bari:
On 3/1/22 13:20, Nicklas SB Karlsson wrote:
Already have a simple implementation of an Ethercat driver with
hardcoded configuration but read something about the license problem
and have kept it for myself.
Den 2022-03-01 kl. 21:17, skrev Bari:
On 3/1/22 13:20, Nicklas SB Karlsson wrote:
Already have a simple implementation of an Ethercat driver with
hardcoded configuration but read something about the license problem
and have kept it for myself.
If you developed this yourself without being
On 3/1/22 13:20, Nicklas SB Karlsson wrote:
Already have a simple implementation of an Ethercat driver with
hardcoded configuration but read something about the license problem
and have kept it for myself.
If you developed this yourself without being under an NDA or some
contract with
Le mar. 1 mars 2022 à 18:17, andy pugh a écrit :
>
> I am generally in favour of anything that makes LinuxCNC easier to use
> and more broadly applicable.
> So, I support bundling-in EtherCAT support, as long as we can be sure
> that nobody will be pointing their lawyers in our direction.
>
On 01.03.22 20:15, Nicklas SB Karlsson wrote:
Den 2022-03-01 kl. 13:27, skrev Rod Webster:
So I shared Steffen's post on the Ethercat section of the forum
calling for
technical volunteers. Maybe some of them are in this group already.
Le mar. 1 mars 2022 à 02:31, Chad Woitas a
écrit :
>
> Exploring a few other options as well for Ethercat.
>
What about those Raspberry Pi EtherCAT HAT and Arduino EtherCAT shields?
___
Emc-developers mailing list
Den 2022-02-28 kl. 15:47, skrev Steffen Möller:
Hello again,
On 28.02.22 14:28, andy pugh wrote:
On Mon, 28 Feb 2022 at 13:22, Steffen Möller
wrote:
Personally I know nothing about EtherCAT. I have always been a little
afraid of the licensing complexities mentioned here:
Den 2022-03-01 kl. 13:27, skrev Rod Webster:
So I shared Steffen's post on the Ethercat section of the forum calling for
technical volunteers. Maybe some of them are in this group already.
Hey Marc,
Be carefull with this. This code is running in Userspace while etherlabs
ethercat stack is running as Kernelmodule.
Ethernet Packets in Linux are transfered to the Userspace over a mechanism
called "Soft IRQ".
This will mess up any Realtime dependency especally on little ARMs like
On Tue, 1 Mar 2022 at 13:56, Steffen Möller wrote:
> *My personal anchors to the community are Seb, Jeff and Andy. I suggest
> that Rod sends whatever we come up with (if we come up with anything)
> directly, but I would like to first have a positive vote by one of them
> and "don't care"s or
Hi,
FYI, I got interested in the conversation and ended up finding this repository
on GitHub:
https://github.com/OpenEtherCATsociety/SOEM
The code for the master is released as a GNU General Public License version 2.
Regards,
Marc
-Original Message-
From: Rod Webster
Sent: March
> From my understanding Beckhoff is very open regarding the master (who
> even does not need a special hardware,
> when driven by an RTOS) and are very restrictive when it comes to the
>slave (where a ASIC / FPGA is needed in any case)
This was also my understanding when I read the licensing
So I shared Steffen's post on the Ethercat section of the forum calling for
technical volunteers. Maybe some of them are in this group already.
https://forum.linuxcnc.org/ethercat/45239-lets-get-ethercat-into-the-linuxcnc-distribution-need-technical-people-to-help
Lets hope the right people come
On 01.03.22 10:59, Les Newell wrote:
So once you've bought the controller, there is no other restriction.
As far as I can tell from their docs, that is the case. It's a pretty
sound business model.
I assume that royalty is 2x per axis, once for each end of the cable.
From what I can
On Tuesday, March 1, 2022 5:29:51 AM EST Rainer Stelzer wrote:
> Hi Gene,
>
> > So once you've bought the controller, there is no other restriction.
> > And I assume that royalty is 2x per axis, once for each end of the
> > cable.
> No, they don't charge twice.
> Part of marketing a
Hi Gene,
So once you've bought the controller, there is no other restriction. And
I assume that royalty is 2x per axis, once for each end of the cable.
No, they don't charge twice.
Part of marketing a Fieldbus-System is to make it widely accepted in the
industry, so Beckhoff
(and others like
So once you've bought the controller, there is no other restriction.
As far as I can tell from their docs, that is the case. It's a pretty
sound business model.
I assume that royalty is 2x per axis, once for each end of the cable.
From what I can tell, it would be one royalty per axis.
On Tuesday, March 1, 2022 4:27:21 AM EST Les Newell wrote:
> > I was not specificaly seeking the monetary cost, more the loss of
> > rights, which could be far more costly than the monetary cost. As
> > always, keep TANSTAAFL in mind.
>
> As far as Beckhoff are concerned this isn't a free lunch.
I was not specificaly seeking the monetary cost, more the loss of rights,
which could be far more costly than the monetary cost. As always, keep
TANSTAAFL in mind.
As far as Beckhoff are concerned this isn't a free lunch. Similar to
Mesa they make their money on the hardware. Supporting the
25 matches
Mail list logo
