Develop an Open Source Diagnostic Tool?

  • No, don't bother you're wasting your time.

    Votes: 5 15.6%
  • Yes, and I am willing to contribute.

    Votes: 16 50.0%
  • Yes, but I am unable to contribute.

    Votes: 11 34.4%

  • Total voters
    32
  • Poll closed .

woogoo

New Member
From the previous thread discussing this topic it would appear that some people are interested in the development of an Open Source (100% free) Diagnostic tool for the Land / Range Rover.

As I have said previously I am willing to make a start on this with the hope that others will lend a hand, not only in the development of the code (C++) but the testing, preparation of data, connectivity for wiring, protocols etc.

For those that followed the thread you will be aware that RSWSolutions are already progressing with the new version of their software and it is hoped to be released by the end of the first quarter of 2010, however there is a cost related to this. (See thread link below.)

Just because there is a (minimal) cost involved does NOT mean that free software should be developed for the tight gits not willing to pay.

For those that haven't read the thread you may want to do this before voting. http://www.landyzone.co.uk/lz/f10/rfc-diagnostic-software-93363.html

I would like to point out that the fact that the development of such software takes time, however the more people working on the code the better, but I would certainly expect RSWSolutions to deliver long before there was a really tangible product available via Open Source.

However, if there is an advantage to doing an Open Source project is that the resulting product will be able to run on operating systems such as Linux, Windows and Symbian (PDAs/Phones) from a single code base.

This is a closed vote poll.
 
Last edited:
Hey, I do robotics as a a hobby and use C++ as the programming language. I currently use an arduino based microcontroller. You may be interested as not only can it talk to the PC in realtime via USB, it is more than capable of 'conversing' with other microcontrollers (or ECU's) and using the arduino board as a 'translator.'

Admitedly i havent done much in this field but i know it is very much possible and a standard off the shelf srduino board can be ought from ebay from as little as £20 and the accompanying programming software is free to use.

I'm not really a hands on man but i do enjoy a good challenge with the programming side. (i don't think i'm any good though : / )

I don't know if you are aware of this software but Centrafuse™ | A Whole New Way this software is very good and comes with a plug in mod that will talk to any car and utilise anything a garage/mechanic's diagnostic software can use.
 
Not right good as far as C++ goes, but i'm a spark with a good background in PLC and SCADA systems (PC>PLC interfacing) if that is any use to you...

Don't have any hands on experience with diagnostics though, cos i've never had a car with any on and never had the need to play with the bike!
 
I'm very interested in this - can't contribute from a Technical point of view (the only thing I know about C++ is how to spell it!!) but I'm happy to contribute towards software costs/licence fees etc.... might be able to locate a Server or two if you need something to write it on though!
 
i would love to helop but havent a clue about programming, but would be willing to contribute in anyway possible, best of luck to you. i know there are many people on here that would be willing you to make that programe.

anyway best of luck!
 
Ready, willing and able..... well ready and willing anyway, not sure I've a huge amount to offer skills wise, cable assembly and testing maybe, but I'll help if I can.
 
well it looks like there are many people who can help out in various ways. even if it is re inventing the wheel to some degree.

theres always a way to make improvements on existing software/methods.

can't wait!
 
so where do you go from here? how long would it take to get the 1st trial up and running?

Well without writing a major spiel it's not an easy one to answer. Of course we have to wait till the poll closes but it would appear that the consensus of opinion is that this be done.

However, with that said this is not, and I mean NOT a trivial task, and the more I look into this the more evident this becomes as OBD-II supports various protocols ISO9141, ISO14230, SAEJ1850 VPW and PWM however in order to make these work they require a physical interface to the hardware why is why RSWSolutions are doing their own!

There are of course many ways to get an interface including use of existing ones such as MultiPlex, Silicone Engines etc, but how many of these interfaces are out there and would need supporting?

Or create our own just like RSW but that means we need to develop our own PIC (Programmable Interface Controller) so we may well be on a hiding to nothing with this one.

It is a bit of a catch 22 here, we could wait on RSW to deliver the goods and do some further development using his libraries, assuming they ever get released. (No disrespect to RSW I just have my doubts on this one.)

But having said that a lot of code can be written in what may be 2.5 months until he releases his product, and maybe even longer till the libraries are available.

If anyone's read this far what do you think?
 
Well without writing a major spiel it's not an easy one to answer. Of course we have to wait till the poll closes but it would appear that the consensus of opinion is that this be done.

However, with that said this is not, and I mean NOT a trivial task, and the more I look into this the more evident this becomes as OBD-II supports various protocols ISO9141, ISO14230, SAEJ1850 VPW and PWM however in order to make these work they require a physical interface to the hardware why is why RSWSolutions are doing their own!

There are of course many ways to get an interface including use of existing ones such as MultiPlex, Silicone Engines etc, but how many of these interfaces are out there and would need supporting?

Or create our own just like RSW but that means we need to develop our own PIC (Programmable Interface Controller) so we may well be on a hiding to nothing with this one.

It is a bit of a catch 22 here, we could wait on RSW to deliver the goods and do some further development using his libraries, assuming they ever get released. (No disrespect to RSW I just have my doubts on this one.)

But having said that a lot of code can be written in what may be 2.5 months until he releases his product, and maybe even longer till the libraries are available.

If anyone's read this far what do you think?

well i think if you have to devote possibly 4 months or more to the project then i think you have to think seriously if your up for the challenge, its all good people like me saying "yeah go for it dude" but we wont be there on the long nights your up trying to write the program. though "WE" would be greatfull if you did and if people are like me would be willing to help in any realistic way i can.

what ever you decide its a good topic to raise
 
the elm 327 supports all thoseprotocols, why not jus write for that platform. Its cheap and readily available, plenty of other pograms out there for te engine ecu. I use it on mine so its a start!
 
ebay, well thats where i got mine. circa 30 quid.

then at least if its not much cop for the p38 stuff you can still get into your engine ecu and alot if not most other cars!!

i read and clear engine fault on a few cars of friends and family!!
 
Rather than start a new thread, I though I'd ask here..... does anyone know the minimum PC spec for the T4/Testbook software?
 
98 bag of poo should do it!!

it'll run on xp tho

do you have it?

do you want it?

what do you propose to do with it once installed?

do you think i should be asleep yet?
 

Similar threads