开云体育

ctrl + shift + ? for shortcuts
© 2025 开云体育
Date

Re: accurate time source

 

I use NetTime 3.14 from www.timesynctools.com on all my windows machines, no
problem. Just install it and forget its there. Seems to work, flawlessly for
me, over wired networks, Wi-Fi,networks 3G and 4G networks using mobile
routers and pocketable 'hotspots', Cannot speak for 5G, there are no 5G masts
anywhere near, nearest I believe is 75 miles away.

Linux, the sensible OS, just does it without any user intervention..

On 24 Aug 2023 at 6:34, wb2cba@... wrote:

Dimension 4 is a reliable time sync software.



73

Barb WB2CBA


Re: QMX - TX shift thrshld bug?

 

Thanks Dan, Noted, I will fix it in the next firmware version.

73 Hans G0UPL



On Fri, Aug 25, 2023 at 2:43?AM N7SHM <n7shm@...> wrote:
I think there's a bug in the "Configuration --> Digi interface --> TX shift thrshld" entry field.? It defaults to '500' (milliHertz), but no more than two digits (00-99) can be entered from the terminal or directly.

This is with firmware versions 006 and 009, at least.

73,

? Dan
? N7SHM


Re: QMX - smoke - another C107/Q108 failure

 

Hello Razvan

If you use linear 3.3V and 5V power supplies it will work fine, and there is no harm in the 5V coming alive before 3.3V. In order to make the processor complete the boot process you will need to arrange the 3.3V and 5V ADC measurements to both be above 1.65 and 2.5V respectively; the easiest way to do this is simply connect them to the 3.3V supply rail.?

73 Hans G0UPL



On Fri, Aug 25, 2023 at 12:38?AM DL2ARL <dl2arl@...> wrote:
On Thu, Aug 24, 2023 at 01:46 AM, Rick Crowther wrote:
I meant only to rig up temporary linear supplies on my bench
hello Rick, Hello Hans,

this is exactly what I was aiming for myself: a temporary replacement of the smps boards until all other smoke tests have been succesfully passed.

Hans: really no offence intended! I am of an older school and do not trust these new-age gadgets piloted by software, not because of paranoia, but because of the fact that they do not belong to my trusted analog world. I find the ideas standing behind the SMPS concept of the QMX most refreshing and innovative: this is the main reason I am glad of having purchased a QMX, without having been in need of yet another qrp toy.

But now.. I am sort of discouraged by my own courage and would like to go one step behind into those quiet linear waters I am used to. Not for good, but at least for the first current intake of the fine rig. Afterwards, having thanks to Chris a test checklist for the SMPS boards outside the rig, without danger of damaging the main professor, I would maybe gain some courage and "replace the linear replacement" with it's new age microprofessor controlled switching PS.

This is what I meant. You might help by telling me if this is doable or if I am to expect some latch-up phenomena during power-up due to the fact that the 5V rail would come alive before the 3,3V would do. But latch-ups are not harmfull, so if you do not have an answer to this question, just forget it: I will find it out by myself.

Yours friendly, Razvan dl2arl?


Re: QMX - Short from 5V to ground somewhere on the main board

 

I should add -

No current draw on initial powerup. Significant current is drawn while pressing left knob. Current goes back to zero after releasing left knob.


Re: USB Device not recognized .... another one #qmx

 

Rick,

Great to hear about your success. However................

Here is a little more about the USB-C connector. The connector is designed around 8 pins and the shields. The connector is designed to accept a USB-C plug which can be plugged in right side up OR?upside down. The connector has 2 rows of 8 pins? on both the top and the bottom of that center insulator. Of course, one goes left to right and one goes right to left ......makes sense. I believe that Hans wired identical pins together between the 2 rows. This would increase the probability of making a connection to the few pins actually used but it does not fix the problem.?

I even saw a picture of someone who had added 16 solder balls to his USB-C connector.? However, you can't see how well the solder has wicked to the very short pin, so maybe.

A much more solid connection can be had with the "toothpick and flux technique" described in my other note. That way you can SEE to solder wicked from the pin to the via barrel. When I examined my kit USB-C connector the 16 pins are all helter skelter inside the via barrels. Some look like they picked up a small dab of solder out of the plated barrel, some were touching, some were not. Talk about "iffy connections". Manufacturers typicall do not use solder paste screening on PIH parts. No wonder there are multiple? USB-C download tries, may require a new (flipped) USB-C plug, may require a little connector wiggling, etc. The net is that it may have an "iffy" contact and may fail later.?

A GOOD, much more solid, connection can be had with the "toothpick and flux technique" described in my other note.?

73 Kees K5BCQ



.






QMX - Short from 5V to ground somewhere on the main board

 

Booted up the new QMX on my bench power supply, managed to flash firmware, hooked up a dummy load to test TX and forgot to increase current limit on the power supply, so it browned out on TX. Then it died, and I'm showing a short from 5V rail to ground that is not on the power supply daughter card, it's on the main PCB.... somewhere. Any tips for figuring out where it is (and why that would have happened) are appreciated.


Re: List of QRP Labs USB Vendor and Product IDs for Serial Ports - ChromeOS

 

Hi

> idVendor=0483, idProduct=a34c

All QRP Labs products use this same VID/PID which is licensed by ST Microelectronics to QRP Labs for exclusive use by QRP Labs amateur radio products using STM32 microcontrollers. I'm very grateful to ST for this assistance as full USB-IF membership and VID/PID is prohibitively expensive for small businesses.?

73 Hans G0UPL



On Fri, Aug 25, 2023 at 7:20?AM jlloydham <captlloyd@...> wrote:

I'd like to get the cdc_acm serial port on the QDX to work on ChomeOS in the Linux (Crostini) container. I'm looking for the Vendor IDs(VID) and Product IDs(PID) for all QRP Labs products so everyone can benefit, not just QDX owners.

On ChromeOS USB devices can be passed through to a Linux container. Currently the QDX works great on Crostini(Full OS container on ChromeOS) except the /dev/ttyACM* device from the cdc_acm driver is not passed through to the container. You can still use a terminal app from outside the container to manually send CAT commands and use VOX but there's no ability for WSJT-X or JS8Call to talk to the serial port.?

I'm opening a request to have these added to the list of devices allowed for pass through. They've done this for other cdc_acm devices when requested. I'm going to ask if all cdc_acm devices can be passed through but they may have a reason to stick with white listing by VID/PID.

I have the VID/PID for my QDX but I'm not sure if there are any other chips/IDs being used on other QRP Labs products and/or versions. If someone has a comprehensive list that would be great, but I'll take them individually here if people want to post them. I'll collect what I get over the next few days and submit a request to the Chromium bug tracker.?

Linux users can plug in their device and check the output of 'dmesg'. I'd be looking for a block of text like this:

[ 1410.951927] usb 1-1.1: new full-speed USB device number 8 using xhci_hcd

[ 1411.134168] usb 1-1.1: New USB device found, idVendor=0483, idProduct=a34c, bcdDevice= 1.00

[ 1411.134181] usb 1-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=0

[ 1411.134185] usb 1-1.1: Product: QDX Transceiver

[ 1411.134188] usb 1-1.1: Manufacturer: QRP Labs

[ 1411.177327] cdc_acm 1-1.1:1.0: ttyACM1: USB ACM device



QMX step 12 continuity oddity

 

Hello fellow QRPers,

?

I am enjoying my QMX build, yet I’ve run into a snag on step 12 page 31 (the first specified continuity checks). I am hoping that someone has either seen/rectified a similar issue, or may have some tips on how I might move forward.?

?

I’m attaching a screenshot that shows the results of the continuity checks, after installation of the larger binocular transformer, and after having gone back to really ensure that the enamel has been properly scraped off prior to completing the solder joints. As you can see in the image, there is a low resistance, approximately 10 ohms conductivity showing between A and B.?

?

I have examined all of the other component connection points, and I’m not identifying any solder bridges, nor clippings, nor whiskers. As far as I can tell, my board doesn’t suffer any of the SMC bridges that have appeared on a few of the boards. I do plan to flip the orientation of D508 to make additional room for L508, but the polarity is already correct.?

?

Any tips are appreciated!

?

Thank you,

Garrett KC3UNP



List of QRP Labs USB Vendor and Product IDs for Serial Ports - ChromeOS

 

I'd like to get the cdc_acm serial port on the QDX to work on ChomeOS in the Linux (Crostini) container. I'm looking for the Vendor IDs(VID) and Product IDs(PID) for all QRP Labs products so everyone can benefit, not just QDX owners.

On ChromeOS USB devices can be passed through to a Linux container. Currently the QDX works great on Crostini(Full OS container on ChromeOS) except the /dev/ttyACM* device from the cdc_acm driver is not passed through to the container. You can still use a terminal app from outside the container to manually send CAT commands and use VOX but there's no ability for WSJT-X or JS8Call to talk to the serial port.?

I'm opening a request to have these added to the list of devices allowed for pass through. They've done this for other cdc_acm devices when requested. I'm going to ask if all cdc_acm devices can be passed through but they may have a reason to stick with white listing by VID/PID.

I have the VID/PID for my QDX but I'm not sure if there are any other chips/IDs being used on other QRP Labs products and/or versions. If someone has a comprehensive list that would be great, but I'll take them individually here if people want to post them. I'll collect what I get over the next few days and submit a request to the Chromium bug tracker.?

Linux users can plug in their device and check the output of 'dmesg'. I'd be looking for a block of text like this:

[ 1410.951927] usb 1-1.1: new full-speed USB device number 8 using xhci_hcd

[ 1411.134168] usb 1-1.1: New USB device found, idVendor=0483, idProduct=a34c, bcdDevice= 1.00

[ 1411.134181] usb 1-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=0

[ 1411.134185] usb 1-1.1: Product: QDX Transceiver

[ 1411.134188] usb 1-1.1: Manufacturer: QRP Labs

[ 1411.177327] cdc_acm 1-1.1:1.0: ttyACM1: USB ACM device



Re: USB Device not recognized .... another one #qmx

 

SUCCESS!!

I resoldered the encoder switches and I was able to get electrons to flow. About 170 mA at 9 VDC (wired for 12 VDC).? The USB port was still not recognized so I gingerly resoldered it. Still no USB port recognized by Win10. But I'm getting closer.?

Finally I tried another USB cable and this time SUCCESS!!! The little QMX booted to 7.074 MHz CW!

The QMX is up and running. I'll do some TX and RX tests tomorrow, but today has been a good day. (Even though I got older - hi!)

Thanks to all who gave me some help!
--
73, Rick
VE7TK

Website:


Re: #QMX Are these Issues? #qmx

 

开云体育

And apparently D102, too. :-(

On 8/24/23 18:14, Paul - AI7JR via groups.io wrote:

I think I found it! R104 is missing on the PS board! Must've gotten knocked off when I was using the air gun to demount Q103...

Have to look at my resistors, now!

Paul

On 8/23/23 22:06, Paul - AI7JR via groups.io wrote:
Is there some kind of log for QMX issues? Don't want to bore anybody by reporting what's known, or my build defect!

Here's what I'm seeing (I've got Firmware version 9 loaded, 7volts, 250ma current limit):

  1. On application of power, initial current is 0, but goes to around 10ma after 10-15 seconds. Stays steady after it comes up.
  2. On initial power application, power on click is ignored, until the above 10ma step in current.
  3. At that point, power on click "delays" for ~10sec, then display comes on and 150ma current draw.
  4. Tune knob frequency only goes up?
  5. Long press power click displays Shutdown, but LCD never goes off, current (150ma) never drops.
  6. While "Shutdown" is displayed, band and mode can be changed!
  7. Going back to 3, if the power is interrupted briefly (maybe 200mS), device turns off. Pressing power-on click activates immediately!

I what I'm seeing "normal" at the moment? :-)

Haven't gotten so far as to transmit or receive, either one. (Need to read that operations manual!)

Please forgive if this is the wrong place to put this!

73, Paul -- AI7JR


Re: QDX Success story

 

One thing that comes to mind when comparing the inductive spike at the drains between the TN/VN*06 and the BS170 - you saw a 120V spike with the former compared to 60V with the BS170 - is that the BS170 is not turned on all the way with a 5V drive while the *06 devices are more strongly turned on due to their lower gate thresholds. This was the primary reason I suggested the *06/*10 FETs. The lower gate threshold of the *06 FETs results in a higher drain current which builds a larger magnetic field in the inductor and therefore a larger inductive kick when the FET turns off. Regardless of what physical limitations in the BS170 are clamping the spikes at 60V, the *06 devices will produce a larger spike and will also produce more power output because they’re simply better switching transistors than the BS170 for the existing PA design. They also dissipate less power than the BS170 because Vds is smaller when they’re on. In any event, I certainly would not recommend allowing a spike over 60V so the clamp diode is a good addition. Long story short and with all other things being equal, the TN/VN*06 transistors are better suited to the existing PA design than the BS170. Others on this forum have found this swap to be very beneficial and I’ve yet to hear a complaint of any *06 devices blowing.

Tony - AC9QY

On Tue, Aug 8, 2023 at 7:01 AM mux_folder2001 <canthony15@...> wrote:
The diode is a good idea I think. Thisis based not only on simulation but on measurements I have made with my scope.

In my case, the loss of two or three sets of BS170 in my two QDX units led me to try different transistors. I ran the other transistors without any failures we for months. But I was curious why the BS170s would fail and the TN0106 and VN0606 would not. Yesterday I got a new scope that allows me to see transients and I decided to look at the QDX with VN0606 transistors in it. To my surprise, the glitch at the end of a transmission was over 120 volts measured at the center tap. The transistor drains were similar. The spike was 100ns wide at the 60 volt level. And this is into a dummy load. The transistors must just be capable of dealing with this.

I then replaced the transistors with BS170s and discovered another surprise. The spike was below 60 volts and had a broad flat (but ragged looking) top.?

Then I added the commutating diode and the spikes were gone.?

Right now my theory is that the BS170s are operating in a "make before break" mode which minimizes the di/dt. The VN0606 (and TN0106) might be in the "break before make" mode. The specific operating conditions might possibly allow the circuit to move between these two cases and the BS170s are just not capable of handling the over-voltage spike while the other transistors can. Just a theory mind you. I have not tried yet to make measurements to verify this. Prior to these measurements, I was thinking that the opposite would be the case, thus explaining why the VN0606/TN0106 did not fail.?

In any case, I am now running with BS170s again but with the diodes installed. We shall see how long this lasts.

Tony
AD0VC


From: [email protected] <[email protected]> on behalf of John Z <jdzbrozek@...>
Sent: Monday, August 7, 2023 6:14 AM
To: [email protected] <[email protected]>
Subject: Re: [QRPLabs] QDX Success story
?
Simulations are here:

/g/QRPLabs/message/105254

JZ

On Mon, Aug 7, 2023 at 8:07?AM John Zbrozek <jdzbrozek@...> wrote:
>
> Hi Pierre,
>
> The diode simply is in parallel with the 47uH inductor L14, with the
> orientation shown in the photo provided by Paul W9AC. Cathode towards
> the power supply connection, anode to the transformer center tap.
> Any of the diodes he mentioned? (1N4448, 1N4148, 1N914) will do a fine
> job of absorbing the end-of-transmission voltage spike it produces.
> I have used a 1N914.
>
> /g/QRPLabs/message/105256
>
> Here you can see simulations with and without the diode present.
>
> On another thread, Evan, Hans and I explore the ability of QDX to
> withstand SWR. It seems to have a reputation for SWR intolerance but I
> think there is a case that the problem may actually be as described
> above.
>
> /g/QRPLabs/message/106759
>
> Regards, JZ KJ4A
>
> On Mon, Aug 7, 2023 at 7:46?AM Pierre FK8IH <jb.gallauziaux@...> wrote:
> >
> > Could you please elaborate: what diode, how did you connect it? A handmade schematic and a photo would be nice.
> > 73
> > Pierre
> > FK8IH
> >






Re: USB Device not recognized .... another one #qmx

 

Rick,

That would make a difference. I assume you also don't have 5V VCC nor 3.3V VDD then

But back to the "no USB" :
Looking at the USB connector pins in your picture, I would say at least 2 pins need to be re-soldered.

Having the pin contact the via barrel and soldered to the barrel is fine but those 2 appear to be really centered in the via barrel hole and the pins are quite small (and short). This will vary from USB connector to USB connector since the locator pins have room to move a little during assy.

What I would recommend is use solder flux (flux pen) and carefully touch each pin (maybe use a toothpick) then use a bit of solder. What you want to do is have the surface tension of the solder to the pin/via barrel draw the solder into the via barrel. Use very little solder and check for unwanted shorts between the surface pads.

Only?SOME?of the USB pins are actually used so you might assume it's OK......but it depends on the pin.

73 Kees K5BCQ





73 Kees K5BCQ

?


Re: #QMX Are these Issues? #qmx

 

开云体育

I think I found it! R104 is missing on the PS board! Must've gotten knocked off when I was using the air gun to demount Q103...

Have to look at my resistors, now!

Paul

On 8/23/23 22:06, Paul - AI7JR via groups.io wrote:

Is there some kind of log for QMX issues? Don't want to bore anybody by reporting what's known, or my build defect!

Here's what I'm seeing (I've got Firmware version 9 loaded, 7volts, 250ma current limit):

  1. On application of power, initial current is 0, but goes to around 10ma after 10-15 seconds. Stays steady after it comes up.
  2. On initial power application, power on click is ignored, until the above 10ma step in current.
  3. At that point, power on click "delays" for ~10sec, then display comes on and 150ma current draw.
  4. Tune knob frequency only goes up?
  5. Long press power click displays Shutdown, but LCD never goes off, current (150ma) never drops.
  6. While "Shutdown" is displayed, band and mode can be changed!
  7. Going back to 3, if the power is interrupted briefly (maybe 200mS), device turns off. Pressing power-on click activates immediately!

I what I'm seeing "normal" at the moment? :-)

Haven't gotten so far as to transmit or receive, either one. (Need to read that operations manual!)

Please forgive if this is the wrong place to put this!

73, Paul -- AI7JR


Re: QMX - smoke - another C107/Q108 failure

 

Razvan said :
"...
the 5V rail would come alive before the 3,3V would do. But latch-ups are not harmfull, so if you do not have an answer to this question, just forget it: I will find it."

Dear Razvan,

The latch up phenomenon that CMOS components exhibit is much more dangerous than that and is to be avoided!

It's effects are unpredictable, ranging from the harmless and resettable condition that you mention to the full? destructive meltdown of the affected component, having made a massive short circuit between supply rail and ground!

Everything depends on the regenerative gain of the parasitic SCR that is intrinsic to the CMOS structure, and of the level of the current that is? being inappropriately injected into that SCR.

Modern CMOS circuits and processes have been engineered with latch up avoidance as an objective, and they have some forgiveness. Risks remain however. The processor in QMX for example has many pins that can "eat" an injection current of up to 5 mA without latch up or other damage. Some of the pins on that processor have zero tolerance for injected current!

Just an FYI, Razvan.

Wishing you well, JZ KJ4A?


On Thu, Aug 24, 2023, 5:38 PM DL2ARL <dl2arl@...> wrote:
On Thu, Aug 24, 2023 at 01:46 AM, Rick Crowther wrote:
I meant only to rig up temporary linear supplies on my bench
hello Rick, Hello Hans,

this is exactly what I was aiming for myself: a temporary replacement of the smps boards until all other smoke tests have been succesfully passed.

Hans: really no offence intended! I am of an older school and do not trust these new-age gadgets piloted by software, not because of paranoia, but because of the fact that they do not belong to my trusted analog world. I find the ideas standing behind the SMPS concept of the QMX most refreshing and innovative: this is the main reason I am glad of having purchased a QMX, without having been in need of yet another qrp toy.

But now.. I am sort of discouraged by my own courage and would like to go one step behind into those quiet linear waters I am used to. Not for good, but at least for the first current intake of the fine rig. Afterwards, having thanks to Chris a test checklist for the SMPS boards outside the rig, without danger of damaging the main professor, I would maybe gain some courage and "replace the linear replacement" with it's new age microprofessor controlled switching PS.

This is what I meant. You might help by telling me if this is doable or if I am to expect some latch-up phenomena during power-up due to the fact that the 5V rail would come alive before the 3,3V would do. But latch-ups are not harmfull, so if you do not have an answer to this question, just forget it: I will find it out by myself.

Yours friendly, Razvan dl2arl?


Re: accurate time source

 

My off grid computer uses BK TimeSync and a USB GPS.



I find that it works very well. I exclusively use it every time. My computer is turned on whether it is on line or completely off grid.


Re: New QRP-Labs product idea? A QMX/QDX based digimode / cat interface?

 

The Microham USB interface III driver/configuration program works fine on my W10 machine.
Gary
W9TD


Re: accurate time source

 

Steve I use dimension4 with Win10 and Win11. No problems.

73

Barb WB2CBA


Re: QDX xmit one flash

 

Wayne,

I noted that you have disallowed applications from using the QDX audio card:


Change the "Don't Allow"

73
Evan
AC9TU


QMX - TX shift thrshld bug?

 

I think there's a bug in the "Configuration --> Digi interface --> TX shift thrshld" entry field.? It defaults to '500' (milliHertz), but no more than two digits (00-99) can be entered from the terminal or directly.

This is with firmware versions 006 and 009, at least.

73,

? Dan
? N7SHM