I will try it tommorrow.
thank you!
Note that restarting a device can also be accomplished in the gateway web interface simply by opening the device's settings (edit) and saving without any actual changes.
3 Likes
Hmmm. I released a bugfix back in May for a client, but forgot to post it here.
For Ignition v8.1+: v0.5.3.231501708
Fixed a regression in OPC item subscriptions.
2 Likes
Automation Professionals is pleased to announce a new production release of this module. The major change here is the removal of the Wicket-based configuration pages for JAR and JNI location overrides. That functionality has been moved to a pair of environment variables to simplify deployment. As a side effect, the need for Vision Client and Designer RPC was eliminated, greatly simplifying the code. (And greatly simplifying the conversion to v8.3.)
The documentation has been updated to reflect this change, and to add installation guidance for Ubuntu 24.04 LTS.
For Ignition v8.1.7+: v1.0.0.251601902
2 Likes
Automation Professionals is pleased to announce the production release of this module for Ignition v8.3: v1.0.0.252721937.
This is functionally identical to the corresponding v8.1 release above.
4 Likes
Good afternoon Mr. Turmel.
We’re encountering an error with previously working video streams after upgrading from 8.1.32 to 8.1.49.
The highly abbreviated error we’re getting in the gateway log is java.lang.NoClassDefFoundError: org/eclipse/jetty/server/HttpOutput, and I see from the ignition release notes for 8.1.49 has Upgraded Jetty from version `10.0.20` to `12.0.17`.
Am I correct in concluding that this module is not currently compatible with 8.1.49?
Ignition 8.1.49 has a major Jetty upgrade with api change.
Jetty is the internal Ignition webserver.
This is the cause of incompatibility.
Well, shoot. I'll have to make a release for 8.1.49+.
Looks like the same Jetty as in v8.3, so I can backport the fix from my v8.3 release.