Forum Replies Created
-
Posts
-
Yes, remove the cardboard backing and you’ll see the microSD card. It’s a push/push card, so push it in and a spring will eject it out. Replacing the cardboard backing is optional unless you intend to wall hang the Game Frame.
I’m a huge fan of Asperite, which has versions for all platforms.
V2 software is designed for the Teensy LC and APA102C LEDs, the hardware used in the Game Frame redesign launched this year. Neopixels are incompatible with the IR Remote control, since they tie up the system interrupts, but if you want to try it out you can just change the LED type from APA102 to WS2812.
I used the version of Entropy installed with Teeensyduino.
Have you consulted the FAQ? 🙂
Arg!! I’m sorry to see this. Please send me an email (jeremy at this domain) and I’ll take care of you.
It’s a push/push. Push it in until it click and then release it. A spring should push it out far enough to very gently pull out.
Sorry for my absence. The level shifter is for the LEDs — and in the case of NeoPixels, it’s only for the data line (sorry I said clock and data). See here…
If you’re using a Teensy LC it has a level shifter built in for this exact purpose on the bottom row. It’s the pin that says “17 at VIN voltage.”
https://www.pjrc.com/teensy/teensyLC.html
I don’t know if this is the cause of your problem but it could be, and you’ll want to run the data through a level shifter to avoid problems regardless.
Yep, that’s strange! I would certainly try another microSD card just to rule that out. And double check your wiring — you’re using a level shifter for the clock & data lines? You could try adding Fastled.show(); to the top of loop and see if it persists identically. if it does, that would point to an SD read error. If not, it would point to an LED error.
Does that animation always distort on the same frame(s)? If so, looks like a SD read error. I’d try reformatting or using another microSD card.
I don’t know who Jermy is but I hope he weighs in. 😉 I have too much on my plate to jump on this project right now but I wish you the best!
1) Yes, pins 11 and 12. The SPI pins are hard wired so the library doesn’t expect you to assign them.
2) It does have a built-in RTC but not a crystal so you’d need to solder one to the appropriate through holes and mess with the Time code to use the Teensy RTC instead. It also won’t be nearly as accurate as the DS3231.
As for pins, the DS3231 communicates via I2C which, like SPI, is hard wired (SDA & SCL). EDIT: These are pins 18 & 19. That is the primary default I2C address.
The first Game Frame ran on Arduino Uno, not Teensy. I think you’re better off just getting NeoPixels working. It should be a simple matter of running the right Init.
Trying changing this line:
FastLED.addLeds<LED_TYPE, DATA_PIN, CLOCK_PIN, COLOR_ORDER>(leds, NUM_LEDS).setDither(0);To this:
LEDS.addLeds<WS2812,DATA_PIN,COLOR_ORDER>(leds,NUM_LEDS).setDither(0);Game Frame 2 uses APA102C LEDs (Adafruit calls them DotStar). Unfortunately NeoPixels are not compatible with the IR receiver since they tie up the system interrupts in order to meet their exact timing.
That said, you should be able to get it working with NeoPixels at the expense of the IR working properly. Look for a FastLED example using WS2812 to see the syntax on how to init them.
