开云体育

Keith's observation is interesting.? Since we know you are getting voltage at source of Q111 (per your measurement) it means L102 is not open.? But it could be shorted (burned), or maybe R114/Q110

Good afternoon, Hans - First - *incredible* work on this.? There don't seem to be many folks left that are putting out and fully supporting complex kits the way that you are, and I can absolutely

Maybe it's only ok for Win10 and up. For field operation I'm using an older and small Netbook / Notebook only good for Win7. So I test all for Win7 using the STMicroelectronics driver for Win7. It

Mine also come up fine. I am using one com port for JTDX, one for LOG4OM, and one for Putty, all at the same time with no issues. Windows 11. Tony AD0VC

Mine connections come up fine (win10) Could the "STM..." devices be from different things you have plugged in? - the serial ports from my QMX show as "USB Serial Device", and the audio ports as

Starting WSJT-X a errormessage appears "Error in sound input". Maybe its from the not ok USB Audio device (see my post before)? But there is "Audio - QMX Transceiver" and I choose this in WSJT-X but

Interesting.? I don't see that happening with mine.? And I don't see anything in the schematic that would cause that to happen. Are you sure you have the ptt wired completely independently of the

Hi Chris My results here on a QMX+ 160m: 2650 80m: 2650 60m: 2650 40m: 2650 30m: 2650 20m: 2650 17m: 1150, subsequent one-off tries 1200 15m: 1500 12m: 1350 11m: 1950 10m: 700, subsequent one-off

Hello, I installed the new FW and have some trouble. Under Win I see Audio - QMX Transceiver - ok Audio - USB Audiodevice - not ok Com - STMicroelectronics Virtual COM Port (COM <x>) - ok Com -

In FT8CN settings turn off no track CQ and no track call and the software won't be so "automated"

Jeff do you have a link to that PCM1804 replacement part? I may need one (or two)?

Jim: Sorry, for the delay - Percocet, don’t ya know ! It was C16 I had set up as a sorta QSK switch like the cover photo. My idea was to use a TRS or TRRS plug where (usually) the T and R (or R1)

Randy, Many of us are getting very different calibration curves, some of the phase ones look crazy. Your phase error plots that don't go up to about 2600 (x-axis, 12V build) are 'incomplete'.? You

More info on USB naming, I just checked again the way QMX does it. I attached a screenshot of my /dev/serial/by-id directory. There are three devices, named by their "Interface ID", which are 00, 02

Maybe not, Diarmuid... we don't even know that Mac doesn't do it yet... 73 Hans G0UPL http://qrp-labs.com https://www.buymeacoffee.com/g0upl

The solution is simple, upgrade to Linux, Jan. Diarmuid EI4LF [email protected]> wrote:

Hi Jan It's done on QDX already and I intend to do it on QMX too. It only works on Linux. On Windows, the OS ignores the name you give it and always gets called COM4, COM5 etc. What happens on Mac

Is it at all possible to set up virtual COM ports so that they will have a consistent name when (re)connecting? I've found that under MacOSX, the name changes every time you plug it in. This makes it

Calibration of QMX+ completed.? Results below: (three QMXs to be tested) Some phases stopped early 160m? 1100 80m? ?1300 60m? 2500 40m 2600 30m 2600 20m 2500 17m 700 15m 700 12m 1500 10m 2300 6m

What would be the symptoms if this component was failed? I set the QMX aside for now to take a break. Troubleshooting this thing all day made me tired. Just to know for when I pick it back up, in case