OBDuino Feature Request...

[electromike]

If the OBDuino started using the Atmega328 Chip (A drop in replacement) there will be an extra 16KB of programming space to add some fun features!

Any one have any great Ideas?

• We could add an SD card expansion and log each current outting trip to graph on the computer...
• Make a slightly graphical display for feed back so people who don't like numbers will know how they are doing...
• Add a varriable for the price of gas so you know how much each trip is costing...

What have you always wanted?

[tangomar]

Maybe you could add the math for aero calcs. I mean it can be a gadget where it understands the rate of deceleration in the next 10 secs (for example).

How about the DACs for the O2 fooling in case of an HHO add-on?

CHT reading (or other external ADC-assisted monitoring).

[randerson0248]

I like this thread. I want to add to the wish list.

I think the refresh rate is too fast. I see instant mileage jumping around several times per second. I think updating data every 1/2 second or so would be about right.

I would like to see another display option. Bigger display with instant mpg and current mpg on the same display. If need be, drop the im and cm and have just the numbers. While driving, the IM and CM are the only ones I pay any attention too, and if those two could be larger on the same screen, that would be great.

[NachtRitter]

Something I would really like to see, and I think would really provide a powerful tool for those serious about hypermiling, is combining the SD card logging with GPS. So it is possible to later graph all the good GPS data (speed, location, elevation) against instantaneous FE. Or maybe, SD card logging by default, with the option to add a GPS module and then combine GPS and FE logging.

[Froggy]

I was just thinking yesterday, that the cost of the gas on a trip would be nice.

Perhaps even a graph showing speed and fuel consumed (per minute?) Could also display a base line for average speed and fuel used during trip (or last tank).

[gone22]

Can you even use the 328p on the current OBDuino code (r127)?

[electromike]

You can, The 328 is just a drop in replacement.
The current code fits on the smaller chip, there is just no room left for features.

[randerson0248]

I would also like to see gallons used with the tank data.

[Froggy]

I am thinking of adding a trip data recall function which will allow the user to save trip data for later recall. This could be useful for comparing two or more runs. Say you have an idea for a new route to work. Is it faster, shorter, uses less fuel?

I was thinking this would likely be restricted to Outings (generally a one way trip) but would TRIP or TANK data be useful as well?

The data set (fuel used, time, distance...) could be named for easier recall about what the trip was about. An automatic name could be like "Outing A", "Outing B"... or you could over ride that with a new name like a driver name or street name. Once named, we could easily sort them by shortest or longest distance, fastest or slowest time...

Would distance, fuel, and time be enough or should other data (maybe wasted) be included too. (If we include just three PID's the name would take the other PID. Additional PIDs could be utilized with two screens per trip, or a title screen, or selectable PIDs...)

Saving the data could occur automatically prior to a data reset, or perhaps via a button selection (like all three buttons at once.)

Anyway. What are your thoughts. Would you like to see this feature?

[rmccomiskie]

Originally Posted by randerson0248

...I think the refresh rate is too fast. I see instant mileage jumping around several times per second. I think updating data every 1/2 second or so would be about right.

Software mods: MPG is a rolling average refreshed every 2 seconds, top right is miles to empty, bottom right is projected total tank miles. Running ATmega328.

//Code for display of rolling average MPG at less frequent intervals
//Based on MPGuino v0.75
//Captures the last 10 MPG values
//Calculates the average MPG for those 10 values
//Refreshes the MPG display each 2 seconds


//insert before setup()

pFunc displayFuncs[] ={ 
  ...
  doDisplayInstantA,  //insert this in displayFuncs[]


//insert in setup()

  displayFuncNames[x++]=  PSTR("InstantA "); //add this for new display template


//insert before loop(), add these global vars to retain values across loops

//mpg averaging
unsigned long instAvgMpg = 0;
unsigned long instMpg = 0;
unsigned long prevMpg = 0;
byte loopIdx = 0;
byte dispIdx = 0;


//insert in loop() right after sei();

    //accumulate mpg values in an array of 10 values, oldest values are overwritten
    instMpg = instantmpg();                      //get current mpg
    if (instMpg >= 999999000) instMpg = prevMpg; //if unbelievably high, use mpg from previous loop
    prevMpg = instMpg;                           //keep track of value for next time through loop
    avgBuff[loopIdx][mpgIdx] = instMpg;          //store the current mpg in array
    loopIdx++;                                   //increment the loop number
    if (loopIdx > 9) loopIdx = 0;                //keep track of 10 loops max
    
    //mpg averaging & display damping
    if (dispIdx <= 0) {                          //recalculate after some number of loops
      instAvgMpg = 0;                            //initialize to zero
      for (byte x=0; x<10; x++) instAvgMpg += avgBuff[x][mpgIdx]; //sum all array values
      instAvgMpg = instAvgMpg / 10;              //calculate avg of array values
      dispIdx = 4;                               //recalculate after 4 loops (~2 seconds)
    }
    dispIdx--;                                   //decrement index each time through loop


//insert new display template containing instAvgMpg

void doDisplayInstantA(){displayTripCombo('i','M',instAvgMpg,'S',instantmph(),'G','H',instantgph(),'D',current.miles());}

It works for me! YMMV.