• State Not Answered
  • Date
    jonesbones
  • Date
  • Replies 1 reply
  • Subscribers 187 subscribers
  • Views 77 views
  • Users 0 members are here

Connecting to wLED controller with NOMAD over sACN

Hello,

I'm trying to get my NOMAD to connect to a wLED controller over sACN and just cannot seem to get anything to work.

Both are on the same network. I believe I have all the settings correct but when I patch in my pixels for my LED tape it just doesn't do anything.

We have an ION here onsite, but it is being used in a show currently and I don't have access to just mess around with it till Monday.

I'm going to try to use my ION console on Monday and see if I can get any results using that instead but figured I would post here and see if anyone had any suggestions.

For context I'm using:

LED tape - BTF Lighting WS2815

wLED controller - QuinLED-Dig-Quad

In the end we are trying to use this to do pixel control on led strips for a few sets of staircases using the ION for a show.

I just cannot for the life of me get any control of the LED strips using my NOMAD program

Parents
  • 0

    Hi jonesbones.

    I am no expert when it comes to WLED/Pixel tape controllers, but I think I can still help with some methodical troubleshooting. 

    Can you please explain how the LED controller is physically connected to the Console/Nomad PC over the network? Also, can you please also confirm that both the sACN source and the LED controller have similar IP addresses on the same subnet? 

    I can think of 3 issues that can lead to issues (from easiest to hardest to diagnose). 

    1. Your patch information inside eos is wrong or sending on a wrong universe. Please double-check which sACN universe the LED controller is trying to receive data from. For testing, you can just patch a full universe of dummy dimmers. Chan 1 thru thru 512 @ X/1. Then you can just run a Sin wave effect with Grouping 0 over the whole universe. This way, there should be some kind of output on the tape. You can confirm that your desk is sending out the values with a Laptop running sACNview, which is plugged into the same network. You can leave this running in the background while testing.

    2. The connection from the LED Controller to the LED tape is faulty. sACN is maybe received, but can not be seen as Output on the Tape. To rule this out, make sure you're able to control the LEDs directly via the controller (i believe there's a WebUI with in-built effects to test output).

    3. Your LED controller config is wrong and can't receive the sACN. I personally don't have any experience with wLED, but the online documentation seems helpful. (https://kno.wled.ge/interfaces/e1.31-dmx/) With the effect running in the background, changing config settings should give you instant feedback if stuff starts working. 

    Hope this helps.

Reply
  • 0

    Hi jonesbones.

    I am no expert when it comes to WLED/Pixel tape controllers, but I think I can still help with some methodical troubleshooting. 

    Can you please explain how the LED controller is physically connected to the Console/Nomad PC over the network? Also, can you please also confirm that both the sACN source and the LED controller have similar IP addresses on the same subnet? 

    I can think of 3 issues that can lead to issues (from easiest to hardest to diagnose). 

    1. Your patch information inside eos is wrong or sending on a wrong universe. Please double-check which sACN universe the LED controller is trying to receive data from. For testing, you can just patch a full universe of dummy dimmers. Chan 1 thru thru 512 @ X/1. Then you can just run a Sin wave effect with Grouping 0 over the whole universe. This way, there should be some kind of output on the tape. You can confirm that your desk is sending out the values with a Laptop running sACNview, which is plugged into the same network. You can leave this running in the background while testing.

    2. The connection from the LED Controller to the LED tape is faulty. sACN is maybe received, but can not be seen as Output on the Tape. To rule this out, make sure you're able to control the LEDs directly via the controller (i believe there's a WebUI with in-built effects to test output).

    3. Your LED controller config is wrong and can't receive the sACN. I personally don't have any experience with wLED, but the online documentation seems helpful. (https://kno.wled.ge/interfaces/e1.31-dmx/) With the effect running in the background, changing config settings should give you instant feedback if stuff starts working. 

    Hope this helps.

Children
No Data
Related

www.etcconnect.com