Post by c21ts on Feb 29, 2024 8:53:30 GMT
Morning, and I apologize if this has come up before but I did a quick search and didn't find anything.
I'm Phill, C21TS. I mostly only use JTDX here for a number of reasons (closing in on 50K QSO). I was wondering if you would consider a change to JTDX that I've asked about in the past but got told it has to be like that.
The issue is this.
If you are in a QSO with someone and things are going OK and then that someone calls someone else and they are within 50hz of you then your JTDX stops! There is a setting to disable this but it is totally ignored for sigs within 50hz )
.
I've been tempted to have a go at this myself with the source but it's been a while. Because I mostly only use JTDX (I don't really like MSHV) and I automate the operation with Actiona (macros, to save QSO) it's very annoying when JTDX just stops because some guy who was calling me decides to call someone else. I would love to have this disabled. I think the idea from early FT8 days that you "own" a QRG are dead and buried.
My main reason for using JTDX is outlined on my QRZ page. In short the logic it uses to decide who to work next is almost flawless. It took me some time to get it just right.
The way I have JTDX setup it will always work
• new calls first
• if more than one then the most distant (so EU always before JA)
• new band next, most distant first
• worked before next if none of the above calling
It's pretty cool to watch in action. It nearly always calls what I would do if I was manually doing it. And just looking at the screen and I can see who I haven't worked etc. and intervene any time.
Any chance to get this once and for all removed? best I can offer is a sked for C21 if you need it, or Paypal for time spent? I did notice it was still like this in an early RC of 160. I've just finished setting up the JTSDK tools just in case :-)
73 Phill C21TS / FK1TS
I'm Phill, C21TS. I mostly only use JTDX here for a number of reasons (closing in on 50K QSO). I was wondering if you would consider a change to JTDX that I've asked about in the past but got told it has to be like that.
The issue is this.
If you are in a QSO with someone and things are going OK and then that someone calls someone else and they are within 50hz of you then your JTDX stops! There is a setting to disable this but it is totally ignored for sigs within 50hz )
. I've been tempted to have a go at this myself with the source but it's been a while. Because I mostly only use JTDX (I don't really like MSHV) and I automate the operation with Actiona (macros, to save QSO) it's very annoying when JTDX just stops because some guy who was calling me decides to call someone else. I would love to have this disabled. I think the idea from early FT8 days that you "own" a QRG are dead and buried.
My main reason for using JTDX is outlined on my QRZ page. In short the logic it uses to decide who to work next is almost flawless. It took me some time to get it just right.
The way I have JTDX setup it will always work
• new calls first
• if more than one then the most distant (so EU always before JA)
• new band next, most distant first
• worked before next if none of the above calling
It's pretty cool to watch in action. It nearly always calls what I would do if I was manually doing it. And just looking at the screen and I can see who I haven't worked etc. and intervene any time.
Any chance to get this once and for all removed? best I can offer is a sked for C21 if you need it, or Paypal for time spent? I did notice it was still like this in an early RC of 160. I've just finished setting up the JTSDK tools just in case :-)
73 Phill C21TS / FK1TS
