99 Miata, 3rd hand ms2x installed, need help getting set up - FIXED!
 

Un-lurking for a moment here.. I have a 99 miata with a rev built ms2x installed and I'm having trouble getting it started for the first time. It just turns and turns so far. I'm completely new to tunerstudio and tuning period so I'm hoping one of you guys can take a quick look at my msq and startup attempt log and tell me what I'm missing. I'm sure I've completely overlooked something obvious to you, I just don't know enough yet to see it. Any help getting started would be greatly appreciated.

Engine: 99 bp4w 1839cc
Injectors: stock 99 Injectors (dark red) 260cc
stock o2 sensor and IAT sensor removed
GM IAT sensor and MTX-L wbo2 sensor installed.
AFM unplugged.
Everything else stock 99.

The basemap loaded on that ECU (hattrick's old ECU) was for 650cc injectors, so you will need to change them to whatever injectors your have. You will also need to almost double the cranking pulse if you have stock injectors.

Will take a look now, I am running stock 99 injectors, 260cc I believe. Thanks Reverant, I'm learning as I go.



Edit: Ok I found the Required fuel calculator, I set displacement at 1839cc, 4 cylinders, 260cc/min injector flow, and left air-fuel ratio at 14.7. This gave me a req fuel of 11.9

But I'm stuck at adjusting the cranking pusle width, you said "almost double it" - Here are the settings as they are, can you be more specific as to what I should set these at? Thanks.

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

Multiply each value on the right by 1.8 or so. So 96 becomes 172, 60 becomes 108, etc.

That's about what I assumed just needed to see someone agree really. Going to try this and see how it goes. Thanks

Thanks SJ, it fired right up with the right settings for the stock injectors. I'll auto-tune tomorrow as the sun is about to go down. I'm going back to lurk mode, I'll post if anything eventful/hilarious happens. thanks again!

Reverant, are there more settings you could recommend tweaking before driving it for an auto tune? Or will ve analyze handle a lot of the rough spots? I guess I'm confused as to what all ve analyze can adjust and what I need to adjust myself before doing any driving/autotuning.

Without knowing more about your setup, I really can't recommend changing any settings. You will want to adjust your acceleration enrichment figures if your injectors are not quite in the 650cc area.

Stock 99 engine with stock red (260cc) injectors. wideband is mtx-L, oem o2 and iat sensor were swapped with the mtx-l sensor and gm iat sensor, stock afm is gutted and unplugged until I can pick up a tube, everything else stock.

EDIT: Ok I adjusted accel enrich and calibrated for the mtx-l within tunerstudio, this has the car idiling pretty nicely now and got rid of the stumbling after quick throttle blips. I think it may be ready to autotune? but I don't know enough yet to know if it's setup properly for my car yet. AFR looks real low for one...I'm sure there's more settings I don't know about that need to be set and searching has literally led me in circles all weekend.

I'd feel better if a pr0 can look this log over and point me in a general direction. The 2nd half of the log was with VEAL running, Any help is greatly appreciated, thanks.

Latest issue, tunerstudio is randomly offlining now after two days of staying connected to my laptop just fine. Having trouble getting settings saved in time before it offlines. My usb-serial adapter com settings are default in windows and so are the communication settings in tunerstudio. Searching for answers now but if anyone has some quick answers or at least some constructive trolling by all means speak up. thanks

EDIT: After reading another similar thread - looks like plugging the power adapter in when my laptop's battery got low fried my usb-serial adapter. Replacing...

Here's the latest - Picked up a new usb-serial adapter from radio shack, tried to connect tunerstudio to ecu and I got this -

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

Wrapped the entire cable from end to end with aluminum tape per a thread I saw - didn't work for me, same result. Any ideas?

I'm about to take a bat to my ms2x, I was way happier when it had all the wrong settings for my car but I could at least connect to it. After buying new serial adapter I'm still not connecting and when I set my port to 115200 and detect in tunerstudio it finds the port at 9600. WTF.

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

Which USB converter did you get?

Also, this may sound ridiculous but try a different USB port. If you are using a USB port that is say, on the left side of your laptop, try the one on the right side.

I got the gigaware 6ft one from radio shack that we talked about. Worked for many others I've seen in many threads. I tried every usb port on the laptop. and tried software coms 1-5 on each usb port. No dice. During this process my error went from "serial noise" to "framing error" and back again. It's pretty frustrating. The entire cable end to end is shielded ghetto style with aluminum tape. triple thick around the chip in the cable.

Ran a port scan, It looks like my adapter is only letting me talk to the ms2x at 9600 baud, even after changing the port settings in windows. Com3 in this list is my modem, disabled that just for testing and still same results otherwise. So basically it looks to me like my computer is coming at the ms2x at 9600 baud speed and the ms2x is like wut? A friend offered to let me borrow another known-good cable for testing, it's one of the FTDI ones, hope to report some good news in the next few days. Here's latest screen- oh and on tunerstudio's detect device tool - I'm hoping it says unknown firmware only because it's not able to talk to the ms2x at the proper speed. That's a mess I don't want to add to this mess for sure..

Also note I'm running tunerstudio v2.0.6, I had same issues with 2.0.8 so I tried the previous release, saw it recommended in a similar situation in a different thread. Is it worth trying this on the beta version that's currently available or is this likely just a cable issue?

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

Do you get this with just the ignition on and the engine not running?

Is the laptop on battery power or are you using an inverter?

Oh, the 9600 baud rate is totally wrong, no idea why TS even accepts a reply like that. Keep it at 115200.

Ignition on, engine not running, correct. Laptop always on battery power when connected to the car now, after frying my first usb-serial adapter when I plugged in the inverter during communication.

It's set at 115200 in windows and in tunerstudio. No idea why it's doing 9600 in port check and in detect device tool. All I can think of at this point is it's gotta be the new adapter I bought yesterday. But why did the same adapter work just fine for so many others in the past I wonder. Serial is on my nerves.

Do you have access to another laptop you can try?

I've seen the weirdest things with these adapters and their drivers.

I'll steal my wife's and report back in 20 mins. Good call might as well check the basics eh.

EDIT: Oh, which flavor of tunerstudio? 2.0.6, 2.0.8, or beta? And i'll need to create new project, and follow your settings, import that .ini, setup tps again etc right? if it works that is.

im running beta 2.2.11 without issue, but 2.0.8 is the latest stable release.

Use a different version of TS on the other laptop, just to rule it out.

I went with 2.0.8 on her notebook since 2.0.6 is on mine, and when I originally was able to communicate with the ecu it was on 2.0.8 - Created new project, imported .ini, got to the communications settings and - same exact results. Seems through this adapter (my first one that died was prolific) my computer wants to talk to the ecu at 9600 even if I have 115200 set in device manager. Ecu wants to talk at 115200 so I get invalid data from ecu error in tunerstudio. Tried different com port numbers and different usb ports on the laptop. It's gotta be this radio shack adapter. I'm picking up an FTDI chipped cable from a friend this evening. Should know if it was the cable or not in about 4 hours. I will post back with my findings. Thanks.

The cable you have should work, i just had issues getting drivers for win7, otherwise on XP and vista it was fine.

I did a fresh install of xp sp3 last night just to check. Same result, but I'm using an all-in-one driver from radio shack. Everything I find when searching for this adapter leads back to radio shack's support site. If you can look at your drivers and tell me what the real name of the device is that should help me find better drivers. You near your laptop?

Are you on 32bit or 64bit Windows?

win7 home premium 64 bit.

Just saw a thread where a guy waited for win7 to locate a driver without using the radio shack one and it worked for him. Going to clear out that driver and see if the win7 native driver does any good. Will report back in a few minutes..

Ok I uninstalled all hidden devices and drivers in my ports section. Plugged it back in, windows 7 DID have a microsoft driver for it, but still, no dice. Same connection issue. My computer only seems to want to communicate through this cable at the default speed of 9600. Looking forward to picking up the ftdi cable tonight, hope that just works..

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

Can you please not perform the autodetection method and instead follow the manual method described in the instructions instead? Ie select "Show Advanced/Offline setup", then select "Other/Browse", and select the .ini file I emailed you.

I did it the way the instructions said to at first. Then to test, I swapped usb ports and adjusted com port settings to match and then took the screenshot you see. Just to cover the base, I will go delete the project folder and start from step 7 in your instructions. Be right back..

Same result, testing port never succeeds so I can't connect and go further than step 31. Here's some huuuuge pics. Also to Brain, you said this cable worked with the radio shack driver and windows vista for you? I have a copy of vista home premium I'm willing to install but it's 64 bit... was yours?

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

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

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

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

Just talked with my dad and he has an old laptop with a serial port, and I have an old serial cable still in the package from my old laptop. Going to put a fresh copy of xp 32 bit on that laptop and see if I can connect tonight. I'll post up afterwards, this has gotta work haha... fingers crossed.

EDIT: Old school good-ness! As a computer guy I've never been so happy to have something with a serial port on it..

http://i49.tinypic.com/uy6ph.jpg

So it worked fine with a serial port?

Turn the FIFO buffers off.

I have no end of trouble with them turned on.

Yeah it was late when I connected and I went to sleep right after or I'd have posted up last night. I stayed connected for about 10 mins without an issue, setup a new project and calibrated the tps and went to bed. Thanks for the help guys, hopefully the connection issues won't be back in any form.

Now back to tuning - What are the first things I need to address in this tune to adapt it to my stock 99? Accel_enrich, req_Fuel, cranking PW, and what else? Keep in mind I'll learn all this soon, but for starters sake, help a brutha out and share some settings if any of you have a stock 99 engine with stock injectors. It's running so lean right now during acceleration and deceleration that I'm afraid to drive it three blocks to a friend's shop to base tune it.

Never heard that one yet, they were on when I connected with serial and everything seemed fine though.

Ok car was base tuned this morning by a local miata/ms2 guru. He said the true serial connection had zero disconnects. It's idling and driving smooth, I'm just waiting on a battery for the old laptop and I'll get to autotuning. I've got the ms2 tuning guide in front of me and learning away. Anyways thanks again guys, I'm going back to lurking until I convert to e85 and bigger injectors this summer. That should be fun eh?!

Try it.

You can also try with them on, but move the sliders to absolute minimum.

I always turn them off and every USB>Serial converter I've tried works fine.

Drove for an hour this morning while running VE Analyze Live with updates on - holy jeebus this is so much better than the stock ecu. I wish I'd have done a dyno pull on stock ecu before I installed this, just to see the real difference. Butt dyno says theres way more power already and it's not even close to done tuning yet.