msq is attached.

It connects, but is not happy yet.

Brain built squirt running the gslender v2.2 found here: http://msextra.com/forums/viewtopic.php?f=91&t=43545"]link

Here are some problems:
- no TPS signal
- coolant reading 180F after entering calibration values from here
- strange humming sound coming from the intake when MS is on.
- not sure if I am wiring in the AIT correctly (see next post with pic)



Will be checking this thread intently over the next two hours, so I can hopefully make some progress today.

Thank you!

 

attached is the photo of where I plugged in the AIT sensor.

Some more info:

- RPMs are not reading when I tried to crank. Reading zero.
- MAP reads about 95
- I have not hooked up the wideband yet
- I can hear the fuel pump running
- MAT jumps from 0-60-0 in weird little pulses

When i click 'Test Port' it initially says successful, then gives me an error message, then connects. See attached pic.

 

Don't let my name or sig fool you- this is an install on a 1999.

 

My noobish guess is a firmware issue.

I am not able to write anything to the MS. It will not even burn a change to the fuel table. It lost the calibration settings for coolant and iat after restarting.

Edit: it says 'not synced' lit up in red in the bottom right.

 

Why would you think that? Fix your config error! You can't do anything until you do that! The flashing red tach that cycles between 0 and 65k rpm, the pulsing fuel pump, the config error pop window, and the red light that says config error are supposed to be clues that something is wrong. And the pop up window tells you how to go about fixing the problem.

Since Braineack was able to connect, it's probably a safe bet that your problem is related to your USB adapter (I assume you're running a serial -> usb) or improper project settings. What kind of cable are you using? Take a screen shot of your communications settings.

There are a few threads on the msextra forums on this. Here are a couple of links

http://www.msextra.com/forums/viewto...?f=101&t=31532
http://www.msextra.com/forums/viewto...?f=101&t=40590
http://www.msextra.com/forums/viewto...?f=131&t=43173

 

I misspoke and did not mean firmware. I meant what I have loaded in tunerstudio. The .ini stuff. Brain is going to send me the right stuff tonight, and will try ago in tomorrow.

The computer is back with the car at another house, can not do a screenshot now.

I don't have a USB. I think it is just called a serial cable. The cable was working fine before the upgrade to ms2.

 

I read through those threads Ben. Looks like it is possible it is my cable. Since it was working on the MS1 with no problems, maybe it can not handle the increased baud rate (I think that's what they call it).

Brain sent me a new project folder and .ini, and it is still acting the same.

I attached a pic of the communications settings. This is after it tells me the connection is successful.


Anything stupid that I am just not thinking of? Last time I had to deal with setting things up was a few years ago, and I struggled then.


I can not upload the pic- but here is what it says:

Comm Settings
Port: COM1
Baud Rate: 115200
Successful!!!

Then the message of death:
turbo99final Controller Error: You have a configuration error!
This means there are conflicting settings and the Controller does not know how to handle them.
The Controller message below should provide some guidabce to the incorrect settings.
Correct your settings then powercycle the Megasquire You do not need to reload the firmware to fix this problem.

Controller message:
Seral problem- framing error - possible cable, computer hardware or settings problem.

 

that project folder i sent you, put that into your tunerstudio project folder. then go to file, open project, and select that one. then try to connect. if it doesn't work it's gotta be your version of TS or your serial cable.

 

I think I have the most recent version: 1.006.

And who the ---- are you, anyway? Who the ---- are they?
Who the ---- am I to say? What the ---- is really going on?
How did the ms2 get so fat?

I am going to start shopping around for a new chord.

 

Before you get a new cable, have you tried any of the comms troubleshooting from the manual? What about reloading the firmware and starting a new project? I would try that, and I'd try it with the most recent stable firmware.

serial troubleshooting
http://www.msextra.com/doc/ms2extra/serial_setup.html

firmware
http://www.msextra.com/doc/ms2extra/....1_release.zip

 

Thanks, I will read that.

I wanted to bring the car home tonight, so I put in the old computer and hooked everything back up. Won't start.



I can smell raw fuel at the tailpipe. Don't know how timing could have changed, so that leaves me with spark. I thought we were done with the days of worrying about blown coil packs?!? ----

Maybe related: that humming sound I mentioned earlier is still there when keyed on. I can't locate the exact source, but it is strongest at the intake piping. It is not the maf. Maybe something wired with the supercharger. Idk. Frustrated at the moment.

Have a truck I can drive, but I want to try to get this sorted out quickly.

 

Just curious, but is this a DIYPNP?

 

Do not belive so. It was originally a ms1 that I have been using on my 94 for the past few years. Brain sprinkled some cat hairs on it, and it turned into the ms2.

 

ugh, had a long post written and the stupid blackberry playbook crashed the browser. Technology fails me today.


Brain, when I tried that, it would not connect at all. Kept giving the same error message indicating hardware or setting problem. I checked for updates of TS and I have the most recent.



Have been using an old laptop with windows 2000 professional. COM troubleshooting scares me.

I have a new laptop with windows 2007, but will need a usb. Ordered the cable mentioned in the first post here.


Nervous about the no start on the stock* computer. On Saturday, I cranked to check for rpm in tunerstudio (none shown), and I am pretty sure I still had the maf connected. What did I fry? I doubt I will start on ms, when I can't now.

I do not know if the humming sound is pre or post supercharger (forgot to pull off all of the intake pipes). It is noticeably loud. The super has no electronics. I have no idea.


* 99 computer with VF Engineering chip

 

My megasquirt originally was a MS-1 3.0 running in parallel on a '97 Miata. I bought it and it ran parallel on my '99 with a CAS retrofit. Then It turned into an MS2 standalone with a PNP board. Then it turned into an MS2 Standalone with all the circuits inside of the MS case. Now it runs my car all the time and makes me smile. (Except for slightly high idle).
Once you get this thing to connect and you get it running, I'm curious to see how this works out for you. I'm also interested in more details, but that's another time...no thread jack here.
Good luck getting it sorted out!

 

Morning bump for the working crew.

New cable arrives on Wednesday.

Guesses as to what I need to fix to run stock computer?

 

yeah I've never seen that error before. I had no issue loading the firmware and map and stiming the ECU.

 

anything? Take some guesses please.

summary:
-car ran flawless before failing at ms2 install, including a couple cranks
-back on stock computer: cranks but no start. Raw fuel smell from tailpipe.
-strange electrical humming sound from the intake piping (not the MAF) when key switched 'ON'. Humming present also with ms2 plugged in. Never noticed it before last weekend.


Have tunerstudio installed in the newer laptop, and received the new chord.




Stupid question for brain:

should I load the "CurrentTune" you sent to me in the project folder or should I try to load the msq contained on the MS?

Stupid questions for everyone:

There are two plugs in the air filter area. One is clearly going to the MAF. The other has two wires and is sticking out of the end of the filter. Do I plug the AIT sensor into the two wire? That is how I set it up last weekend (see third pic). What do I do with the MAF plug? Leave it unconnected to anything?






I appreciate any help!

 

Do I leave these settings as is?

These do not look familiar from ms1, and it popped up by itself.

 

Diving in again tomorrow morning.

Plans are to figure out where exactly the electric humming is coming from, as well as successfully connect to the ms2.

Frustrated posts to follow.