Good morning all,?
If you are interested, please contact me privately.? ??50 including delivery to most UK postcodes.??
Thank you
Chris? G4CWS
|
On 13/11/2021 09:16, Alan G4ZFQ via groups.io wrote: Hmm. Just tried it on a W7 laptop (installing driver is another story!)
Two flashes with all at maximum.. Sorry! The WSJT-X slider was down. This W7 installation is not going well.. 73 Alan G4ZFQ
|
On 13/11/2021 07:49, Ryan Flowers wrote: That indicates that the power output setting in WSJT-X isn't all the way to the top, but it is for Tune. Make sure the slider is all the way up. Ryan, But yes, all the way to the top is important. I checked mine, with all the Windows settings at maximum just about 2dB reduction on the WSJT-X slider stops the QDX. Seems rather close to me. Hmm. Just tried it on a W7 laptop (installing driver is another story!) Two flashes with all at maximum.. 73 Alan G4ZFQ
|
Re: QDX Isues with sWindows10
#qdx
Hi Greg,
Thank you for the reply.? I went back and this time changed both the port that I used and the USB cable with the Windows10 PC.? I used PuTTY to verify that the QDX was connected, exited the terminal program, and then exited PuTTY.? ?Started WSJT-X, had to change the configuration to the new com ports and the new audio card? (same just with a 2 in the name).? It worked for a while, I am not sure how long as I went to check for new emails and to type this email.? When I went back to get the audio port name I saw that it was not updating with any decodes.? I changed it back to the Raspberry Pi and the first two times I connected it, it did not receive signals although the audio input level on WSJT-X was in the red.? Disconnected the power and let sit for a minute, reconnected power, and the RPi was working with the QDX again with the green input signal bar at 50 DB where I had set it last time using the RPi.
So I am seeing the same pattern as before after a slight delay. I should note that the case was cool the entire time, so do not think it was caused by heat, but did not open the case to verify.? The ambient temperature in my basement shack is 67 deg F.
So the new data is that I can get the QDX to work with one of my Windows10 Laptops for a short period of time.? I ran the QDX on the RPi for 30 minutes while I was typing, thinking, and gathering data.? Still working well.? I guess the next step is to go back to the Windows10 PC and disconnect it from the internet, disable all of the security programs, and see if that makes a difference.? I will do this after I let the RPi setup run for at least an hour.? I want to make sure that it works for a longer period of time.
73
Evan
AC9TU
|
Yes, PTT in "Settings" tests PTT, no signal is output.
"Tune" sends audio to rig.
Ryan, I am confident that that is what I see on other radios. "Test PTT" no audio at all. No reason for a QDX to be different. 73 Alan G4ZFQ That indicates that the power output setting in WSJT-X isn't all the way to the top, but it is for Tune. Make sure the slider is all the way up.
|
On 13/11/2021 07:08, Shirley Dulcey KE1L wrote: Weird.
My 25MHz? TCXO in a QDX is 29.999926MHz. Very:-) I meant 24.999926MHz 73 Alan G4ZFQ
|
On Fri, Nov 12, 2021 at 10:33 PM, Alan G4ZFQ wrote:
Yes, PTT in "Settings" tests PTT, no signal is output.
"Tune" sends audio to rig.
That indicates that the power output setting in WSJT-X isn't all the way to the top, but it is for Tune. Make sure the slider is all the way up. ? -- Ryan Flowers - W7RLF
|
Weird. Sounds like he got a 30 MHz TXCO?by mistake, either his in ordering or a misshipment by the supplier. 74 Hz off at 30 MHz; not quite within the 0.5ppm spec even at that frequency (that's about 2.5ppm off), but if it's stable and if the Si5351A works properly I suppose it's good.
On Sat, Nov 13, 2021 at 1:27 AM Alan G4ZFQ < alan4alan@...> wrote: On 12/11/2021 23:25, Shirley Dulcey KE1L wrote:
> If you have the TCXO, the reference frequency needs to be set for
> 25.000000 MHz. The TCXO is specified as being accurate within 0.5 ppm,
> which would be an error of 5 Hz at 10 MHz.
My 25MHz? TCXO in a QDX is 29.999926MHz. It is the same TCXO as in the QCX.
It is one that does not conform to Hans' expectations. It is stable.
73 Alan G4ZFQ
|
On 12/11/2021 21:18, Hans Summers wrote: Hi Ian
That must be correct, it just means pressing PTT doesn't generate any audio. Hence no RF. It presumably just activates RX/TX changeover only but doesn't generate RF.
I can't check this now... But probably someone else can comment?
Hans?Ian Yes, PTT in "Settings" tests PTT, no signal is output. "Tune" sends audio to rig. 73 Alan G4ZFQ
|
On 12/11/2021 23:25, Shirley Dulcey KE1L wrote: If you have the TCXO, the reference frequency needs to be set for 25.000000 MHz. The TCXO is specified as being accurate within 0.5 ppm, which would be an error of 5 Hz at 10 MHz. My 25MHz TCXO in a QDX is 29.999926MHz. It is the same TCXO as in the QCX. It is one that does not conform to Hans' expectations. It is stable. 73 Alan G4ZFQ
|
Hi KJ7YYM (another KJ7er!),
If you monitor this group e-mail server, Hans Summers at QRP Labs will post a message to let everyone know about two days ahead of time when the next batch of QDXes will be available for sale.? The fun typically starts at 0600Z on the Day of Infamy.? There will then be a a mad rush on the QRP Labs web page for the QDX on the appointed hour and day, where hundreds of hopeful hams will be attempting to out-click-and-type each other trying to order their very own kit.? It will all likely be over in under 15 minutes, if the initial offering is any indication.
On Fri, Nov 12, 2021 at 10:33 PM CALEB_ELI_3 via <CALEB_ELI_3= [email protected]> wrote: Hello to the group, I heard that QRP Labs will release another run of 350 QDX kits, and that I could find more information in the group.? I have not found that chat yet, so I would appreciate if someone could inform me on that.? Thanks!
73 DE KJ7YYM
|
Re: QDX firmware 1.01c with aids for debugging no-transmit-RF issues
Hi Darryl...?
Yes I suppose (though please do test it first).?
Other ways could include just seeing VOX as PTT method in WSJT-X but leaving VOX disabled in QDX.
73 Hans G0UPL http://qrp-labs.com
-------- Original message -------- From: Darryl Hambly <darryl.hambly@...> Date: Sat, Nov 13, 2021, 8:25 AM To: [email protected]Subject: Re: [QRPLabs] QDX firmware 1.01c with aids for debugging no-transmit-RF issues Hans,
I noticed that you mentioned, "...and if you chose a key-up threshold which is higher than the key-down threshold, then this will stop transmission, it will always key-up regardless of the volume." ?Would this be an effective transmit inhibit?
This may be useful in cases where I would like to receive using an antenna that will not produce a safe SWR and protect from transmitting accidentally.
73
-Darryl W2DLH
|
Re: QDX issues: please include info:
#qdx
Hey Stan,
Great to hear about your success with the QDX!
I'm really interested in that quad band EFHW... would you kindly share details?
--
Julian, N4JO.
|
Hello to the group, I heard that QRP Labs will release another run of 350 QDX kits, and that I could find more information in the groups.io group.? I have not found that chat yet, so I would appreciate if someone could inform me on that.? Thanks!
73 DE KJ7YYM
|
QCX 50W Amp - Low RF Output
#20m
Hi everyone:
Looking for a little help here.
My newly assembled 20m QCX 50W Amp is not playing nice. RF output is no more than about 9 Watts. This is with about 5 W input from the QCX+ (20m).
Supply voltage is 20 VDC regulated. Input DC current is 0.9 A on key-down.
This maybe a hint:
With the QCX+ in "Practice Mode" and with straight key selected and used, the key-up idle current of the amp is about 21 mA. With R5 fully CCW the key-down current is about 120 mA. When I now turn R5 CW, no rise in current is observed, until R5 is about 90% of its full CW travel. Is this normal or should I see the rise in current much sooner?
Any pointers to troubleshoot my amp are highly welcome.
73
KF6FOH
|
Re: QDX issues: please include info:
#qdx
My feedback on the build and operation -
Bottom line - the QDX operation is awesome.? I built it yesterday and tested and operated it today on all bands.
I read the several recommendations and followed advise.? My biggest issue is my eyesight is not good up close so had to wear magnifying glasses.
It had been a while since I built a kit, but the manual was really good.
After construction, I did ohm checks to make sure no shorts, then powered up with a dummy load and operated on WSPR to measure TX power.? I used a 9V lithium battery for power and got +36 dBm or so on all bands.
I have an EFHW that covers the 80, 40, 30 and 20 meter bands with no tuner at better than 1.8:1 on the WSPR frequencies.? I had WSPR contacts from Alaska, Iceland, Hawaii and Venezuela - I live in Kansas (center of the USA).
Will try 80 meters tonight.
Kudos to Hans - I have used a CW carrier to generate a tone to a SSB receiver as a quick test, and that got me to thinking about the Siliconix chip as a digital SSB transmitter.? No need for that now as the QDX is there!
I ran the QDX with no cover and could not detect the transistors ever getting hot with finger thermometer.
Will update later if 80 meters has any issues.
Stan, AE0LM
|
Re: QDX firmware 1.01c with aids for debugging no-transmit-RF issues
Hans,
I noticed that you mentioned, "...and if you chose a key-up threshold which is higher than the key-down threshold, then this will stop transmission, it will always key-up regardless of the volume." ?Would this be an effective transmit inhibit?
This may be useful in cases where I would like to receive using an antenna that will not produce a safe SWR and protect from transmitting accidentally.
73
-Darryl W2DLH
|
Hello all, So I have my QDX all assembled and overall have been pretty happy with it other than some frustration trying to get it to work with a rasberry pi (which still doesnt work for me).? The issue I am noting is that while I get transmit current draws of 1amp no 30m .7amps on 20m I only get around .2amp on 40 m.? 40 m also has a receive signal of around 14db while 30 and 20 are both up in the 30db range.? I'm trying to figure out where I should start looking to get the power output of 40m up closer to where it should be along with its receive audio strength.?
??? v/r ?? K9WBZ
|
Re: QDX Isues with sWindows10
#qdx
Hi Evan,
I am using my QDX on a windows 10 laptop without the issues you mention. I'm not sure if this is your start-up sequence but mine is: 1. USB cable hooked to windows 10 and the QDX but power to the QDX is off 2. Power on the QDX and wait until the LED goes solid 3. Start WSJT-X
The above works every time for me. Btw, I also disabled the USB 'power down' function in the power saver windows setting, but I'm not sure that matters.
I have seen twice now where the receive seems to go off on the QDX after some time and I'm not receiving any signals. Just switching bands and coming back will restore the signals. I'm not sure what that is about yet.
Cheers, Gregg W7GRM
On Fri, Nov 12, 2021 at 7:49 PM Evan Hand < elhandjr@...> wrote:
- Windows10 Home.?
- Firmware 1_01c.?
- Built for 12 volts operation
- Both Battery and switched DC
- Rev 1 Board
- One deviation: removing the 4 inductors before building the rest of the kit.?
I am having issues using my QDX with Windows10.? I have tried 2 different laptops from different manufactures.? I have not been able to get either one to work.? What is really strange is that after trying with a Windows10 PC I need to do multiple power off resets to then get the QDX to work again with my Raspberry Pi 4 running 32 bit Buster with all updates.? The tests are with version 2.52 of WSJT-X in both environments.? The terminal software that I use is PuTTY on both.? Putty will always connect.? The sound cards will disconnect at times between reboots.
There appears to be something that happens when connecting to a Windows10 USB port that does not happen with Linux as installed on a Raspberry Pi 4 with 8 GB of memory.? It seems to be repeatable on one of my Windows10 PCs:
1 I confirm that the QDX is working both receiving and transmitting on the Raspberry Pi
2 I power all down and move the USB connections to the Windows10 PC
3 Turn on the QDX and the level bar of WSJT-X is much higher than with the Raspberry Pi
4 There are no decodes
5 Shutdown again and reconnect to the Raspberry pi
6 First time on powering up the QDX the terminal window will work, the WSJT-X will not receive audio.? The transmit function will work with the Tune button
7 Power cycle the QDX again and this time or the next power cycle the QDX will start receiving signals and send them to the Raspberry Pi to be decoded.
8 Going back to the Windows PC starts the issues all over again.
The other Windows10 PC used to connect but now will not connect either the comm port or the USB sound devices.
The QDX has been performing well on the Raspberry Pi 4, though do want to use it with the faster Windows10 machines.? Both are laptops.? My speculation at this point is that a windows startup process for the USB device is causing an issue with the update process of the QDX.? That might explain the multiple restarts that are required, in that Windows may be putting something on the disk that gets interpreted as an update that has to be processed to determine it is not a file for the QDX to use.? This is pure speculation at this time and maybe WAY off base.
?
I guess my next step is to try to capture any issues with logs on all three devices.? That will be a task for tomorrow.? Calling it a night tonight.
The question to the group is if anyone else is experiencing similar issues with Windows10?? Has anyone tracked down the issue?
73
Evan
AC9TU
|
QDX Isues with sWindows10
#qdx
- Windows10 Home.?
- Firmware 1_01c.?
- Built for 12 volts operation
- Both Battery and switched DC
- Rev 1 Board
- One deviation: removing the 4 inductors before building the rest of the kit.?
I am having issues using my QDX with Windows10.? I have tried 2 different laptops from different manufactures.? I have not been able to get either one to work.? What is really strange is that after trying with a Windows10 PC I need to do multiple power off resets to then get the QDX to work again with my Raspberry Pi 4 running 32 bit Buster with all updates.? The tests are with version 2.52 of WSJT-X in both environments.? The terminal software that I use is PuTTY on both.? Putty will always connect.? The sound cards will disconnect at times between reboots. There appears to be something that happens when connecting to a Windows10 USB port that does not happen with Linux as installed on a Raspberry Pi 4 with 8 GB of memory.? It seems to be repeatable on one of my Windows10 PCs: 1 I confirm that the QDX is working both receiving and transmitting on the Raspberry Pi 2 I power all down and move the USB connections to the Windows10 PC 3 Turn on the QDX and the level bar of WSJT-X is much higher than with the Raspberry Pi 4 There are no decodes 5 Shutdown again and reconnect to the Raspberry pi 6 First time on powering up the QDX the terminal window will work, the WSJT-X will not receive audio.? The transmit function will work with the Tune button 7 Power cycle the QDX again and this time or the next power cycle the QDX will start receiving signals and send them to the Raspberry Pi to be decoded. 8 Going back to the Windows PC starts the issues all over again. The other Windows10 PC used to connect but now will not connect either the comm port or the USB sound devices. The QDX has been performing well on the Raspberry Pi 4, though do want to use it with the faster Windows10 machines.? Both are laptops.? My speculation at this point is that a windows startup process for the USB device is causing an issue with the update process of the QDX.? That might explain the multiple restarts that are required, in that Windows may be putting something on the disk that gets interpreted as an update that has to be processed to determine it is not a file for the QDX to use.? This is pure speculation at this time and maybe WAY off base. ? I guess my next step is to try to capture any issues with logs on all three devices.? That will be a task for tomorrow.? Calling it a night tonight. The question to the group is if anyone else is experiencing similar issues with Windows10?? Has anyone tracked down the issue? 73 Evan AC9TU
|
Shirley Dulcey KE1L
Julian N4JO
Darryl Hambly
Zachary Painter