1. Attachments are working again! Check out this thread for more details and to report any other bugs.

Prius C Panel Displays to ODB event mapping

Discussion in 'Prius c Care, Maintenance and Troubleshooting' started by thedarave, May 24, 2013.

  1. thedarave

    thedarave Junior Member

    Joined:
    Apr 17, 2013
    41
    22
    0
    Location:
    Yokosuka, JP
    Vehicle:
    2013 Prius c
    Model:
    Two
    Has anyone actually gotten around to mapping the various status displays the Prius C has on the dash to the various ODBII codes to make similar displays in Torque? If not, would there be an interest in working on mapping these out?
     
    minkus likes this.
  2. minkus

    minkus Active Member

    Joined:
    Jan 4, 2013
    369
    125
    0
    Location:
    Cleveland, OH
    Vehicle:
    2012 Prius c
    Model:
    Two
    Torque app forums: Prius C Custom PIDs | PriusChat

    Yes, I'd be interested! Someone in that thread provided a file to be tested, another person volunteered to test the codes out, but nothing else has happened since.
     
    RocMills likes this.
  3. thedarave

    thedarave Junior Member

    Joined:
    Apr 17, 2013
    41
    22
    0
    Location:
    Yokosuka, JP
    Vehicle:
    2013 Prius c
    Model:
    Two
    Ok, I've imported all of those and will start working on this. Next question: Is there a Prius C specific community wiki yet? If not, I'll build one so there's a place for me to work on this out of. It might be a good place for people to store links to aftermarket parts / project how-tos as well. It would make cross linking and updating a little easier than constant forum searches that can sometimes spit out some misleading results.
     
    minkus likes this.
  4. thedarave

    thedarave Junior Member

    Joined:
    Apr 17, 2013
    41
    22
    0
    Location:
    Yokosuka, JP
    Vehicle:
    2013 Prius c
    Model:
    Two
    Meh. Screw it. Made one on Wikia just so I have a place to dump things. Use it, don't use it. Whatever.

    Prius C Wiki
     
    minkus likes this.
  5. thedarave

    thedarave Junior Member

    Joined:
    Apr 17, 2013
    41
    22
    0
    Location:
    Yokosuka, JP
    Vehicle:
    2013 Prius c
    Model:
    Two
    Ok, just tested a few different ones to see what's working and not working. These are ones that I would consider "critical items", but most other people would probably disagree with me on that. I spent 9 hours (and about 310 miles) doing city driving yesterday to try to shake out some of these gauges. Here's some observations:

    Coolant Data @ 2101|7E0 spits out info that mostly makes sense, but the formula leaves me scratching my head. I * 9 / 5 - 40 looks almost like a conversion from Fahrenheit to Celsius, but it looked like it was implemented incorrectly. After a bit of playing around with a calculator to try to break the formula, it turned out to be quite sound. Proof of function: I=10, J=128
    I*9/5-40 -- 10*9=90, 90/5=18, 18-40=-22F
    (I-40)*9/5+32 -- 10-40=-30, -30*9=-270, -270/5=-54, -54+32=-22F
    J*9/5-40 -- 128*9=1152, 1152/5=230.4, 230.4-40=190.4F
    (J-40)*9/5+32 -- 128-40=88, 88*9=792, 792/5=158.4, 158.4+32=190.4F

    Coolant Data @ 2123|7C0 -- I have NO friggin' clue what's going on here. I either get transported to one of the arctic poles the second I sit in my car, or this formula needs a SERIOUS overhaul. I was routinely seeing negative numbers (-37.8 was todays average, with coolant data @ 2101|7E0 telling me ~158.) and they would flux up and down quite a bit. I'd need more time to research what's going on here. It might be a raw read of the output of the coolant from the ICE, but I can't pay attention to both the road and the tablet for obvious and legal reasons. Also, the US formula here is correct. The /2 from the metric formula gets merged in with the /5 from the F->C conversion to give a *9/10+32. Proof: A=10
    SIGNED(A)/2*9/5+32 -- 10/2=5, 5*9=45, 45/5=9, 9+32=41F
    SIGNED(A)*9/10+32 -- 10*9=90, 90/10=9, 9+32=41F

    MG1RPM @ 2161|7E2 confirmed working and correct.
    MG2RPM @ 2162|7E2 confirmed working and correct.
    ALL MG1/MG2 temps, including the inverters appear to function as expected. I will test for overload at some point by finding a decent size mountain to drive down in "B".

    Regenerative Requested and Regenerative Operation 2148|7B0 -- Works, but only sort of. Caps out at 27.3 using the existing formula. A and C do not appear to spit anything out. B and D might be the only units used for these two units in the "C". I need more data and a LONG underutilized parking lot to test in. Note: This seems to cap at a raw output of 37, if that makes sense to anyone. For binary, this makes ZERO sense, as it wastes an entire bit for the ability to spit out a total only 6 higher than if it used one less bit.

    State of Charge (ALL) @ 2101|7E2 -- Incorrect, most likely NOT what this is. Use State of Charge @ 015B|7E2 instead. This was reflecting WEIRD numbers almost the entire time. I spent most of the day's drive at 8.2% varying up to 12%. I've seen this go as high as 90% and as low as 5% when previously used to compare against State of Charge @ 015B|7E2. Not sure what this is supposed to be, but its clearly not a charge state.

    State of Charge @ 015B|7E2 -- Functions as intended, matches readings seen on the dash.

    Aircon Gate Status @ 2175|7E2 -- Always reflects on, even when A/C is off. Might be a "feature exists" reading instead.

    Fuel Input @ 2129|7C0 -- Works, but wasn't what I thought it was at first. This is apparently how much fuel you last added to the vehicle rounded down to the half-liter. The conversion came out to ~7.5 gallons, which was correct for my last fuel up of 7.563 gallons @ $3.58/g

    Cruise Operation Status @ 2121|7E2 -- Always on, even when I have cruise control off. Might just be "feature exists" reading like Aircon Gate Status @ 2175|7E2

    Fuel System Status @ 2103|7E0 -- This one is interesting. Reads 0 when ICE is off, and 2 when on, but the car is in park. I have not observed this while moving. Most likely correct with what is in the formula. More investigation required.

    TORQUE DEFAULT GAUGES-----------
    Fuel Level (From Engine ECU) -- Non functional. Reads nothing constantly.
    Fuel Remaining (Calculated from vehicle profile) -- Spits numbers out, but not ones that make sense.
    Fuel Flow Rates (/m or /h) -- Low. Really Low. Seems to function, but needs tweaking to fit the "C".
    RPM Gauge -- Functions, but I can't verify accuracy. Seems to be about right though.

    -------------------------------------------------

    There was another set of Prius PIDs that I was working with previously. One of them seemed to be a fairly close approximation of the current fuel level. I'll have to find that sheet and see if I can tweak the formula to fit. There were other functions in there as well that might apply. It also seemed to be updated as recent as February/March of 2013. I'll look for it again and post a link.
     
    minkus and ftl like this.
  6. ztanos

    ztanos All-around Geek!

    Joined:
    Jan 10, 2013
    3,339
    1,150
    40
    Location:
    Cumming, Georgia
    Vehicle:
    2012 Prius c
    Model:
    Four
    The fuel remaining is accurate... unfortunately, every single time you refill the car, you have to go back into your profile and tell it 100%. It gets old quick, but it drops accurately whenever you do.
     
  7. thedarave

    thedarave Junior Member

    Joined:
    Apr 17, 2013
    41
    22
    0
    Location:
    Yokosuka, JP
    Vehicle:
    2013 Prius c
    Model:
    Two
    I wonder if its possible to get that to latch to a change in Fuel Input @ 2129|7C0? Might have to go talk to the Torque programmers about that.
     
  8. ztanos

    ztanos All-around Geek!

    Joined:
    Jan 10, 2013
    3,339
    1,150
    40
    Location:
    Cumming, Georgia
    Vehicle:
    2012 Prius c
    Model:
    Four
    Would be worth a try, anyhow... but definitely above my pay grade as far as programming goes. ;)
     
  9. thedarave

    thedarave Junior Member

    Joined:
    Apr 17, 2013
    41
    22
    0
    Location:
    Yokosuka, JP
    Vehicle:
    2013 Prius c
    Model:
    Two
    I have a possible solution:
    Mode and PID: 2129
    Long Name: Fuel Level
    Short Name: Fuel
    Minimum: 0
    Maximum: 9.5
    Scale: 1
    Unit: G
    Equation: A*0.132085
    OBD Header: 7c0

    Would someone else please test this in Torque? I'm getting 6.34008 from this, which is about what I'd expect. It steps in half-liter increments, so its not "real time", but it'll give a better read than the bar gauge on the heads-up if its really what I believe it to be.

    -Steve
     
  10. ztanos

    ztanos All-around Geek!

    Joined:
    Jan 10, 2013
    3,339
    1,150
    40
    Location:
    Cumming, Georgia
    Vehicle:
    2012 Prius c
    Model:
    Four
    I'll check it out. My real question, will it reset the fuel when you refill? or will I still have to do that too? or is that what you are hoping this will fix.
     
  11. thedarave

    thedarave Junior Member

    Joined:
    Apr 17, 2013
    41
    22
    0
    Location:
    Yokosuka, JP
    Vehicle:
    2013 Prius c
    Model:
    Two

    I believe its a raw read on the contents of the tank, yes. That's why I need someone else to test it, I just refilled Friday. -_-;
     
  12. thedarave

    thedarave Junior Member

    Joined:
    Apr 17, 2013
    41
    22
    0
    Location:
    Yokosuka, JP
    Vehicle:
    2013 Prius c
    Model:
    Two
  13. thedarave

    thedarave Junior Member

    Joined:
    Apr 17, 2013
    41
    22
    0
    Location:
    Yokosuka, JP
    Vehicle:
    2013 Prius c
    Model:
    Two
    Confirmed. Fuel Level @ 2129|7C0 is a raw read on the tank. Tested this by letting my C sit idle over night and got a reading of 5.6 steady. Went and shook the vehicle side to side without ever taking it out of park and watched the value slosh from 4.8 to 6.2 and slowly steady back down to 5.6 over a few minutes. For just turning it on to initialize the ECU and then manually rocking it side to side, I have very few doubts as to what this gauge is now. Next trick is to test it for accuracy.

    -Steve
     
    Rob.au and ztanos like this.
  14. thedarave

    thedarave Junior Member

    Joined:
    Apr 17, 2013
    41
    22
    0
    Location:
    Yokosuka, JP
    Vehicle:
    2013 Prius c
    Model:
    Two
  15. Rob.au

    Rob.au Active Member

    Joined:
    Aug 4, 2012
    960
    441
    0
    Location:
    Sydney, Australia
    Vehicle:
    2012 Prius c
    Model:
    i-Tech
    minkus likes this.
  16. hieronymous

    hieronymous Member

    Joined:
    Oct 14, 2012
    154
    92
    0
    Location:
    Auckland, New Zealand
    Vehicle:
    2013 Prius Plug-in
    Model:
    N/A
    I have tested this (metric) and get 8.5L. My display tells me I have 147km range remaining, 680km driven - this result seems correct. Will need to fill up to get a value for a full tank.

    Other matters:
    For SoC my equation has become: A*53/68-58
    I got raw values (A) of approx. 100 where the ICE cut in, so made this SoC 20%, and 168 where the heads-up display changed from bar 7 to 8. Rob.au in a recent post noted his scangauge indicated SoC 73% at this point, so I used this for the equation.
    I tested this up and down a steep little hill nearby, but gave up with 8 very full bars on the display when the raw value got to 204 (didn't use B, but no ICE either). Using my equation gives SoC 100% to be raw 203, so it seems OK.

    From OBD-II PIDs - Wikipedia, the free encyclopedia I have used the standard modes, pids and equations for coolant temp, vehicle speed and revs, to check against Torque's default options, and they all match.
     
  17. Rob.au

    Rob.au Active Member

    Joined:
    Aug 4, 2012
    960
    441
    0
    Location:
    Sydney, Australia
    Vehicle:
    2012 Prius c
    Model:
    i-Tech
    Is that accounting for the SoC not meant to ever be taken up to 100%? The car's battery management is meant to keep the charge away from this - the consensus seems to be the upper limit is 80%.
     
  18. hieronymous

    hieronymous Member

    Joined:
    Oct 14, 2012
    154
    92
    0
    Location:
    Auckland, New Zealand
    Vehicle:
    2013 Prius Plug-in
    Model:
    N/A
    I find various posts on this subject to be a little conflicting - have noted a couple recently where the suggestion was that close to 85% was occurring. Certainly this gauge business is a manufactured construct - you can make it what you want it to be. Having used your observation about where the 73% level occurs, then that is exactly what my Torque gauge shows. It is however simplistic in that the result is linear, whereas the ecu management is at least curvilinear. Would be interesting to know how/whether the scangauge reflects this.

    As to upper limits, well I don't normally repeatedly drive up and down steep streets! I had never seen my heads-up display get to 7 bars before, let alone 8 bars, in my almost 100% city limits driving. Having filled up 8 bars on the hill, just as you have previously noted the car was very strong (eager!) on EV acceleration. But having filled 8 bars there was no indication that the ecu was doing anything to moderate the charging while I was on the hill.

    My view at present is that the ecu takes advantage of higher battery levels, so that in normal driving, even highway driving, the SoC level doesn't get excessive. It is reported that driving down very long hills induces use of the ICE, but I haven't seen any note of what SoC is at the point this starts. What SoC does your scangauge show when this happens?

    The manual says nothing about any of this, including how to use B. My assumption is that when the ecu decides enough is enough it will act, and that I didn't get to that point on the hill. I suspect the concensus on an upper level 0f 80% or so merely reflects ecu management normally being more aggressive in using the traction battery reserve, but that a SoC of 85%+ is perfectly possible. I am happy to be proved wrong!

    In the end I can only construct a linear gauge, so it should reflect my everyday driving, not an extreme.
     
  19. Rob.au

    Rob.au Active Member

    Joined:
    Aug 4, 2012
    960
    441
    0
    Location:
    Sydney, Australia
    Vehicle:
    2012 Prius c
    Model:
    i-Tech
    It doesn't actually take that much to "fill" the battery, but I'd agree it's never happened for me in a built up area, though I have done it in fringe areas of Sydney. It just takes a descent to be long enough where the car has no opportunity to be aggressive with using EV because you're still using regen brakes to regulate your speed.

    When the ICE does kick in, it is very surprising the first time it happens. It is loud and will get louder the more it needs to dump energy. It has been awhile since I last did it and I'll try to watch more carefully next time - my vague recollection is that it comes on at 80% and will fight very very hard to keep it right there. The car does not moderate charging in this situation... if you're on the brake pedal continuously, it'll charge until the point the ICE comes on.

    The manual does touch on using B mode but is very vague about it.

    In normal driving there is now no doubt in my mind that the car targets an SoC of 60%.
     
  20. hieronymous

    hieronymous Member

    Joined:
    Oct 14, 2012
    154
    92
    0
    Location:
    Auckland, New Zealand
    Vehicle:
    2013 Prius Plug-in
    Model:
    N/A
    Having just found this GenIII Prius Custom PIDs for Torque app | Page 11 | PriusChat I am now going back to the original equation for SoC: A*20/51

    The SoC %'s I get for my observed raw values are now as follows:
    boundary bars 2/3 100 39.2%
    boundary bars 3/4 115 45.1%
    boundary bars 4/5 133 52.2%
    boundary bars 5/6 140 54.9%
    boundary bars 6/7 160 62.7%
    boundary bars 7/8 168 65.9%
    top of bar 8 203 79.6% (my peak value on my hill runs)

    The above will mean the ICE will come on at about 40% and 80% - this makes a LOT more sense. The link also reinforces your observation about the 60% level being optimum.

    I will have another hill run to push the level up beyond 80% just to see what it's like...
     
    minkus likes this.