Page 1 of 1
Posted: Sun Dec 23, 2007 11:49 am
by jsmcortina
The reason not to write the data while the engine is running is because the fuelling lookups would get scrambled as there would be FF FF FF FF instead of the lookup data in the time between the erase cycle and the new data was loaded down the serial port.
James
PS. The microcontroller is Freescale, nothing Intel here.
Posted: Mon Feb 04, 2008 5:11 am
by Scrampa
Then could this be why my CLT values haven't properly changed when using the Stim (ecu is seeing a running engine)? I will try to calibrate later tonight with ecu in the car/engine off.
Re: WARNING: Calibrating AFR/Thermistor Tables
Posted: Tue May 26, 2009 6:24 pm
by DonTZ125
Just so I'm absolutely clear - you can TUNE the VE & spark tables in RAM while running, but you must shut off to actually burn to Flash. Is that right?
Re: WARNING: Calibrating AFR/Thermistor Tables
Posted: Wed May 27, 2009 5:52 am
by Matt Cramer
DonTZ125 wrote:Just so I'm absolutely clear - you can TUNE the VE & spark tables in RAM while running, but you must shut off to actually burn to Flash. Is that right?
Close. You can tune the VE and spark tables while the engine is running, and you can burn to Flash on a running engine, though some code versions will hiccup a bit when you burn to flash so it's best not to do that at full throttle. (Note that MS2 B&G code is pretty good at not hiccupping when burning to flash.) What you must not do on a running engine is calibrate the temperature sensors while the engine is running.