No we are not on the same page, far from it, your assumptions are incorrect :) I designed the interfaces, designed the harnesses, wrote the WRT software including communications protocols used for flashing and also write the low level code that runs on the micro controller for products like the log box pro. So basically every part of the solution. My background is in Mechanical Engineering, but i have been writing software and working with electronics for about 20 years.
In plain English hub what is it you are trying to achieve or find?
In my best hubish is the 555 timer you are handcuffed to. The 0.7v drop you are handcuffed to. The universal control-thold-trigger, meaning, monostable-astable-time delay. The basic handcuffing of 14.7 via show me the volt. The handcuffing of binary. That's the page I was looking for. Found it in the most profound way. All right in front of my face I could not see the cover let alone the pages.
Your 20 years took me a few moments on the computer. Ivan's 1999 busa bump, 3 mules later for me and I found the above. To me, this was 20 years down to the basics on the mechanical end. I found the grail. Now the software. We'd still be off page you trying to get me to the software in the basics. If I can reverse the hardware, then I can reverse the software.
Which brings me to the GPS and tre. If the pcv software is geared for geared maps and fueling, then when the sequential maps are in play there is no tre. When the tre is sending in that single number, the maps default to the one combined map made in your software. No flip you run sequential. Flopped you run limp or the default is a signal out of range. It either stays flipped in FULL Power or flopped to Backup.
I answered my own question is what I achieved and I think it runs the handcuffed indisputable run of, unless you can prove different you see a different page than the Penultimate Page is between the shop manual pages.
Tormenting the motorcycling community one post at a time
Lots'a'Mule'Inn...
