Two things come to mind. You generally don't want your sACN source being a wifi node. Wifi is really meant for the wireless clients to be data consumers and the occasional request going back upstream. In general the devices pushing the data out should be on the wired network segment. This is even more important if the listeners are also on the wireless segment. The wireless client is not going to guaranteed enough timeslices to get all of its data out. If the traffic comes from the wired segment onto the wifi for listeners to consume, it will have a more even share of the airtime to get the data onto the airwaves.
Also something to keep in mind is that multicast works better over wireless than unicast. There's another recent thread where I go into detail on this topic (it was named something about choosing an access point)
However, the Ethernet chips used in the 682 controllers work better on unicast than multicast (unless there's been a recent 682 firmware change that I'm not aware of)
--Jon Chuchla--
Sent from my iPhone using Tapatalk
That TP Link 5-Port 10/100 Desktop Switch uses their "Green Ethernet Technology" which, according to them, " saves the power up to 68%".
I had all kinds of trouble with a couple "green switches". Until I put in a reliable, always on, I had no idea that the switch was making a mess of my efforts.
If you have a standard, non-green, to try, I would.
Ruppro wrote:JonLook at his 4th Picture, He has the FPP and Controllers connected on the Wired network. He is using WiFi only to manage FPP from his home network.
Good call. I must have read the OP wrong.
In that case, I'd agree with the others earlier, try a different switch.
--Jon Chuchla--
Sent from my iPhone using Tapatalk
Thanks for all the feedback everybody. I'm just my day started so I'll have a few hours after work to find a new "always on" switch and test it out. I'll let you know a bit later how it goes.
...I knew this was going to be confusing. A picture speaks a thousand words and all that! 😉
Cheers

