Keyboard Shortcuts
Likes
- QRPLabs
- Messages
Search
Re: #qdx 1_08 firmware release
#qdx
¿ªÔÆÌåÓýWill that DLL also work on a Pi? That's all I have to test with.73,
Cliff, AE5ZA
|
Re: #qdx 1_08 firmware release
#qdx
Hi all There hasn't been any change to the TX RX commands. And I'm using 1_08 with JS8call without issues. So I suspect you have some other problem... 73 Hans G0UPL http://qrp-labs.com https://www.buymeacoffee.com/g0upl -------- Original message -------- From: "Michael Black via groups.io" <mdblack98@...> Date: Tue, Jan 24, 2023, 6:37 PM To: [email protected], [email protected] Subject: Re: [QRPLabs] #qdx 1_08 firmware release Apparently TX/RX does not work anymore -- that's what Hamlib uses...FLRig is using the newer TQ1/TQ0. |
Re: QDX pairs nicely with the Micro PA50
¿ªÔÆÌåÓýThis would make a great amp but unfortunately it does not cover the whole 10m band. Not a good idea to stop at 28,5 MHz. ? Robert, OE7OER ? ? Von: [email protected] <[email protected]> Im Auftrag von Joshua Ellis ? James, |
Re: U4B general question
Working on a U4B sensing and sending radiation levels via the U4B telemetry channels project.? Let me know if anyone in our group is interested in working together on this interesting project. Thanks! ? Joe W2JEJ On Wed, Jan 4, 2023 at 2:39 PM WA1EDJ <bobc784@...> wrote: Since I'm placing an order soon, I thinking of picking up a U4B.? Seems to have lots of possibilities. |
Re: #qdx 1_08 firmware release
#qdx
Michael Black
Apparently TX/RX does not work anymore -- that's what Hamlib uses...FLRig is using the newer TQ1/TQ0.
toggle quoted message
Show quoted text
This 64-bit DLL has the change to TQ So give it a try.? It goes in the WSJT-X bin directory. Mike W9MDB On Tuesday, January 24, 2023 at 11:20:21 AM CST, Cliff <ae5zaham@...> wrote:
Mike, I haven't looked at the code for the QDX in flrig, but the firmware manual for 1_06 and on has Tx and Rx as commands as well as the TQ. They should all work. 73, Cliff, AE5ZA On Jan 24, 2023, at 11:14, Michael Black via groups.io <mdblack98@...> wrote: |
Re: #qdx 1_08 firmware release
#qdx
¿ªÔÆÌåÓýMike, 73,
Cliff, AE5ZA
|
Re: #qdx 1_08 firmware release
#qdx
Michael Black
I see that QDX apparently wants the "TQ" command for PTT control.
toggle quoted message
Show quoted text
What compatibility mode is that and why can't it use "TX/RX" like the TS-480 compatibility it claims?? At this point it should recognize either command to maintain backwards compatibility. And the QCX does not support PTT control at all? Mike W9MDB On Tuesday, January 24, 2023 at 09:54:42 AM CST, Cliff <ae5zaham@...> wrote:
Phill, Just a couple of things: - Get the newest flrig alpha from www.w1hkj.com/alpha/flrig. It has a fix in flrig that affected the audio quality with firmware over 1_05. - in Wsjtx select the rig as "flrig flrig" and use flrig for rig control. Makes life much easier. Set USB and Rig for Radio settings to let the QDX use Split. - I don't know about JTDX, but it may support using flrig as well. 73, Cliff, AE5ZA On Jan 24, 2023, at 09:43, Phill via groups.io <rocinante2021@...> wrote: |
Re: QDX pairs nicely with the Micro PA50
Joshua: You can shorten the URL considerably by just using the ID number (3256804580861697). (See below.) The same idea works on Amazon and eBay, too. Jack, W8TEE
On Tuesday, January 24, 2023 at 11:32:06 AM EST, James C. Hall, MD WB4YDL <heartdoc@...> wrote:
Many thanks Joshua ! ? 73, Jamie WB4YDL ? From: [email protected] [mailto:[email protected]] On Behalf Of Joshua Ellis ? James, |
Re: QDX pairs nicely with the Micro PA50
¿ªÔÆÌåÓýMany thanks Joshua ! ? 73, Jamie WB4YDL ? From: [email protected] [mailto:[email protected]] On Behalf Of Joshua Ellis ? James, |
Re: QDX pairs nicely with the Micro PA50
James,
Here is the link:? You can manually change the band prior to key up if needed. Push the button 3 times successively. A manual knob for band selections is what my MX-P50M has. I did a quick check with a 3.5mm TRS cable with the IC705 and am finding strange behavior of the amp. I will need to do a bit more testing. Joshua KJ7LVZ, I will give the PTT cable a try with the QDX as well, hopefully today. As mentioned above, I am seeing strange behavior that I want to sort out. Joshua KO4AWH |
Re: #qdx 1_08 firmware release
#qdx
¿ªÔÆÌåÓýPhill,Just a couple of things: - Get the newest flrig alpha from . It has a fix in flrig that affected the audio quality with firmware over 1_05. - in Wsjtx select the rig as "flrig flrig" and use flrig for rig control. Makes life much easier. Set USB and Rig for Radio settings to let the QDX use Split. - I don't know about JTDX, but it may support using flrig as well. 73,
Cliff, AE5ZA
|
Re: #qdx 1_08 firmware release
#qdx
Well it didn't go quite as well as expected.
FLRIG and FLDIGI worked using QDX as transceiver in FLRIG. WSJT-X and JTDX both receive fine but fail to turn on TX on the QDX. Looks like some incompatibility between them and HAMLIB. Probably some old files I've failed to clear out. Once I've managed to get my wife off her Win 11 laptop I'll burn a copy of Ubuntu onto the sd card and take it from there. Thanks again. -- Phill EA5JHA |
Re: Feeding 30 MHz into the Si5351A with the Ultimate3S
You might try using your 15MHz reference directly.? I know the '5351A isn't exactly specified for this (other devices in the family are though), but I send a 10MHz 3V-logic-level clock to the '5351A on some of my designs and it works very well.
-- Paul Elliott - WB6CXC |
Sharing QDX repair experience
Hi folks -? Sharing this repair experience in case it helps others or if anyone has further advice to add. After a couple of days working fine on 20m and 40m my QDX stopped transmitting and battery current on receive went up from 140mA->320mA. Reading Hans' excellent troubleshooting guide I updated the firmware and suspected at least one blown BS170. Indeed it turned out to have been a bad day for Q11: ? I replaced all four BS170s and, while the board was in front of me, I took the opportunity to resolder some of the inductor windings where it looked like dry-ish joints due to poorly burned off enamel might cause a problem. The TX side seems OK: on the three bands I have enabled the transmitter is delivering around 2.5W on each of 40m and 30m and 4.2W on 20m. However I seem to have upset the RX side as this is what I get from RF sweeps on all bands: Given that the TX side is doing OK, is it safe to assume that the LPF inductors are probably OK and I need to look for anomalies on the board around L12 and the trifilar transformer? |
Re: Feeding 30 MHz into the Si5351A with the Ultimate3S
Hello Halden 30MHz was tried before. The Si5351A works but the spectral purity is greatly impaired. U3S would work too if you set the reference to 30MHz.? But as I said if you put a spectrum analyzer on it and compare, you won't like it perhaps. 73 Hans G0UPL http://qrp-labs.com https://www.buymeacoffee.com/g0upl -------- Original message -------- From: "HF via groups.io" <incorridge@...> Date: Tue, Jan 24, 2023, 1:31 AM To: [email protected] Subject: [QRPLabs] Feeding 30 MHz into the Si5351A with the Ultimate3S I have a stable reference oscillator on 15 MHz.? I could double it to 30 MHz without too much trouble.? Has anyone here tried feeding 30 MHz into the Si5351A on the U3S?? Hans, will the U3S software work with a reference frequency setting of 30.000000 MHz?? I intend to use it with WSPR and CW on 40 and 50 MHz, not 144. |
Not in my corner of the Internet, ¡®only¡¯ 8 of the plastic case, but lots of the aluminum. Both available Prime delivery Wednesday.
toggle quoted message
Show quoted text
You¡¯re on your own for dense fog. ? 73, Willie N1JBJ On Jan 23, 2023, at 7:27 PM, Andy <andy.mm0fmf@...> wrote: |
Re: Si5351a issues with frequency resolution (step size) at 144MHz (or even lower frequencies)
Hi Ron.? I don't think those frequency error examples are the best I can do if I switch to the Adafruit library, which seems to allow easier direct? manual control of some of the parameters
Using the Adafruit library and using the clockgen.setupPLL function, you can setup something like this clockgen.setupPLL(SI5351_PLL_A, 34, 463868, 762939); This sets PLL_A to the reference frequency (25MHz) * (34 +?463868/762939), which is what ClockBulder Desktop suggests. ClockBulder pro suggests? 34.6080016 but gives no integer divider in the report. Presumably it incorporates integer dividers in the suggests C++code for the SI5351 registers. It presumably used the same fraction as ClockBuilder Desktop. PLL A
?Input Frequency (MHz) = 25.000000000
?VCO Frequency (MHz) =? 865.200040002
?Feedback Divider = 34? 463868/762939
?SSC disabled
?
Output Clocks
Channel 0
?Output Frequency (MHz) = 144.200006667
?Multisynth Output Frequency (MHz) = 144.200006667
?Multisynth Divider = 6
This works with the Adafruit library, but the problem is that it doesn't quite give the desired output frequency (144.200006667). The problem is that the Frequency Divider should actually be 34.6080016, and that's not quite the same as the fraction given by Clockbuilder desktop. 463868/762939 = 0.608002736784985431338...
so the xtal is multiplied to (25*34.60800142606420) = 865.20003565160517...
when this is divided by 6 gives 144.200005942, an error of 0.725Hz
I think 463868/762939 is the best you can do with 20-bit registers (I think they are 20bit?), so using this method you may get close to the desired frequency, but still nowhere near the 0.001 or even 0.01Hz accuracy that you see quoted for the Si5351 in various places. The other issue is coming up with a good algorithm for calculating the nearest set of 20-bit numbers to use for the fractional divider. How do you turn? 0.6080016 into a fraction (nearest the correct value) using only 20-bit numbers? That's what ClockBuilder does, but if you have to run ClockBuilder for every frequency you want to generate (and codes like JT65 and Q65 have 65 frequencies) it gets a bit tedious, even for just one sync (base) frequency.? And you are still not exactly on frequency for? of the tones.? The final divider in the chain from PLL_A to the output frequency is an integer (Multisynth Divider = 6).? I guess in order to get higher frequency resolution, you would have to use a fractional divider, and from what I can see, this has to be somewhere between 8 and 900. I don't then see any way to use a fractional divider to generate a signal near 144MHz.? If the PLL limit is 900MHz and the Multisynth Divider can be integers 4, 6 or 8, or fractions between 8 and 900, you can never use fractions above 900/8 = 112.5MHz and so probably never generate signals above 144MHz to better then the nearest 1Hz.? You might be able to generate a particular frequency with the right crystal and fractional divider, but you can't then step the frequency in uniform sub-Hz steps. This would make WSPR on 144 a difficult task, though maybe you can get close enough to the 1.465Hz tone spacing to get it to work (sometimes?). I think I've seen posts saying that it is possible, though I've also seen comments in code that it doesn't). Am I understanding this correctly? If so then the only way to generate 144Mhz signals with high accuracy and resolution, would probably by using harmonics, probably working at 48MHz and looking at the 3rd harmonic. Accuracy abd step size would be 1.3 of that at 48MHz, but probably still better than directly synthesizing at 144MHz. Or am I still missing something? |
Re: QDX arrived
There was some extended chatter about winding toroid coils a few weeks back, here:
/g/QRPLabs/topic/95276160 I sure learned from it.? I wound about 20 toroids for the VFO sinewave siggen and it was fun and easy. Rich |