MMCd New Features

[cbatters]

Originally Posted by Mellon

I'm curious.. when I log with my LM-1 I have to do a bit of smoothing to knock off the peaks and valleys in order to get something useful. for instance, here's what I do with these paremeters.

rpm = 1.06 seconds of smoothing..the rpm signal is pretty noisy
boost = .41 seconds
a/f = .41
tps = 0 ( I don't require it to be a smooth line)

1) does MMCD do something to the incoming signal so it always looks clean
2) how will it handle the external inputs such as a/f? without smoothing in the logging software for the LM-1 you just about can't tune the car because it's so sensitive to changes the line is rough at first /\/\/\/\/\/\/\/\/\/\/\/\/

No digital filtering / averaging of signals in MMCd SW. Not hard to do but not needed if you have good signal conditioning on the analog input signals (lioke the ECU and HSLogger)

Sounds like LM-1 may not have any analog filtering. Although you can smooth signals in SW, I am an old school analog engineer and there is no point in digitizing high frequency noise if you are only sampling at 10-100 HZ.

If you get a chance, please post an unsmoothed CVS log of rpm, boost, a/f and TPS so I can see the magnitude/frequency of the noise you are talking about.



Clint

[Mellon]

I don't have a .csv capability with the LM-1's software called Logworks but here' s a pic of smoothed vs unsmoothed





this is using the LM-1 in conjunction with their RPM converter which allows external inputs 0-5v .. I manually setup the scaling and put a label on them for logworks.

they also make a product call the auxbox which takes the place of the RPM converter and has some presets for RPM, Boost, EGT etc.. for newbs that don't know how to setup the conversion. I found that it wasn't very accurate without some tweaking, but what it does do well is RPM now. Apparently it's doing something internally to clean up that noisy signal. I installed the LM-1 and auxbox on vr4twinturbo92's car and his RPM signal is silky smooth... actually now that I think about it our cars are identical but he does have the HKS Twin Power DLI .. I wonder if it's making the difference for him. I probably should get David to bypass the DLI and do a log for comparison.

[Mellon]

Originally Posted by cbatters

4 thoughts:

1. Did you try just selecting INJD? (MUCH more intuitive)

2. Did the 4X numeric select work ok for you - no blanking?

3. Do you think it will cause confusion to swap INJD with INJP locations.

Now that INJD automatically enables INJP I think it makes more sense to have INJD on the main screen. (And in a future release we will just ahve INJ with a user scaling option.)

4. Most recent version also fixes the polarity of the AIRT alarms and min/max . This is another example of a signal that should have been inverted as a RAW signal instead of creating so many display/alarm exception cases.

5. Most recent version also substitutes the right slugs for the user configured EGRT input. If you pick WBO2, the display will show "WBO2" instead of always displaying "MAP".



Clint

1) yep that was nice.. I noticed IPW started scanning and IDC scanning/displaying

2) the 4x acted fine thus far

3) no and personally I would love to have IDC up there with the other more commonly uses sensors so I don't have to flip pages to get to it but that's a minor thing

4) AIRT? not familiar with that acronym

5) wait a minute you said "4 thoughts" sorry can't answer this one j/k that's cool that it will display correctly.

any timeline on 6x or 8x display

rpm
knock
timing
idc
wb02
boost

all on one screen/log would be fantastic and with 8x I'd add:

tps and maybe egt.

just thinking out loud here, was there ever any talk about changing the display for a sensor on the big numbers view to alert you as to which one of the 8 was setting off an audible alarm?

That would be cool to get a warning sound and a quick flashing of the sensor name (not numbers so you can read it) so you can quickly determine which one has crossed your preset threshold at a glance

[cbatters]

SIGNAL NOISE / FILTERING Hard to tell from the graph alone what is going on. Looks like the LKM-01 is logging at 4-5 samples per second. MAP sensor signal looks prety clean but RPM is all over the palce. Hard to tell if WBO2 is noise or variations in AF.

One of the reasons for developing HSLogger was to be able to sample all inputs at 5-10X faster rates than current ECU / loggers.

LOGS
My understanding is that the log format can be import directly into Excel. If you get a cahnce, please email me you one the logs.

ALARMS
Feels like you have been looking over my shoulder recently. Only two days ago I was playing around with code that chaged the color of the 4X displays when the sensor was in alarm. Makes it easy to see that a sensor is out of normal limits. HSLogger also has provisions to connect alarms to the brake or CEL light on the dash.


Clint

[Mellon]

yep logworks can export to .dif and excel can open those.. I totally forgot about that.

it saves "as is" meaning if I have smoothing on those numbers will be saved.

see attached

[cbatters]

Originally Posted by Mellon

yep logworks can export to .dif and excel can open those.. I totally forgot about that.

it saves "as is" meaning if I have smoothing on those numbers will be saved.

see attached

Can you post an un-smoothed file?

thx

Clint

[Mellon]

Originally Posted by cbatters

Can you post an un-smoothed file?

thx

Clint

see attached.. it should be the same data as before, but without smoothing

[aodk01]

I tried my MMCd v1.7i and I found something minor.

RPM, COOL, AIRT, INJD no decimal digits.

RPM never see 1000, only shown 999 in v1.7i,
COOL 91.6c only shown 91c in v1.7i,
AIRT 26.7c, only shown 26 in v1.7i, why not 27
INJD 1.5% only shown 1% in v1.7i
in big digi mode COOL - reversal of min. & max position (ie:min value is upper, max value is lower position)

the above decimal values review v1.7i log file in MMCd v1.6n, but this is not a problem

THAT's great!! big digits mode!!! I like it. MMCd have 4 big digits now.

Great job, well done. Thx Clint

[cbatters]

Originally Posted by aodk01

I tried my MMCd v1.7i and I found something minor.

RPM, COOL, AIRT, INJD no decimal digits.

RPM never see 1000, only shown 999 in v1.7i,
COOL 91.6c only shown 91c in v1.7i,
AIRT 26.7c, only shown 26 in v1.7i, why not 27
INJD 1.5% only shown 1% in v1.7i
in big digi mode COOL - reversal of min. & max position (ie:min value is upper, max value is lower position)

the above decimal values review v1.7i log file in MMCd v1.6n, but this is not a problem

THAT's great!! big digits mode!!! I like it. MMCd have 4 big digits now.

Great job, well done. Thx Clint

1. Reduction in display resolution:

Had to do some trimming to support BOLD display in limited display area of Palm without overflowing fields.

AIR can tolerate xx.x C format so I will try adding it back in the next build (however COOL would overflow if temp > 100 degrees C)

INJD uses common % routine so for now we have to leave this alone
(memory space is critically low. Lots of cool things to be done afetr we resolve mem space issues)

RPM
GREAT testing!!!! Small error in code added to support overclocked ECU


Clint

[rdmelton]

is 1.7 officially released yet? All of these updates sound great! I am interested in getting an overclocked ECU, but before I do, I want to make sure I can log it with MMCd.