wsjt-devel — WSJT software development

Re: [wsjt-devel] Power Out Issue

[FRANCIS P. SR. <mvp...@co...>]

Menu 017 is TX Out Level. Data Mic Gain is 077 and is currently set at 50. I'm using a SignalLink USB.
The pwr slider on the far right as example if I bring it down to -35db brings my power out to 15 Watts. So I'm under the assumption my problem is solved. Thank you! It's been a few months since I used it.

> On 01/25/2025 9:32 PM EST Reino Talarmo via wsjt-devel <wsj...@li...> wrote:
>  
>  
> 
> Frank,
> 
> Clearly your audio settings require some tuning; there is now an excessive level. Is it a typo, when you refer to menu 017 as that is for Voice memory; the data MIC gain is menu 077?
> 
> What happens when you use wsjt-x Pwr slider on the right hand? Does it start to lower output power at some value. It should as the control range is 40 dB or so.
> 
> How is your audio connected between PC and FTdx1200. Are you using SCU-17?
> 
>  
> 
> 73, Reino OH3mA
> 
>  
> 
> From: FRANCIS PIETLOCK SR. via wsjt-devel <wsj...@li...>
> Sent: Sunday, January 26, 2025 12:23 AM
> To: wsj...@li...
> Cc: FRANCIS PIETLOCK SR. <mvp...@co...>
> Subject: [wsjt-devel] Power Out Issue
> 
>  
> 
> I'm running WSIT-X 2,7,0 RC1 on a Yaesu FT dx 1200.
> 
>  
> 
> I can't seem to get my output lower than 100 watts out on FT8
> 
> Menu 017 reads 57 now. I've lowered it 20 digits & increased it 20 without any changes.
> 
> FYI.. I only use this rig for FT8 and haven't used it in a while and don't recall how to do it.
> 
>  
> 
> Frank WA1UYM
> 
> _______________________________________________
> wsjt-devel mailing list
> wsj...@li...
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
> 

Re: [wsjt-devel] Power Out Issue

[Reino T. <rei...@ko...>]

Frank,

Clearly your audio settings require some tuning; there is now an excessive level. Is it a typo, when you refer to menu 017 as that is for Voice memory; the data MIC gain is menu 077? 

What happens when you use wsjt-x Pwr slider on the right hand? Does it start to lower output power at some value. It should as the control range is 40 dB or so.

How is your audio connected between PC and FTdx1200. Are you using SCU-17?

 

73, Reino OH3mA

 

From: FRANCIS PIETLOCK SR. via wsjt-devel <wsj...@li...> 
Sent: Sunday, January 26, 2025 12:23 AM
To: wsj...@li...
Cc: FRANCIS PIETLOCK SR. <mvp...@co...>
Subject: [wsjt-devel] Power Out Issue

 

I'm running WSIT-X 2,7,0 RC1 on a Yaesu FT dx 1200. 

  

I can't seem to get my output lower than 100 watts out on FT8 

Menu 017 reads 57 now. I've lowered it 20 digits & increased it 20 without any changes. 

FYI.. I only use this rig for FT8 and haven't used it in a while and don't recall how to do it. 

  

Frank WA1UYM 

[wsjt-devel] Power Out Issue

[FRANCIS P. SR. <mvp...@co...>]

I'm running WSIT-X 2,7,0 RC1 on a Yaesu FT dx 1200.
 
I can't seem to get my output lower than 100 watts out on FT8
Menu 017 reads 57 now. I've lowered it 20 digits & increased it 20 without any changes.
FYI.. I only use this rig for FT8 and haven't used it in a while and don't recall how to do it.
 
Frank WA1UYM

[wsjt-devel] #RFI Using USB optical cable

[Black M. <mdb...@ya...>]

In my current setup there is an IC-7300 that has been unable to transmit even 1W without dropping the USB connection.  I have numerous rigs hooked up and lots of USB connections.  The 7300 is well known for being RFI sensitive dropping CAT and Audio service.
So I bought an optical USB cable, plugged it into a non-powered Startech hub, then ran a triplite cable to the rig.  Now able to run full power without any problems.I'll be doing more investigation with a cheaper hub and adding more USB devices to this new hub.  But the optical cable has a USB-B on one end and USB-A on the other.   So do need a USB hub that takes a USB-B cable.
Not a cheap solution but effective.
https://www.amazon.com/dp/B01N94D03Ehttps://www.amazon.com/StarTech-com-Mountable-Rugged-Industrial-Port/dp/B003AVPUZG/ref=sr_1_8?s=electronics&sr=1-8
Mike W9MDB

Re: [wsjt-devel] First build with TCI ready for testing

[Charles S. <g3...@gm...>]

Hi Gerrie

Uwe just released a new test version of -improved which incorporates the TX
shift feature. I have developed it significantly since we were last in
contact.

73

Charlie

---------- Forwarded message ---------
From: Uwe, DG2YCB via wsjt-devel <wsj...@li...>
Date: Fri, 24 Jan 2025 at 11:49
Subject: [wsjt-devel] First build with TCI ready for testing
To: WSJT software development <wsj...@li...>
Cc: Uwe, DG2YCB <dg...@gm...>


Hi all,

I am glad to announce that a first build of WSJT-X Improved with TCI is
ready for testing!

For those who don't know: TCI – Transceiver Control Interface is a network
interface for control, data transfer and synchronization between a
transceiver/receiver, logger, digital software, skimmer, other software and
external power amplifier, band filters, antenna switch, radio station
controller and other devices.

You can find more information in my following post in our WSJT GROUP forum:
https://groups.io/g/wsjtgroup/topic/first_wsjt_x_improved_build/110788103

73 de Uwe, DG2YCB
_______________________________________________
wsjt-devel mailing list
wsj...@li...
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

[wsjt-devel] First build with TCI ready for testing

[Uwe, D. <dg...@gm...>]

Hi all,

I am glad to announce that a first build of WSJT-X Improved with TCI is
ready for testing!

For those who don't know: TCI – Transceiver Control Interface is a
network interface for control, data transfer and synchronization between
a transceiver/receiver, logger, digital software, skimmer, other
software and external power amplifier, band filters, antenna switch,
radio station controller and other devices.

You can find more information in my following post in our WSJT GROUP
forum:
https://groups.io/g/wsjtgroup/topic/first_wsjt_x_improved_build/110788103

73 de Uwe, DG2YCB

Re: [wsjt-devel] Rigs in use #Cat_RigControl

[<al...@al...>]

I agree it's not for the developers to parse the information, it's for 
the station operator.  Privacy is an individual choice and shouldn't be 
dictated.

Rather than a none or everything choice surely it then shouldn't be hard 
to add some checkboxes so users can select what gets published or not?  
That way everyone is happy for what should be relatively minor work to 
implement.

(I should say that I'm not bothered for myself but then I don't own a 
$kkkk top of the range rig that I'd rather not publicise to potential 
miscreants...)

Alan G0TLK



On 18/01/2025 13:45, Hasan N0AN via wsjt-devel wrote:
> Mike,
> That makes sense: if you don't want to publish your private 
> information, then don't enable pskreporting. That is totally in the 
> station operator's control, is it not?
>
> To expect the developers to parse which information should be sent to 
> pskreporter is unrealistic.
>
> Most spots already include (in addition to location information), 
> antenna info and software identification, where's the harm in 
> including Rig/Radio?  If one doesn't want that info public, then don't 
> PUBLISH it.
>
> I don't know what is planned for the future, but it 
> certainly shouldn't be any big secret (such as power output). As far 
> as ham radio is concerned what must be kept private and why? (since 
> the above info is already being revealed).  Where does one draw the line?
>
> I think your solution is the simplest: if you don't want to share your 
> information, (which already includes your rough location, and software 
> you are running, and your Callsign (therefore your Name, etc.)), then 
> don't enable PSKReporter.
>
> I'm not sure, but I don't think PSKreporter is uploaded by default, 
> you have to choose to upload...I think. If that's not the case, I 
> would respond to those who are concerned about privacy by making the 
> next iteration of WSJT-X default to NOT upload to PSKReporter.
>
> 73, N0AN
>
> Hasan
>
>
> On Sat, Jan 18, 2025 at 6:51 AM Black Michael via wsjt-devel 
> <wsj...@li...> wrote:
>
>     That's what the pskreporter checkbox is for.
>
>     Mike W9MDB
>
>
>
>
>
>
>
>
>     On Saturday, January 18, 2025 at 05:28:19 AM CST, alan2--- via
>     wsjt-devel <wsj...@li...> wrote:
>
>
>
>
>
>     As is UK.
>     Alan G0TLK
>
>
>     On 17/01/2025 20:21, Laurie, VK3AMA via wsjt-devel wrote:
>
>
>     > On 18/01/2025 3:27 am, Black Michael via wsjt-devel wrote:
>     >
>     >> That's all that Hamlib NET rigctl shows for now -- I plan on
>     putting more rig info in that entry as well as a couple of others.
>     >>
>     >> Mike W9MDB
>     >>
>     >>
>     >
>     > I suggest you put all this user specific information behind an
>     opt-in setting. This will keep you in compliance with the very
>     strict privacy regulations of many countries. EU as is VK, are
>     very strict with their data privacy restrictions.
>     >
>     > de Laurie VK3AMA
>     >
>     >
>     >
>     > _______________________________________________
>     > wsjt-devel mailing list
>     > wsj...@li...
>     > https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>     >
>
>
>     _______________________________________________
>     wsjt-devel mailing list
>     wsj...@li...
>     https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>
>
>     _______________________________________________
>     wsjt-devel mailing list
>     wsj...@li...
>     https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>
>
>
> _______________________________________________
> wsjt-devel mailing list
> wsj...@li...
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Rigs in use #Cat_RigControl

[Hasan N. <hba...@gm...>]

Mike,
That makes sense: if you don't want to publish your private information,
then don't enable pskreporting. That is totally in the station operator's
control, is it not?

To expect the developers to parse which information should be sent to
pskreporter is unrealistic.

Most spots already include (in addition to location information), antenna
info and software identification, where's the harm in including Rig/Radio?
If one doesn't want that info public, then don't PUBLISH it.

I don't know what is planned for the future, but it certainly shouldn't be
any big secret (such as power output). As far as ham radio is concerned
what must be kept private and why? (since the above info is already being
revealed).  Where does one draw the line?

I think your solution is the simplest: if you don't want to share your
information, (which already includes your rough location, and software you
are running, and your Callsign (therefore your Name, etc.)), then don't
enable PSKReporter.

I'm not sure, but I don't think PSKreporter is uploaded by default, you
have to choose to upload...I think. If that's not the case, I would respond
to those who are concerned about privacy by making the next iteration of
WSJT-X default to NOT upload to PSKReporter.

73, N0AN

Hasan


On Sat, Jan 18, 2025 at 6:51 AM Black Michael via wsjt-devel <
wsj...@li...> wrote:

> That's what the pskreporter checkbox is for.
>
> Mike W9MDB
>
>
>
>
>
>
>
>
> On Saturday, January 18, 2025 at 05:28:19 AM CST, alan2--- via wsjt-devel <
> wsj...@li...> wrote:
>
>
>
>
>
> As is UK.
> Alan G0TLK
>
>
> On 17/01/2025 20:21, Laurie, VK3AMA via wsjt-devel wrote:
>
>
> > On 18/01/2025 3:27 am, Black Michael via wsjt-devel wrote:
> >
> >> That's all that Hamlib NET rigctl shows for now -- I plan on putting
> more rig info in that entry as well as a couple of others.
> >>
> >> Mike W9MDB
> >>
> >>
> >
> > I suggest you put all this user specific information behind an opt-in
> setting. This will keep you in compliance with the very strict privacy
> regulations of many countries. EU as is VK, are very strict with their data
> privacy restrictions.
> >
> > de Laurie VK3AMA
> >
> >
> >
> > _______________________________________________
> > wsjt-devel mailing list
> > wsj...@li...
> > https://lists.sourceforge.net/lists/listinfo/wsjt-devel
> >
>
>
> _______________________________________________
> wsjt-devel mailing list
> wsj...@li...
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>
>
> _______________________________________________
> wsjt-devel mailing list
> wsj...@li...
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>

Re: [wsjt-devel] Rigs in use #Cat_RigControl

[Black M. <mdb...@ya...>]

That's what the pskreporter checkbox is for.

Mike W9MDB








On Saturday, January 18, 2025 at 05:28:19 AM CST, alan2--- via wsjt-devel <wsj...@li...> wrote: 





As is UK.
Alan G0TLK


On 17/01/2025 20:21, Laurie, VK3AMA via wsjt-devel wrote:


> On 18/01/2025 3:27 am, Black Michael via wsjt-devel wrote: 
> 
>> That's all that Hamlib NET rigctl shows for now -- I plan on putting more rig info in that entry as well as a couple of others. 
>> 
>> Mike W9MDB 
>> 
>> 
> 
> I suggest you put all this user specific information behind an opt-in setting. This will keep you in compliance with the very strict privacy regulations of many countries. EU as is VK, are very strict with their data privacy restrictions. 
> 
> de Laurie VK3AMA 
> 
> 
> 
> _______________________________________________ 
> wsjt-devel mailing list 
> wsj...@li... 
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel 
> 


_______________________________________________
wsjt-devel mailing list
wsj...@li...
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Rigs in use #Cat_RigControl

[<al...@al...>]

As is UK.

Alan G0TLK



On 17/01/2025 20:21, Laurie, VK3AMA via wsjt-devel wrote:
> On 18/01/2025 3:27 am, Black Michael via wsjt-devel wrote:
>> That's all that Hamlib NET rigctl shows for now -- I plan on putting 
>> more rig info in that entry as well as a couple of others.
>>
>> Mike W9MDB
>>
>
> I suggest you put all this user specific information behind an opt-in 
> setting. This will keep you in compliance with the very strict privacy 
> regulations of many countries. EU as is VK, are very strict with their 
> data privacy restrictions.
>
> de Laurie VK3AMA
>
>
>
> _______________________________________________
> wsjt-devel mailing list
> wsj...@li...
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Rigs in use #Cat_RigControl

[Laurie, V. <_vk...@vk...>]

On 18/01/2025 3:27 am, Black Michael via wsjt-devel wrote:
> That's all that Hamlib NET rigctl shows for now -- I plan on putting more rig info in that entry as well as a couple of others.
>
> Mike W9MDB
>

I suggest you put all this user specific information behind an opt-in 
setting. This will keep you in compliance with the very strict privacy 
regulations of many countries. EU as is VK, are very strict with their 
data privacy restrictions.

de Laurie VK3AMA

Re: [wsjt-devel] Rigs in use #Cat_RigControl

[Marco C. <PY...@ou...>]

Got it!

73 de PY1ZRJ


Il 17/01/25 13:27, Black Michael ha scritto:
> That's all that Hamlib NET rigctl shows for now -- I plan on putting more rig info in that entry as well as a couple of others.
>
> Mike W9MDB
>
>
>
>
>
>
>
>
> On Friday, January 17, 2025 at 10:18:25 AM CST, Marco Calistri via wsjt-devel <wsj...@li...> wrote:
>
>
>
>
>
> Hi Mike!
>
> Do I have to do something into my WSJT-X RC8?
>
> Or this function is already enabled so I can see my RTX into PSKREPORT?
>
> I see Rig: Hamlib here:
>
>
>
> Thank you!
>
> 73, de PY1ZRJ
>
> ---
> 73 de Marco, PY1ZRJ (former IK5BCU)
>
>
>
>
> Il 17/01/25 11:10, Black Michael via wsjt-devel ha scritto:
>
>
>>    Forgot the pskreporter link
>>
>> https://pskreporter.info/cgi-bin/pskstats.pl#equipment_in_use
>>
>> Mike W9MDB
>>
>>
>>
>>
>>
>>
>>
>>
>> On Friday, January 17, 2025 at 07:51:42 AM CST, Black Michael via wsjt-devel <wsj...@li...> wrote:
>>
>>
>>
>>
>>
>> PSKReporter, Hamlib, RC8 and recent WSJT-Improved have added reporting the rig choice to pskreporter when pskreporter is enabled.  This has several uses...
>>
>> #1 You can find other operators with your rig model to ask for help
>>
>> #2 We developers can also find such people as many do not belong to any of the email lists.
>>
>> #3 Can see what rigs appear to be "OK" with WSJTX so they can be promoted to stable in Hamlib.
>>
>> #4 Marketing -- Interesting to see the distribution of rigs...with the IC-7300 being far-and-away the most popular at 763 units (more then 50% of the Icom rigs) with the next most for the IC-7610 at 225 and then Flex at 208.
>>
>> Here's a current count as of 2025-01-17
>> https://www.dropbox.com/scl/fi/006tlmw3h7bh3mvpha9to/PSKReporter_RIgs.pdf?rlkey=0p9uoh3pn59vezcq8jc1vjet4&dl=1
>>
>> Mike W9MDB
>>
>>
>>
>>
>
> ---
> 73 de Marco, PY1ZRJ (former IK5BCU)
>
>
> _______________________________________________
> wsjt-devel mailing list
> wsj...@li...
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Rigs in use #Cat_RigControl

[Black M. <mdb...@ya...>]

That's all that Hamlib NET rigctl shows for now -- I plan on putting more rig info in that entry as well as a couple of others.

Mike W9MDB








On Friday, January 17, 2025 at 10:18:25 AM CST, Marco Calistri via wsjt-devel <wsj...@li...> wrote: 





Hi Mike!

Do I have to do something into my WSJT-X RC8?

Or this function is already enabled so I can see my RTX into PSKREPORT?

I see Rig: Hamlib here:



Thank you!

73, de PY1ZRJ

---
73 de Marco, PY1ZRJ (former IK5BCU)




Il 17/01/25 11:10, Black Michael via wsjt-devel ha scritto:


>  Forgot the pskreporter link
> 
> https://pskreporter.info/cgi-bin/pskstats.pl#equipment_in_use
> 
> Mike W9MDB
> 
> 
> 
> 
> 
> 
> 
> 
> On Friday, January 17, 2025 at 07:51:42 AM CST, Black Michael via wsjt-devel <wsj...@li...> wrote: 
> 
> 
> 
> 
> 
> PSKReporter, Hamlib, RC8 and recent WSJT-Improved have added reporting the rig choice to pskreporter when pskreporter is enabled.  This has several uses...
> 
> #1 You can find other operators with your rig model to ask for help
> 
> #2 We developers can also find such people as many do not belong to any of the email lists.
> 
> #3 Can see what rigs appear to be "OK" with WSJTX so they can be promoted to stable in Hamlib.
> 
> #4 Marketing -- Interesting to see the distribution of rigs...with the IC-7300 being far-and-away the most popular at 763 units (more then 50% of the Icom rigs) with the next most for the IC-7610 at 225 and then Flex at 208.
> 
> Here's a current count as of 2025-01-17
> https://www.dropbox.com/scl/fi/006tlmw3h7bh3mvpha9to/PSKReporter_RIgs.pdf?rlkey=0p9uoh3pn59vezcq8jc1vjet4&dl=1
> 
> Mike W9MDB
> 
> 
> 
> 


---
73 de Marco, PY1ZRJ (former IK5BCU)


_______________________________________________
wsjt-devel mailing list
wsj...@li...
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Rigs in use #Cat_RigControl

[Marco C. <PY...@ou...>]

Hi Mike!

Do I have to do something into my WSJT-X RC8?

Or this function is already enabled so I can see my RTX into PSKREPORT?

I see Rig: Hamlib here:



Thank you!

73, de PY1ZRJ

---
*73 de Marco, PY1ZRJ (former IK5BCU)*
**


Il 17/01/25 11:10, Black Michael via wsjt-devel ha scritto:
> Forgot the pskreporter link
>
> https://pskreporter.info/cgi-bin/pskstats.pl#equipment_in_use
>
> Mike W9MDB
>
>
>
>
>
>
>
>
> On Friday, January 17, 2025 at 07:51:42 AM CST, Black Michael via wsjt-devel<wsj...@li...> wrote:
>
>
>
>
>
> PSKReporter, Hamlib, RC8 and recent WSJT-Improved have added reporting the rig choice to pskreporter when pskreporter is enabled.  This has several uses...
>
> #1 You can find other operators with your rig model to ask for help
>
> #2 We developers can also find such people as many do not belong to any of the email lists.
>
> #3 Can see what rigs appear to be "OK" with WSJTX so they can be promoted to stable in Hamlib.
>
> #4 Marketing -- Interesting to see the distribution of rigs...with the IC-7300 being far-and-away the most popular at 763 units (more then 50% of the Icom rigs) with the next most for the IC-7610 at 225 and then Flex at 208.
>
> Here's a current count as of 2025-01-17
> https://www.dropbox.com/scl/fi/006tlmw3h7bh3mvpha9to/PSKReporter_RIgs.pdf?rlkey=0p9uoh3pn59vezcq8jc1vjet4&dl=1
>
> Mike W9MDB
>
>

---
*73 de Marco, PY1ZRJ (former IK5BCU)*
**

Re: [wsjt-devel] Rigs in use #Cat_RigControl

[Marco C. <PY...@ou...>]

Hi Mike!

Do I have to do something into my WSJT-X RC8?

Or this function is already enabled so I can see my RTX into PSKREPORT?

Thank you!

73, de PY1ZRJ

---
*73 de Marco, PY1ZRJ (former IK5BCU)*
**


Il 17/01/25 11:10, Black Michael via wsjt-devel ha scritto:
> Forgot the pskreporter link
>
> https://pskreporter.info/cgi-bin/pskstats.pl#equipment_in_use
>
> Mike W9MDB
>
>
>
>
>
>
>
>
> On Friday, January 17, 2025 at 07:51:42 AM CST, Black Michael via wsjt-devel<wsj...@li...> wrote:
>
>
>
>
>
> PSKReporter, Hamlib, RC8 and recent WSJT-Improved have added reporting the rig choice to pskreporter when pskreporter is enabled.  This has several uses...
>
> #1 You can find other operators with your rig model to ask for help
>
> #2 We developers can also find such people as many do not belong to any of the email lists.
>
> #3 Can see what rigs appear to be "OK" with WSJTX so they can be promoted to stable in Hamlib.
>
> #4 Marketing -- Interesting to see the distribution of rigs...with the IC-7300 being far-and-away the most popular at 763 units (more then 50% of the Icom rigs) with the next most for the IC-7610 at 225 and then Flex at 208.
>
> Here's a current count as of 2025-01-17
> https://www.dropbox.com/scl/fi/006tlmw3h7bh3mvpha9to/PSKReporter_RIgs.pdf?rlkey=0p9uoh3pn59vezcq8jc1vjet4&dl=1
>
> Mike W9MDB
>
>

Re: [wsjt-devel] Rigs in use #Cat_RigControl

[Black M. <mdb...@ya...>]

Forgot the pskreporter link

https://pskreporter.info/cgi-bin/pskstats.pl#equipment_in_use

Mike W9MDB








On Friday, January 17, 2025 at 07:51:42 AM CST, Black Michael via wsjt-devel <wsj...@li...> wrote: 





PSKReporter, Hamlib, RC8 and recent WSJT-Improved have added reporting the rig choice to pskreporter when pskreporter is enabled.  This has several uses...

#1 You can find other operators with your rig model to ask for help

#2 We developers can also find such people as many do not belong to any of the email lists.

#3 Can see what rigs appear to be "OK" with WSJTX so they can be promoted to stable in Hamlib.

#4 Marketing -- Interesting to see the distribution of rigs...with the IC-7300 being far-and-away the most popular at 763 units (more then 50% of the Icom rigs) with the next most for the IC-7610 at 225 and then Flex at 208.

Here's a current count as of 2025-01-17
https://www.dropbox.com/scl/fi/006tlmw3h7bh3mvpha9to/PSKReporter_RIgs.pdf?rlkey=0p9uoh3pn59vezcq8jc1vjet4&dl=1

Mike W9MDB




_______________________________________________
wsjt-devel mailing list
wsj...@li...
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Rigs in use #Cat_RigControl

[Doug B. Sr. <dou...@gm...>]

Awesome feature.

On Fri, Jan 17, 2025, 8:53 AM Black Michael via wsjt-devel <
wsj...@li...> wrote:

> PSKReporter, Hamlib, RC8 and recent WSJT-Improved have added reporting the
> rig choice to pskreporter when pskreporter is enabled.  This has several
> uses...
>
> #1 You can find other operators with your rig model to ask for help
>
> #2 We developers can also find such people as many do not belong to any of
> the email lists.
>
> #3 Can see what rigs appear to be "OK" with WSJTX so they can be promoted
> to stable in Hamlib.
>
> #4 Marketing -- Interesting to see the distribution of rigs...with the
> IC-7300 being far-and-away the most popular at 763 units (more then 50% of
> the Icom rigs) with the next most for the IC-7610 at 225 and then Flex at
> 208.
>
> Here's a current count as of 2025-01-17
>
> https://www.dropbox.com/scl/fi/006tlmw3h7bh3mvpha9to/PSKReporter_RIgs.pdf?rlkey=0p9uoh3pn59vezcq8jc1vjet4&dl=1
>
> Mike W9MDB
>
>
>
>
> _______________________________________________
> wsjt-devel mailing list
> wsj...@li...
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>

[wsjt-devel] Rigs in use #Cat_RigControl

[Black M. <mdb...@ya...>]

PSKReporter, Hamlib, RC8 and recent WSJT-Improved have added reporting the rig choice to pskreporter when pskreporter is enabled.  This has several uses...

#1 You can find other operators with your rig model to ask for help

#2 We developers can also find such people as many do not belong to any of the email lists.

#3 Can see what rigs appear to be "OK" with WSJTX so they can be promoted to stable in Hamlib.

#4 Marketing -- Interesting to see the distribution of rigs...with the IC-7300 being far-and-away the most popular at 763 units (more then 50% of the Icom rigs) with the next most for the IC-7610 at 225 and then Flex at 208.

Here's a current count as of 2025-01-17
https://www.dropbox.com/scl/fi/006tlmw3h7bh3mvpha9to/PSKReporter_RIgs.pdf?rlkey=0p9uoh3pn59vezcq8jc1vjet4&dl=1

Mike W9MDB

Re: [wsjt-devel] RIT (Not Split) Please

[Don H. <don...@co...>]

      
  

 Tested on 2304/2320?
  
  
  
  
  
  
  

  
  
>   
> On Jan 16, 2025 at 1:45 AM,  <Charles Suckling via wsjt-devel (mailto:wsj...@li...)>  wrote:
>   
>   
>   
>   
> Hi Dwayne
>   
>
>   
> I have a modified version of WSJT-X 2.7.0 -rc8    running that does exactly that.     
>   
>
>   
> It has been tested on-air and works.
>   
>
>   
> 73
>   
>
>   
> Charlie DL3WDG
>   
>   
>   
>   
> On Thu, 16 Jan 2025 at 07:01, Dwayne Sinclair via wsjt-devel  <wsj...@li... (mailto:wsj...@li...)>  wrote:
>   
> >  That time of the year again and I apologize as this has been asked before. Can we get the option to RIT (don’t want to say Split) between TX and RX frequencies with and without Doppler control?
> >   
> >  Because of the upcoming band changes and miss alignment in both 23CM and 13CM to name two bands, it would be helpful to be able to control independent TX and RX. An example would be TX 1296.065 with CFOM while receiving 1298.065 with CFOM.
> >   
> >  The Doppler screen does show a line for TX frequency and RX frequency and today they are the same so it seems there were thoughts at doing this?
> >   
> >  Regards Dwayne AB6A
> >   
> >  _______________________________________________
> >  wsjt-devel mailing list
> >   wsj...@li... (mailto:wsj...@li...)
> >   https://lists.sourceforge.net/lists/listinfo/wsjt-devel
> >       
>   
>   
>
>  _______________________________________________ wsjt-devel mailing list wsj...@li... https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>   
  
  
     

Re: [wsjt-devel] RIT (Not Split) Please

[Don H. <don...@co...>]

      
  

 How do I get a copy of this modified version?
  
  
  
  
  
  
  

  
  
>   
> On Jan 16, 2025 at 1:45 AM,  <Charles Suckling via wsjt-devel (mailto:wsj...@li...)>  wrote:
>   
>   
>   
>   
> Hi Dwayne
>   
>
>   
> I have a modified version of WSJT-X 2.7.0 -rc8    running that does exactly that.     
>   
>
>   
> It has been tested on-air and works.
>   
>
>   
> 73
>   
>
>   
> Charlie DL3WDG
>   
>   
>   
>   
> On Thu, 16 Jan 2025 at 07:01, Dwayne Sinclair via wsjt-devel  <wsj...@li... (mailto:wsj...@li...)>  wrote:
>   
> >  That time of the year again and I apologize as this has been asked before. Can we get the option to RIT (don’t want to say Split) between TX and RX frequencies with and without Doppler control?
> >   
> >  Because of the upcoming band changes and miss alignment in both 23CM and 13CM to name two bands, it would be helpful to be able to control independent TX and RX. An example would be TX 1296.065 with CFOM while receiving 1298.065 with CFOM.
> >   
> >  The Doppler screen does show a line for TX frequency and RX frequency and today they are the same so it seems there were thoughts at doing this?
> >   
> >  Regards Dwayne AB6A
> >   
> >  _______________________________________________
> >  wsjt-devel mailing list
> >   wsj...@li... (mailto:wsj...@li...)
> >   https://lists.sourceforge.net/lists/listinfo/wsjt-devel
> >       
>   
>   
>
>  _______________________________________________ wsjt-devel mailing list wsj...@li... https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>   
  
  
     

Re: [wsjt-devel] RIT (Not Split) Please

[Dwayne S. <dwa...@me...>]

Awesome! Windows Only or source code changes allow me to comment on MacOS?

Regards Dwayne AB6A

> On Jan 15, 2025, at 10:42 PM, Charles Suckling via wsjt-devel <wsj...@li...> wrote:
> 
> Hi Dwayne
> 
> I have a modified version of WSJT-X 2.7.0 -rc8  running that does exactly that.  
> 
> It has been tested on-air and works.
> 
> 73
> 
> Charlie DL3WDG
> 
> On Thu, 16 Jan 2025 at 07:01, Dwayne Sinclair via wsjt-devel <wsj...@li... <mailto:wsj...@li...>> wrote:
>> That time of the year again and I apologize as this has been asked before. Can we get the option to RIT (don’t want to say Split) between TX and RX frequencies with and without Doppler control?
>> 
>> Because of the upcoming band changes and miss alignment in both 23CM and 13CM to name two bands, it would be helpful to be able to control independent TX and RX. An example would be TX 1296.065 with CFOM while receiving 1298.065 with CFOM.
>> 
>> The Doppler screen does show a line for TX frequency and RX frequency and today they are the same so it seems there were thoughts at doing this?
>> 
>> Regards Dwayne AB6A
>> 
>> _______________________________________________
>> wsjt-devel mailing list
>> wsj...@li... <mailto:wsj...@li...>
>> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
> _______________________________________________
> wsjt-devel mailing list
> wsj...@li...
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] RIT (Not Split) Please

[Charles S. <g3...@gm...>]

Hi Dwayne

I have a modified version of WSJT-X 2.7.0 -rc8  running that does exactly
that.

It has been tested on-air and works.

73

Charlie DL3WDG

On Thu, 16 Jan 2025 at 07:01, Dwayne Sinclair via wsjt-devel <
wsj...@li...> wrote:

> That time of the year again and I apologize as this has been asked before.
> Can we get the option to RIT (don’t want to say Split) between TX and RX
> frequencies with and without Doppler control?
>
> Because of the upcoming band changes and miss alignment in both 23CM and
> 13CM to name two bands, it would be helpful to be able to control
> independent TX and RX. An example would be TX 1296.065 with CFOM while
> receiving 1298.065 with CFOM.
>
> The Doppler screen does show a line for TX frequency and RX frequency and
> today they are the same so it seems there were thoughts at doing this?
>
> Regards Dwayne AB6A
>
> _______________________________________________
> wsjt-devel mailing list
> wsj...@li...
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>

[wsjt-devel] RIT (Not Split) Please

[Dwayne S. <dwa...@me...>]

That time of the year again and I apologize as this has been asked before. Can we get the option to RIT (don’t want to say Split) between TX and RX frequencies with and without Doppler control?

Because of the upcoming band changes and miss alignment in both 23CM and 13CM to name two bands, it would be helpful to be able to control independent TX and RX. An example would be TX 1296.065 with CFOM while receiving 1298.065 with CFOM.

The Doppler screen does show a line for TX frequency and RX frequency and today they are the same so it seems there were thoughts at doing this?

Regards Dwayne AB6A

Re: [wsjt-devel] Message Creator/QSY Monitor Request for feature

[Scott A. <aa5...@gm...>]

Thanks Uwe!


73,
Scott AA5AM

On Wed, Jan 15, 2025 at 4:56 AM Uwe, DG2YCB <dg...@gm...> wrote:

> Hi Scott,
>
> It might be a possibility, but as you have already said, DF is not
> specific to the caller. I will forward this to the developer of this
> feature though. So, if we display something like this in the QSY Monitor
> widget, then only as additional information.
>
> 73 de DG2YCB,
> Uwe
> ________________________________________
> German Amateur Radio Station DG2YCB
> Dr. Uwe Risse
> eMail: dg...@gm...
> Info: www.qrz.com/db/DG2YCB
>
>
>
>
> Am 15.01.2025 um 10:44 schrieb Scott Armstrong:
>
> Hi Uwe,
>
> I don't think you understand what I am proposing.
> I agree it would be nice if we could use the free form text message to
> convey that information but that is not an option.
>
> What I am proposing does not use the message payload.
>
> I'll try to show you with the following picture/text.  Follow the numbers.
>
> #1. W5ABC has a QSO with me.
> #2  AA5AM sends a QSY message to W5ABC and he receives it. Pop up window
> opens. Message appears in the QSY Monitor window.
>
>  Imagine a crowded band,  lots of signals. Who is the message from where
> do I point my antenna?
>
> Now for my proposal to determine who the message is from.
>
> #3 Take the DF of the received QSY Message.
> #4 Compare the DF of the QSY Message with the DF of previous decodes and
> try to match one or more that are within maybe +/- 2Hz.   ( DF QSY = DF QSO
> decode(s))
> #5  DFs match!  Oh. The message is from AA5AM.
> # 6. Add AA5AM  to the Pop up window and QSY monitor window.
>
>
> Thoughts?
>
> 73,
> Scott AA5AM
>
> [image: image.png]
>
> On Wed, Jan 15, 2025 at 2:31 AM Uwe, DG2YCB <dg...@gm...> wrote:
>
>> Hi Scott,
>>
>> I agree this would be useful, but unfortunately this is not possible for
>> technical reasons. We use normal freetext messages for the new message
>> system, and already make full use of the 13 characters available.
>>
>> 73 de DG2YCB,
>> Uwe
>> ________________________________________
>> German Amateur Radio Station DG2YCB
>> Dr. Uwe Risse
>> eMail: dg...@gm...
>> Info: www.qrz.com/db/DG2YCB
>>
>>
>>
>>
>> Am 15.01.2025 um 01:27 schrieb Scott Armstrong via wsjt-devel:
>>
>> Hey Guys,
>>
>> Small issue.   If I receive a QSY message from someone, I have no idea
>> who sent that message other than trying to track down the  station by his
>> DF and that is only good if he hasn't moved.
>> This will not work so well on a busy band in the heat of the contest.
>>
>> I could  blindly QSY to that band but in the case of a band with highly
>> directional antennas, where do I aim the antenna? Not as much of an issue
>> on the lower bands but could still be a problem.
>>
>> This is what I see displayed in the QSY monitor window. It doesn't even
>> show the DF the message came in at.
>>
>> [image: image.png]
>>
>>
>> I have a request,
>>
>> Can some functionality be added that will take the DF of the QSY message
>> and match that to the DF maybe within +/- a few Hz to other prior decodes,
>> pull the callsign of that station that sent the message and display that
>> callsign in the QSY monitor window?
>>
>> Thank you and 73,
>> Scott AA5AM
>>
>>
>> _______________________________________________
>> wsjt-devel mailing lis...@li...https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>>
>>
>>
>

Re: [wsjt-devel] Message Creator/QSY Monitor Request for feature

[Scott A. <aa5...@gm...>]

Hi Reino,


It is an imperfect solution for an imperfect world.
This proposal/solution is not  100% guaranteed to be accurate or work at
all.  However, in the absence of no other information it is better than
nothing.

As it is presented in the user guide the recipient should know the sender
from previous messages, whether your current QSO partner or DXpedition
station.

Where are you getting that from the user guide? There is nothing in the
user guide chapter 8 that I am currently looking at that mentions or
visually shows that an Op should know the sender from the previous message.
And if it does and I missed it, and it should be prefaced with "In a
perfect world".

The screen capture I provided was for representative purposes only. Had
that been a real QSO on a band with 1 signal, there would be no doubt where
the message came from.

You are implying that some other station, who may or may not have called
you earlier (but you have not answered), is sending that message to you,
aren’t you..

That could be one possibility

Another what if... a station sends a QSY request and after a few minutes
doesn't receive a response and sends another
or the first message that was sent was in error i.e. wrong band, mode or
both and a "corrected message gets sent.

One I am imagining is that the band is busy,  and I may be working  QSOs 1
after another and another QSO starts before I can send a QSY message. It
could be a minute or more before that message is sent. Now I also have to
find the previous call of the station I want to send a message to, and
repopulate the message box with the callsign and send the message.  The
message is now sent to the correct station but is  delayed. He may have had
other QSOs in the meantime so who did the message come from?

Another scenario I am thinking of and have no idea how the messages are
handled. What happens if 2 QSY requests come in from 2 stations during the
same sequence or two responses to a QSY request are received. I don't have
the ability to test this scenario.

I could probably come up with several more scenarios but the solution
proposed is going to be the same.

The DF is the only unique bit of data that could possibly identify the
sender. The DF  within a small window, can be correlated with the call of
the sender. I suggested a match based on the DF+/- a few Hz because not
everyone's signal is rock solid and may drift a Hz or two during a QSO.
Doppler could also cause a signal to shift.

There are already other services that present active stations’ callsigns on
the frequency scale.

Sorry, I don't understand what you mean by this statement.

73,
Scott AA5AM



On Wed, Jan 15, 2025, 9:13 AM Reino Talarmo via wsjt-devel <
wsj...@li...> wrote:

> Hi Scott,
>
> Interesting proposal to extend the Message System outside a QSO. As it is
> presented in the user guide the recipient should know the sender from
> previous messages, whether your current QSO partner or DXpedition station.
>
> You are implying that some other station, who may or may not have called
> you earlier (but you have not answered), is sending that message to you,
> aren’t you. That feature would require what you described, but still the
> sending station is identified only by the received frequency. The nature of
> the Message System is more or less broadcasting and only implied one to one.
>
> There are already other services that present active stations’ callsigns
> on the frequency scale.
>
>
>
> 73, Reino OH3mA
>
>
>
> *From:* Scott Armstrong via wsjt-devel <wsj...@li...>
> *Sent:* Wednesday, January 15, 2025 11:45 AM
> *To:* Uwe, DG2YCB <dg...@gm...>
> *Cc:* Scott Armstrong <aa5...@gm...>; WSJT software development <
> wsj...@li...>
> *Subject:* Re: [wsjt-devel] Message Creator/QSY Monitor Request for
> feature
>
>
>
> Hi Uwe,
>
> I don't think you understand what I am proposing.
> I agree it would be nice if we could use the free form text message to
> convey that information but that is not an option.
>
> What I am proposing does not use the message payload.
>
> I'll try to show you with the following picture/text.  Follow the numbers.
>
> #1. W5ABC has a QSO with me.
> #2  AA5AM sends a QSY message to W5ABC and he receives it. Pop up window
> opens. Message appears in the QSY Monitor window.
>
>  Imagine a crowded band,  lots of signals. Who is the message from where
> do I point my antenna?
>
> Now for my proposal to determine who the message is from.
>
> #3 Take the DF of the received QSY Message.
>
> #4 Compare the DF of the QSY Message with the DF of previous decodes and
> try to match one or more that are within maybe +/- 2Hz.   ( DF QSY = DF QSO
> decode(s))
> #5  DFs match!  Oh. The message is from AA5AM.
> # 6. Add AA5AM  to the Pop up window and QSY monitor window.
>
>
> Thoughts?
>
> 73,
>
> Scott AA5AM
>
>
>
> On Wed, Jan 15, 2025 at 2:31 AM Uwe, DG2YCB <dg...@gm...> wrote:
>
> Hi Scott,
>
> I agree this would be useful, but unfortunately this is not possible for
> technical reasons. We use normal freetext messages for the new message
> system, and already make full use of the 13 characters available.
>
>
> 73 de DG2YCB,
> Uwe
> ________________________________________
> German Amateur Radio Station DG2YCB
> Dr. Uwe Risse
> eMail: dg...@gm...
> Info: www.qrz.com/db/DG2YCB
>
>
>
> Am 15.01.2025 um 01:27 schrieb Scott Armstrong via wsjt-devel:
>
> Hey Guys,
>
> Small issue.   If I receive a QSY message from someone, I have no idea who
> sent that message other than trying to track down the  station by his DF
> and that is only good if he hasn't moved.
> This will not work so well on a busy band in the heat of the contest.
>
> I could  blindly QSY to that band but in the case of a band with highly
> directional antennas, where do I aim the antenna? Not as much of an issue
> on the lower bands but could still be a problem.
>
> This is what I see displayed in the QSY monitor window. It doesn't even
> show the DF the message came in at.
>
>
>
>
> I have a request,
>
> Can some functionality be added that will take the DF of the QSY message
> and match that to the DF maybe within +/- a few Hz to other prior decodes,
> pull the callsign of that station that sent the message and display that
> callsign in the QSY monitor window?
>
> Thank you and 73,
>
> Scott AA5AM
>
>
>
> _______________________________________________
>
> wsjt-devel mailing list
>
> wsj...@li...
>
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>
>
>
> _______________________________________________
> wsjt-devel mailing list
> wsj...@li...
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>