Mr RB
Well-Known Member
OK, sorry for the delay Wjhos but I finally worked out what you meant.
Originally the capmeter code was only JUST squeezed into a 2k PIC, so I left out the nicety of leading zero correction. It was a trade-off to still be able to fit all that 32bit math code into a tiny cheap PIC.
So in the original HEX file it shows; " . 1pF" and " .-3pF" instead of "0.01pF" and "-0.03pF".
However there are probably other fussy (OCD?) people like yourself that really hate imperfect leading zeros. So I found a way to squeeze the leading zero correction into the code.
I have re-programmed my own Capmeter and it seems to be all working perfect, and since this was only a minor display tweak I have not bothered with keeping the old HEX file, so the one on the web page is now the new improved HEX.
And thanks for the suggestion.
New HEX file is here;
https://romanblack.com/onesec/CapMeter.htm
Originally the capmeter code was only JUST squeezed into a 2k PIC, so I left out the nicety of leading zero correction. It was a trade-off to still be able to fit all that 32bit math code into a tiny cheap PIC.
So in the original HEX file it shows; " . 1pF" and " .-3pF" instead of "0.01pF" and "-0.03pF".
However there are probably other fussy (OCD?) people like yourself that really hate imperfect leading zeros. So I found a way to squeeze the leading zero correction into the code.
I have re-programmed my own Capmeter and it seems to be all working perfect, and since this was only a minor display tweak I have not bothered with keeping the old HEX file, so the one on the web page is now the new improved HEX.
And thanks for the suggestion.
New HEX file is here;
https://romanblack.com/onesec/CapMeter.htm