Fejemis Teensy: Difference between revisions
| Line 18: | Line 18: | ||
== Software structure == | == Software structure == | ||
[[File:teensy-firmware.png]] | |||
Figure: The Teensy software is structured with a main loop and a number of units. After reset all units are initialized in a setup function, after that the Main loop is entered. The main loop services commands from USB is send to the units for implementation. At regular interval, the sample clock tick, all units are called to execute any sample time function. Most units are interfaces to external devices such as IMU, motor drive or distance sensor. There is further support units for e.g. control. | |||
=== Setup - loop overview === | === Setup - loop overview === | ||
Revision as of 07:25, 29 July 2022
Back to fejemis
Drive Teensy
Block diagram with all interfaces and interface protocol
Front Teensy
Block diagram with all interfaces and interface protocol
GUI
Using USB
Using the bridge
Software structure
Figure: The Teensy software is structured with a main loop and a number of units. After reset all units are initialized in a setup function, after that the Main loop is entered. The main loop services commands from USB is send to the units for implementation. At regular interval, the sample clock tick, all units are called to execute any sample time function. Most units are interfaces to external devices such as IMU, motor drive or distance sensor. There is further support units for e.g. control.
Setup - loop overview
Main and module integration code
Module structure
One file one interface.
Subscription
Standardized setup of data subscription
Command decode
On-line help.
Configuration save
Use of configuration flash.
Update tick
Sample rate and sensor calculation
