[etherlab-dev] ethercat master 1.5.1 - EoE & CoE in parallel

[Geller, Nir]

Hi,

I've been working with ethercat master 1.5.1 for a while now. So far I've used only CoE. I would like to start using the EoE functionality in parallel to CoE.
I managed to ping an ecat slave that supports EoE with MTU of 1500, but when trying to work with CoE and EoE altogether, I ran into a serious problem.

According to the implementation of the master and posts in etherlab-users and etherlab-dev I understand that a mail box protocol demultiplexer isn't implemented in ethercat master 1.5.1.

Is there a patch that implements such a thing on 1.5.1?
Did you already implement a demux in1.5.2? If so, has it been thoroughly tested and verified?
If not, Do you have a plan to do so?

Would you recommend to migrate to 1.5.2, or implement such functionality on the current code of 1.5.1?

Thanks a lot,

Nir.

[Gavin Lambert]

Post by Geller, Nir
According to the implementation of the master and posts in etherlab-users

and

Post by Geller, Nir
etherlab-dev I understand that a mail box protocol demultiplexer isn't
implemented in ethercat master 1.5.1.
Is there a patch that implements such a thing on 1.5.1?

I've previously sent you a link to my unofficial patchset. This includes a
mailbox demultiplexer and all sorts of other new features and other fixes.
You can choose to apply only a subset of patches if you wish, though you
might need to deal with conflicts and fuzz that way. But the latest version
applies against the default branch, which is newer than 1.5.2.

The patch repository also includes older versions of the patchset, some of
which were intended to apply against 1.5.2. But the older versions lack the
handy readme file, so you'd have to look at the list archives for more
details.

1.5.1 is sufficiently old now that you shouldn't be bothering with it. But
if you *really* want to, there's no particular reason why you couldn't
backport some of the patches. (Though if you' go ahead with that, then I
recommend looking at a prior version of the patchset, either from the
repository or the mailing list archives -- there were several patches
dropped because they were incorporated into default, but are still absent
from 1.5.2 and older.)

Post by Geller, Nir
Would you recommend to migrate to 1.5.2, or implement such functionality

on

Post by Geller, Nir
the current code of 1.5.1?

I would recommend migrating to default. Even 1.5.2 was a long long time
ago.