Forum Rule: Always post complete source code & details to reproduce any issue!
Results 1 to 3 of 3

Thread: query about teensy

  1. #1
    Junior Member
    Join Date
    Nov 2022
    Location
    Kathmandu, Nepal
    Posts
    1

    query about teensy

    Hello ,i am new here. I am trying to make a flight computer using MPU6050 gyro sensor, BMP390 and GPS module NEO-8MN. i used them with esp32 and it took great time than expected to process data from each sensors in one iteration. now hearing about the processing speed and applications of Teensy boards, i want to use it for faster response. can teensy gets me what i need?

  2. #2
    Senior Member+ defragster's Avatar
    Join Date
    Feb 2015
    Posts
    16,504
    This is long and old thread using T_3.6 : pjrc.com/threads/48856-uNav-INS?highlight=unav

    It was doing GPS at 10/sec and IIRC could sustain 500 9 DOF at 500+ cycles per second (A T_3.5 IIRC was capable over 400/sec) while doing full calculations as discussed on that thread.

    Using a T_4.x it should be capable of more calculations between the sampling.

    That 500/sec came when all the data was also being sent off using SPI to a second Teensy where it used all of it cycles receiving the resulting data and pushing it out USB to a PC for viewing.

    That thread shows the names of users involved - not sure of newer threads using T_4.x - but Brian on that thread is actively involved with flight control doing this with Teensy.

  3. #3
    Senior Member brtaylor's Avatar
    Join Date
    Mar 2016
    Location
    Santa Fe, NM
    Posts
    801
    Yes, we do professional flight control and data acquisition systems with Teensy and it works great, especially with the dual precision FPU on Teensy 4.x. Depends on how fast of a response you're looking for, it typically takes our systems a little over 1 ms to collect sensor data and perform state estimation. We typically run our flight control systems at 100 Hz (10 ms frame period) and our data acquisition systems at 200 Hz (5 ms frame period). Keep in mind that we've been doing this for a while and generally optimize the hardware and software to work well for these applications. We set a fixed latency between sensing and actuation for our flight control systems to 90% of the frame period (i.e. 9 ms).

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •