Search results

Have you tried reading the image data once, put that data into a buffer, then displaying a line at a time from that buffer? Reading from SD cards is slow. Reading from buffers is going to be at least a thousand times faster. I'm displaying from a buffer to 200 APA102 strips at 500 fps, with...

Cheers for setting up the profile, I've just ordered a couple.

Cheers, I look forward to getting my hands on some and good to hear there's lots of interest. NZ has relatively sane politics, so I'm not going to complain about the postage.

I'd love to try these out as I'd like to make a sound-reactive version of my excessive LED staff. Sadly, I'm in New Zealand and Tindie is telling me that it won't ship these to NZ. Any idea when that might change? Or is there a way around that restriction?

Looks to me like the displayed image has far fewer colours than the original. This can happen if you are not displaying at full brightness. Is this the case? If you have an image with 256 levels, and you display that at 1/8 brightness, then the image will only have 32 levels. You can avoid...

Thanks for finding that out for us. I'm another of the people who wants to use a T3.6 for an LED staff, so it's good to know in advance what the failure modes will be. I've too had a surface-mount component come off a board in an LED staff when I dropped it, so yeah, this is a worry. Stopping...

They are macros defined in the FastLED library. You can look up the code in http://fastled.io/docs/3.1/lib8tion_8h_source.html They don't use interrupts (stated at https://plus.google.com/112916219338292742137/posts/ZCucuzvCJFd).

The FastLED library has a bunch of macros for non-blocking delays, which let your code update frames when needed while allowing your code to do all the other things it may want to do. So you can write something as simple as: EVERY_N_MILLISECONDS( 3 ) { FastLED.show(); } I'd like to have the...

That's looking very nice. And yes, the high frame rate is really needed for this kind of thing, so I'm glad you've got it going hard out.

I'd love to be able to use something like this for music response on my Teensy glow-staff. However, as Paul mentioned, immunity to electrical noise is critical. I'm switching up to 800 APA102 LEDs on and off every two milliseconds. I've tried before using other circuits, but been unable to get a...

My dream Teensy battery charger-breaking out CHRG & POWER_ON lines on STBC08 charger I've used Onehorse's most fine STBC08 High-Current LiPo Battery Charger for several projects, including the Mitocondrion 800 LED POV glow staff. It is nearly ideal. I'm now working on some wearable badges using...

Yup, great news to wake up to. Thanks Paul. Does mean I'm going to have to build another version of the Mitochondrion glow staff. The goal for this one will be LED music visualisation as well as the POV images.

Yup, I did. I don't think I'd get anything without TFT_DC.

I have the Adafruit 3.5" TFT HX8357D and a Teensy 3.2. Here I was about to complain that it wasn't working when I started by checking my wiring. The wiring was wrong. Doh. Fixing that gives me a screen running using SPI, Paul's library and the graphicstest example. However, I've the same...

I am running 800 APA102 LEDs as four 200 LED strips in parallel, i.e. all four strips display the same pattern and are controlled from the same clock and data pins. It works. I'm refreshing them every 3 milliseconds.

Thanks. Yes, that's on the list of things I'd like to do next. I'm thinking something like a BlueSmiRF to wirelessly link to a phone running MIT App Inventor or equivalent.

Can't resist posting a few more pics:

I've put together a pretty detailed write up of the Mitochondrion, Mark 5.3, with lots of high-quality pics and technical details included. This has survived it's first festival (Kiwiburn) with no damage. Next job is adding a watch-dog timer, so that it resets properly when the batteries...

That's impressive. I've never gone below 15.9 mm, but then again I'm using the side holes.

Can you try changing the refresh speed of the LEDs or the clock speed of the Teensy?

Batteries are 14500 lithiums. Power is capped at 10 Watts by FastLED, which is bright enough for daytime use. More power drain just sags the battery Voltage and causes red-out. Boards on three of the four sides just distribute power and data. I've tied strips to the power and ground in multiple...

Yup, four sided, 200 LEDs per strip, so 800 LEDs in total. You can use this in daylight. There's enough room inside a 25.4 mm ID tube for a 14500 cell, the cell holder, four PCBs, four LED strips, and pretty much nothing else. Cells go at the ends, then there's room at the middle in the centre...

I'm also keen to find out. The next version of the Mitochondrion glow staff is now spinnable and ready for Kiwiburn. The on-Teensy memory only holds about fifty images and those are only 16 colour, so I'd be delighted to have more memory to work with. And my audio FFT visualiser is far from...

Hey, that's looking pretty good. I have a heap of questions: What camera did you use to get those recordings? I've tried and failed to get good video of my staff. How effective is the mercury tilt switch if the staff is spinning around a point away from the centre? I went with a gyro coz my...

My experience has been that printing undersize and drilling out is the best way to go, even with prints at Shapeways. I tend to print slightly smaller than the pilot hole size, so for M3, I'll print at 2 and drill out to 2.5. Takes all of a second per hole. Machine screws will hold, but won't...

Ah yes, that did the trick. Changed every Wire.fn() to Wire1.fn() throughout the whole sketch and now I'm getting good comms and good data from the sensors. Thanks for helping with that. To avoid someone else having this problem, would it be possible for you to provide a test sketch...

(For future reference, AD0 on the MPU-9250 microshield corresponds to pin 24 on the Teensy 3.1.) Toggling pin 24/AD0 changes the device address from 0x68 to 0x69 and back, as expected. The I2C scanner recieves an ACK from the valid address. Trying to read the register map (0-126, from...

I agree that current libraries don't make it easy to use alternate or multiple I2C buses. The sketch is now using Wire1. However, the i2c_t3 library is unchanged and I'm pretty sure that it doesn't need to be, coz I've an LSM9DS0 microshield here running just fine using Wire1 and i2c_t3. The...

I am using the sketch at https://github.com/kriswiner/MPU-9250/blob/master/MPU9250BasicAHRS_t3.ino. That uses i2c_t3 and wire, not wire1. Is that incorrect? Changing all of the wire.blah(...) to wire1 resulted in the following unexpected output: "MPU9250 I AM C0 I should be 71 Could not...

This time around, I ordered the MPU-9250 micro add on shield. I'm getting ACK but not WHOAMI. The shield is soldered onto the back of a Teensy 3.2 and the code from https://github.com/kriswiner/MPU-9250, specifically the MPU9250BasicAHRS_t3 code, with the I2C_PINS_16_17 changed to...

Have you tried different clock speeds for the Teensy (not the SPI data rate)? Some earlier versions of FastLED cause flicker at more than 48 MHz. https://plus.google.com/u/0/+JezWeston/posts/f3NtCpxoPR5

Yeah, until then, this:

Because chloroplasts absorb light, whereas mitochondria supply energy.

I went to bed last night having spent the day scratching my head over how to get a Teensy to run the APA102 strips AND the SPI flash memory AND the motion sensor AND the microphone... So Xmas just came early. Thanks, Paul. And the All Blacks won as well. I'm currently designing the next...

A couple of pictures from my glow staff. Teensy 3.1, FastLED, and APA102s. A few more at happyinmotion.com. Sorry for the delay in getting these pics after promising them a month ago. Went to Burning Man, broke everything, learnt lots. Fixed enough for these pics, now working on a newer...

Yup, it was Avast. Disable that and the compile time goes back to a reasonable 15 seconds. Thanks for the pointer. I switched to Avast recently (coz AVG decided to sell user data) which fits with when this problem arose.

Compiling has started to take a while. Like four minutes for the example Blink program. I'm using Arduino IDE 1.6.3, Teensy loader 1.23, onto a 3.1. Verbose mode doesn't reveal any complaints, just a great deal of time spent object files. What might I be able to do about this?

Hi, did anyone get anywhere with this? I've one of the INMP441 breakout boards connected to a Teensy and it produces a bitstream to Serial, but I'm not sure how to analyse that data (or even how to tell if it is valid). What I'd like to do with it is chuck it through an FFT and get a...

On the Hat? Definitely. There's an exposed distribution board and the ends of the strips, all of which pick up dust and need to be protected. Not sure how to dust-proof the switches on the strip drivers though, aside from clingfilm or bagging. Finding a small rocker switch is escaping me, as...

By this point, many of you know the drill: make shiny LED things, take them to Burning Man, discover interesting new failure modes. I made five drivers for LED strips and discovered just how dust-proof my switches were not. Here's my guide to how to make portable and grunty LED strip drivers...

I tested a bunch of level shifters last year. Those were for driving Neopixel LED strips, which are very picky. For anything less demanding, I'd expect the choice of level shifter to matter much less than just having one.

I'm using APA102 strips for my 800 LED POV staff. I'm updating at 3 ms and getting great image display. You'll also have to take my word for it, as I've still no passable photos. I need to repair the staff after Burning Man before I get any. I'm sure this can go faster and give better images...

I'm looking forward to more flash and more pins. An easy to use low power standby mode would be nice. Lack of 5 V I can cope with, as I'm using level shifters to provide 5 V signals to LED strips already. However, the one thing I hope doesn't change is the physical width. The T3.1 is at the...

I don't think we can say whether level shifters are needed or not without some serious testing of what works and what doesn't. The NeoPixel strips were very touchy about Voltage levels. Even with level shifters, most that I tested weren't good enough (Testing level shifters for running Adafruit...

Yeah, I should also start a new thread, as the 800 LED POV staff is now spinnable and people may be interested in that. I've yet to get a good photo though, due it being too bright. I'm also interested to hear more about the higher current lithium charging. I'm using 6S packs and 5 Volt...

As for running multiple strips off a single data line, i.e. strips in parallel, I've had no problems using four 1.5 metre strips, both for NeoPixel and APA102. However, unless you need very fast updates, it's just as easy to put the strips in series, so data from the end of one feeds into the...

I'm working on something similar: Teensy 3.1, LSM9DS0 motion sensor, 12 14500 Li-Ion cells, 90 Watts of UBECs powering 800 LEDs as four parallel strips of 200 APA102 LEDs. Progress as of this week: Given previous experience with NeoPixel strips, I like to make absolutely bloody certain that...

Ok, I figured it out. Here's my stand-alone sketch and library to run the LSM9DS0 micro-shield on a Teensy 3.1. I only have the early micro-shields, so no pressure sensor. This has been tested with IDE 1.6.3 and Teensy Loader 1.23. This sketch requires the i2c_t3 library and my modified...

Putting #include <Wire.h> in the sketch certainly means that it finds Wire.h. However, both i2c_t3 and Wire try to declare the same objects. With i2c_t3 before Wire: C:\Users\Jez\Documents\Making\arduino-1.6.3\hardware\teensy\avr\libraries\i2c_t3/i2c_t3.h:803:15: error: 'Wire' has a previous...

Sorry, now I'm even more confused. https://github.com/kriswiner/LSM9DS0/blob/master/Teensy3.1/LSM9DS0-MS5637/LSM9DS0_MS5637_Mini_Add_On.ino is missing the function definition for MadgwickQuaternionUpdate. That definition is in the quaternionFilters sketch. I don't see any includes for that, so...