Keyboard Shortcuts
ctrl + shift + ? :
Show all keyboard shortcuts
ctrl + g :
Navigate to a group
ctrl + shift + f :
Find
ctrl + / :
Quick actions
esc to dismiss
Likes
- QRPLabs
- Messages
Search
Re: Real time clock
开云体育Yes it does on my QMX+. You might check your battery.John KK4ITX? ?Each mistake is a learning opportunity.? On Apr 2, 2025, at 10:44 PM, Rick Hill via groups.io <6xraytango@...> wrote:
|
Re: qmx+ cw reader
开云体育GE Martin,I would start with the settings that are in the manuals, then; * Turn the volume down! If too loud it’s hard to translate. * Next adjust your filters correctly? * Try to use the Noise Blanker The rig needs to hear the cleanest signal you can feed it. When it’s not clean you get “*”. Sometimes you have to move slightly off frequency to get the best results. You can usually achieve 70-90%, you have to be able to fill in the blanks. The QMX+ seems to be better than my 3 QCX rigs but I am new with the QMX+. Hopefully this helps, John? KK4ITX? ?Each mistake is a learning opportunity.? On Apr 2, 2025, at 11:10 AM, Martin DK3UW via groups.io <m.sellschopp@...> wrote:
|
Re: Help with partially fried QMX
Hi Steve.? Thanks.
So even the CENTER of the BNC?? the middle, radiating contact of the BNC is connected to ground via T507?? MyBS170s look fine.? Is there a way to test them?? It makes sense that they would pop first, but i've no idea how to test them.??
?
Is there a single spot, somewhere on this forum, where it lists key measurements to check when troubleshooting?? I must have made Google a million dollars in eyeball hits in my searches over the last week.
?TNX again!
JD |
Re: QMX+ rev 3 freezes shortly after boot
Alright! I've got some updates.
?
I pulled off the front panel and did a close inspection of the display connections, didn't see anything obvious but cleared out some plastic and some small fibers, possibly from my sweater or ambient dust.
?
Checked R110 and R112, both of those appear to be in fine condition. During normal operation both read at around 1.6V.
?
Checked resistance between VDD & VCC. When my positive probe was on VDD & ground probe was on VCC, the resistance started at around 3.2kΩ and maxed out at around 4.46kΩ.
?
When my positive probe is on VCC and ground probe on VDD, it starts at 2.8kΩ then climbs up to around 6kΩ, then there's a spike up to 28kΩ, then it descends back down to and stabilizes at around 7kΩ.
?
I checked D109 and it seems good as well - no obvious heating or anything like that.
?
No GPS currently installed, and it wasn't installed during any of my earlier tests.
?
Now for the interesting part. After checking all of the above, I turned it on and held steady for about 5 minutes. So I thought I'd try out the terminal again. This time I was able to connect! Previously, it would freeze at the exact moment I hit "enter" to initiate the serial connection. This time I was able to open the menu and even run some diagnostics! Attaching the screenshot from the diagnostics view below.
?
In fact the terminal session was going so well, I thought I might've cleared up whatever the issue was. Unfortunately, it froze again shortly after that. I believe I'd entered into the RF Filter Sweep menu item and was watching the output when I saw the current jump from 0.8A to 0.20A and cut the power.
?
The only substantive things I can think of that I did were:
?
I am wondering if it's temperature related or possibly related to a capacitor somewhere(?), because it seems to perform much better after 10+ minutes of no use, vs 30 seconds to 1 minute of no use. If I wait 10 minutes or more, I can usually get a good few minutes of use, but if I only wait a few seconds or a minute after cutting power, it will either start in the frozen state, reach the frozen state after a few seconds powered on, or the screen wont power on at all, and rather than drawing 0.20A, it'll draw about 0.14A.
?
?
?
?
?
? |
Re: Debugging BS170-related issues
Success !
?
When in doubt, try the simplest thing first.
?
After an afternoon spent looking for the esoteric solution, I touched up all the IC503 pins with the soldering iron.
?
4-5 watts on all bands, again.
?
Many thanks to Ludwig, Stan and Chuck for their help.
?
73,
Steve, N2IC
|
Re: ProgRock2 programming??
Thanks Alan, I’ll measure the xtal socket and see what’s on each pin. I’ll have to be careful to put the voltage pin on a socket with 5v regulated voltage.
toggle quoted message
Show quoted text
73 Tom On Apr 2, 2025, at 1:50?PM, Alan G4ZFQ via groups.io <alan4alan@...> wrote: |
Re: Gibberish characters appended onto end of Message 1
Hi Braden
Putty is the favoured terminal software, works on Windows and Linux.
73
Roger
8P6RX
Get
On 2 Apr 2025, at 19:04, "Braden Glett via " <gmail.com@groups.io target=_blank>[email protected]> wrote:
|
Re: Lin_reg_en
#troubleshooting
开云体育Thanks for the ideas – so a bit of probing and VDD to GND is like .5 ohms – without the smps board installed . Any ideas where to start looking for the short? ? thanks ? From: [email protected] <[email protected]> On Behalf Of Stan Dye via groups.io
Sent: Monday, March 31, 2025 1:24 AM To: [email protected] Subject: Re: [QRPLabs] Lin_reg_en #troubleshooting ? Also inspect carefully the interconnect of the LIN_REG_EN signal fromthe smps card to the main board, ensuring nothing there is pulling it down. |
Re: Help with partially fried QMX
I am also trying to diagnose a fried (?) board, Rev 4, ordered and built in the last couple weeks. wound for 9V.
?
As posted elsewhere, i had an issue with a powerboard, replaced it, and it worked fine for about 12 hours.? made some FT8QSOs (two new DXCC for me even!), and some CW contacts and RBN showing well into europe and across US.
?
But then it all just suddenly stopped.? All terminal diagnostics are pretty much exactly as shown in the operation manual, the only issue being no power out on pressing T.? What i did discover was continuity between the center pin (radiator) of the BNC connector and ground. I removed the BNC connector but the issue turns out to be with the main board. With the BNC connector removed, there is no continuity between the female center and the outer housing.
?
Any suggestions on where to look first?
?
Thanks in advance.?
JD |
Re: Gibberish characters appended onto end of Message 1
I figured out how to delete the entire message. Then, I re-entered the message but I am still getting gibberish sent at the end of the message that I did not enter.
The gibberish is K0****AS?
This renders the message function to be useless.?
I hope no one is listening to the CQ I'm sending.?
Buying a pre-assembled unit, I was hoping not to be doing debugging. Oh well.? |
QMX terminal using GNU screen
Somebody asked me how I access the QMX terminal settings if the radio is connected to a headless Raspberry Pi that I can connect to only with a text based ssh connection (or through a browser window with ttyd). Without a graphical desktop system, tools like Putty don't work. So, here are some notes on using GNU screen for this.
GNU screen is a text based terminal multiplexer that is widely available on Linux machines. If it isn't installed on your raspberry pi, you can install it with 'sudo apt install screen'. I often use it so that, after I connect to the pi using ssh, I can create multiple windows (tabs) that I can switch between to run multiple programs. If my ssh network connection to the pi is closed, programs running in screen windows (like ardopcf or pat) continue to run, and I can reconnect to them later. See 'man screen' or various online articles and videos for a description of this normal usage. A less well know use of screen is to connect to a serial device with it. So, if the QMX is connected to the pi with a USB cord, so that it appears as virtual serial port '/dev/ttyACM0', you can open the QMX terminal using the command: 'screen /dev/ttyACM0'. Just like when connecting with Putty, this displays a blank black screen until you press <Enter>, and then you will see the QMX terminal menus. Keyboard input including arrow keys should then work as expected. However, there are two things that are different than when using a program like Putty. First, Ctrl-Q, which Hans chose to use to back out of various sub-menus and screens, does not work when using GNU screen. To send Ctrl-Q to the QMX, you need to type Ctrl-a and then q. Second, to close a screen window, usually after selecting the 'Exit terminal' command in the QMX menus, type Ctrl-a and then k. This will prompt you with 'Really kill this window [y/n]', so type y. If you are already running screen, perhaps with multiple windows, you can also open a new window to connect to the QMX by typing Ctrl-a and then typing ':screen /dev/ttyACM0' (without the quotes) and pressing <Enter>. Once you type the colon (:), it and the remainder of this command will appear in the lower left corner of the window until you press<Enter>. When you are done, typing Ctrl-a and then k will close this window but not any other screen windows that you have created. Hopefully some of you will find these notes useful. Using the QMX terminal is even more important now with the changes in the new SSB beta firmware. Peter LaRue AI7YN |
to navigate to use esc to dismiss