PDA

View Full Version : Teensy 3.1 & Teensyduino 1.17 Released



Paul
12-09-2013, 04:01 PM
Teensy 3.1 is now available. Full details here:

http://www.pjrc.com/teensy/teensy31.html

Edit: Teensyduino 1.17 has also been released, with support for Teensy 3.1, and all the improvements from rc1 (http://forum.pjrc.com/threads/24393-Teensyduino-1-17-Release-Candidate-1-Available), rc2 (http://forum.pjrc.com/threads/24570-Teensyduino-1-17-Release-Candidate-2-Available), and rc3 (http://forum.pjrc.com/threads/24616-Teensyduino-1-17-Release-Candidate-3-Available-%28Windows-Only%29).

Paul
12-09-2013, 04:17 PM
Well, OctoWS2811 will be able to run many more LEDs due to the increased RAM. I believe the new limit will be in the 3000 to 4000 range.

It might be possible to make a 12 channel version, but I currently have no plans to do so.

The extra DMA channels should allow things like simultaneously running the audio library (when it's published). I'd going to try making a giant LED spectrum analyzer.....

tetsuo
12-09-2013, 04:53 PM
Paul - sorry for deleting my post, especially since you took the time to reply to it! I regretted asking such an eager question only moments after your new product announcement, and it also occurred to me that you were stuck with a limit imposed by the number of PWM pins (of which there appear to be only 2 more on the T3.1).

In any case, this looks like a very exciting improvement on an already fantastic product. And thanks to the addition of gold, now with more "bling" or whatever the cool kids are calling it these days.

PaulStoffregen
12-09-2013, 05:08 PM
It's perfectly fine to ask questions. That's what the forum is for.

But on technical questions, I really do prefer to see questions with complete info and bug reports with code & details to reproduce the problem!

danieljohansson
12-09-2013, 05:22 PM
This is fantastic, congratulations!

It's very nice to see the upgrade to two ADC:s. I noticed there is still only 1 PDB timer. Is it only one of the ADC:s which get hardware triggering or will you be able to control both ADC:s from that one timer?

PaulStoffregen
12-09-2013, 05:27 PM
The PDB can trigger both ADCs, but both must at the same frequency. Each can have its own delay (eg, phase) within that frequency.

The ADCs can also be triggered by the PIT or FTM timers. Details buried within the huge manual....

Pedvide
12-09-2013, 05:58 PM
Wow! I'm very excited about the two ADCs!!
I've worked a lot in the ADC library and I can't wait to see how can I get the most out of the two converters. Do you have any ideas of how you'd like to implement it?

Constantin
12-09-2013, 06:59 PM
Full details here..
Hi Paul,

If you'd like me to make you a Eagle file of the bare chip, could you be so kind and post a schematic with the pin assignments on the chip itself?
I'll update my Eagle files to create a new entry for the assembled Teensy 3.1 board and try to get it to you this week.

MichaelMeissner
12-09-2013, 07:09 PM
It looks nice. This will open the door to using color displays. :cool:

Also, the 5v tolerance will be appreciated for the digital pins (though now, I try to buy stuff that is tolerant of both 3.3v and 5v).

potatotron
12-09-2013, 08:34 PM
Very cool new platform, congratulations.

Does the Mini54 change with this new platform or is it the same? I have a custom hardware design because I needed access to the EZ Port / JTAG pins but am using the PJRC Mini54 for programming. It looks like the Teensy 3.0 is discontinued for the 3.1, do I need to redesign for the new MK20 MCU so I can I keep buying the PJRC programmed Mini54?

PaulStoffregen
12-09-2013, 08:53 PM
Does the Mini54 change with this new platform or is it the same? I have a custom hardware design because I needed access to the EZ Port / JTAG pins but am using the PJRC Mini54 for programming. It looks like the Teensy 3.0 is discontinued for the 3.1, do I need to redesign for the new MK20 MCU so I can I keep buying the PJRC programmed Mini54?

The Mini54 we're shipping now (and have been for several weeks) will automatically detect either chip and "just work".

If you have old Mini54s, purchased before November, they'll probably only work with the '128 chip.

Trumpetto
12-09-2013, 09:46 PM
Sounds good. Is there any info about the audio library?

MichaelMeissner
12-09-2013, 10:18 PM
Paul, is the IDE still going to define __MK20DX128__, or will the various libraries need to test __MK20DX256__ as well as __MK20DX128__. I would hope that both would be set for Teensy 3.1.

MichaelMeissner
12-09-2013, 11:03 PM
Also, in looking at the table comparing Teensy 3.0 and 3.1 (http://www.pjrc.com/teensy/teensy31.html). It mentions the Teensy 3.0 had a 4 byte FIFO. I thought it was 8 byte.

I assume since there is no mention of improved FIFOs for RX2/TX2 and RX3/TX3 that there is no change to the FIFO (1 byte if memory serves). Do the Can/I2S buses have builtin FIFO?

PaulStoffregen
12-09-2013, 11:19 PM
There are a total of 3 FIFO on Teensy 3.0 and 5 FIFOs on Teensy 3.1.

Teensy 3.0 has an 8 byte FIFO on Serial1, a 4 word FIFO on SPI, and a 4 word FIFO on I2S.

Teensy 3.1 has 8 byte FIFOs on Serial1 and Serial2, a 4 word FIFO on SPI, an 8 word FIFO on I2S, and a 6 message FIFO on CAN (which takes 6 of the mailboxes when configured in FIFO mode).




is the IDE still going to define __MK20DX128__, or will the various libraries need to test __MK20DX256__ as well as __MK20DX128__


Libraries will need to check both. Or they can check defined(__arm__) && defined(CORE_TEENSY), as several already do.

I patched the libraries included with the Teensyduino installer to check both. I'll be submitting pull requests to others over the next couple days.

potatotron
12-09-2013, 11:53 PM
The Mini54 we're shipping now (and have been for several weeks) will automatically detect either chip and "just work".

If you have old Mini54s, purchased before November, they'll probably only work with the '128 chip.

Perfect, thanks.

MichaelMeissner
12-10-2013, 12:05 AM
As I was looking at side by side pictures, it looks hard to tell the two apart, other than remembering the Arm part number or seeing whether the contact are gold colored or tin colored. Hopefully in real life it will be easier for those of us who have multiple Teensy's already and may plan to buy new 3.1 boards in the future.

Dawnmist
12-10-2013, 12:26 AM
The new Teensy 3.1 looks really interesting. Are the GPIO port mappings for port A/B/C/D/E the same as they were on the Teensy 3.0? (i.e. as per the tables in this thread: Tutorial on digital I/O, ATMega PIN/PORT/DDR D/B registers vs. ARM GPIO_PDIR / _PDOR (http://forum.pjrc.com/threads/17532-Tutorial-on-digital-I-O-ATMega-PIN-PORT-DDR-D-B-registers-vs-ARM-GPIO_PDIR-_PDOR)). I'm assuming they are, but I figured I'd check...

virtualdave
12-10-2013, 02:48 AM
Awesome work, Paul!

stevech
12-10-2013, 02:54 AM
3.1.. great!
More RAM!
Two FIFO based UART channels.
D/A - good thing.

PaulStoffregen
12-10-2013, 09:08 AM
Are the GPIO port mappings for port A/B/C/D/E the same as they were on the Teensy 3.0?

Yes. The only pin that changes is A14 where Reset used to be. All the others are mapped exactly the same, for compatibility with 3.0.

MuShoo
12-10-2013, 10:39 AM
Well, this looks super sexy.

Constantin
12-10-2013, 11:33 AM
Well, this looks super sexy.

agreed… at least in the context of a chip / MCU board. :D The Teensy is once again pulling ahead of the crowd.

I presume the new DAC output is the elusive/exclusive pin 18? Just trying to get started here on a Teensy 3.1 Eagle libraries, both for the chip as well as the assembled part.

manitou
12-10-2013, 12:56 PM
Paul,
is there a version with header pins?

MichaelMeissner
12-10-2013, 01:17 PM
Paul,
is there a version with header pins?
http://www.pjrc.com/store/teensy31_pins.html

dgarcia42
12-10-2013, 05:56 PM
So glad to see the 3.1 out! Ordered 4 this morning, downloading the datasheet/manual, and I will start bringing the LED library around to it. (Been focusing on day job/personal projects for the past couple of months, life does that sometimes - but still using the teensy 3 for a lot of my stuff).

InterruptRequest
12-10-2013, 09:59 PM
Nobody commented on the change in rated speed from 48 MHz to 72 MHz. Is this in fact and if so does it mean that external interrupt latency will be much less ?

PaulStoffregen
12-10-2013, 10:06 PM
It actually makes very little difference, since both overclock quite well at 96 MHz.

However, the higher bandwidth flash and bigger cache do help some code run faster at 96 MHz.

manitou
12-11-2013, 12:28 PM
Re: teensy 3.1
is the IO clock still 48 MHz?
is crystal still NDK NX3225SA-16

PaulStoffregen
12-11-2013, 04:39 PM
Yes, same crystal, same I/O clock rate.

Teensyduino 1.17 does not support 72 MHz. I'm planning to add it soon, but this is more work than it might at first seem. When 72 MHz is used for the ARM code, the I/O clock will be 36 MHz.

InterruptRequest
12-11-2013, 05:14 PM
What is the current I/O clock with Teensy 3.0 and then with 3.1 ? Just want to determine how much difference there will be when 72 MHz is supported.

PaulStoffregen
12-11-2013, 05:43 PM
Both use 48 MHz I/O clock when the CPU runs at 48 or 96 MHz. When the CPU runs at 24 MHz, the I/O clock is 24 MHz. The clocks are exactly the same on 3.0 and 3.1.

PHaFTa
12-11-2013, 07:59 PM
Great news. The Teensy 3.1 energy consumption is quite the same than T3.0 ^^

Teensy 3.1 is powered with 3 AAA brand new batteries (4.7V):
24MHz: 15mA
48MHz: 23mA
96MHz: 32mA
250uA with DeepSleep (LowPower_Teensy3.h)

With 2 AAA batteries (3.1V), the values are the same, except 640uA with DeepSleep (same strangeness than T3.0)

PHaFTa
12-12-2013, 09:58 AM
Hi Paul,

does an updated version of the teensy_loader_cli (http://www.pjrc.com/teensy/loader_cli.html) with the option -mmcu=mk20dx256 for the Teensy 3.1 is planed?

Avenue33
12-12-2013, 12:08 PM
Paul:

That's great news!

Congratulations for the new release of the Teensy 3 :)

bmsi
12-13-2013, 12:56 AM
Just installed 1.17 rc3 and I do not see any references to Teensy 3.1 or MK20DX256VLH7. Expected to see at least a .ld file....

PaulStoffregen
12-13-2013, 01:16 AM
Install the final 1.17 (http://www.pjrc.com/teensy/td_download.html), not 1.17-rc3.

MichaelMeissner
12-13-2013, 01:19 AM
I upgraded to the 64-bit Linux 1.17 version, and I can select Teensy 3.1 if I run the IDE with a Teensy attached to the system. Given the 1.17rc3 release was announced before the Teensy 3.1 was announced, I imagine you have to go to the official 1.17 release.

renasis
12-13-2013, 04:22 AM
Paul,

Just got the new Teensy 3.1, wanted to give it a try. I loaded up the new Teensyduino 1.17, but I don't see 3.1 listed as a board, is this correct? Should I be using Teensy 3.0 to upload? Using Win 7 64 bit.

You don't need to uninstall anything before upgrading to the new version of Teensyduino, correct? I installed the 1.17(final) version in the same directory that I had 1.17 (rc3) in. That is the correct procedure, right?

Thanks,

-ren

Nantonos
12-13-2013, 07:12 AM
You don't need to uninstall anything before upgrading to the new version of Teensyduino, correct? I installed the 1.17(final) version in the same directory that I had 1.17 (rc3) in. That is the correct procedure, right?

Yes, its correct. It is possible to install successive versions of teensyduino into the same place, and the installer will let you know if it won't work (eg because the base version of Arduino is too low, or if some files are corrupted) by greying out the 'next' button. The installer does a bunch of detailed checks before allowing you to install.

If you are not seeing Teensy 3.1, be sure that the Arduino exe that you are running is in fact the one you just installed and not some older one installed someplace else (perhaps the registry has associated the .ino file extension with that old version?) by directly running Arduino.exe from the directory you just updated.

PaulStoffregen
12-13-2013, 09:46 AM
I loaded up the new Teensyduino 1.17, but I don't see 3.1 listed as a board, is this correct?

When you run Arduino and click Tools > Boards, you should see this:

1191
(click for full size)

If Teensy 3.1 does not appear (as shown in this screenshot), then you simply have not correctly installed Teensyduino 1.17.




You don't need to uninstall anything before upgrading to the new version of Teensyduino, correct?


Usually the Teensyduino installer can install into a copy of Arduino that already has an older version of Teensyduino. If it can't (because some file within that copy of Arduino has changed in any way the installer can't recognize), the "Next" button will not enable. When the installer can't work, you will know, because you will not be able to complete the installation. In those cases, you'll need a fresh copy of Arduino 1.0.5.


However, you MUST select the copy of Arduino you're using (which is almost certainly where things have gone wrong). Here's another screenshot.

1192



I installed the 1.17(final) version in the same directory that I had 1.17 (rc3) in. That is the correct procedure, right?


Obviously something wasn't correct, since you're not seeing Teensy 3.1 in the Tools > Boards menu!

When you say "installed ... in the same directory", what precisely does that mean? If you simply put the Teensyduino.exe in some folder on your hard drive, then no. You must run the installer, and when you get to the step shown in the screenshot above, you must select the location of Arduino.

If you have more than one copy of Arduino on your computer, you must select the one you're actually using. For example, if you have a copy in C:\arduino-1.0.5 and also a copy in your "Downloads" folder, and you select the one in C:\arduino-1.0.5 while running the installer, but then double click the one in Downloads, then of course you won't see any results, because that other copy wasn't changed by the installer. It only writes Teensy support into the copy of Arduino you select.

This problem is unfortunately pretty common on Windows, partly because the modern trend in Windows is to show these virtual locations in many modern Windows programs. It's pretty easy to unknowingly have more than 1 copy of Arduino on your hard drive, because Windows doesn't always make it clear where you're actually running program from and where files are actually installed.


If you're totally stuck, I'd recommend you simply download a fresh copy of the Arduino 1.0.5 zip file (not the installer) from www.arduino.cc and extract it to a known location on your computer. The key point is to remember where you on your computer, the precise folder location, where you extracted the zip file. Before extracting, make sure you do NOT have a prior copy, so you're certain this is a freshly extracted copy. Then run the installer, and carefully select that location. After installation, run Arduino, again being careful to navigate to that location. Simply clicking any existing shortcuts might actually run another previously installed copy of Arduino, so please be careful to use the copy which is definitely in the same location that you selected while running the Teensyduino installer.

manitou
12-13-2013, 10:03 AM
My teensy 3.1 arrived and is working. Several little benchmarks are noticably faster (more later).

Looking at analog.c in 1.17, it appears that pins 38 and 39 are still temperature and vref. I think pin 38 is OK, though i need to recalibrate,
but pin 39 seems to be jumping around. on teensy 3.0, this sketch would give me 3300 mv, but on 3.1 it's jumping around 8500 ?


void setup() {
analogReference(EXTERNAL);
analogReadResolution(12);
analogReadAveraging(32);
}

void loop() {
int mv;
mv = 1200 * 4096 /analogRead(39);
Serial.println(mv);
delay(2000);
}

jdc928
12-13-2013, 12:08 PM
Did I just read that second post correctly???? 3000 - 4000 RGB LEDS?

If so, This just made my morning!!!!! I'm currently working on a project involving 20,000+ RGB LEDs (yep 20,000+ ws2812's on a single robot performance suit). We were originally using one teensy per 1000 RGBs so this is going to be a HUGE improvement. Flat out amazing! (well... unless your Paul and you just cut the amount of Teensy boards I'll be buying for this project by 2/3 ;) . Don't worry, there's plenty of projects I'll be using Teensy 3.X's on )

I said it earlier and I'll say it again. Teensy's are hands down my favorite microcontroller in existence. Thank you!

fnj
12-13-2013, 02:13 PM
Bravo on the 3.1, Paul! Evolutionary but very cool.

PaulStoffregen
12-13-2013, 05:56 PM
Did I just read that second post correctly???? 3000 - 4000 RGB LEDS?

Yes, 4000 RGB LEDs.

The 1000 recommendation was based on allocating at least the 3K frame buffer in the lower 8K of memory on Teensy 3.0. That lower half of the RAM is optimized for DMA, with a separate bus. The USB stack also allocates about 3K of buffers in the lower half. The upper half contains the stack holding local variables, function return addresses, and interrupt context. RAM size was the limiting factor.

Teensy 3.1 has 64K of RAM. The lower half is now 32K, with the USB stack leaving about 29K free. Both the frame buffer and drawing buffer can easily fit in the lower half of RAM.

4000 LEDs means about 500 on each pin. 500 LEDs at 30 us each will make the update time approx 15 ms, which gets pretty close to the limit for achieving 60 Hz progress refresh. You might be able to use 8000 if 30 Hz refresh is ok. That would allocate 48K of RAM for the 2 buffers, so I would definitely not try to push much farther than 8000. If you do connect so many to one Teensy 3.1, please post photos!!!

manitou
12-13-2013, 06:08 PM
teensy 3.1 is faster than 3.0 on some simple benchmarks



UNO DUE maple teensy3 3.1 beagle raspberry
MHz 16 84 72 96 96 720 700
fibo(ms) 927 98 104 82 63 8 10
fft(ms) - 8 8 10 4 .4 .5
daxpy(mflops) .1 .6 .5 .4 .6 13 67
MD5(KBs) 48 2226 2124 2133 3657 10965 8103

Also some simple SysTick timings of ISR overhead are faster on 3.1. see
https://github.com/manitou48/DUEZoo/blob/master/isrperf.txt

The only anomaly so far is with a memory-to-memory DMA test. It runs slower on 3.1 than 3.0? But memcpy() runs faster on 3.1 than 3.0. (Paul noted Flash was 2x faster with bigger cache, so I assume SRAM is no faster ?). Here are DMA results
https://github.com/manitou48/DUEZoo/blob/master/mem2mem.txt

and sketch
https://github.com/manitou48/teensy3/blob/master/mem2mem.pde

manitou
12-14-2013, 01:41 PM
Wire.h won't compile with board teensy 3.1, OK with teensy 3.0 ??? e.g. Example/DS1307RTC/ReadTest

DS1307RTC/DS1307RTC.cpp.o: In function `DS1307RTC::read(tmElements_t&)':
/home/linux/arduino-1.0.5/libraries/DS1307RTC/DS1307RTC.cpp:57: undefined reference to `TwoWire::beginTransmission(int)'
...

me thinks Wire.h and Wire.cpp should read
#if defined(__MK20DX128__) || defined(__MK20DX256__)

Markus_L811
12-14-2013, 01:49 PM
Bravo on the 3.1, Paul! Evolutionary but very cool.

Damn, I just looked a few moments away and bamm there is an new one, and above the last one. Incredible

renasis
12-15-2013, 05:42 PM
Paul,

I am pretty sure that I installed Teensyduino 17(final) in the same directory ..\Documents\Arduino 1.05 as 17 (r.c. 3). However, I am not certain whether I had the IDE closed or not. I tried re-installing Teensyduino 17, but the board drop down in the IDE had an empty spot(where Teensy 3.1 is showing your attachment). I did as you advised, re-installed Arduino IDE 1.05, re-installed Teensyduino 17(final), everything is working fine now. Thanks for your help. Congrats on the new board!

-ren

ChrisH
12-16-2013, 06:28 PM
Hi Paul,

I have been enjoying using the Teensy 3 modules I purchased; thanks for making these devices available to us! I ordered 2 3.1's and was trying to get them running but suffered the same issues as other folks in that 3.1 did not appear as a board type. My version of Arduino 1.05 was installed in C:/Program Files/Arduino and all sorts of re-installing, deleting etc of both 1.05 and Teensyduino 17 final did not put board type 3.1 on the menu. Looking at files I could see that Teensyduino was putting the correct board file into C:/Program Files/Arduino/hardware/teensy. Now, I have mydocuments/arduino with an old version of the IDE in it which I use for sketches in order to avoid the administrator issues with program files, and preferences sketches points at this. I put a copy of the boards file in here and then 3.1 appeared on the menu, but of course the core file was then missing. So what appears to be going on is that the folder pointed to in preferences for sketches is not searching their first for all files, so I need to tidy that up also. This may help other users to get rid of stray copies of the old IDE.

I have been using a copy of teensyduino 17 (final) that I downloaded a few days ago. Yesterday and today though Norton started to block downloads, so you probably need to look at this.

Chris

Filename: teensyduino.exe
Threat name: Suspicious.Cloud.7.EP
Full Path: c:\users\chris\downloads\teensyduino.exe

____________________________

Details
Unknown Community Usage,* Unknown Age,* Risk High

Origin
Downloaded from*http://www.pjrc.com/teensy/td_117/teensyduino.exe

Activity
Actions performed: Actions performed: 1

____________________________


High
This file risk is high.

Threat type: Heuristic Virus. Detection of a threat based on malware heuristics.

stevech
12-17-2013, 02:35 AM
re "Yesterday and today though Norton started to block downloads, so you probably need to look at this."
Long ago I switched to Microsoft Security Essentials (MSE) for security software. Free. Good. Unobtrusive.
I rationalize that MS has at least as much, or more, incentive to protect Win 7 for me than do Norton $ or McAffe $ et al.

Jp3141
12-17-2013, 03:55 AM
On my Mac, I have two user accounts (say 'home' and 'work'). While logged in as 'work', Teensyduino wouldn't install (error like 'teensyduino error unable to write file contents/resources)'. It turns out that I must have installed Arduino as 'home' and when I switched to that user, it installed fine.

Is that expected ? Are the Arduino files 'owned' by one user ?

Nantonos
12-17-2013, 12:06 PM
Threat type: Heuristic Virus. Detection of a threat based on malware heuristics.

Yes, the Teesyduino modifies executable files. That means Norton "guesses" it might be a virus. It isn't.

PaulStoffregen
12-17-2013, 02:46 PM
The Windows and Linux installers are compressed with UPX.

http://upx.sourceforge.net/

Apparently Norton and others occasionally mistake the UPX self-decompression for malware.

Of course, Nantonos is absolutely correct, anti-virus heuristics assume no program should ever modify another program, but that's exactly what the Teensyduino installer does as it adds Teensy support into Arduino.

The installer never uses network connections, so you can disconnect from the internet, and temporarily disable anti-virus while running the installer. Be sure to turn your protection back on before you plug back into the network.

PaulStoffregen
12-17-2013, 02:48 PM
You could also report this to Norton....

https://submit.symantec.com/false_positive/

MichaelMeissner
12-19-2013, 09:40 PM
Paul, I happened to notice that in the summary of features page: http://www.pjrc.com/teensy/index.html, Teensy 3.1 only lists 1 I2C device, instead of 2.

jdc928
12-21-2013, 09:06 PM
Yes, 4000 RGB LEDs.

The 1000 recommendation was based on allocating at least the 3K frame buffer in the lower 8K of memory on Teensy 3.0. That lower half of the RAM is optimized for DMA, with a separate bus. The USB stack also allocates about 3K of buffers in the lower half. The upper half contains the stack holding local variables, function return addresses, and interrupt context. RAM size was the limiting factor.

Teensy 3.1 has 64K of RAM. The lower half is now 32K, with the USB stack leaving about 29K free. Both the frame buffer and drawing buffer can easily fit in the lower half of RAM.

4000 LEDs means about 500 on each pin. 500 LEDs at 30 us each will make the update time approx 15 ms, which gets pretty close to the limit for achieving 60 Hz progress refresh. You might be able to use 8000 if 30 Hz refresh is ok. That would allocate 48K of RAM for the 2 buffers, so I would definitely not try to push much farther than 8000. If you do connect so many to one Teensy 3.1, please post photos!!!

That is awesome news! The 30hz refresh rate is even probably faster then really needed for this purpose. The leds are on a robotic performers suit and are running animations based on live music being played. The original suits I made for personal use utilized a few teensy 2.0 boards linked together just to get a 1000 rgb leds working together. Being able to push the teensy 3.0 to 4000-8000 rgb leds makes the task of putting 20,000 on a single suit Sooooooo much easier. Here's some links to some of the original suit parts running on Teensy 2.0 and using fft to generate effects on the leds. The new suits will be traveling around the world and being seen by thousands of people 3 nights a week starting early part of 2014. I Would have never gotten the chance to do this without the help of these amazing little micros!

LED Suit being controlled by an old school nes powerglove connected to a teensy 2.0
https://www.youtube.com/watch?v=gvFRutT9TLs&feature=youtube_gdata_player

Teensy 2.0 with audio input mic using fft to generate led visuals in real time
https://www.youtube.com/watch?v=uLKNws2Y6t4&feature=youtube_gdata_player

Matching helmet running modified adafruit led effects on Teensy 2.0
https://www.youtube.com/watch?v=WaZp5Yt1aOY&feature=youtube_gdata_player

And lastly... Demo of ability to use led finger gloves and rods to generate patterns using POV during live performance. (being done on a teensy 2.0 of course)
https://www.youtube.com/watch?v=Nbwo9XuqSpQ&feature=youtube_gdata_player

luisonoff
02-03-2014, 09:18 AM
I just wanted to say THANK YOU!
Teensy 3.1 is what I was waiting for!! :D

vcaeken
02-04-2014, 06:42 PM
When will Teensyduino support the programming of the lock bits in order to prevent read out from the flash program memory?

PaulStoffregen
02-07-2014, 07:36 PM
in the summary of features page: http://www.pjrc.com/teensy/index.html, Teensy 3.1 only lists 1 I2C device, instead of 2.

Opps. It's updated now. Thanks!