开云体育

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_006 to it. As discussed in the other thread... I believe I fixed the problem with USB not working on Windows machines; I tested it on my PC with its out-of-date Win10 which I have not logged into for several YEARS. It worked on USB Serial Ports = 1 and USB Serial Ports = 2 (also with USB sound card appearing) but not on USB Serial Ports = 3. When I boot my PC into Linux as normal, all three options work perfectly. See attached. Feedback awaited... and again my apologies for the error in 1_01_005. Just a single character typo which apparently Linux didn't mind but Windows did :-/ 73 Hans G0UPL http://qrp-labs.com https://www.buymeacoffee.com/g0upl

I installed FT8CN to an Android phone but found it sometimes transmitted and often did not. Then I discovered there is a magic button on the screen which turns on transmission! It is in the top right of the Calling screen and looks like a loudspeaker. You need to click on this until it turns red as shown on the screen shot. I also discovered by repeatedly clicking this button it changes the "Sequential" setting between 0 and 1 which changes whether it transmits in the first or second time slot. I have read the English manual but don't remember seeing these controls. The settings are QDX rig selected which works with my QMX and CAT control. Everything else is default. Phone is a Google Pixel 9a.

My newest QMX+ kit Rev 3 arrived and was assembled exactly one week after ordering! The diagnostics test page showed output power (0W) and SWR (random values). Everything else was OK. All sweep tests showed strange results. Yes, the dummy load was in place. So I decided to power off and check all solder joints again. The QMX was on the table without the enclosure and I did not get a good grip on it. As I pressed the Vol button for power-off the QMX moved on the table and the long button press was interrupted, giving *two* long presses like keying Morse M. The display flashed abnormally showing some text and dimmed. All happened so quickly that I did not see exactly what happened. No smoke, no hot components. Now I can not power-on as the radio does not react to any button press. Nothing happens. If jumpered for forced firmware update, no flash drive appears on the PC. This could be a firmware problem. Is it possible that the second long press of the Vol button started the power-on cycle while still powering off and writing data to the flash memory? Clearly, while performing power-off and saving data into the flash memory, the firmware should ignore the button press for power-on. -- 73 Matti OH6BEX

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_005 to it. There are TWO changes only. Firstly, I have made many changes to the SSB Calibration (phase pre-distortion self-measurement). These improve the robustness of the calibration. I made changes both to the way the calibration itself runs, as well as searching different configurations of the radio while running the configuration. On my QMX+ here it now runs from 160m through to 6m and completes all successfully, with the very minor exception of 160m which only gets as far as DAC 2300, so *almost* there, just not quite and it won't matter. All others run all the way to the end (DAC 2600 or so, on a 12V supply). Additionally I applied a little Chaikin algorithm smoothing to the curves. You will notice some additional debug information printed on the screen on some bands on the terminal version of the calibration and the calibration will take slightly longer; this is the system trying to determine feasible calibration configurations on "difficult" bands. Secondly, I have added a configuration in the System Config screen (accessible on both the terminal and the LCD). This is a "list" selection so use the left/right arrows to select a value in the terminal, or the Tune rotary encoder to select a value when adjusting it on the LCD. The possible values are: USB Audio sound card and ONE serial port, as previous configurations USB Audio sound card plus TWO serial ports USB Audio sound card plus THREE serial ports and potential future USB Flash drive Only the third of these makes use of ghost USB endpoints. Note that I also discovered an error in the USB Hub Device Configuration Descriptor in the area of the potential future USB Flash drive. On my Linux system it just worked anyway, but it's possible different Operating Systems are more fussy. I am very curious to hear, particularly from people with Windows (even Win 7 Ludwig), what you experience for each of these configurations. Even if you already tried it on 1_01_004 please try again which each configuration in 1_01_005 as it will provide very useful information. They all work here, but my system is Linux. Feedback eagerly anticipated! 73 Hans G0UPL http://qrp-labs.com https://www.buymeacoffee.com/g0upl

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_004 to it. I did not solve problems with SSB phase distortion calibration, but I added a couple of additional failsafes. I am inclined to stop calling it beta. But I welcome your opinions on this. I know there is more to do, there will always be more to do... I think I would be more comfortable calling it the official version and moving onward. Having it all properly documented in the operating manual and all in one place would simplify things and reduce confusion. What do you think? These are the changes: Bug fix: Incorrect PA voltage display on the Diagnostics screen due to 57 / 10 being rounded to 5, as discussed in this forum. Change TX color in the diagnostics screen from red to blue, to avoid confusion since red things are errors. Added two more USB Virtual COM serial ports. QMX now presents itself as a USB hub with a 24-bit stereo 48ksps USB sound card and three USB Virtual COM serial ports attached. The advantage of this is that you can be running WSJT-X connected to a serial port, then run a terminal emulator connected to a different serial port; then you can make adjustments to the gain for example, to get the WSJT-X SNR meter at your desired level. You can also use other tools like "Input analysis" in the "PC and CAT" menu, which displays incoming audio tones from the PC; previously this could not be used unless you used VOX for Tx/Rx control. The CAT monitor can also be useful to be able to monitor incoming CAT commands and responses in realtime on one port, with CAT running on another. And going forward, for developers who wish to experiment with BASIC scripting, it will also be important to have multiple serial COM ports. Added CAT LC; command to retrieve LCD contents: it returns a 32-character string, whose contents are whatever is on the LCD at that instant. Any custom characters are replaced by spaces. The only exception to this is the VFO indicator which is replaced by an 'A' or 'B' character. Added CAT commands SA; which returns the AGC dB value (dB of attenuation applied by the AGC system). Added CAT command SM; which returns the S-meter value. This value is in dB. To convert to S-units, divide by 6. Added CAT command PC; which returns the power level during TX. The value is in tenths of a Watt. For example response PC45; would mean 4.5W. Added CAT command SW; which returns the SWR meter reading during TX. The value is in units of hundredths. For example response SW142; would mean the SWR measured is 1.42. Added CAT command SS to get/set SSB input source. Valid values are 0 (USB from PC), 1 (Two-tone test generator) or 2 (External microphone). I migrated AF, RF, Image, LPF and Test ADC I/Q terminal tools to the standard ASCII-art graphing tool I developed. Previously every tool had its own piece of code, which of course were copy-and-pasted from each other and largely similar. The advantage is also that the standard ASCII-art graphing tool I developed, also has an interface to display a miniature version of the graphs on a 20 x 16-pixel canvas, shown in a 4 x 2 character section at the right-hand side of the LCD. This means all these sweep tools are now also available on the LCD and buttons, without needing to use the terminal emulator to see them. They are all under the "Hardware tests" menu. I created a new tool called "PA mod. test" specifically to check the operation of amplitude modulator. This is under the "Hardware tests" menu both on the terminal interface and the LCD user interface. Attached is an example of a correctly functioning amplitude modulator. The x-axis shows the DAC value, the y-axis shows the measured PA voltage. A correct result is a straight line that goes (almost) from zero to (almost) the QMX supply voltage; a 12V unit will saturate at about a DAC value of around 2500 as shown. The Hardware tests / Diagnostics screen is now also available on the LCD interface. Here there are 6 screens, which you scroll between by using the Tune knob. You i

Hello, I tested the internal microphone in the menu microphone test. Nice. Now a question: once the beta firmware results in a release, what will be the way to transmit? All controls seem to have already a function and there seems to be nothing left for the PTT function. Jindra

Hi all, Yesterday, I finally found the time to finish building my second QMX (Rev.2, 10m - 20m). Initial setup was easy, and after loading the latest firmware, all tests ran smoothly. Today was its first use, which was also successful with a few FT8 QSOs. But after about 3 hours, the QMX said goodbye with a loud pop. C107 looked like the picture below: https://www.bitquell.de/nextcloud/index.php/s/cf9tbs844aW2mgq I can't identify a cause for this defect. The QMX is built for 9V and was powered by the stabilized 9V output of a TelentCell LF4100. The antenna was a precisely tuned vertical. Will replacing C107 be enough? I'm worried about Q107. Could the burn that can be seen in the picture have been caused by C107, or is Q107 also defective? 73, Joerg DG0JDE

Do any of the commercially available hand microphones for existing QRP radios work with the new QMX SSB? Or perhaps pre-wired adapters for those mics already in the marketplace? Bill W3WJ

I just upgraded to the 027 firmware on my QMX, from 018. Being able to select the CW filter is very nice, but I don't understand how to enable cascading or compounding of two CW filters. The manual says there are two CW filters - 300 and 500 Hz, yet the submenu shows 8 filters, ranging from 50 Hz to 500 Hz. Thanks and 73, Steve, N2IC

Hello! I am trying to find right settings to start work with WinLink and VARA HF threw QMX. CAT connection is OK. The only problem here is that when I choose some Gateway channel QMX always switches to USB mode from DiGi. But it is not a big deal to return back to DiGi manually. The main problem is that when I start connection with the chosen channel QMX shows two dots as TX status. Which means that audio level from PC is too low. But I've put it to maximum. And everything works fine with WSJT-X and JS8Call. So problem is definitely with some WinLink VARA HF settings? Can smb help? Hans, did you try to use WinLink with QMX?

My QMX is working perfect with 12V, but I would like to try 9V to reduce power on FT8. By lowering voltage with a regulated power supply, qmx is going off at <10V (qmx seems not to be completely off, but there is no audio and no display). By increasing voltage again, QMX is starting again at >10V (without pressing "On/Off knob). At exactly 10V QMX is alternately going on and off. The minimal voltage in protection settings is 7V, why isn't it working with 9V? Vy 73 and thanks in advance, Stojan, DK4SR