well 2000 points per site should not be an issue (I’d even say per device I’ve also seen that much work ) I would assume that anything based on OPC-UA is more probably to reach it’s limits than using ADS/AMS.
Well the thing is: I generally have implemented many drivers vor various protocols. I’m currently hardening them for commercial use. I am planning on releasing quite a large number of plugins. Not only for Inductive Automation. I have seen a large number of industrial standard-products missing many such driver plugins (and others) … my plans are simply to close these gaps.
I did try doing this via consulting and open-source for about 8 years now … but that’s a thing I’ve given up on. I think the Automation industry will become comfortable with consuming consulting services shortly before I become a pensioner. So I’m generally stopping that path and continuing on one the industry knows: Buy a licence for a product and get commercial support for that. I will try to offer a better level of support than I have seen with the big players, but being a very small company, that will definitely not be 24/7 5 hour reaction time type of support.
Does that answer your questions? But yeah … I’m planning on licensing the driver on a per-ignition-instance basis … would be interesting to know how many of these you would be requiring. Also if you are willing to act as a beta-tester.
These things are entirely irrelevant. In all drivers the limiting factor is the PLC.
Also as an aside... Java is a memory-safe compiled language. It's garbage collection that can introduce some overhead when compared to languages like C/C++/Rust, but that doesn't matter here.
We’re currently beta testing it … also waiting for a TwinCat2 device being delivered to me for more testing. Need to find I guess one or two last issues. Looking forward to extending the Beta-Testing soon.
Ok … so the TC2 support seems to be working fine and we’re cleaning up the edges. Looking forward to bring this into the stores soon. And thanks to all Beta-Testers … your input has been super helpful.
New PLC is ordered, so I can add secured ADS support and currently implementing the tools for generating licenses … seems we’re closing in on the release date …
However, still a bit of beta-testing to do till I’m fully happy with it. So if anyone is interested in testing (you get a discount as a thank you from my side plus the more testers I have the sooner I’ll be releasing).
Yeah … well in PLC4X we had a working one for quite some time … but during the beta testing we quickly found out it’s missing a LOT of the special stuff needed for non-test-installations … and TC2 was quite a tough nut to crack as it generally doesn’t support all the stuff TC3 supports that needed to be emulated and it needed a lot of workarounds that you only run into once the PLC program reaches a certain size.