search

meduzapat / LEDSpicer

LEDSpicer a LED Animator and Controller for Linux
GNU General Public License v3.0
32 stars 13 forks source link

Random behavior with LED-WIZ on newer systems? #4

Closed gray-space closed 4 years ago

gray-space commented 4 years ago

Hi again,

I'm running into a new issue: when testing my control panel using ledspicerd -l. I get perfect behavior on older systems (my workbench system which is from 2006 or so, and a netbook from 2007). Tell it to turn on an output, and it turns it on,

However. I have problems when running LEDSpicer newer hardware: an UDOO x86 single-board system (which only has USB3) a recent Intel mini-ITX motherboard (which, according to Linux, has a single USB3 controller), and a 2017 HP laptrop. On all of these platforms, using -l to test individual outputs on the LED-WIZ will do random things when I type in a number to turn on an output. Most of the time, nothing happens. Sometimes, random LEDs would come on (even multiple LEDs at the same time). Other times, random LEDs that were on would turn off when I input a number.

Could these newer system (which all have newer, faster USB controllers) overwhelm the LED-WIZ? I noticed that RGBCommander has a setting that lets you throttle communications with the LED controller. I'm able to have RGBCommander turn on and off LEDs without any issues on these systems.

myoung34 commented 4 years ago

USB3 is backwards compatible with USB2

What board are you using from this list

I drive an ultimarc pacled64 from a lattepanda alpha (x86 and just as new or newer) from USB3 with no issues. The device is communicated over USB but powered by its own source, so there cant be any direct issues with speed or power over usb3

gray-space commented 4 years ago

I'm using a Led-Wiz (32 LEDs). It's just on USB power, rather than hooking up an external supply. I'd be surprised if that's the cause, though. That would mean an old netbook is able to supply enough current through its USB port for the Led-Wiz but not the brand new desktop Mini-ATX motherboard board with a 500 Watt power supply. I don't have more LEDs hooked up to the board than the Led-Wiz instructions say it can handle when powered via USB (500Ma).

I did find a reference in another open source interface project that talks about problems specifically with the Led-Wiz. It apparently can drop messages if they are sent at full USB speed. They added a configurable delay between sending messages to compensate. That matches what RGBCommander implies in its config example for the Led-Wiz. It has a higher suggested throttle setting than other controller boards.

myoung34 commented 4 years ago

First thing I would try is to power it over the onboard power connector in addition to USB and see if that changes anything

gray-space commented 4 years ago

Hi. Rather than tearing apart the cabinet again to run wires, I decided to just install Windows and set up LedBlinky. That's working fine, so I'll be using that solution.

meduzapat commented 4 years ago

anyway I will checking the ledwiz code.