[Solved] Diamex DX35 OBD-II connector not working in CF

[c21]

Hi!

Since it is my first time on this site, at first I'd like to say I've tried a lot of carpc software and Centrafuse is clearly the best. About 15 days ago I've bought my last and final component for my carpc. Yes, you've guessed it was the Diamex DX35 OBD-II connector. Now I have installed the Centrafuse 2 trial and wanted to get it all working. Well I managed to get it all working, almost.

I can't seem to get this OBD-II connected. I've googled the internet and found out that my connector works at 9600 bpms and it uses ELM323 chipset. And I set it all like that in Centrafuse settings. But it just seems to get to the state where it says connecting...

Here is the log and I would really appreciate if anyone would help find a solution. Oh, and some specs on my carpc configuration:
- VIA Epia M10000
- 512MB DDR Ram
- 120 GB IDE hdd

- Windows XP sp2
That's it.

Well, the logs are in attachments

Thanks in advance, c21

[Jan]

The device should have come with some software, or you should be able to download some software from the Elm site (or ScanTool.net) to be able to use the OBD-II in stand alone mode.

Can you give that a try and let us know if it works outside of Centrafuse?

[Jan]

I'm passing this along to Scott. He'll be along in a few to read this and see if he can find anything.

[Nislo]

Your computer is connecting to the device ok as seen in the obd log. The problem is that your device does not send the response Centrafuse is looking for when sending the ATZ request. I believe Centrafuse looks for a specific response such along the lines of 'ELM327 v1.0a', however yours responds with 'DIAMEX DX35 v1.0'.

I understand the CF guys can add this with an update pending that the scantool your using is elm compatible.

[ceerocks]

@Nislo
That's correct!
This interface WOULD work, but Centrafuse asked the "ELM32-String", so it could not work. If Centrafuse allow other interfaces to work, so it woud be work fine with the Diamex DX35 Interface.
At the moment the best Interface i know is this:
Centrafuse Mobile Desktop - OBD-II Interface für Fahrzeugdiagnose, inkl. USB Anschlusskabel

This interface is faster than ELM and allready with a "ELM-String" modified. I've exactly this interface and it work great

[c21]

Jan: It came with the moDiag software and it works there with the same bitrate and com port...

CF guys: Is there any possibilities to add this setting manually into some config file or something, because i'm really anxious to get this work. Or will I have to wait for another update?

Nislo: I'm really not very good in German but i think it says on the Diamex page that it is compatible with ELM, but i could be wrong.

Anyway here is the page: http://florianschäffer.de/misc/obd2_agvdx35.html

[ceerocks]

Originally Posted by c21

Nislo: I'm really not very good in German but i think it says on the Diamex page that it is compatible with ELM, but i could be wrong.

The Diamex is comaptible with ELM, but it has no "ELM32-String" that centrafuse could call. So Centrafuse don't know that this Diamex is compatible with it.

[c21]

That is not so hard to believe in this mess of thousand different OBD-II connectors. Centrafuse team couldn't implement them all into the CF software.

Oh well, I just hope someone of the guys will read and resolve my problem soon
Because I'm really not felling o.k. if there is something on my carpc that it is not working

[Jan]

Since this device isn't actually supported by Centrafuse, your best bet is to submit a request in the Suggestions and Request forum for this device.

Just be aware that since we don't have many people using this device, it might be a while until it is implemented. There are a number of other feature requests that multiple users have requested that are higher on the list.

[Scott]

ceerocks is correct in his post, support for this can easily be added, I will put it in my notes to add it for one of the next releases.