Now my CW 'ear' is getting better, I've started to notice these :-). It's not clear why they are commented out - it looks to be that way in the original code as well.
= was the one I noticed 'live', and the above code visually looks right to me - there is an = in the 2x16 LCD character set, and it is 61 (0xd3).
First step then, uncomment the = line above, and see if we get a correct decode for -...-
If that works, move on to see what else is commented out and if there is a sensible way to instate those on the 2x16 charset.
My gut was telling me maybe there was a disparity between the 2x16 charset and ascii, but looking at an ascii chart, = is indeed 61 - so maybe that theory does not wash...
The k4icy CW decoder has some of the decode characters commented out in the code, such as here:
Now my CW 'ear' is getting better, I've started to notice these :-). It's not clear why they are commented out - it looks to be that way in the original code as well.
=was the one I noticed 'live', and the above code visually looks right to me - there is an=in the 2x16 LCD character set, and it is 61 (0xd3).First step then, uncomment the
=line above, and see if we get a correct decode for-...-If that works, move on to see what else is commented out and if there is a sensible way to instate those on the 2x16 charset.My gut was telling me maybe there was a disparity between the 2x16 charset and ascii, but looking at an ascii chart,
=is indeed 61 - so maybe that theory does not wash...