Skip to main content

Using memory channels in uBITX (Storing / recalling frequencies / naming channels)

Using memory channels in uBITX
Storing / recalling frequencies / naming channels in uBITX

This function is supported in uBITX Firmware CEC Version 1.0 or later.



At the bottom of this document is a video shot while creating the manual.

1.Storing Frequency and mode
  - Turn the dial to set the desired frequency.


 - Press the Function Key


- Turn the dial until 'VFO To Channel' Appears



- Press the function key
The channel will be visible.
If you are using this function for the first time, you will see an empty frequency like 'CH01:'.


- Rotate the DIAL until the desired channel appears.



- Press the Function key
'Saved Frequency' message appears and hide


- The current frequency has been saved with the mode you chose.




2.Naming Channel
  This feature is to give the channel a name.
  You can only use the Name tag from channel 1 to channel 10.

- Execute uBITX Manager , Set Comport, baud, stopbit, data bit, parity and Press the Connect button


- Press the Read Button


- Press the Decode Button


- Scroll Down, You will see the User Channel Configuration section.


- You can check the frequency stored in # 1 above.


-Enter a name for each channel. (the channel you want)


- Check 'Name' Check Box.
  Only checked channels are displayed by name.



- Press the Encode Button



- Press the Write to uBITX Button


- The addresses that need to be saved are shown below.
  Press the Write Button


-


-Press the Close button

the channel was given the name you defined.


3.Load Frequency with mode
- Press the Function Key


- Turn the dial until 'Channel to VFO?' Appears


-Press the Function Key
You will see the name, not the channel number.







-Channels without a name tag are channel number appears.

- Select the channel to load with VFO.


- Press the Function Key
The channel frequency will be loaded into the VFO.


Click on the link below to watch videos related to channel control.





Comments

  1. How many channels can you add? Even a few will be fine though.

    ReplyDelete
  2. Replies
    1. Todop

      and 10 without names.
      Increasing the channel is not a problem.
      You only need to change the number to increase the channel. n order to use the eeprom efficiently, I decided to set it to about 20.

      Ian KD8CEC

      Delete
  3. There are numerous reasons why why} a web-based casino would refuse to pay a player. In this article, you'll learn all about that, and the steps to take to get your money from them. That said, 포커 we gave the next ranking to gambling websites that present the most versatile range of banking choices alongside the fastest payout speeds. For many, the most important priority is the standard as well as|in addition to} quantity of the video games obtainable.

    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