Skip to main content

Introducing uBITX's Invalid Calibration Symptoms and Recovery Mode

Introducing uBITX's Invalid Calibration Symptoms and Recovery Mode

uBITX CEC Firmware supports recovery mode from version 1.075
Of course, we have been using uBITX Manager to back up uBITX's settings so far.
I think this is the best way.




But I have to consider users who can not use uBITX Manager. It is available on Windows and Linux, but it has not yet been verified on the MAC.

I also had to consider users using Stock Firmware. Even if you want to keep using Stock Firmware, upload CEC Firmware only once. Then upload the Stock Firmware again and use it. However, I highly recommend using the backup function of uBITX Manager.
I create various backup files and upload them as needed.
Finally, I have also considered users who use CEC Firmware but have not yet used the backup feature.


1.Introduction to Factory Recovery
uBITX does not have Factory Recovery mode.

uBITX has 0 to 1023 EEProm storage space. but uBITX Stock Firmware uses only addresses from 0 to 31, 32 to 1023 are not used.

I implemented the Factory Recovery function using the unused area of the EEProm.
CEC Firmeare (Version 1.075 or later) is uploaded to uBITX and checked whether the configuration value is backed up when it is executed for the first time.
If it has not been backed up, copied the data in addresses 0-31 of EEProm to 65-92 of EEProm. Once it is backed up, it will not be backed up anymore. Updating the firmware will not restart the backup.

If you purchased uBITX and uploaded the CEC Firmware without performing any calibration, your factory configuration will be safely stored at addresses 65-92. Congratulations You have a true Factory Reset function.

For users who have performed the calibration, the current status is backed up to the factory default.

if you have a problem with your uBITX with the wrong settings, you can do Factory Reset using the data that was automatically backed up.

2.User Preparations
Nothing.
You just upload the CEC Firmware. As soon as the CEC Firmware is executed, your uBITX critical information is copied to a safe location.

3.How to Recovery
The recovery procedure is a bit tricky. It is to prevent uBITX from being factory reset due to accidental switch press.
There are two ways to do Factory Recovery.

3.1 Using Factory Recovery with uBITX alone
  - Power off uBITX.

  - While pressing the Function Switch, turn on the uBITX.

  - You will see the article 'FactoryRecovery'. 
  Hold down the switch and wait.
  If you release switch, the Factory Recovery mode is canceled.

- You will see the article 'IF you continue release the key'. 
  When this letter appears, release the switch.
  This letter is displayed for 2 seconds and factory reset mode is canceled if the switch is not released for 2 seconds.

- You will see the article 'IF you continue Press Key PTT'.  (I misspelled the letters. Will be fixed soon)
  When this letter appears, press the PTT.

  
- Finally, You will see the article 'IF you continue Power Reset'

If uBITX is rebooted, your uBITX will return to normal.


3.2 How to recover using uBITX Manager
  - Run uBITX Manager.
  - Connect -> Read -> Decode
  - Press the 'Load Factory Setting'

  - Encode -> Write

  - If uBITX is rebooted, your uBITX will return to normal.

 But if you can use uBITX Manager rather than this, please use the backup function of uBITX Manager.

Below is an video of uBITX's recovery mode experiment.
I deliberately set the wrong calibration on uBITX.
You can see the symptoms when the BFO is wrong in the video below and the calibration is wrong.

If your uBITX shows any of the following symptoms, suspect the BFO and Calibration.



4. Conclusion
However, I highly recommend using the backup function of uBITX Manager. 
I create various backup files and upload them as needed.
If you are already using uBITX Manager, please use Save to File function.
Simply press the Save to File button and your uBITX will be backed up safely.
The Factory Recovery function is used when uBITX Manager is not available or when there is no backup data.

Very simple
















Comments

  1. Hello Ian,
    just tried the nextion NX3224T028_011R display. Unfortunately, the
    2.8" file uploaded to the memory card only gives an error message.

    Regards
    Roger

    ReplyDelete
    Replies
    1. Have you formatted you SD card with "FAT32" file system? And is this card not bigger than 4GB?

      Delete
  2. Is there any hope of restoring defaults for those of us who mucked about with our uBitx before installing the CEC firmware?

    ReplyDelete
  3. Is there any new version of the ubitx manager? My Version is the 0.97 and ther is no "Load Factory Defaults" button. If so, wher can I download the newer Version?

    ReplyDelete
    Replies
    1. my Name is Mathias and my e-mail ist dj9md(at)web(dot)de

      Delete

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