kopia lustrzana https://github.com/bristol-seds/pico-tracker
328ac8ed92
There are three issues with this: * The hardware watchdog cannot be fitted during programming or debugging, as it will override the !RESET! line fromt he debug probe. * The ublox GPS may fail to respond after n position requests, where n is 1000-10000. Either the firmware should be modified to account for this and attempt to reset the GPS, or a watchdog (either hardware or software) should be implemented. * The precision oscillator (TCXO) is connected to the wrong pin on the PCB. The output should be connected to PA14 (pin 15) through the capacitor and resistor divider as used on later revisions. (See the SAMD20 datasheet for more details). Then Line 124 of [inc/hw_config.h](inc/hw_config.h) can be uncommented. Telemetery modes that require precise timing (such as Contestia) require the TCXO to be connected and used for reliable operation. |
||
|---|---|---|
| firmware | ||
| hardware | ||
| sim | ||
| .gitignore | ||
| .gitmodules | ||
| Flights.md | ||
| LICENSE.md | ||
| Notes.md | ||
| README.md | ||
| SAM_D20_Revision_Letter.JPG | ||
| pico-tracker-orig.jpg | ||
README.md
Bristol SEDS Pico Tracker
Gets its GPS position home by whatever means possible, come hell or high water.
(Actually, come low temperatures, long paths, geopolitical restrictions, low power etc.)
Test Flight
On 31st August 2014.