V2.3.0
======

This version 2.3.0 replaces the official 2.2.4 release.

- NEW

• Advanced networking features.
Next to the usual IP configuration settings of LumiNode, this release introduces a number of new features which
will greatly enhance network integration and offers users the flexibility to group and redirect network data
streams more efficiently and more securely.

• Introduction of “GigaCore” group functionality for ethernet ports and internal interfaces
- Groups (VLANs) including an ISL group (Trunk) can be assigned to ports and interfaces. This can be used
for example in scenario’s where data from different applications. in coexistence with the lighting data,
needs to be transported over the same network.
- Create and assign custom trunks that contain groups selected by the user.

• Introduction of advanced networking setting for a system interface with separate IP address
independent of in/output interface. This can be used for example to segregate Lighting control data from
IT related data (e.g. health & status monitoring).
- Optional “allow config” feature to grant/block access to the WUI from within the new system interface.

• Exclusively for LumiCore we offer a third unique advanced networking mode:
An advanced network setting for a split input and output interface each with their own IP settings.
This can be used for example to separate data into 2 different IP ranges for input and output.

• Kinet protocol support.
-KiNet protocol support has been introduced into this version and supports KiNet V1 or V2 on the output
and V2 on the input.
-The KiNet protocol, can be converted from/to other supported protocols (sACN, ArtNet, DMX).
-LumiNode will be discovered as a KiNet device in KiNet control software.

• Chinese language support
In the WUI and on the display.

• Timeout values
For valid DMX input of protocols (DMX, sACN, ArtNet, KiNET) timeout values can now be adjusted via API.
For further details on API http://<Node_IPadress>/api/doc.


- BUG FIXES

• A timing issue was fixed where on very rare occasions DMX was transmitted on a port before the RDM response was
received.

• A bug was resolved where the engine settings could get lost if a user modified settings on the LCD panel.

• A bug in the DMX port LED’s was resolved.

• A cosmetic issue where the redundant slave and sync button status was incorrectly shown, has been fixed.

• If the lock icon on the web interface is “on”, it was still possible to delete all engines or use the +/- buttons on the
top. This is no longer possible, the user will get an error when he attempts one of those actions.

• Less strict checking on the RDM transaction number so RDM transaction validity checking can be done with the
RDM controller.

• Issue fixed where RDM didn’t work when transmitting data over sACN, for example if: DMX + RDM → sACN + ArtRDM →
DMX + RDM.



- KNOWN ISSUES

• When upgrading from old firmware version 2.1.2 to version 2.3.0 there may be a rare occurrence where a manual
restart of the node is required after upgrading.