Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

apa102 end frame adjustments #107

Closed
focalintent opened this issue Nov 30, 2014 · 11 comments

Comments

Projects
None yet
3 participants
@focalintent
Copy link
Member

commented Nov 30, 2014

See http://cpldcpu.wordpress.com/2014/11/30/understanding-the-apa102-superled - apa102 needs to send an end frame of n/2 led 1 bits.

@focalintent focalintent self-assigned this Nov 30, 2014

@focalintent focalintent added this to the FastLED 3.1 release milestone Nov 30, 2014

@jasoncoon

This comment has been minimized.

Copy link
Contributor

commented Jan 14, 2015

Could this be related to an issue I'm seeing with APA102, FastLED 3.1, Arduino 1.0.6, Teensyduino 1.20, Windows 8.1? I get 'scrambled' output on the FastLED 3.1 branch, but it looks correct on master. I'm on my mobile right now, but can post code shortly.

@focalintent

This comment has been minimized.

Copy link
Member Author

commented Jan 14, 2015

What hardware are you running with? And the missing end frame bits should only cause an issue with leds towards the end of your chain. The more important question is how many leds are you running? FastLED3.1 is currently willing to push driving the APA102's up to 24Mhz (I have a board here that can support that) - odds are you might need to scale back the data rate.

LEDS.addLeds<APA102,RGB,DATA_RATE_MHZ(12)>(leds, NUM_LEDS);
@jasoncoon

This comment has been minimized.

Copy link
Contributor

commented Jan 14, 2015

Ah sorry, Teensy 3.1 running at 96MHz, 63 LEDs. All of them are affected, not just the end.

@jasoncoon

This comment has been minimized.

Copy link
Contributor

commented Jan 14, 2015

#define LED_PIN     3
#define CLOCK_PIN   2
#define COLOR_ORDER GRB
#define CHIPSET     APA102
#define NUM_LEDS    63
...
FastLED.addLeds<CHIPSET, LED_PIN, CLOCK_PIN, BGR>(leds, NUM_LEDS);

Thanks in advance for the assistance, by the way. :)

@focalintent

This comment has been minimized.

Copy link
Member Author

commented Jan 14, 2015

Add the data rate change that I suggested:

FastLED.addLeds<CHIPSET, LED_PIN, CLOCK_PIN, BGR, DATA_RATE_MHZ(12)>(leds, NUM_LEDS);
@jasoncoon

This comment has been minimized.

Copy link
Contributor

commented Jan 14, 2015

Sorry, that did it, thanks!

@jar10623

This comment has been minimized.

Copy link

commented Jan 15, 2015

i have a Problem with fastLED since i changed from Arduino nanoV3 (all OK) to
https://github.com/JChristensen/mini1284

i build two to test but this is only a Problem with fastLED!

with https://github.com/cpldcpu/light_ws2812 is no problem, Timing ist well

see the Data Timing with m1284p & fastLED
m1284p_timing

with 33µs (m1284p) für one LED the ws2812b dosn't work, the 30µs is from m328p

@focalintent

This comment has been minimized.

Copy link
Member Author

commented Jan 15, 2015

Please open/track a separate issue. This has nothing to do with the apa102. Also the mega1284 is not a tested/supported platform for FastLED.

@jar10623

This comment has been minimized.

Copy link

commented Jan 15, 2015

Please open/track a separate issue.
? i don't understand

This has nothing to do with the apa102
OK but where can i told you?

Also the mega1284 is not a tested/supported platform for FastLED
thats a good reason to do nothing OMG

sorry that i live......

@focalintent

This comment has been minimized.

Copy link
Member Author

commented Jan 15, 2015

I mean go here: https://github.com/FastLED/FastLED/issues/new and enter a "new issue" - don't just comment on some other random issue.

I didn't say I was going to do nothing OMG. I asked you to make a new issue so that I could track it separately from this one. I was also explaining that the reason why it currently doesn't work on the mega1284 is because I have never tested it on the mega1284 - and there are different instruction and i/o timings on that chip than the mega328.

This issue is specifically for the APA102, and in fact, is about to be closed, as I've fixed the original issue referenced in here.

@focalintent

This comment has been minimized.

Copy link
Member Author

commented Jan 15, 2015

(For example - #121 )

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.