GPS/GNSS UBX protocol test for UART
Dependencies: mbed LoopTicker GPSUBX_UART
main.cpp@1:97c5e20d51a9, 2021-09-17 (annotated)
- Committer:
- cocorlow
- Date:
- Fri Sep 17 15:46:46 2021 +0000
- Revision:
- 1:97c5e20d51a9
- Parent:
- 0:27bfb46452f0
- Child:
- 3:3db7371d08f1
completed!; Do use LoopTicker instead of Ticker.
Who changed what in which revision?
User | Revision | Line number | New contents of line |
---|---|---|---|
cocorlow | 0:27bfb46452f0 | 1 | #include "mbed.h" |
cocorlow | 0:27bfb46452f0 | 2 | #include "GPSUBX_UART.hpp" |
cocorlow | 1:97c5e20d51a9 | 3 | #include "LoopTicker.hpp" |
cocorlow | 0:27bfb46452f0 | 4 | |
cocorlow | 0:27bfb46452f0 | 5 | Serial pc(USBTX, USBRX, 115200); |
cocorlow | 1:97c5e20d51a9 | 6 | GPSUBX_UART gps(PD_1, PD_0); |
cocorlow | 1:97c5e20d51a9 | 7 | |
cocorlow | 1:97c5e20d51a9 | 8 | LoopTicker gps_ticker; |
cocorlow | 1:97c5e20d51a9 | 9 | |
cocorlow | 1:97c5e20d51a9 | 10 | void Display() |
cocorlow | 1:97c5e20d51a9 | 11 | { |
cocorlow | 1:97c5e20d51a9 | 12 | pc.printf("POSLLH: %d, %f, %f, %f\r\n", gps.iTOW_POSLLH, gps.Longitude, gps.Latitude, gps.Height); |
cocorlow | 1:97c5e20d51a9 | 13 | pc.printf("VELNED: %d, %f, %f, %f\r\n", gps.iTOW_VELNED, gps.VelocityNED.x, gps.VelocityNED.y, gps.VelocityNED.z); |
cocorlow | 1:97c5e20d51a9 | 14 | pc.printf("TIMEUTC: %4d/%2d/%2d %2d:%2d %2d\r\n", gps.Year, gps.Month, gps.Day, gps.Hours, gps.Minutes, gps.Seconds); |
cocorlow | 1:97c5e20d51a9 | 15 | } |
cocorlow | 0:27bfb46452f0 | 16 | |
cocorlow | 0:27bfb46452f0 | 17 | int main() |
cocorlow | 0:27bfb46452f0 | 18 | { |
cocorlow | 0:27bfb46452f0 | 19 | gps.Attach(); |
cocorlow | 1:97c5e20d51a9 | 20 | gps_ticker.attach(&Display, 0.5); |
cocorlow | 0:27bfb46452f0 | 21 | while (1) |
cocorlow | 0:27bfb46452f0 | 22 | { |
cocorlow | 1:97c5e20d51a9 | 23 | gps.Update(); |
cocorlow | 1:97c5e20d51a9 | 24 | gps_ticker.loop(); |
cocorlow | 0:27bfb46452f0 | 25 | } |
cocorlow | 0:27bfb46452f0 | 26 | } |