defragster
08-11-2017, 06:59 PM
I and some other Teensy users saw a PIC based Kickstarter project that had a PCB footprint for UNO/Mega (https://www.kickstarter.com/projects/1897710270/retroball-build-it-yourself-pixel-fun-for-upto-fou-0/description) - and we asked about Teensy support. I hadn't yet backed so in reply to a message I got an ALPHA board from Australia to wire up - complete with smoked display cover that hides the white LED body and saves retinas seeing it up close.
1123411235
I found a fork of the Adafruit RGBmatrixPanel.h that supports Teensy 3.x's and as noted in the GitHub ReadMe (https://github.com/Defragster/RGB-matrix-Panel) shifted the Analogs used so the Teensy can use all four POTS where the UNO can only use two. So when I had working wiring I sent an XLS of the pin list to Brad and he marked up his PCB - then I asked for RTC battery and a second row of headers to allow using more of the Teensy and a way to set the pots to 3.3V to make it safe and expandable for all of the Teensy 3.x family. I found it not to work on T_LC with the pin signals as presented to the display - the color control slips to yellow?
Here's the result he just sent off to have a PCB made:
11236
Which will be a bit neater than this:
11237
I tested on T_3.1, 3.5 and 3.6 from 8 MHz to Overclock and it shows no signs of trouble - of course not surprisingly at 8 MHz the POT updates net about 1 second :) This uses the AdaFruit method of a timer to manually push out the batches of bits - not DMA - though at full speed Teensy will have plenty of CPU left. It uses 13 pins - plus 2 switches and 4 pots on the base T_3 footprint.
I had to cut the VIN<>VUSB of course as the Display is externally powered ( 2 A for 32x32 panel all white ). One thing I saw was when I powered the display from a powered USB HUB it worked but it was using the Teensy Programming USB GND for a return path and this would require pushing the button to program? I could tell something was amiss because my USB Charge Doctor power meter would go from 1.5 A to 0.9 A when I plugged in to program - and at the same time the display would brighten when the cable touched the USB connector. If some EE type has more info it might help others diagnose similar issues - when USB programming requires a button push is it a GND problem?
I emailed FrankB asking if I could port his T3TRIS code to this project. It seems it would make a good clock or IOT display.
Brad has a KS update with pics and movie almost ready I'll update with link as it may show stuff I left out here. if anyone is interested The KS is 230% funded and closes Sat, August 19 2017 9:29 PM PDT
1123411235
I found a fork of the Adafruit RGBmatrixPanel.h that supports Teensy 3.x's and as noted in the GitHub ReadMe (https://github.com/Defragster/RGB-matrix-Panel) shifted the Analogs used so the Teensy can use all four POTS where the UNO can only use two. So when I had working wiring I sent an XLS of the pin list to Brad and he marked up his PCB - then I asked for RTC battery and a second row of headers to allow using more of the Teensy and a way to set the pots to 3.3V to make it safe and expandable for all of the Teensy 3.x family. I found it not to work on T_LC with the pin signals as presented to the display - the color control slips to yellow?
Here's the result he just sent off to have a PCB made:
11236
Which will be a bit neater than this:
11237
I tested on T_3.1, 3.5 and 3.6 from 8 MHz to Overclock and it shows no signs of trouble - of course not surprisingly at 8 MHz the POT updates net about 1 second :) This uses the AdaFruit method of a timer to manually push out the batches of bits - not DMA - though at full speed Teensy will have plenty of CPU left. It uses 13 pins - plus 2 switches and 4 pots on the base T_3 footprint.
I had to cut the VIN<>VUSB of course as the Display is externally powered ( 2 A for 32x32 panel all white ). One thing I saw was when I powered the display from a powered USB HUB it worked but it was using the Teensy Programming USB GND for a return path and this would require pushing the button to program? I could tell something was amiss because my USB Charge Doctor power meter would go from 1.5 A to 0.9 A when I plugged in to program - and at the same time the display would brighten when the cable touched the USB connector. If some EE type has more info it might help others diagnose similar issues - when USB programming requires a button push is it a GND problem?
I emailed FrankB asking if I could port his T3TRIS code to this project. It seems it would make a good clock or IOT display.
Brad has a KS update with pics and movie almost ready I'll update with link as it may show stuff I left out here. if anyone is interested The KS is 230% funded and closes Sat, August 19 2017 9:29 PM PDT