Haven't found that. Maybe that's because still don't know how exactly setup my custom screen.
It should actually be in the 1st screen, instrumentation. However, the labelling leaves a bit to be desired.
I'm thinking of incorporating custom characters in the displays, like below. The OBDuino folks apparently already have this, and it's much more readable than what I currently have.
I'm also thinking of completely revamping the screen edit displays, and adding a brief (2 second) helper screen, accessible maybe by pressing all three buttons at once or something.
It would display something like this for the 1st second,
and then it would display something like this for the next second.
Code:
-------------------
| FE SPEED |
| RATE FE |
-------------------
Quote:
Originally Posted by AndrzejM
all I need is to change the code to get proper readings. I have everything hooked up to my MPGuino already.
Hm... Maybe I can make the analog display code a bit more generic, so that people like yourself don't have to diddle with the code internals. It's already 3/4 of the way there.
One more doubt just now tried to set the clock, but without success, I set the time I want, but when I go to another menu, back to the previous hour, what am I doing wrong?
Really menus need to be refrescados, but not easy task keeping the same LCD, perhaps best present 2 results only, instead of 4 which, has thus conquered space for more characters.
The idea of creating custom characters is good but still may not be enough, the ideal was to have a graphic type LCD so.
It should actually be in the 1st screen, instrumentation. However, the labelling leaves a bit to be desired.
I'm thinking of incorporating custom characters in the displays, like below. The OBDuino folks apparently already have this, and it's much more readable than what I currently have.
I'm also thinking of completely revamping the screen edit displays, and adding a brief (2 second) helper screen, accessible maybe by pressing all three buttons at once or something.
It would display something like this for the 1st second,
and then it would display something like this for the next second.
Code:
-------------------
| FE SPEED |
| RATE FE |
-------------------
Hm... Maybe I can make the analog display code a bit more generic, so that people like yourself don't have to diddle with the code internals. It's already 3/4 of the way there.
That would be great to have such nice labels and if you could modify analog display code to be easy to adapt to custom needs that would be just awesome.
__________________
Quote:
Gerhard Plattner: "The best attitude is to consider fuel saving a kind of sport. Everybody who has enough money for a strong car, can drive fast and hit the pedal. But saving fuel requires concentration, self-control and cleverness. It's a challenge with the nice effect of saving you money that you can use for other more important things."
An indication may be missing, and the average consumption of total several trips, to get a sense of the average that is being done, when making small trips. We'd have one for the average of the trip we undertook, and another of the average of all travel since the last reset.
We'd have one for the average of the trip we undertook, and another of the average of all travel since the last reset.
If I understand you correctly, then the average of the trip you just undertook would be equivalent to the "current" (or CURR) trip, and the average of all travel since the last user-caused reset would be the "tank" (or TANK) trip.
The MPGuino currently does that.
The Following 2 Users Say Thank You to t vago For This Useful Post:
If I understand you correctly, then the average of the trip you just undertook would be equivalent to the "current" (or CURR) trip, and the average of all travel since the last user-caused reset would be the "tank" (or TANK) trip.
The MPGuino currently does that.
Ok, had not yet seen that way, I thought that all the information was relative to the tank, not the average of all trips.
It is the lack of information on the LCD that leads to this, I apologize for the error, I'll wait for the new version to see if is simpler.
2nd attempt at making a decent video demostration. The little flashing character represents the type of trip being displayed, where "I" = INST, "C" = CURR, and "T" = TANK. The labels themselves ought to be fairly self-explanatory, now.
All of the information is more-or-less relative to the tank. Here's how all of the trips are related:
RAW -> INST
0 -> RAW
TANK + INST -> TANK
CURR + INST -> CURR
CURR can be configured via EEPROM parameter to reset, every time MPGuino is awakened.
Both TANK and CURR can be manually reset.
You will never see any RAW display, as it is continually being updated within MPGuino. The INST trip represents a 1/2 second average of the RAW data, as RAW is copied to INST every 1/2 second. After each copy, RAW is reset.
The Following 2 Users Say Thank You to t vago For This Useful Post:
Gerhard Plattner: "The best attitude is to consider fuel saving a kind of sport. Everybody who has enough money for a strong car, can drive fast and hit the pedal. But saving fuel requires concentration, self-control and cleverness. It's a challenge with the nice effect of saving you money that you can use for other more important things."
Although the image is not very good, it seems that it gets better identification.
I believe that the metric system "FE" would be better identified with these characters instead of just "L", do you think?
Today
Other popular topics in this forum...
