Hey everyone,

I am trying to setup a startup tune for FC using MS2v3 and the Zeal card. I saw the firmware page had recently been updated so I made the switch to 3.3.1 since I didn't have much time invested in my 3.2.5 tune. Here's my problem:

When I enable rotary mode under ignition settings, It says that one of my programmable outputs is conflicting with an ignition output. I have PA0, PT6, and PT7 as outputs. PA0 in particular is the conflict, which I am using for my radiator fan. When I disable it, the error goes away. If I switch back to 3.2.5 and replicate the settings it goes away. I spoke with DIY and they think it might be a bug in the firmware for Rotary Mode, as only RX8/COP mode should require 4 ign outputs and create this conflict.

Is anyone else running 3.3.1 and NOT using COP with success?

Link to my MSQ

Thanks,

Alex

 

It was a bug. I believe James has fixed it but the fix has not been released yet.

 

I just upgraded from 3.1 something to 3.3.1 and ran into the same problem. I'm using the FC coils and had no issues earlier. Would sure like to have this fixed in the next week or so. I'm taking a trip with my car soon.

I think it has something to do with PA0 too. In my setup I use PA0 to control the 2-speed fuel pump. If I disable it, the message goes away. I looked for where the assignment of Spark A, Spark B and Spark C are in the latest tuner studio, just to see if something had changed. I couldn't find it. That is what I get for staying away from the MS for a year or so.

 

I emailed DIY and they said it was a bug. For whatever reason ANY rotary mode required 4 spark outputs, not just RX8 mode. They said they passed along the bug to the programmer, but I don't know when it'll be fixed. I would use 3.2.5 in the mean time.

 

SHAINIAC, Thanks for the quick reply. For kicks, I just checked in the MS2/Extra development forum and saw the following post:

So it looks like pre-3.3.2 beta7 would fix our problems. I'll give it a try in the next day or so.

 

Thanks for the link!

 

I upgraded to pre-3.3.2 beta8, I can now control PA0 like I should, I think. I say "I think" because I have a problem with my output on that circuit not pulling the output all the way to ground. It might just be a blown transistor, I'll have to take the MS out to analyze the situation. That will be some other day.

I'll ignore all the other problems I had. They were mostly due to the operator and some laptop issues.

 

I have identified a problem. I'm not sure if it is software realated or hardware. After installing the pre-3.3.2 beta8, I now have a problem with the trailing coils. They do not want to fire below about 1000 RPM. Further the RX7 dash tach cuts out at the same time. If I raise the idle it restarts. I have verified this with a timing light.

My setup is MS2 with a rev 3PCB with the LED's wired as in Aaron Cake's writeup. Running FC mode.

I'll also post over in the MS Extra development site.

Is here some sort of "new" setup in Tunerstudio that I have not found? I know this wasn't a problem in 3.1.X firmware/ I don't recall seeing a setup for trailing dwell before. with pre-3.3.2 beta8, I now have trailing spark dwell set for 3.0mS.

 

Huh...No trailing below 1000 RPM was an old MS1 thing...

 

James replied this morning to my post in the MS2EXTRA development site, He verified that the software was working correctly on his bench, down at 500RPM.

James said that I could find the outputs for spark in the engine logger, He said they were PTM3, 4 and 5. I couldn't find those as any of the options in TS2.6.01. I did verify that the LED's appear to be lit and still flashing under 1000 RPM; At least I think so. LED 16, trailing trigger, is nearly full brightness. I can clearly see LED 15 flashing, the coil select signal.

No car wiring related to ignition has changed nor internal wiring on the MS. I am defninitely running a MS2 processor.

I'll try some bypass capacitors on the B+ wires at the ignitor today.

Barring that, is this possibly a known failure mode of the ignitor? I may have reflashed the firmware with the ignitors/coils powered. The fact that they work above 1000 RPM seems to indicate "no".

 

I just tried adding a capacitor at the ignitor. I tried 4.7uF up to 330 uf. No improvement. However while doing so, I noticed that even at higher rpm's, during decelleration, the trailing ignition cuts out. It must have been doing this all along, at least since I upgraded the firmware. This is verified by using a timing light clamped on the T2 ignition wire. I can see when the ignition stops.

I am 1/2 way convinced that the ignitor is bad somehow. But I have 2 and the both act the same.

 

I put a scope on the trigger and the select lines to the coil, D15 and D16 in MS terms. The select continues to oscillate back and forth but the trigger signal just disappears at 1050 RPM. From what I can tell, it just drops out. it does not get narrower to nothing. I am using a modified RX7 CAS with to opposite teeth missing, set up in TS as a 12-1 VR crank sensor. I believe that the potentiometers in the internal circuitry are set right since the leading coil (D14) contines to run the engine.

Clearly it is software related and not the ignitor?

Tomorrow, I'll try to load the released version of MSExtra 3.2.2. and see is that acts any different.

 

Sounds like a software issue if the scope verifies the signal disappears at 1050 RPM.

 

I just upgraded the firmware to the released version of MSExtra 3.2.2. The problem still exists. I have taken a video of the wave forms and posted it on youtube.


I just don't know where to begine to look. I have a trip coming up and I was wondering if I should just disconnect the trailing igniter plugs, or whether I should just let it run as it is, cutting out when it seems fit. What dou you think?

 

James has tried to reproduce this on the bench with the same firmware rev and msq, and he's not seeing the issue.

 

He and I were communicating over in the MSExtra Development site. Today, I finally found either a fix, or a workaround, I'm not sure which it is. The signals to and from the MS2 daughtercard look clean on a scope. It appears that I was doing several things at once. I know I shouldn't do that, but sometime I get ahead of myself. My dropped signal problem appears when trying to idle at ~0 deg advanced to get a smoother idle. I am convinced that the MS2 is doing what it thinks is right. However, if I raise the advance to 3 deg advanced, the issue is resolved. For a bit of margin, I have now set the advance table to 4 deg advanced. I am OK with that for now.

Thanks for looking in muythaibxr.

 

That shouldn't cause that problem. Anything from about -10 to 60 or so should work.

That is a good piece of information towards reproducing it though.

Ken

 

James has now been able to replicate my problem, found a software glitch and is working on a fix.

What a group of great guys! Thanks Aaron, Ken and James for all the effort you all put into this.

 

The actual change to fix the problem was 1 part of 1 line. Some variables were declared as unsigned when they should have been signed.

Ken