The SGII Xgauge Database

Discussion in 'ScanGauge' started by kmactavi, Jun 4, 2008.

  1. hobbit

    hobbit He who posts articles

    I don't think MG1/MG2 figures are coming any time soon. They
    hide in that big multi-packet blocks that Norm was talking about
    last time we exchanged mail. I'm not sure my little network-
    splitter box can dope that out as it's several packets back
    and forth and the SG isn't going to show me that.
    If I had access to a can-view and could stare at the hex long
    enough while messing with the car, I might be able to narrow down
    some places to look in the passive data -- *if* it's there at
    all. But I don't see any reason stuff like that *should* be on
    the bus since only the hybrid controller cares about it internally.
    Did you at least add injector time? I'm quite confident that
    it's correct now; see the other thread.
  2. kuhl

    kuhl Member

    On the RXF screen that will come up next make the first character an 8, this tells the ScanGauge that the gauge you are creating is to be used as a trip gauge. All values after the 8 are ignored. inclusive RXF and RXD and MTH ignored
    and even if you could, you can not get 1 / x

    trip values is probably the only one who can give MPG or l/100km
  3. hobbit

    hobbit He who posts articles

    Just to update things a bit and keep this thread vaguely visible...
    I've had a fairly constant set of four gauges up on mine for
    about a month now, having set aside all the wacky network playing
    for now, and I'll summarize them here instead of making folks wander
    through all those other threads for the bits. All this is for an
    '04 Prius, and should work for all '04 and up model years but they
    should be rechecked on an '06 or later to see if any parameters are
    RPM -- stock
    engine power -- 00 / 4000 8000 0000 / 0000 / 000A 001F 0000 / kW
    fuel percent -- 05AC / 0105 02A4 0000 / 1808 / 0064 0028 0000 / gas
    injector time -- 07E0 21F3 / 0306 8461 05F3 / 3808 / 000A 0008 0001 / inj
    where each is given in TXD / RXF / RXD / MTH / name syntax.
    Fuel level is a known one from the spreadsheets, and really I'm
    just comparing that to the car's gauge. Kilowatts is a math mod
    to horsepower, different divisor. And injector is the one I found
    by doing some scantool reverse-engineering. [Its RXF could be
    different, but I'm choosing to prove my point about certain
    length bytes.]
    Injector time is unfortunately not a generic OBD-II parameter, and
    probably has to be a custom xgauge for every different car. It also
    holds the last-known reading after engine shutdown, which is a
    little confusing until you get used to that.
    The other xgauges I've got floating around aren't quite as useful
    and much of what I routinely watch is handled by the analog gauges,
    but I'm finding "inj" and "kW" really useful for bringing the Prius
    engine down to the very lowest rock-bottom RPM when it's still
    decently loaded, pretty much at a minumum of 5.1 ms injector and 9
    or 10 kilowatts output. And I try to not go too far over 6.5 ms on
    the high side. This is much easier to track than trying to seek a
    minimum in 14 IGN which rises on both sides! As I was saying in some
    other threads the low RPM threshold slides up and down with car
    speed, so on a takeoff I'll be turning like 1200 or less RPM at 6.4 ms
    and that gradually starts to level out toward 1450 and 5.2 ms on the
    highway. But it is helping turn some really good numbers, even as
    it's getting colder around here.
    Pushing four years of ownership, and I'm *still* learning...
  4. Ford Man

    Ford Man Well-Known Member

    Anyone created or know whether oil pressure is available as an X gauge on a '97 Ford 2.0L SOHC engine?
  5. CarlD

    CarlD Well-Known Member

    If your vehicle has an oil pressure sending unit, it might have a PID for it that could be used for an xgauge. If it just has a oil pressure switch for an idiot light, there would probably only be an on/off PID.
  6. Ford Man

    Ford Man Well-Known Member

    It's only an idiot light that's why I was hoping for an x gauge, but I was still thinking maybe the information was available. Thanks Carl. If anyone comes up with anything please post it.
  7. Giffer2

    Giffer2 Active Member

    It's a UK car, the 54 refers to the year of registration, in this case September 2004 to Feb 2005.
  8. jkp1187

    jkp1187 Well-Known Member

    I'm looking for the same thing for my car - a 2000 Chevy Impala LS. I know that the 2000 Monte Carlo SS gauge cluster (which will work in the Impala) has an oil pressure gauge. How can I figure out how to tap into that?
  9. CarlD

    CarlD Well-Known Member

    I think it is possible to limit the number of responses in mode $21 by using the byte after the address. What happens when you use a TXD of say 07E221C301 in the Prius? If Toyota adhered to the SAE J2190 spec then there is a chance that you could extract data from multi-frame responses using the SG.
  10. CarlD

    CarlD Well-Known Member

    I think the problem with the Prius PIDs is the multiframe responses. But, my FEH uses this method for mode $09 request for VIN of $02 and I can get the VIN with the xgauges, but NOT with the CMNDS. If anyone with a CAN Prius can look at the response to a mode $21 PID request of $C3 from the 7E2 server, they would probably see a PCI byte where the # of data bytes is for a single frame response. An xgauge would be coded:

    TXD: 07E221C3
    RXF: 056116C30000
    RXD: 1010
    MTH: 000100010000
    NAM: PCI

    If this displays 0abc then it is a single frame response and everything is easy. If it displays something like 1014 then it is a multi frame response. I think this is why Ron thought that Toyota wasn't following the rules when the upper nibble in this byte was not zero. Since my FEH does it for multi-frame responses and I can get the data, all of the Prius PIDs should also be able to be made into xgauges.

    EDIT: I have found a mode $22 PID for the FEH that has a multi-frame response. The first frame looks like: 074D100B62A913xxxxxx and the second frame looks like: 074D21xxxxxx the 0B indicates 11 data bytes total in the 2 frames. A mode $09 PID $02 request gets a $14 (20 data bytes) in that spot.
    A single frame PID has a response of say: 074D0462A911xx. It appears that the scan guage can't retrieve the multi-frame response with an xgauge because it never sends a flow control message after the first frame is received. Perhaps this is the same for the Prius? I am going to let Ron @ LL know what I have found.

    EDIT: This is the answer -
    Last edited: Mar 12, 2009
  11. Dan

    Dan KiloTanked in post 153451

    Very cool find... Thanks for all the legwork in this Carl!

  12. Rotareneg

    Rotareneg Member

    The Xgauge coding manual incorrectly states that the header for KWP is 686AF1 when it should be Cn33F1, where "n" is the number of data bytes you're sending, normally 2 for OBD-II PIDs.

    Also, I've found that if you display the same gauge in more than one "slot" they still send the requests even if they don't display anything, causing the remaining active gauge to update more often. The O2 sensor Xgauge is one that works a lot better with this trick as it fluctuates between high and low fast enough to render the normal update rate almost useless.

    On my '07 Aveo SVM I've found that the commanded throttle actuator PID is a lot more informative than the regular TPS as the car uses a drive-by-wire throttle. It's probably useful on other DBW cars as well.

    Commanded throttle actuator:
    TXD: C233F1014C , RXF: 0441854C0000 , RXD: 2808 , MTH: 03E800FF0000 , NAM: THR

    Estimated temperature of bank 1, catalyst 1, in degrees celsius:
    TXD: C233F1013C , RXF: 0441053C0000 , RXD: 2810 , MTH: 0001000AFF08 , NAM: CTT

    The ambient barometric pressure in kilopascals:
    TXD: C233F10133 , RXF: 044105330000 , RXD: 2808 , MTH: 000100010000 , NAM: BAR
  13. CarlD

    CarlD Well-Known Member

    A software rev is needed to deal with the flow control frame, but once it is implemented there should be literally hundreds of xgauges for the Prius, and CAN Toyotas in general. So far the only multi-frame stuff I've seen for the FEH is the mode $22 $A913 SoC max/min/avg and the mode $09 VIN and calibration PIDs $02 and $04.
  14. dhaluza

    dhaluza New Member

    Where can I find out more about Xgauges for CAN bus Toyota's? (i.e. see my post under the CAN bus for dummies thread).
  15. CarlD

    CarlD Well-Known Member

    I have a list of VPW mode $01 xgauges for Toyota, but I have no idea if they are the same in CAN yotas. I did spend some time in my brother-in-law's Rx400h and saw supported PIDs in the upper reaches of mode $01. Supported PID lists (but no info on what they mean) can be found for mode $01 by sending 0180, 01A0, 01C0, and 01E0 in the CMNDS menu.
  16. Dan

    Dan KiloTanked in post 153451

    Any ETA on the rev, or is it presently available?

  17. CarlD

    CarlD Well-Known Member

    Haven't checked with LL lately since they have a Prius to test out the multi-frame PIDs and don't need my FEH as a test mule. I may call or stop by today if I can.
  18. xcel

    xcel PZEV, there's nothing like it :) Staff Member

    Hi Carl:

    ___A problem came up with the Prius-III yesterday. Toyota’s PID's have been completely changed and none of the X-Gauges work :(

    ___Good Luck

  19. Right Lane Cruiser

    Right Lane Cruiser Penguin of Notagascar

    That's not good. :(
  20. CarlD

    CarlD Well-Known Member

    Did they by chance switch to long CAN format? CANLF under MODE. If not, perhaps they have adopted the Honda model of trying to force all service through dealers by not using OBD-2 standards for non-emission data.

Share This Page