On Sat, Nov 13, 2021 at 05:40 PM, Julian N4JO wrote:

Yes, it certainly shows you what the orientation should be when properly installed, but unfortunately you can't solder it in that way, because you can't get to the underside of the board. The precision of the kit parts is really good, so if you go for parallel you can't really go wrong.
--
Julian, N4JO.

I connected the BNC to the rear panel then solder the BNC and use the panel to align the remaining connectors.? I did not mount the back to the bottom or top.

Dave, he will be rewarded.? Assuming we are successful, the QDX will be his.? : )

73,? Mike KK7ER

On Sun, Nov 14, 2021 at 01:47 PM, Hans Summers wrote:

I wonder, is it just the 1.01c firmware that doesn't initiate correctly every time? Or all firmware versions??

I had issues with 1.01a as well.? 1.01c seems to be better, although I now know how to get around the issue.? I did not install 1.01b.

73
Evan
AC9TU

Had the same issue, resolved it by filing a bit of the opposite long side of the PCB. Just a fraction of millimeter was enough. I even managed to put a piece of paper (would have used kapton tape if I had any) just in between the IC and the chassis to prevent any possible short.?

Additional on. Previous post regarding ATU 10,, mini-tuner. My tuner worked very well for the first 2 weeks. I am sad to report it stopped tuning and appears to be broken.? When opended up, the construction great, sealed in clear silicone, but no ?repairable problem. To be honest, I loved it so much, I ordered a replacement, but you may want take care.?

It may be the case that this does not resolve all the CAT control issues, but it certainly resolved mine :)?
--
Karl Heinz - K5KHK

My name is Julian and I approve of this message ;-)
--
Julian, N4JO.

Finished QDX today and fired it with? Windows 10 and made two nice contacts.? Learned a few tricks in the process.

1.? Connect QDX and allow time for device to connect before opening WSJT.? This allows WSJT to see the QDX as an option
2.? Open control panel then sound then select QDX? set Record Levels to 85 and output levels to 90.
3.? If you are having issues, use the configuration editor in terminal mode to check the hardware and CAT controls.?
4.? Use configuration menu to update firmware to 1.0c as the blinking LED is a great debugging tool. ( Thank You Hans).

On Sun, Nov 14, 2021 at 08:06 AM, Dave Edwards wrote:

I only just finished my Small Wonder Labs PSK31 kit.

I remember putting together a couple of Dave's kits years ago, and I really thought the rock-bound kits, with no display, were something.? I was on the air on 7030 for well under $100!? That's why I consider the QCX line such an engineering marvel.? So much consideration and functionality, especially at the economical price.? Full band coverage, a display, built-in alignment, and options galore.? My KX1 is great (I use it much more than the K1), but it was a $500 kit for two bands (20m and 40m), and it cost another $100, if I recall correctly, to get 30m and 80m, and that may not have included the ATU.? And considering some of the alternatives - Four State QRP kits, QRPMe (carrying on Dave's RockMite line), Diz's OneWatter and other kits, Pacific Antenna / Hendricks kits, and many others, I would say we are getting enormous value and a well-designed, beautifully-engineered kit from Hans.? The QCX-Mini display board set up is a work of art, in my humble, non-engineering opinion.? haha.

Your post is a nice reminder of how things were in the not-so-distant past.?

A more specific way would be to add a udev rule that let ModemManager ignore this specific device. For example based on the USB ID.

With lsusb I found the ID:

lsusb?-vt
<snip>
??????????? |__ Port 4: Dev 12, If 4, Class=Audio, Driver=snd-usb-audio, 12M
??????????????? ID 0483:a34c STMicroelectronics 
??????????? |__ Port 4: Dev 12, If 2, Class=Audio, Driver=snd-usb-audio, 12M
??????????????? ID 0483:a34c STMicroelectronics 
??????????? |__ Port 4: Dev 12, If 0, Class=Communications, Driver=cdc_acm, 12M
??????????????? ID 0483:a34c STMicroelectronics 
??????????? |__ Port 4: Dev 12, If 3, Class=Audio, Driver=snd-usb-audio, 12M
??????????????? ID 0483:a34c STMicroelectronics 
??????????? |__ Port 4: Dev 12, If 1, Class=CDC Data, Driver=cdc_acm, 12M
??????????????? ID 0483:a34c STMicroelectronics
</snip>

So the VID/PID for the QDX is: 0483:a34c.

Then, create the following rule and reload udev.

# create UDEV rules (as root)
cat > /etc/udev/rules.d/80-qdx.rules << 'EOF'
ATTRS{idVendor}=="0483", ATTRS{idProduct}=="a34c", ENV{ID_MM_DEVICE_IGNORE}="1"
EOF

# Reload udev rules
udevadm control --reload-rules && udevadm trigger

You can show info to see if udev added the ignore tag (ID_MM_DEVICE_IGNORE=1) for ModemManager.

udevadm info /dev/ttyACM0
P: /devices/pci0000:00/0000:00:01.2/0000:02:00.0/usb1/1-2/1-2.4/1-2.4.4/1-2.4.4:1.0/tty/ttyACM0
N: ttyACM0
L: 0
S: serial/by-path/pci-0000:02:00.0-usb-0:2.4.4:1.0
S: serial/by-id/usb-QRP_Labs_QDX_Transceiver-if00
E: DEVPATH=/devices/pci0000:00/0000:00:01.2/0000:02:00.0/usb1/1-2/1-2.4/1-2.4.4/1-2.4.4:1.0/tty/ttyACM0
E: DEVNAME=/dev/ttyACM0
E: MAJOR=166
E: MINOR=0
E: SUBSYSTEM=tty
E: USEC_INITIALIZED=5869499
E: ID_BUS=usb
E: ID_VENDOR_ID=0483
E: ID_MODEL_ID=a34c
E: ID_PCI_CLASS_FROM_DATABASE=Serial bus controller
E: ID_PCI_SUBCLASS_FROM_DATABASE=USB controller
E: ID_PCI_INTERFACE_FROM_DATABASE=XHCI
E: ID_VENDOR_FROM_DATABASE=Advanced Micro Devices, Inc. [AMD]
E: ID_PATH=pci-0000:02:00.0-usb-0:2.4.4:1.0
E: ID_PATH_TAG=pci-0000_02_00_0-usb-0_2_4_4_1_0
E: ID_VENDOR=QRP_Labs
E: ID_VENDOR_ENC=QRP\x20Labs
E: ID_MODEL=QDX_Transceiver
E: ID_MODEL_ENC=QDX\x20Transceiver
E: ID_REVISION=0100
E: ID_SERIAL=QRP_Labs_QDX_Transceiver
E: ID_TYPE=generic
E: ID_USB_INTERFACES=:020201:0a0000:010100:010200:
E: ID_USB_INTERFACE_NUM=00
E: ID_USB_DRIVER=cdc_acm
E: ID_MM_CANDIDATE=1
E: ID_FOR_SEAT=tty-pci-0000_02_00_0-usb-0_2_4_4_1_0
E: ID_MM_DEVICE_IGNORE=1
E: DEVLINKS=/dev/serial/by-path/pci-0000:02:00.0-usb-0:2.4.4:1.0 /dev/serial/by-id/usb-QRP_Labs_QDX_Transceiver-if00
E: TAGS=:uaccess:systemd:seat:
E: CURRENT_TAGS=:uaccess:systemd:seat:

73, Ben
PA2ST

Kit has been sold pending receipt of payment.

Thank you.
John W9QP

On 14/11/2021 19:47, Hans Summers wrote:

I wonder, is it just the 1.01c firmware that doesn't initiate correctly every time? Or all firmware versions?

Hans,

The first time, I'm not sure what the version was but was well before 1.01c.
But then I can't be sure whether there really was a fault with the trifilar windings. Would I get a jagged trace or a smooth one with zero cancellation?
I could go back tomorrow and try an earlier version.

73 Alan G4ZFQ

开云体育

Kit has been sold. Thank you for the interest.?

Yes the disable means “don’t ever start this service”. ??

Aug
AG5AT

When I first tested my QDX it showed traces just like Dennis's
Jagged, no real sign of cancellation.
I removed the trifilar even though I was sure I'd done it correctly, checked the windings and refitted. Got good traces.

I checked again today, bad trace again like Dennis.
I had "Listen to this Device" enabled and instead of a very low smooth noise it sounded "choppy".
I disconnected the QDX and its power and reconnected. Checked the filters again and got good results, monitoring I heard just a smooth low noise and a "chuff chuff" as the test progressed.

The QDX obviously does not initiate correctly every time. If you get bad traces try disconnecting and doing the test again. The Windows "Listen to this Device" helps confirm correct operation.

73 Alan G4ZFQ

Hi Hans,

This does give a clue as to what might cause the CAT command to work but not the USB audio.? There may be a carriage return in some of the Windows system USB management programs.? I think that I will look into ways to monitor what is going over the USB link during USB startup in a Windows system.

73
Evan
AC9TU

Ah, finally an explanation for the communication dropouts that actually makes sense. The "RF in?the shack" just did not explain what I was seeing (and none of my other radios - digital or analog - were affected by this.?

After making these changes, I was still not able to send CAT commands to the QDX, but when I shut down WSJTX again, and started up putty, I was able to see that the device was in the terminal mode. After exiting, WSJTX was happy. I take that as a confirmation that the modem manager was actually the guilty party.?
--
Karl Heinz - K5KHK

I'll take it if still available, John.
My email address is n4qa@...
Thanks & 72 / 73,
Bill, N4QA