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

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

John W5GFI

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

Hey Andy,

I hope you got a good night's rest. I think I have a fix! The attached hex file for me has NOT white screened EVER in my testing. Prior to this commit (f1ea1fd081d128895f336d0ca16de6246a422f2f) I'd get a successful screen render once every blue moon. Now, I have yet to get a failed screen boot. Hopefully it solves the problem on your end too.


Reed