Installation
Install the .modl file that matches your Ignition version through the gateway's Modules page.
Requirements
| Your gateway | File to install |
|---|---|
| Ignition 8.1.33 or newer | Signal-Processing-0.1.0-Ignition-8.1.modl |
| Ignition 8.3.3 or newer | Signal-Processing-0.1.0-Ignition-8.3.modl |
Download both from the 0.1.0 release on GitHub. The two files contain the same functions; Ignition 8.1 and 8.3 need separate builds.
Install
Both module files are signed with the same certificate. The first time, Ignition asks you to accept the Nedama Integrated Solutions certificate. Compare its thumbprint with this one before accepting:
SHA-1 thumbprint: 65:83:84:55:22:06:7C:CC:F9:C6:9B:C6:F3:C6:41:98:3A:28:BD:20
SHA-256: 1C:3C:66:C6:FE:02:27:85:63:29:9B:0F:E0:3B:F4:FA:11:EB:87:8F:21:C9:7D:92:3B:54:ED:59:97:B6:BE:DF
Ignition shows the SHA-1 thumbprint as pairs separated by spaces instead of colons.
- Ignition 8.1
- Ignition 8.3
- Open the gateway's web interface, go to Config > Modules and choose Install or Upgrade a Module.
- Select the
...-Ignition-8.1.modlfile and install it. - Accept the license (Apache 2.0).
- Ignition shows the module's certificate, with the warning "This certificate is self-signed". This is expected. See why it says self-signed.
- Compare the Thumbprint Ignition shows with the one above. If they differ, stop and do not install the file.
- Accept. The module appears as Signal Processing, version 0.1.0, license Free, state Running.
- Go to Platform > System > Modules, choose Install or Upgrade Module +, and select the
...-Ignition-8.3.modlfile. - Accept the license (Apache 2.0).
- Ignition 8.3 may list a self-signed module under Quarantined Modules, at the bottom of the page. If Signal Processing appears there, open its three-dot menu and resolve the certificate reason. See why it says self-signed.
- On the installed module, open the three-dot menu and choose View Certificate. Compare the Thumbprint with the one above. If they differ, stop.
The gateway log confirms it with the line Signal Processing started: system.signal functions are available.
Why it says "self-signed"
Ignition checks the signature of every module when it is installed, and refuses a file that has been changed since it was signed.
Signal Processing is signed with a certificate issued by Nedama Integrated Solutions to itself, not by a certificate authority. That is what "self-signed" means, and it is why Ignition shows the warning. The thumbprint is how you check that the certificate is ours.
Check it works
In the Designer, open the Script Console and run:
print system.signal.butter(4, 0.2)
It prints two lists of five numbers, the filter's b and a coefficients. Typing system.signal. in any script editor lists all 33 functions with their descriptions.
Upgrade
Install the newer .modl file the same way. Ignition replaces the old version in place; scripts keep working without changes.
Uninstall
Uninstall from the Modules page. Scripts that call system.signal then fail with AttributeError, so remove or guard those calls first.
Building from source
The source is on GitHub. With JDK 17 and Maven 3.8 or newer, mvn clean package builds unsigned modules for both versions. Unsigned modules install only on a development gateway set to allow them; for production, use the signed release files.