PaulS

What @jmarsh meant is to use pinMode(<pin>, INPUT_DISABLE); in void setup(). So in your case pinMode(MEASURE_PIN, INPUT_DISABLE); More info here. Paul

This is what your code from message #1 shows on the logic analyzer: Agree with @thebigg that using SPI transactions around every transfer is the correct way. Also described here at paragraph Transactional SPI configuration. Paul

I guess you are referring to this board? Yes, the board's regulator will have a small dropout but the LSM9DS1 chip will work from 2.4 - 3.6V. No. The board's Vin is an input so that can be connected to Teensy's 3V3 regulator output pin. But the...

Are you using this board? If so, connect the sensor board Vin pin to the Teensy 3V3 pin, as described here. Luckily, the DO/MISO pin from the sensor board is not level-shifted to the sensor board Vin voltage, so your Teensy will be OK for now. Paul

You could go for an Arduino Nano breakout board, I saw those on AliExpress for $0.62. Paul

What about this one?

Indeed, those profile posts are gone. Thanks, Paul

Did you set Tools > USB Type to "MIDI"? Paul

Do we need to be able to see new profile posts? Looks mostly spammers that are bothering forum members? Paul

Not really sure I understand your question but I can find usb_desc.h here: C:\Program Files (x86)\Arduino\hardware\teensy\avr\cores\teensy3\ and C:\Program Files (x86)\Arduino\hardware\teensy\avr\cores\teensy4\. Strangly enough, the Windows...

If you are actually using this microphone module, then it can handle 2.7V-5.5V as supply voltage. Paul

Not sure what you want to accomplish...why would you want 3V3 on the adapter? It looks like you mounted a connector on the Teensy 4.0's 3V3 and GND pins, probably to power the Teensy 4.0 externally? By the way, you inserted the Teensy 4.0 the...

What you could do is connect 2 USB-A to micro-USB cables, one to the Teensy and the other to your PCB. Then measure conductivity between the corresponding pins of both USB-A connectors. And check for shorts as well. All while both boards are not...

OK. Can you show us that part of the PCB layout? I would like to have a look at how the D+ and D- traces are run on your PCB. How does your PCB make contact with the Teensy D+ and D- pins? Paul

Can you show us what other USB ports you have tried? What cables did you use? There can be many causes for failure, like noise, polarity, impedance, etc. After all, we are talking about high-speed USB at 480Mbps. Paul

Yes, the Entropy library also works on Teensy 3.2. Source code can be found at C:\Program Files (x86)\Arduino\hardware\teensy\avr\libraries\Entropy\ Paul

Well, actually, it's a part of your program. That makes it difficult to give you advice. Can you share your complete program? Please use the top-left </> icon. Paul

Perhaps one of these posts will help you: https://forum.pjrc.com/index.php?threads/extending-usb-to-external-connector.29294/ https://forum.pjrc.com/index.php?threads/t4-1-external-usb-c-connector.65633/...

Another observation. This is how the MIDI Clock messages look over time. The timing between clocks is less stable than I would expect. @snowsh Does this pose a problem for you or are you doing some averaging? Paul

Confirmed! Paul

Just realized why while (usbMIDI.read()) {}; did not seem to work: it does actually work, but only for 1 buffered message since there is some time between messages (~250us). Hence PaulStoffregen's code elapsedMillis msec = 0; while (msec...

Hi Mark, Copied the relevant code from your message #30 into the code below: #include <MIDI.h> unsigned long currentRXtime; unsigned long previousRXtime; bool initial_pass_only = true; void setup() { delay(10000); // wait 10 secs } void...

Hi Mark, no, I did not. It threw a lot of errors during compilation: C:\Program Files (x86)\Arduino\hardware\teensy\avr\libraries\USBHost_t36\hid.cpp: In member function 'void USBHIDParser::out_data(const Transfer_t*)': C:\Program Files...

@snowsh Your notion is right. Used one Teensy to send RT messages every 21ms: #include <MIDI.h> IntervalTimer myTimer; void setup() { myTimer.begin(sendMIDIclock, 20833); // 120BPM = 24ppq/500ms = 20833us/clock } void loop() { while...

No, that didn't work either. Still 4x96 F8's before the normal 21msec F8 cadence comes in. usbMIDI.read(); does not clear the buffered MIDI clock messages. Paul

Wondered if usbMIDI.setHandleRealTimeSystem(RealTimeSystem) might be the issue, so I changed the code to using usbMIDI.setHandleClock(myClock). Changed void setup() to: void setup() { Serial.begin(57600); Serial.println(F("serial ready"))...

OK, uploaded your latest sketch from message #23. Saw this on the serial monitor: This rush of F8's goes on for roughly 4 x 96 times before the normal 21msec F8 cadence comes in. Setting enableActiveSensing to false or true did not matter...

It turned out to be even easier. The only thing I had to do was adding reaper_automidireset_x64.dll from reaper_automidireset_win_x64.zip (found here) to the REAPER\UserPlugins directory. Restart Reaper and you're done. Works prefectly. More on...

That's weird. Can't get Reaper to reconnect automatically. I also found several posts on the internet that it does not work without "Reset all MIDI devices". Even found this post that someone made a workaround for that issue...

I'm curious to hear how much delay you see by just adding this voltage divider... Paul

What about a passive voltage divider? E.g. 1K8Ω & 3K3Ω. Paul

Allright, the one important observation I had. Steps to reproduce: 1. Reaper (V7.02) plays track and outputs MIDI clock message 'F8' continuously 2. Teensy receives these F8 messages and shows them on the serial monitor 3. Disconnect Teensy from...

Yes, found that out too. Anyway, during the forum outage I installed Reaper, made a simple drum track at 120bpm, and was able to output MIDI clock messages. I updated the RX code a bit: //...