Does anyone happen to have an msq. settings file for MS2 extra? I figured I'd ask this simple question before I list any specs.
I have an "OK" amount of parameters, but not all. I guess I'll try and keep studying the MS2 documentation, unless someone has a link to a website with more rotary specific help for ms2 extra firmware.

 

ok....
Below are 2 zip files. The 1st one is my current ms2 settings that I have been able to set so far, although there are still a few areas that I left blank because I am unaware of what to set the values at. Below that are my ms-1 settings that are working so far. If anyone could look them over and give any input, I would really appreciate it

BTW, when I used firmware 1.0.2 for the ms2, I was not able to set the tps values because it was registering values between 220+ and 700+ for low and high values, but the tps is absolutely fine in ms-1extra), as well as encountering a few other problems/ glitches with the ms2 software. I also have ms2extra activated in the configure menu.

 

The raw TPS values may be different from MS1 to MS2, since for MS1 the raw TPS value is just a number from 0-255 associated with the voltage it sees on the line in, and IIRC MS2 assigns a number from 0-1024 since it is capable of more sensitive measurements/fine control

 

What I forgot to mention was that after I set the values, hit "ok" and started pressing the pedal to the floor, it would only register from 0 to 1%. 1% registered somewhere after half throttle. That's why I mentioned it.
I'll check again today, but I also remember seeing the pulsewidth stuck at 3.000ms when online, and the wideband reading was stuck at 14.70 afr even though my gauge on the PLX in the car climbed up to 19.9 and then registering "air"

 

Frustrating update:
I downloaded the MS2EXTRA Rev 1.0.2 firmware and burned it into the MS. Then, in the configuration menu, I activated ms2extra. Next, I tried to burn my ms2 file into the ms and I constantly get an error message saying "controller voltage too low for reliable FLASH burning. Try anyhow?" Regardless of selecting either yes or no, it will pop up again about 6 times or so. I checked voltage to the MS and it was 12.8 volts. Then, I again tried to set the TPS values and they still register as 228 and 796, but the MS immediately tells me it will only accept anywhere from 0 - 225.
7 of the 8 gauges do not register with the ignition on, with only the ignition advance gauge lit up (white instead of pink).
When I use my MS-I ver 3.0 on this car, it runs and drives short distances just fine.

Can someone actually try and help me out with this, and/or atleast point me in the direction of the link to the firmware I can download that I should be using if I should be using a different version?

 

Ok, after downloading the same firmware onto the ms about 3 times, I decided to rearrange the default figures over to my settings instead of burning my entire file onto it. The 1st time I opened and burned my ms2 file settings after downloading the firmware, only the ign. adv. gauge was working. The 2nd time something happened after I got it working and I had screwed up numbers. The 3rd and final time, I just set all my values one by one and now it seems to finally be working.....although I haven't tried starting it yet because the downpipe has yet to be welded on and it's 11:00pm. I'll try starting it tomorrow and see what happens.

 

Below is my latest MSQ file that I am using, but I'm not getting an RPM signal. Do I need to turn 1 of the potentiometers (U3 or U7) clockwise until it registers....or something? I currently have them both turned fully counterclockwise (as usual). My gauges appear to be working now, except for my afr gauge, which I believe will not register until it sees an rpm signal as well an O2 correction being enabled, as I already calibrated my PLX in the tools menu. I really need help from one of you guys out there that is running ms2 with the 1.0.2 release firmware because I'm getting nowhere fast and I'm trying to do this on my own and it's frustrating. I'd really appreciate it.

BTW, in the MS1, the LED outputs had to be configured for spark output.......is that no longer necessary for ms2?...because it is not found anywhere.

 

Sorry, I meant R56 and R52, not U3 and U7. The adjustable trim pots. I glanced at my old diagram way too quickly.

 

No one?? (aside from ToplessFC3Sman that is....thanks for the reply )
I'm really stuck right now guys and I couldn't tell you just how many hours I have spent searching and reading just trying to get this right.
Please?

 

I havent really done much with MS2 yet (planning on upgrading soon, a few things to do first though), so I dont know about the TPS issues. Could it be that somehow the wire that would normally be 5v to the TPS is seeing 12v, skewing all the measurements upwards?

AFR, at least for MS1, is independant of RPM or other sensors; it should read whatever AFR is being fed to it regardless of what the other things are doing. I dont see a reason for this to be different for MS2, since the AFR measurement really has nothing to do with RPM (although AFR corrections might now)

 

Idk, something got screwy somewhere, as I'm no longer running into that problem. The tps is fine, as well as the MAT and CLT readings. I also haven't gotten the warning about low battery voltage while flashing the MS. As for the AFR, I said that because that is what muythaibxr stated in another thread in here somewhere, but when I tried looking for O2 correction just now, it is nowhere to be found, unless when I select single wideband, it activates. In either case, it does not work. I also calibrated it with the wideband on and warmed up, but the engine off.
So, in search of a reply...........
Back to the basics:
I downloaded and flashed ms2extra 1.0.2 firmware by using the MegaSquirt-II Downloader 2.00 this time, after that I clicked on "copyini.bat", I activated "megasquirt-ii.ini.ms2extra" in the configuration screen, set code variant for my file to "MS_II" and set my lambda sensor to "innovate_0_5_linear" (even though it makes no difference for MS-II), clicked save in the config. menu, exited it out, and then put in all my figures, maps, etc. This is the best that I can do and I still have no rpm signal as well as a working afr gauge, unless it needs to see rpms for it to start working for some strange reason....

Is there anything I am doing wrong or missing??

 

Well guys, it turns out that it's in the hardware somewhere. I swapped the ms1 chip out of my ms and into his ms (jumpering to js8) and the problem persists. Everything shows up, but I'm not getting any rpm signal. So, I'm going to have a look at the assembly section of the manual as well as compare both ecu's and see what is not necessary, or what is causing the problem.

The differences I see so far are:
My MS is missing (when I built it): D1, D2, R43, R13, R12, C11, Q16 and U3.
I noticed on his MS (from DIYautotune) that D1 and D2 are both bridged and without the use of a diode.

 

Well, I just went ahead and removed those and I resoldered every joint on the board and I still don't have an rpm signal. I'm running the exact same ms1 settings in his ecu (with my ms1 chip in it) and the only thing that will not work is the rpm signal. If the lm1815 chip in the proto area was bad (for some strange reason), would this cause it? I mean, I used a grounding wrist band while I built it and I bought it brand new from digikey. It's also a brand new MS 3.0

note: I built the 2nd trigger in my ecu at the same time I built his, and mine works. Both lm1815 chips were new.
Any suggestions Ken? (or anyone for that matter?)

 

I just noticed that R48 in the Diyautotune MS is a 10k resistor and R48 in my MS is a 100k resistor. I'm going to swap them really quick and see if that fixes it.

 

There are a huge number of things that can cause no rpm signal.

bad lm1815, poorly adjusted v3 vr conditioner, noise, bad settings, bad grounds, etc...

The AFR not updating is b/c ms2 does not update AFR unless the engine is running.

Ken

 

Thanks Ken, I appreciate your response
I got great news and frustrating news:
The great news is that after changing the resistor to a 100k, it started up pretty well and as long as I kept tapping the throttle, I could keep it running. The bad news is that the reason why I had to, is because I'm getting MASSIVE table corruption constantly. I've tried rebooting megatune and the MS several times as well as trying to reload my saved file as well as re-burning my saved maps, but even then, my other tables are getting affected. Like my afterstart enrichments and actually just about everything else on a random basis. I had the car running for a total of 5 minutes just now, and I had to reboot them and download my files about 8 times. So, I figured I would post this up in hopes of finding the cause of all of my settings and tables getting corrupted. I'm also no longer seeing any warnings when I load my saved file, and even after I import my saved (and readable) maps by going table by table and saving it, I'm still getting the same problem.

If this helps, I'm using megatune P3 (should I use P1?) and I'm using the the DIYautotune usb adaptor and cable (I wish this replacement laptop had a 9-pin)

 

I've been searching and reading on the msextra site and it seems that a power filter (voltage regulator) might help, or maybe the whole usb thing is creating a problem, just as Ken stated in a thread over there. Basically about corruption occuring with the ms2 since it's now communicating at 115200 bytes instead of 9600 bytes in the ms1, along with the use of a usb adaptor.
Just trying to figure out what to do or what to fix...

 

Do you have a stim?

If you do, try changing settings on there. If it still corrupts, you probably need a different USB->Serial adapter (try the one at DIYautotune).

Ken

 

I've been using the DIYautotune USB to serial adapter for the last year and a half and its worked fine on both XP and vista

 

No, I don't have a stim, but I do have the usb adaptor from DIYautotune and it works great for ms1, but ms2 seems to be a different story. I'll check again today.

 

I ordered an ms1 processor a few days ago and I'm swapping them out. Just when I thought I got it to stop corrupting the files, it happened again. I'll unfortunately wait until there's a writeup or something on using the ms2 as well as coming across someone who has been using it for a while without any problems so that I can find out what I am missing or doing wrong.

 

There are several people who have been using it for a while without having issues, including myself.

If you're getting corruption with the ms2, you can try setting the baud-rate lower, or setting any number of settings in the ini file to help.

Ken