Search results

Actually, that's the one other thing I updated with the change to Teensy 4.1 - switched the LEDs from through-hole to SMD. The new TRL_LED has a forward voltage of 2.15 V, and RESP_LED has Vf of 3.2V. I calculated the resistors to power the LEDs at 10 mA (since that's what the 3.6 could support)...

Hi all, I have a setup that uses a Teensy as a DAQ to control some relays and read a few sensors. It previously worked with Teensy 3.6 with little issue. Since Teensy 3.6 was discontinued I have switched to 4.1, but am having issues with connectivity and Teensys no longer responding (presumably...

Yeah, I completely blanked on the need for a current limiting resistor. I'll add a 370 ohm resistor (If = 10 mA, Vf=1.3V). The solenoid I'm using is rated as using 1.15 W at 24V, which works out to much less than 1 A (47.9 mA). My understanding was the diode would handle the surge current, and...

Just a quick clarification - the Teensy is on USB power, and there is also a 12V power supply in the circuit, but none of the 12V signals go to the Teensy (although they have a common ground).

I have a Teensy 3.6 plugged into a custom PCB. One of the functions of the Teensy is to drive a relay to control a solenoid valve. The solenoid is powered from a 24V supply with an isolated ground (24V ground is separate from the Teensy ground), and the relay is a solid-state optoelectronic...

Unfortunately, the situation is about the same; between the six Teensy units, the disconnect happens at least once per day. Quick Recap: I have six Teensys connected via USB to a PC running Ubuntu 16.04, and communicating through USB serial connection. The Teensys have identical programs...

I have a project that involves multiple (6) Teensys with audio boards connected via USB to a single computer running Ubuntu. Each Teensy is individually controlled by a Python process, and is set up to stream audio from the Python process (i.e., Teensy acts like a sound card). The Python scripts...

So I received the hub today. I'm not actually sure what to make of the lsusb output, but it doesn't immediately read as a single TT device, which is hopeful. The value for bDeviceProtocol is actually 3, and I can't find what that means (but I'm assuming those values are independent settings...

Hi Paul, At this point three are plugged directly into the computer, and three are plugged into the hub, and it's the ones on the hub that are acting up. It looks like the hub is in fact a single TT device - so that means replacing the USB hub with a multi TT device would solve those problems...

Hi all, I have a project that involves multiple (6, at the moment) Teensys with audio boards connected via USB to a single computer. Each Teensy is individually controlled by a python process, and is set up to stream audio from the python process (i.e., Teensy acts like a sound card). Teensys...

So after some experimentation and reading, it appears that it's not easily possible to rename the devices dynamically (https://forum.pjrc.com/threads/32534-Adjusting-the-Teensy-MIDI-device-name). The easiest method I've seen is using the name.c file included with the Teensyduino example...

Based on my understanding, the new device name has to be explicitly defined at compiling (since it uses #define)? Does the USB code require it to be declared that way, or can it somehow be declared as a variable that could be device-dependent? Otherwise it seems that to have multiple Teensys...

I'm building a device that will play audio and simultaneously control some LEDs and read switches. Several of these will be running simultaneously, controlled by a central (Windows) PC, each with its own audio. I need to be able to determine which audio to play for each board using the PC, so...

I'm trying to implement a very basic menu system in my project. I'm using the PJRC ILI9341, Teensy 3.1, audio board, and 4 membrane buttons for inputs. Two 'layouts' will have options to select, both very similar - some approximation of this: I'm trying to figure out the best way to navigate...

Okay, so maybe I misunderstood the CPU speed settings. I thought I'd read somewhere that 16 MHz was the fastest without overclocking, so I set the speed to that, ignoring the words "No USB". :rolleyes: Changed the speed to 72 MHz, suddenly everything works fine now.

I just got two Teensies (3.1), and my computer has trouble recognizing one of them (Teensy A). I've soldered pin headers and a crystal for the RTC. When I connect it via USB, there's no sound that something has been plugged in, the device manager doesn't change to show a new device, and...

So a quick update: I got my new Teensys (Teensies?), and hooked one up to a breadboard with the 7805 and a battery power supply (4 AAs) - success. Switched to the Traco regulator - success. I then soldered the Traco to the board and attached the Teensy, and it worked just fine with the...

Apologies in advance if this is convoluted or confusing. So the vector solution has a two-fold reason (which I now realize I should have mentioned earlier). In addition to writing the data all at once (which you've addressed), I'd be doing some rough data analysis on the whole dataset (taking...

I'm making a datalogging program using Teensy 3.1 and an I2C sensor, with the SD card reader on the ILI9341. I'm using vectors to store the data, since the logging duration is variable. The sampling rate is ~100Hz (every 10 ms), so rather than writing the data to a file continuously, I'm...

So I removed the Traco and tried using a 7805 on the same board, and it looked like the same result. I then tried a different power source, and now the Teensy won't light up at all, so I'm assuming I fried it (second supply may have been bad). While I wait for a new one to arrive, I checked...

I've made some progress on my board, and have a prototype fabricated and soldered. However, I'm having trouble actually using it. I designed it based on this board, but modified to work with the ILI9341 AND the audio board. I'm planning on modifying the screen to run off 3.3V. Schematic and...

EDIT: I just realized I posted this to the wrong board. If it could be moved to Project Guidance I'd appreciate it; otherwise this thread can be deleted and I can recreate it over there. I'm designing a PCB for the Teensy 3.1 and was hoping for some design advice/verification. I have four...