EMStudio is nice and easy to use, I use it to debug my A/D circuite and the MAP works fine and so is my MAX9924. My question is how to stimulate injectors
my MAP
under normal ambient temperature
Drain it and see how low it can reach
This is the pressure my Buick Regal's GM 3.1 can reach at idle
Use a function generator to stimulate tach input
I can see the count increase again and again from 0-255
Then I populate vnp10n07, but the leds don't blink but keep light on
I use this firmware so far
any way, can I use 60-2 decoder to run my engine?
My ECU build thread for Citroen ZX 1.6 gasoline
My ECU build thread for Citroen ZX 1.6 gasoline
Last edited by HotCat on Tue Jan 22, 2013 4:56 pm, edited 1 time in total.
Re: My recent work and some questions
Re your FETs, load them with a simple light bulb to ensure the outputs go to the 12V rail when off.
Re testing your FETs, you can use the BencTest firmware to switch them on and off. MTX still supports it AFAIK, but may crash. You can get SOME results from the prerolled bin packets in the lib dir without any tool, too.
Re 60-2, maybe. It needs work, and testing. You can certainly try, but if you do, do NOT rev above 2500. If you get it running and take 17th place with the low redline I'll prioritise the fix for that.
PS, good to see you around again! :-)
Fred.
Re testing your FETs, you can use the BencTest firmware to switch them on and off. MTX still supports it AFAIK, but may crash. You can get SOME results from the prerolled bin packets in the lib dir without any tool, too.
Re 60-2, maybe. It needs work, and testing. You can certainly try, but if you do, do NOT rev above 2500. If you get it running and take 17th place with the low redline I'll prioritise the fix for that.
PS, good to see you around again! :-)
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!
-
- LQFP112 - Up with the play
- Posts: 211
- Joined: Tue May 01, 2012 4:17 pm
- Location: Shrewsbury PA
- Contact:
Re: My recent work and some questions
Yay!HotCat wrote:EMStudio is nice and easy to use, I use it to debug my A/D circuite and the MAP works fine and so is my MAX9924.
Re: My recent work and some questions
Give him bench test mode ;-)
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: My recent work and some questions
Good idea, I'll try itFred wrote:Re your FETs, load them with a simple light bulb to ensure the outputs go to the 12V rail when off..
I don't like MTX, I prefer EMStudio. Or I can simply skip this step, load 60-2 firmware and use a 60-2 sin wave to stimulate it, is that feasible?Fred wrote:Re testing your FETs, you can use the BencTest firmware to switch them on and off. MTX still supports it AFAIK, but may crash. You can get SOME results from the prerolled bin packets in the lib dir without any tool, too.
I decide to do a parallel install, fuel only. A lot of work need to be figures out myself such as how to generate IAT and CHT curve for my OEM sensor. Does FreeTherm have windows binary like EMStudio. Also I would like to use my timing light to calibrate the ignition offset in 60-2Fred wrote:Re 60-2, maybe. It needs work, and testing. You can certainly try, but if you do, do NOT rev above 2500. If you get it running and take 17th place with the low redline I'll prioritise the fix for that.?
I've read your milestone, I know how to participate my role, I have enough patient, I am your tester not simply a userFred wrote: PS, good to see you around again!
Last edited by HotCat on Wed Dec 26, 2012 6:32 pm, edited 1 time in total.
Re: My recent work and some questions
MTX is good for what it is, and that's a MS app. EMStudio is good because it's a custom fit around our needs. IE, Mike listened to me :-)I don't like MTX, I prefer EMStudio.
Yes, if you can generate the pattern, it should work at low RPM at least.Or I can simply skip this step, load 60-2 firmware and use a 60-2 sin wave to stimulate it, is that feasible?
The limitations apply to all uses, even just sensing RPM with no injection or ignition.I decide to do a parallel install, fuel only.Fred wrote:Re 60-2, maybe. It needs work, and testing. You can certainly try, but if you do, do NOT rev above 2500. If you get it running and take 17th place with the low redline I'll prioritise the fix for that.?
Neither of these are critical for getting up and running. Both only matter in terms of tune "portability" and can be semi ignored at first provided that they're closish.A lot of work need to be figures out myself such as how to generate IAT and CHT curve for my OEM sensor.
FreeTherm ONLY exists as a .exe :-) It's a mono C# app. The latest one works on Linux again, not just windows like the older ones (maintenance decision by mono maintainers).Does FreeTherm have windows binary like EMStudio.
Necessary step on any vehicle setup.Also I would like to use my timing light to calibrate the ignition offset in 60-2
I wasn't complaining at all! Just saying that you've not been around for a while, and your presence has been missed! <3 :-)I've read your milestone, I know how to participate my role, I have enough patient, I am your tester not simply a userFred wrote:PS, good to see you around again! :-)
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: My recent work and some questions
I can see the rev above 2500, what's happend? very confusedThe limitations apply to all uses, even just sensing RPM with no injection or ignition.
I don't understand the words "provide that they're closish", can I completely ignore the IAT and CHT, only have Tach, MAP to start the engine?Neither of these are critical for getting up and running. Both only matter in terms of tune "portability" and can be semi ignored at first provided that they're closish.
I wasn't think that way, I just want to express I always to be the FreeEMS followerI wasn't complaining at all! Just saying that you've not been around for a while, and your presence has been missed! <3
My 60-2 interface seems OK, it's time to figure out how to configure firmware to accept my new engine
What is the combustion Sync flag mean?
Re: My recent work and some questions
That doesn't mean that it's safe or working correctly, though! Beware!HotCat wrote:I can see the rev above 2500, what's happend? very confused
You can't leave the inputs floating/badly wrong, unless you hard code it in the config. Which is easy to do. HOWEVER, CHT will need a potentiometer so you can track engine temperature to control enrichment. Cold setting won't work when hot and vice versa. Cold enrich is a big value for most engines.I don't understand the words "provide that they're closish", can I completely ignore the IAT and CHT, only have Tach, MAP to start the engine?
So, on that basis:
CHT: Get it working within 5 degrees of reality or so before you try to run it.
IAT: Put a resistor in its place, or set the config to fixed value or approximate weather conditions where you're at. Or hang a spare sensor off the front bumper and wire that up.
I appreciate it! I hope it continues into the future.I wasn't think that way, I just want to express I always to be the FreeEMS follower
If you have any questions, please ask. :-) Andy, Sim, Peter, Sean, Mike, and likely others all know how to do it :-)My 60-2 interface seems OK, it's time to figure out how to configure firmware to accept my new engine
Unused in your installation, so ignore it. Ditto cam sync.What is the combustion Sync flag mean?
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: My recent work and some questions
I know how to do it in firmware nowYou can't leave the inputs floating/badly wrong, unless you hard code it in the config. Which is easy to do. HOWEVER, CHT will need a potentiometer so you can track engine temperature to control enrichment. Cold setting won't work when hot and vice versa. Cold enrich is a big value for most engines.
By 3 years evolution, FreeEMS source code had significant changed from 0.0.1. The comments are rich and easy to understand. I can see Fred put so much effort to encapsulate the basic data structures in order to keep the code clean and high level abstract, I hardly find a hardwired code around, I think Fred definitely want FreeEMS to be run on all the gas engines every build. I start to believe FreeEMS don't need document, the source code is the best document. By searching the CONFIG == PRESTO_ID, I quickly sorted out how to make FreeEMS to schedule my injectors and ignition pins. Also I can construct my own VE table based on Fred's truck. Other parameters that I don't understand can always get the answer reading the source codeIf you have any questions, please ask. Andy, Sim, Peter, Sean, Mike, and likely others all know how to do it
Code: Select all
#elif CONFIG == CATPOWER_ID // HotCat's Citroen ZX
anglesOfTDC: {ANGLE(0), ANGLE(180), ANGLE(360), ANGLE(540), ANGLE(0), ANGLE(180), ANGLE(360), ANGLE(540)},
outputEventPinNumbers: {0,1,0,1,2,3,2,3}, // Wasted spark, semi-sequential TODO migrate this to sequential
schedulingConfigurationBits: {0,0,0,0,1,1,1,1}, // First four ignition, last four injection
decoderEngineOffset: ANGLE(144.00), // need to prove with timing light
numberOfConfiguredOutputEvents: 8, // See two lines above
numberOfInjectionsPerEngineCycle: 2 // Semi-sequential, for now.
At last, Merry Christmas
Re: My recent work and some questions
Thank you very much for the very kind words! ♥HotCat wrote:By 3 years evolution, FreeEMS source code had significant changed from 0.0.1. The comments are rich and easy to understand. I can see Fred put so much effort to encapsulate the basic data structures in order to keep the code clean and high level abstract, I hardly find a hardwired code around, I think Fred definitely want FreeEMS to be run on all the gas engines every build. I start to believe FreeEMS don't need document, the source code is the best document.
Great, but there are some "gotchas" there. Please make sure you're rebased onto the latest and then push a clean change set to github for review before you try to fire it up.By searching the CONFIG == PRESTO_ID, I quickly sorted out how to make FreeEMS to schedule my injectors and ignition pins.
Structure/format, OK, fine. But the values in the table are mostly wrong - even for my truck :-)Also I can construct my own VE table based on Fred's truck.
Code: Select all
#elif CONFIG == CATPOWER_ID // HotCat's Citroen ZX
anglesOfTDC: {ANGLE(0), ANGLE(180), ANGLE(360), ANGLE(540), ANGLE(0), ANGLE(180), ANGLE(360), ANGLE(540)},
outputEventPinNumbers: {0,1,0,1,2,3,2,3}, // Wasted spark, semi-sequential TODO migrate this to sequential
schedulingConfigurationBits: {0,0,0,0,1,1,1,1}, // First four ignition, last four injection
decoderEngineOffset: ANGLE(144.00), // need to prove with timing light
numberOfConfiguredOutputEvents: 8, // See two lines above
numberOfInjectionsPerEngineCycle: 2 // Semi-sequential, for now.
For now! I really dislike the way it's done, so it'll be changing a lot in future. It'll stay similar in some ways, though :-)ADC reading, generateCoreVars, generateDerivedVars, calculateFuelAndIgnition, scheduleOutputs, this is how the FreeEMS works
M$ Visual Studio, well I'll be damned, I never thought I'd see the day! :-o
To you too, hotcat! :-)At last, Merry Christmas
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!