Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Routes have incorrect starting point and reporting 2x actual mileage. #548

Open
Memberoffoxhound opened this issue Aug 3, 2024 · 7 comments

Comments

@Memberoffoxhound
Copy link

Memberoffoxhound commented Aug 3, 2024

  • Comma 3 0.9.7-release Dongle 49734429dda9bbe7
  • 2x mileage issue began approximately 7/14/24
  • Secondary issue of incorrect starting location began approximately 7/16/24
  • Both issues continue today on every route
  • Troubleshooting has included rebooting device and reinstalling openpilot. I have not reflashed or tried to unpair/repair in connect.

Longer description:
On routes from 7/14/24 connect seems to have around double the miles reported for each route. Even stranger starting on 7/16/24, all routes have a starting location in Chesterfield,MO regardless of my actual location. Chesterfield is where I work and 40 miles from home.

I am on stock release and did attempt to reinstall openpilot. I haven’t done anything too extreme yet such as reflashing my comma 3 and I haven’t seen any mention of this anywhere else. The route below should be approximately 12 miles but shows 24. I started in Godfrey, IL despite it showing a starting point 40+ miles away in Chesterfield.

https://connect.comma.ai/49734429dda9bbe7/00000000--3324219164

image

@Memberoffoxhound
Copy link
Author

Small update. Decided to re-flash the device tonight using the web utility and switch from stock to a fork. Both issues persist using sunnypilot. Moving back to stock release at this time.

TL;DR

  • Re-flashed comma3 from web utility
  • Switched from stock to sunnypilot fork
  • Both starting point and 2x mileage issues remain
  • Switching back to stock

@Memberoffoxhound
Copy link
Author

Re-paired device on connect. No change.

@m01001100
Copy link

I have the double mileage issue with two separate vehicles using C3 and C3X. Using free version of connect with stock release. Haven't made any attempts to troubleshoot.

@Rocketboy235
Copy link

Rocketboy235 commented Sep 7, 2024

Also experiencing this issue on stock OP after factory reset. Also happened to me while on sunnypilot previously so I can at least confirm that it's a connect issue which may have been obvious from the start.

74b008694de53cc1/0000000b--10878abe6f/0
74b008694de53cc1/0000000c--c967ef9fda/0

Also, been seeing this from previous drives where the starting point starts in the ocean :)
chrome_IRR1aIM8VL

@EasternPA
Copy link

EasternPA commented Sep 8, 2024

I bought a used Comma 3 on July 17th. It was removed from the previous owner's account before we met to make the deal. Every single drive I've ever taken with it has started in the parking lot where we met for the sale. I've run OP devel, SGOP20v2, and SP dev. Always the same.

Edit: dongle id: 34346a8b72e53406

@Memberoffoxhound
Copy link
Author

I have the double mileage issue with two separate vehicles using C3 and C3X. Using free version of connect with stock release. Haven't made any attempts to troubleshoot.

Please post your dongle ID at least so comma will have something to look at.

@Memberoffoxhound
Copy link
Author

I bought a used Comma 3 on July 17th. It was removed from the previous owner's account before we met to make the deal. Every single drive I've ever taken with it has started in the parking lot where we met for the sale. I've run OP devel, SGOP20v2, and SP dev. Always the same.

Please post your dongle ID at least so comma will have something to look at.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants