Date   
Re: uBITX V6 Sideband Issue

 

Set tone to 0 (zero) and see what happens. Haven't delved into the code as yet!

At 13/02/2020, you 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

Bob WB8CAC
 

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

 

My tests on uBitxv5 which is same circuit as V6, the best freq for BFO was 11.055,5

What was the error in CW? I am curios!

Raj

At 13/02/2020, you wrote:
My V6 arrived yesterday. Assembly and calibration were uneventful. I made several contacts on 80 and 40 SSB and CW. The radio seems to be right dead on frequency transmit
and receive on SSB. The SSB sideband issue is that if I switch from LSB to USB, the display changes but nothing happens frequency wise. There is no change in the audio of a
station being received while I switch. People listening to my transmission report no change when I switch.

On CW, if I call CQ on a clear frequency, I have to use the RIT to tune down by whateer my tone is, in order to receive a replying station. If I'm answering someone, I have
to use the VFO to tune up, by my tone frequency, the RIT bat to their frequency.
My BFO setting is 11.056 and like I said, the dial calibration is dead on.
Any ideas what I did wrong?

73 DE BOB WB8CAC

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

Dane Groszek KD2SSS
 

Thanks, Ben "Turn off the Ubitx, then turn it on. Then press and hold the encoder knob..." This worked for me, noted had to hold it in for about 10 seconds.  Guess I am used to a faster processor. Best regards, Dane

uBITX V6 Sideband Issue

Bob WB8CAC
 

My V6 arrived yesterday.  Assembly and calibration were uneventful.  I made several contacts on 80 and 40 SSB and CW.  The radio seems to be right dead on frequency transmit
and receive on SSB.  The SSB sideband issue is that if I switch from LSB to USB, the display changes but nothing happens frequency wise. There is no change in the audio of a
station being received while I switch.  People listening to my transmission report no change when I switch.

On CW, if I call CQ on a clear frequency, I have to use the RIT to tune down by whateer my tone is, in order to receive a replying station. If I'm answering someone, I have
to use the VFO to tune up, by my tone frequency, the RIT bat to their frequency.
My BFO setting is 11.056 and like I said, the dial calibration is dead on.
Any ideas what I did wrong?
 
73 DE BOB WB8CAC

Re: uBitX V4 80m audio distortion

Gordon Gibby
 

great news!!

On Thu, Feb 13, 2020 at 6:28 AM Vic WA4THR via Groups.Io <vhklein=ptd.net@groups.io> wrote:
Just to follow up on this, I installed a .01uf capacitor from the mic line to ground on the mic connector inside the case of the uBitX. That has cleared up all the problem on 80m and it doesn't seem to have affected the audio response. Easy fix.

=Vic=

Re: uBitX V4 80m audio distortion

Vic WA4THR
 

Just to follow up on this, I installed a .01uf capacitor from the mic line to ground on the mic connector inside the case of the uBitX. That has cleared up all the problem on 80m and it doesn't seem to have affected the audio response. Easy fix.

=Vic=

Re: Collector current design point for Q911+Q912? #v6 #ubitx

Evan Hand
 

Barry,

Did another quick test to see if the Si5351 drive might be the issue (this was one of the theories put forth before).  Measure both signals at TP2 with my scope.  Only real difference was the frequency, though the 3.55MHz signal was closer to a square wave, as would be expected. Values were about 480-490 mVpp.

73
Evan
AC9TU

Re: Collector current design point for Q911+Q912? #v6 #ubitx

Evan Hand
 

Barry,

I did try to measure the C81 in circuit.  I got strange results: 26 nF for one of my v4 boards, and the same for my v5  As you stated before, we are measuring in circuit, so I would not trust the values.

v5 board: measuring CW - 6.7 watts at 7.050 MHz and 14.6 watts at 3.550 MHz. 
v4 board: measuring CW - 7.4 watts at 7.050 MHz and 13.7 watts at 3.550 MHz.

 Both with 13.8 volts to the PA measured into a 50 ohm dummy load with a Missei digital SWR meter.

I too have the power drop on 40 meters.  Have not been doing much with the ubitx, have recently built a Hermes Lite 2 and been playing with that with time I have for the hobby.  Most of my time is taking care of my wife who is having medical issues and needs to go into surgery for an intestine problem on Monday.

73
Evan
AC9TU

Re: v6 #arduino

Reed N
 

I assure you that my Dutch is worse than your English. Google Translate lets us help each other anyway!  :)

Sounds like you're close to up and running. Enjoy!


Reed

Re: Tuning knob behavior

Reed N
 

I go back and forth about this. On one hand, having the ability to slew large amounts can be quite nice. On the other, as you point out, having fixed steps gives a solid consistency. With a knob-only interface, I think that slewing far is more important, but the v6 has "keypad" entry and band buttons for large jumps, so maybe consistency is better? Jury is out for me on this one, because neither option is perfect in all normal usage scenarios.

The Si5351A can generate very precise frequencies, but there's a trade off of knob turning vs actual movement. Most of the time, I don't want to have to do 100 turns to get a 1Hz increment. I also don't usually want to shift 1MHz on each encoder tick. Ashhar probably picked 50Hz because it's good enough most of the time. However, If you're willing to change the code, you can pick your favorite step size really easily (provided it's at least 1Hz - sub-Hz is possible, but you'll have to do a fair amount of refactoring). Change the "50" on these two lines of code to whatever step size you wish.
https://github.com/afarhan/ubitxv6/blob/master/ubitx_v6.1_code.ino#L632
https://github.com/afarhan/ubitxv6/blob/master/ubitx_v6.1_code.ino#L638
(or https://github.com/reedbn/ubitxv6/blob/master/ubitxv6.ino#L387 if you're using my version)

I think the *ideal* solution is to have a setting that lets the user choose whether acceleration is on, as well as the step size. Those are both on my road map for v6, but I haven't gotten around to them yet (obviously). I believe that the KD8CEC+nextion software supports adjustable step size, and I think the TSW Teensy software added that too. Not sure if either has acceleration profile settings.


Reed

Re: v6 #arduino

Rene
 

Thx for fast answering and sorry for bad Englisch. And I just wanted to put on the latest firmware before trying to calibrate. Yesterday heart Astonia and a lot of FT8. Just receiving now and I want to get my licence before the summer.
Regards,
Rene
Netherlands

Re: Tuning knob behavior

AndyH
 

I'm not a fan of variable rate tuning.  The CEC software provides plenty of tuning rate options and it's easy to use the switch on the encoder to change rates.

Andy

Re: uBITX V5 Firmware Hex Files

Jack, W8TEE
 

Actually, multiple source code files is a wonderful thing! First, you can dedicate a file to a general category (e.g., MenuSystem.cpp, DisplaySystem.cpp, etc) which can really help when trying to find functions during debugging. More importantly, multiple files with only one INO file (e.g., the one that contains setup() and loop()) allows the compiler to do incremental compiles, which can save a TON of time.

So, look on those files with a smile, as they will make your life easier once you understand their role.

Jack, W8TEE

On Wednesday, February 12, 2020, 6:10:39 PM EST, Daniel Flanagan <danflan49@...> wrote:


OK... Thanks guys for the info.  Sounds pretty straight forward, just
confused by all the files contained in a source code listing.

I'll ask if I have any more questions.

Dan (W3DF)



On 2/12/20, Jack, W8TEE via Groups.Io <jjpurdum=yahoo.com@groups.io> wrote:
>  Dan:
> Yep, the baud rate on the Serial monitor must match that in the program
> code. Otherwise, you get either no output or a derivative of Mandarin.
>
> I have not looked at the KD8CEC software so I can't help much there. Just
> keep in mind that all of the source code files for a project (i.e., sketch)
> must be in the same folder and that folder must have the name of the file
> that contains setup() and loop(). That is, if a project has those two
> functions in a file named myProject.ino, the directory MUST be named
> myProject.
> Jack, W8TEE
>
>    On Wednesday, February 12, 2020, 4:40:38 PM EST, Daniel Flanagan
> <danflan49@...> wrote:
>
>  Thanks Jack,
>
> I worked through the first chapter of your book today and complied and
> uploaded the simple 2 line program in chapter 1. I think the Arduino
> IDE is working OK although
> I didn't see any output until I manually set the baud rate in the
> serial monitor to 115200. I thought the first line of the simple
> program would do that.  Otherwise, I have't a clue how to compile the
> KD8CEC source code files I find with the Arduino IDE.
>
> Several questions.  The V1.2 KD8CEC says you need to set a flag for V5
> and below but doesn't say what flag and where it can be found.  Which
> file/library do I use for the standard 2 line LCD?  Which file or
> files do I compile before uploading?
>
> I am a retired EE.  I did some programming in the 80s and 90s.  I
> wrote a 4000 line program to do active and semi-active radar
> performance analysis at work.  It was originally in Basic then I had
> to switch to QuickBasic to speed things up.  Later I did some assembly
> language on the home PC.  In the mid 90s I learned some standard C to
> see if the programs I had written in QuickBasic would run any faster
> if written in C.  They didn't, actually they were slower compiled with
> the QuickC compiler.  Programming tools changed so often back then I
> got tired to trying to keep up with it and got away from it.
>
> I am looking for hex files so I can use Xloader to update my uBITX V5
> which I recently completed.
>
> Regards,
> Dan (W3DF)
>
>
>
>
> On 2/12/20, Evan Hand <elhandjr@...> wrote:
>> Here is the github repository for the CEC software.
>> https://github.com/phdlee/ubitx/releases/tag/v1.20
>>
>> It has links to both the source code, and the .hex files.  The .hex files
>> can be installed into the ubitx Nano via USB and the Hex Loader software.
>> Hex loader is here:
>> https://sourceforge.net/projects/hex-file-loader/
>>
>> Best of luck and welcome to the group.
>> 73
>> Evan
>> AC9TU
>>
>>
>>
>>
>
>
>
>
>
>
>



--
Jack, W8TEE

Re: Collector current design point for Q911+Q912? #v6 #ubitx

barry halterman
 

Evan, I know that the value is shown as 470pf, but have you measured it in on the board, in the circuit, by any chance?
Like I said earlier, I measured it at 12nf. Someone posted that he changed the value to .01uf (10nf) and his power went up... I too have the low power syndrome with my V6. My v4 kicks butt at over 18 watts on 80 and 11 watts on 40. My V6 on 80 is 6 watts and 4 watts on 40. I don't recall the power on the higher bands.
Trying to figure out what is different in the power chain to cause such a big difference between versions.
Thanks for responding.
Barry
K3Bo

On Wed, Feb 12, 2020, 2:56 PM barry halterman via Groups.Io <kthreebo=gmail.com@groups.io> wrote:
Can someone check the capacitance of c81 in circuit and see what value you get. I get 12.nf when I go across that particular cap. Far from 470pf but then again there is other circuitry to mess with the LC meter.
Barry

On Wed, Feb 12, 2020, 11:57 AM Rick Price <rickprice48@...> wrote:
v3 Schematic shows C81 as a 0.1u
 
Rick Price
KN4AIE


From: BITX20@groups.io [mailto:BITX20@groups.io] On Behalf Of Evan Hand
Sent: Wednesday, February 12, 2020 11:52 AM
To: BITX20@groups.io
Subject: Re: [BITX20] Collector current design point for Q911+Q912? #ubitx #v6

FYI

C81 is 470pF in both the v4 and v5 boards that I have.

73
Evan
AC9TU

Re: Tuning knob behavior

Jerry Gaffke
 

I agree, I hate using an encoder switch for a select,
you often move the encoder a tick or two when you try to push it.
Also, as previously mentioned, you have to hold the rig down with the other hand. 

I'm thinking two encoders, one on each side, a microswitch low and in the middle.
A display across the top.  Nothing else on the front panel.

Rotate the left side to select a function, perhaps tuning at 1hz, 10, 100,1k, 10k, 100k, 1mhz.
Also some menus beyond that, each menu with a half dozen different menu items.
Once that is set up by the left hand, rotate the other encoder with the right hand to tune
or select a specific menu item.  To act on a menu item, hit that switch with either thumb.
Your hands never leave the encoder knobs.

If left handed, there's a menu item in there for you to swap the encoders.

The switch should be quick and sure, actuating with downward pressure
so the rig doesn't skitter across the desk.  I'm thinking one of those microswitches
with the long lever arm, the end of the lever sticking out a hole in the front panel.
After selecting the proper menu item, the switch serves as a hand key in a pinch.

Jerry, KE7ER



On Wed, Feb 12, 2020 at 05:24 PM, W2CTX wrote:

You need a better quality encoder/switch or you might wind up selecting an item above or below the one you wanted!
 
 
 
Sent from my Verizon, Samsung Galaxy smartphone
 
 
Hide quoted text

 

-------- Original message --------
From: Arv Evans <arvid.evans@...>
Date: 2/12/20 8:07 PM (GMT-05:00)
To: BITX20@groups.io
Subject: Re: [BITX20] Tuning knob behavior
 
Jerry
 
If using encoders with built-in push-buttons, that might be all that is needed. 
 
Arv
_-_
 

On Wed, Feb 12, 2020, 5:39 PM Jerry Gaffke via Groups.Io <jgaffke=yahoo.com@groups.io> wrote:
Yup, I've been thinking of doing that for several years now.
But you still need a button of some sort to actually make a menu selection.

Jerry, KE7ER

On Wed, Feb 12, 2020 at 01:58 PM, Arv Evans wrote:
Great idea.  Wish I had thought of it.  With two encoders we could probably eliminate all
the push-buttons.    8-)
 

Re: Beware running uBitx with USB connected

Ashhar Farhan
 

I have often powered up just the raduino (both :tft display version as well as the older 16x2 LCD version) with just the USB cable. It has never smoked.
In fact, our testing of raduino is done by just connecting it to the uSB of the PC.
73, f.

On Thu 13 Feb, 2020, 1:29 AM John (vk2eta), <vk2eta@...> wrote:
Hello Mike,

Sorry to hear about your problems with the uBitx.

If you are determined to part with it I am interested as I am looking for a case to house a bare V3 set.

Email is my callsign at gmail dot com.

73, John

Re: Tuning knob behavior

W2CTX
 

You need a better quality encoder/switch or you might wind up selecting an item above or below the one you wanted!



Sent from my Verizon, Samsung Galaxy smartphone


-------- Original message --------
From: Arv Evans <arvid.evans@...>
Date: 2/12/20 8:07 PM (GMT-05:00)
To: BITX20@groups.io
Subject: Re: [BITX20] Tuning knob behavior

Jerry

If using encoders with built-in push-buttons, that might be all that is needed. 

Arv
_-_


On Wed, Feb 12, 2020, 5:39 PM Jerry Gaffke via Groups.Io <jgaffke=yahoo.com@groups.io> wrote:
Yup, I've been thinking of doing that for several years now.
But you still need a button of some sort to actually make a menu selection.

Jerry, KE7ER

On Wed, Feb 12, 2020 at 01:58 PM, Arv Evans wrote:
Great idea.  Wish I had thought of it.  With two encoders we could probably eliminate all
the push-buttons.    8-)
 

Re: does KD8CEC's firmware work with V6 Ubitx?

lou_w2row
 

To the best of my knowledge the CEC software has not been changed to support the 2.8 inch touch screen display that comes with version 6 of the uBitx. If you replace the supplied display with a Nextion display, the CEC software will work just fine. 

Lou

Re: Tuning knob behavior

Arv Evans
 

Jerry

If using encoders with built-in push-buttons, that might be all that is needed. 

Arv
_-_


On Wed, Feb 12, 2020, 5:39 PM Jerry Gaffke via Groups.Io <jgaffke=yahoo.com@groups.io> wrote:
Yup, I've been thinking of doing that for several years now.
But you still need a button of some sort to actually make a menu selection.

Jerry, KE7ER

On Wed, Feb 12, 2020 at 01:58 PM, Arv Evans wrote:
Great idea.  Wish I had thought of it.  With two encoders we could probably eliminate all
the push-buttons.    8-)