Hyundai Coupe/Tuscani (Siemens ECU)

[alawadhi3000]

Hello,

I'm wondering what are the setting to connect to my Car (2004 Hyundai Coupe) which is known by Hyundai Tuscani in Korea.

I saw it on the compatibility page but it didn't connect, I tried all protocols available.

Thanks.

[cail]

Which market your vehicle from?
If its korean, then you may face a problem, since asian markets have no requirements to support OBD2 and thus such vehicles can't (or maynot) be read by ELM adapter.

[alawadhi3000]

Middle East, yes supporting OBD-II is not mandatory here but neither is in Korea, the Tuscani FX is the same car as the Middle East Coupe and has the same ECU number.

I can connect using your software (the light turns green and it says connected to ECU) but I can't read any sensor information.

[cail]

You may try put here the detailed TRACE logs (enable in system settings),
but most probably your vehicle just do not respond anything on sensors requests.
There of course could be some manufacturer private sensors to be read, but this is difficult to find (no much public info available).

Even the same ECU can have different presets for different markets, so thats not an inidication unfortunately.

[alawadhi3000]

Attached. Thanks.

[cail]

It seems ELM can see the physical level protocol, but for any of OBD2 standard sensor request your ECU replies with error.
Probably there exist some manufacturer protocol, but it is definitely that OBD2 is not supported on this vehicle.

[alawadhi3000]

Thats what I figured out when I saw that the ECU reply with 7F 01 11.

So its the same case as JDM Toyota's and Nissan's, they're not OBD but they worked in the app by a different initialization commands.

Any chance of implementing the Hyundai protocol, I can test anything you want.

Thanks.

[cail]

For now the only was is to findout some publically available information on its protocol - then this can be added to the supported ECUs.

[alawadhi3000]

Too bad.

I've researched for days and didn't find anything.

[alawadhi3000]

I've been reading a lot in the past two days, mostly about ELM327 and KWP2000 protocol.

I managed to connect to the ECU using the following commands.

ATZ
ATSP5
ATSH8111F1
81

But the OBD-II PIDs (0100, 010C ..etc) won't work because the car is not OBD-II, however the car responds to the command 2101 with a long string (around 100 bytes long), lots of values change when I start the car which probably mean that these are the Hyundai PIDs.

The problem now is how can I get the formulas for them, and how do I know which address is for which PID.

The only way I can think of is to start the car and then get the 2101 string, after that for example I disconnect the coolant sensor and see which byte turns to 00.

[alawadhi3000]

Yes I'm absolutely correct.

I disconnected the coolant temperature sensor and one byte of the output became "FF".

I reconnected back the sensor and value became "8E".

The temperature is inverted "FF=00 and 00 = FF".

The equation should be FF-A-40 therefore FF-8E-40 = 31C which is right because the ambient temperature was ~29C, the weird thing is that the whole expression is in hexa.

So I warmed the engine and drove 10 minutes with the A/C on and the byte was "38" therefore FF-38-40= 87C which should be right because the thermostat fully opens at ~90C.

[cail]

Congrats, you probably have delphi-mt20u ECU or with a similar protocol!

Try choosing this ECU in hobdrive vehicle settings and see what it'll show.

You then can openup "ecu/delphi-mt20u.ecuxml" file and see how it describes ECU PIDs.

If your PIDs are not matching (f.e. in delphi the coolant temp is byte 14) - then you have to fix the protocol definition.

You also may try vaz-boschmp7.ecuxml and vaz-yanvar.ecuxml protocol - these has a similar structure with Delphi, but different PIDs positions and formulas.

[alawadhi3000]

Its a Siemens ECU, thats all I know.

The delphi-mt20u.ecuxml is good as a base but the data locations are different.
I have the coolant sensor as byte #6, when I put that into the xml the program shows 88C because the data was 80 and the offset is -40 (128-40=88).

Is there anyway I can do the formula in my previous post?

Edit:- I think I got it, still untested but it should work
<value-6> -2.29577 </value-6>
<offset>215</offset>

[alawadhi3000]

For some weird reason the Coolant value is always being read at 88c (80-40) while the others are always -40 or 0.

I have checked using obd terminal that the value was actually 7f which mean with the offset of -40 the end result should be 87c not 88c.

When I send the 2101 command using terminal:-
>2101

The ECU responds with:-
61 01 7B 0D 71 8C 83 82 0A 00 00 0A 30 ...etc

The 71 is the coolant sensor, 83 is the Intake temperature sensor and the 30 is the throttle position.

Is it right that I put the coolant as <value-4>, Intake as <value-6> and throttle as <value-12>??

Edit:-

Код: Выделить всё

HandleReply: FF 00 00 00 00 00 80 00 00 00 00 01 FF 06 00 00
[TRACE]

That happens only in HOBD, in OBD terminal the ECU reply properly. Whats wrong?

[cail]

Is it right that I put the coolant as <value-4>, Intake as <value-6> and throttle as <value-12>??

Yes, absolutely

That happens only in HOBD, in OBD terminal the ECU reply properly. Whats wrong?

Make sure you've settled up valid EML initialization string (in vehicle settings).

[alawadhi3000]

How to do that??

In terminal the only commands I put to connect are:
ATZ
ATSP5
ATSH8111F1
81
and then get data using 2101.

[cail]

Then, in vehicle settings in ELM Init string field enter:
ATSP5; ATSH8111F1; 81;

[alawadhi3000]

Already did that, still no proper ECU reply.

[alawadhi3000]

HOBD log is attached.

Also OBD terminal (Android app) screenshot is attached which shows proper ECU reply using the same commands.
Also Torque Pro shows proper output.

[cail]

Thats strange indeed!

Could you try putting the next init string:

ATZ;ATSP5;ATSH8111F1;81;2101

and giving log.txt again