I'm just starting to explore the SDK. I'm fairly new to this type of development environment, although I consider myself to have a very good knowledge of Ignition itself.
I'm using a clone of ignition-module-tools to generate a brand-new project from scratch. From what I can tell, the latest branch on GitHub generates new projects compatible with Ignition 8.1.20.
In my case, I've configured my development environment to test against Ignition 8.3.x, since that's the version used by most of our customers. Unless I've missed some instructions, I haven't been able to get the generated project working with 8.3, even though the build succeeds and I'm able to install the resulting .modl file.
Is there a documented procedure somewhere that explains how to modify a newly generated project so that it can be used with Ignition 8.3?
I know that if I use the ignition-sdk-examples/perspective-component or ignition-sdk-examples/perspective-component-minimal examples, everything works correctly. At that point, I could simply modify one of those projects until it becomes equivalent to a freshly generated project from ignition-module-tools.
However, I'd prefer to start with something as clean as possible from the beginning.
The ignition-module-tools extra projects (the generator CLI and the templates themselves) haven't really been touched since they were initially created; mostly down to a lack of time to invest in them. I would personally start a new module today either using the approach Kathy outlined linked above or by editing from a working example.
Also my first experience with Claude Code. I suppose a Pro subscription is needed here? Any information on how to feed Claude with the content of this ignition-module-starter files? I'mnot sure what I have to do here.
I haven't had much luck with ignition-module-starter and Claude when I asked it to generate a project for me. However, I asked it to use an example from ignition-sdk-examples and generate a basic project based on perspective-component-minimal. I was able to rename the various resources and create a basic component. However, I still need to remove the default functionality (the banana animation). It's making progress...
In the end, through trial and error and with the help of AI, I finally managed to create a basic component under a company-specific category. I'll be able to use this as a foundation to implement the desired functionality.
The process also helped me gain a much better understanding of the component registration mechanism.
One thing I still need to figure out is how to specify our company name in the VENDOR NAME field. I haven't been able to find where or how this is configured.
If you're signing, it should be read from your cert. Theoretically it's possible to provide it without a cert, if the right key is present in the module.xml file, but our Gradle plugin doesn't appear to provide you any way to actually set that key.
This is the way. Don’t bother with the no signing option. Signing the module is easier than dealing with the hoops you have to jump through when unsigned.
A lot of the SDK guide seems to be obsolete. Maybe we will get an updated 8.3 guide in time for the Feb 2027 release.
