Mileage calculated incorrectly - Fuelly Forums

Android Users - Coming Soon! - Migrating from aCar 4.8 to 5.0

Reply
 
Thread Tools Display Modes
 
Old 08-15-2014, 02:10 PM   #1
Registered Member
 
Join Date: Jul 2010
Posts: 6
Country: Canada
Location: Mississauga, Ontario
Mileage calculated incorrectly

The mileage for #235 is incorrect. It shows 20 but should be 373.

#235 14-07-18 20.00 31.10 155.46 1.040 odom=166246.0
#234 14-07-18 671.00 64.67 9.64 1.019 odom=165873.0

Thanks.
__________________

gory is offline   Reply With Quote
Old 08-15-2014, 02:31 PM   #2
Registered Member
 
RobertV's Avatar
 
Join Date: Feb 2013
Posts: 1,900
Country: United States
Location: San Antonio, TX
After reviewing your Log, it looks like your July 5th fill-up may be incorrect. The odometer noted was 166226 which is way off compared to the fill-ups around it. Please double check that it is correct and edit as necessary.

Thanks!
__________________

RobertV is offline   Reply With Quote
Old 08-15-2014, 03:23 PM   #3
Registered Member
 
Join Date: Jul 2010
Posts: 6
Country: Canada
Location: Mississauga, Ontario
GREAT! That was it. Funny though. Does fuelly use the odometer readings or dates for sorting, or both? I'm guessing it uses the odometer readings to calculate the distances regardless of date, but then sorts according to date and time? I've found that I've had to add times in some times in order to get things to work correctly. Does this make sense?

Maybe it would be nice if you could add in an odometer column in the standard list view. It might help to catch errors too.

Thanks for all your great work!
gory is offline   Reply With Quote
Old 08-15-2014, 09:46 PM   #4
Registered Member
 
RobertV's Avatar
 
Join Date: Feb 2013
Posts: 1,900
Country: United States
Location: San Antonio, TX
Fuelly calculates distances by Odometer readings regardless of date, but sorts by date on the Log Book.
If you input 2+ fill-ups on the same date at the same time (adding in past receipts) while they may be sorted in the wrong order (newest input first therefore oldest is entered last and on top) as long as the Odometer readings are right, all calculations will still be correct.

We're looking to implement more error-catching upon input of fill-ups to help cut down on instances like this.

Thanks!
RobertV is offline   Reply With Quote
Reply

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are Off
Pingbacks are Off
Refbacks are Off


Powered by vBadvanced CMPS v3.2.3


All times are GMT -8. The time now is 04:50 PM.


Powered by vBulletin® Version 3.8.8 Beta 1
Copyright ©2000 - 2017, vBulletin Solutions, Inc.