t vago's MPGuino workspace thread

[Ardent]

Originally Posted by t vago

What hardware are you using?

Thanks for the update. I'm attempting to run an old Fundamental Logic board upgraded with a 328.

[Ardent]

Originally Posted by AndrzejM

One suggestion for you, maybe worth to consider in a next version of your code. I was changing the "Canadian" version of MPGuino, and I've embeded the code for coast down tests. Up and down speeds are edited with global parameters, and when I go to the proper screen it's showing the exact time and distance that car was coasting from one given speed to the other. It's very accurate and much more convinient than reading time and distance from your speedo and a stop watch.

That would be cool!

[Ardent]

mpguino_1.86_tav.c loaded and appears to be working OK on the bench.

Had one minor issue while entering initial parameters: Sometimes pressing one button would trigger the function of one of the other buttons, such as the right button would cause the value to increment instead of moving the cursor. Could be my shady old hardware and/or user error though.

[AndrzejM]

I had similar issue once and it turned out that was a faulty ground connection at the buttons. You may want to check yours

[Ardent]

That is possible, but not observed with the 0.86 code.

[Ardent]

Also, when waking the unit from sleep-mode by pressing the LEFT, RIGHT or CENTER button, "Current Reset" is displayed.

[Ardent]

Here are some backlight code changes I like: (items need to be placed in their proper locations)

//Backlight range changes
const uint8_t brightness[] PROGMEM = { 0, 85, 170, 255 }; //middle button cycles through these brightness settings
//Changed 0 to 3 for OFF while sleeping
LCD::setBright(3); // set backlight brightness to zero
//Initial brightness
uint8_t brightnessIdx = 2;  //brightness at startup. 2 = LOW
//Descriptive brightness labels
void doNextBright(void) {
	brightnessIdx++;
	if (brightnessIdx >= brightnessLength) brightnessIdx = 0;
	LCD::setBright(brightnessIdx);
	printFlash(PSTR("Backlight = "));
   if (brightnessIdx == 0) {
     printFlash(PSTR("HIGH"));
   } else if (brightnessIdx == 1) {
     printFlash(PSTR(" MED"));
   } else if (brightnessIdx == 2) {
     printFlash(PSTR(" LOW"));
   } else if (brightnessIdx == 3) {
     printFlash(PSTR(" OFF"));
   }
   gotoXY(0, 1);
	printFlash(PSTR("                "));
	holdDisplay = holdDelay;
}

[AndrzejM]

Originally Posted by Ardent

That is possible, but not observed with the 0.86 code.

I think you should try to A-B-A test that

[t vago]

Originally Posted by Ardent

mpguino_1.86_tav.c loaded and appears to be working OK on the bench.

Good to hear!

Originally Posted by Ardent

Had one minor issue while entering initial parameters: Sometimes pressing one button would trigger the function of one of the other buttons, such as the right button would cause the value to increment instead of moving the cursor.

Interesting. Are you using the traditional button setup, or are you using analog buttons?

Originally Posted by Ardent

Could be my shady old hardware and/or user error though.

... No... I've seen that, too, every once in a while, but only when I used analog buttons. I figured that it would eventually be identified through testing. It could either be the analog button code, or it could be the choice selection code change that more easily enables support for more than 3 buttons at a time.

[t vago]

Originally Posted by AndrzejM

t_vago - you've done a tremendous job to upgrade MPGuino's software.

Thank you very much. Looking forward to your help with this code.

Originally Posted by AndrzejM

One suggestion for you, maybe worth to consider in a next version of your code. I was changing the "Canadian" version of MPGuino, and I've embeded the code for coast down tests. Up and down speeds are edited with global parameters, and when I go to the proper screen it's showing the exact time and distance that car was coasting from one given speed to the other. It's very accurate and much more convinient than reading time and distance from your speedo and a stop watch.

You got coastdown testing to work? That would be cool!