Forum Replies Created
-
Posts
-
Sorry you hit a stumbling block, but glad you got it flashed. This is very odd. Did you buy this from eBoy? They’re assembling their own Wi-Fi Adapters, so it’s possible they tried to test yours and forgot to erase it. In general, they should definitely not be claimed already.
In any case, you said, “The doc says to claim your new device.” I don’t think my docs say this…? As for the device being in the drop down list, I think the only reason this was confusing was due to the weird turkey name. (Which, yes, I agree is awesome.) That said, the manager definitely needs to be cleaned up and improved visually. I’m just not a web guru by any stretch (in 1996 I was pretty good!). If anyone wants to take a stab, I’d happily update the file.
Christophe: Something is not being found on the SD card. Send me an email and I’ll send you a fresh file to unzip (jeremy at this domain).
schouten.ca, osmurf, and anyone else having similar problem, please email me and we’ll figure out a solution (jeremy at this domain).
Very interesting. So there is something inherent about the combination of some LED panels with Teensy that results in poor IR remote performance, but it’s solved using a Photon instead.
I just sent 10 Game Frame to Spain, and they ran a similar test for me using their stock components (Teensy) — all performed fine. So this remains a strange problem but you’ve been extremely helpful in narrowing down the cause. Thank you.
1) I haven’t tested anything other than 16×16, and at least one function is hard coded for that (getIndex). Actually, now that I think about it awhile back I did make a 32×32 version and I don’t think I changed more than getIndex… anyway, yes, it will require some small code changes.
2) As you know, V2 uses APA102 LEDs. These are not compatible with NeoPixels (WS2812). You can use the V2 source code but you’ll need to change the way the LEDs are initialized. It’s a simple change that others have done. However, this will mean the IR Remote control is not going to work and you’ll need to use physical buttons.
As for the Wi-Fi Adapter, I haven’t tried it with WS2812 but I imagine it would work with the same code change. The problem is the Photon development environment isn’t as straight forward as the Teensy/Arduino one. I’d stick with Teensy if I were you.
rolf: Any word on this? I’d love to know if swapping in the Teensy from the “good” Game Frame solves the remote problem in the problematic one.
schouten.ca: I suppose you could measure the voltage at the 3.3V pin on the rear, but that won’t tell you how much current it’s capable of providing.
Ah, foolishly I thought you meant the MENU button on the remote control. I just fixed the bug and it will be solved in the next firmware release.
Wow, news to me but looks like you’re right. I’ve signed up to publish their more complex applets. I’ll follow up here when I have access and try to reproduce yours. Sounds cool.
No, I’m sure it’s fine. The page is built into the firmware. I’m traveling today but I’ll take a look when I get home. Are you using the help page for anything in particular?
Yes, it’s definitely possible to fry the Teensy by inserting it wrong. The USB jack should be above the words USB on the circuit board. In any case the Teensy shouldn’t be hot so something is wrong, and because the Photon doesn’t work I’m afraid something happened to the Game Frame itself.
Send me an email (jeremy at this domain) and we’ll figure out some replacements.
