Don't know. Up to this point I haven't seen any source at all. Do you have any links that you could share? As NewKleer said in the previous post, once you get the fundamentals sorted out there isn't much to it. You push some numbers at the ECU and it streams a bunch back at you. We've got a way to go yet but there are a only a couple of unkowns at the moment and they're not biggies. May as well start from scratch and know exactly how it works and be confident that it does. Cheers, Evan.
consult isnt OBD1, its nissans own diagnostic protocol. OBD1 wasnt all that much of a 'standard', moreso just used to refer to what was 'before OBDII'. OBDII libraries if there are any, would be useless because the communication protocol is completely different.
Hi NewKleer, off the top of your head do you know what the ECU does if you send it a stop stream byte 0x30 when it's not streaming? Cheers, Evan.
it replies CF anyway (assuming its been initialised) which reminds me, another tricky thing is making sure the CF you got was from the stream or from the stop acknowledgement. e.g. last byte in a packet could be coincidentally CF
OBD2 links Cause OBD-2 can be used on any post-96 car, there's a lot more tools out there due to the larger market. Probably, hopefully, better documented too. FreeDiag: http://freediag.sourceforge.net/index.html http://freediag.sourceforge.net/OBD_knowledge.html http://sourceforge.net/projects/freediag/ ActiveOBD2 (database inside could be useful for expansion later): http://sourceforge.net/projects/br3-obd2/ Scantool.net: http://sourceforge.net/projects/scantool/ http://www.scantool.net/scantool/downloads/ Not sure what licenses they use, but all are "open source" on sourceforge.
Ahh, so you couldn't just put a translation layer on top of whatever they send out? Well that sucks. What about open source 300ZX tools? Like http://www.supremez.com/empeg-consult/ or something?
well its possible to try and make it all abstracted or converted to OBD2, but that would require learning OBD2 specific stuff which would just double the work. consult isnt too difficult (easier than OBD2) so it will be much easier to write it from scratch than try and convert from OBD2 stuff. there are a few open source consult things like that empeg and luke's c library or whatever it was, but it they arent really required as most of the main bits are in the doc that plms host, and the rest you soon find out yourself with a bit of trial and error with a comm terminal.
Chris, you are correct. I DID say "open source", however that was a mistake on my behalf. I did state "Open Source" , but what I meant to say was openly available free of charge. I apologise for my mistake. If this is the only issue with the project, then I think we are doing well.
This project is going very well. No one with prior work is getting ripped off, and everyone is going to be able to use the results, so let's not get carried away with if it's open, closed or whatever source. I'm sure that everyone has used a bit torrent client or other free piece of software at one time or another and no one complained about not having the source then. Everyone can benifit from this project if they want to, if anyone has anything positive to add then please do so, the more positive ideas that we can get the better. Cheers, Evan.
Evan has hit the nail on the head. The project is going very well, and I haven't even seen the source code yet. If it goes as well as I like, there will be no reason for me to even see the source... so long as I know how to use the library, there will be no reason to see the source. And knowing how the library is used is up to me as the documentation guy.
Clarification I have just been reading about the different licenses available to us. Some of these are: Freeware Open Source Free Software Shareware This project is freeware. Source code will not be made available. You are granted the rights to use output of this project (software) in any non-commercial product. You may not charge for this software or works that use this software. As always, we reserve the right to modify licensing terms without notice. We will however do our best to try and notify 'you' IF these terms change.
Zed Components We need to know diagnostic problem codes and the most probable cause of the problem. I have the following list (from the tech section). If there is anything missing, or this is incorrect, please let me know. http://www.pexcom.com.au/z32cms/e107_plugins/content/content.php?content.415 Code 55 is no fault of course.
all sounds good to me. to put it simply "you dont need a crack" lol Im watching your entire car PC project with interest and Dave, do shout my way if you want help with front end design.
I'm a bit confused. What's the difference between Open Source under the GNU and Closed Source Freeware? The only difference I see is having it open source makes it easier for others to debug (saving you time) and also easier for others to develop their own tools and addons for, without having to wonder if a bug they are encountering is in their code or the libraries. I really can't see any negatives, unless you at some point plan to commercialize the software? Oh, and here's a list of the ECU address's of different sensors etc: http://www.plmsdevelopments.com/images_ms/Generic_Nissan_ECU_Sensor_or_Data_register_table_Ver_2.pdf And here is alot in interface information: http://www.plmsdevelopments.com/images_ms/Consult_Protocol_&_Commands_Issue_6.pdf
This is from your first post. Now I wonder what will make your project any different? Since the documentation will have to be damn good if others hope to interface with the software (which it rarely is, no offense), and also, it's adds the complication of finding a bug and not knowing if it's your interface program or the library. I was excited hearing this was open source, now it sounds like it's heading towards being just another Conzult-Free clone, with an option to buy the full version (not saying that will happen, but why keep it freeware with an option to change the license otherwise?)
No problems Chris. Will let you know. As Evan stated earlier, the main focus of this project is NOT to create a final product that does ['whatever' - insert you main focus here], rather it will produce separate assemblies that when put together with some developer 'glue', will do what you want. Chances are thought, we will possibly graduate to that after our layers are produced.
Obviously we haven't explained ourselves fully enough. Either that, or you haven't read the complete thread. I will assume the former. Watch this thread for a diagram that will hopefully better explain what it is we are creating.
Will do. I'd love to help with common code indications etc. but I still don't see the difference between freeware and GNU open-source. I did read the thread, but there were a few contradictions in places, I was just going off the last answer of yours I read, though I admit it's possible I got confused.
Freeware does not provide the source code. Free to use, not to redevelop. Now let me concentrate on this diagram
people with sufficient knowledge to be able to help track down a bug could easily have a look at the code with reflector and suggest cause etc that way. so i dont see that being a necessary reason to make it open source.
