PaulS
Senior Member

Thanks Rolf, You might be interested in the measurements I did as well on several DAC's. Paul

Hallo Rolf, Thanks for your reply. I was wondering what A/D-converter you were using for your measurements. Some USB audio device? Paul

Hallo Rolf, Just curious: what measurement program did you use and what ADC? Danke, Paul

Most probably yes. But you can easily verify that by commenting out the line filter1.frequency(30); // filter out DC & extremely low frequencies and check again with Audacity. Paul

Maybe this post helps? Paul

Hi Manitou, what voltage do you power the DAC board with: 3V3 or 5V? The board you referred to should be powered by 5V. Paul

MISO1 is actually brought out on the Teensy 4.0. Just below the card on this page, it states "Not shown on this reference card, Pin 0: CS1, Pin 1: MISO1" Paul

First unofficial Arduino IDE support for the Pico: YouTube and on Github. From the video: @3m31s: "And as last time, the Teensy 4.1 is in a different class" :cool: Paul

This was the first hit when I googled for "Peregrine Developments". Is that what you are looking for? Paul

Hi Kevin, Your wiring diagram "Attachment 24027" does not show up: Paul

Whether those dinosaur versions are supportive of x64, I don't know. Perhaps the quickest way to find out is to install those old versions and try it out? Regards, Paul

Yes, it does. Until recently, I ran Teensyduino on Windows 7 x64 Pro before upgrading to Windows 10. Regards, Paul

Here is another interesting video: https://www.youtube.com/watch?v=_PfUEnkqeOs Both reviewers had not noticed though that this yellow board has the cinch jacks reversed. The jack with the red plastic insert is...

The board I referred to has 3 voltage regulators: the charge pump is powered separately, not interfering with the analog power. Also the 1000uF caps at the output of the 3V3 regulators is a bit overkill. And I would...

This strongly suggests that the button input pins on the 5V Device are pulled up to 5V and that an external button pulls that line low. Problem is that this 5V pullup voltage will kill your Teensy. Best way to check...

@MichaelM, I think you mean the SN74AHCT125N part, isn't it? The one with TTL level input IH = 2V]. The non-T part has an VIH of 3.85V at 5.5V VDD. Regards, Paul

Hi Andy, Only in case a peripheral wants to drive a signal higher than 3V3 to the Teensy. For your application, CS, MOSI and SCK are all outputted by the Teensy at 3V3 max so no problem in that respect. You...

Hi Jim, (1) SPI always uses push-pull pins. (4) I don't see a problem, the chip can be used for SPI, see this product. (5) the chip is bi-directional, it just "voltage-translates" signals from one side to the other,...

Allright. Glad you got it to work. Regards, Paul

Since you are soldering on the backside of the Teensy 4.0: you did not accidently short pin 32 to one of the SPI pins 10, 11 or 12? Regards, Paul

You stated "The problem is that there is no response from the HC-05". Well, the first thing I would do is to measure whether pins EN and EN7 are actually set HIGH by the digitalWrite's when not having the SPI.end()...

The board I linked to also has 2 voltage regulators on board. I assume to generate a 3V3 analog and a 3V3 digital power supply. If you want an easier-to-use board, go for this one. Check out the wiring here. To be...

Price versus quality, I think the PCM5102A is the best choice. You can find boards for less than 5 US$. See here. Regards, Paul

Found the datasheet of the TL2796: The controller has an SPI interface for configuring the display and a 16/18/24-bit RGB video interface. And found some Linux driver stuff on Github as well. Not sure whether this...

The Alibaba page you linked mentioned "D-IC Built-in D53E6EA8805". Searching for that led me to this panel: Samsung AMS326P01. Samsung panel datasheet here. The driver chip is from Magnachip, part# D53E6EA8805....

I verified your sketch on a T4.1 and with or without the analogRead(randomVar ); line, it shows a serial USB device . Did you set Menu > Tools > USB Type to Serial? Using Arduino 1.8.13 & Teensyduino 1.53 on Windows...

Generally, for strips having more than 3 DotStar LEDs, you want to power that strip externally. You don't want the propshield board to supply significant current to DotStar strips. See this page for more info how to...

Great! What was the issue in the end? Was it indeed an SH1106 controller on the 1.3" OLED? Regards, Paul

Other Dutch resellers like Antratek and Floris always shipped Teensy's to me with a card Paul

When searching further about the difference between an SSD1306 and a SH1106, I saw some display pictures looking very similar to your picture in message #4. Here is such a thread. And another thread. The solution is...

Looks OK to me. Could it be that your 1.3" OLED has a different controller, like the SH1106?

Same here with Tinytronics, no card with the Teensy 4.0. But never bothered to call them... Paul

Allright, no I2C pullups apparently. So you know what to do I guess? See this post. Paul

Allright. Now it's time to measure whether pullups are present the I2C lines. With the display disconnected from the Teensy, measure with an ohm-meter between the SDA pin and GND and between the SCL pin & GND. Paul

You also may want to try to run at a lower I2C clock frequency: Adafruit_SSD1306 display(128, 64, &Wire, -1, 400000); Paul

I would not be surprised if the 1.3" display is on another I2C-address. The zero ohm resistors near the 4 pin connector are differently strapped. Did you run the I2C scanner example sketch on both displays? Paul

Hi Bruce, you may consider buying a cheap CANbus analyzer like this one. This device saved me a lot of time while implementing & debugging a wireless CAN bus. Here is a thread with some screenshots of the analyzer...