Date   
Re: Made Mods to V3 uBitx - no longer transmitting #ubitx-help #v3

Steve - KE0VCD
 

I tested voltage out of TXA TXB and TXC (when keyed-up and talking) at R151-3.  Nada

Re: The Saga continues.... uBITX v5 Firmware update

N0YWB
 

Windows 7 and Windows 10 will normally automatically install the CH340 driver the first time you connect the Nano or UNO to your PC.
If you have uninstalled driver with the remove files option, You can get the CH340 drivers at
https://cdn.sparkfun.com/assets/learn_tutorials/8/4/4/CH341SER.EXE
Instructions (read past the ads):
https://learn.sparkfun.com/tutorials/how-to-install-ch340-drivers/all

There is no need to uninstall the Arduino IDE to be able to use XLoader or other loaders.
In fact, you can use the AVRdude utility in the Arduino installation to load hex files:
https://forum.arduino.cc/index.php?topic=410618.0

On 2/13/2020 09:38, Daniel Flanagan wrote:
Hello again,

I now have all the tools I need to update my uBITX V5 firmware to
KD8CEC's V1.2 firmware thanks to the help of this group.

My new problem is my computer(s). I am using Windows 7 Professional
service pack 1.

I want to use XLoader to upload hex files to my uBITX V5, however I
can't get the CH340 driver to install properly. No com ports are
recognized after installation (none show up in device manager). When
I install the CH340 driver it tells me that the driver has been
installed in advance, i.e. pre-installed. When I installed the
Arduino IDE it installed a bunch of drivers. I thought that might be
the problem so I removed it (using Revo Pro which removes everything
associated with the program).

I have also tried doing this on my Windows 7 Home premium computer
with the same result. Can anyone tell me what I am missing?

Thanks,
Dan (W3DF)

Re: The Saga continues.... uBITX v5 Firmware update

Daniel Flanagan
 

OK thanks... well after much head scratching I discovered you have to
have the Arduino Nano connected into a usb port before it shows up as
a com port in device manager.

Now Xloader opens the com port and when I hit upload the led on the
nano blinks a couple of times then stops and it just sits there with
the led on. I have tried two different com ports from my two usb
ports, one is com 4 the other com 5. Both do the same thing.

How should the port be configured?

They are configured as follows:

Data bits 8
Parity None
Stop bits 1
Flow control None
In Advance settings.... Use FIFO buffers is checked (requires 16550
compatible UART)

The port was originally set at 9600 baud.... I set it for 115200
Neither setting works

Any ideas?

On 2/13/20, AndyH <ahecker@...> wrote:
Dan,

What does the computer do after you install the CH340 driver and then
plug-in the USB cable connected to the Arduino?

If it's working correctly, you won't see anything on the desktop or lower
right status area.  To see if the Arduino has been assigned a port, you'll
have to hit the control panel, then Device Manager, and look at Ports (COM &
LPT).  (The image is from a Win 10 ultimate machine but it behaves the same
as my remaining Win 7 box.)

If the driver isn't loaded correctly, or there's a problem with a particular
USB port, you'll get an error pop-up in the lower right of the desktop when
you connect the Arduino.  Sometimes, using a different USB port is enough to
'force' Windows to reload/reconfigure the driver - that will usually make it
work in all USB ports.

73, Andy, KG5RKP



Re: Made Mods to V3 uBitx - no longer transmitting #ubitx-help #v3

Steve - KE0VCD
 

I took out the AGC and put a jumper wire in its place.  Nada

Thanks Dave.  Should I be able to detect the signal on KT1-3 pin 12 when keyed-up and talking?

Are there key points in the circuit I can test to narrow down the issue?   If something blew, what are the most likely offenders?

Re: Tuning knob behavior

AndyH
 

I'm somewhat surprised by the 'rig sliding' comments.  My µBITX is in a metal box with stick-on rubber feet, and I'm using a spinner knob with an inexpensive encoder.  I put four fingers on top of the case and my thumb falls on the tuning knob.  It's a one-hand operation throughout.  While I sometimes misjudge the length of press required to enter the step size function in Ian's software, making a step change is two button presses - one in and one out.  I would guess that a system requiring more button presses might provide more opportunity for sliding, especially with a lighter radio.  Can't say for sure, though, so that's just a guess.

73, Andy, KG5RKP


On Thu, Feb 13, 2020 at 08:18 AM, Jack, W8TEE wrote:
 
Andy:
 
I think my solution will be a NO push button on the front panel that advances the increment value by one digit (e.g., a 10x change) each time you press the button. After a user-defined number of presses, it "wraps" back to the starting position. I would probably start with the 10Hz digit and have 4 presses (e.g., 10KHz) before wrapping back to 10Hz... I think this approach for a frequency delta is better than an encoder switch press because my tests suggest it obviates the "rig sliding" problem which forces you to hold the rig with one hand as you press the encoder switch with the other.

Re: uBITX V6 Sideband Issue

W2CTX
 

Hey Reed
If we were not confused before we now are! ( This is a joke ) hihi

rOn

On February 13, 2020 at 12:28 PM Reed N <greenkid336600+groupsio@...> wrote:


I'm describing what the code *is* doing. Not what it necessarily *should* be doing.

Reed


Re: uBITX V6 Sideband Issue

Reed N
 

I'm describing what the code *is* doing. Not what it necessarily *should* be doing.


Reed

Re: uBITX V6 Sideband Issue

Reed N
 

To be clear, "not behave as Jim described" was in reference to his comment https://groups.io/g/BITX20/message/75987
Not his comment https://groups.io/g/BITX20/message/75994


Reed

Re: uBITX V6 Sideband Issue

Gordon Gibby
 

Reid, what you described is the WRONG way for a CW transceiver to work.   




On Feb 13, 2020, at 12:09, Reed N <greenkid336600+groupsio@...> wrote:

Ashhar,

Do you have commits you haven't pushed yet? My reading of the code suggests that CW tuning does not behave as Jim described.

Let's suppose somebody I want to chat with is transmitting exactly at 7.200.000Hz. Let's also suppose that I have my side tone set to 600Hz, and that I can tune perfectly to this pitch. Finally, suppose that I'm in LSB mode.

I tune my dial, and when my display says 7.200.000Hz then I will actually be hearing that frequency as 600Hz, because the actual tuning frequency is offset by the side tone, which is good
https://github.com/afarhan/ubitxv6/blob/master/ubitx_v6.1_code.ino#L391

However, when I then try and transmit, I believe that I end up transmitting at 7.199.400Hz, because the side tone is applied on transmit too
https://github.com/afarhan/ubitxv6/blob/master/ubitx_v6.1_code.ino#L448

Am I misreading that?


Reed

Re: The Saga continues.... uBITX v5 Firmware update

AndyH
 

Dan,

   What does the computer do after you install the CH340 driver and then plug-in the USB cable connected to the Arduino?

   If it's working correctly, you won't see anything on the desktop or lower right status area.  To see if the Arduino has been assigned a port, you'll have to hit the control panel, then Device Manager, and look at Ports (COM & LPT).  (The image is from a Win 10 ultimate machine but it behaves the same as my remaining Win 7 box.)

   If the driver isn't loaded correctly, or there's a problem with a particular USB port, you'll get an error pop-up in the lower right of the desktop when you connect the Arduino.  Sometimes, using a different USB port is enough to 'force' Windows to reload/reconfigure the driver - that will usually make it work in all USB ports.

73, Andy, KG5RKP



   

Re: uBITX V6 Sideband Issue

Reed N
 

Ashhar,

Do you have commits you haven't pushed yet? My reading of the code suggests that CW tuning does not behave as Jim described.

Let's suppose somebody I want to chat with is transmitting exactly at 7.200.000Hz. Let's also suppose that I have my side tone set to 600Hz, and that I can tune perfectly to this pitch. Finally, suppose that I'm in LSB mode.

I tune my dial, and when my display says 7.200.000Hz then I will actually be hearing that frequency as 600Hz, because the actual tuning frequency is offset by the side tone, which is good
https://github.com/afarhan/ubitxv6/blob/master/ubitx_v6.1_code.ino#L391

However, when I then try and transmit, I believe that I end up transmitting at 7.199.400Hz, because the side tone is applied on transmit too
https://github.com/afarhan/ubitxv6/blob/master/ubitx_v6.1_code.ino#L448

Am I misreading that?


Reed

Re: filling the nextion 5 inch screen

Stephanus K6NG
 

Joe,
   Have you been able to figure out the math with sys*x? I have a hard time figuring it out.
Thanks
 Stephanus

Re: low output only on 40m

Vic WA4THR
 

I have been following this thread with a little confusion, and I am not sure what the resolution is or if there is one. I have a V4 uBitX and the 40m CW output has always been low. Where I see 3.5w out on 40m CW into a dummy load, I can see 12w when on SSB and "Ahhh"ing into the microphone. I see a similar disparity on 17m. Since the SSB output is reasonable, I haven't worried about it too much and assumed something about the way CW is generated isn't unbalancing the mixer enough or something. Is there a fix?

FWIW, i am using KD8CEC v 1.1 software.

=Vic=

Re: uBITX V6 Sideband Issue

Jim Sheldon
 

I am sorry Farhan, I just downloaded and installed your LATEST from GitHub (V6.1).  The TRANSMITTER is still being offset by the sidetone, NOT the receiver.  You have NOT fixed the CW offset issue and until thatj is corrected, you will still be getting complaints.  

I TESTED this on the air with a local ham and he confirms the fact (he was using a Yaesu FT-5000 commercial transceiver). I had him tuned in on exactly 7025.00 matching the 800 sidetone to the incoming signal, CW and LSB selected.  The V6 uBITX was transmitting on 7024.20 KHz.  That is a TRANSMIT offset, NOT a receive offset.

Sorry, but it ain't fixed yet and has always been like this since way back in Version 3

Jim Sheldon,  W0EB

------ Original Message ------
From: "Gordon Gibby" <docvacuumtubes@...>
Sent: 2/13/2020 9:55:27 AM
Subject: Re: [BITX20] uBITX V6 Sideband Issue

Great!  I stand corrected. 


On Feb 13, 2020, at 10:53, Ashhar Farhan <farhanbox@...> wrote:


V6 offset for CW is already fixed. I have tested it too.
The lsb to usb switch happens when you tune. It should happen when you press the button. I will fix that one.
- f

On Thu 13 Feb, 2020, 8:53 PM Gordon Gibby, <docvacuumtubes@...> wrote:
Yup—I agree.
> On Feb 13, 2020, at 10:20, Jim Sheldon <w0eb@...> wrote:
>
> Gordon, and others.  That is the way it's supposed to work.  I have posted on that a few times in the past, almost from day one, but NOBODY, not Farhan or CEC seems to have listened.
>
> You NEVER offset the transmitter by the sidetone value in CW.  That makes the dial inaccurate and can cause inadvertent out of band operation very easily.
>
> The way CW works on ALL, repeat ALL properly designed transceivers that include CW as a mode is, when in CW mode, the keyed carrier MUST be on the exact frequency shown on the transceivers dial or whatever frequency indicator is used.  The RECEIVER is offset by the sidetone frequency and in the direction from the transmitted carrier to put it in the center of whichever (USB/LSB) sideband is being received at the time.  This allows the operator to tune in a CW signal to match his/her sidetone frequency and be basically zero beat to the received signals actual transmitting frequency.
>
> This way, if you pay attention to your band limits and if your uBITX master oscillator is properly calibrated, you should never have to worry about accidentally transmitting out of band with possible legal repercussions from your country's licensing authority.
>
> Until the people supplying the software used get this fixed, CW will never work right.
>
> By the way, our TSW group has done it right from the first time we came up with working software for the uBITX and all our software has CW transmitting on the dial frequency with the receiver being properly offset.
>
> Jim Sheldon, W0EB
> TSW Project Coordinator
>
> ------ Original Message ------
> From: "Gordon Gibby" <docvacuumtubes@...>
> To: BITX20@groups.io
> Sent: 2/13/2020 8:59:30 AM
> Subject: Re: [BITX20] uBITX V6 Sideband Issue
>
>> It can easily be fixed, however it would require that people explicitly choose to be in CW mode.  Then the offset can be built right into the code, with the display showing your TRANSMIT  frequency, and receiving offset by the proper amount.
>>>> On Feb 13, 2020, at 09:49, W2CTX <w2ctx@...> wrote:
>>>
>>> You are correct in how the ubitx works in CW and it has been wrong since day 1.
>>> However itb has never been fixed!
>>>
>>>
>>>> On February 13, 2020 at 8:37 AM currently@... wrote:
>>>>
>>>>
>>>> The CW issue it that I have to tune off of my frequency, by whatever frequency I have the tone set for, in order to hear a replying station.  I thought the entire idea of having that tone setting was to not have to use the RIT.
>>>>
>>>> Bob
>>>>
>>>>
>>>>
>>>
>>>
>>>
>>
>>
>>
>
>
>
>



Re: #v6 #calibration - Where is the Setup Menu? #v6 #calibration

Reed N
 

The 10 second wait isn't a processor speed issue. It's programmed by Ashhar to take that long.


Reed

Re: uBITX V6 Sideband Issue

Gordon Gibby
 

Great!  I stand corrected. 


On Feb 13, 2020, at 10:53, Ashhar Farhan <farhanbox@...> wrote:


V6 offset for CW is already fixed. I have tested it too.
The lsb to usb switch happens when you tune. It should happen when you press the button. I will fix that one.
- f

On Thu 13 Feb, 2020, 8:53 PM Gordon Gibby, <docvacuumtubes@...> wrote:
Yup—I agree.
> On Feb 13, 2020, at 10:20, Jim Sheldon <w0eb@...> wrote:
>
> Gordon, and others.  That is the way it's supposed to work.  I have posted on that a few times in the past, almost from day one, but NOBODY, not Farhan or CEC seems to have listened.
>
> You NEVER offset the transmitter by the sidetone value in CW.  That makes the dial inaccurate and can cause inadvertent out of band operation very easily.
>
> The way CW works on ALL, repeat ALL properly designed transceivers that include CW as a mode is, when in CW mode, the keyed carrier MUST be on the exact frequency shown on the transceivers dial or whatever frequency indicator is used.  The RECEIVER is offset by the sidetone frequency and in the direction from the transmitted carrier to put it in the center of whichever (USB/LSB) sideband is being received at the time.  This allows the operator to tune in a CW signal to match his/her sidetone frequency and be basically zero beat to the received signals actual transmitting frequency.
>
> This way, if you pay attention to your band limits and if your uBITX master oscillator is properly calibrated, you should never have to worry about accidentally transmitting out of band with possible legal repercussions from your country's licensing authority.
>
> Until the people supplying the software used get this fixed, CW will never work right.
>
> By the way, our TSW group has done it right from the first time we came up with working software for the uBITX and all our software has CW transmitting on the dial frequency with the receiver being properly offset.
>
> Jim Sheldon, W0EB
> TSW Project Coordinator
>
> ------ Original Message ------
> From: "Gordon Gibby" <docvacuumtubes@...>
> To: BITX20@groups.io
> Sent: 2/13/2020 8:59:30 AM
> Subject: Re: [BITX20] uBITX V6 Sideband Issue
>
>> It can easily be fixed, however it would require that people explicitly choose to be in CW mode.  Then the offset can be built right into the code, with the display showing your TRANSMIT  frequency, and receiving offset by the proper amount.
>>>> On Feb 13, 2020, at 09:49, W2CTX <w2ctx@...> wrote:
>>>
>>> You are correct in how the ubitx works in CW and it has been wrong since day 1.
>>> However itb has never been fixed!
>>>
>>>
>>>> On February 13, 2020 at 8:37 AM currently@... wrote:
>>>>
>>>>
>>>> The CW issue it that I have to tune off of my frequency, by whatever frequency I have the tone set for, in order to hear a replying station.  I thought the entire idea of having that tone setting was to not have to use the RIT.
>>>>
>>>> Bob
>>>>
>>>>
>>>>
>>>
>>>
>>>
>>
>>
>>
>
>
>
>



Re: uBITX V6 Sideband Issue

Ashhar Farhan
 

V6 offset for CW is already fixed. I have tested it too.
The lsb to usb switch happens when you tune. It should happen when you press the button. I will fix that one.
- f

On Thu 13 Feb, 2020, 8:53 PM Gordon Gibby, <docvacuumtubes@...> wrote:
Yup—I agree.
> On Feb 13, 2020, at 10:20, Jim Sheldon <w0eb@...> wrote:
>
> Gordon, and others.  That is the way it's supposed to work.  I have posted on that a few times in the past, almost from day one, but NOBODY, not Farhan or CEC seems to have listened.
>
> You NEVER offset the transmitter by the sidetone value in CW.  That makes the dial inaccurate and can cause inadvertent out of band operation very easily.
>
> The way CW works on ALL, repeat ALL properly designed transceivers that include CW as a mode is, when in CW mode, the keyed carrier MUST be on the exact frequency shown on the transceivers dial or whatever frequency indicator is used.  The RECEIVER is offset by the sidetone frequency and in the direction from the transmitted carrier to put it in the center of whichever (USB/LSB) sideband is being received at the time.  This allows the operator to tune in a CW signal to match his/her sidetone frequency and be basically zero beat to the received signals actual transmitting frequency.
>
> This way, if you pay attention to your band limits and if your uBITX master oscillator is properly calibrated, you should never have to worry about accidentally transmitting out of band with possible legal repercussions from your country's licensing authority.
>
> Until the people supplying the software used get this fixed, CW will never work right.
>
> By the way, our TSW group has done it right from the first time we came up with working software for the uBITX and all our software has CW transmitting on the dial frequency with the receiver being properly offset.
>
> Jim Sheldon, W0EB
> TSW Project Coordinator
>
> ------ Original Message ------
> From: "Gordon Gibby" <docvacuumtubes@...>
> To: BITX20@groups.io
> Sent: 2/13/2020 8:59:30 AM
> Subject: Re: [BITX20] uBITX V6 Sideband Issue
>
>> It can easily be fixed, however it would require that people explicitly choose to be in CW mode.  Then the offset can be built right into the code, with the display showing your TRANSMIT  frequency, and receiving offset by the proper amount.
>>>> On Feb 13, 2020, at 09:49, W2CTX <w2ctx@...> wrote:
>>>
>>> You are correct in how the ubitx works in CW and it has been wrong since day 1.
>>> However itb has never been fixed!
>>>
>>>
>>>> On February 13, 2020 at 8:37 AM currently@... wrote:
>>>>
>>>>
>>>> The CW issue it that I have to tune off of my frequency, by whatever frequency I have the tone set for, in order to hear a replying station.  I thought the entire idea of having that tone setting was to not have to use the RIT.
>>>>
>>>> Bob
>>>>
>>>>
>>>>
>>>
>>>
>>>
>>
>>
>>
>
>
>
>



The Saga continues.... uBITX v5 Firmware update

Daniel Flanagan
 

Hello again,

I now have all the tools I need to update my uBITX V5 firmware to
KD8CEC's V1.2 firmware thanks to the help of this group.

My new problem is my computer(s). I am using Windows 7 Professional
service pack 1.

I want to use XLoader to upload hex files to my uBITX V5, however I
can't get the CH340 driver to install properly. No com ports are
recognized after installation (none show up in device manager). When
I install the CH340 driver it tells me that the driver has been
installed in advance, i.e. pre-installed. When I installed the
Arduino IDE it installed a bunch of drivers. I thought that might be
the problem so I removed it (using Revo Pro which removes everything
associated with the program).

I have also tried doing this on my Windows 7 Home premium computer
with the same result. Can anyone tell me what I am missing?

Thanks,
Dan (W3DF)

Re: uBITX V6 Sideband Issue

Gordon Gibby
 

Yup—I agree.

On Feb 13, 2020, at 10:20, Jim Sheldon <@W0EB> wrote:

Gordon, and others. That is the way it's supposed to work. I have posted on that a few times in the past, almost from day one, but NOBODY, not Farhan or CEC seems to have listened.

You NEVER offset the transmitter by the sidetone value in CW. That makes the dial inaccurate and can cause inadvertent out of band operation very easily.

The way CW works on ALL, repeat ALL properly designed transceivers that include CW as a mode is, when in CW mode, the keyed carrier MUST be on the exact frequency shown on the transceivers dial or whatever frequency indicator is used. The RECEIVER is offset by the sidetone frequency and in the direction from the transmitted carrier to put it in the center of whichever (USB/LSB) sideband is being received at the time. This allows the operator to tune in a CW signal to match his/her sidetone frequency and be basically zero beat to the received signals actual transmitting frequency.

This way, if you pay attention to your band limits and if your uBITX master oscillator is properly calibrated, you should never have to worry about accidentally transmitting out of band with possible legal repercussions from your country's licensing authority.

Until the people supplying the software used get this fixed, CW will never work right.

By the way, our TSW group has done it right from the first time we came up with working software for the uBITX and all our software has CW transmitting on the dial frequency with the receiver being properly offset.

Jim Sheldon, W0EB
TSW Project Coordinator

------ Original Message ------
From: "Gordon Gibby" <docvacuumtubes@...>
To: BITX20@groups.io
Sent: 2/13/2020 8:59:30 AM
Subject: Re: [BITX20] uBITX V6 Sideband Issue

It can easily be fixed, however it would require that people explicitly choose to be in CW mode. Then the offset can be built right into the code, with the display showing your TRANSMIT frequency, and receiving offset by the proper amount.
On Feb 13, 2020, at 09:49, W2CTX <w2ctx@...> wrote:
You are correct in how the ubitx works in CW and it has been wrong since day 1.
However itb has never been fixed!


On February 13, 2020 at 8:37 AM currently@... wrote:


The CW issue it that I have to tune off of my frequency, by whatever frequency I have the tone set for, in order to hear a replying station. I thought the entire idea of having that tone setting was to not have to use the RIT.

Bob






Re: uBITX V6 Sideband Issue

Jim Sheldon
 

Gordon, and others. That is the way it's supposed to work. I have posted on that a few times in the past, almost from day one, but NOBODY, not Farhan or CEC seems to have listened.

You NEVER offset the transmitter by the sidetone value in CW. That makes the dial inaccurate and can cause inadvertent out of band operation very easily.

The way CW works on ALL, repeat ALL properly designed transceivers that include CW as a mode is, when in CW mode, the keyed carrier MUST be on the exact frequency shown on the transceivers dial or whatever frequency indicator is used. The RECEIVER is offset by the sidetone frequency and in the direction from the transmitted carrier to put it in the center of whichever (USB/LSB) sideband is being received at the time. This allows the operator to tune in a CW signal to match his/her sidetone frequency and be basically zero beat to the received signals actual transmitting frequency.

This way, if you pay attention to your band limits and if your uBITX master oscillator is properly calibrated, you should never have to worry about accidentally transmitting out of band with possible legal repercussions from your country's licensing authority.

Until the people supplying the software used get this fixed, CW will never work right.

By the way, our TSW group has done it right from the first time we came up with working software for the uBITX and all our software has CW transmitting on the dial frequency with the receiver being properly offset.

Jim Sheldon, W0EB
TSW Project Coordinator

------ Original Message ------
From: "Gordon Gibby" <docvacuumtubes@...>
To: BITX20@groups.io
Sent: 2/13/2020 8:59:30 AM
Subject: Re: [BITX20] uBITX V6 Sideband Issue

It can easily be fixed, however it would require that people explicitly choose to be in CW mode. Then the offset can be built right into the code, with the display showing your TRANSMIT frequency, and receiving offset by the proper amount.
On Feb 13, 2020, at 09:49, W2CTX <w2ctx@...> wrote:

You are correct in how the ubitx works in CW and it has been wrong since day 1.
However itb has never been fixed!


On February 13, 2020 at 8:37 AM currently@... wrote:


The CW issue it that I have to tune off of my frequency, by whatever frequency I have the tone set for, in order to hear a replying station. I thought the entire idea of having that tone setting was to not have to use the RIT.

Bob