Re: Si5351A Synth kit board Rev 5 now available, fits TCXO module
Is the progrock happy to run with the 25Mhz TXCO module in the si5351 synth? Simon, I'd guess so. I use 26MHz TCXOs in most of my QRPLabs gear including Progrock. 73 Alan G4ZFQ
|
Re: Si5351A Synth kit board Rev 5 now available, fits TCXO module
Is the progrock happy to run with the 25Mhz TXCO module in the si5351 synth?? I couldn't find anything in the progrock manuals on this other than a reference to how to manually program the reference frequency for the progrock but it only mentions 27mhz frequencies.
73
Simon
VK3ELH
|
Re: Order "in transit" at Grace-Hollogne for 3 weeks?
Thank you Curt and Ian for your input.? As it turns out, when I looked this morning, I got this message:
| 09/11/2021, 21:04 |
? |
Formal customs clearance required |
So it appears to be some movement.? What it means, I do not know but...at least something is happening.
Kent.
|
I get Ts all the time just listening. Noise seems to produce Ts if the code reader is turned on.
David J. Wilcox¡¯s iPad
toggle quoted message
Show quoted text
On Nov 9, 2021, at 4:05 PM, Jim Campbell <jecspasc@...> wrote:
?I built my QCX+ some time ago. When completed the power out was approximately 3 watts. Recently I decided to get it up to 5 watts with a 13.6 volts DC supply. After taking 3 turns off L3 I achieved my goal. After putting my covers back on the QCX+ I discovered I had no RF out. Going back through the Menu settings I found a few things amiss so I corrected them. When I did a save configuration I got an "0 7 0 7" on the bottom right of the screen. I cycled power and got a "T" on the bottom right of the screen and then another "T" with a space between them several seconds later. This continued till I powered the QCX+ off.
I did a cursory pass through the documentation looking for error codes but was unable to find any. Can some kind soul tell me where they might be found?
Thanks es 73,
Jim - W4BQP since 1953
|
Im still ground testing your Lora pico tracker with no problems.
Im going to continue test using a car and solar power only Can i please test your python script to transfer telemetry to the other online tracker
regards
richard
|
Re: QDX CAT Control Issue?
Hans,
that looks like an Ubuntu desktop, rather than Windows! Possibly 20.04 default desktop background, but it's hard to be sure. As for serial comms, and emulations thereof, it's all Dark Arts, even if we don't need/can't use the serial breakout box!
Yours having a nervous breakdown,
Robin, G8DQX
toggle quoted message
Show quoted text
On 10/11/2021 08:49, Hans Summers wrote: Thanks Ross
I have added this to the manual <>
I do not see why this should make any difference because it should not be required on a Virtual COM port where start, stop bits etc are of no relevance (it is USB comms not real serial. However... if it improves things for Windows users, why not :-D? ?We don't have to understand it. Windows moves in mysterious ways.
73 Hans G0UPL
<>
|
Or, perhaps, try 2021-11-10! (Unless you're H. G. Wells' time traveller, in civvies!)
73,
Robin, G8DQX
toggle quoted message
Show quoted text
On 10/11/2021 03:32, Hew Lines wrote:
Make that date "Nov 11"? !!
On 11/9/2021 6:32 PM, Hew Lines wrote:
Many thanks Hans. It finally arrived yesterday Oct (10). in perfect shape.
Just FYI, this email from you was the only shipping/tracking document I got so that process got messed up somehow.
After coffee, my next job is to download all documents. Are there any new ones or any change listings as well yet ?
Thanks again,
73 Hew VA7HU
|
QDX issues: please include info:
#qdx
Hi all
I'm seeing a growing number of reports from people happily using their QDX and making QSOs.?
Personally?I am quite enjoying JS8Call. This morning?I had a nice QSO with YO3FVR on 40m JS8Call (875km distance), two-way QRP, me on QDX and him on FT817 to a random wire. JS8Call is a chat mode that utilizes the underlying communication protocol of FT8. His SNR varied wildly from -9 to -21 and I missed some transmissions. We both changed to "slow" mode where the transmission slots are 30s rather than 15s and I did not lose any "packets" after that.?
JS8Call is fun and I prefer a real chat; but it is nowhere near as much activity as FT8. I have set mine up so that if it notices any incoming directed messages to me, or any general CQ call, then it plays a sound on my PC to alert me. It's much like receiving an incoming email, WhatsApp message, Facebook IM message, Telegram or Signal message - all of which also make an alert sound. But with JS8Call it's radio, not internet :-D?
Anyway - those of you in less happy situations, having QDX issues: in general, when reporting any issues on QDX it would be very helpful if everyone includes information as follows, that will help us to spot any trends, and more efficiently learn troubleshooting issues: - What?OS you are running, including what version of MS Windows, or what flavor of Linux. Remember?that Linux, Mac and MS Windows 10 users do not need any driver installs, but earlier MS Windows users will need to install a Virtual COM Port driver as described in the QDX manual.?
- What QDX firmware version you are running; preferably if you have any issue, it would be best to make sure you are using the latest firmware at and see if the problem persists.?
- Whether you built the QDX for 12V operation (output transformer 3:2) or for 9V operation (output transformer 3:3).
- What power supply you are using: voltage, current capability, and whether it is? a Linear or Switched Mode type.
- Now everyone has Rev 1 PCBs, but in future when Rev 2 comes along, please also state what PCB revision you have.?
- Also state any deviations you intentionally made from the manual. We may need to know about your deviations? :-/?
73 Hans G0UPL
|
Re: Thoughts on protecting BS170s in QDX
Hi all
I think over-voltage BS170s on QDX are a lot less likely?than on QCX (where I have never experienced it myself, either) - because Class-E is a lot more sensitive to this and because QDX is operating push-pull Class-D, the voltages should be a lot less.?
If the 180-degree phase relationship broke down due to some Si5351A issue, I am not sure whether this would cause a problem or not. For example - what happens if Clk0 and Clk1 are in phase. To be sure, each set of BS170s is still switching at the operating frequency correctly. However, now the output transformer will be all wrong... won't the RF from each half now be in-phase and the output transformer will be seeking?to annihilate the two halves, not reinforce them? Anyway, I think this is very unlikely.?
A bigger problem has been ways to get the Si5351A to output DC rather than anything sensible at all. DC will certainly destroy BS170s as they will pass a very high current.?
Several people found ways to cause the Si5351A to output DC: - Configuration via WSJT-X of a band that the QDX cannot support
- Entering a very incorrect reference oscillator value in the QDX Config screen - for example by missing off one of the digits entirely.?
Both of these have now been resolved via firmware updates. So please make sure you use the latest QDX firmware version published at ?
73 Hans G0UPL
It is certainly worth some experimental effort. Somehow it needs to detect severe stress while not false alarming too often, as in FT modes quite annoying when rig decides not to transmit. I have many rigs with bs170 finals, zero failures but all these are Morse cw.?
Failure of si5351?? Perhaps you mean error in its quadrature.?
I don't know if this complexity makes sense versus reasonable derating of PA bias. One of my rigs did suggest some diodes to drop PA bias voltage, but I didn't do that. But for digital modes it may make sense to back down PA bias voltage.?
Curt
|
Re: QDX CAT Control Issue?
Thanks Ross
I have added this to the manual
I do not see why this should make any difference because it should not be required on a Virtual COM port where start, stop bits etc are of no relevance (it is USB comms not real serial. However... if it improves things for Windows users, why not :-D? ?We don't have to understand it. Windows moves in mysterious ways.?
73 Hans G0UPL
On Wed, Nov 10, 2021 at 6:54 AM Afghan Kabulldust via <kabulldust= [email protected]> wrote: Hello all, I have a nice new QDX that, at times, is working very well, however, firstly I would get an odd startup screen in WSJTX, as attached, and the CAT would sometimes not transmit. I did some research on Kenwood CAT protocol and found it prefers the attached setup, not ¡°Default¡±
Data bits 8
Stop bits 1
Handshake none
I¡¯ve had fewer CAT issues since of set these params.
73
Ross
EX0AA
|
Re: A couple QDX questions: 60 meters? & 9v vs 12v
I have not tried it myself. In fact my WSJT-X does not even show 60m as an option, Hans, This is done because of the various different frequencies in use worldwide. Adding frequencies is easy. John AE5X reported good 60m results, and good low enough harmonic levels My crude tests seem to give good results. The way? Just enter the frequency you want in WSJT_X (See manual, frequency tab.) and select it. Is it "legal", I think that is a tricky question... Yes... 73 Alan G4ZFQ
|
Re: Troubleshooting DOA QDX
#qdx
On Tue, Nov 9, 2021 at 09:41 PM, Fred Spinner wrote:
been warned not to talk about my microcontroller work as a kid with Z80s and 8051s
8051s, no.? Z80s, yes.? And? 6502s, and 6800s!
|
Re: A couple QDX questions: 60 meters? & 9v vs 12v
1)?I know it¡¯s not designed to but can you set up a QDX to run on 60 meters? ( and of course, is yes, then how? )
( and also of course is it ¡°legal¡± to do so ? )
I have not tried it myself. In fact my WSJT-X does not even show 60m as an option, and neither does my JS8Call. Maybe I am not running the latest versions, and latest versions do, I don't know.?
John AE5X reported good 60m results, and good low enough harmonic levels measured on his spectrum analyzer:? ?
Is it "legal", I think that is a tricky question... not only does it depend on where you are located, but interpretation?of the rules differs. Someone on hear said the other day that ARRL is not recommending FT8 on 60m in US. Though someone else said lots of people are doing it anyway.?
73 Hans G0UPL
|
A couple QDX questions: 60 meters? & 9v vs 12v
1)?I know it¡¯s not designed to but can you set up a QDX to run on 60 meters? ( and of course, is yes, then how? )
( and also of course is it ¡°legal¡± to do so ? )
2) is there a way for this list/site to be set up to poll how many builders chose 9v and how many picked 12v?
Impression: seems like most are picking 12 volts, my guess is already having 12v, or near 12volt, supplies already at hand and less chance grabbing the wrong one. But... also have the impression that 9 volts is, perhaps, more efficient so maybe a better portable choice. An 8 cell AA holder with 1.2 volt ni metal hydrides make a pretty good rechargeable ~9v source.
73/72 jt aa1of
|
Re: Troubleshooting DOA QDX
#qdx
Hi Fred
Z80 is fine... only maybe we mark the topic OT hi hi. I learned on Z80s see?
73 Hans G0UPL
Well I kinda actually did know most of that but I think Brent would not have gotten to the reflowing part if I said it all! :)?
I need to break out my blue pills and Nucleo Boards again some time.? I am getting rusty in my memory for all this stuff.? But I find the STM32s to be great fun.? I have already been warned not to talk about my microcontroller work as a kid with Z80s and 8051s here in a previous post but these processors are the end result of what we dreamed of back then.? I get much more out of them than say a Raspberry?Pi running Linux.?
Hell the level of DSP you can get out of these rivals FPGAs in the early days...?
Fred W0FMS?
Nice!?
FYI the STM32 sort of CAN function without a clock. At least, without an external one. I'm not being pedantic, the details are interesting. To me anyway.?
On an ATmega328 as used in QCX, the decision on whether to use the internal 8MHz RC oscillator or an external clock or a crystal, is made at code-flashing time by how you choose the fuse bytes.
But on STM32 the clock configuration is rather complex. It is done at runtime, normally at the start of the program. STM32 always boots up on the internal 8MHz RC oscillator, then early on in the initialization code you write some stuff that configures it to use an external clock. You also have to configure the PLL and dividers etc such that for example, in the case of QDX, everything is set up such that the USB peripheral is clocked at 48MHz (slightly off in fact, but well within spec), and the I2S ADC master clock is at 24.576MHz (being 512 times the 48ksps sample rate... And also slightly off frequency but again well within spec). The processor speed isn't critical but in QDX runs at a little over 72MHz which is just how the numbers fall out after concentrating on getting USB and I2S communications clocks correct.?
But the story doesn't stop there. In the case of ATmega328, when the fuses set it up for a 20MHz crystal (example, QCX) and if the 20MHz crystal isn't there, the processor just sits and plays dead. But on STM32, if there is a problem with the external clock then it falls back automatically to use the internal 8MHz RC oscillator. However, then nothing will run at the right speed which means USB won't connect either.?
Probably what happened in Brent's case was the 25MHz TCXO had a soldering issue, so the STM32 didn't get 25MHz but fell back to its 8MHz... Which would also account for the slow flashing LED (all timing being wrong at 8MHz). -------- Original message -------- From: Fred Spinner < fred.spinner@...> Date: Wed, Nov 10, 2021, 7:58 AM To: [email protected]Subject: Re: [QRPLabs] Troubleshooting DOA QDX #qdx Whoo hoo!? I do troubleshooting for a living as a test engineer and I am extremely happy to actually get one right this week!? Glad it helped you!?
Fred W0FMS?
On Tue, Nov 9, 2021, 8:31 PM Brent WT4U < brentm@...> wrote: Thanks Fred! Aparently that?was it. Reflowed those joints and gave it power and the LED woke up and the computer recognized the sound card. Waterfall full of stations.?
Now it's past my bedtime and I'm going to have to wait until tomorrow to play with it!
73,
¨CBrent WT4U
|
Re: Troubleshooting DOA QDX
#qdx
Well I kinda actually did know most of that but I think Brent would not have gotten to the reflowing part if I said it all! :)?
I need to break out my blue pills and Nucleo Boards again some time.? I am getting rusty in my memory for all this stuff.? But I find the STM32s to be great fun.? I have already been warned not to talk about my microcontroller work as a kid with Z80s and 8051s here in a previous post but these processors are the end result of what we dreamed of back then.? I get much more out of them than say a Raspberry?Pi running Linux.?
Hell the level of DSP you can get out of these rivals FPGAs in the early days...?
Fred W0FMS?
Nice!?
FYI the STM32 sort of CAN function without a clock. At least, without an external one. I'm not being pedantic, the details are interesting. To me anyway.?
On an ATmega328 as used in QCX, the decision on whether to use the internal 8MHz RC oscillator or an external clock or a crystal, is made at code-flashing time by how you choose the fuse bytes.
But on STM32 the clock configuration is rather complex. It is done at runtime, normally at the start of the program. STM32 always boots up on the internal 8MHz RC oscillator, then early on in the initialization code you write some stuff that configures it to use an external clock. You also have to configure the PLL and dividers etc such that for example, in the case of QDX, everything is set up such that the USB peripheral is clocked at 48MHz (slightly off in fact, but well within spec), and the I2S ADC master clock is at 24.576MHz (being 512 times the 48ksps sample rate... And also slightly off frequency but again well within spec). The processor speed isn't critical but in QDX runs at a little over 72MHz which is just how the numbers fall out after concentrating on getting USB and I2S communications clocks correct.?
But the story doesn't stop there. In the case of ATmega328, when the fuses set it up for a 20MHz crystal (example, QCX) and if the 20MHz crystal isn't there, the processor just sits and plays dead. But on STM32, if there is a problem with the external clock then it falls back automatically to use the internal 8MHz RC oscillator. However, then nothing will run at the right speed which means USB won't connect either.?
Probably what happened in Brent's case was the 25MHz TCXO had a soldering issue, so the STM32 didn't get 25MHz but fell back to its 8MHz... Which would also account for the slow flashing LED (all timing being wrong at 8MHz). -------- Original message -------- From: Fred Spinner < fred.spinner@...> Date: Wed, Nov 10, 2021, 7:58 AM To: [email protected]Subject: Re: [QRPLabs] Troubleshooting DOA QDX #qdx Whoo hoo!? I do troubleshooting for a living as a test engineer and I am extremely happy to actually get one right this week!? Glad it helped you!?
Fred W0FMS?
On Tue, Nov 9, 2021, 8:31 PM Brent WT4U < brentm@...> wrote: Thanks Fred! Aparently that?was it. Reflowed those joints and gave it power and the LED woke up and the computer recognized the sound card. Waterfall full of stations.?
Now it's past my bedtime and I'm going to have to wait until tomorrow to play with it!
73,
¨CBrent WT4U
|
Re: Troubleshooting DOA QDX
#qdx
Nice!?
FYI the STM32 sort of CAN function without a clock. At least, without an external one. I'm not being pedantic, the details are interesting. To me anyway.?
On an ATmega328 as used in QCX, the decision on whether to use the internal 8MHz RC oscillator or an external clock or a crystal, is made at code-flashing time by how you choose the fuse bytes.
But on STM32 the clock configuration is rather complex. It is done at runtime, normally at the start of the program. STM32 always boots up on the internal 8MHz RC oscillator, then early on in the initialization code you write some stuff that configures it to use an external clock. You also have to configure the PLL and dividers etc such that for example, in the case of QDX, everything is set up such that the USB peripheral is clocked at 48MHz (slightly off in fact, but well within spec), and the I2S ADC master clock is at 24.576MHz (being 512 times the 48ksps sample rate... And also slightly off frequency but again well within spec). The processor speed isn't critical but in QDX runs at a little over 72MHz which is just how the numbers fall out after concentrating on getting USB and I2S communications clocks correct.?
But the story doesn't stop there. In the case of ATmega328, when the fuses set it up for a 20MHz crystal (example, QCX) and if the 20MHz crystal isn't there, the processor just sits and plays dead. But on STM32, if there is a problem with the external clock then it falls back automatically to use the internal 8MHz RC oscillator. However, then nothing will run at the right speed which means USB won't connect either.?
Probably what happened in Brent's case was the 25MHz TCXO had a soldering issue, so the STM32 didn't get 25MHz but fell back to its 8MHz... Which would also account for the slow flashing LED (all timing being wrong at 8MHz).
73 Hans G0UPL http://qrp-labs.com
-------- Original message -------- From: Fred Spinner <fred.spinner@...> Date: Wed, Nov 10, 2021, 7:58 AM To: [email protected]Subject: Re: [QRPLabs] Troubleshooting DOA QDX #qdx Whoo hoo!? I do troubleshooting for a living as a test engineer and I am extremely happy to actually get one right this week!? Glad it helped you!?
Fred W0FMS?
On Tue, Nov 9, 2021, 8:31 PM Brent WT4U < brentm@...> wrote: Thanks Fred! Aparently that?was it. Reflowed those joints and gave it power and the LED woke up and the computer recognized the sound card. Waterfall full of stations.?
Now it's past my bedtime and I'm going to have to wait until tomorrow to play with it!
73,
¨CBrent WT4U
|
Re: Troubleshooting DOA QDX
#qdx
Whoo hoo!? I do troubleshooting for a living as a test engineer and I am extremely happy to actually get one right this week!? Glad it helped you!?
Fred W0FMS?
On Tue, Nov 9, 2021, 8:31 PM Brent WT4U < brentm@...> wrote: Thanks Fred! Aparently that?was it. Reflowed those joints and gave it power and the LED woke up and the computer recognized the sound card. Waterfall full of stations.?
Now it's past my bedtime and I'm going to have to wait until tomorrow to play with it!
73,
¨CBrent WT4U
|
Re: OT: Congratulation JackW8TEE
Congratulations Jack.... I may have to subscribe.? I've always liked CQ Magazine but usually had to choose between ARRL or CQ.? maybe now is the time in my life i should do both.? Now, gotta run that logic past the finance director (wife).? But anyhow, it's cool to know you here in the QRP Labs group, and I look forward to reading your contributions to CQ. 73 Phil WA8YAN
Sent from my Verizon, Samsung Galaxy smartphone
toggle quoted message
Show quoted text
-------- Original message -------- From: "jjpurdum via groups.io" <jjpurdum@...> Date: 11/9/21 3:18 PM (GMT-05:00) Subject: Re: [QRPLabs] OT: Congratulation JackW8TEE
Thanks Jeff. I think the first column will be out next month.
Jack, W8TEE
On Tuesday, November 9, 2021, 12:52:14 PM EST, Jeff | VA2SS via groups.io <jeff@...> wrote:
Hi,
I would like to congratulate Jack W8TEE for his nomination as? Microcontrollers Editor for CQ Magazine.
Like many excellent contributors we already have in this group, we are grateful to all who like to share their knowledge.
Best regards and 73.
--
Jeff | VA2SS
|
Re: QDX CAT Control Issue?
Hello all, I have a nice new QDX that, at times, is working very well, however, firstly I would get an odd startup screen in WSJTX, as attached, and the CAT would sometimes not transmit. I did some research on Kenwood CAT protocol and found it prefers the attached setup, not ¡°Default¡±
Data bits 8
Stop bits 1
Handshake none
I¡¯ve had fewer CAT issues since of set these params.
73
Ross
EX0AA
|
Retired Doc
David Wilcox K8WPE
Jim Allyn - N7JA
Fred Spinner
wa8yan.radio