Search results

I was using FastLED (3.4) in OctoWS2811 (1.4) output mode with the Teensy Audio Library (master) using AudioInputAnalog & AudioAnalyzeFFT256 on a Teensy 3.2 and noticed some periodic flickering. It did not seem hardware related. It would go away if I stopped using the Audio library, or if I...

Thanks for your quick replies. To clarify, when I said choke I meant that nothing would be output on SPI1 (CLK or DATA), either on my logic analyzer or when I probed the points with analog probes. Here is a picture of my setup working with the analyzer plugged in. I tried running my tests...

Is there a maximum speed for SPI1 on the teensy 4.1? I can easily push SPI to 32mhz, but SPI1 seems to choke between 26 and 27mhz. #include <SPI.h> #define PAYLOAD 4096 uint16_t dac[PAYLOAD]; void setup() { pinMode(2, OUTPUT); SPI1.begin(); //WORKS...

1. I frequent the Minneapolis Microcenter. 2. They carry the Teensy 3.1, 2.0, and 2.0++ 3. They seem to have at least one of each Teensy in stock all the time, but sometimes they can be hard to find on the shelf (I'll get a picture next time). I think their web inventory levels are...

Thanks for the clarification, the library works great! I'm currently using ADC0 with the Audio Library while using ADC1 with your library to sample a few analog inputs slowly in a round robin fashion. This added functionality would have been totally out of my project's scope if I had been...

Warnings: After thinking about it a bit, I realized my project was being compiled from scratch every time I went to upload it, causing all the libraries I was using to generate all of their warnings every time, which shouldn't really be happening. After cleaning out my temp folders...

I think the Arduino MPU6050 library included in i2cdevlib is the defacto standard. https://github.com/jrowberg/i2cdevlib/tree/master/Arduino/MPU6050 Some of the warnings are easy fixes, some of them I'm less sure of. I also get a few warnings from OneWire about the variable "mask" being...

I'd prefer to do that too, but the warnings are in other people's libraries that seem to work OK as they are (*Points at MPU6050 Library*). Digging into them to fix them is somewhat out of the scope of my project...

I just installed the Arduino 1.6.3 IDE and Teensyduino 1.23 on Windows 8.1, and I can't seem to hide compiler warnings when compiling for the Teensy 3.1. I recently upgraded from 1.0.6 and some older version of Teensyduino (1.20?) but I completely deleted my arduino folder in program files so I...

It appears that the latest update removed ADC_REF_INTERNAL. Should I be using ADC_REF_ALT now? It looks like ADC_REF_INTERNAL was defined as 2, ADC_REF_ALT is defined as 1. I was using it to read the internal temp sensor on the Teensy 3.1.

You could do something like my Non-Blocking master example from one post above. You'd likely adjust the mode 0 section to write whatever the command byte is instead of a whole array like I was doing. You don't need to use my modified library unless you have problems with the i2c bus locking...

While I seem to have it working, my solution doesn't seem to agree with the datasheets... I ended up doing a lot of trial and error until I could get the bus to reliably recover. After I got it working well enough, I set up a little machine with relays to continually connect and disconnect SDA...

Initially I based my reset off of this: 3.1.16 Bus clear Page 20: "If the data line (SDA) is stuck LOW, the master should send nine clock pulses. The device that held the bus LOW should release it sometime within those nine clocks. If not, then use the HW reset or cycle power to clear the...

I realized that modifying the library would be a bit out of the scope of my quick little project, so I did what needed externally. Here is an quick and dirty example that is non-blocking (As long as you stick to the non-blocking functions) and can recover from SDA being left down by a slave...

The timeouts in the library seem to only deal with slaves that go silent and disappear, I want to handle slaves that disappear and come back thinking they still need to send some data (and are trying to hold SDA low). I Suppose I could also detect if something is holding SCL low, but there...

I'm going to be getting data from i2c slave devices that can be hot plugged in and out (bad idea, I know), so I've been playing around with a way to make sendTransmission and sendRequest recover from bus lockups (I was running into them during testing). In the library commented out the two...