MMCd New Features

[cbatters]

Joe,

As you are working on your SW, keep in mind a structure like MMCD where users can define new sensors. My plan for MMCd / expansion interface is to map the new sensors into unused registers (E0-E7) and add user configurable sensor scaling. (This shoulsd also make site very easy for Chris from Mirage to take advantage of the new interface.)

You should also provide an option to configure higher baud rates. (Planning to run the interface at 19200)


Clint

[cbatters]

Update:

Have implemented peak / hold and it is pretty slick.

o Checkbox to enable display of peak/current values in panel display
o Graph / large display always shows current data values
o Button to reset peak values

Unit is always capturing peak values so you can click on peak anytime you want. (MUCH more interesting than trying to watch values or wade through graphs/logs to find MAX value.)

Will finish auto-log and then post a new release which will include:

o Peak/hold
o New O2 graph scaling
o Autolog mode
o 0-5V scaling option for EGRT input
o ISC displayed in counts

Planning to simplify the the sensor configuration/logging to maintain compatibility with the earlier versions. Have also come up with a clever way to simplify export scaling for 2.5 / 3.0 BAR boost sensors.

Input expander project is proceeding in parallel. Getting excited about having a bunch of new inputs available. (I have always wanted a live display/log of HP, Acceleration and MPG along with more sensor inputs.)


Clint

[WARdriver]

Awesome stuff..subscribing!

I've been searching and reading all your threads about this, and about being able to log boost...for the average joe, in layman's terms, what/when/howhow much/ can we expect to be able to do this? Already? I'm a hardware guy, not software, so I'm getting lost in the jargon And would this be something for average users, or serious tuners only?

Thanks for the hard work,

chris

[Steve3kgt]

Originally Posted by cbatters

My plan for MMCd / expansion interface is to map the new sensors into unused registers (E0-E7) and add user configurable sensor scaling.
Clint

So your saying there will be provisions for 8 user defined scalable and logable inputs! That is so sweet...

I'd be willing to do some software development, heres my contact info, send me the info on setting up the development enviornment you had mentioned in a previous thread that was to long to post.

Email: sschaefe@fit.edu
sschaefer@acedsl.com

--Steve

[cbatters]

Originally Posted by WARdriver

Awesome stuff..subscribing!

I've been searching and reading all your threads about this, and about being able to log boost...for the average joe, in layman's terms, what/when/howhow much/ can we expect to be able to do this? Already? I'm a hardware guy, not software, so I'm getting lost in the jargon And would this be something for average users, or serious tuners only?

Thanks for the hard work,

chris

Boost logging is already implemented. All you have to do is hook up a 2.5 or 3.0 BAR sensor to the unused EGRT input as per the instructions at this link and use the latest version of MMCd

1G Electronic Boost Data Logging

Hard to believe this was not implemented a LONG time ago. Easier/cheaper/better than hooking up a boost gage. Very cool to have boost alarm/logging along with all of the other ECU inputs.

Next phase is to add some additonal sensor inputs.


Clint

[cbatters]

Originally Posted by Steve3kgt

So your saying there will be provisions for 8 user defined scalable and logable inputs! That is so sweet...

I'd be willing to do some software development, heres my contact info, send me the info on setting up the development enviornment you had mentioned in a previous thread that was to long to post.

Email: sschaefe@fit.edu
sschaefer@acedsl.com

--Steve

A/D Inputs
Correct... also looking at providing signal conditioning for Thermocouple / Thermistor / Pressure transducers to make it less expensive to add additonal sensors.

Speed Input
Speed signal is available at the ALDL connector which will be connected through the cable to a frequency input on the interface. Vehicle speed will allow us to do all sorts of derived calculations.

Communication
The interface will use standard RS232 interface to the Palm using "standard" baud rates (9600 / 19200 / 38400 etc.) This should allow MMCd to work with newer palms that only have USB interfaces by using a USB-> RS232 adapter cable.

SW Development
Happy to send you the necessary files tomorrow along with instructions for setting up the dev environment. Happy to get some mor HP involved in the project.

Advise interest/expertise and I'm sure we can get you started implementing some new features.


Clint

[cbatters]

New interface:

[cbatters]

Testing a beta release of the new peak/hold / autolog features and would welcome any input...

AUTOLOG FUNCTION
o Enable / diable from preferences dialog
o Autlog triggered by TPS > 50% or any alarm condition
o Postlog currently set at 10 seconds (future release will allow user config)
o Log checkbox on front panel overrides autolog function

PEAK/HOLD
o Peak mode enabled via new control on monitoring screen
o Peak mode is enabled / disabled on the fly
o Peak values are reset from new button on monitoring screen
o Peak mode does not affect graphs
o Large display is always live data
o Considering adding min/max values along with current in large display format

EGRT SCALING
o Implemented 0-5V scaling
o Implemented wideband O2 scaling (0-5V = 10-20 A:F ratio)


Clint

[Oxygen955]

really want this...

[cbatters]

Originally Posted by Oxygen955

really want this...

Implemented min/max values in large display format - also implemented the complete data structure to display Min/Max on all of the sensors in the panel. All I have to do now is find a good place for a button and wrestle with the age old problem of using a button with a legend.

i.e. Does [MIN] mean the min values are already being displayed or do you push the button to se the min values and then the button displays [MAX]??

Version looks solid in the simulator but want to take it for a spin on the way to work in the AM before publishing it.


Clint

PS: Peak / hold and autolog work like a champ. No more missed events! (I noticed I am getting higher knock count than I realized during heavy but not WOT acceleration.) Peak display rules!!