Skip to main content

CAT Support uBITX Firmware CEC Version 1.06 Release (Added WSPR)

uBITX Firmware CEC Version v1.06 (changed v1.061)

I deployed 1.06 and received feedback from WSPR's beta tester, Philip (G7JUR).
It was a problem that the LPF was not automatically selected according to band selection during WSPR transmission.

Version 1.08 has been released.
http://www.hamskey.com/2018/05/ubitx-firmware-cec-version-108-release.html

I modified it soon and changed uBITX Firmware CEC Version to 1.061.
uBITX Manager also changed Version to 1.01.

-----------------------------------------------------------------------------------

I released version 1.06 which added WSPR function to uBITX.
Beta testers have been very helpful when embedding WSPR functionality. WSPR will continue to improve in the future.

By using WSPR before and after QSO, you can check where your uBITX is spreading all over the world.  If uBITX Manager is used to put WSPR information into uBITX, uBITX no longer needs any external device to transmit WSPR.

The uBITX group's excellent tester also shared a way to use CW Beacon using the Autokey feature (Autokey is a memory keyer built into CEC Firmware.) I will test this later and post it separately.


Added or improved in version 1.06
The uBITX firmware has many built-in functions. Most of the features are described on this blog. If you look at uBITX usage on this blog, you can use it more and more fun.

Especially WSPR or AutoKey (renamed Memory Keyer from Version 1.06) will be quite fun and useful.

-------------------------------------------------------------
1.Added WSPR function to uBITX


You only need uBITX to use WSPR. No external devices are required.
Added second Si5351 control module for WSPR. I needed another control method to control the WSPR frequency.

See the link below for more information.
http://www.hamskey.com/2018/03/beta-testing-of-stand-alone-wspr.html
http://www.hamskey.com/2018/03/wspr-function-test-in-6m-2m-band-built.html
http://www.hamskey.com/2018/03/how-to-use-si5351-2-si5351-library-for.html

2.Update uBITX Manager to Version 1.0 -> Version 1.01
Built-in functions for WSPR.










The WSPR band has a choice of up to 2 meters. I think uBITX should be modified when using at over 50Mhz. Waiting for feedback from those who succeeded in 50Mhz or more. And if you want to test 2m band on uBITX, I will send you the test program that I used. This makes the Si5351's clock a little more stable.



3.Reduce program size
  - for WSPR
  - For display to be improved in the future
  - for other Module

4.Fixed IF Shift Bug
  - Disable IF Shift on TX
  - IF shift available in USB mode
  - Fixed cat routine in IF Shift setup


See the link below for more information.
http://www.hamskey.com/2018/03/test-and-explain-for-if-shift-function.html


5.fixed other bugs
  - cw start delay option
  - Auto key Bug
   (found bug : LZ1LDO)
  - Message selection when Auto Key is used in RIT mode
    (found bug : gerald)

6.Improve
  - CW Keying (start TX)

7.In CWL and CWU mode, it is possible to manage the use of two options which are displayed by shifting frequency.
CWL, CWU mode can be used more easily.
If you are in the CWL or CWU mode and you are using the function to shift the receive frequency, please check the option again in uBITX Manager.




8.Rename 'Auto Key' to 'Memory Keyer'

9.Even if the uBITX is powered off, the IF Shift setting value can be maintained.
If you use uBITX Manager 1.0 or later, you can select options as shown below.

If the 'Auto Save-IF Shift Value' option is selected, the IF Shift setting will continue to be maintained even if the uBITX power is turned off.

--------------------------------------------------------------
Please refer to the links below for explanations before 1.01
http://www.hamskey.com/2018/02/cat-support-ubitx-firmware-cec-version.html

Please refer to the links below for explanations before 1.04
http://www.hamskey.com/2018/03/cat-support-ubitx-firmware-cec-version.html


Please refer to the link below for how to install the firmware.
http://www.hamskey.com/2018/01/how-to-upgrade-ubitx-firmware.html


To download Hex file, uBITX Manager, source file, please click the link below.
https://github.com/phdlee/ubitx/releases

HEX File :
https://github.com/phdlee/ubitx/releases/download/v1.06/uBITX_CEC1.061.zip

uBITX Manager :
https://github.com/phdlee/ubitx/releases/download/v1.06/ubitx_Manager1.01.zip

The uBITX Firmware CEC version is open source and the source is in the link below.
You can see all the revision history by going to the link below.
https://github.com/phdlee/ubitx


Comments

  1. Replies
    1. Thank you for using this firmware.

      Ian KD8CEC

      Delete
  2. Hi Ian.

    I am afraid that the LPF selection problem is back with V1.06.
    Need to select the correct band before doing a WSPR beacon. The same as V1.05, before V1.051.

    Philip G7JUR

    ReplyDelete
    Replies
    1. Philip

      Thank you for important feed back
      Fixed a bug where the LPF does not change with the WSPR band. (Version is now 1.061)
      If you have time, please test this firmware.

      Ian KD8CEC

      Delete
    2. Hi Ian.

      Now working fine. Thanks for the quick fix.

      Philip G7JUR

      Delete
    3. Philip
      Thanks for test.
      I also updated uBITX Manager to 1.01. Several features have been added. Upgrade uBITX Manager as well.

      Ian KD8CEC

      Delete
  3. Tnx Ian
    Great
    A questions
    In the manager i see SMETER..?
    Great work tnx
    De
    In3fci

    ReplyDelete
    Replies
    1. Daniele

      It is reserved for those who want to install the S meter in uBITX later on.
      I will support S.Meter soon.

      Ian KD8CEC

      Delete
  4. Hi Ian, Please email me, I'd like to send you a RaduinoI2C board...
    Thanks
    Nik,.

    ReplyDelete
    Replies
    1. Thank you for your suggestion.
      But I live quite far away. I am quite interested in your project.
      I will test the RaduinoI2C board by hand.
      I have to buy an I2C LCD today.

      Really Thanks agian for your suggestion.

      Delete
  5. Hi Ian
    I tried the V1.061 yesterday with an Si5351 with crystal of 27mHz, after changing the settings for 27mHz xtal and compiling, no receive in this version. Version 1.04 works fine with 27mHz xtal.
    Not sure what the difference may be between 1.04 and 1.061
    Thanks Alan

    ReplyDelete
    Replies
    1. Alan,
      I love this custom uBITX, hope your uBITX will work again.
      Si5351 clock control module has changed.
      1. Added WSPR module.
         - But it does not seem to have much to do with your problem.

      2.BFO clock related (Clock1, Clock 0)
      - Modified the part that controls Clock0.

      I have an question. How did you edit the ubitx_Si5351.ino file?
      This is because there is a modification at the bottom of ubitx_si5351.

      If you keep ubitx_Si5351.ino as the original one, you may have problems.
      Check the function below.

      void SetCarrierFreq()
      {
      unsigned long appliedCarrier = ((cwMode == 0 ? usbCarrier : cwmCarrier) + (isIFShift && (inTx == 0) ? ifShiftValue : 0));
      si5351bx_setfreq(0, appliedCarrier);
      }

      void initOscillators(){
      //initialize the SI5351
      si5351bx_init();
      si5351bx_vcoa = (SI5351BX_XTAL * SI5351BX_MSA) + calibration; // apply the calibration correction factor
      SetCarrierFreq();
      }

      I do not have a si5351 control module that uses 27Mhz, but I think if you help, I can solve this problem.

      If you continue to have problems, please compress all the sources you compiled and send them to me.

      Ian KD8CEC

      Delete
    2. Hi Ian

      Well downloaded again from Github 1.061, changed as last time to 27mHz xtal, and all is well. All working fine, must not have compiled or uploaded correctly.
      Thank you for the excellent software, will look forward to the next update.
      Many thanks
      Alan

      Delete
    3. Congratulations on your uBITX with 27Mhz x-tal coming back to work.
      I am very good at having various uBITX.

      Delete
  6. Hi Ian
    today upload ver 1.061,working on FT8 with Ham radio delux cat and Wsjtx rc3,
    all working fine ,ptt work with cat also,
    but when I transmit cq or replay some station in FT8 mode ,when ubitx go to tx mode the USB mode automatically go to LSB mode,and then Rx also remain in LSB mode,If I test Ptt in CAT mode or press TX on HRD, its also go from USB to LSB, During this if I press mic PTT then no change mode remains same ,please help
    73 de VU2KYZ/Ashok

    ReplyDelete
    Replies
    1. Ashok

      I have not had such an issue yet, so I am very interested in this issue.
      1. I'm curious about your connection settings.
      There are things that I set up when I watch my videos. You can refer to it.

      2.I wonder if the problem always occurs or occurs occasionally.

      3.Please enable 'STOP TX' in the menu and try again. This function can be seen by activating 'Set on'.

      4.If you have dummy load, connect uBITX to dummy load.

      5.Try using a shielded USB cable.

      6.Install and try a previous version of my firmware (0.27)

      Just go through the tests you can try and let me know the results.
      If you follow this sequence, your problem may be solved.

      Ian KD8CEC

      Delete
  7. Thanks Ian
    Yes it's problem with my USB cable, i am using usb hub , just removed it and connected directly usb cable from ubitx to pc, works fine,
    Thanks again
    73 de Vu2kyz /Ashok

    ReplyDelete
    Replies
    1. Great.

      I have experienced some situations similar to you.
      I have solved the problem by using a shielded cable that came with the printer when I bought it.

      Ian KD8CEC

      Delete
  8. first time install of your software...got 1.061 installed but having a rough time with the calibration and BFO settings. Do you have a rough setting for the BFO ?? mine started at 12 mhz plus (should have marked the initial setting down somewhere). I was hearing plenty of signals on the USB setting but trying to get the calibration and BFO to slide over to LSB setting was impossible. Now I got it so messed up that its totally a deaf. If I got a ballpark value for the BFO I think I can get the calibration right.

    thanks Don

    ReplyDelete
  9. Don

    There have been several inquiries about calibration. And everyone was able to solve the problem.
    I felt the need to post an FAQ soon.This answer will be posted in the FAQ and will be a little more detailed. So I will divide it into several

    Do not worry about your radio.

    First, I will let you know.
    1. My firmware keeps the Master Calibration and BFO Calibration that you used. Even if my firmware is updated a number of times, the setting value will remain unchanged.
    This is also true of the original firmware.

    2.Master Calibration and BFO Calibration follow the original firmware method.
    You can use the same method as the original firmware.

    However, the original firmware starts from 11995000 when calibrate the BFO, but my firmware starts with the current BFO of the transceiver.
    This is at the request of many users. This is the only part of the original firmware that has been fixed in relation to Calibration.

    3.My firmware has the same calibration as the original firmware. However, if you are comfortable calibrating in the original firmware, you can reload the original firmware, calibrate and upload my firmware again.
    Again, my firmware retains the Calibration, BFO, etc. used in the original firmware.
    LS

    ReplyDelete
    Replies
    1. Second. How to calibration
      (This is the same in the original firmware)

      1.I recommend you do BFO Calibration first.
      2.Reset the power of uBITX and reboot.
      3.Rotate the dial to set where the people are QSO (Frequency does not matter)
      4.Setup On? -> Enter the BFO Calibration menu.
      5.Fit in the place where people's voices are best heard.
      -Find a similar place to the SSB reception you experienced
      -It will probably be between 11996000 and 11997000.
      - For reference, I use 11996500.
      - The exact value of this depends on the radio.
      - If it is less than 11996000, the LSB and USB may be heard in reverse.
      - This method is repeated several times (from 1) to set the BFO.
      - When you are satisfied with both LSB communication and USB communication, please end the BFO calibration.

      6.If you set the BFO, Check your frequency display.
      Many cases do not indicate the correct frequency.
      If your frequency is correct, finish all calibration.

      Delete
    2. 7.Master Calibration (Your frequency is showing a wrong frequency)
      - You have to choose one that is at a relatively precise frequency, such as QSO, Beacon, Digital communication.
      I usually use 14.074 000 or 7.074 000 (FT8) which is always received.

      - Perhaps your radio should be tuned slightly below or above the originally known frequency so that the frequency you know will be received.
      For example, FT8 is communicating at 14.074, but I am receiving at 14.072.

      -Turn the dial to set the frequency you know.
      For example, FT8 is communicating at 14.074, but I am receiving at 14.072.
      Set frequency of uBITX to 14.074

      - Enter Master Calibration. (Setup On? -> Set Calibration)

      - Master Calibration always starts from 0.
      - Turn the dial to find where you hear the QSO.
      - For reference, I heard a sound when the Master Calibration value was 16.
      - Important : As Master Calibration increases, BFO also increases.
      Ignore the sound is getting smaller or larger, etc. Please confirm that you can hear the QSO.

      - Press PTT to end Master Calibration.
      - Important2 : Be sure to turn the uBITX off and then on.
      (Because now your BFO will be wrong. When you reboot, you will return to the original BFO.
      I'm guessing that this is because the original firmware was trying to calibrate at the factory.)

      Delete
    3. 8. How to calibrate more easily
      - Please use uBITX Manager to directly input the calibration value and reboot uBITX.
      - uBITX Manager allows you to back up your calibration values.

      9.Most of the uBITX firmware I know maintains the Master Calibration area.
      But sometimes it is wrong to use the firmware that does not maintain the Master Calibration area, or if the wrong firmware (such as another radio or Memory Keyer for uBITX) is uploaded.
      In this case, the calibration value will be deleted or has wrong values.

      To prevent this situation, if uBITX is installed and you uploaded my firmware, make a backup of the configuration file. How to backup the calibration values with uBITX Manager is on my blog or YouTube.

      10.Please email me anytime. I can not always check my mail and blog, but I will tell you my experience later.

      Ian KD8CEC

      Delete
    4. thanks so much Ian.....will try this in the morning

      73 Don KC1AT

      Delete
  10. looks like that BFO setting fixed my problem. Don't know why the BFO started at 12mhz. Should have got my electric drill rigged up to get the freq down to around 11996500. I can fool around with it today and get the frequency calibration correct.

    thanks again for the quick response.....love the software...especially the Manager program.

    73 Don KC1AT

    ReplyDelete
    Replies
    1. Don
      The story of your electric drill was so much fun.
      The Step to Tune the BFO has been reduced in size by the request of quite a few users of the uBITX Group (Forum). That made you need an electric drill.

      With uBITX Manager, you no longer need drill.

      Ian KD8CEC

      Delete
  11. I've been tinkering with your firmware a little and came up with a working version with a Teensy 3.5 and I2C 20x4 LCD.
    Teensy allows a faster processor with vastly superior memory, SD card support and many more ports.

    All of your basic functionality is unchanged.

    I forked your code at github /mosteveo/ubitx

    ReplyDelete
    Replies
    1. Excellent!!!

      I am not really familiar with Arduino. This was the first time I used it.
      I originally work with ARM, especially Motorola MCUs are very familiar. Many friends I met at Bitx group recommended Teensy. I am so glad that you did it.
      I am going to make the UI part separate for easy to support various LCD.
      I will notify you of it.
      If you get a chance later, please introduce photos or Teensy mounting circuit.
      Thank you for your efforts.

      Ian KD8CEC

      Delete
  12. Ian for WSPR timing why not use DS3231 i2c module if some code space is left. Alexander RA9YER has built WSPR tx using si5351 + ds3231 and arduino. I had built it and works very well. Your uBITX manager can be used to sync RTC for first time.

    This is just a suggestion, appreciate your work.

    Thanks
    Max VU2IIA

    ReplyDelete
  13. Max
    Thanks for information.
    I also saw Alexander's great code. It's one of the codes I've studied WSPR.
    Until now, it was a concept that does not modify hardware as much as possible.
    Soon I will be preparing a hardware Modification version (so I can choose as an option)
    Now it is time for us to consider these things.

    Thanks for the feedback.

    Ian KD8CEC

    ReplyDelete
  14. Ian,

    I have converted to using an I2C display using a RadI2Cuno board. The software available is limited and doesn't provide the functionality yours does.

    Do you have an estimate on when you will put out an I2C version?

    There is also some functionality that I don't plan to use such as split operation and wspr. Is there an easy way to recompile your software without these so it comes out smaller?

    Thanks,

    tim ab0wr

    ReplyDelete
    Replies
    1. Tim
      I am ordering an I2C LCD and waiting.
      Version 1.07 has prepared for various LCDs.
      And if you want to exclude features because of the size of the firmware, you can have up to 10% free space depending on the compilation options in Version 1.07.

      Version 1.07 I will go through some more tests and post related articles.

      And I am interested in the Radi2Cuno board. I will buy it when it is released.
      Thank you for your interest.

      Delete
  15. I just loaded your 1.061. Thank you. It seems to work well. I am having problems getting the audio from the ubitx to fldigi The frequency adjust works and it will transmit show the signal on the waterfall and just stop scrolling. Cant get it to work with winlink too. Suggestions?

    ReplyDelete

Post a Comment

Popular posts from this blog

How to upgrade uBITX Firmware

uBITX is based on Arduino Nano. So uBITX's firmware upgrade method is the same as Arduino.
There are two ways to upgrade the firmware of uBITX.

The first is to compile the source from the Arduino IDE, and the second is to upload the compiled hex file using the Firmware Upgrade Tool.

I'll show you how to upload a compiled hex file as a second method.

1.Connect the uBITX's USB cable to the computer.


2.Run Device Manager on your computer.
  The way to open the Device Manager for each OS Version differs slightly.
  In most Windows, you can easily launch the Device Manager by running.

  On your computer, press the Windows key + R.



 Type devmgmt.msc and press OK Button.




On most operating systems, there will be a serial port named Ports with CH340. If so, the next step is skipped.

If the serial port is not installed as below, you need to install the driver.



Included in uBITX is the Adonano, which uses the CH340 USB To UART part.

Download the latest CH340 driver from the Internet.

CAT Support uBITX Firmware CEC Version 1.01 Release(Changed from v1.0)

CAT Support uBITX Firmware CEC Version 1.01  Release (Changed from v1.0)

uBITX Firmware CEC Version 1.06 has been released.
Please click the link below.
http://www.hamskey.com/2018/03/cat-support-ubitx-firmware-cec-version_24.html

This version of the concept is an upgrade without hardware modifications. No hardware modifications are required to use this firmware. Continuous release and testing has been done in the uBITX group. I tried to put only the basic functions that an HF transceiver should have. The features have been upgraded with the advice of people who have great ideas in the uBITX group.
It was a project that started to contribute to the original source in github. The project was intended to fix some simple bugs and request merge to the original source. And I was planning to delete the project. At the beginning of the project there was a bit of discussion about this in the uBITX group.
Since then, I've keeping the original source type to allow code share with any user fork…