Date   

sorry no schedule

dave <dgclifford@...>
 

Sorry guys myattempt at getting some slow morse on 40 going failed last night due to  waiting in A E for 7hours for my wife t have an emergency mri scan  until 2030 last night ( bady inflamed area around lower discs) fortunately pain killers abd anti infamatory drugs have started working  will try again thurs at 2000hrs   07.035 or thereabouts  dave c    gw0nvf


Re: low output only on 40m

MVS Sarma
 

Sorry Jim to have mis spelt tou name. 


On Wed, 5 Feb 2020, 7:43 pm MVS Sarma via Groups.Io, <mvssarma=gmail.com@groups.io> wrote:
Kim, try to trst the cut off point of theclpf and loss at say 40m mid range. 

On Wed, 5 Feb 2020, 7:22 pm Jim, <n0oct@...> wrote:
I removed L17 from the board, and measured it with my nanoVNA -- 745 nH, right about where the schematic says it should be.  The other three inductors have the same number of windings as L17.


Re: low output only on 40m

MVS Sarma
 

Kim, try to trst the cut off point of theclpf and loss at say 40m mid range. 


On Wed, 5 Feb 2020, 7:22 pm Jim, <n0oct@...> wrote:
I removed L17 from the board, and measured it with my nanoVNA -- 745 nH, right about where the schematic says it should be.  The other three inductors have the same number of windings as L17.


Re: New V5 build results and calibration issues. #ubitx-help #nextion #ubitx #calibration

Evan Hand
 

On the HF Signals BFO tunig page https://www.hfsignals.com/index.php/bfo-tuning-aid/ they list 300 Hz as the lower level for the "Plateau" and 3,000 Hz as the upper bound to center the 2,500 Hz response.  I have found the web page useful.  It also works with chrome running on both my iPad and iPhone.

The page is doing an audio spectrum analysis on the audio input from the computer/laptop.  Since I cannot see the frequency scale on your pictures I would assume that you need to be closer to the upper response (lower BFO value).

Above is for SSB voice, as I have not yet gone digital with any of my uBitx.

FWIW
73
Evan
AC9TU


Re: low output only on 40m

Jim
 

I removed L17 from the board, and measured it with my nanoVNA -- 745 nH, right about where the schematic says it should be.  The other three inductors have the same number of windings as L17.


Re: Interface to Computer #v6

Dean Souleles
 

Zac,

I have had good luck just using stereo patch cables between the PC and the UBITX. Mic to phone phone to mic. You just need to watch your levels, so that you don't overdrive either the mic input to the PC or the mic input to the UBITX. I have not had any problem with unintentional PTT using this method. I recently ran a 24-hour test using WSJTX software on WSPR and I was  heard in Antarctica in South Africa and heard stations from all around the world, so I guess it's working okay. Others prefer to use a digital interface device. There are people that sell them here on the board, but I don't really know anything about them. Others use a USB audio dongle to connect..


Good luck and have fun,
 
Dean 
KK4DAS


Re: New V5 build results and calibration issues. #ubitx-help #nextion #ubitx #calibration

Przemek
 

Hi Roman!
Could you do the video tutorial or write what to expect in the analyzer?
My results:
11.055 MHz

 
11.057 MHz
 


Re: Interface to Computer #v6

GM4CID
 

Hi Zac,

Probably be a good idea to add a series blocking capacitor, something like 100nF to stop dc from the uBitx (used to power the electret mic capsule) from reaching the PC soundcard.

73, Bob GM4CID


Re: Sensitive Mike cord

Lawrence Galea
 

Good.
Glad to help
Regards
Lawrence

On Wed, Feb 5, 2020 at 9:36 AM Maurice Bersan via Groups.Io <Vk6hly=yahoo.com@groups.io> wrote:
Problem fixed! Decoupling the Mike wires with .01 caps was the answer. Thanks Lawrence for your wisdom. Dennis, You are correct, obviously some stray rf floating around. and Arv I didn't get around to trying out your idea but thanks for your help.
Maurice


On Tue, Feb 4, 2020 at 6:04 PM, Maurice Bersan via Groups.Io
<Vk6hly=yahoo.com@groups.io> wrote:



On Tue, Feb 4, 2020 at 4:36 PM, Maurice Bersan via Groups.Io
<Vk6hly=yahoo.com@groups.io> wrote:
Thanks Arv, decoupling at the moment but will try your idea if decoupleing fails.
Maurice



On Mon, Feb 3, 2020 at 5:00 PM, Lawrence Galea
<9h1avlaw@...> wrote:
Yes

On Mon, Feb 3, 2020 at 7:30 AM Maurice Bersan via Groups.Io <Vk6hly=yahoo.com@groups.io> wrote:
Yes the cable is shielded....do you mean decouple all Mike leads to ground?



On Sun, Feb 2, 2020 at 9:28 PM, Lawrence Galea
<9h1avlaw@...> wrote:
Is the cable screened?
Try decoupling capacitors from all leads to ground
Regards
Lawrence

On Sun, Feb 2, 2020 at 7:59 AM Maurice Bersan via Groups.Io <Vk6hly=yahoo.com@groups.io> wrote:
Thanks Dennis, I did try 2 snap on ferrites at various locations and did not make any difference at all. I find the curly cord is most sensitive at the Mike end. 
I just made up a new Mike cord using straight cord not the curly type and it seems to have cured the problem, or at least vastly improved it.
Maurice


On Thu, Jan 30, 2020 at 7:28 AM, Dennis Beverage
<Sodypop@...> wrote:

Maurice,  

you probably have spurious rf carrier on your antenna feed line coming into your radio antenna hookup.  Try putting two or three snap on ferrites on the antenna lead near the radio.  You could also be generating similar signals in the shielded cable lead you said you used on the radio side of the antenna connector.  Try the same solution there.  Also, try touching those antenna leads in both locations to see if there are any changes similar to the ones your having on the mic cable.  It would seem likely there is RF floating around somewhere in proximity to your mic hook up.
--
Sodypop🤠

KJ6VGB


Re: Sensitive Mike cord

Maurice Bersan <Vk6hly@...>
 

Problem fixed! Decoupling the Mike wires with .01 caps was the answer. Thanks Lawrence for your wisdom. Dennis, You are correct, obviously some stray rf floating around. and Arv I didn't get around to trying out your idea but thanks for your help.
Maurice


On Tue, Feb 4, 2020 at 6:04 PM, Maurice Bersan via Groups.Io
<Vk6hly@...> wrote:



On Tue, Feb 4, 2020 at 4:36 PM, Maurice Bersan via Groups.Io
<Vk6hly@...> wrote:
Thanks Arv, decoupling at the moment but will try your idea if decoupleing fails.
Maurice



On Mon, Feb 3, 2020 at 5:00 PM, Lawrence Galea
<9h1avlaw@...> wrote:
Yes

On Mon, Feb 3, 2020 at 7:30 AM Maurice Bersan via Groups.Io <Vk6hly=yahoo.com@groups.io> wrote:
Yes the cable is shielded....do you mean decouple all Mike leads to ground?



On Sun, Feb 2, 2020 at 9:28 PM, Lawrence Galea
<9h1avlaw@...> wrote:
Is the cable screened?
Try decoupling capacitors from all leads to ground
Regards
Lawrence

On Sun, Feb 2, 2020 at 7:59 AM Maurice Bersan via Groups.Io <Vk6hly=yahoo.com@groups.io> wrote:
Thanks Dennis, I did try 2 snap on ferrites at various locations and did not make any difference at all. I find the curly cord is most sensitive at the Mike end. 
I just made up a new Mike cord using straight cord not the curly type and it seems to have cured the problem, or at least vastly improved it.
Maurice


On Thu, Jan 30, 2020 at 7:28 AM, Dennis Beverage
<Sodypop@...> wrote:

Maurice,  

you probably have spurious rf carrier on your antenna feed line coming into your radio antenna hookup.  Try putting two or three snap on ferrites on the antenna lead near the radio.  You could also be generating similar signals in the shielded cable lead you said you used on the radio side of the antenna connector.  Try the same solution there.  Also, try touching those antenna leads in both locations to see if there are any changes similar to the ones your having on the mic cable.  It would seem likely there is RF floating around somewhere in proximity to your mic hook up.
--
Sodypop🤠

KJ6VGB


Re: low output only on 40m

MVS Sarma
 

Can jim and curt  check the inductorcwinding turns for L17, 18 and 19 thatcwerectentatively used for 40m.

Old boards i remember overwinding thereby blocking 40m 
These coils should have 14 or max 15T

If more , make it 14, 40m improves.

On Wed, 5 Feb 2020, 9:33 am Jim, <n0oct@...> wrote:
Curt,

Did you ever get resolution on this?


Re: low output only on 40m

Jim
 

Curt,

Did you ever get resolution on this?


Re: Interface to Computer #v6

Zac T
 

Hello Reed,

I was actually looking at that second option as well by going over the schematic  of the radio.  Though I think I can dig up a sacrificial stereo cable and just cut the wire that is feeding the center of the connector.  Either option works for me.  Thank you for the response. 

Zac T. 


Re: : #V6 software issues help please #v6

Reed N
 

Glad it's working for you, John! Let me know if any issues come up.


Reed


Re: Interface to Computer #v6

Reed N
 

Hi Zac,

If you get a stereo cable, then cut the wire for the PTT, leaving the ground and mic input connected, I think that you'd get the behavior that you want?

You could also connect to the AUDIO1 port inside the radio, pin 1 for mic, 2 for ground, if you prefer. In this case, you'd need to cut a hole to get the wires out, or perhaps sneak them out the vents or some other crack.

Reed


Re: UBITX6 arrived today - cracked display

Support HF Signal
 

Hello Paul,

Glad to hear that everything's well.

Do contact us in case you have any other query.

Regards,

Thomas
--
Support@...


Interface to Computer #v6

Zac T
 

So this question has already probably been answered but I couldn't find any info on it.
I plan on running FT8/JS8 on my v6.  However, I see the pin out on the mic jack is a standard stereo connector.  Looking at the schematic, it appears the PTT works by grounding out the center of the connector to ground.  So my question is, how is everyone feeding audio into the mic jack of the Ubitx v6?  I don't plan on using ptt in the mic jack but by CAT controls, but I don't want to short out the ptt either and have the rig go into transmit. 

Thank you again and take care.


Re: Got my new V6 uBITX "Full Kit" this morning! #v6 #ubitx

Jim Sheldon
 

pborges475, I was just getting ready to answer your questions when Another Jim did it for me.  He was right on all counts.  


Two other guys and I have a rather loose knit group we call the “Triumvirate Skonk Worx” or TSW for short.  Our website is www.w0eb.com and all the info you asked for can be found there.

Jim Sheldon, W0EB
TSW Project Coordinator


Re: uBITX VFO Encoder

Ted
 

Adrian,


I came across 3 or 4 optical encoders on my day job that convert nicely to work with a uBitx..... in theory. That is, I've tested one of them but have gone no further as yet.  In their original use, they pulse out 5V in overlapping sequence in the same way the uBitx encoder pulses out earth contacts in a similar overlapping sequence.  In order to make these mimick a uBitx encoder, It was necessary to have the two output terminals feed a transistor on each output wire that in turn grounds the positively-charged uBitx encoder wires. In other words, the rotary knob outputs in positive logic which in turn shunt open collectors to earth, thus effectively outputting in negative logic & doing exactly what the original encoder does to the encoder wires. 

Before one can use this, though, one will have to change the firmware to reflect use of a few hundred closures per revolution instead of a few dozen per revolution. As it is, the optical encoder over-runs the processor's ability to follow the pulses with only a moderate spin of the knob even at 10hz resolutuon. A slow turn works fine. 

I'll go and use this in my next, or third, uBitx build. I first have to decide what sort of form to make this one into and how to include some ancient (1970's - 1980's) analog meters salvaged from a tape player or two.


Good luck,

Ted
K3RTA






On Tue, Feb 4, 2020 at 13:23, Adrian Rees
<rees.a@...> wrote:

Hi

I would like to buy some of the encoders used in the uBITXfor other projects I have. Does anyone know the make & model ? I want exactly the same encoders because they don't have that annoying click-stop.

Alternatively if anyone has managed to get a proper optical encoder working with the software, I would really like to hear about that.

Thanks

Adrian M1LCR




2 Firmware Versions?? #v5 #firmware

Brad, K7NNR
 

I recently bought a v5 un-assembled.  After a few days of assembly I immediately updated the firmware to CEC 1.2.  Now when I power the radio is quickly displays what seems to be 2 software versions like below

uBITX v0.20
+v1.200

Is this normal?