开云体育

the laptop is mounted into the lid of the case by using some short alu profiles ...
so I have a all-in-one ...
may you can try your own ideas

Hi, I like to show you my new /p setup with QMX low band:

Dbl.click 300 - no reaction, 500 - works after 3-5 attempts, 600 - switch RIT on immediately. It was not so before, 300 was OK.

73
Igor oh2jxa

Chris,
I think it still comes back to volume level. I tried using my little amplified speaker and the clicks are gone - that is until you turn the volume up to really uncomfortable levels - then they are as bad as before. To put it another way, if you notice the clicks in the headphones, then change to amplified speaker, the clicks are still there.?
--
73, Dan? NM3A
There are moments when everything turns out right .... Don't let them alarm you; they pass.?

-Jules Renard

Chris,
?I tried your settings and there is no change. Unless... you turn the volume way down. Volume level is the only thing that seems to make a difference. Low volumes, I don't hear clicks. High volumes, it is awful. As I said before, at volume levels in a QSO with medium to strong stations, the clicks are minimal.?
--
73, Dan? NM3A
There are moments when everything turns out right .... Don't let them alarm you; they pass.?

-Jules Renard

Greg,? I think I also trimmed most of the tab off so it wouldn't interfere with other components.?
--
73, Dan - W2DLC

I have to admit that I was a bit mystified as to how I managed to get the sidetone working perfectly as I initially played a lot with the settings to no avail and then the problem just seemed to disappear.

I've just remembered that I had headphones connected to the audio jack when I first had the problem.? I just tried those same headphones again and the problem returns but when I connect the audio jack to the line-in on my PC soundcard it's perfect!? So It seems that input impedance of the headphones/speaker may be a factor here?

?

Dan, Rowan and Ron, thanks for your help.? I think I am off and running.

73, Greg, KM5GT

On 13/03/2024 11:18, hamradio@... wrote:

For me it looks like QDX usb resets as soon as it starts transmitting.

Torsten,

RF getting into the USB cable?

Try different cables, put chokes on cables.

Or stop common-mode signals on the feeder. Reconfigure antenna.

72 Alan G4ZFQ

It's an easy mod. You just move the 7805 over to the left one pin and solder the left most pin to the bottom of the diode.?

--
73, Dan - W2DLC

Tnx all.? Not that I *plan* on shorting the 5VDC to ground, but replacing the regulator with a 78M05 is appealing.? Where will I find details on that fix?? Is it drop-in, or does it require some creative wiring?

73, Greg, KM5GT

Hans - It looks like we have a real problem for many (most?) of us! Perhaps it is a bigger issue than we all realised. I welcome your comments please, meanwhile, back in the desk drawer it goes as, sadly, unusable.

Everyone - Thanks for posting your settings.

Rather than reproduce my settings here, I will just say that I am using the same settings as Adrian YO3GFH, having copied them from an earlier thread. I have also tried disabling the AGC and copying Chris Bolton's settings - it makes no difference. Audio thumps exist after (not before) every dit and dah (whether at 2 wpm or 30 wpm.)

Please can we fix this asap?

Best wishes all,

Daimon.
G4USI

Hello there :)


I built a QDX (PCB Rev 5 and firmware 1_10) for 20, 17, 15, 12, 11 and 10m (12 volts version) that works well (rx & tx) on 15m, but fails running on 10m.

The QDX is connected to a Debian Bookworm system.

For me it looks like QDX usb resets as soon as it starts transmitting.

/var/log/syslog right after booting the system:
024-03-13T07:28:21.281069+01:00 lab kernel: [ 1.404372] usb 1-4: New USB device found, idVendor=0483, idProduct=a34c, bcdDevice= 1.00
2024-03-13T07:28:21.281069+01:00 lab kernel: [ 1.404378] usb 1-4: New USB device strings: Mfr=1, Product=2, SerialNumber=0
2024-03-13T07:28:21.281073+01:00 lab kernel: [ 1.404379] usb 1-4: Product: QDX Transceiver
2024-03-13T07:28:21.281073+01:00 lab kernel: [ 1.404381] usb 1-4: Manufacturer: QRP Labs
...
024-03-13T07:28:21.281238+01:00 lab kernel: [ 2.636203] cdc_acm 1-4:1.0: ttyACM0: USB ACM device
2024-03-13T07:28:21.281242+01:00 lab kernel: [ 2.636255] usbcore: registered new interface driver cdc_acm
2024-03-13T07:28:21.281242+01:00 lab kernel: [ 2.636259] cdc_acm: USB Abstract Control Model driver for USB modems and ISDN adapters


7:40 torsten@lab:~$ sudo ls -l /dev/ttyAC*
crw-rw---- 1 root dialout 166, 0 13. M?r 07:28 /dev/ttyACM0
07:41 torsten@lab:~$


WSJTX error-message:
Hamlib error: write_block():1077 failed -1 - Input/output error
ic10_transaction: called cmd='IF;', len=3, data=0x7ffa789f33d0, data_len=0x7ffa789f3384
rig_flush: called for serial device
read_string_generic called, rxmax=4095 direct=1, expected_len=1
read_string_generic(): read failed, direct=1 - Input/output error
tcflush
write_block():1077 failed -1 - Input/output error
ic10_transaction: called cmd='IF;', len=3, data=0x7ffa789f33d0, data_len=0x7ffa789f3384
rig_flush: called for serial device
read_string_generic called, rxmax=4095 direct=1, expected_len=1
read_string_generic(): read failed, direct=1 - Input/output error
tcflush
write_block():1077 failed -1 - Input/output error
IO error
)
1:rig_get_vfo: elapsed=1ms
1:rig.c(2991):rig_get_vfo returning(-6) IO error

IO error
IO error
while getting current VFO



/var/log/syslog after the error:
2024-03-13T07:17:23.028955+01:00 lab kernel: [41902.754569] usb usb1-port4: disabled by hub (EMI?), re-enabling...
2024-03-13T07:17:23.028974+01:00 lab kernel: [41902.754583] usb 1-4: USB disconnect, device number 2
2024-03-13T07:17:23.074877+01:00 lab kernel: [41902.804441] usb 1-4: cannot submit urb (err = -19)
2024-03-13T07:17:23.074926+01:00 lab kernel: [41902.804538] xhci_hcd 0000:00:14.0: WARN Event TRB for slot 1 ep 5 with no TDs queued?
2024-03-13T07:17:23.074929+01:00 lab kernel: [41902.804551] xhci_hcd 0000:00:14.0: WARN Event TRB for slot 1 ep 6 with no TDs queued?
2024-03-13T07:17:23.076888+01:00 lab kernel: [41902.804632] usb 1-4: Unable to submit urb #2: -19 at snd_usb_queue_pending_output_urbs
2024-03-13T07:17:23.076918+01:00 lab kernel: [41902.804800] usb 1-4: cannot submit urb 0, error -19: no device
2024-03-13T07:17:23.076921+01:00 lab kernel: [41902.804810] usb 1-4: cannot submit urb 0, error -19: no device
2024-03-13T07:17:23.079146+01:00 lab pulseaudio[1953]: Could not recover from POLLERR|POLLNVAL|POLLHUP and XRUN: Datenübergabe unterbrochen (broken pipe)
2024-03-13T07:17:23.083795+01:00 lab pulseaudio[1953]: Could not recover from POLLERR|POLLNVAL|POLLHUP and XRUN: Eingabe-/Ausgabefehler
2024-03-13T07:17:23.356935+01:00 lab kernel: [41903.082794] usb 1-4: new full-speed USB device number 4 using xhci_hcd
2024-03-13T07:17:23.504901+01:00 lab kernel: [41903.232739] usb 1-4: New USB device found, idVendor=0483, idProduct=a34c, bcdDevice= 1.00
2024-03-13T07:17:23.504930+01:00 lab kernel: [41903.232755] usb 1-4: New USB device strings: Mfr=1, Product=2, SerialNumber=0
2024-03-13T07:17:23.504933+01:00 lab kernel: [41903.232761] usb 1-4: Product: QDX Transceiver
2024-03-13T07:17:23.504934+01:00 lab kernel: [41903.232765] usb 1-4: Manufacturer: QRP Labs
2024-03-13T07:17:23.508949+01:00 lab kernel: [41903.235416] cdc_acm 1-4:1.0: ttyACM1: USB ACM device
2024-03-13T07:17:23.513661+01:00 lab mtp-probe: checking bus 1, device 4: "/sys/devices/pci0000:00/0000:00:14.0/usb1/1-4"
2024-03-13T07:17:23.513836+01:00 lab mtp-probe: bus: 1, device: 4 was not an MTP device
2024-03-13T07:17:23.546437+01:00 lab systemd[1936]: Reached target sound.target - Sound Card.
2024-03-13T07:17:23.546901+01:00 lab systemd[795]: Reached target sound.target - Sound Card.
2024-03-13T07:17:23.549359+01:00 lab mtp-probe: checking bus 1, device 4: "/sys/devices/pci0000:00/0000:00:14.0/usb1/1-4"
2024-03-13T07:17:23.549495+01:00 lab mtp-probe: bus: 1, device: 4 was not an MTP device


As you can see the port changed from /dev/ttyACM0 to /dev/ttyACM1, and its not recognized correctly anymore. Also the "Soundcard"-devices aren't available anymore ... sometimes the input device "survived", but the output-device is gone each time.


Any hints what to do/test?


Cheers,
Torsten

--
vy 73 de Torsten | DO4TE

/"\ ASCII Ribbon Campaign
\ / Against HTML Mail
?X www.asciiribbon.org
/ \

Got my QMX on Monday March 10th. Did 2 QSO's 20m.
CQ'ing again on tuesday - no rx at all. Transmit is fine to me.

1 - board revision: Rev3 so Hans told me - got it assembled from QRP-Labs and do not open it.
2 - Bands: low, 80-20 m
3 - build supply voltage: 12 V
4 - FW version: 1_00_017
5 - modifications: none

I am slightly frustrated...
cheers - Raimund

I think the thumps are coming from the AGC and you disabled it. increasing sidetone volume to 60 also somehow helps.

Simon

I only just started to test my QMX with a paddle a few days ago.? Initially I experienced the severe sidetone clicks that have been reported with the latest and previous version of firmware.? I made a few arbitrary changes to the settings as follows and the clicks have vanished completely!?





and a sample of here's the signal being produced


73 Chris - M0KNF

Hi Greg,

I bought an unbuilt kit of the same vintage recently.
It requires a capacitor on the power input to prevent potential damage from supply spiking.
D33 cathode to 0V.
10uF tantalum or electrolytic.
Described and shown in QCX-mini assembly Rev1.05. Pages 67 - 69.

If you’re installing AGC module there are a couple of wires to be added, information in AGC manual.

73.

Hello Emory,

12, 11, and 10 meters share the same low pass filter (LPF).? This would point to a problem there.? The most common is one of the toroid connections did not burn through the enamel.? This assumes that the configuration is correct.? I suggest the following:

1 - Update to the latest firmware from the QRP-Labs web page:?


2 - Do a factory reset

If the above does not solve the issue, then:

3 - Verify that the LPF diode selection is working correctly.? This also verifies that the toroid connections are good, as the toroids are used to conduct the DC bias.? The LPF diodes are D508 through D513.? D510 and D513 select the 12/11/10 meter LPF.? The banded end (Cathode) should be close to 0 volts.? The other four should be close to the supplied voltage to the QMX.? This test is while receiving, not transmitting.

The next steps would depend on your findings from the above.? Please post your results, including the version of the firmware.

73
Evan
AC9TU

Just a note that this issue of? some of Granberg's pronouncements and inconsistencies is still being looked at.

1.? John Z's comment about? Adsl? Line drivers applies to some? Texas chips . I think the part numbers start MHD.? Anways they can be driven from 24 V and?
the indications are they would produce about? 6W rf out up to 30 Mhz.? The 30 Mhz is from the Tx industries'? datasheet.

2. Some basic work on the? phasing choke used in the Kees Talen? 16 W RF amp? (13.8 V supply) shows that the? ?BN 43-302 appears to only just work.? That's to say? it appears to be near saturation and that would cause the impedance to fall away badly.? This? would lead to power from the primary of the? OP transformer being dumped into the series impedance of the RF choke.? ? I need to do some LTspice simulation? on this aspect (but bear in mind LTS treats magnetic components as completely linear ). H? Granberg? ?(EB and AN series from Motorola) provided no discussion of? Pt choke design anywhere I can see - eg impedance requirements versus the parasitic impedance of the transformer primary it was driving or any criterion like that.?

Will report in due course.? TEF