I have bought the OBD-2 Analyser from Elektor Elektronics with the mOByDic oe90c2600.
I have received the OBD-2 Analyser Friday last week, but I was unsuccessful in communicating with the ECU in my car yesterday. I have a Peugeot 206 2.0 HDi from December 2003.
I used a laptop with Windows 2000 + the mOByDic Computer Interface (mOByDic_Free1.1.0.0). I don't think the software should not be an issue. The COM1 port is correctly initialized as well as the chip version is ok, but the connection to ECU is failing! My hardware seems to be working correctly (no smoke is coming out and non of the circuits are getting hot), but I'm not 100% sure. I tried different connection topologies - and I tried to turn on the ignition before/after plugging in the OBD-II connector. The red LED comes on and the yellow LED starts to blink. However, the green LED never turns on. I don't understand why the OBD-2 Analyser is not able to find any of the 5 supported protocols. Regarding the Peugeot's ECU I think it is using the ISO9141-2 (or is it the KWP2000?) protocol - can anyone confirm this?
My question is whether the mOByDic oe90c2600 is not working correctly (some software bug?) or if the ECU is using a completely unique protocol? Maybe there are certain voltages/signals you suggest I must check? I'm not aware of which part I should start debugging first.
I can add that I don't think there is any issue regarding the reset circuit since I'm using the IC7 + C7 !! I also guess that the yellow light never comes on if the mOByDic has not been correctly reset.
I really don't know whether this is a hardware problem or a software problem but now I want to put all my effort into getting this tool to work until I succeed.
Thanks in advance.
Regards,
Christian Lodberg
