Search results

Thanks a lot, I will definitely give this a try.

I need to use the Teensy 4.1 USD Device to connect to a host computer and simulate physical USB connects/disconnects. It it at all possible to (ab)use the NXP iMXRT1062 on-board Native USB device in this manner? Hacking SDIS bit (Soft disconnect) on OTG_FS_DCTL in TeensyArduino? If not through...

So if I needed to connect the same Teensy to 2 PCs, using one for bootload and debug and the other to act as a HID device, which one should I use for the former and which for the latter? On-board USB Device for bootload? If latency was an issue (but only for HID/Raw HID), is there a USB to...

How about connecting the Teensy 4.1 device to more than 1 Host? Similar to a protocol analyzer: Host - Teensy4.1 - Device | Analyzer Two hosts, two physical connections, plus one device with the 3rd physical connection. Teensy 4.1 has 2 out of 3. Use one of the other...

Well, I know it is a niche, but I'd really like to get all 16 QUAD timers on 16 pins ...

Sent you a PM re: dissertation. Did you successfully convert it? Thanks!

For (my own) future reference, also found this thread w/ @KurtE https://forum.pjrc.com/threads/57894-Teensyduino-1-48-Beta-3?p=220131&viewfull=1#post220131

Related: the Future 1170 thread is also closed for the duration "until after Teensy 4.1 ships" https://forum.pjrc.com/threads/57842-Future-Teensy-features-amp-pinout?p=233257&viewfull=1#post233257 but I was wondering - for those interested in 60+ MHz resolution capture of 16+ concurrent input...

Thread's closed, but I must be misreading this post: "These are all the unconnected pins on Teensy 4.0 which could become available: [..] B0_06 A8 QTIMER3_TIMER0 B0_07 A9 QTIMER3_TIMER1 B0_08 B9 QTIMER3_TIMER2 B1_10 B13 QTIMER3_TIMER3...

What if you want three connections, placing the Teensy 3.6 in the middle between a USB device and a USB Host, with a 3rd connection to a PC. Is there enough onboard USB on the 3.6 to address all three, or is there a way to use a serial connection for the PC?

Would it be possible to do PulsePosition input capture on eFlexPWM as well? You mean the NXP reference manual (non-login version) ? https://www.nxp.com/docs/en/reference-manual/IMXRT1050RM.pdf I see Chapter 9 able 9-1 shows TMR1-4 with 4 channels each, so in theory a large PCB Teensy 4.x...

The card does not list QTM, is Beta2 identical to final T4? 10 B0_00 2.0 4:CS0 QT1_0 MQS_RIGHT 2:0 11 B0_02 2.2 4:MOSI QT1_2 1_TX 2:2 12 B0_01 2.1 4:MISO QT1_1...

Maybe I don't know how to read it, but it does not appear to list/track the FlexTimer Module pins? https://www.pjrc.com/teensy/td_libs_PulsePosition.html I am trying to figure out what the future of PulsePosition input capture would be on T4 (and maybe on a larger T4.x down the road), mapping...

Only pinout overview I found calling out Quad Timers: https://forum.pjrc.com/attachment.php?attachmentid=15040&d=1540676635 Implies 9 concurrent inputs.

From the various beta threads: * https://github.com/PaulStoffregen/FreqCount T4 updates * https://github.com/manitou48/teensy4 qtmr_ experiment sketches I lost track on pinout revisions, but at one point: 10 B0_00 QT1_0 11 B0_02 QT1_2 12 B0_01 QT1_1 13...

QTIMER (output) tests: https://forum.pjrc.com/threads/54711-Teensy-4-0-First-Beta-Test/page151 output 150MHz at pin 19 https://forum.pjrc.com/threads/54711-Teensy-4-0-First-Beta-Test?p=210440&viewfull=1#post210440 never getting the QTIMER overflow interrupt to work...

T4 version of Flex Timer Module called QTIMER From: https://forum.pjrc.com/threads/52761-Teensy-4-0-(hypothetical)-pin-assignments?highlight=QTIMER

I'll add what I find (eventually find out) here. One way to phrase my question: What's the expected/hoped for spec for Pulse Position (QTimer equivalernt) on Teensy 4? How many pins, which, what sample frequency, dual-edge capture (discriminating rising from falling)...

Teensy 4 FlexTimer Module (FTM) / Quad Timer (QTIMER) Input Capture capabilities Just in case somebody has already dug out relevant specs: I am using Teensy 3.x for FTM input capture, targeting bursts of pulses at modulation frequencies between 1.8MHz and 10MHz, with burst O(10-100) pulses...

OK, maybe I2C to a PIC32 then? Something like https://dorkbotpdx.org/blog/wbowers9000/multi_board_madness but with 3.x and more details?

Is there an equivalent for the PIC CTMU on the Teensy? I am not looking to capacitive touch, but a timer for distance measurement. See page 5 figure 5 here: http://ww1.microchip.com/downloads/en/AppNotes/CTMU%2001375a.pdf I need better than the 60MHz I get with PulsePosition. Hoping for...

Thanks - if you don't expect to to have 24-pin versions anytime soon, the suggestion to cut 14-pin down to 10-pin is a sensible one.

This page https://www.pjrc.com/store/header_14x1_d.html confuses me. Title says 5 pins, order button legend says 5 pins, image shows 14 pins, which also makes sense. These would work for Teensy LC as well? Is there a 24pin version of this for Teensy 3.5/3.6? Not for Audio use, but to put a...

I am trying to find a good solution to connect several - possibly a dozen - Teensy nodes to a PC host. The simplest approach would be to just connect them wired, to a USB hub, and run both power and serial. However, eventually I will have to run wire lengths up to 10m and possibly beyond. Is...

Thanks Michael, those are really useful links for mock-ups and prototypes - I can ignore extra width for now, or maybe even cut it off once or twice. Sort of like this, though cutting might be easier starting with a large perfboard to begin with...

The Tindie part is just the chip, so I am looking at these in earnest: https://www.ebay.com/itm/LSM303C-3-Axis-6DOF-Accelerometer-Magnetometer-Sensor-Module-for-Arduino-H1Z7/273132674862...

Thanks - I might not even need feature creep, because the LC might be running all out if I actually use the max of 6 sensors (42mA) it can serve. Each sensor needs at least one FlexTimer Module InputCapture, with 10Mhz as max pulse rate over up to 200usec duration for each event, usually all...

There's the LSM303, for which breakout boards exist, but they aren't any cheaper. I was hoping for $5-$10, not $15+. Edit: eBay provides. I needed to start looking for eCompass etc., not 6DoF. Edit2: better yet - just mislabeled as gyro https://www.tindie.com/products/onehorse/lsm303d-accelgyro/

Did, but not closely enough. It's 9 DoF. I thought it was an IMU, but the gyro is separate. So the FXOS8700CQ would be an option https://www.pjrc.com/store/fxos8700cq.pdf and I already planned on getting a prop shield for experiments anyway. But I need something cheaper that does just...

I want to determine orientation at rest, using an accelerometer with high resolution and small range. Need only +/- 1G. But I also want to measure the magnetic field vector. Do I have to go for a full IMU (don't need gyro etc.)? Or combine two parts? Is there an all-on-one breakout for the...

I want to power 1-8 sensors from the Teensy 3V3. The 3.5 and 3.6 "welcome" cards say 250mA for 3V3 max. I don't have a card for the LC - is it the same? Is that regardless of how hard the processor is working? Per spec, each sensor draws a max of 7mA at 3V3. At 8 sensors, this would be less...

Is there a perfboard that has the same width as a Teensy and fits on it? Anybody know of e.g. an OSH perfboard-style "shield" made for Teensy I could mod or use as-is?

In broad strokes, I am looking to prototype a Teensy-based solution for 48/60 MHz data acquisition from 1-6/8 infrared sensors using FTM, using Teensy LC and/or Teensy 3.6. Something using a Teensy that looks a bit like https://trmm.net/Lighthouse#Calibration https://hivetracker.github.io...

I think I found the solution - it occured to me that the FTM calls are currently made in this order: *portConfigRegister(pin) = PORT_PCR_MUX(4); CSC_CHANGE(ftm, cscEdge); If ALT4 does not default to InputCapture, then this could make the pin an output instead in the time between those two...

I can post source of the exact sequence of Teensy API calls for GPIO and InputCapture, but w/o the hardware it's not much of a repro. I can phrase my question like this: what I observe is that: *portConfigRegister(pin) = PORT_PCR_MUX(4) has the same effect as digitalWrite(E_pin, LOW)...

I also tried INPUT_PULLUP at the end of the final GPIO read verifying the state transition, same issue. If I read this right, the internal pullups ensure that disconnected pins are guaranteed HIGH, not random, so I suspect that they do not affect what registers externally. I also made sure...

Somebody kindly suggested I should consider the built-in pull-up resistor to ensure that my E pin, configured as input, does not get drawn to LOW - assuming that's what happens when setting ALT4. Looking at 11.14.1 Pin Control Register on page 227pp I am guessing: #define PORT_PCR_MUX(n)...

Thanks a bunch for the references, Paul. I think I understand the InputCapture setup, but I am not sure this covers the problem I am observing. First, I have to generate a bunch of once-off pulse signals when using the D,E pins as output. Maybe I do not understand OutputCompare, but I read it...

Preamble: I understand this will take a while for me to sort out. At this point the guidance I could really use is somebody who understands the Teensy/FTM hardware constraints to tell me "this will never work because ..." Or a confirmation that, yes, this can be done. To elaborate: I want...

I had hoped to use PPM as-is, and I am not through doing due diligence on it, but I started a thread here: https://forum.pjrc.com/threads/51727-Question-about-PulsePosition-for-same-pin-I-O I don't think I have identified the problem yet, but I tried both PPM and a derivative of it, and it...

This: //#define I2C_F_DIV28 ((uint8_t)0x08) ... //#define I2C_F_DIV1536 ((uint8_t)0x39) https://github.com/PaulStoffregen/cores/blob/master/teensy3/kinetis.h The usual caveats - as in "it might not work" or "you could wreck the Teensy" ? Thanks for the info. Definitely will go for F_BUS...

I would much appreciate a clarification on this - is 48MHz the best this can do (including more recent e.g. Teensy 3.6)? Is it possible to run at 96MHz and sample PP at 48MHz? How did you get this to work running at 96MHz? Which example was the right one? Any changes you had to make in the PP...

Sanity check needed regarding a possible PulsePosition modification. I am trying to capture data at 48MHz, similar to what was done here: https://trmm.net/Lighthouse https://github.com/osresearch/lighthouse/blob/master/firmware/InputCapture.cpp But, instead of using the simpler TS3633, I...