any issue with compiling for x64 in visual studio? about libplctag HOT 4 CLOSED

Everything is explicit messaging still. The horribly delayed 2.0 series is being reworked to support completely different models such as implicit messaging, automatic reconnection, better retry behavior and better handling of some older PLCs that do not speak CIP well. It will also speak ModBus TCP after I finally come up for air and get a chance to hack that in. After CIP, ModBus looks like a walk in the park.

from libplctag.

I usually compile with 64-bit Windows when I use Windows. I also use exclusively 64-bit code when I use Linux, so the code is 64-bit clean.

from libplctag.

@kyle-github thanks for that info, that's great news.

An extra question I have is: this library/stack allows for read/write of tags in a host PLC, is the protocol handled as implicit messaging (constant read/write to tag names) or is it via explicit messaging (direct-messages) to named tags?

from the setup required, it looks (at first glance) to support the implicit messaging way of doing things, which is ideal for real-time control/feedback and is better than doing single direct messages of explicit table contents..

my company has a lightweight working stack for direct messaging (EthernetIP via CIP), but not the implicit continuous updating-tag-style communications

from libplctag.

Thankyou, that's all my questions for now. Closing my issue!

from libplctag.