On 8/10/2013 6:45 PM, andy pugh wrote:
> On 11 August 2013 00:32, Michael Haberler
> wrote:
>
>> Flatly, the idea of using locally generated serial numbers to tag a
>> commands in a shared memory buffer and hoping for no collisions to
>> occur was - to put it mildly - a lapse in design to start w
On Aug 10 2013 5:45 PM, andy pugh wrote:
> On 11 August 2013 00:32, Michael Haberler wrote:
>
>> Flatly, the idea of using locally generated serial numbers to tag a
>> commands in a shared memory buffer and hoping for no collisions to
>> occur was - to put it mildly - a lapse in design to start
On 11 August 2013 00:32, Michael Haberler wrote:
> Flatly, the idea of using locally generated serial numbers to tag a commands
> in a shared memory buffer and hoping for no collisions to occur was - to put
> it mildly - a lapse in design to start with.
I can think of several ways to make that
a few notes from the djungle (most of the following will only make sense to
folks which have tried to understand what task does):
I've transliterated the Python mockup into C++, and switched to protobuf
encoding - which at the time only means NML messages are tunneled via a
protobuf wrapper.
On 08/10/2013 09:55 AM, andy pugh wrote:
> On 7 August 2013 20:18, Sascha Ittner wrote:
>
>> The project home of the used EtherCAT master:
>> http://www.etherlab.org/de/ethercat/index.php
>
> There is an english version at: http://www.etherlab.org/en/ethercat/index.php
>
> I am not sure how we
On 7 August 2013 20:18, Sascha Ittner wrote:
> The project home of the used EtherCAT master:
> http://www.etherlab.org/de/ethercat/index.php
There is an english version at: http://www.etherlab.org/en/ethercat/index.php
I am not sure how we support things which require additional packages
like t
