A maintenance release: a few enhancements, one security patch, an updated Java runtime, current Ignition and Cirrus Link versions, and some bug fixes.

If you use or plan to use groov hardware, you’ll want to be aware of this small but important firmware release.

Firmware 4.1.3 handles upkeep and a few small enhancements: a web server security patch, current Ignition and Cirrus Link versions, and fixes for hostname registration, backup restores, and USB port control.

It’s available for every groov EPIC and groov RIO device ever shipped!

Here's what's in it and what each item means for your application.

Updated software

Java Development Kit 17.0.19 on EPIC and RIO. Ignition runs on Java, so the JDK sits directly underneath your gateway.  

What it means for you: nothing to reconfigure. The JDK point release carries security and stability fixes for the runtime your Ignition gateway sits on.

Ignition and Ignition Edge 8.1.54/8.3.8, with Cirrus Link modules 4.0.35/5.0.3

What it means for you: the Cirrus Link modules are the MQTT modules that publish and subscribe to data (standard MQTT and MQTT Sparkplug). Keeping module versions current on the edge keeps them in step with the modern MQTT brokers on the other end. If you develop projects in Designer against a newer gateway, matching the Ignition version on your groov device keeps project imports predictable.

Two specific changes in this update:

• Ignition can now read files stored in the unsecured area of memory. If you exchange data through files, CSV logs, recipe files, or reports, your Ignition project can reach them where they already live instead of routing them through secured storage.
• On Ignition 8.3 and higher, a new Java Data Logging parameter in the gateway configuration file changes how Store and Forward handles multi-threading. Store and Forward is what buffers historian data when the link to your database drops and sends it when the link returns. If you have watched a device take a long time to catch up after a network outage, this parameter can be adjusted to improve performance.

Two more enhancements for groov RIO (and RIO EMU)

• On a groov RIO EMU, recovery from field-side power measurement device faults that cause quality code 8 errors is improved. If a meter on the field side faults, the energy monitoring point comes back more reliably.
• For shell users, the Debian package repository for groov RIO (and EMU) devices now includes the setcap command, matching what EPIC processors already had. If you run custom code that needs one privileged operation, like binding to port 502, you can grant that single capability instead of running the whole program as root.

Security

This release patches NGINX vulnerabilities in groov EPIC and RIO (KB91516). NGINX is the web server behind groov Manage and groov View.

What it means for you: if anything besides your own workstation can reach your device's web interface, a plant network, a jump box, or a firewall rule you opened for remote access, this patch closes off that path. Devices sitting on an isolated machine network are less exposed, but there's no reason to wait.  

Bug fixes

This release also fixes:

• mDNS and Bonjour hostnames registering only at boot (KB91345)
• the "Loading..." screen not refreshing after a restart finished (KB91449)
• on EPIC, no indication when a component in a backup file failed to restore (KB91455)
• on RIO, the USB port staying enabled after switching Enable USB to disabled (KB91532)

For the full descriptions, please see the release notes:

groov EPIC firmware release notes
groov RIO firmware release notes

Where to get it

Firmware 4.1.3 installs on every groov EPIC and groov RIO we've shipped, back to the first units, and it's free.

• EPIC PR1 and PR2: download from your MyOpto portal.
• RIO MM1, MM2, and EMU: download from the groov RIO module firmware page.

Questions about how an update affects your application? Talk to an Opto 22 engineer.