LUMINODE / LUMICORE
v2.8.1 Release notes.

Related products: LumiNode range, LumiCore range.


With this release, we will introduce new features and product improvements.
Note this firmware is required to use the enhanced LumiNode fixture takeover features in the upcoming Araneo Studio release.

New features:

It is now possible to use a record button to configure the startup buffer. With the record button, the current output of the process engine will be set in the startup
buffer configuration window. Next, these values can be modified and applied. This
improves the workflow; fields no longer need to be filled in manually.
Improved visualisation of selected inputs 

Merge mode status for Switch and Backup:
• Now a frame is displayed to highlight at selected input.
• Inputs that are not selected are visually connected with a dashed line
to the engine.
Input source status:
• The state of the input source is now displayed with a green input icon
(actively sending data).


Device name.
The device’s short name is now displayed in the top right corner of the web interface. This allows for easier identification when multiple browser tabs are opened.

Play inputs.
Can now be controlled in the control window from the ‘Play’ tab in the web interface.

RSTP.
LumiNode / LumiCore now support RSTP (Rapid Spanning Tree Protocol). RSTP is automatically enabled based on the network configuration and, when used on both network ports, provides redundant links with faster failover without any configuration needed.
RSTP is disabled when both ports use non-overlapping groups or trunks to avoid
a switch placing one link in a discarding state. In previous firmware, this required
disabling RLinkX (RSTP) on the switch; this is no longer necessary.
RSTP parameters are tuned to prefer paths through network switches (so the device
does not become the root bridge).


Product Improvements:
• DMX hold/continuous is now shown with a heartbeat blink, indicating the port is active but no new data is received (last values held).
• Hovering over a play input in the web interface will now show which Play scene/snapshot is active and which one is played next.
• Drag-and-drop now also copies and increments internal inputs, simplifying multi-engine setup.
• The process engine output monitor is now more responsive when monitoring outputs. An FPS counter was added as well.
• When multiple input groups are used with sACN on LumiCore, multicast registrations will now only be done only in those groups where they are needed instead of all input groups. This may reduce the multicast registrations in large networks.
• When overwriting a saved profile, the web interface now suggests the existing
profile name for faster updates.
• LumiNode / LumiCore now reply to mDNS queries in unicast mode for improved
discovery in large networks.
• The process engine status information and tooltips are now also accessible
when engine configuration has been locked with the lock icon.
• Profile exports will now have the `.lpp` file (Luminex Profile Package) extension.
This makes it easier to find profile files on your computer.
• The contact closure preview icon on LumiNode now also shows the open/closed
state of the contact closure.
• Various other smaller updates and improvements have been performed
throughout the web interface

Bug fixes:
• An issue has been resolved where the web interface would show ‘no active connection’ in certain situations where web authentication was enabled.
• An issue has been rectified where sometimes the wrong DMX port was removed from the process engine. [Note: a very specific order of operations was needed to trigger this].
• A bug has been fixed in LumiCore issue where the incorrect group could be used if different control sources were configured to use separate input groups but with the same universe.
• An issue has been resolved where the startup buffer would not be updated when using the CSV upload functionality in a custom process engine.
• With certain LLDP neighbours that didn’t provide select optional LLDP fields, the LLDP API would return a ‘500 internal error’. This bug is now resolved.