t vago's MPGuino workspace thread, continued

[t vago]

Did some more modifications to my code to make it more modular. One side effect is that my code now supports 20x4 LCD displays with ease. It also supports any TWI LCD 16x2, 20x2, or 20x4 display.

[t vago]

Performed substantial re-write to menu code to support 20x4 screens, among other things. Rearranged menu items to strengthen menu-based feature selection.

Finished refactoring dragrace / accel test code, and discovered that it didn't work as of several years ago. Dragrace / accel test debugged and works now.

Minor refinements to debug terminal code.

Now starting to refactor existing coastdown test code.

[t vago]

Coastdown testing is again put on hold for now - trying to figure out the best way ahead to actually do the calculations

In the meantime, I have started efforts to allow my code to run on the MPGuino Colour Touch.

So far, I have Bluetooth support incorporated and almost completely debugged. My code is now able to transmit to an Android smartphone using the MPGuinoBlue app found on Google Play. No word on iPhone compatibility, since I do not think there is currently an iPhone app written for the Colour Touch.

The only hiccup remaining for my code's Bluetooth support is that the smartphone screen will occasionally stop updating after a parameter is changed, and will not start updating again until the settings menu is accessed.

https://www.youtube.com/watch?v=ZPqg6iU29Tw

[t vago]

A little more testing suggests that my hiccup described above is happening when MPGuino is processing signals simulating high speeds and high RPMs.

Since i don't expect people to do a lot of configuration changes while speeding down the highway, i am going to give solving this hiccup a low priority.