|
Hi all
Here you can find a version 1_06_004 beta:
The version contains the following changes: - When bias mA is 5mA, disable PIN diode forward bias SMPS system completely (results in around 4mA default bias current).
- Change default 80m Frequency min to 3200000.
- Add "Night mode" parameter to configuration screen - when enabled, it makes panel LED very dim, by defining the GPIO pin with internal pullup to light the LED. It's dim but if the QDX is on a shelf in front of you and not in too bright lighting, it will be visible.
- Now successful TX is a 1Hz pulsating indication, the LED current actually follows a 1Hz sinewave; meanwhile the spacing between the 2 blinks in "audio insufficient" error reporting mode is now 0.2 seconds, wider spaced for easier counting
- Changed minimum TX freq from 300kHz to 75kHz (to allow 2200m operation). Note: receive quadrature for 2200m is not done yet.?
- Changed length of band name in the Band Config screen to 4 digits (to allow 2200m operation)
- Bug fix: Qn; CAT command return string length is now longer to fit larger numbers
|
Hans,
Thanks for the quick update!
I'm using the night mode, it is dim! It will take a little getting used to.
It's a very good addition to the firmware.
--Al
WD4AH
|
Hans,
Any chance of enabling the Split and second VFO operations?
toggle quoted message
Show quoted text
Hi all
Here you can find a version 1_06_004 beta:
The version contains the following changes: - When bias mA is 5mA, disable PIN diode forward bias SMPS system completely (results in around 4mA default bias current).
- Change default 80m Frequency min to 3200000.
- Add "Night mode" parameter to configuration screen - when enabled, it makes panel LED very dim, by defining the GPIO pin with internal pullup to light the LED. It's dim but if the QDX is on a shelf in front of you and not in too bright lighting, it will be visible.
- Now successful TX is a 1Hz pulsating indication, the LED current actually follows a 1Hz sinewave; meanwhile the spacing between the 2 blinks in "audio insufficient" error reporting mode is now 0.2 seconds, wider spaced for easier counting
- Changed minimum TX freq from 300kHz to 75kHz (to allow 2200m operation). Note: receive quadrature for 2200m is not done yet.?
- Changed length of band name in the Band Config screen to 4 digits (to allow 2200m operation)
- Bug fix: Qn; CAT command return string length is now longer to fit larger numbers
|
How about the pulsating sinewave brightness 1Hz LED flash during transmit, and the slower blink once or twice error indication? Do the folks that found the blinks difficult to count like this way better??
73 Hans G0UPL http://qrp-labs.com https://www.buymeacoffee.com/g0upl
-------- Original message -------- From: Al Holt <grovekid2@...> Date: Wed, Nov 23, 2022, 5:40 PM To: [email protected]Subject: Re: [QRPLabs] QDX firmware 1_06_004 beta Hans,
Thanks for the quick update!
I'm using the night mode, it is dim! It will take a little getting used to.
It's a very good addition to the firmware.
--Al
WD4AH
|
Hi Hans, Am 23.11.22 um 15:13 schrieb Hans Summers: 3. Add "Night mode" parameter to configuration screen - when enabled, it makes panel LED very dim, by defining the GPIO pin with internal pullup to light the LED. It's dim but if the QDX is on a shelf in front of you and not in too bright lighting, it will be visible. Does "Night mode" work with a Rev. 3 PCB as well? Vy 73 Stefan. -- Stefan U. Hegner <db4st@...> * * * DB4ST --- German Ham Radio Station D-32584 L?hne ----- Locator JO42IE * * * GPG-Key | C3CC 23A4 FBA8 622B 48AE F-Print | 4F19 D0EE E39E ABDC 2BCE
|
On Wed, Nov 23, 2022 at 12:16 PM, Hans Summers wrote:
How about the pulsating sinewave brightness 1Hz LED flash during transmit...
With night mode and lower LED brightness I think blinking is better than pulsating. BUT, in "day" mode or full brightness, pulsating works better for me.
Blinking grabs your attention. Pulsation is more relaxed. Unfortunately there' now clear winner here.
--Al
?
?
|
Hello Stefan
Night mode and all other changes in 1_06 work on all PCB revisions.?
On Wed, Nov 23, 2022 at 9:11 PM Stefan U. Hegner < db4st@...> wrote: Hi Hans,
Am 23.11.22 um 15:13 schrieb Hans Summers:
> 3. Add "Night mode" parameter to configuration screen - when enabled,
> it makes panel LED very dim, by defining the GPIO pin with internal
> pullup to light the LED. It's dim but if the QDX is on a shelf in
> front of you and not in too bright lighting, it will be visible.
Does "Night mode" work with a Rev. 3 PCB as well?
Vy 73
Stefan.
--
Stefan U. Hegner? ? <db4st@...>
? ? ? ? ? ? ? ?* * *
DB4ST --- German Ham Radio Station
D-32584 L?hne ----- Locator JO42IE
? ? ? ? ? ? ? ?* * *
GPG-Key | C3CC 23A4 FBA8 622B 48AE
F-Print | 4F19 D0EE E39E ABDC 2BCE
|
Will load the blob on Friday and give it a whirl.? Thanks Hans!? Looking forward to 2200 m also.? We have a specific application for that on Rx here in the US outside of Ham radio.
|
Hello Cliff
> Any chance of enabling the Split and second VFO operations?
I am still far from convinced of the need for this, but I will enable it to keep the troops happy.?
Hans,
Any chance of enabling the Split and second VFO operations?
Hi all
Here you can find a version 1_06_004 beta:
The version contains the following changes: - When bias mA is 5mA, disable PIN diode forward bias SMPS system completely (results in around 4mA default bias current).
- Change default 80m Frequency min to 3200000.
- Add "Night mode" parameter to configuration screen - when enabled, it makes panel LED very dim, by defining the GPIO pin with internal pullup to light the LED. It's dim but if the QDX is on a shelf in front of you and not in too bright lighting, it will be visible.
- Now successful TX is a 1Hz pulsating indication, the LED current actually follows a 1Hz sinewave; meanwhile the spacing between the 2 blinks in "audio insufficient" error reporting mode is now 0.2 seconds, wider spaced for easier counting
- Changed minimum TX freq from 300kHz to 75kHz (to allow 2200m operation). Note: receive quadrature for 2200m is not done yet.?
- Changed length of band name in the Band Config screen to 4 digits (to allow 2200m operation)
- Bug fix: Qn; CAT command return string length is now longer to fit larger numbers
|
?
Split (mode THANKS) works very well when the fox calls? "CQ UP 1"? (1 kHz for example) keeps the pileup off the fox so all hounds (troops :>) can hear the fox
72 73
John
N3AAZ
|
On 24/11/2022 11:51, John Kirby wrote: Split (mode THANKS) works very well when the fox calls? "CQ UP 1"? (1 kHz for example) John, According to the manual WSJT-X has two ways of working split without the radio contributing. Basic no split changes the audio frequency, not always ideal, but "Fake it" tunes the radio. 73 Alan G4ZFQ
|
Alan,
For Wsjtx, yet it isn't needed. Not all people live in FT8 land either.
73,
Cliff, AE5ZA
toggle quoted message
Show quoted text
On Nov 24, 2022, at 06:07, Alan G4ZFQ <alan4alan@...> wrote:
On 24/11/2022 11:51, John Kirby wrote:
Split (mode THANKS) works very well when the fox calls "CQ UP 1" (1 kHz for example) John,
According to the manual WSJT-X has two ways of working split without the radio contributing. Basic no split changes the audio frequency, not always ideal, but "Fake it" tunes the radio.
73 Alan G4ZFQ
|
Thank you very much Hans. I really appreciate it.?
toggle quoted message
Show quoted text
Hello Cliff
> Any chance of enabling the Split and second VFO operations?
I am still far from convinced of the need for this, but I will enable it to keep the troops happy.? Hans,
Any chance of enabling the Split and second VFO operations?
Hi all
Here you can find a version 1_06_004 beta:
The version contains the following changes: - When bias mA is 5mA, disable PIN diode forward bias SMPS system completely (results in around 4mA default bias current).
- Change default 80m Frequency min to 3200000.
- Add "Night mode" parameter to configuration screen - when enabled, it makes panel LED very dim, by defining the GPIO pin with internal pullup to light the LED. It's dim but if the QDX is on a shelf in front of you and not in too bright lighting, it will be visible.
- Now successful TX is a 1Hz pulsating indication, the LED current actually follows a 1Hz sinewave; meanwhile the spacing between the 2 blinks in "audio insufficient" error reporting mode is now 0.2 seconds, wider spaced for easier counting
- Changed minimum TX freq from 300kHz to 75kHz (to allow 2200m operation). Note: receive quadrature for 2200m is not done yet.?
- Changed length of band name in the Band Config screen to 4 digits (to allow 2200m operation)
- Bug fix: Qn; CAT command return string length is now longer to fit larger numbers
|
Hans,
Your the Best!?
A nice surprise to explore for the QDX.
Thanks?
James
|
Anyone using QDX on Top Band ?
72,
Bill, N4QA
|
On 24/11/2022 13:27, Cliff wrote: For Wsjtx, yet it isn't needed. Not all people live in FT8 land either. Cliff, Perhaps I should have asked Hans why he seemed reluctant to add split/extra VFO. I must be missing something. Or, why do you think it is necessary? 73 Alan G4ZFQ
|
?re SPLIT es 'fox-s'
Lack of articulation on my part
????? the WSJT-X fox ; >(? I've??'never' been there
I should have said?
?? ...when the ((CW)) fox calls? "CQ UP 1...
Which implies he is running split
CW tip ...
A wise ole fox starts from the top of the pileup es works down
73 73
John
N3AAZ
|
Alan,
Hans will have to answer that question himself. I can guess, but I don't want to put words in his mouth.
Is it critical to using the QDX, no. Is it necessary, it depends on what you are doing with it. Is it useful, yes, at least for some of us. Many hams never use it, either because they never do anything that requires it or they don't know how to use it.
I use fldigi a lot and having the ease to switch VFOs is handy. Any contest or DX Exhibitions usually run split. It is far easier to set the TX freq in one VFO and the RX in the other and have the rig switch automatically by using the split function for transmitting. One can emulate that depending on how wide the freq. split is with built in fldigi functions, but again operating split just makes life so much easier. Is it used a lot, no, but when needed is very useful. BTW, the Wsjtx docs recommend using it if the rig supports it so for them it maybe means less stuff to do to "fake it", I don't know their reasons.
73,
Cliff, AE5ZA
toggle quoted message
Show quoted text
On Nov 24, 2022, at 09:06, Alan G4ZFQ <alan4alan@...> wrote:
On 24/11/2022 13:27, Cliff wrote:
For Wsjtx, yet it isn't needed. Not all people live in FT8 land either. Cliff,
Perhaps I should have asked Hans why he seemed reluctant to add split/extra VFO.
I must be missing something.
Or, why do you think it is necessary?
73 Alan G4ZFQ
|
On 24 Nov 2022 at 3:43, John Kirby wrote: Split (mode THANKS) works very well
when the fox calls? "CQ UP 1"? (1 kHz
for example) keeps the pileup off
the fox so all can hear the fox in Fox mode, the fox will simply NOT respond to calls below 1000Hz offset ... when the fox responds to you, the sw changes YOUR offset audio to the channel 'your fox' is on... this should be done IN the software [WSJT-X] in 'fake it' mode. OR the sw will send a CAT command to the tx to change freq in 'split' mode. w2jc
|
On Thu, Nov 24, 2022 at 01:27 PM, Cliff wrote:
Not all people live in FT8 land either.
Thanks Christ for that !!! FT8'ers are nothing more than shoot 'em gamers wreaking RF anarchy on the rest of us.. ? -- - 73 de Andy -
|
Mitch Winkle
KB9NBL