Hi, just started my roadtrip to Germany, noticed the odometer / distance to empty no longer updates, the odometer was being read directly off the CanBus. I also noticed the mileage does update when I turn off the car. Was working perfect in previous versions, seems to have stopped working in 2.5.0
Anyone else has the same issue?
Thanks
Ian
My mileage is saved only when I am connected to the internet
It should be reading from the CANBUS, itās only updating when I cycle the ignition, very strange, my guess is that because the mileage is stuck itās not calculating distance to empty
Check 2.5.1 if that fixes the issue.
@realdashdev tried the range calculation today and while I was getting up to 25km/L fuel consumption, with 50 litres in the tank, the range (DTE) never went above 108 km, this is on 2.5.1
There was an update for this. RD has internal ālong termā consumption that did not work properly. The Range should catch up to correct reading within next hundred kilometers. Another option is uninstall/install cycle to catch up on range immediately.
So updated to 2.5.1
, have the same issues, odometer from the CanBus is not updating until ignition is recycled and distance to empty after 100km still hasnāt updated
Now Iām back from Germany, Iāve had a proper look, the mileage is definitely not updating, should be simply reading from the CANBUS target ID is 310, only updates when ignition is cycled
Distance to empty is using Range (calculated), the Debug screen has a different value to what is displayed on the dash see screen shots, I also tried removing the input and re-adding, still get the wrong number and itās static
For range, it looks like you are using Miles as a distance unit. Debug Data View shows raw data, which is in Kilometers.
Ah that makes sense, so iām still stuck then, odometer doesnāt update until ignition is cycled, Range is not updating at all.
RealDash reads vehicle speed? That is required to calculate consumption and range.
Donāt know why you need to cycle the power in order to make proper connection. How does your boot cycle work on the device?
All other data pids are fine from what I can see, itās just the odometer, I have a video after a very short trip showing the odometer change only once the ignition is turned off, the connection to the CAN is stable and doesnāt drop out.
Iāve checked all the settings and canāt see why this particular value has this behaviour, tomorrow Iām going to map to a custom input and see if that makes a difference
Update: I found the odometer issue; the CANID I was using only updates when ignition is turned off, I did some more sniffing and found another ID, this updates realtime - this is now fixed.
So just the ācalculated rangeā now to sort out.
@realdashdev in the diag screen Iām seeing āserial parsing error countā counting up after 725 seconds is about 17200 errors
What CAN adapter you are using? Seeedstudio and Waveshare adapters produce a lot of errors when ran at high baud rates.
Iām using the WiCan, I did another long run yesterday, the calculated range is still showing the 216miles (I also filled the tank), what else should I check?
How is the range calculated, what other data from the car does it use other than vehicle speed?
Range is calculated from average fuel consumption (from Trip A) and Fuel Amount (calculated).
So Iām confused, it was working before 2.5.0, I have fuel level % from the car going to target ID 170 and it calculated the range, now itās just showing a static value for range (calculated)
If itās using fuel amount calculated, is that being calculated from the tank capacity in the settings and then the fuel level from target is 170?
So fuel amount calculated would be 100% of tank capacity when full?
Sorry if Iām being a pain, Iām assuming a change was made that broke something at this point I canāt see what I need to do to fix it
EDIT:: I think Iāve found a workaround;
Iām now taking my fuel level % from the CAN, dividing by 100 and multiplying by my tank capacity, this then is passed to target id 222 (Fuel Amount (calculated)). The range then looks reasonable, however the trip A average fuel consumption is still zero. Will test over the next few drives to see how I get on.
It could be that Fuel Amount (in liters) is only updated from calculated fuel level. I will check this.
Edit: Are you using Input Mapping for fuel level? Check āSettings->Units & Values->Input Mappingā
