On Nov 16, 2021, at 5:50 AM, Ashhar Farhan <farhanbox@...> wrote:



I will have to do it. As soon as I finish this accursed sbitx....

On Tue, Nov 16, 2021, 3:36 PM David Wilcox K8WPE via groups.io <Djwilcox01=yahoo.com@groups.io> wrote:

Farhan,

Is your keyboard connected to your rig via a circuit of some type and uses a stereo three contact plug, not a tip-sleeve two contact plug like most CW rigs.  Bill is right on with a straight key needing a tip-ring-sleeve type of plug wired like the Dah on my paddles. That is finally working for CW on my new V6.

If so could you have one of your assistants update the manual?  That would be great for those who are assembling a Bitx for the first time.  Even the screw lengths are either not listed or those that are listed in the manual were wrong.  Or at 76 I can’t follow directions well (ask my wife). Just a few improvements would have made my job a lot easier.  

The V6 is a sweet sounding radio, even with the top mounted speaker.  So far worth the price for what it does. I do my happy dance daily as I discover something else about it.

Dave K8WPE

David J. Wilcox’s iPad

On Nov 16, 2021, at 1:17 AM, Ashhar Farhan <farhanbox@...> wrote:



Bill,

Just i clear up the air, I am a cw operator. I prefer cw ragchew at 10 to 12 wpm because I can copy at that rate in my head while doing something else.

However, I send cw as ssb tones from my keyboard. Again, this works because I can type out fast and go back to what I was doing. Hence I dont use either the straight key nor the paddle.

There is a significant bug that causes the intial delay. I just havent found the time to fix it. Does someone know what the fix is?

- f

On Tue, Nov 16, 2021, 7:05 AM Bill Cromwell <wrcromwell@...> wrote:

Hi,

Cw in the stock uBitX was not very good. Farhan has testified that he is
NOT a CW op. In my case I installed the CEC software but I don't think
that is the root of your problem. I think my previous post about the
plug is where you get resolution.

73,

Bill KU8H

bark less - wag more

On 11/15/21 7:58 PM, David Wilcox K8WPE via groups.io wrote:
> But that doesn’t explain why a set of paddles works using the Dah key
> when the setup is set for “hand key”.  It does work, just uses
> different connections so processor speed must be satisfactory. Just
> the straight key is hooked up wrong to the processor. At least that is
> what I am thinking…… and I am not really up to speed on how the uBitx
> works for CW.  Any more thoughts?  I really want this to work stock
> before I screw it up with upgrades or mods.
>
> Dave K8WPE
>
> David J. Wilcox’s iPad
>
>> On Nov 15, 2021, at 7:36 PM, Paul Jensen via groups.io
>> <wkend_traveler=yahoo.com@groups.io> wrote:
>>
>> On Mon, Nov 15, 2021 at 03:32 PM, David Wilcox K8WPE wrote:
>>
>>     Any ideas as to what the cause might be?
>>
>> >From memory, this is a software issue combined with a slow processor
>> (Nano).  The software reads an a/d converter that looks at the key
>> pin.  During the voltage transition (key press), it can read an
>> intermediate voltage.
>>
>> The only solution is a faster processor.  I went with the teensy
>> processor solution (by w0eb <http://www.w0eb.com/>).  This works
>> great.  I can hook up a keyboard, use a keyer and a straight key. 
>> Never messes up.  The user interface is well done and quite pleasing
>> to use.
>>
>> I have a icom 7300 sitting next to the ubitx.  I tune around the
>> bands with the ubitx.  It is more fun to use and is pleasant to
>> listen to.  Perfect for listening to code practice.  If I hear
>> something good, I will use the icom to transmit.
>

On Nov 16, 2021, at 1:17 AM, Ashhar Farhan <farhanbox@...> wrote:



Bill,

Just i clear up the air, I am a cw operator. I prefer cw ragchew at 10 to 12 wpm because I can copy at that rate in my head while doing something else.

However, I send cw as ssb tones from my keyboard. Again, this works because I can type out fast and go back to what I was doing. Hence I dont use either the straight key nor the paddle.

There is a significant bug that causes the intial delay. I just havent found the time to fix it. Does someone know what the fix is?

- f

On Tue, Nov 16, 2021, 7:05 AM Bill Cromwell <wrcromwell@...> wrote:

Hi,

Cw in the stock uBitX was not very good. Farhan has testified that he is
NOT a CW op. In my case I installed the CEC software but I don't think
that is the root of your problem. I think my previous post about the
plug is where you get resolution.

73,

Bill KU8H

bark less - wag more

On 11/15/21 7:58 PM, David Wilcox K8WPE via groups.io wrote:
> But that doesn’t explain why a set of paddles works using the Dah key
> when the setup is set for “hand key”.  It does work, just uses
> different connections so processor speed must be satisfactory. Just
> the straight key is hooked up wrong to the processor. At least that is
> what I am thinking…… and I am not really up to speed on how the uBitx
> works for CW.  Any more thoughts?  I really want this to work stock
> before I screw it up with upgrades or mods.
>
> Dave K8WPE
>
> David J. Wilcox’s iPad
>
>> On Nov 15, 2021, at 7:36 PM, Paul Jensen via groups.io
>> <wkend_traveler=yahoo.com@groups.io> wrote:
>>
>> On Mon, Nov 15, 2021 at 03:32 PM, David Wilcox K8WPE wrote:
>>
>>     Any ideas as to what the cause might be?
>>
>> >From memory, this is a software issue combined with a slow processor
>> (Nano).  The software reads an a/d converter that looks at the key
>> pin.  During the voltage transition (key press), it can read an
>> intermediate voltage.
>>
>> The only solution is a faster processor.  I went with the teensy
>> processor solution (by w0eb <http://www.w0eb.com/>).  This works
>> great.  I can hook up a keyboard, use a keyer and a straight key. 
>> Never messes up.  The user interface is well done and quite pleasing
>> to use.
>>
>> I have a icom 7300 sitting next to the ubitx.  I tune around the
>> bands with the ubitx.  It is more fun to use and is pleasant to
>> listen to.  Perfect for listening to code practice.  If I hear
>> something good, I will use the icom to transmit.
>

But that doesn’t explain why a set of paddles works using the Dah key when the setup is set for “hand key”.  It does work, just uses different connections so processor speed must be satisfactory. Just the straight key is hooked up wrong to the processor. At least that is what I am thinking…… and I am not really up to speed on how the uBitx works for CW.  Any more thoughts?  I really want this to work stock before I screw it up with upgrades or mods.

Dave K8WPE

David J. Wilcox’s iPad

On Nov 15, 2021, at 7:36 PM, Paul Jensen via groups.io <wkend_traveler@...> wrote:

On Mon, Nov 15, 2021 at 03:32 PM, David Wilcox K8WPE wrote:

Any ideas as to what the cause might be?

From memory, this is a software issue combined with a slow processor

(Nano).  The software reads an a/d converter that looks at the key pin.  During the voltage transition (key press), it can read an intermediate voltage.

The only solution is a faster processor.  I went with the teensy processor solution (by w0eb <http://www.w0eb.com/>).  This works great.  I can hook up a keyboard, use a keyer and a straight key.  Never messes up.  The user interface is well done and quite pleasing to use.

I have a icom 7300 sitting next to the ubitx.  I tune around the bands with the ubitx.  It is more fun to use and is pleasant to listen to.  Perfect for listening to code practice.  If I hear something good, I will use the icom to transmit.

After looking over my new Version 6 uBitx and enjoying it I have discovered an issue regarding using a straight key. As I had mentioned in a previous email to the group when in “hand key” mode and using a straight key when I press down using the key (actually trying three different keys) it makes a squeak and occasionally will hold the side tone irrationally but I can’t use it to send. It sounds like dirty contacts but cleaning them makes no difference. BUT if I insert a set of paddles I can use the dah paddle all day sending like a straight key (still in the “hand key” mode).

I pulled out the board and closely examined the key jack. All looks great and the soldering looks excellent. I reheated the solder contacts anyway but no change. I am probably going to wire up a straight key using the same plug and contacts as a dah paddle and see how it goes.

I checked the contacts in the key jack under high power magnification and with an ohm meter and all seems according to the schematic as far as I can see. Some have advised to use the N8ME firmware but if there is an error or short somewhere I doubt that will fix the issue.

Any ideas as to what the cause might be? I can live with it but would like to figure this out.

Dave K8WPE

David J. Wilcox’s iPad

On Nov 15, 2021, at 7:36 PM, Paul Jensen via groups.io <wkend_traveler@...> wrote:

On Mon, Nov 15, 2021 at 03:32 PM, David Wilcox K8WPE wrote:

Any ideas as to what the cause might be?

From memory, this is a software issue combined with a slow processor (Nano).  The software reads an a/d converter that looks at the key pin.  During the voltage transition (key press), it can read an intermediate voltage.

The only solution is a faster processor.  I went with the teensy processor solution (by w0eb).  This works great.  I can hook up a keyboard, use a keyer and a straight key.  Never messes up.  The user interface is well done and quite pleasing to use. 

I have a icom 7300 sitting next to the ubitx.  I tune around the bands with the ubitx.  It is more fun to use and is pleasant to listen to.  Perfect for listening to code practice.  If I hear something good, I will use the icom to transmit.