Date   
Re: Manual to set up uBitx Ver 6

Ashhar Farhan
 

The tune up manual is coming up.
- f

On Sun 15 Dec, 2019, 8:38 PM GM4CID, <gm4cid@...> wrote:
Paul,

Does this perhaps answer your question ?

http://www.hfsignals.com/index.php/ubitx-v6-assembling-the-full-kit/

73 Bob GM4CID

Re: Manual to set up uBitx Ver 6

GM4CID
 

Paul,

Does this perhaps answer your question ?

http://www.hfsignals.com/index.php/ubitx-v6-assembling-the-full-kit/

73 Bob GM4CID

Re: Let's Minimize the Library problems.

Jack, W8TEE
 

Tom:

I think you mean the tool chain developed by Roger Clark for the STM32. Most of Paul's work is dedicated to the Teensy family, which his company developed. Paul's Teensy 4.0 (aka T4) is a real game-changer.  Our book's DSP project does a real time FFT plot of the audio signal so you can see the impact of your DSP changes in real time. You can't do that without having a fast processor (e.g., the 600MHz clock of the T4).

The key to working with any graphics library is to make sure your display has the right video driver chip to match the library. If more people understood that, or if us programmers were more careful to use download URL's for the correct library in the code, there would be a lot less bandwidth used here. This is taken from the JackAl header file:

#include <Arduino.h>          // Standard with IDE
#include <EEPROM.h>           // EEPROM distributed with Teensy libraries
#include <math.h>             // Standard with IDE
#include <Wire.h>             // Standard with IDE
#include <SPI.h>              // Standard with IDE
#include <stdio.h>            // Standard with IDE

#include <OpenAudio_ArduinoLibrary.h> // http://hamradiodesigns.com/index.php/content/
#include <Adafruit_GFX.h>     // Now supplied with Teensy Library install
#include <Audio.h>            // Now supplied with Teensy Library install
#include <RA8875.h>           // http://hamradiodesigns.com/index.php/content/
#include <Rotary.h>           // https://github.com/brianlow/Rotary
#include <SerialFlash.h>      // Now supplied with Teensy Library install
#include <Time.h>             // Now supplied with Teensy Library install
#include <TimeLib.h>          // Now supplied with Teensy Library install
#include <TimerOne.h>         // Now supplied with Teensy Library install
#include <UTFT.h>             // Now supplied with Teensy Library install
#include <URTouch.h>          // http://www.rinkydinkelectronics.com/library.php?id=92
#include <UTFT_Buttons.h>     // http://www.rinkydinkelectronics.com/library.php?id=61

As you can see, it is not hard to do and it makes it unequivocal which library to use.

Jack, W8TEE

P.S. Now that the book's done, Al and I are going to resurrect our hamradiodesigns web site. It's been hacked, so don't go there now. For the moment, most of the files have been moved to my softwarecontrolledhamradio web site.

On Saturday, December 14, 2019, 11:44:11 PM EST, Tom, wb6b <wb6b@...> wrote:


Perhaps the biggest problem with STM32F103 Blue Pill development on the Arduino platform is there are two competing tool chains, the original "Paul Stoffregen" toolchain and the "official" STM32 tool chain endorsed by STM. I would prefer the official STM32 toolchain, but most Arduino Blue Pill projects seem to have been developed with the Paul Stoffregen version, so I use it. 

Another big issue I've found, for example with the graphics/touchscreen libraries, is several libraries such as the Adafruit graphic libraries need to work together with the lower level display module drivers for the TFT and touchscreen hardware. 

Library writers upgrade and enhance their libraries and no regression tests are (or can be) done on other libraries compatibilities, especially the non-mainstream libraries like those for the Blue Pill. And writers of the STM32 libraries may not be maintaining their libraries anymore, so they don't get updated. 

For what ever reason, the ESP32 toolchain developers have been doing a much better job in keeping their libraries updated to reflect changes in other libraries they are dependent on.

In an example of trying to get a touchscreen display working on a Blue Pill, AdaFruit updated one of the screen attributes from one parameters to two. (I've forgotten which one, but they changed the X and Y parameters [possibility a dot size value] to be separately specified, rather than the X and Y values being equal.) There was no backwards compatibility so the STM32 touchscreen libraries no longer worked. The change was done in a way that adding simple wrappers, still required culling through the AdaFruit code to correct numerous instances in the code. (There were still other issues with the hardware assumptions around interrupts and SPI ports, that clashed in the latest libraries, but may not have in older libraries when the STM32 toolchains were first introduced, years earlier)

Unlike the ESP32 toolchain, the STM32 toolchain(s) seemed to get off to a bad start, along with libraries breaking over time as other libraries are updated, generating confusion and trouble it so far has not recovered from. Then adding two toolchains to top the confusion off. 

For many simpler projects, these issues are less troublesome and the Arduino platform is still simple fun to use.

Finally, I don't bother with putting boot loaders on the Blue Pills. I either flash the program with the serial boot loader built into the chip, with a USB to serial adaptor, or use one of the inexpensive ST-Link adaptor clones from eBay. Although I might try the various boot loaders out at some future point. I can see for something like the uBitx installing a USB boot loader would be the best way to go for usability. 

Whichever toolchain you use, as Jack pointed out, let people know where the actual source location of library you used can be found.  As, many libraries have more than one version and authors.

Tom, wb6b

--
Jack, W8TEE

Re: V4 TX problems and new finals #ubitx-help

Bob Fischer, Fischer Technical Services
 


Thanks to Don, KM4UDX for, very eloquently, stating the opinion many of us have about the uBITX Community.
Better "customer service" than I have ever received from an original equipment manufacturer.  And I have been a Ham for over 50 years.
Bob
WB8BEL


From: "Don - KM4UDX" <dontAy155@...>
To: BITX20@groups.io
Sent: Sunday, December 15, 2019 1:14:35 AM
Subject: Re: [BITX20] V4 TX problems and new finals #ubitx-help

Evan, Mark, Raj, Anthony, & Co.

What is marveling about this lovely radio is its resilienance to stupidity.

What is marveling about this community is how unbelievably kind, helpful, generous and talented you people are.

How many times did I turn the bias pots the wrong way? Counter what? And the driver adjustment does what which way?  Why does the uBITX go dark and reset when my DVM probe slips and shorts the  IRF510 pins?  Which pin is the gate (again?)?  Why does my uBITX go all Chernobyl when I put 2Ov on the PA brown wire and fail to notice that I'm stuck in TX  WSPR digital mode 100% duty cycle for 10 minutes with way too much drive?

Why didn't I study electronics in school? Okay there were way more girls in English class, but still...it would be sort of useful around now...

I have to draw little cute diagrams of transistors and label them because I can never remember what lead is what. I feel like a first grader learning how to tie their shoes. 

If I set the bias current drain, then the voltage on the gate can't be zero.  Ah....so there is an error here...wait...is this that well meaning dope Don?  Good grief, he  can't get him out the door if you pushed him -- electrically. Hahah.

And I always feared that my problem (s?) are due to "operator error". I seem to have lots of that. Hahaha. 
 
uBITX  is just humility spelled backwards.  It is sooooo much better and smarter than I am.  But, that makes it really fruitful to study and poke and add to. 

I'll get back to Lab Class and report out on the "Rs" and the "TPs" and the counter clock wise what? Hahah.

Thanks a hundred million.

Don



ubitx V5 assembled + battery + accessories to sell

Adrien F4IJA
 

Hi all,

I've bought a V5 board some months ago, I assembled it in a custom case with a good battery pack, connectors, etc etc.

I've well set up the frequency calibration (see there : https://www.tobeca.fr/f4ija/doku.php?id=ubitx:calibration)

But now I need to calibrate finely the BFO and I really have no time (we bought a house and I've a company to run...)
Instead of leaving this board unused I'd like to sell it to someone who wants a fresh start with an already assembled board.

The setup is working as I was able to make some contacts with WSPR and also FT8 but I really have no time to go further for now.

I propose the complete system with :

V5 board with stock LCD screen
the battery pack
the whole box (3d printed and CNC milled for the plates)
the connectors, etc etc.
the battery pack charger

You can see the project and the build here : https://groups.io/g/BITX20/topic/project_ubitx_go_box_with/33030891?p=,,,20,0,0,0::recentpostdate%2Fsticky,,,20,2,0,33030891

https://www.tobeca.fr/f4ija/doku.php?id=start

I propose 200€ for this + shipping depending on where you are.
The price can be negociable, just please be honest and respectful.

Looking forward for your contacts !

--
73's
Adrien F4IJA
https://www.qrz.com/db/F4IJA

Re: Let's Minimize the Library problems.

Tom, wb6b
 

On Sat, Dec 14, 2019 at 10:09 PM, Ashhar Farhan wrote:
I have moved on to using nothing except the standard arduino libraries.
Hi Farhan,

I was just reading the post you did elsewhere and was impressed at the work you did to accomplish the user interface with such minimal resources. For the uBitx that is fantastic as it allows the folks that are building it to learn, to also delve into the software world without all the pain of using less stable toolchains and libraries. Cost is also important for your uBitx to have the reach of users around the world it is enjoying. So the path you went down is great. I'm definitely interested in looking at the code you wrote for creating the minimal resources needed user interface. 

Tom, wb6b

Re: V4 TX problems and new finals #ubitx-help

Don - KM4UDX
 

Evan, Mark, Raj, Anthony, & Co.

What is marveling about this lovely radio is its resilienance to stupidity.

What is marveling about this community is how unbelievably kind, helpful, generous and talented you people are.

How many times did I turn the bias pots the wrong way? Counter what? And the driver adjustment does what which way?  Why does the uBITX go dark and reset when my DVM probe slips and shorts the  IRF510 pins?  Which pin is the gate (again?)?  Why does my uBITX go all Chernobyl when I put 2Ov on the PA brown wire and fail to notice that I'm stuck in TX  WSPR digital mode 100% duty cycle for 10 minutes with way too much drive?

Why didn't I study electronics in school? Okay there were way more girls in English class, but still...it would be sort of useful around now...

I have to draw little cute diagrams of transistors and label them because I can never remember what lead is what. I feel like a first grader learning how to tie their shoes. 

If I set the bias current drain, then the voltage on the gate can't be zero.  Ah....so there is an error here...wait...is this that well meaning dope Don?  Good grief, he  can't get him out the door if you pushed him -- electrically. Hahah.

And I always feared that my problem (s?) are due to "operator error". I seem to have lots of that. Hahaha. 
 
uBITX  is just humility spelled backwards.  It is sooooo much better and smarter than I am.  But, that makes it really fruitful to study and poke and add to. 

I'll get back to Lab Class and report out on the "Rs" and the "TPs" and the counter clock wise what? Hahah.

Thanks a hundred million.

Don


Re: Let's Minimize the Library problems.

Ashhar Farhan
 

Tom,
I have moved on to using nothing except the standard arduino libraries. The current build is dependent only in the i2c and spi libraries. I am going bare metal on the touch library as well. I will oush the touch and display code into one file that you can rewrite for every display.
- f

On Sun 15 Dec, 2019, 10:14 AM Tom, wb6b, <wb6b@...> wrote:
Perhaps the biggest problem with STM32F103 Blue Pill development on the Arduino platform is there are two competing tool chains, the original "Paul Stoffregen" toolchain and the "official" STM32 tool chain endorsed by STM. I would prefer the official STM32 toolchain, but most Arduino Blue Pill projects seem to have been developed with the Paul Stoffregen version, so I use it. 

Another big issue I've found, for example with the graphics/touchscreen libraries, is several libraries such as the Adafruit graphic libraries need to work together with the lower level display module drivers for the TFT and touchscreen hardware. 

Library writers upgrade and enhance their libraries and no regression tests are (or can be) done on other libraries compatibilities, especially the non-mainstream libraries like those for the Blue Pill. And writers of the STM32 libraries may not be maintaining their libraries anymore, so they don't get updated. 

For what ever reason, the ESP32 toolchain developers have been doing a much better job in keeping their libraries updated to reflect changes in other libraries they are dependent on.

In an example of trying to get a touchscreen display working on a Blue Pill, AdaFruit updated one of the screen attributes from one parameters to two. (I've forgotten which one, but they changed the X and Y parameters [possibility a dot size value] to be separately specified, rather than the X and Y values being equal.) There was no backwards compatibility so the STM32 touchscreen libraries no longer worked. The change was done in a way that adding simple wrappers, still required culling through the AdaFruit code to correct numerous instances in the code. (There were still other issues with the hardware assumptions around interrupts and SPI ports, that clashed in the latest libraries, but may not have in older libraries when the STM32 toolchains were first introduced, years earlier)

Unlike the ESP32 toolchain, the STM32 toolchain(s) seemed to get off to a bad start, along with libraries breaking over time as other libraries are updated, generating confusion and trouble it so far has not recovered from. Then adding two toolchains to top the confusion off. 

For many simpler projects, these issues are less troublesome and the Arduino platform is still simple fun to use.

Finally, I don't bother with putting boot loaders on the Blue Pills. I either flash the program with the serial boot loader built into the chip, with a USB to serial adaptor, or use one of the inexpensive ST-Link adaptor clones from eBay. Although I might try the various boot loaders out at some future point. I can see for something like the uBitx installing a USB boot loader would be the best way to go for usability. 

Whichever toolchain you use, as Jack pointed out, let people know where the actual source location of library you used can be found.  As, many libraries have more than one version and authors.

Tom, wb6b

Re: V4 TX problems and new finals #ubitx-help

Evan Hand
 

Don,

The initial post states that you were able to follow the bias adjustment procedure correct?  And that you were able to adjust the bias resistors to get 100 ma increase for each IRF510.  That should pretty much eliminate them, the bias and connections through to the PA power supply.  

You have checked the other driver transistors and they seem to checkout as well.

At this point I would remove power from the rig
Look at R97 and R98 to verify that they are not open. 
Verify that TP7 is at ground to check the output coil on the output tranformere. 
Then without any power, verify that there is continuity from TP7 to TP8, followed by applying power to ONLY the main board (Red wire) and not the PA (Brown wire). 
Then select each band and verify connection from TP7 to TP8 with the key or PTT pressed. 

This is to verify that all of the relays are working, and that the inductors are not open.

That is the extent of what I can think of to test without an RF probe or oscilloscope.

There are RF probes that can be made with a few components.  Check out this web link:
http://n5ese.com/rfprobe1.htm

Let us know if the continuity checks play out.

73
Evan
AC9TU

Re: bitx v6 is here

Buddy Brannan
 

Oh wow…thanks Farhan! That’s pretty useful information to have. I think that putting keypad control together will be useful still, especially for direct frequency entry, but glad to hear that all functions can still be activated without the touch screen. With morse output, it really could be used eyes-free. Great news, and I’ll pass it on.

Vy 73,


Buddy Brannan, KB5ELV - Erie, PA
Email: buddy@...
Mobile: (814) 431-0962

On Dec 14, 2019, at 9:44 PM, Ashhar Farhan <farhanbox@...> wrote:

Buddy,
All the user interface is usable without needing touch. If you tap on the tuning knob for a second, you can move the focus from one button to the next and then click in the button to select again. Each button has text associated with it that can be read out. I have taken care to see to it that all features are accessible with and without touch. For example, the ability to enter a new frequency using the touch pad is replicated in fast tune where if you hold down the button while on one of the vfos , you can now quickly move across the bands in 50 khz steps.

Jack,
The function names are confusing as well..many variables are declared and not used any more. There is a large amount of code that is commented out as well. I have to clean that up, refactor reassemble. I will hopefully do this after Christmas.
The graphics library should really be called just a user interface library. The ILI9341 uses a SPI interface where it can fill a rectangle with a 16-bit colour. I used this to draw vertical lines, horizontal lines and pixels. No other graphical primitives have been used. The text characters are plotted pixel by pixel. The entire graphics routines are less than 100 lines. An often reused routine is the drawText routine that draws text centered inside a rectangle with a border. That makes all the buttons trivial. Almost all the user interface is just buttons, very much inspired by the jackal.
While tuning, i observed that only one digit if the frequency read out changes most of the time. So, the displayVFO routines figures which digits need to be repainted and updates only those. This routine is probably what makes the interface usable with the 8 bit power of the Arduino Nano.

- f

On Sun 15 Dec, 2019, 5:43 AM Buddy Brannan, <buddy@...> wrote:
Ooh…a thing that reads the screen in morse? That’s half the battle toward eyes-free operation. The other half, of course, is some additional way to control besides the built-in touch screen interface, like a programmable keypad. Seems to me there were a couple of implementations of this floating around. Do please elaborate.


Buddy Brannan, KB5ELV - Erie, PA
Email: buddy@...
Mobile: (814) 431-0962



On Dec 14, 2019, at 12:38 PM, Ashhar Farhan <farhanbox@...> wrote:

By morse reader, I actually meant software that reads out the screen in morse code.
I had fooled around with many morse decoders. Nothing really works on the bands. CW skimmer is the only thing that works under contest conditions.
So, if you want a morse code decoder that really works well, can adapt to any radio and needs no special hardware, then, spend a month, 20 minutes a day and practice at 30 wpm.
- f

On Sat 14 Dec, 2019, 9:56 PM splat1956, <dnrabin7@...> wrote:
Hi
This is very exciting. I have been thinking a long time but have not purchased one because I was afraid that the soldering and wiring instructions would be confusing. There have been many posts by confused builders.

This sounds great. Is there a morse code decoder built in or coming soon ? Your earlier post said " I have added a morse reader already. I shall finish integration to the user interface soon."
Please let us know when that is incorporated. I am unlikely to upgrade the software-firmware once it is working and that would be a very nice feature.

Great idea on the calibration with a known station signal for people without test equipment.

Thank you very much for this great upgrade !

David W9PH





Re: V4 TX problems and new finals #ubitx-help

 

Hmm,

A counterfeit could be 0V at its "gate" though. Did you ever track down the source of the new finals?

73


Mark

Re: Let's Minimize the Library problems.

Tom, wb6b
 

Perhaps the biggest problem with STM32F103 Blue Pill development on the Arduino platform is there are two competing tool chains, the original "Paul Stoffregen" toolchain and the "official" STM32 tool chain endorsed by STM. I would prefer the official STM32 toolchain, but most Arduino Blue Pill projects seem to have been developed with the Paul Stoffregen version, so I use it. 

Another big issue I've found, for example with the graphics/touchscreen libraries, is several libraries such as the Adafruit graphic libraries need to work together with the lower level display module drivers for the TFT and touchscreen hardware. 

Library writers upgrade and enhance their libraries and no regression tests are (or can be) done on other libraries compatibilities, especially the non-mainstream libraries like those for the Blue Pill. And writers of the STM32 libraries may not be maintaining their libraries anymore, so they don't get updated. 

For what ever reason, the ESP32 toolchain developers have been doing a much better job in keeping their libraries updated to reflect changes in other libraries they are dependent on.

In an example of trying to get a touchscreen display working on a Blue Pill, AdaFruit updated one of the screen attributes from one parameters to two. (I've forgotten which one, but they changed the X and Y parameters [possibility a dot size value] to be separately specified, rather than the X and Y values being equal.) There was no backwards compatibility so the STM32 touchscreen libraries no longer worked. The change was done in a way that adding simple wrappers, still required culling through the AdaFruit code to correct numerous instances in the code. (There were still other issues with the hardware assumptions around interrupts and SPI ports, that clashed in the latest libraries, but may not have in older libraries when the STM32 toolchains were first introduced, years earlier)

Unlike the ESP32 toolchain, the STM32 toolchain(s) seemed to get off to a bad start, along with libraries breaking over time as other libraries are updated, generating confusion and trouble it so far has not recovered from. Then adding two toolchains to top the confusion off. 

For many simpler projects, these issues are less troublesome and the Arduino platform is still simple fun to use.

Finally, I don't bother with putting boot loaders on the Blue Pills. I either flash the program with the serial boot loader built into the chip, with a USB to serial adaptor, or use one of the inexpensive ST-Link adaptor clones from eBay. Although I might try the various boot loaders out at some future point. I can see for something like the uBitx installing a USB boot loader would be the best way to go for usability. 

Whichever toolchain you use, as Jack pointed out, let people know where the actual source location of library you used can be found.  As, many libraries have more than one version and authors.

Tom, wb6b

Re: How to get rid of Local FM broadcast stations #ubitx

Gavin
 

I stripped all the paint from the connections to the chassis, and twisted the wires up a bit more. There is continuity between the coax ground and the other grounds. Any other ideas why its picking up these local stations?

Re: Let's Minimize the Library problems.

Ashhar Farhan
 

Cory, jack,
Great ideas. I am travelling and I will try implementing these.
One of my key constraints is to keep things working with what others find easy to use. I would switch from Arduino to the Blue pill in a second except that programming it from Arduino or Platform I/O isn't so simple. You have burn in the boot loader that needs you to hook it up with a serail to usb cable, then switch over to usb programming.
I just give this as an example. Platform io isn't as familiar to many as the horribly kuldgy Arduino IDE. I aleast wish they had implemented a goto line feature!

73, f


On Sun 15 Dec, 2019, 2:16 AM Cory King, <cory@...> wrote:
And sorry to double reply, “good ide support” I mean something other than Arduino IDE.  VSCode or JetBrains CLion.  Both have much better syntax highlighting, auto-completion, git integration and oh so much more.

Manual to set up uBitx Ver 6

wnpauls
 

Is there a manual, or pictures, or help to set up the new uBitx Ver 6? 

If so, where can I find it?

thanks,  Paul K0ZYV

Re: bitx v6 is here

Ashhar Farhan
 

Buddy,
All the user interface is usable without needing touch. If you tap on the tuning knob for a second, you can move the focus from one button to the next and then click in the button to select again. Each button has text associated with it that can be read out. I have taken care to see to it that all features are accessible with and without touch. For example, the ability to enter a new frequency using the touch pad is replicated in fast tune where if you hold down the button while on one of the vfos , you can now quickly move across the bands in 50 khz steps.

Jack,
The function names are confusing as well..many variables are declared and not used any more. There is a large amount of code that is commented out as well. I have to clean that up, refactor reassemble. I will hopefully do this after Christmas.
The graphics library should really be called just a user interface library. The ILI9341 uses a SPI interface where it can fill a rectangle with a 16-bit colour. I used this to draw vertical lines, horizontal lines and pixels. No other graphical primitives have been used. The text characters are plotted pixel by pixel. The entire graphics routines are less than 100 lines. An often reused routine is the drawText routine that draws text centered inside a rectangle with a border. That makes all the buttons trivial. Almost all the user interface is just buttons, very much inspired by the jackal.
While tuning, i observed that only one digit if the frequency read out changes most of the time. So, the displayVFO routines figures which digits need to be repainted and updates only those. This routine is probably what makes the interface usable with the 8 bit power of the Arduino Nano.

- f

On Sun 15 Dec, 2019, 5:43 AM Buddy Brannan, <buddy@...> wrote:
Ooh…a thing that reads the screen in morse? That’s half the battle toward eyes-free operation. The other half, of course, is some additional way to control besides the built-in touch screen interface, like a programmable keypad. Seems to me there were a couple of implementations of this floating around. Do please elaborate.


Buddy Brannan, KB5ELV - Erie, PA
Email: buddy@...
Mobile: (814) 431-0962



> On Dec 14, 2019, at 12:38 PM, Ashhar Farhan <farhanbox@...> wrote:
>
> By morse reader, I actually meant software that reads out the screen in morse code.
> I had fooled around with many morse decoders. Nothing really works on the bands. CW skimmer is the only thing that works under contest conditions.
> So, if you want a morse code decoder that really works well, can adapt to any radio and needs no special hardware, then, spend a month, 20 minutes a day and practice at 30 wpm.
> - f
>
> On Sat 14 Dec, 2019, 9:56 PM splat1956, <dnrabin7@...> wrote:
> Hi
> This is very exciting. I have been thinking a long time but have not purchased one because I was afraid that the soldering and wiring instructions would be confusing. There have been many posts by confused builders.
>
> This sounds great. Is there a morse code decoder built in or coming soon ? Your earlier post said " I have added a morse reader already. I shall finish integration to the user interface soon."
> Please let us know when that is incorporated. I am unlikely to upgrade the software-firmware once it is working and that would be a very nice feature.
>
> Great idea on the calibration with a known station signal for people without test equipment.
>
> Thank you very much for this great upgrade !
>
> David W9PH
>
>
>




Re: bitx v6 is here

Buddy Brannan
 

Ooh…a thing that reads the screen in morse? That’s half the battle toward eyes-free operation. The other half, of course, is some additional way to control besides the built-in touch screen interface, like a programmable keypad. Seems to me there were a couple of implementations of this floating around. Do please elaborate.


Buddy Brannan, KB5ELV - Erie, PA
Email: buddy@...
Mobile: (814) 431-0962

On Dec 14, 2019, at 12:38 PM, Ashhar Farhan <farhanbox@...> wrote:

By morse reader, I actually meant software that reads out the screen in morse code.
I had fooled around with many morse decoders. Nothing really works on the bands. CW skimmer is the only thing that works under contest conditions.
So, if you want a morse code decoder that really works well, can adapt to any radio and needs no special hardware, then, spend a month, 20 minutes a day and practice at 30 wpm.
- f

On Sat 14 Dec, 2019, 9:56 PM splat1956, <dnrabin7@...> wrote:
Hi
This is very exciting. I have been thinking a long time but have not purchased one because I was afraid that the soldering and wiring instructions would be confusing. There have been many posts by confused builders.

This sounds great. Is there a morse code decoder built in or coming soon ? Your earlier post said " I have added a morse reader already. I shall finish integration to the user interface soon."
Please let us know when that is incorporated. I am unlikely to upgrade the software-firmware once it is working and that would be a very nice feature.

Great idea on the calibration with a known station signal for people without test equipment.

Thank you very much for this great upgrade !

David W9PH


Re: Digital mode transmit via CAT but MIC-connector switches to Transmit directly - #cat #digital #v5 #ubitx-help - SOLVED #digital #v5 #ubitx-help #cat

Erwin Serlé
 

Solved by inserting the small PTT switch into the orange Raduino line. Now I can switch to Tx by PTT via CAT with or without plug in the mic jack. And can activate Tx via the little PTT switch manually when a plug is in the mic jack.


--
PE3ES - F4VTQ - Erwin
73

Re: PTT with digital modes #bitx20 #cat #digital

Erwin Serlé
 

Just had the same since yesterday. I installed the small PTT push button in the orange cable coming from Raduino board and going to the microphone key jack. Now th problem is over.

You can now do a CAT PTT with the CEC firmware (with or without a plug in the key jack) or a manual PTT when the plug is in the mic key jack.
I have used JS8CALL and WSJT-x to test PTT.
I have not transmitted so far.
--
PE3ES - F4VTQ - Erwin
73

Re: uBITX CW offset woes

Gordon Gibby
 

You are very gracious.

I think the real issue is that my other rigs know if you are in CW mode or in single side band mode, and so they can’t offset the beat frequency oscillator appropriately

The MicroBid X with Stock software does not know; if you push the mic button you are single side band if you push the key you are CW., and until you do that it doesn’t know. By merely adding a way for it to know which technique (SSB vs cw) you prefer this could be solved.

On Dec 14, 2019, at 09:34, Bill Cromwell <wrcromwell@...> wrote:

Hi Gordon,

Either way we setup the dial is right. Either way is wrong. If we use it the wrong way. As we have both said, we have to know how the radio in front of us works if we are going to have good results. That means we don't have any part of our emission outside the band AND our signal is where the other ham can hear it. For SSB we must present the right sideband, too.

Once upon a time I got a headache sorting it all out. At that time the headache medicines had a commercial showing Thor's hammer inside a human head striking an anvil complete with lightning strikes. If you remember those you will know it was at least a week ago:)

73,

Bill KU8H


On 12/13/19 8:35 PM, Gordon Gibby wrote:
Aargh. I may be wrong here! If I am, my apologies, it makes my head spin a bit. I’ll have to go fiddle with the radio and try it out.
--
bark less - wag more