Recent content by loopmail

24 hours on and a new .bin file has been released for wled. flashed both my controllers and seems to be working well. the issue with the 170th pixel has gone and it's now having like a good little pixel. thanks again to everyone who offered help. it's much appreciated from a noob like me!

Absolute huge props to @Jorge Bolivar for his help. Explained a lot and found a few other errors for me. THanks, heaps mate. He filled in some info in my head and then a google from it turns out the problem is in nodeMCU/WLED as per...

I have changed wled as recommended, updated to latest xlights and restarted everything. Still no change. I'm happy with Teamviewer. I'll pm you my number and if you'd call me when you're happy to have a look, that would be fantastic.

I"m a complete noob to all this, so I don't know what I don't know and I don't know where to start looking. I will say any help is appreciated. I'm open to if people want to dial into my PC and look at the set up remotely?

Star is on it's own Node MCU and working fine. the window was presenting this behaviour before I added the star. Currently (as a previous suggestion from here) i have the arch as the start of universe 3 and use that as the reference point. The window is the first item in the chain. it's...

:) all good. i just wondered how it got to 230? but I can't point fingers, I couldn't count 4 sides of a square before. Any other suggestions? is it possible the controller is just braindead and a reflash might fix it?

From post #6 Top 46 Right 46 Bottom 46 Left 46 Arch 56 That's 240, i ran it through the calculator 3 times to check? how did you get 230?

Screen shots of wled led setup page

I can;t see anywhere in the wled portal to set it.

Can you give me a tip on how to do that? I can get the arch to start on universe 2, but I'm unsure of how to get section 4 to start on Universe 2, as its part of the window frame model?

ok, where have I done that? this si all new to me and if I've done that, I've not meant to. where would I look to find that?

That would be the end of universe 1? in the controller it was set as universe length of 2. and every pixel after that one works fine too? its just that one odd pixel.

Just tried that, no joy :( Same result.

240 PIxels. 1 node MCU. It all runs fine from WLED on the NodeMCU. The pixel with the problem is 169 (my error originally, sorry)

Attached is hopefully a helpful guide to the way I'm referencing things. Blue is side number and direction of data red is the pixel that's being bad.