hobDrive Support

Hello,
I have succesfully connected my Hyundai Santa Fe with a ELM327 unit and have run HOBD (great programm by the way). I have used every combination of Vehicle Type and ELM Init Template in Vehicle Settings and I do get some output and numbers, but they don't seem to make much sense.
Does anybody know the right Vehicle Type configuration and/or PID input for the ECUXML file?
Thanks!

jvantichelt,

Do you mean the output numbers are all invalid and random??

If you feel only fuel consumption is ugly, you should just calibrate it.

Your vehcile should work normally with "Common OBD Diesel" profile.

Hello Cail,
Thanks for your reply. I'm using version 1.1.87 wince. With vehicle set to "Common OBD Diesel", vehicle "Standard" and ELM Template "ELM reset" I get no readings at all. When I choose vehicle "Siemens ACR167 KWP" I do get some (changing) numbers, but they are invalid and random for Engine Coolant, Intake Air and Acceleration.
I haven't yet tried to calibrate the fuel consumption, but I'm beginning to think that my ELM327 Bluetooth might be faulty...

I've run the TRACE-log and Vehicle type "Standard OBD2" and it goes right to Protocol ID 3 where I get for the sensors some nubers. For example Speed (41 0D 00), EngineLoad (41 04 56), RPM (41 0C 0D 38), CoolantTemp (41 05 4D) and IntakeAirTemp (41 0F 31).
But in the next cycle for this Protocol I get for these sensors "HandleReply: NO DATA".
And then it switched suddenly to Protocol ID 5 and I get for all sensors "HandleReply: 7F 01 12".
So there seems someting happening, but not don't know exactly what...

Getting closer:
[TRACE] 02-01-14 18:19:38.581[OBD2Engine] HandleReply: 61 01 FF FE CB 00 0C 34 15 20 11 E2 07 4E 00 02 4A FF 00 00 FF 00 4B 04 04 08 FC DF FC C0 C2 00 00 16 00 05 5B
Now just trying to find out which value corresponds to which sensor...

jvantichelt,

The fact you see replies for "Standard OBD2" means your vehicle should work on these settings, but something prevents it from further communications. Could you put here your log.txt with corresponding replies?

The latest reply you see "61 01" is from KWP2K protocol (not OBD2). Yes, it seems your ECU can work on this protocol but it should be unencrypted and coded into ecuxml file (you may use siemens.ecuxml as a reference). You may use excel to build charts to better understand each number. attached is a sample xls for that.

Cail,

Here’s my log.txt.

And the settings of my car are:
->Vehicle settings:
Vehicle name: My Vehicle
Make: Common
Title: OBD-II, Diesel
Year: 2007
Vehicle type: Standard OBD2
ELM Init Template: ELM Reset
ELM Init string: ATSP 0
MPG method: Engine Load Sensor
->OBD-II Port Settings:
Delay for ELM Interactions: 0

I see two strange things:

1. internal config data save consumes > 5sec on your flash card, this makes OBD protocol to hangup for 5 seconds and reconnect. Please try updating to latest 1.1.90, also you may try a faster flash card.

2. After [1] reconnection your ELM for some reason losts ECU and connects to some other ECU with no PIDS. That could be ELM adapter strange or incorrect behaviour.

Try fixing [1] and may be [2] will go away.