Skip to main content

WSPR function test in 6M, 2M band built in uBITX - update 20/3

WSPR function test in 6M, 2M band built in uBITX


The picture below is example for the results of transmitting WSPR by uBITX stand alone. Thanks beta testers.


Various WSPR tests are underway in preparation for the release of 'uBITX Firmware KD8CEC Version 1.06'.
The uBITX KD8CEC firmware is based on the concept that it can be used without modification or additional devices.

However, this version can be used without modification, but modifying the filter section will improve performance.




All tests were carried out with dummy loads and laboratory equipment in the laboratory.
Filter modifications are required at 6M (50Mhz) and above. In addition, the higher the frequency, the more accurate the calibration is required.
(I was able to adjust the calibration more precisely as a result of viewing the WSPR transmission results)
I did the test without modification the filter. (6m, 2m)

This post does not explain the basic usage of WSPR built into uBITX.
Click the link below for basic instructions for using WSPR of uBITX.
http://www.hamskey.com/2018/03/beta-testing-of-stand-alone-wspr.html

I have found through my WSPR transmission several times that the exact calibration of my uBITX is 140800.


In this uBITX Firmware CEC Version, we tried to support only 28Mhz with WSPR function.

The WSPR protocol I implemented uses only Clock2 of uBITX, so We only need to modify the TX filter part.
The uBITX Manager to be released this time includes 6m, 4m, 2m.









Sent WSPR in 6m band without any filter modification.
(using Dummy load and RF-Gain controller)



The 6m band succeeded in all the WSPR transmissions in a few tests. Below is an image that was sent from uBITX to WSPR and received from FT-857.


I tried the test at 2m.


The transmitted frequency is unstable as shown below. I will be trying some 2m band tests.
And when we release this uBITX firmware, I will consider whether to leave 2m band.



At 2m Band, we occasionally succeeded in sending WSPR, but there were many failures. I will look for the cause.

The video below is an experimental image of WSPR embedded in uBITX. 6m succeeded to send but 2m failed.

I will be several more experiments on the 2m band. I will add the experimental results below this post.

The figure below shows an unstable frequency graph for 15 seconds after the clock is generated.

With the exception of 2M in uBITX, all WSPR transmission tests were successful. I tried it in various ways, but the probability of failure was higher than success.

I found that the oscillation starts at the WSPR transmit frequency and stabilizes after about 10 seconds.

So I made a WSPR ready state in the RX state and then I chose to send the WSPR.
The graph was somewhat stable when viewed with Spectrum analyzer or Wsjt-x, but it was not transmitted in the 2M band either.

So, this time, I entered the same algorithm in the Si5351 module and sent it.



The Si5351 module has been successful, but I think it will be difficult to use it in the 2M band in the future.




Ian KD8CEC

Comments

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.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 …

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…