MPGuino release one workspace

[markr-nc]

Originally Posted by dcb

Have you been able to dial in the trip distance?

I've noticed that the trip on the metro seems pretty accurate despite the jumpy instant speed reading, which means it is getting most/all of the vss pulses anyway.

The cheap fix is to skip the timing of the vss pulses and just compute "instant" speed based on last few seconds worth of pulses instead of the last .5 seconds worth.

Do we make a change in here:

unsigned long instantmph(){
cli();
unsigned long vssPulseTimeuS = (lastVSS1 + lastVSS2) / 2;
sei();
init64(tmp1,0,1000000000ul);
init64(tmp2,0,parms[vssPulsesPerMileIdx]);
div64(tmp1,tmp2);
init64(tmp2,0,3600);
mul64(tmp1,tmp2);
init64(tmp2,0,vssPulseTimeuS);
div64(tmp1,tmp2);
return tmp1[1];
}

unsigned long instantmpg(){
cli();
unsigned long vssPulseTimeuS = (lastVSS1 + lastVSS2) / 2;
sei();
init64(tmp1,0,1000000000ul);
init64(tmp2,0,parms[vssPulsesPerMileIdx]);
div64(tmp1,tmp2);
init64(tmp2,0,3600);
mul64(tmp1,tmp2);
init64(tmp2,0,vssPulseTimeuS);
div64(tmp1,tmp2);
// return tmp1[1];


or somewhere else? If it's in here, I've been trying to figure it out but haven't had much success. It kinda looks to me like the second paragraph is doing what the first one describes, I think. I was wondering if the 3600 in the second init64 was where the number would change?

I'll certainly admit that the abstract thought processes used in programing aren't my strong point, if it were I wouldn't be getting greasy and my knuckles beat up working on cars for a living...

Many thanks,
Mark

[ishiyakazuo]

Originally Posted by Clev

Has anybody considered the ATMega128 controller? (Link: ATMega Controller) It has double the clockspeed, 4K EEPROM, 128K FLASH. Does anybody know if this is compatible with the Arduino? I'd like to be able to add some extra functionality, and I think we're going to hit the limits of Arduino's FLASH.

ATMega128 only comes in flat-packs (not easy for everyone to solder).
Did you look at ATMega328? It should be Arduino-compatible some day (and someone already has mods you can do to make it run Arduino code today). It comes in the same 28-pin DIP package.
Details on using ATMega328 with Arduino

[TruckTrash]

Originally Posted by MetroMPG

Also.... the MPGuino wiki. Think it's worthwhile starting a new thread to talk that over in more detail? How would you like to see it evolve, content wise? I was talking to Ben, and have agreed that one or both of us will take an active role in shepherding that part of the project, if you like.

Sounds like a winner, I have not really been managing the WIKI much, because it really does not fit in my daily routine, but I would like to make a suggestion. Start by putting a link in the first post, because that is where everyone goes that is new to this post.

As with many good pieces of information, it gets lost in the forum, and the WIKI is basically lost right now because anyone new to this post will not even know it exists and as a result no-one will bother to update it if they do not know it exists or others do not continue to update it.

I look forward to seeing how the WIKI transforms.

TruckTrash

[Clev]

Originally Posted by ishiyakazuo

ATMega128 only comes in flat-packs (not easy for everyone to solder).
Did you look at ATMega328? It should be Arduino-compatible some day (and someone already has mods you can do to make it run Arduino code today). It comes in the same 28-pin DIP package.
Details on using ATMega328 with Arduino

Ah, excellent. Looks like a drop-in upgrade (physically, anyway) that doubles the EEPROM, SRAM and FLASH. I'll go ahead and order the Arduino with that possibility in mind.

[bbjsw10]

Originally Posted by wagonman76

since bypassing that transistor circuit. NO glitches since, not even one.

How did you bypass and should I do this when I build mine to just avoid the problem. Will be receiving parts soon.

[dcb]

Originally Posted by bbjsw10

...should I do this when I build mine...

You should try to build it correctly so the guino can control the backlight for you.

[bbjsw10]

dcb Thanks for the quick response. I will take your word on it.

[ptsmith24]

I got my board and LCD in today and picked up the misc. parts that I need. I'll get it all built in the next few days (definitely by this weekend) and post back with results. I'll try and take note of vehicle specific stuff so I can contribute to the wiki.

[forgottenmindset]

Originally Posted by ac7ss

An idea for the instant speed problem. (Stolen from the space shuttle software.) Take 3 time readings (time between pulses) and average the 2 that are closest in value to each other.
If you have the following 3 values: 100 45 47, have it throw out the 100 and return a value of 46.

I have some experience in optimizing code. Would you mind if I look at the source and help save some memory?

Thanks, that's a great idea, I'll try it


Please optimize this if you can, it uses lots of memory

void doDisplay0_60() {

  
  switch ( g_Mode060 ) {
      
    // STAGE VEHCLE INTRO
    case 0:
      LCD::LcdCommandWrite(B00000001);  // clear display, set cursor position to zero
      LCD::print("STAGE VEHICLE...");
            
      if( instantmph() < 1000ul )
        g_Mode060 = 1;
      
      g_StartTime060 = 0;
      g_StopTime060 = 0;
      
      break;
      
      // ON YOUR MARK GET SET AND GO
    case 1: 
      LCD::LcdCommandWrite(B00000001);  // clear display, set cursor position to zero
      LCD::print("..ON YOUR MARK..");
      LCD::gotoXY(1,1);
      LCD::print("...GET SET...  ");
      delay2(2000);
      LCD::LcdCommandWrite(B00000001);
      LCD::print("      G0!      ");    
      
      
      delay2(3000);
      
      // Start the Timer and compensate for the delay
      g_StartTime060 = millis2() - 3000; 
      g_Mode060 = 2;
      break;
  
    // ITS GO TIME
    case 2:
    
      // Timer's already started
     // IF NOT AT 60 mph yet, DSPLAY BIG TIMER
     if( instantmph() < 60000ul )  
       bigNum( instantmph() ,"CUR","SPD");
     
     // Else, move on
    else {
       g_Mode060 = 3;
       LCD::LcdCommandWrite(B00000001);
     }
      break;
    case 3:
      // Lets stop the timer,
      // But only once
      if( g_StopTime060 == 0 ) {
        g_StopTime060 = millis2() - 500; // reads 500 high due to processing
      }
      LCD::print("0 to 60 in...");
      LCD::gotoXY(1,1);   
      LCD::print(format((g_StopTime060 - g_StartTime060))); 
      LCD::print(" Seconds");
      
      g_Mode060 = 0;
      delay2(5000);          
      break;
  }
  
    
} // end doDisplay0_60

[wagonman76]

Originally Posted by dcb

You should try to build it correctly so the guino can control the backlight for you.

Yes I agree, start by building it per the specs. Only if something isnt quite right then find a workaround. Mine was one such case where the display ended up not having the exact same specs as the stock display. I found out my pin 15 is basically just there for looks, it does not connect to anything internally. I found that it takes a different circuit to dim my backlight, I have to break the display ground. So I was using the stock transistor to control my own transistor to control the backlight, which may have led to my problems. Going to just my own transistor and changing some code seems to have solved the issue.