I'm in the same boat. About a month ago, Fred estimated that he wouldn't release it for about 6 months perhaps more, then a week or so ago he put up an estimate of a couple weeks. So I guess it could come out any day, or it could come in more than half a year. With out collaboration, there isn't much I can do to help contribute with this code, so I guess I should just sit back and wait.EssEss wrote:yep - knowing that something is around the corner prevents me from wanting to contribute to a base which will be obsolete momentairly. i've got plenty of other things to keep me busy until it happens.
Fred's firmware development diary comments thread
Re: Fred's firmware development diary comments thread
Re: Fred's firmware development diary comments thread
You know, your firware devel thread... Needs a link IN IT, perhaps at the bottom (or link to all locked threads' comment threads in your sig). If I was the kinda person who could go through all the steps of leaving one thread, finding another, and posting in there... Well, I could probably just open and close my injectors on my own and wouldn't need some computer to do it for me.
Re: Fred's firmware development diary comments thread
I cloned the Fred's vanilla. I then ran Doxygen, to generate the most uptodate documentation I can, based on this latest dev copy. Under the module section I see "Currently only NipponDenso is semi functional." Does that still hold true? I believe NipponDenso was what was used in the Volvo, so that is now mostly functional correct? Was that the RPM code used for the volvo?
Re: Fred's firmware development diary comments thread
No docs have been updated since the code was written. Simple was what I ran on the volvo. NipponDenso was what I ran on the bench in the UK. 36-1 was also semi functional last time that I checked it.
Fred.
Fred.
DIYEFI.org - where Open Source means Open Source, and Free means Freedom
FreeEMS.org - the open source engine management system
FreeEMS dev diary and its comments thread and my turbo truck!
n00bs, do NOT PM or email tech questions! Use the forum!
The ever growing list of FreeEMS success stories!
FreeEMS.org - the open source engine management system
FreeEMS dev diary and its comments thread and my turbo truck!
n00bs, do NOT PM or email tech questions! Use the forum!
The ever growing list of FreeEMS success stories!
Re: Fred's firmware development diary comments thread
So what code did you use in the Volvo to decode the RPM signal? NipponDenso.c, or other? I see 36-1 mentioned over in this thread.Was that the RPM code used for the volvo?
http://www.diyefi.org/forum/viewtopic.p ... 2&start=10
Did you use the MissingTeeth.c code? That chunk of code is less commented than much of the other code, which might indicate you didn't use it, however, it also notes 36-1, so it might have used.
Re: Fred's firmware development diary comments thread
Was that the RPM code used for the volvo?
Fred wrote:Simple was what I ran on the volvo.
jharvey wrote:So what code did you use in the Volvo to decode the RPM signal?Was that the RPM code used for the volvo?
:-)Fred wrote:Simple was what I ran on the volvo.
DIYEFI.org - where Open Source means Open Source, and Free means Freedom
FreeEMS.org - the open source engine management system
FreeEMS dev diary and its comments thread and my turbo truck!
n00bs, do NOT PM or email tech questions! Use the forum!
The ever growing list of FreeEMS success stories!
FreeEMS.org - the open source engine management system
FreeEMS dev diary and its comments thread and my turbo truck!
n00bs, do NOT PM or email tech questions! Use the forum!
The ever growing list of FreeEMS success stories!
Re: Fred's firmware development diary comments thread
Sorry about that, I didn't see it because I was looking under the modules. I see it in the file list now. Thanks for the pointer to it.
Re: Fred's firmware development diary comments thread
No worries! :-) I guess I should update the docs huh... ok, point taken!
DIYEFI.org - where Open Source means Open Source, and Free means Freedom
FreeEMS.org - the open source engine management system
FreeEMS dev diary and its comments thread and my turbo truck!
n00bs, do NOT PM or email tech questions! Use the forum!
The ever growing list of FreeEMS success stories!
FreeEMS.org - the open source engine management system
FreeEMS dev diary and its comments thread and my turbo truck!
n00bs, do NOT PM or email tech questions! Use the forum!
The ever growing list of FreeEMS success stories!
Re: Fred's firmware development diary comments thread
It's a dev release, not an official release, I'd say continue working on the good stuff, and worry about the doxy stuff when it's closer to an official release. Besides, if I wasn't so programing incompetent, I'd be able to figure out which one it used, with out the assist.
Thanks for the assist.
Thanks for the assist.
Re: Fred's firmware development diary comments thread
Docs for Simple.c updated and pushed (while on the toilet lol, geek humour, the worst kind).
I forgot to the header, so I'll do that now if it needs it. Then I'll update the copyright years on the other files that I've changed since last year, too...
Fred.
I forgot to the header, so I'll do that now if it needs it. Then I'll update the copyright years on the other files that I've changed since last year, too...
Fred.
DIYEFI.org - where Open Source means Open Source, and Free means Freedom
FreeEMS.org - the open source engine management system
FreeEMS dev diary and its comments thread and my turbo truck!
n00bs, do NOT PM or email tech questions! Use the forum!
The ever growing list of FreeEMS success stories!
FreeEMS.org - the open source engine management system
FreeEMS dev diary and its comments thread and my turbo truck!
n00bs, do NOT PM or email tech questions! Use the forum!
The ever growing list of FreeEMS success stories!