¿ªÔÆÌåÓý

ctrl + shift + ? for shortcuts
© 2025 Groups.io

QDX firmware 1_06_004 beta


 

On 25 Nov 2022 at 13:51, Da Amazin' man G0FTD via
groups.io wrote:

FT8'ers are nothing more than shoot
'em gamers wreaking RF anarchy on the
rest of us..
yup, 3kHz for 100 simultaneous contacts vs
3kHz for ONE ssb contact is really wrecking
anarchy on the entire rf spectrum.

Doesn't seem like this particular talk group
is very appropriate for attitudes like that.

w2jc


 

On 26 Nov 2022 at 2:57, Andy [FTD] wrote:

Regardless of bandwidth, they still shit all over the band.
It's still just a fucking video game to them.
your language is offensive... there is no reason for it with
someone you don't even know...

THIS IS A HOBBY with many many facets of interest...
if a particular operator is acting badly, complain to them but
don't blame the whole group.

I really don't see how a single user with channel width of
60Hz can be very offensive to any other users -- unless
maybe you don't know how to notch out a signal.

QRT from here now. Clean up your language.


 

Jim:

Probably more offensive than specific words is folks who feel the need to enforce their own brand of morality. Go ahead and cuss. We are big boys and girls.

BTW god is fiction.

OK?

Ward Merdes - KL7IXW
Fairbanks, Alaska

On Fri, Nov 25, 2022 at 6:15 PM Jim W2JC <io@...> wrote:
On 26 Nov 2022 at 2:57, Andy [FTD] wrote:

> Regardless of bandwidth, they still shit all over the band.

> It's still just a fucking video game to them.

your language is offensive... there is no reason for it with
someone you don't even know...

THIS IS A HOBBY with many many facets of interest...
if a particular operator is acting badly, complain to them but
don't blame the whole group.

I really don't see how a single user with channel width of
60Hz can be very offensive to any other users -- unless
maybe you don't know how to notch out a signal.

QRT from here now.? Clean up your language.








 

Maybe W2JC should keep PMs as PMs, rather than switching to cc'ing midstream.

--
- 73 de Andy -


 

¿ªÔÆÌåÓý

Ward,

Well, to me the big boys and girls are the ones that have learned to use proper language to express themselves and have no need of cussing.

BTW, You'll know for sure when you take your last breath if God is fiction or not, won't you.

73,
Cliff, AE5ZA

On Nov 25, 2022, at 23:28, Ward Merdes <W.merdes@...> wrote:

Jim:

Probably more offensive than specific words is folks who feel the need to enforce their own brand of morality. Go ahead and cuss. We are big boys and girls.

BTW god is fiction.

OK?

Ward Merdes - KL7IXW
Fairbanks, Alaska

On Fri, Nov 25, 2022 at 6:15 PM Jim W2JC <io@...> wrote:
On 26 Nov 2022 at 2:57, Andy [FTD] wrote:

> Regardless of bandwidth, they still shit all over the band.

> It's still just a fucking video game to them.

your language is offensive... there is no reason for it with?
someone you don't even know...

THIS IS A HOBBY with many many facets of interest...
if a particular operator is acting badly, complain to them but
don't blame the whole group.

I really don't see how a single user with channel width of?
60Hz can be very offensive to any other users -- unless
maybe you don't know how to notch out a signal.

QRT from here now.? Clean up your language.









 

FWIW, I have degrees in both journalism AND English literature, and I
know when to use foul language. I've also earned the right to do so,
after too many decades writing non-fiction and fiction.

I won't support an unconditional ban on using foul language here, but
I unconditionally support its use when and IF it's appropriate. Which
around here is darned rarely, probably almost never.

Oh yeah -- I have an off-list story about one group where unseemly
language or discussion of adult tobes was absolutely banned, because
children under 14 might happen to see it at home. You'd need to hear
page 2 of the story....

73
Jim N6OTQ

On Sat, Nov 26, 2022 at 8:27 AM Cliff <ae5zaham@...> wrote:

Well, to me the big boys and girls are the ones that have learned to use proper language to express themselves and have no need of cussing.


 

All seems to be working ok for me with 1.06 (newest hardware to date).?

3. Night Mode is welcomed, thank you.
4. Is much easier to quickly verify good TX.? Very nice.??

7. I had worked around the include NULL's, but I'll back that out and test it again.


 

Hi all

I enabled?Split mode in firmware 1_06_006 and it works the same way as on QCX radios. When in Split mode, reception is on VFO A, and transmission is on VFO B.?

Beta?

You can enter split mode by any of the CAT commands:

SP1;
FR2;
FT2;

Please?let me know if this is OK.?

73 Hans G0UPL



On Sat, Nov 26, 2022 at 6:43 PM Mitch Winkle <ab4mw@...> wrote:
All seems to be working ok for me with 1.06 (newest hardware to date).?

3. Night Mode is welcomed, thank you.
4. Is much easier to quickly verify good TX.? Very nice.??

7. I had worked around the include NULL's, but I'll back that out and test it again.


 

¿ªÔÆÌåÓý

Hans,

Thank you very much. Works like it should. Wsjtx requires VFOA to be receive and then with split selected in the setup it turns on split and uses VFOB for transmit.

Using other software like fldigi it also will use VFOB as receive and VFOA for transmitting as it should.?

Very nice and thanks again.

73,
Cliff, AE5ZA

On Nov 30, 2022, at 11:30, Hans Summers <hans.summers@...> wrote:

Hi all

I enabled?Split mode in firmware 1_06_006 and it works the same way as on QCX radios. When in Split mode, reception is on VFO A, and transmission is on VFO B.?

Beta?

You can enter split mode by any of the CAT commands:

SP1;
FR2;
FT2;

Please?let me know if this is OK.?

73 Hans G0UPL



On Sat, Nov 26, 2022 at 6:43 PM Mitch Winkle <ab4mw@...> wrote:
All seems to be working ok for me with 1.06 (newest hardware to date).?

3. Night Mode is welcomed, thank you.
4. Is much easier to quickly verify good TX.? Very nice.??

7. I had worked around the include NULL's, but I'll back that out and test it again.




 

¿ªÔÆÌåÓý

Hans,

One glitch in the new firmware, 006 and 007 is that Transmit on 60M is about 1450 hz low. Firmware 1_05 works fine, but the 1_06_006 and 007 transmit 1450 hz low. Strange that only this one band has an issue, but I've verified it with receiving on a separate receiver.

73,
Cliff, AE5ZA

On Nov 30, 2022, at 20:59, Cliff <ae5zaham@...> wrote:

Hans,

Thank you very much. Works like it should. Wsjtx requires VFOA to be receive and then with split selected in the setup it turns on split and uses VFOB for transmit.

Using other software like fldigi it also will use VFOB as receive and VFOA for transmitting as it should.?

Very nice and thanks again.

73,
Cliff, AE5ZA

On Nov 30, 2022, at 11:30, Hans Summers <hans.summers@...> wrote:

Hi all

I enabled?Split mode in firmware 1_06_006 and it works the same way as on QCX radios. When in Split mode, reception is on VFO A, and transmission is on VFO B.?

Beta?

You can enter split mode by any of the CAT commands:

SP1;
FR2;
FT2;

Please?let me know if this is OK.?

73 Hans G0UPL



On Sat, Nov 26, 2022 at 6:43 PM Mitch Winkle <ab4mw@...> wrote:
All seems to be working ok for me with 1.06 (newest hardware to date).?

3. Night Mode is welcomed, thank you.
4. Is much easier to quickly verify good TX.? Very nice.??

7. I had worked around the include NULL's, but I'll back that out and test it again.





 

Hello Cliff

> One glitch in the new firmware, 006 and 007 is that Transmit on?60M?is?
> about 1450 hz low. Firmware 1_05 works fine, but the 1_06_006 and 007?
> transmit 1450 hz low. Strange that only this one band has an issue,?
> but I've verified it with receiving on a separate receiver.

Very strange... please could you let me know, exactly what USB Dial frequency, and what audio offset frequency, you are using? And is it WSJT-X for example by pressing the "Tune" button, or some other way? Then I can try to reproduce it here.?

73 Hans G0UPL



On Thu, Dec 1, 2022 at 6:36 PM Cliff <ae5zaham@...> wrote:
Hans,

One glitch in the new firmware, 006 and 007 is that Transmit on 60M is about 1450 hz low. Firmware 1_05 works fine, but the 1_06_006 and 007 transmit 1450 hz low. Strange that only this one band has an issue, but I've verified it with receiving on a separate receiver.

73,
Cliff, AE5ZA

On Nov 30, 2022, at 20:59, Cliff <ae5zaham@...> wrote:

Hans,

Thank you very much. Works like it should. Wsjtx requires VFOA to be receive and then with split selected in the setup it turns on split and uses VFOB for transmit.

Using other software like fldigi it also will use VFOB as receive and VFOA for transmitting as it should.?

Very nice and thanks again.

73,
Cliff, AE5ZA

On Nov 30, 2022, at 11:30, Hans Summers <hans.summers@...> wrote:

Hi all

I enabled?Split mode in firmware 1_06_006 and it works the same way as on QCX radios. When in Split mode, reception is on VFO A, and transmission is on VFO B.?

Beta?

You can enter split mode by any of the CAT commands:

SP1;
FR2;
FT2;

Please?let me know if this is OK.?

73 Hans G0UPL



On Sat, Nov 26, 2022 at 6:43 PM Mitch Winkle <ab4mw@...> wrote:
All seems to be working ok for me with 1.06 (newest hardware to date).?

3. Night Mode is welcomed, thank you.
4. Is much easier to quickly verify good TX.? Very nice.??

7. I had worked around the include NULL's, but I'll back that out and test it again.





 

On 02/12/2022 12:26, Hans Summers wrote:
Very strange... please could you let me know, exactly what USB Dial frequency, and what audio offset frequency, you are using?
Hans

I've only just put v1_06_005 on one of my V1 QDXs.
On 5.364700 it transmits almost exactly on 5.366282 as expected. (Needs a few Hz tweak on the calibration.)

Further tests to follow..

73 Alan G4ZFQ


 

¿ªÔÆÌåÓý

Hi Hans,

I realize it is very strange and I thought so as well. Actually I didn't discover this, but a good friend of mine alerted me to it and asked me to verify it. My test setup was Tx on the QDX to a dummy load and receive on my IC7300. The waterfall on the 7300 display makes it very easy to see the location of a received freq.

QDX is a Rev 4 and the freq. was 5357.000 kHz USB. Waterfall offset is 1500 hz. I am using fldigi to test and its Tune function. My friend who alerted me to the issue was using Wsjtx and noted that with the new firmware he was not making any 60M contacts, but reverting to the older firmware he was successful in making contacts.

Testing with firmware 1_06_007 on any of the other bands showed the Tx freq exactly centered on the 7300 display, but ?on 60M it was low by 1450 hz which I thought also was strange. I could see 1500, but 1450? I tested multiple times to verify. Reverting to firmware 1_05 corrected the problem with no changes to the test setup.

73,
Cliff, AE5ZA

On Dec 2, 2022, at 06:26, Hans Summers <hans.summers@...> wrote:

Hello Cliff

> One glitch in the new firmware, 006 and 007 is that Transmit on?60M?is?
> about 1450 hz low. Firmware 1_05 works fine, but the 1_06_006 and 007?
> transmit 1450 hz low. Strange that only this one band has an issue,?
> but I've verified it with receiving on a separate receiver.

Very strange... please could you let me know, exactly what USB Dial frequency, and what audio offset frequency, you are using? And is it WSJT-X for example by pressing the "Tune" button, or some other way? Then I can try to reproduce it here.?

73 Hans G0UPL



On Thu, Dec 1, 2022 at 6:36 PM Cliff <ae5zaham@...> wrote:
Hans,

One glitch in the new firmware, 006 and 007 is that Transmit on 60M is about 1450 hz low. Firmware 1_05 works fine, but the 1_06_006 and 007 transmit 1450 hz low. Strange that only this one band has an issue, but I've verified it with receiving on a separate receiver.

73,
Cliff, AE5ZA

On Nov 30, 2022, at 20:59, Cliff <ae5zaham@...> wrote:

Hans,

Thank you very much. Works like it should. Wsjtx requires VFOA to be receive and then with split selected in the setup it turns on split and uses VFOB for transmit.

Using other software like fldigi it also will use VFOB as receive and VFOA for transmitting as it should.?

Very nice and thanks again.

73,
Cliff, AE5ZA

On Nov 30, 2022, at 11:30, Hans Summers <hans.summers@...> wrote:

Hi all

I enabled?Split mode in firmware 1_06_006 and it works the same way as on QCX radios. When in Split mode, reception is on VFO A, and transmission is on VFO B.?

Beta?

You can enter split mode by any of the CAT commands:

SP1;
FR2;
FT2;

Please?let me know if this is OK.?

73 Hans G0UPL



On Sat, Nov 26, 2022 at 6:43 PM Mitch Winkle <ab4mw@...> wrote:
All seems to be working ok for me with 1.06 (newest hardware to date).??

3. Night Mode is welcomed, thank you.
4. Is much easier to quickly verify good TX.? Very nice.??

7. I had worked around the include NULL's, but I'll back that out and test it again.








 

On 02/12/2022 12:40, Alan G4ZFQ via groups.io wrote:
I've only just put v1_06_005 on one of my V1 QDXs.
Hans,

I missed v 1_06_006, tried that. (is 007 anywhere?)

A quick check shows correct transmit frequencies on the two WSPR frequencies on the WSPRnet site. 5.287200, 5.364700

BUT as Cliff says on 5.357000 USB it receives correctly but transmits 1375Hz low. +/- a few Hz.

73 Alan G4ZFQ


 

On 03/12/2022 12:27, Alan G4ZFQ via groups.io wrote:
but transmits 1375Hz low.
With an audio frequency of 1500Hz


 

My v3 with 1_6_7 at 5357 transmits on 5357.15.?
Change in Audio frequency? doesn't change the rf frequency. Also no modulation, just a steady carrier. If I change the rf freq to 5358 the rf follows the audio as should be.
73 Ton PA0ARR?


 

On 03/12/2022 16:00, Ton - PA0ARR wrote:
My v3 with 1_6_7 at 5357 transmits on 5357.15.
Change in Audio frequency? doesn't change the rf frequency. Also no modulation, just a steady carrier. If I change the rf freq to 5358 the rf follows the audio as should be.
Ton,

A v1 with 1_06_006 does the same.
I used the Terminal VOX and CAT. Fed the QDX with audio 100Hx-2.5KHz. from software.

At 5.357000 I think there is some change with audio frequency but not much.

At 5.358000 all good.
At 5356000 maximum of 1000Hz then no corresponding increase in frequency.
At 5.356500 maximum of 500Hz then no increase.

I saw Hans chose 5.357000 as the centre frequency in the band table but changing those values made no difference.

73 Alan G4ZFQ