Looking for OBD Software for JTD ...

Hi guys, with looking into my MCSF I've decided I should get hold of some OBD software/hardware so I can look at the faults the ECU is reporting, EOBD only came in for Diesels in 2004, my JTD is a '52, I've found this http://cgi.ebay.co.uk/GALLETTO-1250-...3286.m14.l1308 on ebay which seems to be compatible with my ECU (according to e-learn is Direct BOSCH Common Rail EDC-15C), have any of you guys tried this? or do you used any other devices?

That doesn't look like diag software.

You need Examiner ! I have it, but to get it working is another story... dedicated Laptop with W98 and the correct interface and a special comms board..
you wanna try ?

A*sr ... you're quite right ... just did a search from my ECU and that came up ... I'll keep on looking

Originally Posted by rarebear

You need Examiner ! I have it, but to get it working is another story... dedicated Laptop with W98 and the correct interface and a special comms board..
you wanna try ?

OK
I have Examiner 5.5 and also 6 version...correct ones...but version 6 ask me for serial which I don't have....so ...version 5.5 is ok and I can get it running no problem
Dedicated laptop is also no problem because VMware can handle the job
VMware can also pass signals from serial port...
But can you tell me what is comm board type of? (is it using elm327 maybe? )
any pinouts tips?
I will even say please

BTW...Galletto is for downloading and uploading maps from ECU
Download map from ECU with Galletto
Edit with ECM2001 (or tune it ...whatever someone can call this process)
Upload with Galletto to ECU
Done.

Originally Posted by rarebear

You need Examiner ! I have it, but to get it working is another story... dedicated Laptop with W98 and the correct interface and a special comms board..
you wanna try ?

Yes I wanna try!!! dedicated laptop is also not a problem (I've got an old one lying around) ... dish the dirt on this "special comms board" that you mention ..

What diagnostic equipment do various people use and rate? Until recently, I used the Snap On Solus with 2006 software. I found it easy to use and fairly useful as it would do OE management, EOBD II, ABS and SRS on Alfas. It would do live data and graphing on engine and ABS. Only codes etc on everything else. It wouldn't do security, but as a mechanic who wants to be able to do diagnostics and repairs at home, I wonder what others would recommend as it seems a logical progression of this tread.

Pre-2001 Petrol cars, quite a few of us, including me, tend to use AlfaDiag.

Petrol cars after 2001 are EOBD compatible and people use a range of off-the-shelf tools and software.

Diesels are a problem as it's only post 2004 that are EOBD compatible so before that is a nightmare and hard to find anything that will work.

I use a texa for anything but peugeots... for peugeots use peugeot planet 2000

Originally Posted by gazza82

Pre-2001 Petrol cars, quite a few of us, including me, tend to use AlfaDiag.

Petrol cars after 2001 are EOBD compatible and people use a range of off-the-shelf tools and software.

Diesels are a problem as it's only post 2004 that are EOBD compatible so before that is a nightmare and hard to find anything that will work.

Yes I used to use AlfaDiag on my '98 twinny ... who would've thought it would be this hard to find something for my Tractor!!!

Right ... I think it's time to put my skills to work ... I write real time embedded military software, generally most of the work is interfacing with external equipment (Navigation Systems, Radars etc ...) so writing an app to do this should be a piece of cake ...


... all I need is an ICD (interface control document) i.e. something that defines how the interface works/the content of the messages etc and preferably a bit of hardware that can communicate at the "link" level (i.e. can operate the serial bus) ... (should be the same as the "special comm board" mentioned eariler)


Anyone know where I can get this sort of info ... (obviously if I get it working I'll post it up so anyone can use it ...)

Originally Posted by 156Chris

... all I need is an ICD (interface control document) i.e. something that defines how the interface works/the content of the messages etc and preferably a bit of hardware that can communicate at the "link" level (i.e. can operate the serial bus) ... (should be the same as the "special comm board" mentioned eariler)

that's the problem... that info is proprietary until obd came along.... and obd only has to be used for emmisions related stuff...

maybe do it like the japs/chinese do it... get an original reader and reverse engineer that.... you could even copy the interface

Originally Posted by Cuore_Sportivo_155

maybe do it like the japs/chinese do it... get an original reader and reverse engineer that.... you could even copy the interface

Yes but if I had an original reader then being the lazy git I am I probably wouldn't bother reverse engineering it!!!!

except you can sell the original and get yer money back...

True ... do you have a few thousand pounds you can lend me then? ... at least those are the only one's I've found whilst searching ...

sorry

but i do have a texa I can use which can read my jtd...

according to me (but don't shoot me if I am wrong) it is ELM, problem is to get one that fits in a laptop..
I use alfadiag now, because Examiner is too heavy and too fiddly, alfadiag has the ME3.1, airbag MY97 and Selespeed ECU.
Works great ! and Derek is very helpful
for my car anyway

It's not clear to me if the Alfadiag only uses EOBD protocol or and/does it also use the manufacturer's protocol for certain vehicles?

Gendan have just written an interface for pre 04 tractors, they tell me, 80 quid. Spoke to them a fortnight ago and it wasn't on their website yet. Laptop based live feed, real time graphs.

Originally Posted by Quadcamboy