Re: QMX power up instructions
Bill,
I am probably wrong but I don’t see how starting at a lower voltage will create any less chance of issues than full voltage…. may just prolong the inevitable.?
Yes, it may not smoke a part or make as loud a pop but unless you have some great testing tricks the only thing you may determine is that there’s no smoke at 9V…… but when you go to 12V there is.
After following these threads for a couple of years I believe that careful assembly, checking component values, component orientation, good soldering, CORRECT VOLTAGE, and paying attention to detail leads to happy results.
I don’t know what the standard is today but back in the ‘60s and ‘70s we burned in our equipment for a full 30hours before it was considered shippable, if there was a failure or drifting the problem was fixed and another 30 hours went by before it was declared ready. ?All we used in those days were U.S. components and even then sometimes we had to sort through to make sure that the parts made specs.
So, IMHO, read the manual 2-3 times, take your time and do it right. ?Apply the expected power and see what happens. ?If you did everything right and it still blows then you had a bad component.
Ya, and be sure to check your antenna for a good SWR too, that’s a biggie.
Enjoy some fantastic kits,
John KK4ITX? ?Each mistake is a learning opportunity.?
toggle quoted message
Show quoted text
On Aug 1, 2023, at 3:14 PM, nz0tham@... wrote:
?Would a? standard 9V battery do for first startup? I'm building my QMX for 12V.
73, Bill NZ0T
|
Re: QMX power up instructions
On Tue, Aug 1, 2023 at 06:26 PM, Chris wrote:
I think there should be more after item 10 to help users get things started slowly, checking that the voltages and currents are correct and avoiding catastrophic damage.
It WBN if there was a far more extensive first start diagnostic, something that starts by assuming that everything is broken and only moves on when a function has been tested and demonstrated to work:
I agree with Chris.? There could be? "commissioning" routines built into the firmware to systematically bring parts of the system on line, with checks done on power rail voltage and current.? In particular, running on the linear 3.3V supply initially so the MCU works would be useful, especially as the heat generated by the linear supply would not be a factor with the rest of the unit not fully working.? As I have said before, a 9V battery (as used in smoke alarms) can be used to power up QCX/QDX/QDM units on RECEIVE only for initial tests.? They have an inherent current limiting characteristic and are readily available. ? -- Peter Lee G3SPL
|
Re: Gate voltages to BS 170s are not stable. Need some suggestions.
#help
#problem
#qmx
Walt, check D109 as it too is vulnerable and it is an easy pull.
Beyond that, sensing heat either by finger or IR Cam is best. Trying
to probe by DVM for voltage drops is nearly hopeless.
Here is my worry: The MCU is by far the largest area of vulnerable
silicon on the Vdd network. It is also the one thing you cannot
replace. Ugghh!
JZ
toggle quoted message
Show quoted text
On Tue, Aug 1, 2023 at 4:32?PM Walt (KK4DF) <wewilsonjr@...> wrote:
John,
In checking the main board, somewhere on this board, the 3.3v VDD is shorted to ground. Are there components that are most likely to be the cause of the short? I did try injecting 3.3v with a current limited supply set at max 150 mA, and could not detect any component heating up. Components using VDD directly (without a series resistor) include IC501, IC502, IC201, IC202, and the main processor. Any thoughts on how to isolate without removing components?
Thanks,
Wat
|
QDX-HB Rev 4 incomplete high band configurations
I just completed and started testing a QDX Rev 4 built as high band using the Rev 4 Assembly manual.
On first power-up everything went OK and I updated the firmware to 1_10.
On bootup, in the Band configurations menu 12 & 10 Meters are not defined.
What I have are 20,17,15,30, & 20 Meters defined.
How do I get 12 & 10 Meters defined?
73 - Dave, N4ELM
|
Re: Gate voltages to BS 170s are not stable. Need some suggestions.
#help
#problem
#qmx
John,
In checking the main board, somewhere on this board, the 3.3v VDD is shorted to ground. Are there components that are most likely to be the cause of the short? ?I did try injecting 3.3v with a current limited supply set at max 150 mA, and could not detect any component heating up. Components using VDD directly (without a series resistor) include IC501, IC502, IC201, IC202, and the main processor. Any thoughts on how to isolate without removing components?
Thanks,
Wat
|
Re: QMX power up instructions
Would a? standard 9V battery do for first startup? I'm building my QMX for 12V.
73, Bill NZ0T
|
Karl,
"Radio Shack 64-2185 solder...DIGITAL soldering station is way too big. Can't find tips for it "
I'm not in front of my RS digital soldering station, but if it is like yours, I found Hakko tips work for it.? I get them from EAE Sales ()? when they show up at Dayton (now Xenia) each year in the big white tent in the flea market.
They sell great refurbed soldering equipment - I have a Hakko SMD hot air rework station from them, as well as one of the Edsyn soldering stations, so I have something more portable than the RS beast to take for build-a-thons at hamfests or club meetings.
73,
-- Dave, N8SBE
toggle quoted message
Show quoted text
On 2023-07-28 17:52, Karl via groups.io wrote:
Thank you! Control-w...gotta remember that! I get more heartburn with windows! Now, after several years of hitting wrong buttons and winding up in Fukawi-land, am getting a little more able to not EXPLODE when these things happen!
By the way, I have soldered about 3.5 capacitors in my QMX learning that I need a way smaller tip to do this! My trusty Radio Shack 64-2185 solder...DIGITAL soldering station is way too big. Can't find tips for it so got a cheapo 9 dolla 60 watt iron coming from Amazon. It has a tunable thermostat and a very small .2 mm tip in the pile of tips!
73
Karl
KI4ZUQ
|
Can others verify what I'm seeing so I know it's not just me?
Fldigi is non-functional for digital modes with the new firmware 007. Wsjtx seems to work, but not fldigi. Fldigi will transmit one time and then never again until the power on the QMX is cycled. No rise in current flow at all after the initial transmit. I suspect the change in the PTT function is what broke it.
Both fldigi and Wsjtx strangely put out less power with 007. Using 006 I get about a watt more power out.
Everything worked with 006 except Olivia mode required a Tune or the use of another mode before it would work.
Moving back to 006 for now.
toggle quoted message
Show quoted text
I changed the delimiter from "," to "." back in firmware 006. Tried to change it again and it will not take any changes. It always comes up the same even on 007. Ideas? Bug?
Also the RF sweeps still hang on 40 and 60meters as it has for a couple of firmware versions now. It leaves the QMX locked up so only a power cycle will get it going again.
Can someone point me to where to set the default frequency on boot up? I want it to come up on 14.070, but it always comes up on 80M, 3573 kHz. I've never used that freq. as far as I know so where does it come from. Older firmware had a default freq. that sometimes worked.?
P.S. I forgot to mention, that until I can make the S-meter worthwhile, which will be wrapped up with implementing the SWR metering, I just blanked the S-meter for now. So this is intentional, not a bug. I will make? nice proper S-meter that works nicely and is properly logarithmic.? On Tue, Aug 1, 2023 at 8:43?PM Hans Summers via <hans.summers= [email protected]> wrote: Hi all
QMX firmware 1_00_007 is now released see with the following change summary:
1. Add Keyer menu configuration "GPS protection" to enable auto protection 2. Make GPS protection auto-practice a bit less paranoid 3. Bug fix: Fix the WSPR/CW/FSKCW beacon functionality 4. Bug fix: Fix the applicable CAT Q1, Q2 etc commands 5. Add mode indicator character, row 1, column 12 6. Digimode transmit status indicator, underlines VFO A symbol 7. Fix string editing (messages editing) in the LCD/buttons 8. When editing messages, horizontal scroll when message longer than a screen width 9. Bug fix: Practice mode indicator not shown if it is set at power-up 10. Bug fix: Keyer Swap reversed compared to QCX 11. Bug fix: Practice mode indicator not shown in Digi mode 12. Bug fix: On digi, carrier transmission started on PTT not on incoming audio 13. Improve LCD write speed by a factor of approx 50 14. Bug fix: When battery indicator enabled, CW decode could corrupt top row
Just testing it with the power supply at 9V (this is a 12V QMX, so I must have about 2W) on 20m FT8 right now while writing this email - I worked China BG0CAB and Japan JG3LGD (answering their CQs). I think it works ;-)
Details:
1. Add Keyer menu configuration "GPS protection" to enable auto protection
This feature of auto-practice mode ("G" in the display) can now be disabled in the keyer menu.?
2. Make GPS protection auto-practice a bit less paranoid
It now takes 10 times longer for QMX to decide it has a GPS serial data stream incoming on its paddle port. Which is still only a few milliseconds.
3. Bug fix: Fix the WSPR/CW/FSKCW beacon functionality
WSPR, CW and FSKCW?beacon functionality (standalone WSPR encoding) now works the same as in QCX-mini. GPS can be used to set the time and location.?
4. Bug fix: Fix the applicable CAT Q1, Q2 etc commands
Self-explanatory... the Q1, Q2 etc commands which some programs use, are now back and compatible with QDX (where applicable).?
5. Add mode indicator character, row 1, column 12
Now the mode is always shown on the display in a single character at column 12 of the first row. See attachment. I designed it to say "DI GI" on the single 5 x 8 pixel grid character, and "C W" in the case of CW. I also have pixel patterns LSB, USB, AM etc designed for when the time comes.?
6. Digimode transmit status indicator, underlines VFO A symbol
There's also now a transmit status indicator which underlines the "A" of the VFO symbol in Digi mode; the behaviour of this symbol is similar to the LED on a QDX. Taking WSJT-X as an example: .? means WSJT-X sent a CAT command to put QMX into TX mode, but there is no audio (perhaps wrong sound card selected) .. means that QMX is receiving audio from the PC but the volume level is insufficient - all three settings should be 100% - means that the QMX is in transmit and the audio is correct, and it is outputting RF.?
7. Fix string editing (messages editing) in the LCD/buttons
You can now edit CW messages properly on QMX, in the same way as it is done in QCX. Previously the special characters for inserting and deleting did not work?properly, though CW message sending worked and you could enter the messages properly in the terminal.?
8. When editing messages, horizontal scroll when message longer than a screen width
Now when you are editing messages, it will scroll the display bottom row to the right so that a 16-character window on the whole messages scrolls and always shows the character being edited, with the cursor correctly?underlining it.?
9. Bug fix: Practice mode indicator not shown if it is set at power-up
Now the Practice mode P symbol is correctly shown from power up.?
10. Bug fix: Keyer Swap reversed compared to QCX
Fixed it... so now QMX interpretation of Dit and Dah inputs should match QCX. If you need to enable Keyer Swap on a QCX, you do on a QMX too.?
11. Bug fix: Practice mode indicator not shown in Digi mode
Now P indicator for Practice mode is shown (and effective) in Digi mode too
12. Bug fix: On digi, carrier transmission started on PTT not on incoming audio
Transmission started on PTT becoming active, but at the "USB Dial" frequency (audio offset zero). Just nobody noticed it ;-)
13. Improve LCD write speed by a factor of approx 50
The LCD writing was incorrectly timed, massively paranoidly... I have now sorted all that out properly with the proper 37us LCD command and write waits (and 1.5ms in the case of a screen clear). So it is working very well now. Everything should be much more responsive now, and not skipping menu entries etc.?
14. Bug fix: When battery indicator enabled, CW decode could corrupt top row
I believe you can now enable the battery indicator and it will not corrupt the keyer timing now, too.?
SO...
Please provide any observations and bug reports in this thread.?
73 Hans G0UPL
|
QMX X502: BNC RF connector
Hi, is X502: BNC RF connector supposed to fit flat on the QMX pcb??
There is a raised flat just behind the threaded part ,that holds the connector about 1mm off the pcb.
Scotty
|
Hans, it seems when the radio is *already* in practice mode before plugging in the GPS (QLG2), it doesn't recognize it and the keyer just goes on keying endlessly. It does seem to actually be reading the GPS serial data though as the GPS diagnostic screen works while it's happily keying away. I have the radio in practice mode a lot because sometimes I'm just listening on a not-very-resonant antenna and don't want to accidentally transmit into high SWR (and I'm a godawful CW operator who needs a *LOT* of practice). I observed this in the previous firmware revision that added the GPS screen too.
Turning practice mode off, attaching dummy load and then plugging GPS in seems to key a few times (maybe 5 dits worth at 20wpm), then properly recognizes it and puts the "G" on screen and stops keying.
Overall the other changes seem to be a big improvement... haven't tested everything but enabling the battery indicator doesn't appear to be affecting the CW keyer like it was before, and using the on-device UI in general seems way more responsive/less glitchy. I did notice the battery indicator itself glitching a little bit when keying but this is super minor (photo attached). This only seems to happen if you have the CW decoder enabled for TX.
I like the little mode indicator, and the digi TX indicator was something I definitely was hoping for. Good stuff!
Thanks and 73
Andrew KI7FXL
|
Thank you for all the updates! One thing I have not seen addressed is the inconsistent volume knob behavior. It skips and loops from full volume to zero if you pass full volume. (I haven’t checked 007 for it. )
--
Colin - K6JTH?
|
I changed the delimiter from "," to "." back in firmware 006. Tried to change it again and it will not take any changes. It always comes up the same even on 007. Ideas? Bug?
Also the RF sweeps still hang on 40 and 60meters as it has for a couple of firmware versions now. It leaves the QMX locked up so only a power cycle will get it going again.
toggle quoted message
Show quoted text
Can someone point me to where to set the default frequency on boot up? I want it to come up on 14.070, but it always comes up on 80M, 3573 kHz. I've never used that freq. as far as I know so where does it come from. Older firmware had a default freq. that sometimes worked.?
P.S. I forgot to mention, that until I can make the S-meter worthwhile, which will be wrapped up with implementing the SWR metering, I just blanked the S-meter for now. So this is intentional, not a bug. I will make? nice proper S-meter that works nicely and is properly logarithmic.? On Tue, Aug 1, 2023 at 8:43?PM Hans Summers via <hans.summers= [email protected]> wrote: Hi all
QMX firmware 1_00_007 is now released see with the following change summary:
1. Add Keyer menu configuration "GPS protection" to enable auto protection 2. Make GPS protection auto-practice a bit less paranoid 3. Bug fix: Fix the WSPR/CW/FSKCW beacon functionality 4. Bug fix: Fix the applicable CAT Q1, Q2 etc commands 5. Add mode indicator character, row 1, column 12 6. Digimode transmit status indicator, underlines VFO A symbol 7. Fix string editing (messages editing) in the LCD/buttons 8. When editing messages, horizontal scroll when message longer than a screen width 9. Bug fix: Practice mode indicator not shown if it is set at power-up 10. Bug fix: Keyer Swap reversed compared to QCX 11. Bug fix: Practice mode indicator not shown in Digi mode 12. Bug fix: On digi, carrier transmission started on PTT not on incoming audio 13. Improve LCD write speed by a factor of approx 50 14. Bug fix: When battery indicator enabled, CW decode could corrupt top row
Just testing it with the power supply at 9V (this is a 12V QMX, so I must have about 2W) on 20m FT8 right now while writing this email - I worked China BG0CAB and Japan JG3LGD (answering their CQs). I think it works ;-)
Details:
1. Add Keyer menu configuration "GPS protection" to enable auto protection
This feature of auto-practice mode ("G" in the display) can now be disabled in the keyer menu.?
2. Make GPS protection auto-practice a bit less paranoid
It now takes 10 times longer for QMX to decide it has a GPS serial data stream incoming on its paddle port. Which is still only a few milliseconds.
3. Bug fix: Fix the WSPR/CW/FSKCW beacon functionality
WSPR, CW and FSKCW?beacon functionality (standalone WSPR encoding) now works the same as in QCX-mini. GPS can be used to set the time and location.?
4. Bug fix: Fix the applicable CAT Q1, Q2 etc commands
Self-explanatory... the Q1, Q2 etc commands which some programs use, are now back and compatible with QDX (where applicable).?
5. Add mode indicator character, row 1, column 12
Now the mode is always shown on the display in a single character at column 12 of the first row. See attachment. I designed it to say "DI GI" on the single 5 x 8 pixel grid character, and "C W" in the case of CW. I also have pixel patterns LSB, USB, AM etc designed for when the time comes.?
6. Digimode transmit status indicator, underlines VFO A symbol
There's also now a transmit status indicator which underlines the "A" of the VFO symbol in Digi mode; the behaviour of this symbol is similar to the LED on a QDX. Taking WSJT-X as an example: .? means WSJT-X sent a CAT command to put QMX into TX mode, but there is no audio (perhaps wrong sound card selected) .. means that QMX is receiving audio from the PC but the volume level is insufficient - all three settings should be 100% - means that the QMX is in transmit and the audio is correct, and it is outputting RF.?
7. Fix string editing (messages editing) in the LCD/buttons
You can now edit CW messages properly on QMX, in the same way as it is done in QCX. Previously the special characters for inserting and deleting did not work?properly, though CW message sending worked and you could enter the messages properly in the terminal.?
8. When editing messages, horizontal scroll when message longer than a screen width
Now when you are editing messages, it will scroll the display bottom row to the right so that a 16-character window on the whole messages scrolls and always shows the character being edited, with the cursor correctly?underlining it.?
9. Bug fix: Practice mode indicator not shown if it is set at power-up
Now the Practice mode P symbol is correctly shown from power up.?
10. Bug fix: Keyer Swap reversed compared to QCX
Fixed it... so now QMX interpretation of Dit and Dah inputs should match QCX. If you need to enable Keyer Swap on a QCX, you do on a QMX too.?
11. Bug fix: Practice mode indicator not shown in Digi mode
Now P indicator for Practice mode is shown (and effective) in Digi mode too
12. Bug fix: On digi, carrier transmission started on PTT not on incoming audio
Transmission started on PTT becoming active, but at the "USB Dial" frequency (audio offset zero). Just nobody noticed it ;-)
13. Improve LCD write speed by a factor of approx 50
The LCD writing was incorrectly timed, massively paranoidly... I have now sorted all that out properly with the proper 37us LCD command and write waits (and 1.5ms in the case of a screen clear). So it is working very well now. Everything should be much more responsive now, and not skipping menu entries etc.?
14. Bug fix: When battery indicator enabled, CW decode could corrupt top row
I believe you can now enable the battery indicator and it will not corrupt the keyer timing now, too.?
SO...
Please provide any observations and bug reports in this thread.?
73 Hans G0UPL
|
Can someone point me to where to set the default frequency on boot up? I want it to come up on 14.070, but it always comes up on 80M, 3573 kHz. I've never used that freq. as far as I know so where does it come from. Older firmware had a default freq. that sometimes worked.?
toggle quoted message
Show quoted text
P.S. I forgot to mention, that until I can make the S-meter worthwhile, which will be wrapped up with implementing the SWR metering, I just blanked the S-meter for now. So this is intentional, not a bug. I will make? nice proper S-meter that works nicely and is properly logarithmic.? On Tue, Aug 1, 2023 at 8:43?PM Hans Summers via <hans.summers= [email protected]> wrote: Hi all
QMX firmware 1_00_007 is now released see with the following change summary:
1. Add Keyer menu configuration "GPS protection" to enable auto protection 2. Make GPS protection auto-practice a bit less paranoid 3. Bug fix: Fix the WSPR/CW/FSKCW beacon functionality 4. Bug fix: Fix the applicable CAT Q1, Q2 etc commands 5. Add mode indicator character, row 1, column 12 6. Digimode transmit status indicator, underlines VFO A symbol 7. Fix string editing (messages editing) in the LCD/buttons 8. When editing messages, horizontal scroll when message longer than a screen width 9. Bug fix: Practice mode indicator not shown if it is set at power-up 10. Bug fix: Keyer Swap reversed compared to QCX 11. Bug fix: Practice mode indicator not shown in Digi mode 12. Bug fix: On digi, carrier transmission started on PTT not on incoming audio 13. Improve LCD write speed by a factor of approx 50 14. Bug fix: When battery indicator enabled, CW decode could corrupt top row
Just testing it with the power supply at 9V (this is a 12V QMX, so I must have about 2W) on 20m FT8 right now while writing this email - I worked China BG0CAB and Japan JG3LGD (answering their CQs). I think it works ;-)
Details:
1. Add Keyer menu configuration "GPS protection" to enable auto protection
This feature of auto-practice mode ("G" in the display) can now be disabled in the keyer menu.?
2. Make GPS protection auto-practice a bit less paranoid
It now takes 10 times longer for QMX to decide it has a GPS serial data stream incoming on its paddle port. Which is still only a few milliseconds.
3. Bug fix: Fix the WSPR/CW/FSKCW beacon functionality
WSPR, CW and FSKCW?beacon functionality (standalone WSPR encoding) now works the same as in QCX-mini. GPS can be used to set the time and location.?
4. Bug fix: Fix the applicable CAT Q1, Q2 etc commands
Self-explanatory... the Q1, Q2 etc commands which some programs use, are now back and compatible with QDX (where applicable).?
5. Add mode indicator character, row 1, column 12
Now the mode is always shown on the display in a single character at column 12 of the first row. See attachment. I designed it to say "DI GI" on the single 5 x 8 pixel grid character, and "C W" in the case of CW. I also have pixel patterns LSB, USB, AM etc designed for when the time comes.?
6. Digimode transmit status indicator, underlines VFO A symbol
There's also now a transmit status indicator which underlines the "A" of the VFO symbol in Digi mode; the behaviour of this symbol is similar to the LED on a QDX. Taking WSJT-X as an example: .? means WSJT-X sent a CAT command to put QMX into TX mode, but there is no audio (perhaps wrong sound card selected) .. means that QMX is receiving audio from the PC but the volume level is insufficient - all three settings should be 100% - means that the QMX is in transmit and the audio is correct, and it is outputting RF.?
7. Fix string editing (messages editing) in the LCD/buttons
You can now edit CW messages properly on QMX, in the same way as it is done in QCX. Previously the special characters for inserting and deleting did not work?properly, though CW message sending worked and you could enter the messages properly in the terminal.?
8. When editing messages, horizontal scroll when message longer than a screen width
Now when you are editing messages, it will scroll the display bottom row to the right so that a 16-character window on the whole messages scrolls and always shows the character being edited, with the cursor correctly?underlining it.?
9. Bug fix: Practice mode indicator not shown if it is set at power-up
Now the Practice mode P symbol is correctly shown from power up.?
10. Bug fix: Keyer Swap reversed compared to QCX
Fixed it... so now QMX interpretation of Dit and Dah inputs should match QCX. If you need to enable Keyer Swap on a QCX, you do on a QMX too.?
11. Bug fix: Practice mode indicator not shown in Digi mode
Now P indicator for Practice mode is shown (and effective) in Digi mode too
12. Bug fix: On digi, carrier transmission started on PTT not on incoming audio
Transmission started on PTT becoming active, but at the "USB Dial" frequency (audio offset zero). Just nobody noticed it ;-)
13. Improve LCD write speed by a factor of approx 50
The LCD writing was incorrectly timed, massively paranoidly... I have now sorted all that out properly with the proper 37us LCD command and write waits (and 1.5ms in the case of a screen clear). So it is working very well now. Everything should be much more responsive now, and not skipping menu entries etc.?
14. Bug fix: When battery indicator enabled, CW decode could corrupt top row
I believe you can now enable the battery indicator and it will not corrupt the keyer timing now, too.?
SO...
Please provide any observations and bug reports in this thread.?
73 Hans G0UPL
|
once you select VFO A and B and then doble click right button to get messages ?the old values are left on the screen
next few clicks are moving the value to VFO
73 de Robert EI9ILB Hi Hans,
Sorry (head in hands). I looked for it and just didn't see it. I figured it had to be somewhere. Thanks for your patience with us oldies and apparently I'm going blind as well.
Hello Cliff
No, I explained in the release notes that this transmitter test function is now incorporated into the "Diagnostics" screen. All the "Transmitter test" functionality is now present in the diagnostics screen. Hans,
I'm sure you've already noticed, but I just noticed that 006 is missing the Transmit Test function under the Hardware Tests grouping. Had to go back to 005 to do the transmit tests.
- Keyer Swap still needs to be 'ON' for paddles to be correct and therefore is not consistent with QCX.
Thanks I fixed it in the forthcoming 1_00_007 ?
-'P' does not show up after power cycle; must go into menu and exit before it reappears. There is no power out during this time even though lack of 'P' would make you think it is not in practice mode.
Thanks I fixed it in the forthcoming 1_00_007
73 Hans G0UPL
|
Backwards almost never happens in an automated assembly process. In a rework/repair station maybe, but even that is low likelihood. JZ On Tue, Aug 1, 2023 at 1:43?PM Daniel Walter via groups.io <nm3a@...> wrote:
Allison,
I doubt it was in backwards - low likelihood - but I didn't take a picture before so I'll never know for sure.
Working through trouble shooting now. Not clear if anything else has been fried.
--
73, Dan NM3A
|
P.S. I forgot to mention, that until I can make the S-meter worthwhile, which will be wrapped up with implementing the SWR metering, I just blanked the S-meter for now. So this is intentional, not a bug. I will make? nice proper S-meter that works nicely and is properly logarithmic.?
On Tue, Aug 1, 2023 at 8:43?PM Hans Summers via <hans.summers= [email protected]> wrote: Hi all
QMX firmware 1_00_007 is now released see with the following change summary:
1. Add Keyer menu configuration "GPS protection" to enable auto protection 2. Make GPS protection auto-practice a bit less paranoid 3. Bug fix: Fix the WSPR/CW/FSKCW beacon functionality 4. Bug fix: Fix the applicable CAT Q1, Q2 etc commands 5. Add mode indicator character, row 1, column 12 6. Digimode transmit status indicator, underlines VFO A symbol 7. Fix string editing (messages editing) in the LCD/buttons 8. When editing messages, horizontal scroll when message longer than a screen width 9. Bug fix: Practice mode indicator not shown if it is set at power-up 10. Bug fix: Keyer Swap reversed compared to QCX 11. Bug fix: Practice mode indicator not shown in Digi mode 12. Bug fix: On digi, carrier transmission started on PTT not on incoming audio 13. Improve LCD write speed by a factor of approx 50 14. Bug fix: When battery indicator enabled, CW decode could corrupt top row
Just testing it with the power supply at 9V (this is a 12V QMX, so I must have about 2W) on 20m FT8 right now while writing this email - I worked China BG0CAB and Japan JG3LGD (answering their CQs). I think it works ;-)
Details:
1. Add Keyer menu configuration "GPS protection" to enable auto protection
This feature of auto-practice mode ("G" in the display) can now be disabled in the keyer menu.?
2. Make GPS protection auto-practice a bit less paranoid
It now takes 10 times longer for QMX to decide it has a GPS serial data stream incoming on its paddle port. Which is still only a few milliseconds.
3. Bug fix: Fix the WSPR/CW/FSKCW beacon functionality
WSPR, CW and FSKCW?beacon functionality (standalone WSPR encoding) now works the same as in QCX-mini. GPS can be used to set the time and location.?
4. Bug fix: Fix the applicable CAT Q1, Q2 etc commands
Self-explanatory... the Q1, Q2 etc commands which some programs use, are now back and compatible with QDX (where applicable).?
5. Add mode indicator character, row 1, column 12
Now the mode is always shown on the display in a single character at column 12 of the first row. See attachment. I designed it to say "DI GI" on the single 5 x 8 pixel grid character, and "C W" in the case of CW. I also have pixel patterns LSB, USB, AM etc designed for when the time comes.?
6. Digimode transmit status indicator, underlines VFO A symbol
There's also now a transmit status indicator which underlines the "A" of the VFO symbol in Digi mode; the behaviour of this symbol is similar to the LED on a QDX. Taking WSJT-X as an example: .? means WSJT-X sent a CAT command to put QMX into TX mode, but there is no audio (perhaps wrong sound card selected) .. means that QMX is receiving audio from the PC but the volume level is insufficient - all three settings should be 100% - means that the QMX is in transmit and the audio is correct, and it is outputting RF.?
7. Fix string editing (messages editing) in the LCD/buttons
You can now edit CW messages properly on QMX, in the same way as it is done in QCX. Previously the special characters for inserting and deleting did not work?properly, though CW message sending worked and you could enter the messages properly in the terminal.?
8. When editing messages, horizontal scroll when message longer than a screen width
Now when you are editing messages, it will scroll the display bottom row to the right so that a 16-character window on the whole messages scrolls and always shows the character being edited, with the cursor correctly?underlining it.?
9. Bug fix: Practice mode indicator not shown if it is set at power-up
Now the Practice mode P symbol is correctly shown from power up.?
10. Bug fix: Keyer Swap reversed compared to QCX
Fixed it... so now QMX interpretation of Dit and Dah inputs should match QCX. If you need to enable Keyer Swap on a QCX, you do on a QMX too.?
11. Bug fix: Practice mode indicator not shown in Digi mode
Now P indicator for Practice mode is shown (and effective) in Digi mode too
12. Bug fix: On digi, carrier transmission started on PTT not on incoming audio
Transmission started on PTT becoming active, but at the "USB Dial" frequency (audio offset zero). Just nobody noticed it ;-)
13. Improve LCD write speed by a factor of approx 50
The LCD writing was incorrectly timed, massively paranoidly... I have now sorted all that out properly with the proper 37us LCD command and write waits (and 1.5ms in the case of a screen clear). So it is working very well now. Everything should be much more responsive now, and not skipping menu entries etc.?
14. Bug fix: When battery indicator enabled, CW decode could corrupt top row
I believe you can now enable the battery indicator and it will not corrupt the keyer timing now, too.?
SO...
Please provide any observations and bug reports in this thread.?
73 Hans G0UPL
|
Allison,?
I doubt it was in backwards - low likelihood - but I didn't take a picture before so I'll never know for sure.?
Working through trouble shooting now. Not clear if anything else has been fried.?
--
73, Dan? NM3A
|
Hi all
QMX firmware 1_00_007 is now released see with the following change summary:
1. Add Keyer menu configuration "GPS protection" to enable auto protection 2. Make GPS protection auto-practice a bit less paranoid 3. Bug fix: Fix the WSPR/CW/FSKCW beacon functionality 4. Bug fix: Fix the applicable CAT Q1, Q2 etc commands 5. Add mode indicator character, row 1, column 12 6. Digimode transmit status indicator, underlines VFO A symbol 7. Fix string editing (messages editing) in the LCD/buttons 8. When editing messages, horizontal scroll when message longer than a screen width 9. Bug fix: Practice mode indicator not shown if it is set at power-up 10. Bug fix: Keyer Swap reversed compared to QCX 11. Bug fix: Practice mode indicator not shown in Digi mode 12. Bug fix: On digi, carrier transmission started on PTT not on incoming audio 13. Improve LCD write speed by a factor of approx 50 14. Bug fix: When battery indicator enabled, CW decode could corrupt top row
Just testing it with the power supply at 9V (this is a 12V QMX, so I must have about 2W) on 20m FT8 right now while writing this email - I worked China BG0CAB and Japan JG3LGD (answering their CQs). I think it works ;-)
Details:
1. Add Keyer menu configuration "GPS protection" to enable auto protection
This feature of auto-practice mode ("G" in the display) can now be disabled in the keyer menu.?
2. Make GPS protection auto-practice a bit less paranoid
It now takes 10 times longer for QMX to decide it has a GPS serial data stream incoming on its paddle port. Which is still only a few milliseconds.
3. Bug fix: Fix the WSPR/CW/FSKCW beacon functionality
WSPR, CW and FSKCW?beacon functionality (standalone WSPR encoding) now works the same as in QCX-mini. GPS can be used to set the time and location.?
4. Bug fix: Fix the applicable CAT Q1, Q2 etc commands
Self-explanatory... the Q1, Q2 etc commands which some programs use, are now back and compatible with QDX (where applicable).?
5. Add mode indicator character, row 1, column 12
Now the mode is always shown on the display in a single character at column 12 of the first row. See attachment. I designed it to say "DI GI" on the single 5 x 8 pixel grid character, and "C W" in the case of CW. I also have pixel patterns LSB, USB, AM etc designed for when the time comes.?
6. Digimode transmit status indicator, underlines VFO A symbol
There's also now a transmit status indicator which underlines the "A" of the VFO symbol in Digi mode; the behaviour of this symbol is similar to the LED on a QDX. Taking WSJT-X as an example: .? means WSJT-X sent a CAT command to put QMX into TX mode, but there is no audio (perhaps wrong sound card selected) .. means that QMX is receiving audio from the PC but the volume level is insufficient - all three settings should be 100% - means that the QMX is in transmit and the audio is correct, and it is outputting RF.?
7. Fix string editing (messages editing) in the LCD/buttons
You can now edit CW messages properly on QMX, in the same way as it is done in QCX. Previously the special characters for inserting and deleting did not work?properly, though CW message sending worked and you could enter the messages properly in the terminal.?
8. When editing messages, horizontal scroll when message longer than a screen width
Now when you are editing messages, it will scroll the display bottom row to the right so that a 16-character window on the whole messages scrolls and always shows the character being edited, with the cursor correctly?underlining it.?
9. Bug fix: Practice mode indicator not shown if it is set at power-up
Now the Practice mode P symbol is correctly shown from power up.?
10. Bug fix: Keyer Swap reversed compared to QCX
Fixed it... so now QMX interpretation of Dit and Dah inputs should match QCX. If you need to enable Keyer Swap on a QCX, you do on a QMX too.?
11. Bug fix: Practice mode indicator not shown in Digi mode
Now P indicator for Practice mode is shown (and effective) in Digi mode too
12. Bug fix: On digi, carrier transmission started on PTT not on incoming audio
Transmission started on PTT becoming active, but at the "USB Dial" frequency (audio offset zero). Just nobody noticed it ;-)
13. Improve LCD write speed by a factor of approx 50
The LCD writing was incorrectly timed, massively paranoidly... I have now sorted all that out properly with the proper 37us LCD command and write waits (and 1.5ms in the case of a screen clear). So it is working very well now. Everything should be much more responsive now, and not skipping menu entries etc.?
14. Bug fix: When battery indicator enabled, CW decode could corrupt top row
I believe you can now enable the battery indicator and it will not corrupt the keyer timing now, too.?
SO...
Please provide any observations and bug reports in this thread.?
73 Hans G0UPL
|
Re: QMX power up instructions
I think there should be more after item 10 to help users get things
started slowly, checking that the voltages and currents are correct
and avoiding catastrophic damage.
It WBN if there was a far more extensive first start diagnostic,
something that starts by assuming that everything is broken and
only moves on when a function has been tested and demonstrated to
work:
First, no PWMs running.? Power from the 3V3 linear only.? That
should get the MCU running, the USB working, and allow the
fundamental functionality to be checked. Expect/require no more
than 9V.
Ramp up the power PWMs slowly, checking the voltages, maybe get
the user to check things, especially the current. Don't change to
PWM power until confident that it's OK.? Then the 5V power in a
similar way.
Same with the TX_BIAS and PA control, work up gently and check
that the drive setting and the output are consistent.? Start by
assuming the 1N4007s and BS170s have been installed backwards, or
not at all.
ADC_BIAS might be useful to check the LPF circuit, as? well as
checking that the bias circuit is OK.? With no LPFs enabled it
should be off scale high, with one around 0.7V.? That's with the
TX bias off.
Have the ability to set the PA voltage really low so initial
tests don't destroy things.
The SWR meter would be really useful, combined with running at
low power it could help to preserve the PA and it's friends.
This looks like a lot but much of the fundamental control should
already be implemented, there's some UI and a lot of thought about
using the control and measurements available in slightly
unconventional ways.
This comes from flying and particularly gliding, you don't think
about if something goes wrong, you think about when. Most of the
time it doesn't but when it does you know what to do.
Chris, G5CTH
|
Hi Hans,
Sorry (head in hands). I looked for it and just didn't see it. I figured it had to be somewhere. Thanks for your patience with us oldies and apparently I'm going blind as well.
toggle quoted message
Show quoted text
Hello Cliff
No, I explained in the release notes that this transmitter test function is now incorporated into the "Diagnostics" screen. All the "Transmitter test" functionality is now present in the diagnostics screen. Hans,
I'm sure you've already noticed, but I just noticed that 006 is missing the Transmit Test function under the Hardware Tests grouping. Had to go back to 005 to do the transmit tests.
- Keyer Swap still needs to be 'ON' for paddles to be correct and therefore is not consistent with QCX.
Thanks I fixed it in the forthcoming 1_00_007 ?
-'P' does not show up after power cycle; must go into menu and exit before it reappears. There is no power out during this time even though lack of 'P' would make you think it is not in practice mode.
Thanks I fixed it in the forthcoming 1_00_007
73 Hans G0UPL
|
KK4ITX John
Andrew KI7FXL
Colin Kaminski
EI9ILB