nitrous yet?

[dieselgeek]

After a ton of happy MSnS-Extra installs, I'd like to try an MS-II on a friend's truck.

Is there Nitrous control yet, similar to MSnS-Extra, and if not, how hard would that be to add?

thanks!

-scott

[jsmcortina]

Tricky.
Working on MS2/Extra
1. We've only just started but have already run out into the 32k compiler limit in the free CodeWarrior compiler, so we need do some trickery
1A. I tried gcc but the code seems WAY slower.
2. There are so few spare output pins it is going to be a real compromise between different features.

James (glum face)

[Bruce Bowling]

After a ton of happy MSnS-Extra installs, I'd like to try an MS-II on a friend's truck.

Is there Nitrous control yet, similar to MSnS-Extra, and if not, how hard would that be to add?

thanks!

-scott

Scott,

What requirements do you use for your nitrous configuration? Asking because the general-purpose I/O may be sufficient, depending on what conditions you need. The three LED drivers and IAC all have GPIO mode.

- Bruce

[dieselgeek]

physically, we only need on/off grounding of a 12v relay's coil (same as fuel pump circuit)..

Software, we'd settle for something as simple as a generic output triggered by RPM and TPS, so we can at least trigger a wet system. Ignition timing retard would save the expense of running an external ignition box (triple the cost of MS).

But what's in MSnS-Extra, would be nice: ignition retard, extra fuel (for a dry shot) Anti-lag, checkback, etc. The turbo truck uses anti-lag to fire 100-150hp N2O until 10psi of boost, this is *incredibly* effective for launch tuning. Not that our needs are the same as everyone else... but Extra's N20 controls better most of the commercial units IMO.

I'm not sure how much effort it would take to implement the software portion into MS-II; please forgive me if I am asking for miracles...



thanks,
-scott

[jsmcortina]

I'm not sure how much effort it would take to implement the software portion into MS-II; please forgive me if I am asking for miracles...

The software side isn't particularly difficult, it is a matter of juggling the outputs.

James

[BottleFed70]

The only thing keeping me from doing nitrous controll on my MSII v3 is a lack of inputs.

I need something to connect to my "N2O armed" switch. So that the N2O flows only when I want it to.

I'm not using a knock sensor.. I wonder if there's an easy way to make the knock sensor input work for this?

[grippo]

The only thing keeping me from doing nitrous controll on my MSII v3 is a lack of inputs.

I need something to connect to my "N2O armed" switch. So that the N2O flows only when I want it to.

I'm not using a knock sensor.. I wonder if there's an easy way to make the knock sensor input work for this?

The knock sensor is an ADC. You can have a 0V / 5V rocker switch tied into it. You just have to write code that tests for > or < 2.5 V, code up what you want to do when the switch is on, and you are done. The knock sensor is presently read at least every few ms, plenty fast.

[BottleFed70]

The knock sensor is an ADC. You can have a 0V / 5V rocker switch tied into it. You just have to write code that tests for > or < 2.5 V, code up what you want to do when the switch is on, and you are done. The knock sensor is presently read at least every few ms, plenty fast.

That's almost too easy! I'm going to have to give this a try.

[EFI-Unlimited]

This would be just what the doctor ordered for my Mustang, and with the way the 2.5+ code is written, would be easy to implement. What would be good for me, would be, when an input goes high, add PW over RPM, and retard timing a fixed amount. Simple and VERY effective.

(PW over RPM, as in)

2.5ms 2500
2.9ms 3500
3.1ms 4500
3.0ms 5500
3.0ms 6500
etc.

Brian