Date   
Re: WSJT-X Split Operations #ft8 #ubitx

dwhacks
 

I know this is a super old thread, but does anyone know anything about fixing the split mode with KD8CEC firmware? Or am I not understanding something. When using Rig split mode in WSJT-X, VFO a becomes the same as VFO B after transmit.

V5 reprogram.

ronldt@...
 

Where can I d/l te\h software for a V5 reprogram?

Re: UBITX6 arrived today - cracked display

Jack, W8TEE
 

Reed:

When I did an Antenna Analyzer build for our builder's group, I ordered 30 2.8" TFT displays, of which 11 arrived cracked. I wrote to the seller and, while unhappy, they replaced them. (They were in China.) Oddly, the displays still worked. They were not touch screen, so that might make a big difference, but for just display stuff, they all worked. In most of them, the crack was barely noticeable once they were "lit".

I find it odd that they came in a gray poly bag rather than a cardboard container. Now I'm starting to think that, when it gets opened for inspection by Customs, they take a look at whatever it is and then just toss it in a bag and send it along its way. I could be totally wrong, but the vendor said they were packed in a box.

Anyway, don't throw the display away, as you might still be able to "experiment" with it.

Jack, W8TEE

On Monday, January 20, 2020, 9:26:29 PM EST, Reed N <greenkid336600+groupsio@...> wrote:


Hi Paul,

I read a number of specs for similar looking panels and some said 3.3v, and some said 5v tolerant, so it might be that you got a 3.3v only?

What specific code did you try and run?


Reed

--
Jack, W8TEE

Re: OK, what I do wrong? 20M QCX

Curt
 

Leon

There is an adjustment pot there, both ubitx and qcx, maybe most lcd units. Many of us were slow to figure this out.

Curt

Re: [BITxV6] BRICKED recovery help needed

Andy_501
 

Thanks for f/b Jerry,

that lag due to display update might well be something to investigate as when CW is selected as mode the key down cause the TX button to light then the RF appears at the output so clearly that is a lag possibility. I would have to compare the sequence of events using one of the iambic keyer inputs to see if the lag exists using the raduino keyer TX control as opposed to the PTT on the mic line.

It is hard to imagine a class of basic hams trying to study to upgrade to advanced levels having to go through this much trouble with a practical kit before they can focus on course theory for an exam.


Step 2 I just manually adjusted  the BFO freq so that I had the best sounding audio from the two time signal stations in the headset but could not zero beat or adjust it for  a zero difference point so no tone was audible over the received signal tones.

On 2020-01-20 2:28 p.m., Jerry Gaffke via Groups.Io wrote:
Andy,

I'm not quite sure I understand your first and second bullet points.
But then I'm not familiar with the firmware you are using.
So feel free to disregard these comments in they seem wrong.



1. I am unable to set the ref FREQ to 10 000 ; the closest is 10500

A 500khz error at 10mhz is an awful a lot, that's 50000 ppm
You might use a shortwave receiver to verify that the Si5351 crystal reference oscillator
is operating within perhaps 400ppm of 25.0mhz, so within 10khz
Probably somewhat high, as the crystal loading capacitance on the Raduino is too low. 

2. ... The zero beat adjustment allows me to hear the signals and voice components/announcements but continuously has approx a 500 Hz tone superimposed on the time signals which appears as though it might be due to the freq setting from step 1. not working as text instructions state it to be set.

You lost me.  Is it 500khz or 500hz?
At any rate, if the calibration step for the 875mhz vco advances in 875hz steps (so 1ppm), you should be able to get it within 10hz.
The operating frequency is always a ratio of the 875mhz vco, and thus any error in the operating frequency is that same ratio
of any error in the 875mhz vco.

the lag between key down and RF output is serious problem 

Got to be a firmware issue, perhaps due in part to the slow display if they are trying to update the display when the key goes down.
Not everybody here uses CW much, including those writing the firmware.
The uBitx is primarily an SSB rig, but there has been firmware that works well enough on CW.

Jerry, KE7ER



On Mon, Jan 20, 2020 at 07:12 AM, Andy_501 wrote:

Hi Reed,

I finally managed to get your arduino hex file uploaded into the nano and the display back to what appears to be normally visible. The 17M selection is working properly, albeit sluggishly,  with this version also.

I managed to get the test menu to work also somewhat sluggishly.

1. I am unable to set the ref FREQ to 10 000 ; the closest is 10500

2. The zero beat adjustment adjusts above and below but does not produce a zero beat state. The receiver works and I am able to hear WWV on  2.5 MHz and CHU Canada on 3.330 MHz The zero beat adjustment allows me to hear the signals and voice components/announcements but continuously has approx a 500 Hz tone superimposed on the time signals which appears as though it might be due to the freq setting from step 1. not working as text instructions state it to be set.

3. I am able to select Hand Key setting and in CW mode it outputs the full 10 Watts on 80 M band on key down; however if I key a test transmission at about 10-12 wpm with the hand key the lag between key down and RF output is serious problem (no setting of key delay helps improve). It is so bad I would not be able to use it for CW operation. I plug the hand key into the Mic jack and have the key control the PTT; in CW mode it generates CW sidetone signal but hand key does not work when plugged into the J4 Morse Jack at all.

4. Changing modes using the color display buttons and a stylus works but it also exhibits serious delays and even sometimes requires selecting the new band a second or third time to finally get it to change. It is almost as if the morse code hand keying and TFT screen servicing routines get hung up in an idle code loop delay of some sort that makes the overall operation seem sluggish or seriously lagged or unresponsive/insensitive.

But on the plus side The BRICKED white screen appears to have been cleared up; The only other possibility is that the TFT/nano daughterboard pair has a problem that is creating the sluggish performance; and HFSignals promised replacement has not been sent to me and thus I am unable to compare it with a supposed new one. They promised on two separate emails to send me a replacement however have not so far lived up to that promise.

Any suggestions now Reed?

Thanks for the hex file download

Andy

Re: BFO update

Andy_501
 

My unit came with only one jack with the 2.2K resistor and a 10 K resistor connected to the Tip and Ring with the J4 sleeve ground. I don't have an extra 2nd jack installed in mine connected with Tip Sleeve providing a direct ground to the keyer input pin. The only description I had wrt straight key was to use the Mic connection and connect the hand key to the PTT line which is different point than the keyer line and might definitely be a source of aggravation lag from key down to RF output timing.

On 2020-01-20 2:09 p.m., John Schlosser via Groups.Io wrote:
Andy, here is a link to the wiring diagram for both straight key and paddle, I have a jack for each.



John W5GFI

Re: #ubitx #v6 Internal Microphone wiring on provided hand mic #v6 #ubitx

AndyH
 

On Mon, Jan 20, 2020 at 06:39 PM, Smitty, KR6ZY wrote:
Having said that, my uBitX doesn't want to put out power on SSB.  I key up, but my meter doesn't register any power.  If I key up CW, it registers power just fine.  But not on SSB.  
Mark,

   Are you talking into the mic when you press PTT on SSB?  The radio won't generate an output signal without sound going into the mic.

   Fingers crossed!
    Andy KG5RKP

Re: UBITX6 arrived today - cracked display

Reed N
 

Hi Paul,

I read a number of specs for similar looking panels and some said 3.3v, and some said 5v tolerant, so it might be that you got a 3.3v only?

What specific code did you try and run?


Reed

Re: OK, what I do wrong? 20M QCX

Leon Bishop
 

my bad


From: "Evan Hand" <elhandjr@...>
To: "BITX20" <BITX20@groups.io>
Sent: Monday, January 20, 2020 7:23:14 PM
Subject: Re: [BITX20] OK, what I do wrong? 20M QCX

If you have an issue with a QRP Labs WCX, you have the wrong forum. That would be the QRPlabs group. 

Re: OK, what I do wrong? 20M QCX

Evan Hand
 

If you have an issue with a QRP Labs WCX, you have the wrong forum. That would be the QRPlabs group. 

Re: #ubitx #v6 Internal Microphone wiring on provided hand mic #v6 #ubitx

Mike WA0YCN
 

Here’s a picture of the stock Baofeng microphone I use on my v5 before I connected it. 


I removed the capacitor (C2) and resistor (R1) between the (positive) electret microphone lead and ground - these are not needed (or wanted). Then I connected red for mic, yellow for PTT, and blue for ground. Green has no connection.


Also, these wires are extremely fragile - if you’re not having any voice modulation, you might check continuity from the solder point of the red wire and the tip of the plug. 

OK, what I do wrong? 20M QCX

Leon Bishop
 

I completed the 20 M QCX!  When I applied power, nothing but a row of white blocks!  Can someone point in a direction to check something?
73,
Leon N5PU

Re: #ubitx #v6 Internal Microphone wiring on provided hand mic #v6 #ubitx

joshuaclough@...
 

I'm also curious about the wiring...
Is the included mic a stock Baofeng mic or has it been modified for the ubitx?

#ubitx #v6 Internal Microphone wiring on provided hand mic #v6 #ubitx

Smitty, KR6ZY
 

Can someone tell me how their hand mic is wired, the one provided with the uBitX v6?  It looks like the speaker is in series with the ground wire on mine, and I'm trying to figure out if that's expected.

There's a board inside the hand mic.  It has terminals for Mic, PTT, GND, and Spk.  The mic connector on the uBitX doesn't have speaker signals, so we care about the Mic, PTT and GND.  The 3.5mm TRS mic connector should be wired as:
  • Tip: Mic, red wire
  • Ring: PTT, black wire
  • Sleeve: GND, white wire
In my speaker mic, the GND terminal is connected to a green wire, which is cut-off inside the 3.5mm connector, it doesn't go anywhere.  Instead, the white wire is connected to the Spk terminal.  The other side of the speaker is connected to ground.

For PTT, this just effectively adds about 8 to 16 ohms to the ground side, but against the 10k-ish pull-up on the other side, its still plenty low to register.  So PTT works fine.

But this also puts 8 to 16 ohms in series with the mic signal.  Looking at the mic circuit in the uBitX schematic, that shouldn't matter TOO much.  The rest of the circuit is 4.7k, 2.2k, and 10k.  So 16 ohms should be noise floor compared to those impedances.

Having said that, my uBitX doesn't want to put out power on SSB.  I key up, but my meter doesn't register any power.  If I key up CW, it registers power just fine.  But not on SSB.  I don't THINK this is the cause, but I'm putting the question out to see if anyone else is having a similar problem, or whether their mic is similarly wired.

Thanks!

73 de KR6ZY
-Mark

Re: [BITxV6] BRICKED recovery help needed

Jerry Gaffke
 

Andy,

I'm not quite sure I understand your first and second bullet points.
But then I'm not familiar with the firmware you are using.
So feel free to disregard these comments in they seem wrong.



1. I am unable to set the ref FREQ to 10 000 ; the closest is 10500

A 500khz error at 10mhz is an awful a lot, that's 50000 ppm
You might use a shortwave receiver to verify that the Si5351 crystal reference oscillator
is operating within perhaps 400ppm of 25.0mhz, so within 10khz
Probably somewhat high, as the crystal loading capacitance on the Raduino is too low. 

2. ... The zero beat adjustment allows me to hear the signals and voice components/announcements but continuously has approx a 500 Hz tone superimposed on the time signals which appears as though it might be due to the freq setting from step 1. not working as text instructions state it to be set.

You lost me.  Is it 500khz or 500hz?
At any rate, if the calibration step for the 875mhz vco advances in 875hz steps (so 1ppm), you should be able to get it within 10hz.
The operating frequency is always a ratio of the 875mhz vco, and thus any error in the operating frequency is that same ratio
of any error in the 875mhz vco.

the lag between key down and RF output is serious problem 

Got to be a firmware issue, perhaps due in part to the slow display if they are trying to update the display when the key goes down.
Not everybody here uses CW much, including those writing the firmware.
The uBitx is primarily an SSB rig, but there has been firmware that works well enough on CW.

Jerry, KE7ER



On Mon, Jan 20, 2020 at 07:12 AM, Andy_501 wrote:

Hi Reed,

I finally managed to get your arduino hex file uploaded into the nano and the display back to what appears to be normally visible. The 17M selection is working properly, albeit sluggishly,  with this version also.

I managed to get the test menu to work also somewhat sluggishly.

1. I am unable to set the ref FREQ to 10 000 ; the closest is 10500

2. The zero beat adjustment adjusts above and below but does not produce a zero beat state. The receiver works and I am able to hear WWV on  2.5 MHz and CHU Canada on 3.330 MHz The zero beat adjustment allows me to hear the signals and voice components/announcements but continuously has approx a 500 Hz tone superimposed on the time signals which appears as though it might be due to the freq setting from step 1. not working as text instructions state it to be set.

3. I am able to select Hand Key setting and in CW mode it outputs the full 10 Watts on 80 M band on key down; however if I key a test transmission at about 10-12 wpm with the hand key the lag between key down and RF output is serious problem (no setting of key delay helps improve). It is so bad I would not be able to use it for CW operation. I plug the hand key into the Mic jack and have the key control the PTT; in CW mode it generates CW sidetone signal but hand key does not work when plugged into the J4 Morse Jack at all.

4. Changing modes using the color display buttons and a stylus works but it also exhibits serious delays and even sometimes requires selecting the new band a second or third time to finally get it to change. It is almost as if the morse code hand keying and TFT screen servicing routines get hung up in an idle code loop delay of some sort that makes the overall operation seem sluggish or seriously lagged or unresponsive/insensitive.

But on the plus side The BRICKED white screen appears to have been cleared up; The only other possibility is that the TFT/nano daughterboard pair has a problem that is creating the sluggish performance; and HFSignals promised replacement has not been sent to me and thus I am unable to compare it with a supposed new one. They promised on two separate emails to send me a replacement however have not so far lived up to that promise.

Any suggestions now Reed?

Thanks for the hex file download

Andy

Re: BFO update

John Schlosser
 

Andy, here is a link to the wiring diagram for both straight key and paddle, I have a jack for each.



John W5GFI

Re: UBITX6 arrived today - cracked display

Paul G8KIG
 

Hi again,

First of all a data point: The cracked display meant that the touch screen did not work causing what seemed to be a lockup.
Therefore I purchased a replacement display it is identical in every way to the original one apart from one thing. It only displays a white screen, no graphics.
On the basis that it could be the initialisation bug discussed in the forums, I compiled and uploaded the firmware with the fix to the Raduino (successfully).
I still get the white screen. With the new display I turned the volume to maximum and heard birdies and whistles so lots seem to be working - this did not happen with the original display. I also have an 1.8" display with the same controller (used on a Raspberry Pi) - and the same pin out; plugging that in displays something. I think I got a duff replacement display so will order another one. Looking around I get the impression that the IL19341 controller operates on 3.3v but I noticed that the Raduino uses 5v. I can't track down a data sheet so I was just checking that 5v is OK.

Paul G8KIG

Re: Relative Power indication on Nextion display

Mike WA0YCN
 

Dan,

Thanks for the info.  To this point, I have only used .hex files in the Raduino.  I need to successfully compile and build a version, and will definitely include your code.  When I do, I'll see if I can figure anything out about it not displaying for CW.

I'm still experiencing infrequent times where the S-meter is frozen mid-scale.  Have you run into that?

Regards,

Mike

Re: [BITxV6] BRICKED recovery help needed

Reed N
 

Hi Andy,

I'm glad to hear it fixed your white screen problem. I've made some changes to the code since then, and can get you an updated binary if you can't compile yourself, though I don't know that it will solve any of your specific issues.

1) the stock code changed the LO in steps of 875Hz, which is ~1ppm, since the PLL target is 875MHz. I know that my setup is also slightly off of zerobeat, but I figured "close enough" and left the step size as is. I could make the step smaller, but then you'd have to do a lot more turning. I'm hoping to get a "momentum" thing built in to the encoder, so if I get that in place, I can drop all the step sizes without sacrificing speed of tuning.

2) This is quite likely due to the step size of the cal

3) A couple other threads have mentioned issues with keying, so you're not alone. I haven't looked into improving those functions at all, so I can't comment as to how easy or hard a fix might be.

4) I haven't experienced much, if any, lag on my touch inputs recently, but I know that if it's not well calibrated, it will drop inputs because it will think you're pressing where no buttons are. If you haven't already, remove the protective film that shipped covering the screen. Try recalibrating the touch screen using the stylus, even if you plan on operating using your fingers, and see if that helps.


Reed

updated software

dave
 

hello given there are a few different sets of software for the ubitx v5 whatare the latest that are available and from who  many thanks   dave c gw0nvf