Protocol display

[HParks]

What would cause the IQ Tester not show MA Net 2 or sACN protocols when connected to a network.
The network has three MA2 consoles and two OnPC stations and two NPUs running v3.7.0.1 running sACN output to 26 Pathway nodes receiving sACN final.
The IP range of all of the devices on the VLAN running this configuration is 192.168.103.xxx

The system is running and performing well, except for a software bug in 3.7.0.1 that effects web remotes.
All of the nodes are displaying active dmx and outputting data.

Plugging the tester into this network displays active devices, but no protocol indicators display as active, even though the network is active with. MA Net and sACN.
Plugging the tester directly into one of the MA2 desk activates the MA Net protocol indicator.
With the desk in sACN stand alone on, the sACN protocol indicator is red
Hooking the tester to my laptop running sACNVIEW software shows sACN protocol as active, and all tester functions appear to work fine.

Thanks
Henry

[Rihards]

It seems like the IQTester is not receiving multicast packets from MANet2 and sACN when connected to the system through a network switch.
MANet2 detection depends on the IQTester being able to receive packets from the MA2 multicast groups.
Same for sACN if multicast addressing is used.

This is happening because the IQTester does not join all available multicast groups when connected to a network.

The protocol detector starts working when plugged directly into the console because there is no network switch between the console and the IQTester to filter out multicast packets for multicast groups that the IQTester has not joined.

Devices showed up in the Active Devices window because they had probably sent out a broadcast packet that does not get filtered by the network switch.

This problem should be fixed in the next firmware release [ 0.7 ]

Thank you for reporting this!

[Ryan.gottlieb]

I will add I am having the same issue, over (some) managed switches, the IQ tester does not see any protocols or sACN Universes. if I plug straight into the generating device (MA2) it see's everything happily. I will await .7 before testing further with our network team.

[HParks]

Unless I am not using the new features of the current software correctly, the Protocol Display still doesn't display either the MA-Net or sACN as active on any VLANs, which is the my primary method of distributing lighting data. If the tester is plugged directly into the source, it works fine. Most of my jobs involve multiple VLANS with multicast in full play. Currently my system is using Netgear 4250 series switches running over a 10g backbone in a redundant star topology. Each edge switch is receiving two 10g fiber runs, one from the primary core optical switch and the other from a backup core. The system runs well with no issues, except that the IQ Tester doesn't fully function in the systems environment. We run multiple VLANS carrying multiple departmental data and control systems, including guest lighting VLANS, which carry the sACN feeds for their acts. So as can be seen, I first posted the question on 05/14/2019. Your response explained the problem, with a reference to version 0.7 potentially having the problem solved.
Does the new software that I am running have a way around this issue, or is the fix due on the next release. ? I am always working in more complex network systems and having the Protocol display working would be of great help on fast signal routing problems. The DMX Receiving functions do work, displaying the multicast universe addresses and when selected showing active levels. So this has become a standard tool for tracking down gateway distribution issues. But for quick verification that the guest console is in session and talking on the correct VLAN would be appreciated.

Thanks
Henry