t vago's MPGuino workspace thread

[josemapiro]

Thank you, my car is a Honda Civic MB3 1999 with the D15Z8 engine, the reference is the Injector 06164-P2A-000, this site says it is an injector Bosch 0-280-150-783.
You can see here in these information sites on the injector.
Bosch
https://www.google.pt/url?sa=t&rct=j...54934254,d.ZGU

The MAP sensor has the reference 37830-PAA-S00. What is a Denso 079800-4250.
HONDA MAP SENSOR (CIVIC 1998-2000) - 37830PAAS00


Thank you
José Rodrigues

[t vago]

Originally Posted by josemapiro

Thank you, my car is a Honda Civic MB3 1999 with the D15Z8 engine, the reference is the Injector 06164-P2A-000, this site says it is an injector Bosch 0-280-150-783.
You can see here in these information sites on the injector.

Okay, this injector appears to flow 209 cc/min (ml/min is equivalent). The reference pressure is 300 kPa, or 43.5 psig. I've read on the intertubes that stock Honda fuel pressure is at 40 psig, or 276 kPa. Assuming 4 cylinders, my MPGuino says that the Microseconds/gallon number is 283300095 (microseconds/liter should be 74839967). What is your number?

Originally Posted by josemapiro

The MAP sensor has the reference 37830-PAA-S00. What is a Denso 079800-4250.

You should not need to worry about the MAP sensor. Your car has a traditional fuel pressure regulator that is indexed to manifold vacuum.

[josemapiro]

Thank you
I will use these values ​​and see how it works.
Which of these settings, advise me to use in my car:

#define blankScreenOnMessage true
#define trackIdleEOCdata true
#define useSerialPortDataLogging true
#define useBufferedSerialPort true
#define useCalculatedFuelFactor true
#define useWindowFilter true
#define useClock true
#define useSavedTrips true
#define useScreenEditor true
#define useBarFuelEconVsTime true
#define useBarFuelEconVsSpeed true
#define useSpiffyBigChars true
#define useChryslerMAPCorrection true
#define useCoastDownCalculator true
#define useDebugReadings true
#define forceEEPROMsettingsInit true
#define useEEPROMviewer true
#define useBenchMark true
#define useSerialDebugOutput true
#define useSWEET64trace true
#define useSWEET64multDiv true

If use the MAP does not get better results?
I still need a help is what the letters mean in the LCD menus

 --------------------------------------------------
| is ---- t ---- | iL ---- s ---- | iL ---- s ---- |
| ir ---- L ---- | ir ---- L ---- | cL ---- d ---- |
 --------------------------------------------------
| iL ---- s ---- | cs ---- L ---- | ts ---- L ---- |
| tL ---- d ---- | cd ---- L ---- | td ---- L ---- |
 --------------------------------------------------
| Cd ---- L ---- | tL ---- L ---- |
| Td ---- L ---- | tT----- d----- |
 ---------------------------------

Thank you
José Rodrigues

[t vago]

Originally Posted by josemapiro

Which of these settings, advise me to use in my car:

Why did you strip out the comments?

// selectable options - all may be chosen independently of one another, save for serial data logging.
// the serial data logging option will conflict with the Parallax LCD output option, if both are selected at the same time
//#define blankScreenOnMessage true		// Completely blank display screen upon display of message
#define trackIdleEOCdata true			// Ability to track engine idling and EOC modes
//#define useSerialPortDataLogging true	// Ability to output 5 basic parameters to a data logger or SD card
//#define useBufferedSerialPort true		// Speed up serial output
//#define useCalculatedFuelFactor true	// Ability to calculate that pesky us/gal (or L) factor from easily available published fuel injector data
#define useWindowFilter true			// Smooths out "jumpy" instant FE figures that are caused by modern OBDII engine computers
#define useClock true					// System clock, and means to set it
#define useSavedTrips true				// Ability to save current or tank trips to any one of 10 different trip slots in EEPROM
//#define useScreenEditor true			// Ability to change any of 8 existing trip data screens, with 4 configurable figures on each screen
#define useBarFuelEconVsTime true		// Show Fuel Economy over Time bar graph
#define useBarFuelEconVsSpeed true		// Show Fuel Economy vs Speed, Fuel Used vs Speed bar graphs
#define useSpiffyBigChars true
//#define useChryslerMAPCorrection true	// Ability to perform on-the-fly fuel injector data correction for late-model Chrysler vehicles
//#define useABresultViewer true			// Ability to graphically show current (B) versus stored (A) fuel consumption rates
//#define useCoastDownCalculator true		// Ability to calculate C(rr) and C(d) from coastdown

// program measurement and debugging tools
//#define useDebugReadings true
//#define forceEEPROMsettingsInit true
//#define useEEPROMviewer true			// Ability to directly examine EEPROM
//#define useBenchMark true				// this is probably broken - last time I used it was in August
//#define useSerialDebugOutput true

// SWEET64 configuration/debugging
//#define useSWEET64trace true			// Ability to view real-time 64-bit calculations from SWEET64 kernel
//#define useSWEET64multDiv true			// shift mul64 and div64 from native C++ to SWEET64 bytecode

I'd recommend that you use the above selections.

Originally Posted by josemapiro

If use the MAP does not get better results?

The MAP option is only needed for late model Chrysler (and other cars) that have a constant-pressure fuel regulator. This fact is even reflected in the option name (useChryslerMAPCorrection). Your Honda does not need it.

Originally Posted by josemapiro

I still need a help is what the letters mean in the LCD menus

In order, these are the main screen displays:

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

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

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

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

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

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

"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 |
 ---------------------------------------------

[josemapiro]

Thank you

Originally Posted by t vago

Why did you strip out the comments?

I just removed the comments to save space in the post.

I've done the settings aconcelhou now just use and see how it behaves.
The abbreviations "FE" and "EOC" what they mean concretely, ask excuse because probably the answer is obvious for you but for me it is a bit difficult.

Thank you
José Rodrigues

[t vago]

Originally Posted by josemapiro

I've done the settings aconcelhou now just use and see how it behaves.
The abbreviations "FE" and "EOC" what they mean concretely, ask excuse because probably the answer is obvious for you but for me it is a bit difficult.

Sorry - FE means fuel economy, while EOC means engine-off coasting.

[t vago]

Finally got the TinkerKit LCD module to work with MPGuino. As expected, substantial pin re-mapping was required. Also, it looks like the only button option available for the TinkerKit module is analog buttons. The traditional digital buttons (1 per pin) simply cannot be adapted.



Keep in mind that the below information in this here post is very preliminary, and may be subject to change.

The USB port on this module may be used as the serial datalogging output, while the TWI (either TWI1 or TWI2) pin0 (PD0/INT0) and pin1 (PD1/INT1) pins are going to be used for the fuel injector open/close sense pins. Digital port D12 (which is what is labeled on the module that I have in my hands) should really be labeled D11 (as it is in the picture). D11 (PB7/PCINT7/OC0A/OC1C) is going to be used for the VSS input. Analog port A0 (PF7/ADC7) is going to be used as the analog button input.

The serial port pin0 (PD3/INT3) and pin1 (PD2/INT2) might also could be used for fuel injector input, or it could be used for another serial port... perhaps for a secondary MPGuino display.

The TX LED is driven off of PD5/XCK1/CTS. The RX LED is driven off of PB0/PCINT0/SS. The S LED is driven off of PC7/OC4A/CLK0.

Analog ports A1 and A2 (PF6/ADC6, PF5/ADC5) are likely going for either the Chrysler MAP correction hardware, or for other analog voltage projects (vehicle battery, coolant temperature, or what have you).

Digital port D6 (PD7/OC4D/ADC10) apparently can also double as an analog pin, so this might could also be used for analog voltage projects.

Digital port D5 (PC6/OC3A/OC4A) appears to be a straight digital port.

[josemapiro]

Originally Posted by t vago

Finally got the TinkerKit LCD module to work with MPGuino.

Another good buy for who is limited with the pins.

I have a doubt regarding the values ​​that are presented in MPGuino, which is when I stop the displayed value on instant FE begins to increase until it disappears, is this normal? Or have something that is not right?
I leave here one video a bit bouncy, but is not easy to conduct and record at the same time.

http://www.youtube.com/watch?v=wYQQzTXytw8

Thank you
José Rodrigues

[t vago]

Originally Posted by josemapiro

Another good buy for who is limited with the pins.

I have a doubt regarding the values ​​that are presented in MPGuino, which is when I stop the displayed value on instant FE begins to increase until it disappears, is this normal? Or have something that is not right?
I leave here one video a bit bouncy, but is not easy to conduct and record at the same time.

Yep, it is normal to have your instant fuel economy value increase until it disappears, when you stop. You can check the instant fuel economy value by taking your instant speed value, multiplying it by 100, and then dividing it by your instant fuel rate value.

So, for the case for just before the instant FE disappears, it is displayed as 184.55 L/100km. The instant speed is 2.5 km/hr, and the instant fuel rate is 0.63 L/hr. Taking these values, we find that the instant fuel economy is actually (2.5 * 100) / 0.63, or 396.8 L/100km.

In this case, the displayed instant fuel economy value is actually lower than it should be, and that's due to the window filter code that smooths out the display values. So - this is normal.

People that use US units, instead of metric units, will see their instant fuel economy value drop as they come to a stop.

That's a pretty cool display, by the way. I like the black background with white dots.

[josemapiro]

Originally Posted by t vago

Yep, it is normal to have your instant fuel economy value increase until it disappears, when you stop. You can check the instant fuel economy value by taking your instant speed value, multiplying it by 100, and then dividing it by your instant fuel rate value.

So, for the case for just before the instant FE disappears, it is displayed as 184.55 L/100km. The instant speed is 2.5 km/hr, and the instant fuel rate is 0.63 L/hr. Taking these values, we find that the instant fuel economy is actually (2.5 * 100) / 0.63, or 396.8 L/100km.

In this case, the displayed instant fuel economy value is actually lower than it should be, and that's due to the window filter code that smooths out the display values. So - this is normal.

People that use US units, instead of metric units, will see their instant fuel economy value drop as they come to a stop.

Ok, it was more to remove doubts because it seems strange behavior.

That's a pretty cool display, by the way. I like the black background with white dots.

I like most dark background and bright letters, I think more visible as well.

Thank you
José Rodrigues