Netron Suggestions

[jmonson]

Having the view and test functions available on the web interface, and in CLU would be great

[Luke]

There should be an option to turn off the LED’s after a variable period on the nodes (specifically I have NS8’s and EN4’s in front of me). In a dark television environment where nodes might be hidden in sight of the camera, they’re VERY bright. Having the screen go dark while bright LEDs shine at your is useless. Thanks.

[Edward]

Hi @Luke

Welcome to the forum.

@Luke

There should be an option to turn off the LED’s after a variable period on the nodes (specifically I have NS8’s and EN4’s in front of me).

On Netron Ethernet to DMX gateways, such as EN4, the indicator LEDs can be switched off from their System > Device Settings page.

The brightness of the LEDs on the NS8 cannot be controlled.

Now that this thread has resurfaced, I’ll provide some replies, for any future readers of this thread…

@David_Henry

It would be really great if we could set up our presets so each preset on the wall stations called a single DMX channel at full (i.e. 8 buttons = DMX channels 1-8), and then in netron, set those DMX channels to trigger cues - BUT - only as “backup” to the primary Art-Net or sACN feed. As of right now, if we set this up, the wall station takes over the console output - not what we intended. This would give us the option to trigger cues with multiple universes (and across multiple netron nodes) from a simple DMX wall station.

#2 - If Netron built a well-priced wall station that could program to the netron cues and trigger them from the nodes, that would be awesome.

This is now possible through the new “Input Priority” feature, and BS10 for EN12i…

BS10-EU

@bjeffrey2492

Some form of hardware manager/Network selector.

PLS 2025 | NETRON FS16 Networkswitch

@bjeffrey2492

Would also love some way to trigger cues on all Netron nodes in the system simultaneously.

This could be done either using “Resend Ethernet”, or multiple simultaneous network triggers, for example from Companion.

@BartHornesch

A DMX splitter like the DMX10-5 with RDM capabilities would be verry nice to have. Right now it’s more cost efficient to just use another EN12 than to buy two RDM6XL or a single RDM10.

Pricing may have changed since this post, however the RDM10 is cheaper than an EN12.

@jmonson

Having the view and test functions available on the web interface, and in CLU would be great

This is not possible. However, this is one of the reasons “Resend Protocol” has been added to each port - you can send this data back out onto the universe, to see what the Netron port is receiving.

Edward

[Luke]

Here’s some more wishlist items:

#1 is fixing this huge bug where the NS8’s often don’t take their IGMP settings and fall off the radar. This is horrid.

The ability to change settings to multiple devices at once: If I have a couple dozen EN4’s on the network and want to change the DMX speed on all of them, I should be able to select them with radio boxes and then globally push changes to them

The ability to organize the nodes in the CLU by column (ie a user can choose by device type, by name, by IP, etc). Right now it seems by device type and then I’m not sure… I can’t tell what it’s doing. It’s almost alphabetical by name, but then some nodes seem out of line. It gets unwieldy when the device counts go up though.

A tally box in the CLU devices tab to show how many of each type are on the network (ie, 16 EN4’s, 6 NS8’s, etc) so a user can quickly tell if all the expected devices are online

It would be great to be able to change more settings before clicking save, since often saving requires a refresh of of the CLU (with IP’s etc). The way ETC’s Concert works, where you can change all sorts of stuff and then “sync” to the devices would be great.

The ability to export a csv of all the nodes and their settings as a reference

The abiliity to set an individual port(s) to broadcast (aka, to suspend snooping on a per-port basis within a VLAN) to accomodate random non-compliant devices without having to broadcast to all ports

[Edward]

Hi @Luke

I know we have discussed some of this via email, however for the benefit of others reading this thread, I will answer each point:

@Luke

#1 is fixing this huge bug where the NS8’s often don’t take their IGMP settings and fall off the radar.

This issue is logged as NETRON-155.

@Luke

The ability to change settings to multiple devices at once: If I have a couple dozen EN4’s on the network and want to change the DMX speed on all of them, I should be able to select them with radio boxes and then globally push changes to them

Batch configuration changes is logged as feature reference number NETCLU-11.

@Luke

The ability to organize the nodes in the CLU by column (ie a user can choose by device type, by name, by IP, etc). Right now it seems by device type and then I’m not sure… I can’t tell what it’s doing. It’s almost alphabetical by name, but then some nodes seem out of line. It gets unwieldy when the device counts go up though.

This will be implemented in a future revision of CLU.

@Luke

A tally box in the CLU devices tab to show how many of each type are on the network (ie, 16 EN4’s, 6 NS8’s, etc) so a user can quickly tell if all the expected devices are online

This is a nice idea. Logged as NETCLU-13.

@Luke

It would be great to be able to change more settings before clicking save, since often saving requires a refresh of of the CLU (with IP’s etc). The way ETC’s Concert works, where you can change all sorts of stuff and then “sync” to the devices would be great.

The only change that requires CLU to be refreshed, is if a device’s IP address is changed. In a future update, CLU should be able to refresh just that device with its new IP address, avoiding the need to initiate a fresh discovery.

@Luke

The ability to export a csv of all the nodes and their settings as a reference

Logged as NETCLU-10.

@Luke

The abiliity to set an individual port(s) to broadcast (aka, to suspend snooping on a per-port basis within a VLAN) to accomodate random non-compliant devices without having to broadcast to all ports

This is an interesting idea. We would need to investigate this further.

Please let me know if you have any questions.

Edward