Quote:
Originally Posted by AndrzejM
t_vago, In next couple of weeks I'm taking a round trip across central Europe, with a plan to make ~4kkm and the plan is to test your code. So my question is... Any recent updates that you could post here for me to upload the latest version? Finally I'll be able to test it and I'm so glad to be able to finally see all those nice features working.
|
a 4k km test run? That would truly be awesome! Are you going to be able to reprogram your MPGuino during this trip? Reason I'm asking, is because the code itself is still changing, although no longer on a daily basis. I'm currently chasing down a potentially serious bug in the fuel injector pulse reading code, and I'd like to know that you would be able to apply the possible bug fix, when one comes out.
Also, I'd like to finalize the A-B graphical display, and I'd like to get the coastdown test code working (there are several defined EEPROM parameters so far, the RAM variables have been defined, and the coastdown data gathering routine is up and running, but the actual computation and display code has not yet been coded).
I'll post the latest version, later on today.
Quote:
Originally Posted by Ardent
it seems as though both a rising and falling edge are registering as a pulse since displayed MPH was double actual. PPM needed to be set to 19600 to display a realistic value (not yet calibrated -- just ballpark).
|
Yah, both the 1.86 code and the original MPGuino code count both the rising and the falling edges of the VSS pulse train. At first glance, that doesn't appear to make a whole lot of sense. However, if you consider that some VSS pulse trains are mechanically generated via reed switches (instead of Hall effect sensors), then it makes a little bit of sense, because there is then a need to be able to debounce said switches.
It's a fancy way of saying "I kept it in the 1.86 code because it's always been there."