garageCube

[chuckinmap]

Hi there !

I followed the different steps suggested in the led tutorial with teensy/arduino to drive leds from Madmapper through "Artnet Usb" and got stuck with an issue i cannot overcome.

I 've tested the Arduino FastLED - Simple test sketch and everything is fine. The LEDs perfectly fade in and out but whenever I use the simple line sketch with the same settings (led number, led protocol, data pin), it does not drive anything. At start, i thought it could come from my Leonardo and bought a Teensy V4.0 but the same issue comes up.
Madmapper is able to see the usb device and i can select it and set it as mentioned in the tutorial.
However, whenever i create a fixture nothing happens. I currently word under the demo version (so it s supposed to have random cuts) but still not get any result when dmx data should be sent.

Anyone got stuck with the setting that could help me out ? This is actually my first time using madmapper with this kind of led feature.

Thanks a lot in advance,


Gear :
Macbook Pro 15" 2018 (usb A through usb c hub)
macOS Mojave
Madmapper Demo Version 3.7.4
Teensy v4.0
Led Strip WS2812B

[mad-matt]

Can you send a screenshot of you ArtNet => LED routing table ?
If you use the arduino patch we provide with the line "#define JUST_TEST_LEDS" uncommented

[chuckinmap]

hi Matt,

Sorry for the delay, i could not put hands on my stuff.
I made a few new tries on this led issues and i've noticed different things.

- when I open Madmapper Led device panel, the baudrate is different from the one in the Arduino code (230400 instead of 921600). I tried to change on the Madmapper side and on the Arduino Side but still get no answer from the led strip. Could it cause any issue ?
- I tested the Simple Line code with JUST_TEST_LEDS uncommented and it did not work until i introduced a slight delay at the end (delay(5)) to notice it actually fades in and out. I guess it might be because the Teensy 4 calculates too fast the loop so i cannot see it but i wanted to know wether it's a normal behaviour ?

I join the screenshot you asked and hope we'll find the solution for this issue.

[chuckinmap]

ps : i also noticed Madmapper kind of freezes when I modify some parameter in the Led device panel. I cannot quit the panel anymore.

[nicholasperillo]

Did you ever resolve this?

I'm having the exact same issue now with a Teensy 4.0. I can get simple test to work, and I can get "JUST_TEST_LEDS" to flash both strips just fine. However when I go into madmapper it freezes once it tries to send any data to the teensy.

I did get it to work periodically with one strip just fine but I have no idea how. I haven't been able to replicate it since.

[Simonluca]

I also have a similar but slightly different problem when connecting Teensy 4.0 and WS2812b to MadMapper.

I get the 60 pixel strip to run the "JUST_TEST_LEDS" almost fine as all LED blink as expected apart from the first one which stays on.

When I then go into MadMapper something really weird happens. There is a communication and the LED react to the inputs but they turn on when the fixture is on black and dim to the minimum (without actually going off) when is on white. Also they flicker heavily when they get inputs from MadMapper.

Furthermore when there is no input to the fixture from MM the LED stay on instead of going off.

Anyone with some wisdom to share?

[mad-matt]

Which FastLED library did you install ?

I never tried with teensy 4.0, I saw last year they released a fix for teensy 4: https://www.reddit.com/r/FastLED/commen ... 0_support/

[spectral_flux]

Hey,

I was having the same problem, 1 line sketch works fine, but with 2, nothing.

After some reading I think is a voltage problem. The 3.3v signal from teensy can't drive the 5v for two strips, 1 yes but 2 too much.
Not sure.

I bought that octoW2... thing adaptor that ups de signal to 5v to see if that would solve.

But I ll only get it in a few weeks.