Keyboard Shortcuts
Likes
- QRPLabs
- Messages
Search
Re: QMX step 12 continuity oddity
开云体育Garrett,It still makes on sense to me that you have continuity between B1 & B2, but B2 shows 10 ohms to the A points and B1 does not. Try swapping your probes around and see if that changes anything. I'm assuming that by continuity you mean 0.0 ohms or very close to that. 73, Cliff, AE5ZA
|
Stuck on my QMX build
Hi, can anyone suggest where to go next please.
Connect power, no current draw. press on button PC sees QMX current draw approx 160ma, load software and LCD lights up with splash screen (software version QMX ect) and thats all. Turn off power unplug pc press start current draw about 160ma but nothing on display. wait try again nothing. Connect to PC reload software and LCD lights up, but same situation as above. It also does not turn off the current draw if i hold the power off button. I stripped and rebuild the contols board and check every conection and switch opperation. Any advice would be appreciated? Mike |
Re: #QMX holy smoke released again, C107 and D108 destroyed
#qmx
g4edg
Hi Gunnar
I noticed that C107 was getting warm at a supply voltage of 6v, and that D108 ceased working as a zener. C107 is only rated at 6.3v according to the parts list...which is OK til something goes wrong and it gets the full supply voltage across it. Tantalums always put on a good show!? I had no PWM5V from the processor in my case and Q106 was full on, causing? the "full 6v" to appear across C107...at 13.8v I cant imagine. 73 Steve G4EDG |
Re: QDX Build Completed
On 26/08/2023 10:04, Alan G4ZFQ via groups.io wrote:
Radio Hams need to turn off all audio "enhancements"That reminds me, Dell computers run a service "Waves Audio Services" that should be disabled. I'm not sure it has affected me but some users of WSJT-X have reported problems. There was also another Dell service but I do not see that anymore. 73 Alan G4ZFQ |
Re: No Sound Card digital modes
Wsjtx does however at least show what is being sent and received in two places other than the screen. In the UDP data stream, and logged in the all.txt file.
What I managed to do for my experiment is to track the all.txt file with a small node.js app, encode that message to ft8 frequency offsets and send that number via serial port to the Arduino that controls the si5351. It is clumsy but it kinda works. And no visible latency either.? While this is far from finished and useful, it is an idea how annoying "audio coupling" between wsjtx and a transceiver that does direct signal generation can be done with a small software shim. In theory, it wouldn't be too hard to add optional "current message output" to existing wsjtx cat serial data, but haven't explored that yet.? |
Re: QDX Build Completed
On 26/08/2023 09:32, John Shufflebarger wrote:
Turned out my transmit issues were due to some "automatic" attenuation that defaults on Windows 10 and 11John, I expect these settings satisfy 95% of Windows users. Radio Hams need to turn off all audio "enhancements" when they start using a Windows computer. 73 Alan G4ZFQ |
Re: QDX Build Completed
Late posting this, but want to complete the story.
Turned out my transmit issues were due to some "automatic" attenuation that defaults on Windows 10 and 11. Here is Paul Jorgenson's excellent post on the issue??/g/QRPLabs/message/104591?? After stopping windows from "automatically" lowering my output levels, getting transmit fine on all bands 80-20 |
#QMX holy smoke released again, C107 and D108 destroyed
#qmx
Well... I just finished my second QMX, the first one was toasted by increasing the supply voltage from 6V to 12V wiith a ramp-up time of 3milliseconds.
The full story is here:?/g/QRPLabs/message/106237 That one was? running firmware 1.07. Image. D109 was destroyed (short) so I removed it. After that my QMX turned on but power? consumption was200mA @12V input. Image rejection was nonexistant and bandpass filters totally wrong, so I concluded IC402 and/or IC403 were damaged. I decided to stop there and ordered a new kit Now the second QMX, finished last night: I loaded firmware 1.09 without problems. Everything was fine and I was just about to write something on the forum of a successful build. I wanted to put in some figures of RF power output and current consumption. Power output was fine 4W on all bands @12V supply. Image rejection and filter sweeps were also fine. Supply current about 100mA in receive and 600mA in transmit But while I was measureing supply current I heard a "crack" and the QMX turned itself off. I turned it on again by pressing the left rotary switch. Now I smelled burnt electronics. I opened the case and out came the holy smoke... C107 was now black and with a large crack in it. I took out the power board and removed C107 and measured the resistance between Vcc and GND. 733 Ohms in both directions with the DMM, so i removed D108. Now I had 75 kOhm in one diection and about 7 kOhm in the other. I also checked Q108, no short between terminals, so I guess it survived. So I took the 5V power board from my first QMX and put it into the second. And voila, everything back to normal. So what happened? During the current measurement It is possible that I interrupted the power supply line shortly when I disconnected the DMM without powering down the QMX before. But htis case was addressed by Hans in his article about SMPS behaviour during input voltage step... There is a saying in swedish "en g?ng ?r ingen g?ng, tv? g?nger ?r en gong-gong" Free translation: One time is OK, two times is an alarm clock. I can see that several QMXs have blown up C107. I think this is no coincidence. There is something going on here I recall that all who reported blown C107 were running 12V supplies with high current capability I suspect a HW/SW interaction: During a power interruption glitch, is it possible that the processor can leave the the PWM signal high, thus creating a voltage increase that kills C107 and D108? I would suggest that the PWM-signals should be AC-coupled so that if stuck high, the SMPS would turn itself off. 73 de SM5EIE /Gunnar ? So I ordered? |
Re: QDX 20-10 9v
On 25/08/2023 20:09, W GALAUGHER wrote:
L4 started smoking. Yikes!Maybe a better description. What version QDX? L4?? are you sure? Terminal shows only 80m, do a reset? WSJT works? RX and TX? All bands? USB sketchy? How? D1, 4 shorted? Seems unlikely. 73 Alan G4ZFQ |
Re: New QRP-Labs product idea? A QMX/QDX based digimode / cat interface?
On Thu, Aug 24, 2023 at 08:51 PM, Gary W9TD wrote:
The Microham USB interface III driver/configuration program works fine on my W10 machine.I downloaded the new driver and virtual port installer yesterday. I tried it on my laptop (Win10) and desktop (Win11) and all worked as expected, but haven't connected a radio yet. The cables I have were for some radios I no longer have.? I'll have to make some new ones. I am glad someone asked the question.? It made me look at a piece of equipment that I wasn't using - but could be! ------- Rob KB8RCO |
Re: #QMX Are these Issues?
#qmx
The voltage on LIN_REG_EN is a little over 0.7 volts when the power on switch is pressed, which leaves me a bit suspicious... Still don't understand what could've compromised the CPU.
|
Re: #QMX Are these Issues?
#qmx
开云体育Well, I thought I had an easy glide path. Repairing the Q103/Q104 short, I damaged (lost) R104 and D102. Turns out what I was seeing was, with no pull up, once connected to the supply the 12 volt supply drifted upwards until the unit turned itself on! Repaired the board with discrete components and tried powering up again. No Joy. :-( Looks like the repaired board is doing what it should, but the 3.3 volt supply (which had to be working before!) is not coming up because the linear 3.3 PS is not enabled. Gate voltage on Q102 is 8 V (what I've got my test supply set to). Gate voltage on Q101 is less than a volt. The 100k pull up resistor is in place, and the correct value. Only thing I can see is the LIN_REG_EN output of the uP must be pulling it low (before the uP has enough voltage to run!) Checked for shorts, nada -- 80-100k. Have I missed something? Any suggestions? Is the uP defective somehow, and how did it get that way when it was working, albeit strangely, before? TIA for any suggestions! A very frustrated, 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! |
Re: USB Device not recognized .... another one
#qmx
IT's ALIVE!!!
The QMX hears and transmits as well! (Ironically the 1st thing it heard was from the QRP-Labs SigGen!) On transmit without any adjustments at ~12VDC? into my QRPoMeter dummy load I measured: 80m?? 4.1W 60????? 4.0 40????? 4.1 30????? 3.7 20????? 3.5 Now to start setting the rig up!! I may even need to print out the operating manual! -- 73, Rick VE7TK Website: |