PaulS's latest activity

OK, so that's not going to work. Back to the previous code. Are you actually using this product: IO5202 with 4 AI/AO? Another question on your message #24. You stated: What did you actually measure? Paul

Lin.read is a "private" function in the library, as defined in lin-bus.h: private: Stream* _stream; void send_break(); void breaklength(uint8_t length); void breaklength_35(uint8_t length); void breaklength_LP(uint8_t length); void...

OK, at least we can rule out that checksum question for now. Perhaps, but I don't know enough about those LIN timings whether it's mandatory timings or minimum timings. It certainly looks like ID 34 is the "Write power" command register...

OK. I modified my LIN-slave to respond with a classic checksum on 0x11, 0x22, 0x33, 0x44, 0x55, 0x66, 0x77, 0x88, being CRC 0x99 [153 decimal]. Now when I modify this line of your code CRC = lin.response(responseID, linRXdata, 8, lin2x); to CRC...

Hi Jordan, it seems ID 23 is the register to focus on first. Yes, that's weird. In order to verify whether your code may have an issue, I used my homebrew LIN-slave setup. I fabricated that setup a few weeks ago to verify the claim that there is...

That's interesting, you are writing value 1000 to AOx but you are reading back value 2000 from AOx. You may want to try the other use of the modbusTCPClient.holdingRegisterWrite() command. Instead of boolean writeSuccess =...

Getting the hardware integrated on your board is probably the easy part, the coding is the part that is harder to accomplish. You still may want purchase the shield as a reference for the person is doing the actual coding... Paul

Had a quick look at the EasyCAT shield and related library. The shield uses a Microchip LAN9252 EtherCAT device controller, not a 'standard' Ethernet controller. I assume that the LAN9252 chip probably takes care of the EtherCAT protocol...

Too bad that we don't have LDF file for the HVH50. Saw your request for info at the peak-system forum as well... I agree. Frames { HV_He_01: 28, Controller, 4 { KL_HV_PTC_soll, 0 ; KL_PTC_ein, 8 ; } This tells me that the bit...

The short and simple answer is you should uninstall or delete SdFat you've installed, so Arduino IDE will use the copy of SdFat which comes with Teensyduino. When you install a library, usually Arduino IDE gives your installed copy priority...

Yes, this problem usually happens on Windows if Teensy Loader is still running when uninstalling the older Teensy files or using an older IDE. Windows does not allow the EXE file to be deleted. Arduino IDE does not handle the situation well...

When using Arduino IDE 1.8.19, you can download Teensyduino 1.58.2 here: https://www.pjrc.com/teensy/td_158/TeensyduinoInstall.exe. Paul

Using Arduino IDE 2.3.2, I'm using the Boards Manager to switch between Teensyduino versions: Paul PS: I ran into an issue when when updating from 1.58.2 to 1.59: Need to look into that now... Update on the precompile_helper": file does not...

Additional info: with Teensyduino 1.58.2, the sketch from message #6 runs fine on both Teensy 4.0 and Teensy 3.2. I tried with 2 versions of FastLED: 3.4.0 and 3.6.0, same results. Paul

Ran the exact code from message #6. Runs on Teensy 4.0, does not run on Teensy 3.2. Related is this thread. Paul

Posted an article on the website today with info about how the Windows EXE cross compile and signing works. https://www.pjrc.com/how-to-cross-compile-and-sign-windows-exe-on-linux-with-yubikey-token/ Hopefully it can help other people who want...

You may want to share your complete code (including a reference to the used libraries) in case someone has the same hardware available and would like to try. Please use the </> button in the top-left corner of this window if you want to share...

Here you go. On Windows 10. My Chrome browser downloaded it fine, hello2.exe runs fine from command line. Paul

Probably the Teensy 4.1 can change pins faster than the 74HC595 can handle. Teensy 4.1 is way faster than a Teensy LC. Sprinkle a number of delay(1);'s in the updateShiftRegisters() function like so: void updateShiftRegisters() {...

Yes, your design will do. Set the sine module output to 1.0 and set the attenuation or amplification at the amp module. Paul

It looks like you are restarting an old thread. You better continue the old thread. Did you follow all the advice given by @defragster, @mjs513 and @BriComp? Paul

Or short press-fit header pins? Link. Paul

In combination with these kind of pins for the Teensy? Link. Paul

Are these an option? 2.11 mm clearance. Specification here. Paul

Pff, too many variants of ESP32 boards around. Also chip pin numbers != board pin numbers != GPIO numbers. Look at the pinout. Found this in the datasheet of the chip: You would have to use board pin numbers 16 & 17 [GPIO16 & GPIO 17]. This...

It looks like you have this board. Problem is that the TX & RX signals of the ESP32 chip connect to [1] the external TX & RX board pins and to [2] the onboard "USB-to-UART Bridge". So you are using the same serial port for Teensy communication...

On Teensy pin 0 is RX and pin 1 is TX. If you have them wired as you state above you have RX going to RX and TX going to TX. RX should go to TX and TX should go to RX.

Strangely enough, I couldn't get DeviceExample.ino to work with SoftwareSerial also. So I tried using hardware serial on pins 0 & 1 instead. That works! Mind you: I had to connect Teensy TX1 to module pin RX [green wire] and Teensy RX1 to module...

Where in your code do you actually read out the data from the GPS module? From this page: Perhaps it's a good idea to get the DeviceExample.ino [using SoftwareSerial and your pins] operational first and then move to HardwareSerial. Paul

For a really basic test of the DAC, I would get rid of the MIDI code and just send a digital value to each of the DAC outputs and measure the voltage on that particular pin. Did you try your code above? Did it work? Paul

Tried the above code on a different ESP32 module and it works. This DOIT ESP32 DEVKIT V1 module also shares the first serial port [TX0 & RX0] with the onboard serial-to-usb converter and thus is not usable for external comms. So had to use TX2 &...

If I understand this section of the FireBeetle board WIKI correctly, pins 1 & 3 are used for the serial communication to the PC/Arduino IDE. For a comm link to the Teensy, you need to use UART2 (Serial2) on pins 16 & 17. Your code would look like...

Hi Jordan, no, unfortunately that doesn't work that way. Thing is you can only send bytes (values if you like) over the LIN bus. Electrically they are just 0's and 1's. What these bits mean, is up to us. We start with a lin.order() command and...

Actually not... Serial0.begin also works for the ESP32-C3 UART #1. void setup() { Serial.begin(115200); Serial0.begin(9600); Serial0.setTimeout(100); } void loop() { while (Serial0.available() > 0) { Serial.print("Message received...

Well, gave it a try myself. Took me some time to find out that I had to use the HardwareSerial class to receive data by my ESP32-C3 SuperMini board... Anyway, it's working now: Teensy 4.0 code: void setup() { Serial1.begin(9600); } void...

While @AndyA's remark is certainly valid, I would focus on the serial port connection first like @jmarsh indicated. Your Teensy code should look like this: void setup() { Serial1.begin(9600); } void loop() { Serial1.println("Hello Boss")...

This looks perfectly acceptable to me. Paul

So you have been using (and are using) an external USB hub all the time? Is it possible to test without this hub? Also, the timing remark by @MatrixRat does make sense to me. Paul

Found this schematic with resistor values [but not LED Vforward]: If that resistor value of 330Ω is true, a Teensy pin outputting 3.3V will probably not get the optocoupler LED to conduct sufficiently. Paul

On the pinout card, the yellow-background signals are all related to digital audio I/O. They can also be used for other purposes if you don't use these particular signals. Paul

Teensyduino comes with its own PulsePosition library. You should delete the one here C:\Users\Primary\Documents\Arduino\libraries\PulsePosition. Then your code compiles fine (just tried). Paul

Assuming you used this Rotary encoder library, I got it to compile with 2 errors: Then I looked into the Teensy Joystick example [File > Examples > Teensy > USB_Joystick > Complete.ino] and there I noticed this piece of code: void loop() { //...

As a follow-up to anyone who is coding for a LIN-bus, I opened an issue (with the simple fix) on the LIN-bus library on Github. Paul

Teensy does not use a hardware serial port for uploading. Instead it uses a "virtual' serial port over USB [under the hood, it is a bit more complex than that but for basic understanding OK to work with]. That same virtual serial port is also...

Looking into the Teensy RadioHead library, in the examples/Teensy folder, I noticed the README.md states: In your code, you use #define RFM69_INT digitalPinToInterrupt(3). Perhaps you should connect the G0 (IRQ) signal to Teensy pin 0 or 1...

When I look at Mouse.ino, I think the code should be: #include "USBHost_t36.h" USBHost myusb; MouseController mouse(myusb); USBHIDParser hid1(myusb); USBHIDParser hid2(myusb); void setup() { Serial.begin(115200); myusb.begin(); } void...

Great result! Happy to be of help in reverse engineering in what was nearly a black box [but not any longer now]. Well, I hope you get the other heaters to communicate as well! I will check the wiki page every once in a while. Paul

Both commenting _stream->read(); and modifying data[i-3] = tmp[i-1]; serve the same purpose: correcting the wrongly shifted byte. So you should choose either one. When I run your code, I get this response: Same response but correctly shifted by...

No warnings. No. Tried both Fast and Smallest. Related are this thread and this thread. Paul

There is a RawHID example. In the Arduino IDE, open File > Examples > Teensy > RawHID > Basic Paul