开云体育

Hi all I updated the SSB beta testing webpage of the brave, here: https://qrp-labs.com/qmxp/ssbbeta.html and released firmware version 1_01_003 to it. These are the changes: Bug fix: Initial value for noise gate samples was 100 (should be max 99) - makes no real difference but it needed to be fixed Added TX indication underlining the A character when transmitting from USB sound card in SSB mode. Note that the two possible states for this indication are a single dot (indicating PTT has been applied and now the radio is in TX mode) and the solid bar (indicating audio is being received from the PC and transmitted). There is no double-dot like there is in Digi mode indicating insufficient volume, because in SSB mode the radio transmits whatever you give it, even if the volume is low. Bug fix: CAT command TQ1; did not cause transmit when in SSB mode. Now TQ1; and TQ0; work properly in SSB mode. Bug fix: Prevent button presses from accidentally activating VOX, which was happening due to sound picked up from the internal (cancellation reference channel) microphone when you pressed buttons right next to it, and that prevented band change because the second click of the double click was ignored because by then the radio was in transmit mode. All fixed! Now you can click buttons however you like and when button clicks are done, VOX is temporarily disabled until your button pushing frenzy is over. Power meter now reads Peak Envelope Power (PEP) when in SSB mode. Previously it was just reading a sampled value (NOT an average); so if the power meter was updated 10x a second, the updates would just randomly pick a value from the SSB amplitude envelope, which was most unlikely to be its peak value. Bug fixL Calibration hung at DAC 1300 when run on LCD. Now the calibration completes properly when run from the LCD. Many thanks for all the feedback so far, SSB in QMX is getting better and better! 73 Hans G0UPL http://qrp-labs.com https://www.buymeacoffee.com/g0upl

Hans (and others who may know): On my QMX and QMX+, I have often wondered why the measured TX voltage, as shown in the Diagnostics page, always has a significant drop (about 1.5V) from the supply voltage. Looking at the schematic, it should have only the very small drop due to Q507. So (while answering someone else's question today) I measured the voltages at Q507 and ADC_PA with my DMM and oscilloscope, on my 12V QMX+ build, all measurements done at 7.074MHz. Diagnostic screen shows: - supply voltage 11.8V receive, 11.5V during TX - transmit voltage 0.4V receive, 9.8V during TX (the unexpected drop of 1.7V in TX voltage) DMM measurement shows: - supply voltage 11.84V receive, 11.48V during TX (measured at Q507 source terminal) - agrees well with QMX+ supply voltage measurement - transmit voltage 0.43V receive, 11.22V during TX (measured at Q507 drain terminal, a drop of 0.26V) - does NOT agree with QMX+ transmit voltage measurement - but is as expected from Q507 drop So it appears that measurement of TX voltage on QMX/QMX+ is not well calibrated. Could this be causing some of the problems seen in SSB calibration, etc? So I measured the voltage at ADC_PA with my DMM (at top of C529), in case it is helpful: - ADC_PA during diagnostic receive mode (off): 0.08V - ADC_PA during diagnostic transmit: 1.96V Using just the 47k/10k voltage divider ratio, this would equate to 9.2V (rather than the full 11.22 measured); hmmm, is this part of the problem? Or is there an expected additional resistance in the STM32 input that completes the voltage divider? Stan KC7XE

Is the QMX itself in any way capable to negotiate the required voltage with the power bank PD? In other words is a 12V trigger cable required or not? I feel more comfy with a trigger cable as it steers away from any negotiating. 73 es dx

Assembled my QMX+ and it's working. I had a couple of issues related to enameled wire not making good connections that were resolved. I know it's working, I've made contacts on several bands successfully, including some decent DX, all on FT8. What bothers me is that the output power seems to jump around wildly. If I go to the diagnostics screen and key the transmitter, the Bias SMPS shows fluctuations in current that correspond to the fluctuations in the output power. The Duty cycle on the Bias SMPS always shows 0%, even as the current jumps around in the red. I suspect I've managed to damage one (or more) of the surface mount semiconductors. At least that's what my reading on the subject would seem to suggest. What I need is a test that can be done with a multi-meter that would shed some light on the problem. I can probably resurrect an oscilloscope if I need it, but I'm hoping someone can lead me to a simple voltage or resistance test that could help isolate the problem. My last problem was related to soldering and enameled wire which was easily resolved. I'm hoping this issue can be resolved without major surgery as well. Thanks in advance for all of the good advice I'm about to receive. Andy WB9YXA

I have been trying to capture the digital signals driving the 2x16 LCD on my fully functional QMX transceiver. I am using an application called Scopy and the ADALM2000 learning module hardware from Analog Devices. I don't understand the captured data. I am hoping someone on this forum is familiar with this protocol and can provide some insight. My two main questions I have are: 1) Should the Enable line go high when the microprocessor of the radio is writing to the screen? From what I have captured so far these does not seem to be the case. However the reference material I read on line about typical 2x16 LCD screens indicates the Enable signal means write to the screen. 2) Should the Register Select (RS) line go high when the microprocessor is writing an ASCII character and low when it is writing a screen command? My data collection shows that there seems to be far more RS pulses than Enable pulses, which I don't understand. Am am attaching a screen shot of the data collected when I power up the QMX receiver with the factory reset splash screen. I have the Enable pin tied to input bit 0, the RS pin tied to input bit 1 and LCD data bit 0 through 7 tied to input pins 2-9 respectively. Any info on this would be greatly appreciated. Thanks in advance Mike (KC2EHR)

Hi, I've just completed construction of a QMX+ for 9V, with a good inspection for dry joints and solder bridges. Things seem fine on TX - power varies from 5+ watts on lower bands to about 2.5 watts on higher ones. However, on RX on Digital mode there are birdies at 700, 1400, 2100 and 2800Hz on all bands, with 12m showing others at 1000, 1500, 2000 and 3000Hz but at lower level. I have made a couple of QSOs on FT8, so it is working, but I'm sure these tones will cause problems with received tones at these frequencies. On CW mode though, there is a wide range of audio tone from about 600 to 750Hz with a spike at 700Hz. On 15m it is really loud (WSJT-X waterfall shows it as bright red). I can include screenshots of the WSJT-X waterfall for all bands on each mode if that helps. Any ideas where I might start to look to solve it? I see there are numerous threads here about different tones being manifested, but I haven't found anything similar to my situation. I don't have the skills or equipment to replace the PC1804 chip which seems a possible solution to some of the audio anomalies. TIA, 73, Kev G0AKH

hi, may i`m wrong with some qmx+ config, but sending cw from stored messages isn?t possible without loosing some characters, as like as "cq de df4bj" may ends in "ca de dfuba" or something else. Same behavior if sending from logging programm via cat. Did i don`t have correct configs or is that an known issue? I have installed the v1_01_003, updated from 1_00_027 on QMX+ Rev 3 , but going back to a non ssb fw doesn`t help. any suggestions ? vy 72/73 de Udo DF4BJ /qrp

Oh emm gee, I just ordered a QMX+ kit. Yay! I haven’t found a rundown on the specs for the current QMX/+. Does the new SSB firmware beta change anything for the sdr as a receiver? I am about 95% a listener, ham bands and not. I enjoy getting radiofax, so if anyone has done that please let me know how it does? Tnx es 73, Aunty Bee

The QCX was returned to me as "Not Working." I set it up on a 12vDC battery and dummy load. Then used a signal generator and found that the QCX was receiving a signal. Also, using another radio (FT-891) I transmitted and the 891 received the QCX signal. Next I put in on the osciliscope and found that the output was 1V peak to peak. At this point I checked Q1, Q2 and Q3. All were functioning properly. Here I began checking the IC's. The pins I did not list here are within specs. The ones listed were not. IC5 pin 5 (2.28) is actually showing 12v IC5 pin 8 (11.67) is 2.55 IC6 pin 3 (1.63) is 2.66 IC6 pin 5 (1.55) is 11.67 IC6 pin 8 (11.67) is 2.66 IC7 pin 3 1.99) is 2.60 IC7 pin 5 (1.89) is 11.67 IC7 pin 8 (11.67) is 2.66 IC8 pin 3 (0.65) is 2.57 IC8 pin 5 (0.65) is 2.57 IC8 pin 8 (11.67) is 2.60 IC9 pin 3 (0.65) is 4.49 IC9 pin 5 (0.67) is 11.67 IC9 pin 8 (11.67) is 2.56 IC10 pin 5 (4.21) is 11.67 IC10 pin 6 (3.94) is 5.94 IC10 pin 8 (11.67) is 5.90 This is as far as I got. Sorry for the 1st email. I have torn the bicep in my left arm and probably took too many pain killer before I emailed.. Hi Hi Your help will be most appreciated... Thank You Ron Pearson KA5HZV

The QCX was returned to me as "Not Working." I set it up on a 12vDC battery and dummy load. Then used a signal generator and found that the QCX was receiving a signal. Also, using another radio (FT-891) I transmitted and the 891 received the QCX signal. Next I put in on the osciliscope and found that the output was 1V peak to peak. At this point I checked Q1, Q2 and Q3. All were functioning properly. Here I began checking the IC's. The pins I did not list here are within specs. The ones listed were not. IC5 pin 5 (2.28 is actually showing 12v IC5 pin 8 11.67) is 2.55 IC6 pin 3 (1.63) is 2.66 IC6 pin 5 (1.55) is 11.67 IC6 pin 8 (11.67) is 2.66 IC7 pin 3 1.99) is 2.60 IC7 pin 5 (1.89) is 11.67 IC7 pin 8 (11.67) is 2.66 IC8 pin 3 (0.65) is 2.57 IC8 pin 5 (0.65) is 2.57 IC8 pin 8 (11.67) is 2.60 IC9 pin 3 (0.65) is 4.49 IC9 pin 5 (0.67) is 11.67 IC9 pin 8 (11.67) is 2.56 IC10 pin 5 (4.21) is 11.67 IC10 pin 6 (3.94) is 5.94 IC10 pin 8 (11.67) is 5.90 This is as far as I got. Sorry for the 1st email, Hans. I have torn the bicep in my left arm and probably took too many pain killer before I emailed.. Hi Hi Any help will be most appreciated... Thank You Ron Pearson KA5HZV

New QCX Mini (20m) build and everything seems to be working except for the screen will go blank and/or display a mix of /'s and ?'s after the initial boot screen. Boot screen always displays both lines of text and then roughly half the time I get the random mix of ?//? on just the top line or a single black character on the top right. The other half of the time the screen displays the frequency on the top line and I'll get a few button presses before it again falls back to the ?/???? junk. Pushing any of the buttons updates the line but never goes back to anything other than a single black box or the junk characters. I've inspected the board pretty closely, re soldered pretty much everything on the board at this point, and checked continuity between the screen and IC2 pins which all seems to check out. I've also checked the voltage on all the screen pins with a multimeter and while they aren't exactly what is in the build guide they seem to be within the expected operating range. That about hits the limit of what I know to do for troubleshooting, any advice would be more than welcome.

Gents, Just finished build of QMX+. Everything works perfectly from first power-up. Glad I watched Hans' video. The 6-layer board really does take a lot of heat to solder properly. Power is a little low - about 3W on most bands, compared to 4W from my QMX but that doesn't make much difference. One feature would be handy... I find that the QMX goes into SWR protection before my ATU10 has a chance to tune. I have to manually turn off protection when I want to tune a new antenna and/or band. How about when turning keyer speed to zero, in addition to going to straight key, set power to 50% and turn off SWR protection. 73, Glen W6GJB

Just finished my QMX+ and I have noticed 2 things: First the radio is deaf, I can here the standard background noise, but I can not hear any CW even though I am tuned to a frequency that I know has someone transmitting CW (I can hear them on my main radio.) Second issue ( I think they are related) is that as soon as I try to key up, the radio goes into safe mode. Everything else seems to be working good. Any thoughts on where to look or things to check. I do show an open between the center conductor of the BNC connector and ground. That is a far as I have gotten.

Hi all! I want to build a qmx with at least 40, 20, and 10m bands. This is not currently an official build and I was wondering if it is recommended or indorse by Hans. I know that it is possible and I am willing to give up other bands to have all three. Thanks!

Meanwhile having some QCX mini, now also own a QMX. Unfortunately I experienced a mysterious issue while keying CW that I don't know from the QCX. Every once in a while the QMX keyer omits a dit or a dah. At first I thought of a contact problem of my morse key (BaMaTech) but on my WinKeyer it worked flawlessly. I tried several speeds but even at low speeds this issue was present. After some futher experimenting with some alternative configurations and with other morse keys I think this is a problem of the QMX. I have firmware 1_00_027. Any ideas? 73 de Michael, DF9TZ

2.6 on my Win 10 machine receives great with new QMX Plus but can’t get it past a hamlib error. Tried it with QDX that worked fine some months ago and it does the same error. Tried to download but link to Princeton.edu is broke. Looks as though only site is SourceForge. That requires some registration and other manipulation. That safe place for download or is there other programs for FT-8? Think I still have WSJT-X on a Linux machine but I’m not so good Linux. Just an old guy who started life with tubes but love this new fangled stuff! 72/73 Jim w0nkn