openbikesensor / openbikesensor/OpenBikeSensorFirmware
In rare cases time sent by GPS is not initially correct which leads to wrong filename and hard track rendering
Open
Nobody has claimed this yet.
bug
gps
- Dominant language
- C++
- Stars
- 124
- Forks
- 29
- PR merge metrics
- No merged PRs in 30d
Description
DEV: GPS: TIMEGPS set: 2022-03-12T10:54:21 -> 2022-03-26T10:54:21 0ms.
DEV: GPS: TIMEGPS set: 2022-03-20T12:23:52 -> 2022-03-27T12:23:52 0ms. (GPS Week)
Feels like we should xcheck the date received.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the TIMEGPS handling in the firmware and compare the received dates against the logged GPS Week examples. The issue is done when invalid or unexpected GPS dates no longer produce wrong filenames or prevent tracks from rendering correctly.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- arduino, cpp
- Domain
- embedded-iot
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100