Alpha test: 36-1+1

[jsmcortina]

Post info and test results here

[rb26dett]

Just to confirm, this is what used to be known as dual trigger
correct? ie a 36-1 on the crank, and a 1 on the cam?

Thanks,

Fred.

[jsmcortina]

No, this is a crank wheel using a hall sensor and a funky 36-1+1 pattern. It is used (apparently) in next-gen Neons.

I have pictures of most of the wheel patterns and will add them to the manual when I get chance.

James

[rb26dett]

Then do I use the standard missing tooth wheel and just an extra check
box or two for the second trigger? excuse my ignorance, i had what i
thought was a good look around. i'll be playing with it again tonight,
hopefully looking for rpms to be shown.

Fred.

[jsmcortina]

Then do I use the standard missing tooth wheel and just an extra check
box or two for the second trigger? excuse my ignorance, i had what i
thought was a good look around. i'll be playing with it again tonight,
hopefully looking for rpms to be shown.

Fred.

Yes 36-1 crank wheel with second trigger cam wheel is a "standard toothed wheel"

James

[rb26dett]

Thanks James, Its just that I'm sure it was down as "dual wheel" in the beta.

Fred.

[boost junkie]

FYI, this wheel is used on all 03 to current chrysler engines (4, 6 and 8 cyl). Only the cam signals are different between them.

[jsmcortina]

OK, presently I've hardcoded this to 4 cylinders.
If someone can supply the timing information for 6 and 8 these should be fairly easy to add as well.
Having the cam signal data will also allow 4 cyl coil on plug now and pave the way for sequential fuel in MS3.

James

[jsmcortina]

Anyone tried this yet?

James

[esteinmaier]

I'm trying it now. Using the RC1B code, I can't get it to get a tach signal set on 36-2+2. EDIS is the only setting that gives me any RPM, and it's obviously way off. I did successfully run MS1 on the car before, so I'm pretty sure it's not a wiring problem. Be easy on me, as I'm pretty noobish.

[esteinmaier]

I switched to a firmware from November, and it read RPM just fine. Leads me to believe that the newest firmwares (Jan forward, at least) are broken for the NGC decoder.

[jsmcortina]

Please post your two MSQs and the two firmware dates and I'll take a look on the bench.

James

[esteinmaier]

I overwrote the MSQs, so I don't have them anymore, but the 2 firmwares that I tried unsuccessfully were the new RC1b and the beta from 2/10/08. I configured the ignition as indicated in the manual for it for all of the above.

[swnp]

I never saw this before... lmao...

James and boost, it works perfectly.

I posted my MSQ on (several) different post I've made here recently. I've been using this code since last summer/fall with the beta12 release(I think it was beta 12). I got it working well and have been using it w/o any problems since beta15.

I'm currently using it with RC1b and I don't believe that the problems I'm having with my fuel map are due to this wheel code.

Great work! All this time I didn't know it was still being "tested". lol I thought it was all said and done, because it works like it is.

(This is 2K4NightRiderSRT from the other boards, btw)

[jsmcortina]

Thanks for the feedback.

James

[swnp]

Hey, no problem, James.

All this time I didn't know I was "blazing the trail". lol I knew it needed testers from the other forums I visit, but I figured by the time I was using it, there would have been others. Honestly, I got my SRT4 started with this code before I got it started and running on my MSI-extra unit. I didn't just jump in and started using it because MS was totally new to me, and I wasn't confident enough (at the time) to learn EVERYTHING on my own. So I learned what I could from MSI, and now use the MSII exclusively on my SRT4.

And for the record, I've only spun the engine to 6000RPM. I plan on taking it to 7500 later, but so far I don't think it'll be a problem doing that as far as wheel code is concerned.

Cheers!

[swnp]

James, et al.

Is there anything with this code (I doubt it's the code, but I figured I'd ask here) that will cause the RPMs to drop out with low Z injectors? High Z injectors worked fine, but when the MS was switched over to low Z, the wheel decoding seems to break up from time to time.

Is it more likely that it's a hardware issue in the MS2 itself? I thought MS2 had native low z injector support?

Vic

[muythaibxr]

it's most likely that you need more grounds, or need to redo your power circuit. You may also want to check the megamanual for suggestions on what to do in this case.

Ken

[Matt Cramer]

OK, presently I've hardcoded this to 4 cylinders.
If someone can supply the timing information for 6 and 8 these should be fairly easy to add as well.
Having the cam signal data will also allow 4 cyl coil on plug now and pave the way for sequential fuel in MS3.

James

FYI, I've confirmed that 8 cylinder engines use this same wheel. I have a cam wheel from one of the and intend to check it on a degree wheel soon - it's as weird as a Subaru setup.

[esteinmaier]

I'm having the cutout problem too, and I'm going to first try a few more grounds. I already have it grounded well, but I'll do more. If that doesn't work, my next plan of action is to move the injectors off the board and onto a peak and hold board. From what I understand, this is a good idea anyway, so the peak and hold board is probably what I'll do.