Release Two Workspace (/Fork name TBD)

[steffen707]

Originally Posted by dcb

msc, a clock would be "nice" but I can't see replacing trip or instant mpg with it or other efficiency parameters. Of course it is open source so you don't need to talk about it, you can just do it and see if it sticks. Just post a patch in the wiki on how to do it. It looks like that is the boat I am in for cda and bsfc.

I would agree that if the clock code took up so much space that you would have to delete some other features, then you should get rid of the clock; however, I thought Falcon4 said that there is plenty of room on the new larger chip, therefor, since he already has a very stable (4 weeks and counting accurate clock code for v.86), then you might as well incorporate it into the new gauge as some people, myself included would find it useful.

Not everybody has a clock or cd player in their car that is going to use mpguino. I want one in my drag crx to tell me MPH, mpg and time. Very cheap speedometer if one doesn't want a typical speedometer in their car. My drag car will only have a 5inch tach, no other gauges except for a hondata controlled check engine light, then i will hook my netbook up to hondata to figure out what warning was triggered if the check engine light comes on.

So for me, a clock would be nice, because i don't have one in the car already.

[dcb]

hello kitty + hotglue = clock

There are plenty of whizbang drag racer computers, that cannot be the motivation here though. However cdA cRR might be an area of mutual interest. Less so for bsfc probably, unless you are on fuel restricted race of some sort (though the algorithms are based on changes in acceleration and mass and cdA cRR). If a feature helps you drag race though, it is only incidental, not the primary intent of the mpguino project. Maybe you need an ETGuino branch of your own

[FalconFour]

@dcb: clock is already done in my modded (and running) v0.86 code... it's dead-silly accurate, based only on an unsigned int counting loops since start. I actually compensated for it in the code, but even if the counter did loop after about 25 years, it'd still be accurate The skew due to the functional "rounding-up" at the end of the main loop, though, I haven't even been able to identify after a week of running... it's a pretty reliable software clock from what I've seen!

@bobski: Here, lemme illustrate... here's the LCD, and underlined are the places I want the cursor to land when I hit the left or right buttons:

MPG I:24 C:26.2>
MPH35.2 MS20.33<

That would equate to a tabStops array:
{0,0+tabLine2,8+tabLine2,tabEnd}
(which would compile to {0,128,136,255})

The purpose is to quickly describe the positions I want each display screen to have "selectable", which makes selecting and identifying UI functions *VERY* easy within the code:
leftButtonPressed() {
byte x = 0;
if (currentTab > 0) currentTab -= 1;
else {
// find end
while (currentTabStops[x] != 255) x++;
// set current tab to one element before end
currentTab = x-1;
}
rightButtonPressed() {
// increment blindly
currentTab++;
// did we hit a wall? back to 0
if (currentTabStops[currentTab] == 255) currentTab = 0;
}
...
randomDisplayFunctionHandler() {
// if the middle button is pressed to perform that action, perform the action for that selection.
if (middleButtonPressed()) performAction(currentTab);
}
displayHandler() {
displayFuncs[currentDisplay]();
setCursor();
}
setCursor() {
byte row, col;
row = currentTab >> 7; // 129 for row 1 col 1 = b10000001 shift to b1
col = currentTab & (!tabRow2) // 129 "and" 127 = 1
lcd.setCursor(row,col);
}

See why I want to make this work?
Oh, and the "master array" would reside in PROGMEM, and would be memcpy_p'd to the currentTabs array when the screen is switched (using that handler, which may also update a "currentTabsLen" var). It makes things a lot easier, if I could just find a way to unify that "master array" in a sensible way... maybe I could just cram them all together, separated by 255's, and use the memcpy_p's routine to sort them out at runtime?

[bobski]

Ah, k... I get it.

[steffen707]

Originally Posted by dcb

hello kitty + hotglue = clock

There are plenty of whizbang drag racer computers, that cannot be the motivation here though. However cdA cRR might be an area of mutual interest. Less so for bsfc probably, unless you are on fuel restricted race of some sort (though the algorithms are based on changes in acceleration and mass and cdA cRR). If a feature helps you drag race though, it is only incidental, not the primary intent of the mpguino project. Maybe you need an ETGuino branch of your own

DUDE! What is your problem?

If you read my post in its entirety you would have seen that I said the clock would be cool (FOR ANYBODY) as long as its not using up precious code space for other "ecomodder friendly" features.

And as I stated before, and as FALCON4 stated after your post, he's already created the code for the clock.

And since the mpguino project is open source, why don't you stop bashing other people's suggestions. I don't need a clock to drag race, I would like a clock on the mpguino as I will use it for a MPH gauge on my drag car. And if it can show a clock as well, then cool. If it can't have a clock because that will take too much time to code, take up too much space then that's okay. I've got a cell phone with a clock as backup.

[msc]

Originally Posted by dcb

Of course, something that might be entirely appropriate to prototype in arduino is a cda program (that hopefully runs on mpguino hardware). So that folks with a mpguino can swap in a CDA chip when they are doing aeromods..

I had considered the idea of an alternate program that just does the drag calculation. I think rather then continuing the discussion in this thread I may start a thread for this topic.

Originally Posted by dcb

I would point out that you can't swing a dead cat without hitting a clock. As well as it takes time/rom to sort out the interface for setting the clock, so what is the value proposition for adding a clock?

When I swing a dead cat in my car it strikes the dash right where I would like to install my MPGuino.

In considering installation options for an MPGuino in my CRX the place I think will be best for use is where the dash clock is mounted. I don't want to give up my dash clock so I would want the instrument to display a clock when I'm not using it for something else. If I retain interest in the project long enough to do it I can fit the MPGuino inside the OEM clock module. Power and ground are all supplied to the clock module so the only extra wires required would be for the injector and speed signals. I would also bring out a USB cable for reprogramming in place.

A clock routine that meets my needs has been developed already. I'm just voicing support for FalconFour to include it with this project. There should be a large display clock available. The clock can be included with other small displays but to be useful for me it should have a large size screen of it's own.

Mike

[dcb]

Originally Posted by steffen707

DUDE! What is your problem?

WTF? I just said clocks are available everywhere and nipping drag racing concerns in the bud as relating to this project. You don't like the ETGuino idea? There's plenty of instruments you could come up with for that arena. And yes there isn't as much space as you think.

Incorporating plain old battery voltage could be useful for those of us who spend lots of time with the engine off and could be done with a couple resistors.

I'm not sure about "generic" analog display, maybe, just haven't thought about it. but the existing analogs might be menu configurable to specific sensors.

Some sort of o2 reading could be very useful, especially if your car has a wideband.

Incorporating map+rpm/maf/throttle readings can also be informative.

coolant temp maybe too, but at some point you should use a laptop to correlate/display all the data.

Still cdA/cRR seems like the most enabling feature to me plus it is simplest to implement (no extra circuitry required). It's just hard for me to get excited about a clock (though I'm glad the main loop timing is proving accurate).

[steffen707]

Originally Posted by msc

I would also bring out a USB cable for reprogramming in place.

Unless you made a mpguino from a kit, the one from dcb does not have a usb port. You have to buy an arduino to program the chip. So then you have to unplug it from the socket on the mpguino, plug it into your arduino, upload the new code to it from your computer and usb cable, then pop the chip out of arduino and put it back into the socket on the mpguino.

Unless you've done something else, and would like to share with us. Im interested. Also the crx factory clock location would be a great spot to mod and mount the mpguino. Ive got one in my 97 ek hatch and will be putting one in the drag crx as well.

[steffen707]

Originally Posted by dcb

WTF? I just said clocks are available everywhere and nipping drag racing concerns in the bud as relating to this project. You don't like the ETGuino idea? There's plenty of instruments you could come up with for that arena. And yes there isn't as much space as you think.

Again you are failing to read peoples posts. THE CODE FOR A CLOCK IS WRITTEN, IT WORKS, ITS FUNCTIONAL ON FALCONS V.86 MODED CODE.

I didn't ask for a 0-60 calculator, or a 1/4 mile ET calculator, though if FALCON4 wants to write that code i'm down for it.

"Nipping drag racing concerns in the bud as relating to this project" - maybe you are, but maybe FALCON4 is also interested in this, did you ever ask the man? Guess you just want to speak for everybody. If he says he's not going to bother with the code, then fine, he's the one running this thread and putting the time in to write the code.

Why you gotta hate? You must post on honda-tech.

[steffen707]

Originally Posted by dcb

Still cdA/cRR seems like the most enabling feature to me plus it is simplest to implement (no extra circuitry required). It's just hard for me to get excited about a clock (though I'm glad the main loop timing is proving accurate).

Yes I agree as well. This would be very cool to test and generate good data about tire choices and aero mods. And making it backwards compatible to anybody who "DONATED" for a mpguino in the past is very important.