开云体育

I built a version 1 QMX+ transceiver which I really like. It seems to work well on the channels I use which is 40-20-15-10M. I recently updated the firmware to version 1_02_000 and I am impressed with the SSB reception. At this time I took the opportunity to connect the transceiver to the Ham Radio Deluxe software which definitely helps me to scan the bands. But I have a reoccurring problem in that my computer does not always recognize the QMX+ and I will get a Device Malfunction when I connect up the patch cord? I have rectified the problem by rebooting both the computer and QMX+ which seems to work.?I have a new HP 64 bit laptop running Windows 11 Home software. I was hoping someone could tell me if this is normal?

?

I would like to run the Hardware Tests Menu and I was hoping someone could walk me through using the Windows 11 PC Terminal Emulator. I understand that I should use the Windows PowerShell Terminal App? I opened the Terminal App and realized it is DOS based with which I am very rusty. It has been 20 years since I have interfaced with DOS and I don’t want to jump down the proverbial rabbit hole. What commands do I use and is it fairly straightforward?

?

The QMX+ is my third QRP Labs kit as I previously built a 20 M QCX-mini and an upper band QMX transceiver. ?Also have a lower band QMX kit coming so I have something to build this summer. Always amazed at how well these kits perform without adjustment. I built a Heathkit HW-16 in High School which was a blast but I had to get a friend who worked at the local TV station to tune it for me.?

?

?

I'd suggest a program such as PuTTY rather than PowerShell. For starters, it's got a GUI which makes it a lot easier to create connections and save presets with the appropriate settings without having to learn a bunch of CLI syntax. I actually use MobaXterm, but you can't go wrong with PuTTY. I believe it's what Hans uses and recommends and it will keep you out of that rabbit hole!

?

My Windows 11 PCs recognize my QMX+ immediately upon plugging it in. Try a different USB C cable, some of the cheap ones are flakey and can cause the kinds of problems you're seeing.

I second the recommendation to not use powershell.? Use PuTTY or my favorite, TeraTerm, which is a little more intuitive, and reconnects without intervention to QMX after a powercycle.? Both are free downloads.?

?

Also, with the SSB firmware loaded, go to the qmx system menu and enable two USB serial ports.? This will allow you to set up TeraTerm (or putty) for one COM port, and your other software with the other COM port.

?

And as already mentioned,? for your Windows machine to see the com ports, your USB cable must be connected (and your windows machine booted) before turning on QMX.? QMX only enumerates the ports to Windows once at power-on,? so if you remove the USB cable or reboot Windows, then you also need to restart? QMX to cause it to send the enumeration again that Windows needs to see.

?

?

Thank you for the quick response and I am very grateful! The cord I am presently using is an Amazon Basic USB cable so I will replace that first.?

?

II plan to start learning how to diagnose with a QCX-Mini on twenty meters that was the first QRP Labs kit I built. It works fine but the output is lower than my other kits. That way if I let the smoke out I will not be upset. My other kits both work perfectly fine but I want to learn how to diagnose problems on these newer radios. Trying to teach myself new skills.?

Thanks again everyone you were a big help!