Not able to send any info from xlights to any controllers

[keithsw1111]

127.0.0.1 is the inbuilt loop back adapter that just sends the data to itself. With wireless disabled what does ipconfig display.

[Phrog30]

Here's what I found.

With wireless enabled: "IP Address we are outputting data from: 10.219.213.26"--this is the shared apartment wireless network....
With wireless disabled: "IP Address we are outputting data from: 127.0.0.1"

I don't have a clue where the 127.0.0.1 IP address is coming from though...    I have my Ethernet setup to 192.168.10.110.   

Next, I will try connecting to my controllers with wireless disabled.   Gotta help my wife with something first.

Disable wireless and set your wired NIC to a static address that is on same subnet as controllers.

Sent from my Pixel using Tapatalk

[danj]

Keith:
Here's what ipconfig shows in the CMD screen with wireless disabled:

Ethernet adapter Ethernet:
   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :

Ethernet adapter Bluetooth Network Connection:
   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :

Tunnel adapter Teredo Tunneling Pseudo-Interface:
   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :

James:
I have my Ethernet adapter set to static IP 192.168.010.110--all my controllers are set to 192.168.010.xxx

THANKS!!!!!!!!

I connected all four controllers to my laptop.  I am able to ping them and manipulate them via their GUIs--turn on test patterns, change settings, etc.   I am able to send packet info and make lights do stuff with SACNView--checked several universes on every controller---all good--but nothing (including no packets sent to any controllers...) when running test or sequence signals from xlights.   I made sure I turned SACNView off before trying to flash lights with xlights...   With the wireless disabled, xlights reports it is outputting data from 192.168.010.110--my laptop's Ethernet static IP address.

[danj]

Sorry to bug everyone to death with my network woes....   I decided to try something--I reset all of my controllers as multicast in their GUIs (except F16...) and reset all of them in xlights as multicast.    I had to change the universe assignments of the E682s because they are only capable of receiving 7 universes in multicast...   After I made those changes, I was able to make lights flash with xlights in test and with sequences.   I was also able to keep the wireless enabled while generating test/sequence signals from xlights to my controllers.   When I used the "check sequence" tab, xlights is now choosing 192.168.010.110 (my static Ethernet IP address) as its "output from" IP address.

Does that help troubleshoot my network issues?  If forced to, I could make a bunch of channel changes and set everything up in multicast but I would really like to run in unicast; that allows me to use the E682s to their fullest capabilities and to keep the sockets/outputs as planned.

THANKS AGAIN!

[Gilrock]

Unicast vs Multicast shouldn't matter.  Were you restarting xLights after you made the network changes?

[danj]

Thanks Gil.  I don't think I closed/reopened when I changed from unicast to multicast.  I had closed/ reopened many other times, though...    After I changed the setup from unicast to multicast, XL then generated test & sequence output data.   I saw the data output via flashing lights hooked up to controllers (lights were doing what the sequence or test was driving....) and via SACNView--SACNView shows each universe that is receiving data from XL, SACNView, whatever...   As stated last night, I changed all my E682s to receive multicast data; F16 does not have any changes necessary regardless of unicast/multicast.

But...   Tonight I'll change back from multicast to unicast and I'll make sure I close/reopen XL before I try test/sequence signals...

[jnealand]

Trying to help a friend out with a large public display and having the same type of problem.  Can see all the controllers on the network using IP Scanner, can log into controllers and manipulate the settings, can turn lights on using Da_e131, but can not access lights using xlights 52 or53 or 4.3.02.  Very strange.

[Phrog30]

I wonder if something is blocking xlights, like virus scanner or something.

Sent from my Pixel using Tapatalk

[jnealand]

What would block xlights.  I have windows firewall off, I have only Windows defender on this laptop.  We can talk to the network, we can access the controllers via their web UI, we can turn lights on and off with da_e131.  This just does not make sense.  We have 3 different computers here and xlights does not work on any of them.

[Gilrock]

So Jim you didn't say anything about following the advice I've given here.  Did you run check sequence to see what IP address xLights says its going to use for output?  Did you shutoff wifi on the machines?

[Phrog30]

What would block xlights.

Antivirus could.  I'm not saying this is your problem, but it could stop a program from sending out packets.  You could still ping, you could still access via webpage.  Since you have the same problems on multiple computers, it sounds like something else.  But, it's very possible for an antivirus to block xlights.

James

[jnealand]

So Jim you didn't say anything about following the advice I've given here.  Did you run check sequence to see what IP address xLights says its going to use for output?  Did you shutoff wifi on the machines?

Sorry did not mention a lot of stuff that we tried. but we did run sequence checker.  We are not using wifi for anything.  This is a completely wired show.  We did turn wifi off on the computer connected to the show network, did not make any impact.  The network is all unicast with 9 alphapix controllers.  We only have one network cable to connect to the show network. 

We took another laptop and direct wired it to one controller.  Again we can access the web UI, make changes, etc.  but can not turn on lights with xlights.  We could turn lights on using da_e131 program.

[Phrog30]

Jim, do you have your computer to test with?

Sent from my Pixel using Tapatalk

[jnealand]

I had my computer direct connected to one controller, but could only get lights on with the da_e131 program and I could make lights come on although I don't know enough about that program to diagnose anything.  At the moment that controller is back on the show network and I am just my computer to search for answers on the internet.

[Gilrock]

Make sure Frame Sync is not enabled under Settings.  I would maybe install WireShark and see if you can see xLights sending packets when you turn on Output to Lights.  I've been doing all my testing from xLights as I don't move my files over to FPP till later.