MicroSquirt.com read only forum (Jan.15,2018)

Thanks, Al. I'll be working on the install this week and should have a report for you soon. Ref your initial post - am I in the ballpark assuming to not exceed 6000 trigger events/sec or so?

-Mike

Mike,

In the last version of 2.53 code I looked at, the limits were:

- with a 36-1 wheel (and ''last interval' predictor) I saw a stable rpm signal up to 10770 rpm (signal is ± ~10 rpm), above that the rpm started to bounce after few dozen seconds (all tests at 8 cylinders, etc., etc.). However, the ignition outpout begins to falter at about 8900 rpm (occassionally retarding slightly, never advancing).

- with 60-2 wheel and 'first derivative' predictor, it looks like 6250 rpm is the top sustainable speed for a stable rpm and ignition signal.

These were the top rpms that could be held indefinitely (more than a minute or two) with no issues. The code is capable of higher rpms for a dozen or so seconds before it becomes 'overwhelmed' with interrupts.

And this is all bench testing - no 'real world' situations, so be careful!

<edit: these limits have been raised considerabley in the 2.6 code>

Lance.

Thanks, Lance - being careful entails asking questions, that's why I'm inquiring! I should be just fine with a 12-1 running the rotary (equal sparkwise, to a 4 cyl 4 stroke) at <8500. As always I'll bench it first with the same trigger device that the engine uses then log the crap out of things with very conservative settings.

-Mike

Mike,

Yeah, I was sure you would be careful, and you know what you are doing, but I try to keep in mind those few individuals that might try it without your wealth of experience and knowledge. A few words of warning spread throughout the thread can't hurt!

In fact, I ought to apologize to the whole list for this - my replies are often long winded, but for the most part this is for the above reason. It does make for tedious reading, though!

Lance.

I have a question about those rpm limits...

I've been able to successfully run msns-extra on the bench up to 12000-13000 rpms with everything set up for a rotary engine...

What is the execution time of the MS2 code as it is whenever a trigger tooth is hit?

Al,

Could you provide the CodeWarrior project for v2.53 because even using CodeWarrior I can't get it to link. There are a few functions missing such as NoOp, SpSub, reboot, monitor. I got the 32k license for CodeWarrior so I should be able to generate the s19 file, I assume. I'm either doing something wrong in my project or there are some files missing. With gcc, these functions are included in .s files but these files are not compatible with CW.

If you can't provide the project could you (or someone else) write up a small dummy's guide for generating the s19 file as is already done for the gcc compiler.

Thanks,
Jean

grippo wrote:The code and s19 files are attached. Note that thia wheel decode is only for m-n wheels, no m+n ; also, it only handles one wheel - its not sequential. That will come with the router board.

Phil Johnson does the gcc code. I generally send him a copy after the code is tested - we still haven't completed testing 2.34 code.

I have been running 2.34 for 2 weeks and a few hundred miles plus 8 or 10 hours seting up in the garage and it has so far presented no bugs of any description. Of course I can only speak for the EDIS configuration on the ignition side of things. I am using MT225b756 Beta, I have had a few comms issues but I am quite sure that is my configuration as I have only USB to serial or the Serial-bluetooth connections to choose from and neither is very reliable.

Jon

thanks for putting in the new VR sensor code it is exactly what i wanted
I will be trying out this new firmware in-car soon (3s-ge, 4 wires from dizzy-type)

keep up the good work everyone!

Barf:
You will need to grind two teeth off the NE wheel to use this code.
It doesn't support the G1 and G2 2nd trigger inputs sorry.

a software solution would be nicer, but ohwell
does it matter which two teeth i grind off?