PaulS
Reaction score
34

Latest activity Postings About

    • PaulS
      PaulS replied to the thread Teensy 3.2 End Of Life.
      Mouser even has 15K+ pieces on stock. I would buy Teensy 3.2 if they are available - I have actually never needed the processing power of the T4 [and the related power consumption]. Paul
    • PaulS
      PaulS replied to the thread Schematic different.
      Agree. Like his other post. Paul
    • PaulS
      PaulS reacted to WMXZ's post in the thread Schematic different with Like Like.
      @AndyA. The prev message (WillimamsimC) seems ChatGPT generated an should, MHO, be considered Spam
    • PaulS
      It's related to the SdFat library. Syscall::yield and SysCall::halt were apparently removed in V2.1.1 of the library. Paul
    • PaulS
      Thanks a lot! Wish I would have known this feature long time ago... Paul
    • PaulS
      A 1920x1200 PNG file can be uploaded without problem. So perhaps shrink your photo? Paul
    • PaulS
      Reviewing the board files and the schematic, I think the power supply to the Teensy is fundamentally not correct. In the schematic, the Vin pin is labeled "+3.3V". That 3V3 comes from a regulator mounted on JP13. 3V3 is too low to power the...
      • 1712687894392.png
    • PaulS
      In Eagle, you can [1] "Print to File (PDF)" which looks very readable, or [2] File > Export > Image. Choose resolution '300dpi' and it will output a very readable PNG image. Your design seems to be done in Eagle 9.7 which I can not open in...
    • PaulS
      OK, took me a while to figure out you meant BOB-10124... This board. It is indeed not really clear from the schematic and silkscreen on the PCB but the RTS signal should be connected to pin 4 of J9: The LED will be ON when transmitting and OFF...
      • 1712512699737.png
    • PaulS
      PaulS replied to the thread GPS not working when integrated.
      Had a look at your code but nothing obviously wrong stood out. What if you integrate only 2 sensors at a time [BME680 & MQ135 or BME680 & GPS or MQ135 & GPS]? Any combination that works? I guess it is a matter of commenting out parts of your...
    • PaulS
      PaulS replied to the thread Using Waveshare 1.14" w/Teensy 4.1.
      Welcome to the forum. You may want to share more and higher resolution pictures. I tried to see where the wires go from the display to the Teensy, but it's not discernible. Please share a schematic and your simplest code that shows the issue...
    • PaulS
      I think it changed here. I assume it was for a good reason then - hope it's not going to bite us somewhere else now. Anyway, thanks very much to @PaulStoffregen and @jmarsh after indepth sleuthing! Paul
    • PaulS
      Could it be a timing issue with the one-wire interface? Teensy 4.x is pretty fast so perhaps some timing could get on the edge. Heating and/or cooling the IMXRT1062 chip carefully might reveal something. Paul
    • PaulS
      I had a quick look, I think I know what the cause is but I'm not sure of a few details. If you look at the memory allocated immediately before the ClocklessController there should a 4-byte guard variable. Guards are generally used for local...
    • PaulS
      Yes, sounds good to me. I'm running it now and FastLED seems to be working. Committed the fix just now! https://github.com/PaulStoffregen/cores/commit/638a2079d290e3d6683aeceb07b6dfd8b09151a9
    • PaulS
      PaulS replied to the thread Teensy 4.1 fuse location.
      Did you measure that 2.5V on the Teensy VIN pin? Is the Teensy powered over USB? Paul
    • PaulS
      PaulS replied to the thread MODBUS TCP.
      I suppose you are trying to read out these registers? Not sure whether I can be of any help here. I think you just have to fiddle with the settings until you read something that looks valid. Paul
      • 1712258201143.png
    • PaulS
      PaulS replied to the thread MODBUS TCP.
      This is a bare PT100 “Resistance Temperature Detector”. It's basically a resistor so it does not output a current. You can not hook up such a resistor to a 4-20mA current loop. Whatever circuit you will be using to measure the resistance [and...
    • PaulS
      PaulS replied to the thread MODBUS TCP.
      Do you have a datasheet or part# for that transmitter? Paul
    • PaulS
      PaulS replied to the thread Sampling voltage with Teensy 4.1.
      It may well be a worn-out or low quality breadboard. Breadboards vary a lot in quality. A lot of chinese breadboards are very cheap but low quality - you get what you pay for! Two brands stand out: 1. BPS [BusBoard Prototype Systems]. I have...
    • PaulS
      PaulS replied to the thread MODBUS TCP.
      Did you check the sub-settings as well? See the manual, paragraph 5.7.4 Analog Output (AO) and 5.7.4.1 AO Detail Settings. OK, but what voltage did you actually measure then? You said "it doesn't match the intended 2V" so I'm curious what...
    • PaulS
      PaulS replied to the thread MODBUS TCP.
      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
    • PaulS
      PaulS replied to the thread Teensy 4.0 / High Voltage Heater.
      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...
    • PaulS
      PaulS replied to the thread Teensy 4.0 / High Voltage Heater.
      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...
    • PaulS
      PaulS replied to the thread Teensy 4.0 / High Voltage Heater.
      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...
      • 1711886478712.png
    • PaulS
      PaulS replied to the thread Teensy 4.0 / High Voltage Heater.
      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...
      • 1711880230069.png
    • PaulS
      PaulS replied to the thread MODBUS TCP.
      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 =...
    • PaulS
      PaulS replied to the thread EtherCat on Teensy 4.1?.
      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
    • PaulS
      PaulS replied to the thread EtherCat on Teensy 4.1?.
      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...
    • PaulS
      PaulS replied to the thread Teensy 4.0 / High Voltage Heater.
      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...
    • PaulS
      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...
    • PaulS
      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...
    • PaulS
      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
    • PaulS
      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...
      • 1711206268306.png
    • PaulS
      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
    • PaulS
      Ran the exact code from message #6. Runs on Teensy 4.0, does not run on Teensy 3.2. Related is this thread. Paul
    • PaulS
      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...
    • PaulS
      PaulS replied to the thread 8 x 8 button matrix help.
      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...
    • PaulS
      Here you go. On Windows 10. My Chrome browser downloaded it fine, hello2.exe runs fine from command line. Paul
      • 1711042012509.png
      • 1711042034091.png
    • PaulS
      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() {...
    • PaulS
      PaulS replied to the thread Simple audio sine signal generator.
      Yes, your design will do. Set the sine module output to 1.0 and set the attenuation or amplification at the amp module. Paul
    • PaulS
      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
    • PaulS
      Or short press-fit header pins? Link. Paul
      • 1710831911516.png
    • PaulS
      In combination with these kind of pins for the Teensy? Link. Paul
      • 1710830266748.png
    • PaulS
      Are these an option? 2.11 mm clearance. Specification here. Paul
      • 1710829279876.png
      • 1710829412442.png
    • PaulS
      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...
      • 1710747160713.png
    • PaulS
      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...
      • 1710712959514.png
    • PaulS
      PaulS reacted to BriComp's post in the thread GPS not working with Teensy 4.1 with Like Like.
      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.
    • PaulS
      PaulS replied to the thread GPS not working with Teensy 4.1.
      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...
      • 1710687542347.png
      • 1710687629970.png
    • PaulS
      PaulS replied to the thread GPS not working with Teensy 4.1.
      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
  • Loading…
  • Loading…
Back
Top