MS3 Basic: installed latest firmware and now car will not start.
#1
MS3 Basic: installed latest firmware and now car will not start.
I recently updated the firmware to my ecu to fix a bug that prevented the throttle position gauge to work. After installing the new firmware and calibrating the VTPS (Wells 201) the TPS gauge in tuner studios is now working
However, the car does not start anymore. It will turn but will not start. Any ideas (settings?) on how/where I can start troubleshooting?
TIA,
Linh
However, the car does not start anymore. It will turn but will not start. Any ideas (settings?) on how/where I can start troubleshooting?
TIA,
Linh
#2
Boost Pope
iTrader: (8)
Join Date: Sep 2005
Location: Chicago. (The less-murder part.)
Posts: 33,046
Total Cats: 6,607
Stupid questions:
Did you re-load the configuration (MSQ) after doing the update?
When you crank the engine, do you see a stable, believable RPM indication on the TunerStudio dashboard?
What firmware revision were you running previously, and what revision did you update to?
Did you re-load the configuration (MSQ) after doing the update?
When you crank the engine, do you see a stable, believable RPM indication on the TunerStudio dashboard?
What firmware revision were you running previously, and what revision did you update to?
#4
A little more specific: The configurations I used was basically from my msq tune on the previous firmware. I also uploaded the .ini file that came with the new firmware and still the car does not start.
Tuner Studio's RPM gauge does not move at all when the car is trying to start.
TPS works fine tho.
Tuner Studio's RPM gauge does not move at all when the car is trying to start.
TPS works fine tho.
Last edited by Linh; 07-03-2013 at 07:57 PM.
#7
Boost Pope
iTrader: (8)
Join Date: Sep 2005
Location: Chicago. (The less-murder part.)
Posts: 33,046
Total Cats: 6,607
For kicks, connect to the MS and take a look at the "Ignition options / wheel decoder" screen under the "Ignition Settings" button. It sounds to me like the MS may simply have reverted back to a default configuration.
If you have an NA, this should say 4G63. If you have an NB, it should say "Miata, 99-00"
If it says anything else, your old configuration was not properly restored. Don't just fix this one setting- everything else is probably hosed as well.
You can probably fix it simply by re-loading a previously-saved MSQ file (including any of the auto-save files from prior to the firmware update.)
#9
Okay. I checked the ignition configs and it was on "tooth wheeled". I reloaded the firmware once again successfully and now it is at 4G63.
Edit: Im a noob. I didnt unplug this the first time uploading the firmware.
http://www.megasquirtpnp.com/gen1/mo...s/image025.jpg
Now, my ignitor is probably damaged?
Edit: Im a noob. I didnt unplug this the first time uploading the firmware.
http://www.megasquirtpnp.com/gen1/mo...s/image025.jpg
Now, my ignitor is probably damaged?
#10
Boost Pope
iTrader: (8)
Join Date: Sep 2005
Location: Chicago. (The less-murder part.)
Posts: 33,046
Total Cats: 6,607
Edit: Im a noob. I didnt unplug this the first time uploading the firmware.
http://www.megasquirtpnp.com/gen1/mo...s/image025.jpg
Now, my ignitor is probably damaged?
http://www.megasquirtpnp.com/gen1/mo...s/image025.jpg
Now, my ignitor is probably damaged?
That caution relates to the "standard" ignition driver design commonly used in the MS1 and MS2. In those, the state of the ignition outputs is OPPOSITE that of the CPU pins which drive them- they naturally tend to float high, and the CPU must actively pull them down.
The MS3X uses a 74AC541 IC as its ignition output driver, and that chip is non-inverting (outputs follow inputs.) So as long as the output pins of the MC9S12 CPU naturally float low when un-driven (which I believe they do) the ignition outputs should be "safe" during a reflash.
This is all just speculation, of course. I've never tried it. But I suspect you're ok.
#12
Boost Czar
iTrader: (62)
Join Date: May 2005
Location: Chantilly, VA
Posts: 79,501
Total Cats: 4,080
you're reloading your 1.2.2 MSQ after you're loading the 1.2.3 firmware and starting, correct?
every time I upgrade firmware, i start a new project with the new firmware .ini (at least detect it and d/l it), then I'll connect to the unit and reload my old map. Calibrations should have saved.
every time I upgrade firmware, i start a new project with the new firmware .ini (at least detect it and d/l it), then I'll connect to the unit and reload my old map. Calibrations should have saved.
Last edited by Braineack; 07-05-2013 at 07:41 AM.