I am currently working hard on getting Apache IoTDB deployed on various platforms, that would benefit from a high performant time-series DB. As part of this, would I love to implement a Tag-Historian extension for IoTDB for Ignition. As IoTDB is implemented in Java, running it inside Ignition would also be an option.
As I am really new to Ignition (even if I did have contact with it at a previous employer) I would really appreciate some pointers to APIs, documentation regarding the development of a Tag-Historian for Ignition.
From what I've read here in the forum, the pretty unique way IoTDB stores data, would eliminate moste of the disadvantages of storing data in a tag-historian.
Expect significant refractors to the tag historian interfaces in 8.3.0. I wouldn't start a greenfield project until mid 2024, when we're expecting to have API changes finalized or at least close to so module authors can start developing against the new version of the platform.
guilty as charged ... yeah Apache PLC4X is my baby, indeed ... new big update coming pretty soon
Thanks for the pointers. They will definitely help a lot.
Right now there's one customer interested in this and I guess I'll whip up something and we can start learning with that ... once the major refactoring is done, I guess it makes sense to concentrate on building something "product-wise".
Will look into this tomorrow ... but a huge help .. thanks
Great, otherwise for waiting the new major release you can train with the SDK by adding a Profinet IO driver for Ignition .
Driver expose data with @Kevin.Herron Opcua Milo stack you are already known.
Regarding your links AT mazeyrat (As I seem to be not allowed to mention you ... yet) it seems that the last link would be interesting for an Apache PLC4X Adapter, right? I should probably check the licenses the required API modules are available under (Being an Apache project does restrict us a bit with what we are able to do)
so I've started inspecting things and I've setup a base module using the archetype. So my first steps were to build a module based on that, deploying it and then continuing from there on.
So as I didn't quite like doing manual steps in my builds, I whipped up a little maven plugin that uses the module-signer to sign the finished modules. However when installing the modules I got "signature verification failed" errors. When trying to install it the first time, Ignition asked me about the risk of using self signed modules, but I accepted. Unfortunately I seem to be unable to deploy the modules I built.