MGTF OBD question

[scaryoldcortina]

Just in case anyone knows the answer, I'm having issues getting a generic OBD reader to behave on my MGTF. "Proper" scantools work fine, and say it is compliant using ISO 9141-2. I have several cheapo elm327 interfaces, they don't normally have any issues with ISO but don't want to talk to the MG. This is a bit of a pain because I wanted to do some logging, and also the MIL keeps coming on. I'll probably just use the ethos eventually, but it's bugging me because it should work and doesn't.

 

For example - torque (android app) won't connect at all, but a serial terminal (blueterm) on the same device will connect and read everything except mode 03 (call DTC codes). It will even put the MIL out (04) and reports all live data on mode 01 correctly, but 03 just returns "NO DATA".

 

Google hasn't told me anything pertinent except to confirm that an 04 MGTF should be fully compliant with OBD2, so I'm at a loss for now as to why it's being strange.

[SiC]

Have you tried extending the timeout (ATSTxx)? Some of the Renault modules I have found are very slow at responding and so the ELM327 hits its default timeout.

 

Also maybe try putting two elm327 on a y-lead and have ATMA on one running. It may be responding, just the app timeout is too short.

[scaryoldcortina]

Good idea. I'll try that tomorrow!

 

edit - the "NO DATA" reply looks instant in blueterm - it's there as soon as you press enter and the timeout is 200ms so should be noticable, but I'll try extending the timeout anyway. Might be that, I guess mode 3 takes a little longer to process than the others.

[Barry Cade]

Eh?

 

All modern cars  computers are...........far too technical for me.

[scaryoldcortina]

 

Wasn't that. I got all the way up to atstff (about 1 second timeout) with no change.