Miata Turbo Forum - Boost cars, acquire cats. - MS2PNP Total sync loss black exhaust splatter.

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

- - MS2PNP Total sync loss black exhaust splatter. (https://www.miataturbo.net/megasquirt-18/ms2pnp-total-sync-loss-black-exhaust-splatter-69496/)

MS2PNP Total sync loss black exhaust splatter.

https://www.miataturbo.net/attachmen...ine=1353095381

Yep..
Well I got my engine running smooth yesterday (MAP sensor VAC line wasn't getting vac)
So today I was going to fix the idle (Which was at like 1500) down to the normal 800~.
Well as I achieved it, I also just installed the WBo2 so I changed the AFR tables to wideband, didn't change the EGO or the project pref yet. (forgot about them I suppose)
Idled lowered to 4-500~ next thing I know bam!, car shuts off, I'm trying to figure out what happened. No sync now, ever.
And I found this sweet black surprise waiting on me..

:crx:

Here is a datalog and synclog

This .msq currently.

I tried flashing firmware. Still no sync
+now my engine speed is crazy
I got this config error message tho:
https://www.miataturbo.net/attachmen...ine=1353104686

And here are the logs:

I disabled the Accel LED and Warm up LED outputs to get rid of the conflict.
Engine speed is back to 0.

Still no sync tho. :/
I give up.:crx:

under project properties. what do you have selected for "megasquirt selection"

needs to be microsquirt module/mspnp/diypnp

try that, reload the first map, and try again.

It was already microsquirt?

Original plan was: 99 base map and tune it from there for the boost. It's an 04 MSM engine. Same BP4W just turbo.

I also get these warnings when just trying to load the 99 base map:

Code:

18 Warnings:

Warning: Parameter in .msq, but not valid for current firmware: No options found for Bit EcuParameter:flexport equal to the proposed "JS11"

Warning: Parameter in .msq, but not valid for current firmware: No options found for Bit EcuParameter:spk_config_spka equal to the proposed "JS10"

Warning: Parameter in .msq, but not valid for current firmware: No options found for Bit EcuParameter:rtbaroport equal to the proposed "MS2 AD6/JS5"

Warning: Parameter in .msq, but not valid for current firmware: No options found for Bit EcuParameter:ego2port equal to the proposed "MS2 AD6/JS5"

Warning: Parameter in .msq, but not valid for current firmware: No options found for Bit EcuParameter:boost_ctl_pins equal to the proposed "JS11"

Warning: Parameter in .msq, but not valid for current firmware: No options found for Bit EcuParameter:tacho_opt3f equal to the proposed "D14"

Warning: Parameter in .msq, but not valid for current firmware: No options found for Bit EcuParameter:launch_opt_pins equal to the proposed "PE0/JS7"

Warning: Parameter in .msq, but not valid for current firmware: No options found for Bit EcuParameter:N2Oopt_pins2 equal to the proposed "IAC1+2"

Warning: Parameter in .msq, but not valid for current firmware: No options found for Bit EcuParameter:N2Oopt_pins equal to the proposed "PE0/JS7"

Warning: Parameter in .msq, but not valid for current firmware: No options found for Bit EcuParameter:flexport equal to the proposed "JS11"

Warning: Parameter in .msq, but not valid for current firmware: No options found for Bit EcuParameter:spk_config_spka equal to the proposed "JS10"

Warning: Parameter in .msq, but not valid for current firmware: No options found for Bit EcuParameter:rtbaroport equal to the proposed "MS2 AD6/JS5"

Warning: Parameter in .msq, but not valid for current firmware: No options found for Bit EcuParameter:ego2port equal to the proposed "MS2 AD6/JS5"

Warning: Parameter in .msq, but not valid for current firmware: No options found for Bit EcuParameter:boost_ctl_pins equal to the proposed "JS11"

Warning: Parameter in .msq, but not valid for current firmware: No options found for Bit EcuParameter:tacho_opt3f equal to the proposed "D14"

Warning: Parameter in .msq, but not valid for current firmware: No options found for Bit EcuParameter:launch_opt_pins equal to the proposed "PE0/JS7"

Warning: Parameter in .msq, but not valid for current firmware: No options found for Bit EcuParameter:N2Oopt_pins2 equal to the proposed "IAC1+2"

Warning: Parameter in .msq, but not valid for current firmware: No options found for Bit EcuParameter:N2Oopt_pins equal to the proposed "PE0/JS7"

I tried. Got disconnection.
Sometimes tells me there is noise.
Sometimes tells me it found a device on Com2 but no name/firmware.

I'm guessing I'm fucked.

Did your timing belt snap?

Quote:

Originally Posted by curly (Post 950785)

Did your timing belt snap?

I sure hope not.
What's the best way to check?

Crank car and see if the cams are moving or not.

Quote:

Originally Posted by albumleaf (Post 950787)

Crank car and see if the cams are moving or not.

Figures. A 2 person job. Sigh..

Forever alone?

Iphone? Pop the oil cap off and put your cam on. Probably in a plastic baggy. You only need a split second crank.

Quote:

Originally Posted by curly (Post 950793)

Forever alone?

Iphone? Pop the oil cap off and put your cam on. Probably in a plastic baggy. You only need a split second crank.

You know it! haha deployment made me divorced :P

nahh! Iphone = poop. Android! :D I'll give that a shot tho haha.

I'll post results!

your errors suggest you're still not setup for msicrosquirt.

JS11, JS10, and D14, etc. listed in your errors are only found on a v3.0 mainboard NOT a microsquirt module. If the basemap is being converted into using those outputs, then it's because you have the wrong setting in your project and it's making changes to the map in which it will never run on your car.

Quote:

Originally Posted by Braineack (Post 950811)

That's weird because that's the 99 map I'm suppose to load for the mspnp.
I found someones 99 ms2e turbo map and loaded that and that's when I can't connect anymore when I power cycled it. I got that noise error/warning

Well. The cams move so timeing belt isn't snapped. I'm both relieved and discouraged now tho.
Doing a timing belt sucks. But I want to know what the problem is.
Any chance the the main fuse (80A) may have blown for some reason? That'd be why I don't get spark or sync with MS? I put the stock 99 ecu in just to see if it'll start it, and nothing.

The engine fuse under the dash is good tho. so I'm thinking something in the main fuse box?

I get the constant volts to the coils, I don't get the trigger tho but I heard you need to test for hertz for the trigger?

Now I can't connect to the MS at all. [Note: This is the error if it even pops up at all]

https://www.miataturbo.net/attachmen...ine=1353218081

Getting ready to set fire to the car.
:crx:

don't load random maps; that's a sure way TO failure. Your MSPNP2 with a Microsquirt Module is UNIQUE to itself and you should not share maps that were developed around the MSPNP2 for a 99-00. Otherwise ALL the setting will be different and can cause issue like you're seeing. Not all MSes are built the same. Not all MSes share the same internals even on the same firmware.

I suggest you get in contact with DIYAUTOTUNE.com and start troubleshooting with them the issue.

As for the connection issue, the baud rate for your MS should be 116500 or whatever. So look into why it can only see 9600 baud rate.

Also, since the stock ECU wont run, it would be a smart move to look over all your fuses. If you can restore a connection to the MS, then you'd want to stop datalogging and composite logging while cranking to determine what's going on.

seriously, something major went wrong, slow down, dont make it worse by crapshooting.