Just a short boring posting today. One critical aspect of the CW code development is the timing. A dash is three time the length of a dot. Then there is the time spacing between the elements like dah di dah dit (letter C) and time spacing between the next letter like dah dah di dah, (letter Q). Finally time spacing between words like CQ CQ.
We pick the dot length as the magic decoder ring and call that "x" and therefore a dash = 3*x. By doing this we are able to define all times by x with multipliers. If we want to change the loop speed, we need only modify the code with a single changed x value.
I had fun making x = a really small-time increment. What resulted was "the spy stuff" -- a code burst. The serial monitor showed it was sending the code but there was only but a brief flash of LED 13. How cool is that? I wonder if the Reverse Beacon Network can decode that?
I mention the Reverse Beacon Network as that is a great tool for testing a rig. You call CQ (in CW) where there are CW skimmers worldwide that listen for the CQ calls and if recognized will display your call on an internet webpage. This will convince you that 100 milli-watts travels a long way. The CW Sender will do a lot of the heavy lifting using the RBN.
Code Burst
Like I said BORING!
73's
Pete N6QW