t vago's MPGuino workspace thread

[josemapiro]

The result of my first 200km with MPGuino were fine, not sensed any fault, showing the great work the t vago. Still have not adapted well to the menus, but with time it will improve, below I will make some suggestions that might help.

Originally Posted by t vago

That might could work. Or, maybe have these blinking special characters appear for 1.5 seconds, then disappear for 0.5 seconds.

Yes 1.5 or 2 seconds, it is a matter of try and see what works best.

This is why I made it a requirement that any code I added would still have to run on legacy hardware, even if the code will also support better or more advanced hardware. This is why I am not currently thinking of supporting anything other than a 16x2 LCD display.

Glad you stayed true and did not follow my deviations because we must not forget the others.

The suggestion I have to make has to do with the position of the values ​​in the menus. Sometimes changing menu have the same values ​​but in different positions, the idea was to try to maintain the same positions in the various menus for easier identification.
What do you think?

"Instrument"
 -----------------------------------
| instant FE        - instant speed | 
| instant fuel rate - tachometer    |
 -----------------------------------

"Custom"
 -----------------------------------
| instant FE        - instant speed |
| instant fuel rate - current FE    |
 -----------------------------------

"Instant/Current"
 ----------------------------------
| instant FE       - instant speed |
| current distance - current FE    |
 ----------------------------------

"Instant/Tank"
 -------------------------------
| instant FE    - instant speed |
| tank distance - tank FE       |
 -------------------------------

"Current"
 -------------------------------------
| current fuel used  -  current speed |
| current distance   -  current FE    |
 -------------------------------------

"Tank"
 -----------------------------
| tank fuel used - tank speed |
| tank distance  - tank FE    |
 -----------------------------

"EOC/Idle"
 --------------------------------------------------
| current EOC distance - current fuel used at idle |
| tank EOC distance    - tank fuel used at idle    |
 --------------------------------------------------

"Remaining"
 ---------------------------------------------
| tank fuel used     - tank fuel remaining    |
| tank time to empty - tank distance to empty |
 ---------------------------------------------

Thank you
José Rodrigues

[Ardent]

Originally Posted by t vago

So, what do you think? 4 total saved run sets?

I think that would be fine.

Originally Posted by t vago

Or, maybe have these blinking special characters appear for 1.5 seconds, then disappear for 0.5 seconds.

That would likely be helpful. If the code for the amount of delay isn't too difficult to custom mod that would be helpful too.

[Ardent]

Originally Posted by josemapiro

The suggestion I have to make has to do with the position of the values ​​in the menus. Sometimes changing menu have the same values ​​but in different positions, the idea was to try to maintain the same positions in the various menus for easier identification.
What do you think?

Not a bad suggestion, but my preference would be to not change the vertically stacked relationship of Instant and Current or Tank FE.

[josemapiro]

Originally Posted by Ardent

Not a bad suggestion, but my preference would be to not change the vertically stacked relationship of Instant and Current or Tank FE.

It's just an idea, which can be adjusted, if not difficult put into in practice, of course.

Thank you
José Rodrigues

[josemapiro]

Hi t vago When we can expect news.
I intended to use a RTC board in MPguino not to have always be setting the clock, whenever I turn off the ignition, or not to have MPGuino always on.
What changes in the code are necessary in order to work on the Arduino Mega.

Thank you
José Rodrigues

[t vago]

Originally Posted by josemapiro

I intended to use a RTC board in MPguino not to have always be setting the clock, whenever I turn off the ignition, or not to have MPGuino always on.
What changes in the code are necessary in order to work on the Arduino Mega.

What are the details of the RTC board?

[josemapiro]

Originally Posted by t vago

What are the details of the RTC board?

The RTC board is of the link, but without the DS18B20.
Real Time Clock Module | www.hobbyist.co.nz

Thank you
José Rodrigues

[t vago]

Originally Posted by josemapiro

The RTC board is of the link, but without the DS18B20.
Real Time Clock Module | www.hobbyist.co.nz

Thank you
José Rodrigues

I would have to buy something like this, to properly integrate it into MPGuino.

I like the fact that it has 32K of EEPROM. One could store a good deal many more things inside there.

This TinyRTC appears at the top of Amazon.com's query results for "arduino rtc". As I have to buy a few other things anyhow, I will get one or two of these things, too, to experiment with.

[josemapiro]

Originally Posted by t vago

I would have to buy something like this, to properly integrate it into MPGuino.

I like the fact that it has 32K of EEPROM. One could store a good deal many more things inside there.

This TinyRTC appears at the top of Amazon.com's query results for "arduino rtc". As I have to buy a few other things anyhow, I will get one or two of these things, too, to experiment with.

For you who also have the Arduino Mega is good but for those who have the Arduino Uno is least two pin Analogue, and as we are few is a little bit difficult to implement.
These 32k EEPROM also provides to use for in the remainder of the code or is it just to the clock?

Thank you
José Rodrigues

[t vago]

I got my TinyRTC module in the mail yesterday, and have made some changes to the code to begin supporting being able to use TWI. Both the serial and the LCD buffering code have been modified to use a simple Buffer class, and this class should prove useful for implementing TWI support. One welcome side benefit was that approximately 200 bytes of code space got freed up.

Also killed a few obscure bugs, and implemented the requested refinement in the blinking code. Now, the special little type characters in the main display will disappear for 0.5 seconds, then appear for 1.5 seconds. I can very easily make it so that they can appear for 3.5 seconds, then disappear for 0.5 seconds, if need be.

A-B testing code and coastdown testing code have not been worked on, I'm afraid. Life has been busy lately, so haven't been able to do much else with coding.

Originally Posted by josemapiro

For you who also have the Arduino Mega is good but for those who have the Arduino Uno is least two pin Analogue, and as we are few is a little bit difficult to implement.

If somebody (like me) is willing to go with the 5-button analog button code and hardware, that will make available the two required pins for the native hardware TWI communication interface.

Originally Posted by josemapiro

These 32k EEPROM also provides to use for in the remainder of the code or is it just to the clock?

The EEPROM and the clock share the SCL and SDA pins, but they are separate devices.