@webdevbrian, on the Particle web IDE you will find the FastLED library for the (formerly) Spark Core. There are many libraries which will need to be updated for the Photon but those updates will include future proofing of code if done correctly. So you need to turn your WHOOPS into a WOOHO!!
Hey man – thank YOU for the reply! I’ll check this out. I’ve been caught with this guy “MDMA” and “Zach” censoring my posts, and you came through with a response … nay … and answer! You’re the man. HAPPY FRIDAY!
It definitely comes down to Dan with his FastLED library and converting it for photons, I understand that now (after including the library through the web IDE) – few issues but Dan is “the man”. So, anyone reading this – FastLED port is in the works – Dan is working hard on it I’m sure. I had a misunderstanding of how the photon works and assumed that I could use any arduino code with it - which is incorrect (I’m 100% certain others have this miscommunication as well).
Mods, please, don’t censor this post. Others need to see this. – @peekay123 – thank you for your replies!
Sadly, because of how low level and hardware direct that I go with FastLED, there’s little such thing as “future proofing” for me…
(I go straight for the juggular, er, direct hardware/io register access for things like SPI output and pin twiddling - makes for stupidly fast code, but makes it a bit less straightforward to port).
Given that the photon and spark are both STM32 devices though, I’m hoping the port consists of verifying that the i/o register layout is the same, defining new pin/port register mappings, and calling it good. It’s just a matter of getting the time to do it (I already have the Photons!)
Great concern @dgarcia! – I have a ‘few’ photons as well …
@dgarcia, the jugular is good! If not future proof then goof proof. The community is here to assist should you need any help
Any updates?
Try following the activity on GitHub, there are more updates, including a user contribute port that the FastLED authors are testing:
Yay! It got pushed earlier today!
If you are like me and wonder why it seems not to work - try clicking the ( i ) more info button and selecting the 3.1.4
So excited to not write crappy knock off code!