CAN-View Software Updates

i just checked the website and it still has the jan 26 versions up. is this the new file with the old name?

 

there on the bottom of the download page when I checked.

 

These last updates are for "now" beta test and for specific users with specific problems, probably not recomended to everybody to use.

Correction:
My appologies to the forum, I miss these last updates. This afternoon where not there.

 

it's the three below the frenchie and horatio test codes, starting with CVfeb096,

 

well im not seeing it. guess i'll try flushing my cache

 

thanks EVAN that did it... oh well, time to flush the cache anyway

 

Not seeing an updated web-page is usualy your browser set to not check for new page every time; hitting the 'refresh' icon is the quickest fix.

To answer Dolio in this thread now that Evan's set it up, MPG data is not on the CAN or AVC, but the basic elements are: Toyota reports speed in one km per hour increments and fuel burn in ~0.1 litre/hour increments. Any display in other units for different countries is always calculated back to these basics.

So just divide speed by fuel and then convert from km to miles and litres to US gallons. Took me 2 days to remember how to do 16 bit division properly.

I think it's important to realise what these short-lived real high mileage numbers mean, so we don't read too much into them. Yes, I can see 230mpg dawdling along a local flat road. And yes it helps to increase the overall real mileage. But you should realise what the numbers are based on before we get a bunch of ' I got 235mpg and you only saw 227mpg' posts.

mpg is speed (miles per hour) divided by fuel burn rate (gallon sper hour)
So as the fuel burn rate gets progressively smaller for these very high mpg figures, the resolution of the result begins to suffer. For example, suppose at 35mph by some means you manage to burn just 0.15 usg/hour, resulting in 233 mpg. The smallest possible change to this is the 0.1 litre (or 0.0268 usgallon) increment reported by CAN, so that changes the answer to 35/(0.15+0.0268) =198mpg Its not that it suddenly dropped from 233 mpg to 198mpg, its that the Prius only reported the fuel flow change to that resolution. In contrast, at normal rates of say 60mph and 1.2usg/hr for 50mpg, each increment is only2% and so not so obvious. Any attempt to filter these results in software is just making a pretty display, its not showing the real result.


I knew this would then lead to someone saying, well why can't also we have average mpg over a longer time or distance? This is much more complicated because it means keeping track of all speed and fuel data constantly and with all the housekeeping tasks CANview has to do this is not a simple matter. I suspect the Prius manages average mpg because it has a much more powerful processor and very little else to do. I am trying something similar with Amp-hours and by not collecting every single message while I handle other things, I build up a significant cumulative error. It needs a new approach to recognise vital messages and process every one, but recognise relatively unimportant repeat messages ando do the necessary chores during them. It can probably be done, but don't expect it too soon.

 

I just want to take this opportunity to point out how fortunate we are to have Norm working on this nifty widget. While I'm feeling a little deprived that I haven't had a chance to connect with my neighbor tomdeimos and update to newer (or newest) code yet, and a little guilty that I'm not really contributing to the 'effort' (I try not to drive around too much,) I'm still sort of amazed (and definitely thrilled) that Norm is popping out these updates like this.

Thanks again Norm!
Joel

 

What would we do without Norm??
If I was an avid Republican I's say "MegaDittos"! But I'm not too avid anymore.
Arnie

 

any thoughts on the mystery graph?? it seems to only run when the ICE does. i rotated each graph option with the mystery to see if any seemed to match. although it doesnt vary in any discernable ratio with ICE RPM, it does come on at the same time the ICE does.

 

Evan suggests that instead of X2 size display going blank at 255 mpg, it be infinity or at least '---' My limited X2 char set means I can't offer the logical infinity sign, but I can put in '!!!!' or '****' or '----'
preferences?
hmmm, space for 4 letters possible... if you drive really carefully, your mpg can get to 'evan'? sorry, bad pun, couldn't resist.


Also as the amount of time >100mpg is very limited, should I scale the graph portion alone to be say 100mpg =full scale bar, (but leaving the numbers to go to 255) so its more useful in 'normal' driving
Preferences?

 

I vote for doing similar to Toyota!

For graph: go to 100 and when higher just read 100.

For text: go to 255 and when over just read 255.

 

how about ∑...


! to me means an error (which in this case maybe true)

? means unknown (the rate could be figured if we determined how much gas it takes to burn to get a certain amount of charge and factored in how fast we were dissipating the charge

or we could use Џ to symbolize a goal or "touchdown" metaphorically.

or maybe

Ө to symbolize hybriditiy... half gas half electric...since the electricity came from the gas...

or maybe ♫ to symbolize "humming along in EV?"


or maybe...ok maybe im getting carried away by the character map. you say you can do 4 characters??? how about 9999?

 

include my vote for "evan"

 

boy your going to do a double take when it goes from 9999 down to 198, I'll probably hear you scream all the way up here.