Forum Replies Created
-
Posts
-
It can’t find the clock BMP file. I have a feeling you purchased the SD files since the release of the new Game Frame (Teensy-based). Send me an email and I’ll get you the files for the Arduino version (jeremy at this domain).
I hope to ship it anywhere from my store, but I’m waiting to hear about on customs details from Particle. In the meantime, you can always make your own. Info on GitHub:
Excellent question. Currently the system ignores events (I call them Alerts internally) if an alert animation is currently playing, and starts listening for new ones when it finishes.
It’s possible to queue alerts but given the limited resources a better solution might be to send an event on alert completion to your server that tells it the display is ready for another command. What do you think?
Wow these are great ideas! I’m only on mobile right now but suffice to say just about everything you want can be done, and probably with the stock firmware I plan to ship. If not, I’ll work with you to add the features you need because this is exactly what I wanted to see.
For now take a look at the Particle REST API docs.
https://docs.particle.io/reference/api/
I have functions already exposed to play animations on demand. Also the clock can be setup to never play animations unless they are called as “alerts” from the Internet.
I would just create an animated GIF as your source and convert it to Game Frame using my script in the tools section. Just make sure it has a constant frame rate. Film strips are slightly faster since it doesn’t have to load new files for each frame.
Before connecting an SD the display should show an SD error message, and you can also hold down both MENU and NEXT buttons when powering on to show some test colors.
Any buttons should work. As for the resistors, it’s probably easiest to just use the Adafruit SD adapter here:
https://www.adafruit.com/product/254
…and connect its pins directly to the appropriate pins on the Uno.
I’m compiling with FastLED3.1.2pre. What version are you using?
By the way, as a workaround you can comment out breakoutLoop(); from loop() and get the version that works to fit into Flash, at least until you figure out what’s wrong.
Sounds like an initialization issue. Are the sketches the exact same? If not, have you tried the sketch that works with the library that fits into RAM?
Great, glad it worked. I’ve added a link to Teensyduino 1.22 on GitHub in case others run into the same trouble.
The code really pushes the Flash memory limit. Try Teensyduino v1.22 and see if that does the trick. If not, let me know the compile size for Teensy 3.1.
I’m perplexed. It sounds like something might be wrong with your clock ship — the black chip underneath the Teensy. Does anything look wrong with it? It sounds like the Teensy can read from it but can’t write to it properly.
Sorry for the trouble! Send me an email and we’ll figure out a replacement. (Jeremy at this domain).
Does it keep time after that (starting from 12:00)? What if you unplug and replug, does it remember the time?
