upgrade control

[charlie-68]

I have just up graded my controller. I'm having an issue with the setup. I can access the controller, and do testing from the controller's home page. IP address is 192.168.1.201; the computer's IP address is 192.168.1.50.
In XLights I have 16 channels configured with 1 thru 13 150 channels per universe, with the port 192.168.1.201.
The tree is set up for 12 strings of 50, the star is channel 13 50 nodes. I cannot get XLights to talk to my controller. Its looks like all the setup is OK. I hope that you can help me figure this out. Charlie J.

[babybear]

The first question we ask is the lights bulb Yellow. (Is the output to lights on, clicked)

[charlie-68]

Yes, the yellow power light is on.  I should have noted that my new controller is a HinksPix 16. I can control the lights thru the controller home page just fine.

[Phrog30]

If you are on a laptop turn wireless off just to make sure you are using the correct NIC.

Sent from my Pixel using Tapatalk

[keithsw1111]

Does test tab work?

[Gilrock]

Do you have multiple network adapters?  Do check sequence to see which adapter is being used to transmit data.

[charlie-68]

I'll answer all questions; I do not have any adapters, it is direct connected; no the test tab does not work; I'm using a separate desktop computer running windows 10. I did get the controller to work a little last nite meaning just first 4 out of 13 strings and very erratic. I'm thinking of installing Wireshark to check the outputs. It was suggested when I was talking to Joe Hinkle of Hinkspix. I have not checked on that yet. I may also try a network switch between the computer and the controller. Thanks  Charlie J.

[Gilrock]

You have a network adapter whether you knew it or not.

[Gilrock]

If you look under Network and Sharing Center on the side there is an option to "Change Adapter Settings".  If your using the onboard network interface it will probably be called "Local Area Connection".  So you can still do what I said and make sure it lists the IP address you believe is correct.

[Gilrock]

You can also open a command prompt and try to ping the controller.  If that doesn't work xLights won't be able to talk to it either.

[keithsw1111]

If necessary you can force which network adapter we use by using the settings menu force local ip setting but you must enter your computers IP address for the adapter that is connected to your controller.

[charlie-68]

Again some answers to your questions; when you asked about adapters I was thinking like a router but I did not follow. Yes the network is set up computer IP is 192.168.1.50; the controller is 192.168.1.201. I can ping the controller satisfactorily. I can assess the controller home page and test the lights from there. I cannot test from XLights or run a sequence. I have downloaded Wireshark and checked the source and destinations its source 192.168.1.50 destination is 192.168.1.201. I rechecked the net work adapter setting and it is 192.168.1.50.
.

[charlie-68]

A thought I just had will the gate way or the primary  DNS have any effects? The Hinkspix16 controller has like an IP address in those fields  which is 192.168.1.1? Does those areas need changed?

[Gilrock]

Best thing to do is show as many screenshots as possible of everything involved in the setup on both the controller and in xLights.  If you are sure xLights is sending the data by confirming with Wireshark then it has to be a configuration issue as to telling the controller which universes/channels to receive versus what xLights is sending.

[Phrog30]

Is it working at all? In one post you mentioned getting a few strings working but they were erratic. So, will anything work from xlights? I'm going to assume that not many people on this forum has a hinkspix. Most use a falcon. But you should include the setup of the controller anyways so we can see what you have. By the way, had you bought a falcon you would be running already.

Sent from my Pixel using Tapatalk