t vago's MPGuino workspace thread

[Ardent]

The day ended up being 375 miles total with no glitches. I'm pleased; thanks for the good work t vago!

[AndrzejM]

First part of my trip behind me. I'm in Prague and MPGuino works flawlessly. I just need to get used to it because it's different from previous version I was using. I'm just not familiar with all the button combinations and all the letters describing values yet.

It's not calibrated yet so I can't tell anything about it's accuracy but I've entered all numbers from the previous setup so there shouldn't be a big difference anyway. For a moment I was thinking that new code gas the same problem as 0.86 version described here:Metric version bug, but after figuring out how to properly reset current view (that took me a while ) it turned out that everything seems to be working just fine.

More to come after fill up and calibrating new setup.

Anyway good job t_vago!

[Quezacotl]

Would'nt it be best that the text would scroll in the settings? Then there would be enough room to write it clearly instead of 16 char limit.

[t vago]

Originally Posted by Ardent

The day ended up being 375 miles total with no glitches. I'm pleased; thanks for the good work t vago!

It's good to hear that the code worked correctly this time. Looks like it was a mistake to move the injector interrupt code onto a single pin.

Originally Posted by AndrzejM

First part of my trip behind me. I'm in Prague and MPGuino works flawlessly. I just need to get used to it because it's different from previous version I was using. I'm just not familiar with all the button combinations and all the letters describing values yet.

Yah, I got to work on documentation. Maybe I can convince the powers-that-be here to give me a Wiki page for the new-and-improved MPGuino.

The metric bug you described in the 0.86 code was indeed due to modifying the original code to work with 20 MHz processors, and not updating every single time-dependent line of code. That was one of the first things I overhauled, and I tested the bejeezus out of it to make sure it'd work correctly on 16 MHz and 20 MHz processors.

Originally Posted by AndrzejM

More to come after fill up and calibrating new setup.

Anyway good job t_vago!

Thank you! Looking forward to more of your feedback!

Originally Posted by Quezacotl

Would'nt it be best that the text would scroll in the settings? Then there would be enough room to write it clearly instead of 16 char limit.

That might could be a good idea, too. It wouldn't take too much effort to set up.

[AndrzejM]

Originally Posted by t vago

Yah, I got to work on documentation. Maybe I can convince the powers-that-be here to give me a Wiki page for the new-and-improved MPGuino.

That would be great.

Originally Posted by t vago

The metric bug you described in the 0.86 code was indeed due to modifying the original code to work with 20 MHz processors, and not updating every single time-dependent line of code. That was one of the first things I overhauled, and I tested the bejeezus out of it to make sure it'd work correctly on 16 MHz and 20 MHz processors.

And it works as it should! Good job!

And driving here I got this idea that I could use your code for measuring pressure to get temerature reading from the engine. I was working on that with "canadian" code but haven't finished that yet. So I need to start again with 1.86tav code Could you provide the diagram how you actually connected MPGuino to the MAP sensor? Thanks

[t vago]

Originally Posted by AndrzejM

And driving here I got this idea that I could use your code for measuring pressure to get temerature reading from the engine. I was working on that with "canadian" code but haven't finished that yet. So I need to start again with 1.86tav code Could you provide the diagram how you actually connected MPGuino to the MAP sensor? Thanks

The diagram has been folded into the code itself.

Also modified the code to make it easier to display things like the A-B display and the coastdown display, and added Arduino Mega 2560 support (which needs to be tested). The display modifications are slightly buggy right now, but should be fixed soon.

[AndrzejM]

Great job! As always

Thanks

[josemapiro]

I was been testing the arduino mega and buttons legacy are working, but the injector readings does not give me any information, even tested if it worked? The information of the speed pin, did not get to test because had the car stopped in the garage.
The pins of the LCD to the Arduino Mega, is that they could be changed to free the PWM pins. I'm using the ports A

const uint8_t lcdData = 		(1 << 5); // on PORTA
const uint8_t lcdEnable = 		(1 << 4); // on PORTA
const uint8_t lcdBit3 = 		(1 << 0); // on PORTA
const uint8_t lcdBit2 = 		(1 << 1); // on PORTA
const uint8_t lcdBit1 = 		(1 << 2); // on PORTA
const uint8_t lcdBit0 = 		(1 << 3); // on PORTA

Another fantastic work, as always.

Thank you
José Rodrigues

[t vago]

Originally Posted by josemapiro

I was been testing the arduino mega and buttons legacy are working, but the injector readings does not give me any information, even tested if it worked? The information of the speed pin, did not get to test because had the car stopped in the garage.

If the legacy buttons are working now, then the VSS signal should work, as well.

What pins do you have your injector signal connected to? I currently have the pins mapped to:

  Arduino Mega2560
	injector sense open  PE4 (INT4)
	injector sense close PE5 (INT5)

Originally Posted by josemapiro

The pins of the LCD to the Arduino Mega, is that they could be changed to free the PWM pins. I'm using the ports A

const uint8_t lcdData = 		(1 << 5); // on PORTA
const uint8_t lcdEnable = 		(1 << 4); // on PORTA
const uint8_t lcdBit3 = 		(1 << 0); // on PORTA
const uint8_t lcdBit2 = 		(1 << 1); // on PORTA
const uint8_t lcdBit1 = 		(1 << 2); // on PORTA
const uint8_t lcdBit0 = 		(1 << 3); // on PORTA

Another fantastic work, as always.

Thank you!

So these two statements are still correct?

const uint8_t lcdBrightness = 		(1 << 1); // on PORTB
const uint8_t lcdContrast = 		(1 << 6); // on PORTD

[josemapiro]

Originally Posted by t vago

If the legacy buttons are working now, then the VSS signal should work, as well.

What pins do you have your injector signal connected to? I currently have the pins mapped to:

  Arduino Mega2560
	injector sense open  PE4 (INT4)
	injector sense close PE5 (INT5)

Yes I moved the pins PE4 and PE5 but not getting any information in MPGuino.

So these two statements are still correct?

const uint8_t lcdBrightness = 		(1 << 1); // on PORTB
const uint8_t lcdContrast = 		(1 << 6); // on PORTD

Use different pins, the OC0A OC1A in the arduino mega is on pins PB5 and PB7.

const uint8_t lcdBrightness = 		(1 << 5); // on PORTB
const uint8_t lcdContrast = 		(1 << 7); // on PORTB

Thank you
José Rodrigues