Page 1 of 3 123 LastLast
Results 1 to 15 of 38

Thread: Tuner Pro V5 and OBDII plug-in?

  1. #1
    Fuel Injected!
    Join Date
    Aug 2011
    Posts
    42

    Tuner Pro V5 and OBDII plug-in?

    Wondering if anyone has has success using the plug-in for the ELM converter?
    I just bought a cheap BT one from sleezebay and am figuring the thing won't work as expected like others have found.
    At least if someone confirms they have connected with it I would feel better.
    For the $$ i figured i'd give it a try with the Android phone and the "Torque" software.
    Worst case with all of this is I will use the Droid as a dual programmable gauge and save $200 from buying those.
    The "interceptor" is nice but very pricey!
    http://www.pfyc.com/pc/GN2110/GTGAU/...+vehicles.html

    I'd like to log my 06' LS2 GTO with TP V5 if possible and see whats going on in there:)
    Any info on the "E40" datastream PIDs?
    I guess there are some GM specific PIDs for oil psi, trans temp that are not in the std set.
    Just fishin for info on this to begin...
    Jp

  2. #2
    Carb and Points!
    Join Date
    Feb 2011
    Posts
    5
    I never did get that to work?

    There are standard OBDII PIDs and then manufacturer enhanced PIDS.

    ScanXL Pro with the GM enhanced PIDS is sweet so far. It's simalar to EFI Live Scan and has a feel of TunerPro. More data then you could dream of and specilty PIDS built in for track times, torque, MPG etc... graphs, maps and dashboards, really has a wow factor for joe smoe, does read and clear codes, watch data or record and all data needed for tuning as well! So far it has more then what is needed to use with TunerCat OBDII.

    It's supposed to work with the Innovate OT-2 wireless but as of now no luck. If you just want data with bells and whistles to iPhone it's got a sweet app but I've never tried it and don't know if the app will work on other phones.

    In the end if you want to do anything with data you'll need EFI Live or TunerCat OBDII with cables to re-flash PCM. EFI Live has the Scan with it so no need for ScanXL. TunerCat OBDII can still be bought with a RoadRunner, which is back ordered and I'm still waiting...

    EDIT: EagleMark on kids laptop again...

  3. #3
    Fuel Injected!
    Join Date
    Aug 2011
    Posts
    42
    ScanXL looks pretty good.
    I'm bouncing between just logging ability and full tuning.
    EFI Live is a ton of $$, TunerCat and others are also big $$.
    I don't mind spending if it turns into a long term use but for the short term I only need to see what is going on (logging)
    i know once I see an issue I'll want to tweak it...
    you know how that goes.

    PS,
    Uou really should buy your own computer, that kid is going to get sick of you borrowing his!

  4. #4
    EFI GearHead ! EagleMark's Avatar
    Join Date
    Feb 2011
    Location
    North Idaho
    Age
    54
    Posts
    10,046
    Quote Originally Posted by JP86SS View Post
    PS,
    Uou really should buy your own computer, that kid is going to get sick of you borrowing his!
    Ouch!

    I need a backup laptop but have never even a qlitch with the HP laptop I bought about 2-3 years ago.

    1990 Chevy Suburban 5.7L Auto ECM 1227747 $42!
    1998 Chevy Silverado 5.7L Vortec 0411 Swap to RoadRunner!
    -= =-

  5. #5
    Fuel Injected!
    Join Date
    Aug 2011
    Posts
    42
    i actually got it to work today.
    Had allot of bluetooth/comm setting issues but it did log some data on the GTO.
    I'm looking into the hex commands going to the ELM327 now to see how to build a full set of data into the ADX.
    There are a bunch more hex chars going to the device in the request command than what I'm seeing is required.
    Not sure why this is, so if anyone has looked at them and has an idea, LMK.
    Thanks,
    Jp

  6. #6
    EFI GearHead ! EagleMark's Avatar
    Join Date
    Feb 2011
    Location
    North Idaho
    Age
    54
    Posts
    10,046
    Do you realize if it works? How does it get the PIDS? Do you have any idea how many PIDS there are? Have you looked at EFI Live or Scan XL Pro custom PIDS? It's amazing!

    I wouldn't want to write that ADX file... how does the ELM Plug in work? Do you need an ADX file?

    1990 Chevy Suburban 5.7L Auto ECM 1227747 $42!
    1998 Chevy Silverado 5.7L Vortec 0411 Swap to RoadRunner!
    -= =-

  7. #7
    Super Moderator
    Join Date
    Mar 2011
    Location
    Camden, MI
    Age
    25
    Posts
    2,490
    luckily, one ADX would cover almost all applications, to a certain degree.

    i'd rather do that than the ~250+ that i have in progress for the GM OBD1 applications.
    1995 Chevrolet Monte Carlo LS 3100 + 4T60E


  8. #8
    Fuel Injected! PJG1173's Avatar
    Join Date
    Nov 2011
    Location
    Jacksonville NC
    Age
    40
    Posts
    488
    I was looking into this a while back but lost interest but I did find this. http://www.delcohacking.net/forums/v...&t=1320#p14773
    87 4Runner, 15" spring lift, 3" body, chevy vortec 355, 5.29 gears, 44x18.5x15" TSL's, 280hr, 16168625 running $0D
    93 S10, 12" spring lift, 4.56 gears, F/R lockers, 36x12.5x15 TSL's, long tube headers, 266HR cam, p&p vortec heads, 16168625 running $0D.
    05 Silverado, 2' lift, 4" exhaust, Bully Dog programer,
    88 Jeep Wrangler (Daughters) 3" lift, 33x12.5x15, no gears, no lockers, no engine mods.

  9. #9
    Fuel Injected!
    Join Date
    Aug 2011
    Posts
    42
    I got it to work with the default ADX file.
    Looking at the file the commands are kind of foreign to me.
    From what I'm reading, all it takes is the "$01 and the PID number in hex to get the current value.
    The ADX with the plug in has a longer string that I can't figure out. (like multiple more hex codes)

    I downloaded "touchscan" (a free program that went commercial) and it has a raw data screen that has some of the same long format retrieval codes going to the PCM.
    I'm attempting to correlate the port monitored hex chars to an actual request / recieve theme but its not adding up in my pea brain.
    I'd really like to make a std OBDII set of data from this (so any compliant car can use it) and then investigate OEM PIDS for my 06 GTO.
    Its kind of working but I'm not grasping what is really going on there.
    The supplied ADX only has throttle position, RPM and one other parameter (I forget what it was)
    Any ideas would be appreciated.
    I'll try to grab some of the data and post it so you can see what I'm describing better.
    Jp

  10. #10
    Fuel Injected!
    Join Date
    Aug 2011
    Posts
    42
    Wondering if the additional commands are to interpet through the ELM device interface.
    Not sure...
    Still digging with enthusiasm :)
    Jp

  11. #11
    Fuel Injected!
    Join Date
    Aug 2011
    Posts
    42
    Quote Originally Posted by RobertISaar View Post
    luckily, one ADX would cover almost all applications,
    That is my plan

  12. #12
    Super Moderator
    Join Date
    Mar 2011
    Location
    Camden, MI
    Age
    25
    Posts
    2,490
    Quote Originally Posted by JP86SS View Post
    Wondering if the additional commands are to interpet through the ELM device interface.

    if i had to guess, that would be where i would expect extra commands to be needed.
    1995 Chevrolet Monte Carlo LS 3100 + 4T60E


  13. #13
    Fuel Injected!
    Join Date
    Aug 2011
    Posts
    42
    This is a raw data dump from the Touchscan SW as it connected and was displaying data.
    Its not all of it just the first part where it connected and then I started the engine.
    I'm "supposed to be" the E40 setup on my car.
    This program finds it as the "7EA" or "7E8" not sure why that is.

    Code:
    Trying Protocol: ISO 15765-4 CAN (11 bit ID, 500 Kbaud)
    ATSP 6: [OK]
    01 00: [41 00 80 00 00 01 
    41 00 BF BF B9 93 ]
    Protocol detected: ISO 15765-4 CAN (11 bit ID, 500 Kbaud)
    
    ATH1: [OK]
    Reading vehicle information
    01 00: [7EA 06 41 00 80 00 00 01 
    7E8 06 41 00 BF BF B9 93 ]
    01 00: [7EA 06 41 00 80 00 00 01 
    7E8 06 41 00 BF BF B9 93 ]
    01 20: [7EA 06 41 20 80 01 80 01 
    7E8 06 41 20 80 07 E0 19 ]
    01 40: [7EA 06 41 40 40 00 00 00 
    7E8 06 41 40 FE D0 00 00 ]
    Detected PIDs:
        ECU: 7EA
            0x00 - SupportedPIDs0
            0x01 - MonitorStatus
            0x20 - SupportedPIDs1
            0x21 - DistanceTraveledWithMILOn
            0x30 - NumWarmUpsSinceCodesCleared
            0x31 - DistanceSinceCodesCleared
            0x40 - SupportedPIDs2
            0x42 - ControlModuleVoltage
        ECU: 7E8
            0x00 - SupportedPIDs0
            0x01 - MonitorStatus
            0x03 - FuelSystemStatus
            0x04 - EngineLoad
            0x05 - EngineCoolantTemp
            0x06 - ShortTermFuelTrimBank1
            0x07 - LongTermFuelTrimBank1
            0x08 - ShortTermFuelTrimBank2
            0x09 - LongTermFuelTrimBank2
            0x0B - IntakeManifoldPressure
            0x0C - EngineRPM
            0x0D - VehicleSpeed
            0x0E - TimingAdvance
            0x0F - IntakeAirTemperature
            0x10 - MassAirFlowRate
            0x11 - ThrottlePosition
            0x13 - OxygenSensorsPresent
            0x14 - OxygenSensor1Voltage
            0x14 - OxygenSensor1ShortTermFuelTrim
            0x15 - OxygenSensor2Voltage
            0x15 - OxygenSensor2ShortTermFuelTrim
            0x18 - OxygenSensor5Voltage
            0x18 - OxygenSensor5ShortTermFuelTrim
            0x19 - OxygenSensor6Voltage
            0x19 - OxygenSensor6ShortTermFuelTrim
            0x1C - OBDStandard
            0x1F - RunTimeSinceEngineStart
            0x20 - SupportedPIDs1
            0x21 - DistanceTraveledWithMILOn
            0x2E - CommandedEvaporativePurge
            0x2F - FuelLevelInput
            0x30 - NumWarmUpsSinceCodesCleared
            0x31 - DistanceSinceCodesCleared
            0x32 - EvapSystemVaporPressure
            0x33 - BarometricPressure
            0x3C - CatalystTemperatureBank1Sensor1
            0x3D - CatalystTemperatureBank2Sensor1
            0x40 - SupportedPIDs2
            0x41 - MonitorStatusThisDriveCycle
            0x42 - ControlModuleVoltage
            0x43 - AbsoluteLoadValue
            0x44 - CommandEquivalenceRatio
            0x45 - RelativeThrottlePosition
            0x46 - AmbientAirTemp
            0x47 - AbsoluteThrottlePositionB
            0x49 - AcceleratorPedalPositionD
            0x4A - AcceleratorPedalPositionE
            0x4C - CommandedThrottleActuator
    
    09 0A: [NO DATA]
    01 00: [7EA 06 41 00 80 00 00 01 
    7E8 06 41 00 BF BF B9 93 ]
    01 00: [7EA 06 41 00 80 00 00 01 
    7E8 06 41 00 BF BF B9 93 ]
    01 00: [7EA 06 41 00 80 00 00 01 
    7E8 06 41 00 BF BF B9 93 ]
    01 00: [7EA 06 41 00 80 00 00 01 
    7E8 06 41 00 BF BF B9 93 ]
    01 00: [7EA 06 41 00 80 00 00 01 
    7E8 06 41 00 BF BF B9 93 ]
    01 00: [7EA 06 41 00 80 00 00 01 
    7E8 06 41 00 BF BF B9 93 ]
    01 00: [7EA 06 41 00 80 00 00 01 
    7E8 06 41 00 BF BF B9 93 ]
    01 00: [7EA 06 41 00 80 00 00 01 
    7E8 06 41 00 BF BF B9 93 ]
    01 00: [7EA 06 41 00 80 00 00 01 
    7E8 06 41 00 BF BF B9 93 ]
    01 00: [7EA 06 41 00 80 00 00 01 
    7E8 06 41 00 BF BF B9 93 ]
    01 00: [7EA 06 41 00 80 00 00 01 
    7E8 06 41 00 BF BF B9 93 ]
    01 00: [7EA 06 41 00 80 00 00 01 
    7E8 06 41 00 BF BF B9 93 ]
    01 00: [7EA 06 41 00 80 00 00 01 
    7E8 06 41 00 BF BF B9 93 ]
    01 00: [7EA 06 41 00 80 00 00 01 
    7E8 06 41 00 BF BF B9 93 ]
    01 00: [7EA 06 41 00 80 00 00 01 
    7E8 06 41 00 BF BF B9 93 ]
    01 00: [7EA 06 41 00 80 00 00 01 
    7E8 06 41 00 BF BF B9 93 ]
    01 00: [7EA 06 41 00 80 00 00 01 
    7E8 06 41 00 BF BF B9 93 ]
    01 00: [7EA 06 41 00 80 00 00 01 
    7E8 06 41 00 BF BF B9 93 ]
    01 00: [7EA 06 41 00 80 00 00 01 
    7E8 06 41 00 BF BF B9 93 ]
    01 00: [7EA 06 41 00 80 00 00 01 
    7E8 06 41 00 BF BF B9 93 ]
    01 00: [7EA 06 41 00 80 00 00 01 
    7E8 06 41 00 BF BF B9 93 ]
    01 00: [7EA 06 41 00 80 00 00 01 
    7E8 06 41 00 BF BF B9 93 ]
    01 00: [7EA 06 41 00 80 00 00 01 
    7E8 06 41 00 BF BF B9 93 ]
    01 00: [7EA 06 41 00 80 00 00 01 
    7E8 06 41 00 BF BF B9 93 ]
    01 00: [7EA 06 41 00 80 00 00 01 
    7E8 06 41 00 BF BF B9 93 ]
    ATSH 7DF: [OK]
    09 02: [7E8 10 14 49 02 01 36 47 32 
    7E8 21 56 58 31 32 55 30 36 
    7E8 22 4C 35 36 31 35 37 37 ]
    01 01: [7EA 06 41 01 00 04 00 00 
    7E8 06 41 01 00 07 65 00 ]
    ECU disconnected
    AT@1: [OBDII to RS232 Interpreter]
    01 0D: [7E8 03 41 0D 00 ]
    AT@2: [?]
    AT@2: [?]
    AT@2: [?]
    AT@2: [?]
    01 10: [7E8 04 41 10 02 75 ]
    01 00: [7EA 06 41 00 80 00 00 01 
    7E8 06 41 00 BF BF B9 93 ]
    01 44: [7E8 04 41 44 80 00 ]
    STI: [?]
    STI: [?]
    STI: [?]
    STI: [?]
    01 04: [7E8 03 41 04 33 ]
    01 00: [7EA 06 41 00 80 00 00 01 
    7E8 06 41 00 BF BF B9 93 ]
    01 0B: [7E8 03 41 0B 25 ]
    01 1C: [7E8 03 41 1C 07 ]
    01 0C: [7E8 04 41 0C 09 06 ]
    01 0E: [7E8 03 41 0E 97 ]
    01 11: [7E8 03 41 11 2D ]
    01 14: [7E8 04 41 14 A9 80 ]
    01 15: [7E8 04 41 15 81 FF ]
    01 18: [7E8 04 41 18 A9 80 ]
    01 00: [7EA 06 41 00 80 00 00 01 
    7E8 06 41 00 BF BF B9 93 ]
    01 19: [7E8 04 41 19 85 FF ]
    01 2E: [7E8 03 41 2E 00 ]
    01 33: [7E8 03 41 33 63 ]
    01 3C: [7E8 04 41 3C 11 9E ]
    01 3D: [7E8 04 41 3D 11 9E ]
    01 43: [7E8 04 41 43 00 2F ]
    01 4C: [7E8 03 41 4C 14 ]
    01 0D: [7E8 03 41 0D 00 ]
    01 10: [7E8 04 41 10 02 46 ]
    01 44: [7E8 04 41 44 80 00 ]
    01 04: [7E8 03 41 04 30 ]
    01 0B: [7E8 03 41 0B 24 ]
    01 0C: [7E8 04 41 0C 08 85 ]
    01 0E: [7E8 03 41 0E 9B ]
    01 0F: [7E8 03 41 0F 66 ]
    01 00: [7EA 06 41 00 80 00 00 01 
    7E8 06 41 00 BF BF B9 93 ]
    01 11: [7E8 03 41 11 2D ]
    01 14: [7E8 04 41 14 AE 7F ]
    01 15: [7E8 04 41 15 83 FF ]
    01 18: [7E8 04 41 18 A9 7F ]
    01 19: [7E8 04 41 19 86 FF ]
    01 2E: [7E8 03 41 2E 00 ]
    01 33: [7E8 03 41 33 63 ]
    01 00: [7EA 06 41 00 80 00 00 01 
    7E8 06 41 00 BF BF B9 93 ]
    01 3C: [7E8 04 41 3C 11 B2 ]
    01 3D: [7E8 04 41 3D 11 B2 ]
    01 43: [7E8 04 41 43 00 2F ]
    01 4C: [7E8 03 41 4C 15 ]
    01 0D: [7E8 03 41 0D 00 ]
    01 10: [7E8 04 41 10 02 53 ]
    01 44: [7E8 04 41 44 7F E0 ]
    01 04: [7E8 03 41 04 31 ]
    01 0B: [7E8 03 41 0B 25 ]
    01 0C: [7E8 04 41 0C 08 F1 ]
    01 0E: [7E8 03 41 0E 95 ]
    01 11: [7E8 03 41 11 2E ]
    01 00: [7EA 06 41 00 80 00 00 01 
    7E8 06 41 00 BF BF B9 93 ]
    01 14: [7E8 04 41 14 9B 7F ]
    01 15: [7E8 04 41 15 87 FF ]
    01 18: [7E8 04 41 18 A2 7F ]
    01 19: [7E8 04 41 19 85 FF ]
    01 2E: [7E8 03 41 2E 00 ]
    01 33: [7E8 03 41 33 63 ]
    01 3C: [7E8 04 41 3C 11 BC ]
    01 3D: [7E8 04 41 3D 11 BC ]
    01 00: [7EA 06 41 00 80 00 00 01 
    7E8 06 41 00 BF BF B9 93 ]
    01 43: [7E8 04 41 43 00 31 ]
    01 4C: [7E8 03 41 4C 15 ]
    01 0D: [7E8 03 41 0D 00 ]
    01 10: [7E8 04 41 10 02 58 ]
    01 44: [7E8 04 41 44 80 00 ]
    01 04: [7E8 03 41 04 31 ]
    01 0B: [7E8 03 41 0B 24 ]
    01 0C: [7E8 04 41 0C 08 B5 ]
    01 0E: [7E8 03 41 0E 98 ]
    01 11: [7E8 03 41 11 2E ]
    01 00: [7EA 06 41 00 80 00 00 01 
    7E8 06 41 00 BF BF B9 93 ]

  14. #14
    Fuel Injected!
    Join Date
    Aug 2011
    Posts
    42
    Just got a reply from Magnus on this :)
    Code:
    // Expected command format: 
    // Mode + PID + Replies to gather (optional) 
    // 'M' + HH + 'P' + HH + 'S' + HH + 'R' + H 
    // 
    // Where "HH" is two hex ASCII bytes (e.g. 'F' 'F' for 0xFF). 'M' is for Mode, 
    // 'P' is for PID, 'S' is for size of PID data reply, and 'R' is for reply count. 
    // Note that the 'R' data is a single hex digit (e.g. '2'). 
    // 
    // Example PID request for Mode 1 PID 4, get only 1st reply: 
    // 'M' '0' '1' 'P' '0' '4' 'S' '0' '1' 'R' '1' 
    // Example, same as above but get all replies (return last reply) 
    // 'M' '0' '1' 'P' '0' '4' 'S' '0' '1'
    Will be playing around this weekend, stay tuned (yes, that was a bad pun!)
    Jp

  15. #15
    Fuel Injected!
    Join Date
    Aug 2011
    Posts
    42

    ASCii text !!!!!

    from my post on Mark's site.
    Eureka!
    My pea brain finally broke through the start of this.

    Yes, you only need to send "01 00" to get a value...
    But...
    That command must come as ASCII text characters! (NOT HEX directly)

    So "01 00" = "30 31 20 30 30 0D'
    "0D" on the end is a period in my logger. Might be needed as EOL or something.

    30 in ASCii = 0
    31 in ASCii = 1
    20 in ASCii = "space"
    30 in ASCii = 0
    30 in ASCii = 0

    More to come...

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •