MS2PNP Total sync loss black exhaust splatter.
11-18-2012, 02:45 PM
#21
Senior Member
Thread Starter
iTrader: (1)
Join Date: Jan 2012
Location: Tampa, FL
Posts: 754
Total Cats: 19
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.
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.
Also ordered a serial to bluetooth, from EFI Analytics to get rid of noise problem all together.
I have no idea why it was at 9600, everything was set to the 115600 (or whatever it is)
I'm going to go threw all the under dash and hood fuses again.
Reply
0
0
11-19-2012, 07:04 PM
#22
Senior Member
Thread Starter
iTrader: (1)
Join Date: Jan 2012
Location: Tampa, FL
Posts: 754
Total Cats: 19
I actually got the laptop to connect by messing with the baud rate and transfer/receive buffers.
This is what I got when trying to load firmware.|
Picked MS2 option, 1 no debug, not first time
Also tried Microsquirt (since that's what it's called microsquirt module ms2pnp, right?), 1 no debug, not first time
This is what I got when trying to load firmware.|
Picked MS2 option, 1 no debug, not first time
Also tried Microsquirt (since that's what it's called microsquirt module ms2pnp, right?), 1 no debug, not first time
Reply
0
0
11-22-2012, 12:23 AM
#27
Senior Member
Thread Starter
iTrader: (1)
Join Date: Jan 2012
Location: Tampa, FL
Posts: 754
Total Cats: 19
Engine Is up and running now.
It was the crank angle sensor. Turns out the trigger wheel teeth were engraving themself a line in the center causing it toI go bad.
Now that the engine is working I also have a clutch that doesn't want to disengage.
I replace the slave cylinder and I also adjusted the pedal it still does not disengage.
But at least I made problem is gone right now.
I also have a 36 - 1 trigger wheel that I hear megasquirt like.
I gotta do some reading up on install/settings for it tho.
It was the crank angle sensor. Turns out the trigger wheel teeth were engraving themself a line in the center causing it toI go bad.
Now that the engine is working I also have a clutch that doesn't want to disengage.
I replace the slave cylinder and I also adjusted the pedal it still does not disengage.
But at least I made problem is gone right now.
I also have a 36 - 1 trigger wheel that I hear megasquirt like.
I gotta do some reading up on install/settings for it tho.
Reply
0
0
Thread
Thread Starter
Forum
Replies
Last Post
stoves
Suspension, Brakes, Drivetrain
5
04-21-2016 03:00 PM
