MS2/Extra pre-3.3.2 beta 8 released

[jsmcortina]

To announce the release of pre-3.3.2 beta 8.

Main changes since pre-3.3.2 beta 7
Bug fixes:
ini tweak for inj bank 2 param ungreying
FC rotary only needs 3 spark outputs. Was claiming PA0 also due to typo.

Minor/internal:
Implement CAN TX timeout and reset.

The zip can be downloaded from:
http://www.msextra.com/doc/ms2extra/fil ... 2beta8.zip

Please be sure to read the README.txt and RELEASE-NOTES.txt supplied within the firmware zip file.

The current TunerStudio is REQUIRED. (2.5.20 or later.)

James

[slyrye]

I noticed a bit of hiccup around 1800 to 2500 rpm and whenever I change something and hit burn button the "Programmable IO's" toggle and stays to low output, unless restarting the engine.

[jsmcortina]

That's not enough information to understand your problem.

Please enable Project Properties -> Settings -> PORT_STATUS
and then take and upload a datalog that demonstrates the issue.
Mark the datalog (SPACE BAR) when the problem occurs.
Mention exactly what setting or output you are referring to.

Otherwise I will not be able to investigate.

James

[rx7locost]

James, After having output conflicts with the released code 3.3.1, I have loaded pre-3.3.2 beta8.
I am running an RX7 rotary setup with FC mode ignition.

I have identified a problem. I'm not sure if it is software realated or my 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. The dash tach is driven from the Trailing igniter/coils. If I raise the idle it starts working again. I have verified this ignition stopping with a timing light. All the while, the leading igniter/coils work normally.

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

Is here some sort of "new" setup in Tunerstudio that I have not found that can create this effect I know this wasn't a problem in 3.1.X firmware. I don't recall seeing a setup for trailing dwell before. Maybe I just didn't pay attention. With pre-3.3.2 beta8, I now have trailing spark dwell set for 3.0mS. if that is any help.

I appreciate any help. If you need an MSQ file, let me know.

Chuck

[rx7locost]

Here are the MSQ and MSL files.

I don't know where to look on the MSL file to see leading ignition, trailing trigger and trailing select.

2014-05-30_20.02.01.msl

missing trailing under 10000.msq

[jsmcortina]

At 500rpm on the bench using the current 3.3.2 firmware I'm seeing all outputs working.

I checked with the Diagnostics -> Engine Logger in TunerStudio and can see PTM3, 4, 5 behaving as expected.

James

[rx7locost]

Thanks for the quick reply. I appreciate your looking into this.

While I could not find PTM3, 4 and 5 as any selection under engine logger, using Tuner studio 2.6.01, I did verify that all three LED's are still flashing under 1000 RPM. So I have to assume that the MS is sending a signal. I guess I'll search elsewere for my problem.

[rx7locost]

Sorry this got broken out into a new thread . I deleted the new thread and moved that post back here and updated it:


James, 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?

I loaded the released version of MSExtra 3.2.2. and that acts the same. The trigger signa;l from the MS2 till drops out below ~ 1000 to1050 RPM . I posted a video on youtube of the trigger signal on a scope. You can see that the signal just disappears.
https://www.youtube.com/watch?v=4LZXYCtQUKk

Thanks for any help.

[jsmcortina]

I have no idea what's going on there, your video clearly shows a lack of IGt, but my scope shows there is one - using your MSQ.

Could anything be interfering with that signal at the lower RPMs ?

James

[jsmcortina]

Scope shot @ 510rpm.
The top trace is just used as a trigger input to the scope.

2014-06-01 21.01.36.jpg

James

[rx7locost]

geeeze! I guess I'll start troubleshooting from the outputs, back into the MS and see if I loose the signal along that path. Am I safe to assume that if the main ign output is firing the waste spark( leading) coil, and the select signal is functioning, that the input side of the circuit. i.e. the crank angle sensor and the VR potentiometers are adjusted and working right? I'm not getting any lost sync indication. That would indicate the tooth wheel signal is good, right?

from top to bottom, can you ID the signals in your photo?

I can't guarantee that everything was properly before the upgrade. I have no reason to believe that it wasn't, just not sure.

[jsmcortina]

My photo has
(cam pulse - only used to trigger scope)
12-1 crank signal
Leading
Trailing
Select

James

[rx7locost]

James, I traced the signal from the output of the MS back to the associated pin on the MS2 daughter card. Everything looked good and clean as it
should when it is running at higher RPMs. Below the magic 1000 RPM, there is just a flat line, no indication of a signal trying to make its way out.

I then probed the input from the CAS at the INT1 pin of the MS2 daughter card and that looked good and clean too.

Then I thought for a bit and rember recently changing the spark advance table at idle to get a smoother idle. If I run at 0 degress, (original RX is -5 deg advanced, actually After TDC) I get a dropped trailing trigger as we have seen. However if I raise the advance to 2 deg advance, the trigger is a bit more stable. At ~ 3degrees the trigger signal is rock solid. So I have set it for 4 degrees advanced for a bit of safe margin and left it at that. I'd like to run at 0 deg, but if this is what it takes, I am OK.

Maybe the processor is too busy at that period of time doing other housekeeping chores. I don't know and really don't care to get into the details. I am happy that I am back running on all 4 plugs.

Thanks for you prompt and willing attention to this issue.

[jsmcortina]

I've done more testing just now and there IS a problem. I wasn't able to find the fault immediately, but under certain conditions the trailing is indeed misbehaving. It does appear to be related to the 0 deg leading timing and 15 deg split you have commanded.
The MS2/Extra code isn't designed to run later than 15ATDC, but obviously the spark needs to work and handle any out of range situation gracefully.

It looks as though there is an internal miscalculation in certain circumstances that is giving a negative delay. That impossible delay then does weird things.

More investigation required.

James

[jsmcortina]

I think I've found the problem and solved it, but will test more over the coming days.

James

[rx7locost]

WOW James, unbelievable!!! You found it. It is good to know that my system is not acting in some strange manner different than everybody else's. It gives me confidence in my system.

So, I should be good to go as I am set for now with the leading set at 4 deg BTDC? I'd like to get the idle timing down a bit further, but I have a 1500 mile trip with the car coming up in 2 days and can't take any more time to upgrade the firmware before then.

Would another possibile work around be to reduce the split timing to get the combined less than ~12 ATDC?

Maybe I should just stop asking more questions and wait for your test results.

Thanks again.

Chuck

[jsmcortina]

I sent a test code by email that should fix this issue.

James