Macbook Terminal Program - How to go back in QMX+ Terminal Menu
I have been able to successfully connect to my QMX+ using the native terminal program in Mac OS Sonoma. ?However, after selecting a sub menu item, I cannot go back to the main menu. ?I've tried CTRL-Q but nothing happens. ?My only option is to use Command-Q to log out completely and then log back in to the main menu. ?Do any of you Mac users know how to return to the previous menu item using the Mac terminal program?
?
Thanks,
Bill K4GDR
|
Re: #QMX Rev4 v27, kit just built not working
#qmx
Have you run the suite of diagnostics test available in a Terminal session??
?
Greg
|
Re: #QMX Loaded FW 27, Now Dead?
#qmx
One thing that's been troubling me is the ADC voltages are much lower than I expect. From the schematics they both look to be simple voltage dividers, with the ADC voltage being half of VCC and VDD. But when I measure those voltages they're quite a bit lower.
?
I suspected my original 5v SMPS board was missing half of the voltage divider, so I tacked a resistor on with no success. So I got a new SMPS and it's still behaving the same. I'm going from memory but I want to say both ADC lines are in the 240mv range. That seems very wrong, but with the 3.3v "working" I just figured there must be more to that circuit than the schematic shows.
?
I'll have to get my hands on a better power supply to test the SMPSs. I have the original set and a spare set a friend lent me. So far I've only replaced the 5v board since the other seemed to be producing 3.3v.
?
In the meantime, any thoughts on the ADC voltages? Should those be 2.5v and 1.65v respectively?
?
-Todd
|
Hans,
?
Thanks for the update on SSB!
?
Regarding having speech to test with, there are publicly available corpora for training neural networks with thousands of hours of speech.? Here is a pointer:
?
?
There are also corpora with noisy speech.
And there are corpora with many types of noise (to be mixed with the speech recorded in quiet conditions to simulate various conditions).
?
FYI.
?
--Mike
?
|
Many thanks for the detailed update Hans!
?
The use of one of Winston's speeches seems quite appropriate. If you're looking for something more "real world" you could consider one of his speeches from Question Period in the House of Commons! Perhaps one of the many where he effortlessly slices and dices members of the opposition!
?
Again, thanks for the update and, hopefully, things will continue to progress as planned!
--
73, Rick VE7TK
Website:
|
Re: Is there documented process to fully test QMX+ ?
Sam, the QMX+ is comprised of many subsystems.? You need to be a bit more explicit in describing the situation you are currently in post build difficulties.
73
K8FC
toggle quoted message
Show quoted text
We finished our build of the QMX+.? Still having issues.?
?
Is there documented process that goes beyond the assembly
and operations manual to fully test and troubleshoot the QMX+ ?
?
Thank you
Sam
?
?
|
Is there documented process to fully test QMX+ ?
We finished our build of the QMX+.? Still having issues.?
?
Is there documented process that goes beyond the assembly and operations manual to fully test and troubleshoot the QMX+ ?
?
Thank you
Sam
?
?
|
Re: #QMX Rev4 v27, kit just built not working
#qmx
Okay - I have the QMX transmitting now! I think there was a function set to disable the transmitter. (by default ????) but I toggled that setting in the terminal mode and now it transmits!! Fairly decently at that. The Diagnostic Test shows good current power and SWR on a dummy load. I consider that a win.
?
Next obstacle: receive audio. I still don't have any. Anybody have a clue why I can't turn it up? I looked around in the terminal mode for anything that could give a clue why the RX audio could be turn off....
?
Anybody have any ideas on how to turn on the volume control or turn it up? Yes, the encoder is working fine..
?
Thanks,
Myron WV0H
|
On Sat, Sep 28, 2024 at 03:23 PM, Cal (AD8Q) wrote:
The folded doubled wire section gets tugged back on either side of the hole a little during the adjustments.
?
?
Just to be clear about the general technique I used, perhaps this sentence is better: The slightly slack, folded and doubled wire section gets tugged a little, as needed, towards either side of the hole during adjustments. One section of turns tends to expand while the adjacent section tends to compress. ?
dit dit
|
Glad to help, Greg! w0wly helped me tremendously and I'm just passing-on the information and techniques I've learned and my results. Everyone's mileage can vary (due to BPF capacitor differences, if nothing else), but duplicating the windings and spacing in my final L401 photo might be a good starting place for anyone winding a 19t/28t/28t(END) inductor, per the Rev. 1 instructions and Hans' "52 Tips" video. In any case, the technique I used to cancel the adjustment I made to the first tap inductance by adjusting the inductance after the first tap in the opposite direction is probably applicable in many circumstances, including inductors featuring several taps.
?
It dawned on me that such an adjustment is facilitated by having a little extra slack in the folded, doubled wire section that is soldered into the tap hole on the PCB. As once section is squeezed, the adjacent section can be expanded. The folded doubled wire section gets tugged back on either side of the hole a little during the adjustments.
?
I took another look at my graphic. I think it's all correct. Please let me know if you find any discrepancies. I need to get back outside again and clear a bunch of blow-down debris from a huge windstorm we had a couple of days ago here in the Clearwater River Valley of N. Central Idaho. Having watched a few Helene videos from Florida, I don't feel sorry for myself at all!
?
73,
Cal -- AD8Q
|
Chuck AI7SY, an old supervisor and mentor once told me, "The job will get done when it wants to get done."? We had more than one similar situation.? A serious problem had to be rapidly overcome.? The program manager decided to have a daily "SITREP".? For those not familiar, a SITREP is something used in the military for a situation report of the current military situation.? I guess if management gave the daily reports a military connotation, it gave them a feeling of better control since it's analogous to a military operation.? ?Adding more manpower to the job was sometimes attempted but only would help if the personnel were highly skilled and somewhat knowledgeable with the problem domain.? If they were taken from a pool of whoever was most available at the time rather than highly skilled for application to the problem at hand, it wouldn't work because training and coordination time would exceed productive working time.? In the software world, this is known as Brooks' Law (adding more people to a software project can make it later). Hans, With regard to SSB Status, bravo to you on including CESSB if you can pull it off.? This would result in?an effective average power increase of about 140%!??
With regard to QSX futures, I would consider the QMX+ features and the following new features mandatory: 1. A spectrum scope.? Touchscreen not required. 2. Additional control buttons for ease of operation.
3. 10 watt minimum output power at 100% duty cycle with adjustable output power level. This is a hard nut to crack with the same architecture in the output stage. 3. An absolutely bulletproof switching power supply, totally independent of the main processor except for status monitoring and capable of wide input voltage range which includes 13.8 volts.? Power supply must put out +5V, +3.3V, and output stage voltages with power sequencing as necessary.? Protections TBD.
Nice to haves but not mandatory: 1. An optional built-in antenna tuner with a "quick tune" feature by measuring the antenna's impedance and computing the required matching L and C values. at least 3:1 VSWR matching capable.? 2. An optional built-in battery
toggle quoted message
Show quoted text
------ Original Message ------
Date 9/28/2024 4:35:36 PM
Subject Re: [QRPLabs] #qmx SSB Update
Thanks Hans. I thought you might be taking the CESSB road.
?
Lest people here get too curious as to SSB status, here's a cautionary tale:
?
I worked at a meduim sized company that was building a BabelBox; i.e., a server that would route any physical network available to any other (depending on the server's hardware) and we were about 60 days out from a hard ship date to Air France, and in testing.
?
Management (inexperienced) panicked and instituted a daily status meeting for all developers, at 8 AM no less. This was so the project managers could submit a daily report to the executives.
?
That slipped the project another 90 days.
?
TL;DR Moral: Be careful what you ask for, and also how often you ask for it.
|
Re: #QMX Rev4 v27, kit just built not working
#qmx
Myron,
for TX the QMX could draw up to 1 A or a bit more. Could it be your power supply drops the voltage in this case for a very short time? This brown out may affect the controller to go to an undefined status. The display may hold the old characters but the firmware doesn't work completely from here on. Of course with the display backlight is on VCC must be available and this means the controller must send PWM to the SMPS.
Is the backlight on in the usual brightness when the QMX is frozen? Could you check the value of VCC in this state?
?
73 Ludwig
|
Fascinating and ?enlightening Hans. ?Thank You!
It seems to me that increased output power with the QMX may require a different output stage, fed the carrier phase info and a beefed up amplitude modulator. ?Perhaps there could be two pick off points that the QMX+ builder could access to attach the optional Big Output accessory, and still fit into the QMX+ case.?
toggle quoted message
Show quoted text
On Sep 28, 2024, at 15:13, Hans Summers via groups.io <hans.summers@...> wrote:
? Hi Chris, Stefan, all > If I recall correctly Hans has shelved the QSX
No, I've never said that. To be sure, literally speaking, it has spent some time sitting on my shelf; but in the more commonly understood meaning, it has not been shelved as in retired, given up on, etc. Just that I suspended work on it while I have generated lots of other interesting designs in the meantime, until I get back to it and finish it. But more on this below.??
> Are you able to give us an update. > Your last update was very welcome.
Sure. Well, I had a somewhat disappointing week in which I had to spend most of the days on some very urgent SteppIR work, on which I made a lot progress and it's almost completed, but nonetheless it consumed most of the time. Which I don't regret because I love the guys at SteppIR, they're a great bunch of people and a great company with very fine products; and also because I have always found that if I follow my passion and don't question my gut feel too much, it has a strong tendency to lead somewhere interesting. In this case perhaps things I learn along the way are going to be very useful applied back into QRP Labs transceivers, so it all becomes worthwhile in the end with hindsight, even if in present day we can't foresee the future.?
Interleaved between that, I did make some progress on the QMX SSB firmware. I had concluded that the SSB modulation is about as good as I can make it - which is very good indeed with intermodulation performance that exceeds several?respected commercial transceivers costing 20x the price.
I was reminded more than once of an event at school when I was around 15, in the "Technology" class. We were paired to do a major end-of-course (2 year course) project. My friend and I had decided to make a pneumatic robot arm but that turned out to be hopelessly over-ambitious (and perhaps an indicator of? future tendencies); we made nearly no progress, certainly not enough to suggest success within the limited timescales. In the end 3 weeks before the deadline, we abandoned it, changed course and made a burglar alarm system instead with various detectors like ultrasonic movement detector, infra-red beam, magnet reed switch, pressure mat, etc. We did OK on that, even with the very little time available.? Anyway that's a digression from the digression. The real story is the chap who, unpaired (doing his project alone) had decided he should build a radio-controlled duck out of balsa wood. Then he would plan to sail this duck on a pond where there were other (real) ducks, and thought the other ducks would follow his fake duck and not notice it was fake, then he could lure them closer and take a nice photograph of the ducks. Such was his plan. I recall not really paying much attention to his plan for the balsa wood duck but it all went wrong one day, when cutting balsa wood with an extremely sharp industrial strength box cutter-style knife. A small slip and the blade half chopped off his thumb. It cut down at least an inch and a half between thumb and forefinger. He didn't yell or scream, just stood and stared at it, frozen with a perplexed look on his face. His predicament was quickly noticed by the teacher, who was actually the head of the physics dept and a good friend of mine (I ended up doing physics at uni); anyway he was a very practical and calm fellow and did not panic at the situation. He just grabbed the kid's arm and held it up high, to reduce blood pumping that way; then he tried to squeeze the wound together, and started making plans to attend hospital which fortuitously was only about a 5 minute drive from our school. Which comes to the point. As he squeezed the two pieces of hand together, bits of flesh, blood, bones, tendons, muscles and whatever else is inside hands, sort of came out the other side. So he would then squeeze that other side but then bits of innards came out this side. And no matter where he squeezed, the poor kid's insides seemed to ooze out one place or another. And in the end there wasn't much point trying any further, so off they went to the hospital to get repairs done properly (which did take some time). And this is why it reminds me so much, on many occasions, in other areas. Specifically in this situation, here I was with my? 700 / 1900 Hz two-tone test signal, trying to reduce IMD product spurs. Some things reduce IMD3 but worsen IMD5, 7, 9. Some the other way around. Sometimes it's possible to improve what happens above the twin peaks at the expense of what goes on below, and vice versa. Squeeze somewhere, and elsewhere things go wrong.?
So eventually like the venerable Mr Plougman, head of physics dept, it became time to shrug my shoulders, accept I made SSB as good as I can right now, which is actually very good and way better than expected, and move on to the next phase.?
I spent some time researching compression techniques and ALC, AGC, and then CESSB. Because all the questions now center around how to connect up the microphone samples to the SSB transmitter and get the best results.?
So currently I am working on CESSB (Controlled Envelope Single Sideband). The best reference to learn more about CESSB is the original ARRL QEX article published in November 2014 by?David L. Hershberger, W9GR .? See also:?
CESSB is a technique to prevent overshoot (clipping and splatter in the PA) and increase average power by several dB relative to peak envelope power. It is implemented in a rather small number of transceivers currently limited (as far as I know) to SmartSDR software by Flex Radio Systems, Apache labs ANAN series and the Elecraft K4.
Now before a subset of you rapidly start angrily typing a reply along the lines of, why are you bothering with CESSB before you have even released SSB? There?is method to my madness.
One has to do *something* to establish the appropriate gain for the transmit chain from microphone to antenna. I do not feel that just having a manual gain setting and relying on the operator to speak in level tones at a fixed distance from the microphone, is really going to be a sufficiently "good" system. And since 5W of SSB is not exactly gigantic, it doesn't have the relative SNR advantages of narrow bandwidth modes like CW and many digi modes; so SSB needs all the help it can get. The key aim is to increase the average power level relative to the peaks, without causing clipping and splatter. There are several things that can take place in an SSB transceiver: - Some kind of automatic gain control which is similar to what's done on receive
- Actual compression, in which quieter speech is amplified by a larger amount than loud parts of the speech
- ALC -? Automatic Level Control in which the PA itself acts to limit the amplitude to prevent clipping; in the case a quite sophisticated delay-line look-ahead system could be used.?
CESSB replaces the need for ALC and increases average power. Inevitably ALC will REDUCE the gain to an extent that SSB peaks don't cause clipping; effectively it increases dynamic range not decreases it so arguably it's the opposite of the compression we want.?
Furthermore the unusual Envelope Elimination Restoration -like way in which SSB is being generated in QMX already sees the SSB signal split into separately modulated phase and amplitude components; we are therefore already at the point of messing with the RF envelope level so it actually makes CESSB several steps closers already. Because of this it may end up being the EASIEST way to achieve my SSB goals.?
For all these reasons it makes sense to consider CESSB at this stage, as long as it does not cause an unreasonably long delay in development.?
Current status: I wanted a speech sample to use for testing. Googling, it appeared surprisingly difficult to find a simple speech sample; there's lots of music, lots of things illustrating different compression levels and distortion effects; but little in the way of just some plain speech. The first plain thing I happened to come across was Winston Churchill's "Be Ye Men of Valour" speech from 1940
This is a 10+ minute speech which means I don't have to restart it too often. It doesn't suffer background noise or music and appears to be a clean recording. To start with, I opened it in Audacity (PC audio software). It's sampled at 11025 samples/second and isn't "full volume" in so far as it does not touch -1 /?+1 levels (full-scale). See attached "Winston Orignal.jpeg".?
I still haven't listened to the whole speech by the way. I just wanted some recording of someone talking and it was the first I found.?
Next I re-sampled it to 48ksps sample rate; I know the PC will automatically do this for me when I play the sample to the QMX (USB sound card) but I felt happier if I knew I already had it in the required format under my control. I always try to reduce the number of unknown variables wherever possible. I then used Audacity's Amplify function which automatically tells you the amount of amplification to apply to bring it up to full-scale; such that the highest and lowest peaks of the entire recording are exactly at (but do not exceed) the?+/- 1.0 level (fullscale). I then added a 2 second 1kHz full amplitude sinewave to use as a reference tone, at the start of the recording, before Churchill embarked on his waffleology. This is shown in the attached file "Resampled and 2 seconds 1kHz.jpeg".
Now I could play this sample into QMX. Of course I now had to connect up the USB sound card in QMX, to the SSB modulator which until now, has been busy only on synthesized 700 / 1900 Hz two-tone signals and other such things. Firstly to convince myself the audio was coming correctly into QMX I routed it to the audio output directly; at this point I could listen to Churchill in my QMX earphones (and understand the significance of the large overweight overpriced USB headphone dongle thing on my bench). Now I did some DSP for a factor of 4 decimation down to the 12ksps sample rate used for the transmit processing. Bear in mind that the fastest the '5351 synth can be updated is 16ksps. The faster you go, the more accurate the amplitude and phase modulation is (smaller steps) but the slower the filters and DSP are for the equivalent same shape factor of the filters etc. So a compromise has to be chosen.?
I set the gain such that my 1kHz test tone at the start produces 0.6W PEP. I'm far below the 4-5W I can get on 40m. So I could now see any overshoots beyond "full power" 0.6W PEP, without them actually driving the amplifier?to a clipped state.?
Interesting results... the attached "scope1.jpeg" shows the first 9 seconds, the 2kHz tone is at "full power" and I set the dotted horizontal blue line cursors of the 'scope to be able to clearly see any overshoots. You can see the RF envelope shown on the 'scope trace closely resembles that of the Audacity software PC audio clip in attached image "Resampled and 2 seconds 1kHz.jpeg". But - crucially -? you can also see the overshoots! They are more visible too on a long clip, attached "scope2.jpeg" shows nearly 3 minutes of Winston. You can see that the blue cursors are at 15.6Vpp (0.6W PEP). But the peaks extend to 19.01Vpp. So the overshoots are 22% beyond the "PEP" level. That means ALC would have to apply a gain factor of 0.82 to this clip to prevent any clipping of the RF envelope. Which would reduce the average power of the transmission, decreasing the SNR at the receiving end. Reducing the power of your watts PEP...?
This is all exactly what is talked about in the CESSB article; but it's important to be able to demonstrate it because now when I put in some CESSB code I should be able to quantify the improvement. To re-iterate - the SSB modulation process, no matter whether it is done digitally or by purely analog techniques (whether phasing or superhet with crystal filter), inherently it causes overshoot (clipping) necessitating reduction in PA gain to avoid clipping that causes splatter. Even with a completely perfect input signal, such as Churchill's speech, which has no clipping at all, it still occurs at RF. Clipping at baseband audio and clipping of the SSB envelope are NOT the same thing! And this is what CESSB is aiming to improve.?
Note that I also measured the spectrum - transmitting Churchill at 0.6W PEP on 7030 kHz into my dummy load, 26dB of attenuation to the spectrum analyzer; the attached "Spectrum.jpeg" shows the result, 20kHz span (2kHz / horizontal division). The video bandwidth setting is 1Hz, resulting in a slow 140 second sweep time so the spectrum indicates average power not peaks.?
I could also zoom in on the end of the 1kHz 2 seconds tone burst at the beginning of the audio sample. You can see that even though at audio, there is no clipping (overshoot), at RF the envelope exhibits an unwanted bulge at the end which in a PA at full power, would result in clipping and splatter.?
Next as an experiment I amplified Churchill by 3dB in Audacity; which is a very crude form of compression because now his peaks which were close to full scale, get clipped. Still, nothing at the audio input exceeds full scale (+/- 1.0) though now the higher frequency components will be emphasized because the clipping instances are getting like a squarewave at their edges. Now the attached "ScopeCompressed.jpeg" shows the overshoot situation got a lot worse, it is now 58%. The spectrum - attached file "SpectrumCompressed.jpeg" is still as expected, OK, because the "overshoot" is not really overdriving the amplifier because the gain was set so low, for only 0.6W PEP so that I could observe the overshoots. The average level is seen rk be higher, as expected.?
All of this is exactly what the QEX CESSB article talks about; so there's nothing unexpected here; but it's very nice to be able to see it and "feel it" and have a baseline to compare against when I put in improvements.?
> Yes, I would also be interested in an update. > Will there actually be a difference between a? > QMX with SSB and a QSX?
That's a very interesting question. I had previously expected that the transmit performance on SSB for QMX would not be as good as SSB generated conventionally by a quadrature sampling exciter and linear driver/PA chain. This would mean QSX still had value though undoubtedly the gap would be narrow and perhaps indicate an upgrade in QSX spec would be desirable.?
However now it seems that QMX SSB performance will exceed what was possible with QSX. Which is a very interesting concept to put it mildly (actually I find it mind-blowing). So what then IS the remaining point of QSX as it was originally planned? Almost all originally planned QSX features will have been delivered by a 160-6m QMX+. A remaining difference is that QSX has 10W output compared to 3-6W on a QMX+.?
So it's an existential question I spend a lot of my thinking about. A lot of thinking on long drives, lying in bed hot summer nights insomniac-style, and other such occasions when it is not wasteful to spend thought: not saying I stare at the lab ceiling for hours when I should be hammering out a thousand emails, help desk tickets or lined of C code for QMX SSB.?
I suspect in the end the answer will probably be, that QMX+ does indeed cover almost all of what QSX intended. So as often mentioned here and everywhere, though QSX was a lot slower than originally expected, and many other projects and products occurred in the interim, seemingly to some commentators as unwelcome interruptions, most of these actually became stepping stones towards QSX. And now we may have accidentally taken one stepping stone too far and achieved QSX before its time and name, in the form of QMX+. Apart from that 3dB output power, it's almost all in there, and more.
All of that still doesn't mean QSX has been or should be abandoned. It's not necessary to step down with any degree or sorrow, regret or remorse. On the contrary, QSX having been substantially delivered via QMX+, relieves the demand and pressure for launch of QSX. Which allows the imagination to run wild and free with a much more ambitious product. Which could be quietly developed to a much higher specification, to provide a more substantial differentiation to QMX+.?
Some may have heard me talk of 7 radios. 7 plans. Which isn't because the Harry Potter novels are 7 in number. And doesn't limit me to developing no more after that 7. Just that in my own head having gradually formulated a multi year technical and business plan, I had conceived 7 transceivers. 5 you have. QCX+, QCX-mini, QDX, QMX and QMX+. The shape and form of the remaining two, which may or may not materialize unexpectedly in the coming year or two, is imperfectly defined and in a constant state of change. One was to be QSX; but now given the success with QMX+, I started to dare dream that the QSX plan can evolve more into a super QSX.?
Executive summary: exciting times and I ain't done yet!
73 Hans G0UPL
On Sat, Sep 28, 2024 at 3:50?PM Chris KB1NLW via <chrisrey1= [email protected]> wrote: Hans:
Are you able to give us an update.
Your last update was very welcome.
?
Thanks?
Chris
<Winston Original.jpeg> <Resampled and 2 seconds 1kHz.jpeg> <Scope1.jpeg> <Scope2.jpeg> <Spectrum.jpeg> <1kHz Audacity.jpeg> <SpectrumCompressed.jpeg> <1kHz Scope.jpeg> <ScopeCompressed.jpeg>
|
Re: QMX+ Base legs (Bales) from Misumi
#qmx
?
Got the smaller legs from Amazon for the QMX!
--
73 Karl KI4ZUQ
|
Re: #QMX Loaded FW 27, Now Dead?
#qmx
Todd, in the moment its hard to imagine what happens. For both VDD and VCC the Duty cycle is at or above the Limit Duty max. That's wrong. Its weird both SMPS are with the same problem. I would test both sub PCB off line (see QMX QMX_Plus Power supply test Process).
?
If the SMPS boards are ok you may go a second step. To have consistent data produce a screen shot from diagnostics and check in the same state all voltages at the two pin header of the SMPS. If an oscilloscope is available check PWM_3V3 and PWM_5V for duty cycle and voltage min / max and also ADC_3V3, ADC_5V, VCC and VDD for ripple.
?
73 Ludwig
|
Thank you again Cal. Beautiful work.? The angle comparison is especially well done.? You obviously have good assembly skills.
Now off to save this message and the photos.?
toggle quoted message
Show quoted text
On Sat, Sep 28, 2024 at 4:19 PM, Cal (AD8Q) via groups.io <cbrabandt@...> wrote: I'm very pleased that you made this request, Greg, because it motivated me to re-assess my changes using before and after photographs and the changes I made to L401 were very subtle in the end. It turns out that BPF peak positions are far more sensitive to L401 windings spacing than RF output power is to corrections made in L511, L512, and L513!
?
As I mentioned in my last post, I "over-squeezed" the spacing between L401 turn 1 and turn 19 on my initial squeeze and then attempted to reduce that squeeze and mitigate its impact on the bands below 30m by opening up the spacing between turn 19 and turn 28.
?
In this morning's investigation, I used the photo that I posted below (post ? #130394) as my L401 "before tuning" photo. I had already squeezed L511, L512, and L513 to nearly their final settings to increase my my RF output power but I had not touched L401 yet.
?
I just opened-up the sandwich to take the attached "after" board photo. To make the subtle changes more apparent (extremely apparent), I also created an L401-only comparison graphic. The left side of the graphic is the original L401 (blurry side...sorry) and the right side illustrates the state of my final L401.? Pay attention to the angle subtended by the "squeeze" and "expand" sections of the windings. The GIMP too makes this easy!
?
The "squeeze" section (yellow) originally subtended about 222 degrees. It now subtends only 198 degrees.
The "expand"? section (blue) originally subtended about 114 degrees. It now subtends about 150 degrees.
?
I drafted the comparo graphic rather hastily. I hope it doesn't contain errors but I'll check it tonight. Even so, you and others will get the idea.
?
73,
Cal -- AD8Q
?
On Fri, Sep 27, 2024 at 04:09 PM, Greg McCain wrote:
<snip>
?
Please do post the picture. It needs to be in the WIKI section too. I plan to save it in my personal QMX golden knowledge files store too.
?
73 GREG KI4NVX?
|
Bravo, Hans!
73,
Randy, KS4L
toggle quoted message
Show quoted text
On Sat, Sep 28, 2024, 2:13?PM Hans Summers via <hans.summers= [email protected]> wrote: Hi Chris, Stefan, all > If I recall correctly Hans has shelved the QSX
No, I've never said that. To be sure, literally speaking, it has spent some time sitting on my shelf; but in the more commonly understood meaning, it has not been shelved as in retired, given up on, etc. Just that I suspended work on it while I have generated lots of other interesting designs in the meantime, until I get back to it and finish it. But more on this below.??
> Are you able to give us an update. > Your last update was very welcome.
Sure. Well, I had a somewhat disappointing week in which I had to spend most of the days on some very urgent SteppIR work, on which I made a lot progress and it's almost completed, but nonetheless it consumed most of the time. Which I don't regret because I love the guys at SteppIR, they're a great bunch of people and a great company with very fine products; and also because I have always found that if I follow my passion and don't question my gut feel too much, it has a strong tendency to lead somewhere interesting. In this case perhaps things I learn along the way are going to be very useful applied back into QRP Labs transceivers, so it all becomes worthwhile in the end with hindsight, even if in present day we can't foresee the future.?
Interleaved between that, I did make some progress on the QMX SSB firmware. I had concluded that the SSB modulation is about as good as I can make it - which is very good indeed with intermodulation performance that exceeds several?respected commercial transceivers costing 20x the price.
I was reminded more than once of an event at school when I was around 15, in the "Technology" class. We were paired to do a major end-of-course (2 year course) project. My friend and I had decided to make a pneumatic robot arm but that turned out to be hopelessly over-ambitious (and perhaps an indicator of? future tendencies); we made nearly no progress, certainly not enough to suggest success within the limited timescales. In the end 3 weeks before the deadline, we abandoned it, changed course and made a burglar alarm system instead with various detectors like ultrasonic movement detector, infra-red beam, magnet reed switch, pressure mat, etc. We did OK on that, even with the very little time available.? Anyway that's a digression from the digression. The real story is the chap who, unpaired (doing his project alone) had decided he should build a radio-controlled duck out of balsa wood. Then he would plan to sail this duck on a pond where there were other (real) ducks, and thought the other ducks would follow his fake duck and not notice it was fake, then he could lure them closer and take a nice photograph of the ducks. Such was his plan. I recall not really paying much attention to his plan for the balsa wood duck but it all went wrong one day, when cutting balsa wood with an extremely sharp industrial strength box cutter-style knife. A small slip and the blade half chopped off his thumb. It cut down at least an inch and a half between thumb and forefinger. He didn't yell or scream, just stood and stared at it, frozen with a perplexed look on his face. His predicament was quickly noticed by the teacher, who was actually the head of the physics dept and a good friend of mine (I ended up doing physics at uni); anyway he was a very practical and calm fellow and did not panic at the situation. He just grabbed the kid's arm and held it up high, to reduce blood pumping that way; then he tried to squeeze the wound together, and started making plans to attend hospital which fortuitously was only about a 5 minute drive from our school. Which comes to the point. As he squeezed the two pieces of hand together, bits of flesh, blood, bones, tendons, muscles and whatever else is inside hands, sort of came out the other side. So he would then squeeze that other side but then bits of innards came out this side. And no matter where he squeezed, the poor kid's insides seemed to ooze out one place or another. And in the end there wasn't much point trying any further, so off they went to the hospital to get repairs done properly (which did take some time). And this is why it reminds me so much, on many occasions, in other areas. Specifically in this situation, here I was with my? 700 / 1900 Hz two-tone test signal, trying to reduce IMD product spurs. Some things reduce IMD3 but worsen IMD5, 7, 9. Some the other way around. Sometimes it's possible to improve what happens above the twin peaks at the expense of what goes on below, and vice versa. Squeeze somewhere, and elsewhere things go wrong.?
So eventually like the venerable Mr Plougman, head of physics dept, it became time to shrug my shoulders, accept I made SSB as good as I can right now, which is actually very good and way better than expected, and move on to the next phase.?
I spent some time researching compression techniques and ALC, AGC, and then CESSB. Because all the questions now center around how to connect up the microphone samples to the SSB transmitter and get the best results.?
So currently I am working on CESSB (Controlled Envelope Single Sideband). The best reference to learn more about CESSB is the original ARRL QEX article published in November 2014 by?David L. Hershberger, W9GR .? See also:?
CESSB is a technique to prevent overshoot (clipping and splatter in the PA) and increase average power by several dB relative to peak envelope power. It is implemented in a rather small number of transceivers currently limited (as far as I know) to SmartSDR software by Flex Radio Systems, Apache labs ANAN series and the Elecraft K4.
Now before a subset of you rapidly start angrily typing a reply along the lines of, why are you bothering with CESSB before you have even released SSB? There?is method to my madness.
One has to do *something* to establish the appropriate gain for the transmit chain from microphone to antenna. I do not feel that just having a manual gain setting and relying on the operator to speak in level tones at a fixed distance from the microphone, is really going to be a sufficiently "good" system. And since 5W of SSB is not exactly gigantic, it doesn't have the relative SNR advantages of narrow bandwidth modes like CW and many digi modes; so SSB needs all the help it can get. The key aim is to increase the average power level relative to the peaks, without causing clipping and splatter. There are several things that can take place in an SSB transceiver: - Some kind of automatic gain control which is similar to what's done on receive
- Actual compression, in which quieter speech is amplified by a larger amount than loud parts of the speech
- ALC -? Automatic Level Control in which the PA itself acts to limit the amplitude to prevent clipping; in the case a quite sophisticated delay-line look-ahead system could be used.?
CESSB replaces the need for ALC and increases average power. Inevitably ALC will REDUCE the gain to an extent that SSB peaks don't cause clipping; effectively it increases dynamic range not decreases it so arguably it's the opposite of the compression we want.?
Furthermore the unusual Envelope Elimination Restoration -like way in which SSB is being generated in QMX already sees the SSB signal split into separately modulated phase and amplitude components; we are therefore already at the point of messing with the RF envelope level so it actually makes CESSB several steps closers already. Because of this it may end up being the EASIEST way to achieve my SSB goals.?
For all these reasons it makes sense to consider CESSB at this stage, as long as it does not cause an unreasonably long delay in development.?
Current status: I wanted a speech sample to use for testing. Googling, it appeared surprisingly difficult to find a simple speech sample; there's lots of music, lots of things illustrating different compression levels and distortion effects; but little in the way of just some plain speech. The first plain thing I happened to come across was Winston Churchill's "Be Ye Men of Valour" speech from 1940
This is a 10+ minute speech which means I don't have to restart it too often. It doesn't suffer background noise or music and appears to be a clean recording. To start with, I opened it in Audacity (PC audio software). It's sampled at 11025 samples/second and isn't "full volume" in so far as it does not touch -1 /?+1 levels (full-scale). See attached "Winston Orignal.jpeg".?
I still haven't listened to the whole speech by the way. I just wanted some recording of someone talking and it was the first I found.?
Next I re-sampled it to 48ksps sample rate; I know the PC will automatically do this for me when I play the sample to the QMX (USB sound card) but I felt happier if I knew I already had it in the required format under my control. I always try to reduce the number of unknown variables wherever possible. I then used Audacity's Amplify function which automatically tells you the amount of amplification to apply to bring it up to full-scale; such that the highest and lowest peaks of the entire recording are exactly at (but do not exceed) the?+/- 1.0 level (fullscale). I then added a 2 second 1kHz full amplitude sinewave to use as a reference tone, at the start of the recording, before Churchill embarked on his waffleology. This is shown in the attached file "Resampled and 2 seconds 1kHz.jpeg".
Now I could play this sample into QMX. Of course I now had to connect up the USB sound card in QMX, to the SSB modulator which until now, has been busy only on synthesized 700 / 1900 Hz two-tone signals and other such things. Firstly to convince myself the audio was coming correctly into QMX I routed it to the audio output directly; at this point I could listen to Churchill in my QMX earphones (and understand the significance of the large overweight overpriced USB headphone dongle thing on my bench). Now I did some DSP for a factor of 4 decimation down to the 12ksps sample rate used for the transmit processing. Bear in mind that the fastest the '5351 synth can be updated is 16ksps. The faster you go, the more accurate the amplitude and phase modulation is (smaller steps) but the slower the filters and DSP are for the equivalent same shape factor of the filters etc. So a compromise has to be chosen.?
I set the gain such that my 1kHz test tone at the start produces 0.6W PEP. I'm far below the 4-5W I can get on 40m. So I could now see any overshoots beyond "full power" 0.6W PEP, without them actually driving the amplifier?to a clipped state.?
Interesting results... the attached "scope1.jpeg" shows the first 9 seconds, the 2kHz tone is at "full power" and I set the dotted horizontal blue line cursors of the 'scope to be able to clearly see any overshoots. You can see the RF envelope shown on the 'scope trace closely resembles that of the Audacity software PC audio clip in attached image "Resampled and 2 seconds 1kHz.jpeg". But - crucially -? you can also see the overshoots! They are more visible too on a long clip, attached "scope2.jpeg" shows nearly 3 minutes of Winston. You can see that the blue cursors are at 15.6Vpp (0.6W PEP). But the peaks extend to 19.01Vpp. So the overshoots are 22% beyond the "PEP" level. That means ALC would have to apply a gain factor of 0.82 to this clip to prevent any clipping of the RF envelope. Which would reduce the average power of the transmission, decreasing the SNR at the receiving end. Reducing the power of your watts PEP...?
This is all exactly what is talked about in the CESSB article; but it's important to be able to demonstrate it because now when I put in some CESSB code I should be able to quantify the improvement. To re-iterate - the SSB modulation process, no matter whether it is done digitally or by purely analog techniques (whether phasing or superhet with crystal filter), inherently it causes overshoot (clipping) necessitating reduction in PA gain to avoid clipping that causes splatter. Even with a completely perfect input signal, such as Churchill's speech, which has no clipping at all, it still occurs at RF. Clipping at baseband audio and clipping of the SSB envelope are NOT the same thing! And this is what CESSB is aiming to improve.?
Note that I also measured the spectrum - transmitting Churchill at 0.6W PEP on 7030 kHz into my dummy load, 26dB of attenuation to the spectrum analyzer; the attached "Spectrum.jpeg" shows the result, 20kHz span (2kHz / horizontal division). The video bandwidth setting is 1Hz, resulting in a slow 140 second sweep time so the spectrum indicates average power not peaks.?
I could also zoom in on the end of the 1kHz 2 seconds tone burst at the beginning of the audio sample. You can see that even though at audio, there is no clipping (overshoot), at RF the envelope exhibits an unwanted bulge at the end which in a PA at full power, would result in clipping and splatter.?
Next as an experiment I amplified Churchill by 3dB in Audacity; which is a very crude form of compression because now his peaks which were close to full scale, get clipped. Still, nothing at the audio input exceeds full scale (+/- 1.0) though now the higher frequency components will be emphasized because the clipping instances are getting like a squarewave at their edges. Now the attached "ScopeCompressed.jpeg" shows the overshoot situation got a lot worse, it is now 58%. The spectrum - attached file "SpectrumCompressed.jpeg" is still as expected, OK, because the "overshoot" is not really overdriving the amplifier because the gain was set so low, for only 0.6W PEP so that I could observe the overshoots. The average level is seen rk be higher, as expected.?
All of this is exactly what the QEX CESSB article talks about; so there's nothing unexpected here; but it's very nice to be able to see it and "feel it" and have a baseline to compare against when I put in improvements.?
> Yes, I would also be interested in an update. > Will there actually be a difference between a? > QMX with SSB and a QSX?
That's a very interesting question. I had previously expected that the transmit performance on SSB for QMX would not be as good as SSB generated conventionally by a quadrature sampling exciter and linear driver/PA chain. This would mean QSX still had value though undoubtedly the gap would be narrow and perhaps indicate an upgrade in QSX spec would be desirable.?
However now it seems that QMX SSB performance will exceed what was possible with QSX. Which is a very interesting concept to put it mildly (actually I find it mind-blowing). So what then IS the remaining point of QSX as it was originally planned? Almost all originally planned QSX features will have been delivered by a 160-6m QMX+. A remaining difference is that QSX has 10W output compared to 3-6W on a QMX+.?
So it's an existential question I spend a lot of my thinking about. A lot of thinking on long drives, lying in bed hot summer nights insomniac-style, and other such occasions when it is not wasteful to spend thought: not saying I stare at the lab ceiling for hours when I should be hammering out a thousand emails, help desk tickets or lined of C code for QMX SSB.?
I suspect in the end the answer will probably be, that QMX+ does indeed cover almost all of what QSX intended. So as often mentioned here and everywhere, though QSX was a lot slower than originally expected, and many other projects and products occurred in the interim, seemingly to some commentators as unwelcome interruptions, most of these actually became stepping stones towards QSX. And now we may have accidentally taken one stepping stone too far and achieved QSX before its time and name, in the form of QMX+. Apart from that 3dB output power, it's almost all in there, and more.
All of that still doesn't mean QSX has been or should be abandoned. It's not necessary to step down with any degree or sorrow, regret or remorse. On the contrary, QSX having been substantially delivered via QMX+, relieves the demand and pressure for launch of QSX. Which allows the imagination to run wild and free with a much more ambitious product. Which could be quietly developed to a much higher specification, to provide a more substantial differentiation to QMX+.?
Some may have heard me talk of 7 radios. 7 plans. Which isn't because the Harry Potter novels are 7 in number. And doesn't limit me to developing no more after that 7. Just that in my own head having gradually formulated a multi year technical and business plan, I had conceived 7 transceivers. 5 you have. QCX+, QCX-mini, QDX, QMX and QMX+. The shape and form of the remaining two, which may or may not materialize unexpectedly in the coming year or two, is imperfectly defined and in a constant state of change. One was to be QSX; but now given the success with QMX+, I started to dare dream that the QSX plan can evolve more into a super QSX.?
Executive summary: exciting times and I ain't done yet!
73 Hans G0UPL
On Sat, Sep 28, 2024 at 3:50?PM Chris KB1NLW via <chrisrey1= [email protected]> wrote: Hans:
Are you able to give us an update.
Your last update was very welcome.
?
Thanks?
Chris
|
|
Thanks Hans. I thought you might be taking the CESSB road.
?
Lest people here get too curious as to SSB status, here's a cautionary tale:
?
I worked at a meduim sized company that was building a BabelBox; i.e., a server that would route any physical network available to any other (depending on the server's hardware) and we were about 60 days out from a hard ship date to Air France, and in testing.
?
Management (inexperienced) panicked and instituted a daily status meeting for all developers, at 8 AM no less. This was so the project managers could submit a daily report to the executives.
?
That slipped the project another 90 days.
?
TL;DR Moral: Be careful what you ask for, and also how often you ask for it.
|
I'm very pleased that you made this request, Greg, because it motivated me to re-assess my changes using before and after photographs and the changes I made to L401 were very subtle in the end. It turns out that BPF peak positions are far more sensitive to L401 windings spacing than RF output power is to corrections made in L511, L512, and L513!
?
As I mentioned in my last post, I "over-squeezed" the spacing between L401 turn 1 and turn 19 on my initial squeeze and then attempted to reduce that squeeze and mitigate its impact on the bands below 30m by opening up the spacing between turn 19 and turn 28.
?
In this morning's investigation, I used the photo that I posted below (post ? #130394) as my L401 "before tuning" photo. I had already squeezed L511, L512, and L513 to nearly their final settings to increase my my RF output power but I had not touched L401 yet.
?
I just opened-up the sandwich to take the attached "after" board photo. To make the subtle changes more apparent (extremely apparent), I also created an L401-only comparison graphic. The left side of the graphic is the original L401 (blurry side...sorry) and the right side illustrates the state of my final L401.? Pay attention to the angle subtended by the "squeeze" and "expand" sections of the windings. The GIMP too makes this easy!
?
The "squeeze" section (yellow) originally subtended about 222 degrees. It now subtends only 198 degrees.
The "expand"? section (blue) originally subtended about 114 degrees. It now subtends about 150 degrees.
?
I drafted the comparo graphic rather hastily. I hope it doesn't contain errors but I'll check it tonight. Even so, you and others will get the idea.
?
73,
Cal -- AD8Q
?
On Fri, Sep 27, 2024 at 04:09 PM, Greg McCain wrote:
toggle quoted message
Show quoted text
<snip>
?
Please do post the picture. It needs to be in the WIKI section too. I plan to save it in my personal QMX golden knowledge files store too.
?
73 GREG KI4NVX?
|