After quite a bit of thinking about it ... I've actually started working on an ADS Driver for Ignition. The connection is already working ... currently working on making the tag-information available to the Designer. As soon as that's done, the read/write stuff will follow.
The driver itself already works really well, just working on the task of integrating that into Ignition.
In order to get a feeling, if it's worth the effort of registering a company in order to be able to provide this plugin in the Ignition store, I'd love to know who would actually be willing to pay for such a plugin (and most probably more drivers that seem to be missing in Ignition).
I was going to say that I would be aiming for something round 300β¬/license for a pure-java ADS driver. Would that be a reasonable price-tag? If you're interested I'd also love to know how many licenses would you be needing.
(If you don't want to publicly disclose this, please send me a PM)
So by "Pure Java" you mean one that doesn't need the windows ADS DLL files like Kepware requires? Essentially meaning that it would work in docker containers, and anything that runs native Ignition?
I think there is a decent amount of interest, but Iβll caution you that:
Users overwhelmingly prefer βfirst partyβ modules, which in the case of drivers are effectively free because we include our drivers with a platform license.
A Beckhoff ADS driver is on our roadmap, but wonβt be in 8.3.0 nor the handful of releases after it. Not sure on timeline, but it wonβt be immediate.
For anyone, like me, who had no idea of what this topic is about:
The Automation Device Specification (ADS) is the communication protocol of TwinCAT. It enables the data exchange and the control of TwinCAT systems. ADS is media-independent and can communicate via serial or network connections.
I guess I'll have to pass on the ICC event. Would have been a perfect airing to my trip to apacheβs community over code conference in Minneapolis, where I'm flying home on the 15th.
But please ping me on LinkedIn⦠then I can ping you as soon as I'm ready. I definitely think some customers testing things and getting a big discount in return is definitely something I'm planning on doing.
Sorry about my delayed reply. Without going into deep setup details on a public form, we can always have a seperate call on this via our Account Manager.
Iβd say approx 2000 max points per site and we have atleast >20 sites of varying criticality per site. Ignition is in a HA setup but not active-active as I believe only active-standby is supported in 8.2. Setting up OPC in Beckhoff is also somewhat involved, not saying it canβt be conquered but a driver from yourselves avoids this as you guys figure this all out so to speak.
Is there a published upper and lower limit on IAβs implementation of the OPC UA subsystem? Also not sure what sort of overhead Java brings to this vrs say a memory safe compiled language such as Rust or just a compiled language such as C/C++. Again not trying to start a discussion on if Java is the right tool or notβ¦ it is what is used today by IA. Simply trying to understand how much overhead a JIT language with GC has. It maybe completely negligible. Thanks Kevin.
I applaud you for your hard work. What would be the implications of IA sports their own driver a some point as I think discussed here?
Also would you have your support model sorted out for end customers? What about your support with Beckhoff? I haven't seen much progress on their Java ADS code the last I checked.
Sorry if I am asking questions you already have answers for. Naturally if IA sports Beckhoff driver these support questions are fairly moot as it will come under their existing support model. They would also sort out things with Beckhoff as necessary is the assumption, if there are issues in the Java ADS kit. Thanks.