Open Source ECU Diags

[Jabbah]

I have been working on and off on writing my own ECU diags software. Currently it is just a console app that will do real time diags, error codes, history, read out the full adaptive maps, clear / reset etc. There is also an ECU emulator so you don't have to connect to the actual ECU all the time. I've only been going off of my own ECU so may be issues with others.

As I'll be selling up at some point I won't be putting much more time into this so is there any interest in me putting this up on GitHub so other people can carry on? If so what would be the license preferred?

[aide]

Hi Jabbah

I'd be happy to maintain your free version and make sure it's kept available.

ETA: A LGLP license would ensure the code remains in the public domain.
https://en.wikipedia.org/wiki/GNU_Lesser_General_P...

Aide

Edited by aide on Thursday 2nd February 09:55

[Juddder]

Count me in too!

[Steve_T]

Very generous of you Jabbah! LGPL sounds like a good call too.

[Englishman]

Personally I'd rather see the code released under a GNU GENERAL PUBLIC LICENSE (GPL). This licence means that anyone that uses your code has to make their source code available too, which supports the reason for Open Source in the first place.

RoverGauge (software for RV8 ECU's and hence Wedges/Chims/Griffs/V8S) and the library it uses, are both released under a GPL licence for this very reason.

[thefrog]

I wouldn't mind contributing either if this takes off.
Greg

[viperbluecerb]

+1 for publishing on GitHib. Would also love to contribute to it.

Out of interest, what is the code base in? C++, C#?

Edited by viperbluecerb on Tuesday 21st February 19:20

[egilkv]

Interested, absolutely.

Would be extra marvellous if you are using a language that also would work on a Raspberry Pi, for instance.

[crypto]

Jabbah said:

I have been working on and off on writing my own ECU diags software. Currently it is just a console app that will do real time diags, error codes, history, read out the full adaptive maps, clear / reset etc. There is also an ECU emulator so you don't have to connect to the actual ECU all the time. I've only been going off of my own ECU so may be issues with others.

As I'll be selling up at some point I won't be putting much more time into this so is there any interest in me putting this up on GitHub so other people can carry on? If so what would be the license preferred?

I assume you are talking about a pc application ? I'm just curious, what was your motivation putting effort into something that already exists ? There is the original TVR tool supporting only serial (&usb) ports as well as EvoOlli's or Aide's application ?

[Tanguero]

crypto said:

Jabbah said:

I have been working on and off on writing my own ECU diags software. Currently it is just a console app that will do real time diags, error codes, history, read out the full adaptive maps, clear / reset etc. There is also an ECU emulator so you don't have to connect to the actual ECU all the time. I've only been going off of my own ECU so may be issues with others.

As I'll be selling up at some point I won't be putting much more time into this so is there any interest in me putting this up on GitHub so other people can carry on? If so what would be the license preferred?

I assume you are talking about a pc application ? I'm just curious, what was your motivation putting effort into something that already exists ? There is the original TVR tool supporting only serial (&usb) ports as well as EvoOlli's or Aide's application ?

None of which are open source...

[EvoOlli]

Tanguero said:

None of which are open source...

Correct, but mine is available for free. The same for my mobile diagnostic unit, where you can build one for yourself with my descriptions.

A month is gone and we didn't get a reply from the Thread creator, so maybe he don't want to share the code with us anymore ?

[Tanguero]

EvoOlli said:

Correct, but mine is available for free. The same for my mobile diagnostic unit, where you can build one for yourself with my descriptions.

A month is gone and we didn't get a reply from the Thread creator, so maybe he don't want to share the code with us anymore ?

Is your source code available for free?

[EvoOlli]

Tanguero said:

Is your source code available for free?

No, didn't write that...the software itself is free. Don't know why I should share my source code with someone else. I think it's enough to give a functional working software to the TVR community :-)

[Tanguero]

EvoOlli said:

Tanguero said:

Is your source code available for free?

No, didn't write that...the software itself is free. Don't know why I should share my source code with someone else. I think it's enough to give a functional working software to the TVR community :-)

I am not saying that you should share your source code, I and many others appreciate your contribution. However that you should understand that the interest in an open source version is precisely because of access to the source code. It is not fulfilling the same need as your free software.

Edited by Tanguero on Friday 3rd March 13:48

[EvoOlli]

Sorry, I misunderstood you...is it fine for my plea that I'm a german native :-))

[Jabbah]

The main reason for open sourcing what I had written was so that the knowledge of how to talk to the ECU is free. I have been somewhat busy recently with personal stuff so haven't had a chance to put the code up yet, and want to clean it up a bit first.

The one thing that I can do that only the original software can do is download the whole of the adaptive maps not just the current cell.

I'm still in two minds about the license to use too, if it is worth using a more commercial license or not. It probably doesn't matter wrt the adaptive map reading as it is purely logic and mathematics, so once the algorithm is out there the GPL won't stop anyone using it in a commercial app anyway, just the specific code.

I'll try and get something up this weekend...

[Jabbah]

Put up a Git repo for the console diags here:

https://github.com/Jabbah/mbediags

I have a simple ECU emulator that allows easy testing of the diags that I will put up later.

I have only tested this fully on my own ECU and have had limited success and issues with another Cerb ECU that I tried. Not sure why but hopefully that is what other people can help with

[jammy-git]

I currently own/host The TVR Site with the original diag software and also have a GitHub repo for my web dev company. If there's anything I can help with, just shout!

[thefrog]

Jabbah said:

Put up a Git repo for the console diags here:

https://github.com/Jabbah/mbediags

Hi, thanks for putting the code up. I've taken a copy off the GIT repository, installed BOOST, but can't get the solution to resolve boost/variant.hpp.
I've set a system environment variable as you suggested on GIT, but to no avail. Could you confirm where you have installed boost and what value your variable is set to ?

Trying not to make any changes to the project setup otherwise what will build for me won't work for you and others.

Thanks
Greg

[thefrog]

egilkv said:

Interested, absolutely.

Would be extra marvellous if you are using a language that also would work on a Raspberry Pi, for instance.

Trouble with Pi is that it didn't deal well with unplanned power outages. Needed to be shutdown properly. This may have been resolved with newer iterations.
Arduino or similar hardware is a better platform.