[sti robot]

Originally Posted by 4banger

How do you cycle through the various functions?

Currently its a two button interface. One button cycles through the modes and the other does things like start/stop the timer and reset the peaks on the meters. Right now they are a little off and the timing, etc. need some work.

Originally Posted by fullerton

what about engine temp and g rating on one screen?

Sure, why not It'd take 15 minutes max to set up.

[4banger]

Fullerton and STi robot, what would you guys think of this:
When you first turn the car on, it would display engine oil temp.
After the temp warms up to say 200 (someone more knowledgable about proper oil operating temps could suggest a better number), it automatically switches over to a boost/g-meter screen.

This way you know when your car is warmed up and ready to be driven hard. Then if your oil exceeds a certain temp, the oil temp comes back on so that you can see that you need to take it easy.

[Mack]

not a bad idea. maybe if the temp reaches X°, it would take over the top half of the screen and flash continuously, leaving the bottom half doing the g force or timing...

[4banger]

That's a good idea too. I guess the "problem" is that when you get to design your own system, there are just too many good ideas and you have to draw the line somewhere.

[Mack]

You're right, we could think of new ideas forever.

I do like the warning idea though, and think it's worthy of implementation.

[sti robot]

Originally Posted by fullerton

You're right, we could think of new ideas forever.

I do like the warning idea though, and think it's worthy of implementation.

-Deciding what comes up first, second or third is really easy stuff. Having this switch to another "mode" automatically based on set value is easy (4 lines of code). If (big IF there as I still want to keep this thread legit and not get ) I were to make these for people they would most likely be small run/custom jobs. I would be told things like: what boot up screen, what order modes would show up in, which sensors to implement, what type of display for what sensors, what type of enclosure installation, warning values, etc.
-Warning: This can be implemented. I'm not sure what it'd look like. Maybe flashing between "warning" and value or maybe just changing the refresh rate of a value so it shows blank-value-blank to make the value of interest blink rapidly. Not sure, I'll look into it though.

These ideas are good. Keep them coming. I probably won't implement every idea that gets sent to me but I'll at least try the good ones out.

[sti robot]

On another subject I'm looking into relocating/doing the job hunt thing. So when I disappear for a bit its because i'm on the job hunt. When I find one I'll tell you all about it so you won't think i've abandoned this project. It's just that I've got some other priorities right now.

[Mack]

Originally Posted by sti robot

-Warning: Maybe flashing between "warning" and value or maybe just changing the refresh rate of a value so it shows blank-value-blank to make the value of interest blink rapidly. Not sure, I'll look into it though.

I like the blank-value-blank, since the word warning would just confuse us IMHO.

I am not sure if this is possible with what you have, but an audible beep could also do the job. That can't be too expensive to implement.

I like 4's idea for startup, with this twist: Top line is oil temp. Bottom is a timer. When a set temp is hit, a little jungle can play, letting you know you can beat on her. The screen stays up with timer and temp until the user selects a new screen. Preferably, the timer would always count up, until power is interrupted. That way you can switch between screens, but always come back to your trip timer. This timer would be a separate function from the lap timer.

[sti robot]

To be completely honest I personally don't like beeping...but as someone who has actually studied and written papers on auditory alerts I know that they are very, very effective. It's all in how you use them.

"Top line is oil temp. Bottom is a timer. When a set temp is hit, a little jungle can play, letting you know you can beat on her. The screen stays up with timer and temp until the user selects a new screen." This part would be a personalization.

This idea sort of reminds me of a turbo timer...only it works backwards.

I do like the globalized timer variables (keep counting the time even if you switch modes)...I might do that too.

What I really need is someone in Atlanta that wants me to develop stuff like this as a full time job...that would be the stuff.

EDIT: how does 21cents for a 5k 70db buzzer sound...these things are cheap and you can get them in whatever configuration you want. I figure 2 tones...one warning one ready...you guys have added a lot to my list. But, as I still have yet to order the sensors I'll just add this to my order.

70db is not very noisy but depending on the tone should cut through the "whiteish" noise of your car running...even on a track day. 5kHz is a high pitched noise like your microwave oven beep or maybe even close to the key-in-ignition-with-door-open chime. FYI we can hear from 20Hz to bout 20kHz roughly. Engine noise and whatnot is probably all below 1kHz.

on second thought maybe i'll keep it at 2kHz ... this sample is at 1kHz http://freesound.iua.upf.edu/samples...e.php?id=25881

[Meridock]

Wish list -

Temp gauges (intake, intercooler, ambient(even though the care already does this,) underhood, and maybe a portable (yet wired) one than could measure brake rotor or tire temps... )

boost ref ic spray !!!

Oil temp - with a TINY off the shelf sender (of course then I need to fine another galley plug to pop.)

G-Meter (one screen - axis with peak - acceleration/braking on and one screen lateral on line.) I like peak hold values for this - of course this is almost a data acquisition module...


I would not like ECU splicing - ODBII would be cool, but you shot that down