Will Vixen work with Wled

A

AJVenti

Member
I have a WT32 ETH01 with Wled firmware. I am trying to get it to work with Vixen. I would like to use it as a e1.31 controller. I am so confused now that I don't know what I have done and not done. I was hoping that someone could point me in the right direction. This is my first time of building a controller. I was hoping to put espixelstick firmware on it, but I can't get it to load. Any suggestions would be greatly appreciated.
 
WLED should recognize e1.31 data when you send to it. Yes, Vixen can send to it.

Where would you prefer to start your troubleshooting? WLED or espixelstick install?
Can you connect to the Wled firmware on the wired ethernet?
 
AJVenti said:
I have a WT32 ETH01 with Wled firmware. I am trying to get it to work with Vixen. I would like to use it as a e1.31 controller. I am so confused now that I don't know what I have done and not done. I was hoping that someone could point me in the right direction. This is my first time of building a controller. I was hoping to put espixelstick firmware on it, but I can't get it to load. Any suggestions would be greatly appreciated.
Click to expand...
What is the issue? Can you post the log from the flashtool. Using the WT32 board is not as straightforward as using a node MCU based board. It will require you to manually reboot the WT32 multiple times with GPIO0 (zero) pulled low and then one last time with GPIO0 floating.

The other issue we see is a permissions issue when trying to run Flashtool on a MAC. Forkineye has a set of workarounds for that.
 
I got wled to load after trying all-day yesterday. What I can't do is get it to work with vixen. I was thinking that I would flash espixelstick firmware on to it but can't get it to work. I have a couple espixelsticks that I have used so I am familiar with it. Should I try to put the espixelstick firmware on it or will the wled firmware work just as well.
 
WLEd needs to be set up as E1.31. Create an E1.31 controller in vixen. Patch needed output channels to the controller. Create a test sequence and play it.
 
I tried to. I up the E1.31 as Mulitcast and Unicast with 10.0.0.103, not sure what universe to use I just picked 54. I am thinking there is something I need to do in wled.
 
You will need to tell wled what the starting universe is. I would start with unicast and universe 0. You can get fancy once it is working.
 
Thanks for the help. I was playing around trying to get it to work and I got that infamous smoke that tells you that you are paying attention.
 
Got a new Wt32 ETH01 board. Let's hope I don' blow this one. I got it to work on wifi but can't get it to work with ethernet connection.
 
I actually just had issues with flashing the WT32 ETH01 boards and here is what I figured out.

For WLED flash the device using the web-based flash tool, it's just easy this way. Be sure to choose the Ethernet Option.

https://install.wled.me/

1717811750197.png

OR

You can use the ESPixel Stick firmware, use the latest 4.0 beta 5 https://github.com/forkineye/ESPixelStick/releases.
The flash tool doesn't really work as it clears the EEPROM then tries to reboot the device, this always fails, so I use the following from command prompt to manually erase and then flash the firmware.

1717812279419.png


First run the flash tool and let it fail, be sure to fill out your options and choose your hardware ESP32 ETH01, Uncheck Reboot on AP failure.
This will build the firmware to manually flash.
Then run these from the folder you extract from the Pixel stick firmware. (Change your COM port and speeds to match your setup)

Code: 
bin\win32\python3\python bin\upload.py --chip esp32 --baud 115200 --port COM4 erase_flash

Unplug and replug in your USB flashing device so it resets then run

Code: 
bin\win32\python3\python bin\upload.py --chip esp32 --baud 115200 --port COM4 --before default_reset --after hard_reset write_flash -z 0x1000 firmware\esp32\esp32_wt32eth01-bootloader.bin 0x8000 firmware\esp32\esp32_wt32eth01-partitions.bin 0xe000 firmware\esp32\boot_app0.bin 0x10000 firmware\esp32\esp32_wt32eth01-app.bin 0x3B0000 firmware\filesystem.bin

If you do use the ESPixel stick firmware and are going to be using wired ethernet only, be sure the "Reboot on AP failure" options are unchecked, else you'll end up in a boot loop.

This should get you running with either WLED or ESPixel Stick v4 on your WT32 ETH01 device. I've got both firmware up and running on my controllers now.
 
Well, I have been playing with the Wled firmware with Vixen, I got a Wasatch Duo with Two outputs. I put 105 pixels on one output and 105 on the other the #1 output will work on all 105 pixels but the #2 output I don't get the first 60pixels to work, the ones after the 60 work. I am sure that there a setting I am missing.

Thanks
Tony
 

Attachments

  • Screenshot (1).jpg
    Screenshot (1).jpg
    130 KB · Views: 6
  • Screenshot (2).jpg
    Screenshot (2).jpg
    196 KB · Views: 6
Assuming a 512 universe size, the Vixen setup should be 512 instead of 315 on the first universe and then the 2nd one would be 118 instead of 315. If you are using 510 universe size you would just adjust it to 510 and 120.

This skip is because the controller is starting at a specific universe and using all the channels in sequence. You are skipping a block in the Vixen setup by skipping the remainder of universe 1.
 
What you say makes sense. Now the end of the #2 output is blinking a different color then the rest. do I need to make both props 170 pixels in Vixen? (170x3=510)
 

Attachments

  • Screenshot (1).jpg
    Screenshot (1).jpg
    117.1 KB · Views: 3
  • Screenshot (2).jpg
    Screenshot (2).jpg
    29.4 KB · Views: 4
The patching in Vixen should be continuous for the number of channels in each prop. Starting at whatever universe you setup in wLED. I think wLED defaults to 510 so make sure you set 510 for the size of the universe.
 
You must log in or register to reply here.
Back
Top