Miata Turbo Forum - Boost cars, acquire cats. - Car won't start ms2

- MEGAsquirt (https://www.miataturbo.net/megasquirt-18/)

- - Car won't start ms2 - '99 (https://www.miataturbo.net/megasquirt-18/car-wont-start-ms2-99-a-44429/)

Car won't start ms2 - '99

The car won't start. I smell fuel from the exhaust but it wont spark.

My rpm cranking was at 300 and now at 200. Nothing.No spark.
I m reading rpms and all the sensors gauges show decent values.
With stock ecu car fires right up.
I'm using toyota cops also.

Dwell settings: crank dwell 4.5
max dwell 2.5
spark dur 0.7

Well not to be lame but why do you not get a spark?

Without it you are never going to get the car started. If you built the MS yourself does the circuit work? Is your wiring from the MS to the loom okay?

Whats your battery voltage? You say your cranking droped so much that might be due to a flatish battery which wont help you.

Pull a plug and check you have a spark id suggest.

I pulled the plugs, that was my conclusion that I had no spark. The unit was built by Reverant which worked in his car succefully (01-05) Mine is 01-05 too but with '99 engine.
As for the cranking rpms I am refering to the software settings.
Battery voltage is around 11.5V
The stock ecu fires right away even now.

Here is my msq
MEGAUPLOAD - The leading online storage and file delivery service

His unit tested out ok on the stim, plus it's the MS-2 I had on my car before getting the DIYPNP, including the adapter harness.

Jim

what version firmware and please upload your MSQ.

Brain you can see my msq on my 2nd post.
I have a 2nd problem now, during uploading a new msq tunerstudio got stucked and now I cant get the ms to connect to the laptop.

Which TS version are you running?

the ms2 firmware is 3.0.3q

I would at first try to reflash the newest firmware (which is 3.0.3r) and reload the tune.

I think you should at least be able to flash the firmware - maybe TS can connect again after this...

Greets

In the download .bat it says when trying to connect: opened comm 4 at 115200. ERROR: timed out reading response 0xE0

For some weird reason, burning the msq corrupted the firmware. The fuel pump would turn on at startup, but nothing else worked, including comms. Burning a new firmware with the bootloader was not possible. I had to set the boot jumper and burn the entire firmware including the bootloader from scratch and restore the msq.

After doing that, I scoped the coil trigger signal, only to find out that with the COPs, the trigger signal is reduced to 1V! Remove the COPs, and the signal is 5V. We installed a half-burnt stock coilpack and it actually tried to start (and there was spark). So the problem is definately with the Toyota COPs. I will investigate further and report.

Jim

Damned toyota cop's Jim.

Quote:

Originally Posted by gianic (Post 530394)

In the download .bat it says when trying to connect: opened comm 4 at 115200. ERROR: timed out reading response 0xE0

This is the exact error I was getting trying to help a buddy this weekend. His laptop could not flash the unit, but mine did right away the first time. However once i got the map loaded and the car running the tune kept walking and the sync dropped out. Seems like I need to reflash it again and build the msq by hand.

Quote:

Originally Posted by Q

Ben or Matt,

I helped upgrade Lar's (Shueinds - He had his black BEGi car down there last year for tuning) MSI to MSII. We had an issue flashing the firmware, kept getting "received e=c0x0" errors with his laptop. Using my laptop there was no issues whatsoever.

Once running, the communications seems bad and it kept having sync drop outs, and to top it off the map would constantly alter from the offline tune, tuner studio kept giving me warning, after it would reload the offline tune, it would happen again after a few minutes, crazy random values in the spark table. We couldn't figure out the issue and he now driving around on my spare MS-I box.

Can you take a look at this log and point us in the right direction?

Quote:

Originally Posted by A

When the map walks around by itself, it's because of corruption in the firmware. It's usually caused by opening a blank tune in MT or TS, and then trying to create a base map from a blank tune. If you have the ECU hooked up to the laptop and basemap it while online, this type of thing generally does not happen. Though it could also have occurred since you had so much trouble flashing in the first place.

At this point, I'd flash the firmware again (including the boot strap), then basemap it while on line. You can move over any/all of the tables in .vex, but everything else needs to be done by hand.

For future reference, the Toyota COPs don't work with 1K resistors on D14 and D16. You need something lower, in the 330 range. The stock 2001+ coilpacks work fine on 1K.

Jim

Car is running fine now, thanks rev!