Skip to main content

Reducing CW Key Errors in uBITX

Reducing CW Key Errors in uBITX

uBITX uses ADC to distinguish CW Keys.
Unmodified uBITX uses A6 of ADC I / O as CW Key input.
The A6 is connected to 5Volt with a 4.7K ohm resistor.



The Arduino ADC has a value between 0 and 1023.
As shown in the figure above, A6 is connected to 5Volt at 4.7K, so you will get a value of 1023.
1023 / 5 * 5(input) = 1023

If you press the straight key, A6 will have a value close to zero.
1023 / 5 * 0(input) = 0

To use Paddle with uBITX, we need to use 2.2k and 10k resistors.

When press the Dot key of Paddle
5 * 2.2 / (4.7 + 2.2) = 1.594
1023 / 5 * 1.594  = 326

When press the Dash key of Paddle
5 * 10 / (4.7 + 10) = 3.4
1023 / 5 * 3.4 = 695

When both Dot and Dash are pressed
5 * 1.8 / (4.7 + 1.8) = 1.3
1023 / 5 * 1.3 = 265


The above values are ideal values.
In actual use, errors occur in the measured value due to the error rate of the resistance, the length of the wire, and the resistance of the key contact.
Therefore, we use a wide range of values as shown below.


With the above code, can use CW Key in most environments.

However, if for any reason a strange value occurs, it will behave as if the wrong key is pressed.
The video at the bottom of this document deliberately caused the contact to become unstable, resulting in an error.

To reduce these errors, CEC Firmware 1.0 and later versions allow you to optimize the range of ADC values for your environment.
The video made the worst case and minimized the ADC range to avoid the worst unreliable contact errors.



Press the function key


Press the function key, when 'Setup On?' appears.



Press the function key

Press the function key, when 'ADC Line Monitor' appears.



Confirm the position marked A6.


1023 is displayed when no key is pressed.


327 is displayed when 'Dot' key is pressed.


Enter the 'dot' range in uBITX Manager.
Please refer to other documents for basic usage of uBITX Manager.




I made the range of values considerably smaller because I made the worst.
Your CW Key has a better contact point than a screwdriver, so you may want a larger range of values.


698 is displayed when 'Dot' key is pressed.


Input ADC Range for Dash Key


285 is displayed when 'Dot' and 'Dash' key is pressed.



Input ADC Range for both Key

Store the value in uBITX.



Reboot and test uBITX.



Test video


Comments

  1. This comment has been removed by the author.

    ReplyDelete
  2. Casino - Bracket betting guide for your chance to win
    The Casino is a unique casino that has been around for over a dental implants decade. It has managed to offer great games such https://septcasino.com/review/merit-casino/ as Blackjack, Roulette and Video gri-go.com Poker,

    ReplyDelete

Post a Comment

Popular posts from this blog

Introduction to UV-K5 HF Fullband receive version 0.3

Introduction to UV-K5 HF Fullband receive Version 0.3 This is an introduction to UV-K5 HF full-band reception firmware 0.3HF using SI4732-A10. This version is released separately from the existing UV-K5 CEC firmware version. because space is needed to store a large PATCH file to use SI4732-A10's SSB. 0.3HF added several functions to use SSB for shortwave radio and amateur radio.

Release CEC Firmware v1.200 for uBITX All version(include V2, V3, V4, V5)

Release CEC Firmware v1.200 for uBITX All Version (include v2, v3, v4, v5) I did the firmware work for v5 when uBITX V5 was released, but I release it now. I received the feedback from a thankful beta tester and tested it myself by converting my uBITX v3 to v5 but I was not sure. I ordered the uBITX V5 and delivered the correct uBITX V5, so I made a little more fine-tuning. If you use V2, V3, V4, you do not need to update this firmware.

Introducing UV-K5 Version 0.1P (CW)

  Introducing UV-K5 Version 0.1P (CW Mode) CW-related functions have been added to version 0.1P. The spectrum function has been removed but is maintained in the source code. Later, when the source code is distributed, you can activate it and use it if necessary. This version is for testing purposes only. It will be redistributed as the stable version 0.2 in approximately 1-2 weeks. If you don't want to beta test, you can wait a week or two and download 0.2