Date   

locked Re: unsuccessful contacts with 7q7ru

Joe - W9RF
 

Joe,


I'm pretty much convinced of that.

Since you have reminded me, that's what I remember about the clones, no F/H but appears to be in F/H mode.

I am running an older version of WSJT but Laurie suggested I upgrade to the newest one.

Going to do that and test a little more tonight.


You are right about the garbage clones they might be using, could be why you see 10-20 calls moved down to the 0-500 slot then never get answered..


73,

W9RF - Joe





On Monday, November 16, 2020, 4:24:32 PM CST, Joe Subich, W4TV <lists@...> wrote:



Joe,

Are you sure 7q7ru is using WSJTX and not a [garbage] clone like MSHV
or JTDX?

Some of the clones do not implement the F/H protocol correctly but
do allow for multiple simultaneous QSOs.  It may be that 7q7ru is
using one of the incompatible software packages and using the
*NON F/H* mode in WSJTX is the correct way to operate!

73,

    ... Joe, W4TV


On 2020-11-16 5:12 PM, ray cathode via groups.io wrote:
>  Laurie,
>
>
>
> I suppose it could be but did the parameters for F/H change since 2.1.2?
> I'll upgrade and see what happens
>
>
> 73,
> W9RF - Joe
>
>
>
>
>      On Monday, November 16, 2020, 4:05:42 PM CST, Laurie, VK3AMA <hamapps.support@...> wrote:


>
> On 17/11/2020 8:49 am, ray cathode via groups.io wrote:
>> There might be some validity in your reasoning BUT I will stick with
>> the PLAIN FT8 (at least for 7q7ru)
>>
>> 9 times of making contact then getting put up to the 500_ slot is not
>> coincidence.
>>
>>
>> I just made another qso on 20 meters with 7q7ru in PLAIN FT8 mode
>> (4'th call) fairly bad signal reports.
>>
>>
>
> Could it be your very old WSJT-X version?
> 2.1.2 is rather dated.
>
> de Laurie VK3AMA
>








locked Re: Callsigns get cleared before I can see them

HamApps Support (VK3AMA)
 

On 17/11/2020 9:13 am, John Peck wrote:
I am running current versions of WSJT and JTAlert. My issue is that JTAlert clears the callsigns before I can click on them or even read them! To make it more frustrating, the nice lady announces that there is a station there that I am looking for, but then I can't access it! 

Am I missing a setting somewhere? 

What versions of WSJT-X and JTAlert? Quote the actual numbers, "current versions", tells me nothing.

de Laurie VK3AMA


locked Re: Callsigns get cleared before I can see them

Jim Cooper
 

On 16 Nov 2020 at 14:13, John Peck wrote:

I am running current versions of
WSJT and JTAlert. My issue is that
JTAlert clears the callsigns before
I can click on them or even read them!
To make it more frustrating, the
nice lady announces that there is a
station there that I am looking for,
but then I can't access it!

Am I missing a setting somewhere?
use the "Decodes" window ... it keeps
a history of all the decoded stations.

JTalert can't display the calls until WSJT-X
has completed the decode process and passed
the calls to JTalert via UDP ... if your cpu is
loaded or 'slow' then it will eat up the time
for display before the next cycle.

fwiw, I had similar problems with a cheap
$100 win10 desktop that I was using ... it seemed
to do everything ok EXCEPT the cpu would get
maxed at times and the decodes would be slow;
not to mention that I could watch the waterfall
and see the decode 'pause' at times when the
cpu didn't quite keep up with the incoming audio .....

Moved my FT8 stuff to a much 'better' PC and
now there are no dropouts and no decode or
display delays ... it DOES make a difference.

Jim w2jc


locked Re: unsuccessful contacts with 7q7ru

wc3w
 

I definitely believe what you are saying is true—I cannot get my band activity screen to scroll when changing to F/H….I can hear the signals coming in but it refuses to decode!

Mark
WC3W

On Nov 16, 2020, at 3:24 PM, Joe Subich, W4TV <lists@subich.com> wrote:


Joe,

Are you sure 7q7ru is using WSJTX and not a [garbage] clone like MSHV
or JTDX?

Some of the clones do not implement the F/H protocol correctly but
do allow for multiple simultaneous QSOs. It may be that 7q7ru is
using one of the incompatible software packages and using the
*NON F/H* mode in WSJTX is the correct way to operate!

73,

... Joe, W4TV


On 2020-11-16 5:12 PM, ray cathode via groups.io wrote:
Laurie,
I suppose it could be but did the parameters for F/H change since 2.1.2?
I'll upgrade and see what happens
73,
W9RF - Joe
On Monday, November 16, 2020, 4:05:42 PM CST, Laurie, VK3AMA <hamapps.support@vkdxer.com> wrote:
On 17/11/2020 8:49 am, ray cathode via groups.io wrote:
There might be some validity in your reasoning BUT I will stick with
the PLAIN FT8 (at least for 7q7ru)

9 times of making contact then getting put up to the 500_ slot is not
coincidence.


I just made another qso on 20 meters with 7q7ru in PLAIN FT8 mode
(4'th call) fairly bad signal reports.

Could it be your very old WSJT-X version?
2.1.2 is rather dated.
de Laurie VK3AMA






locked Re: unsuccessful contacts with 7q7ru

Joe Subich, W4TV
 

Joe,

Are you sure 7q7ru is using WSJTX and not a [garbage] clone like MSHV
or JTDX?

Some of the clones do not implement the F/H protocol correctly but
do allow for multiple simultaneous QSOs. It may be that 7q7ru is
using one of the incompatible software packages and using the
*NON F/H* mode in WSJTX is the correct way to operate!

73,

... Joe, W4TV

On 2020-11-16 5:12 PM, ray cathode via groups.io wrote:
Laurie,
I suppose it could be but did the parameters for F/H change since 2.1.2?
I'll upgrade and see what happens
73,
W9RF - Joe
On Monday, November 16, 2020, 4:05:42 PM CST, Laurie, VK3AMA <hamapps.support@vkdxer.com> wrote:
On 17/11/2020 8:49 am, ray cathode via groups.io wrote:
There might be some validity in your reasoning BUT I will stick with
the PLAIN FT8 (at least for 7q7ru)

9 times of making contact then getting put up to the 500_ slot is not
coincidence.


I just made another qso on 20 meters with 7q7ru in PLAIN FT8 mode
(4'th call) fairly bad signal reports.

Could it be your very old WSJT-X version?
2.1.2 is rather dated.
de Laurie VK3AMA


locked Callsigns get cleared before I can see them

John Peck
 

I am running current versions of WSJT and JTAlert. My issue is that JTAlert clears the callsigns before I can click on them or even read them! To make it more frustrating, the nice lady announces that there is a station there that I am looking for, but then I can't access it! 

Am I missing a setting somewhere? 


locked Re: unsuccessful contacts with 7q7ru

Joe - W9RF
 

Laurie,



I suppose it could be but did the parameters for F/H change since 2.1.2?

I'll upgrade and see what happens



73,

W9RF - Joe





On Monday, November 16, 2020, 4:05:42 PM CST, Laurie, VK3AMA <hamapps.support@...> wrote:




On 17/11/2020 8:49 am, ray cathode via groups.io wrote:
> There might be some validity in your reasoning BUT I will stick with
> the PLAIN FT8 (at least for 7q7ru)
>
> 9 times of making contact then getting put up to the 500_ slot is not
> coincidence.
>
>
> I just made another qso on 20 meters with 7q7ru in PLAIN FT8 mode
> (4'th call) fairly bad signal reports.
>
>

Could it be your very old WSJT-X version?
2.1.2 is rather dated.

de Laurie VK3AMA







locked Re: unsuccessful contacts with 7q7ru

Laurie, VK3AMA
 

On 17/11/2020 8:49 am, ray cathode via groups.io wrote:
There might be some validity in your reasoning BUT I will stick with the PLAIN FT8 (at least for 7q7ru)

9 times of making contact then getting put up to the 500_ slot is not coincidence.


I just made another qso on 20 meters with 7q7ru in PLAIN FT8 mode (4'th call) fairly bad signal reports.

Could it be your very old WSJT-X version?
2.1.2 is rather dated.

de Laurie VK3AMA


locked Re: unsuccessful contacts with 7q7ru

Joe - W9RF
 

Bjorn,


There might be some validity in your reasoning BUT I will stick with the PLAIN FT8 (at least for 7q7ru)

9 times of making contact then getting put up to the 500_ slot is not coincidence.


I just made another qso on 20 meters with 7q7ru in PLAIN FT8 mode (4'th call) fairly bad signal reports.




213430 -10 0.1 289 ~ CQ 7Q7RU KH67

213445 Tx 1325 ~ 7Q7RU W9RF EM57

213500 -15 0.1 348 ~ W9RF 7Q7RU -06

213515 Tx 1325 ~ 7Q7RU W9RF R-15

213530 -16 0.1 348 ~ W9RF 7Q7RU -06

213545 Tx 1325 ~ 7Q7RU W9RF R-16

213600 -11 0.1 288 ~ W9RF RR73; K8SIX <7Q7RU> -04

213615 Tx 1325 ~ 7Q7RU W9RF R-16

213630 -11 0.1 289 ~ W9RF 7Q7RU RR73

213646 Tx 1325 ~ 7Q7RU W9RF 73



73,

W9RF - Joe



On Monday, November 16, 2020, 3:24:37 PM CST, Björn SM7IUN <bjorn@...> wrote:


It's not the DX that pulls you down in frequency. It's the logic in your WSJT-X just following the F/H protocol.

The fact that you succeeded just meant they could decode you correctly and has nothing to do with F/H or not. 
Or software compatibility for that matter.

If there are lots of LIDS using plain FT8 calling on or around the DX' frequency, you will struggle 
to make QSO with F/H since the frequency you move to (i.e. the carrier of the responding stream) 
is clobbered. If you are unlucky, the secondary (random but below 1000Hz) frequency the software 
moves you to after three failed attempts may still be that of a LID. 

Björn SM7IUN

Den mån 16 nov. 2020 kl 21:22 skrev ray cathode via groups.io <ray_cathode1=yahoo.com@groups.io>:
Roger,




For what it's worth here is another update on my unsuccessful confirmation with 7q7ru in F/H mode.

Yesterday evening the problem on 30 meters F/H mode was remedied buy switching out of F/H mode.


Same thing happened to me today.

While calling them at 18.095 F/H mode I was answered with a +1 report both ways and after a few exchanges I was thrown up to the 500+ slot and they began calling other calls.

I took Jtalert/WSJT-X out of F/H mode and called again with plain FT8 at 1325, third try they answered me, did NOT pull me down to their freq, and after 2 exchanges they gave me a confirmation (RR73)


SO, if anyone is having the same problem I have been experiencing I would suggest giving a plain FT8 a try.


I feel the only answer is software incompatibility at some level.

and before anyone asks, this is what I understand to be F/H  mode.

182145 Tx 1325 ~ 7Q7RU W9RF EM57

182200 1 0.1 286 ~ K4PX RR73; NB2P <7Q7RU> -10

182200 1 0.1 346 ~ W9RF 7Q7RU +01

182215 Tx 1325 ~ 7Q7RU W9RF R+01

182230 1 0.1 346 ~ W9RF 7Q7RU +01

182245 Tx 1325 ~ 7Q7RU W9RF R+01

182300 6 0.1 286 ~ W9RF RR73; W1KG <7Q7RU> -04








On Sunday, November 15, 2020, 9:07:50 PM CST, ray cathode via groups.io <ray_cathode1=yahoo.com@groups.io> wrote:


Roger,


I finally worked him just now on 10.131 but I was NOT in f/h mode, although he is in f/h mode, unless he switched on the fly, go figure??

Called him at 1500 and he did not call me to his freq but we exchanged reports and got a RR73 from him..


73,

W9RF - Joe








On Sunday, November 15, 2020, 6:52:45 PM CST, Roger M via groups.io <ac6bw=yahoo.com@groups.io> wrote:


Joe,
OK, fair enough. Yes, it does seem strange.
All I can suggest is keep trying. Are you using WSJT-X, or JTDX? I recently switched over to JTDX, because it has better decode sensitivity, as well as some other features that I like. If you have both programs installed, perhaps you can try one or the other in F/H mode, and see if that makes a difference.
Also, it's possible that something is not configured correctly on the Fox end, but I wouldn't know exactly what. There are a lot of settings that the Fox can enable.
--
73,
Roger
AC6BW


locked Re: unsuccessful contacts with 7q7ru

Björn SM7IUN
 

It's not the DX that pulls you down in frequency. It's the logic in your WSJT-X just following the F/H protocol.

The fact that you succeeded just meant they could decode you correctly and has nothing to do with F/H or not. 
Or software compatibility for that matter.

If there are lots of LIDS using plain FT8 calling on or around the DX' frequency, you will struggle 
to make QSO with F/H since the frequency you move to (i.e. the carrier of the responding stream) 
is clobbered. If you are unlucky, the secondary (random but below 1000Hz) frequency the software 
moves you to after three failed attempts may still be that of a LID. 

Björn SM7IUN

Den mån 16 nov. 2020 kl 21:22 skrev ray cathode via groups.io <ray_cathode1=yahoo.com@groups.io>:

Roger,




For what it's worth here is another update on my unsuccessful confirmation with 7q7ru in F/H mode.

Yesterday evening the problem on 30 meters F/H mode was remedied buy switching out of F/H mode.


Same thing happened to me today.

While calling them at 18.095 F/H mode I was answered with a +1 report both ways and after a few exchanges I was thrown up to the 500+ slot and they began calling other calls.

I took Jtalert/WSJT-X out of F/H mode and called again with plain FT8 at 1325, third try they answered me, did NOT pull me down to their freq, and after 2 exchanges they gave me a confirmation (RR73)


SO, if anyone is having the same problem I have been experiencing I would suggest giving a plain FT8 a try.


I feel the only answer is software incompatibility at some level.

and before anyone asks, this is what I understand to be F/H  mode.

182145 Tx 1325 ~ 7Q7RU W9RF EM57

182200 1 0.1 286 ~ K4PX RR73; NB2P <7Q7RU> -10

182200 1 0.1 346 ~ W9RF 7Q7RU +01

182215 Tx 1325 ~ 7Q7RU W9RF R+01

182230 1 0.1 346 ~ W9RF 7Q7RU +01

182245 Tx 1325 ~ 7Q7RU W9RF R+01

182300 6 0.1 286 ~ W9RF RR73; W1KG <7Q7RU> -04








On Sunday, November 15, 2020, 9:07:50 PM CST, ray cathode via groups.io <ray_cathode1=yahoo.com@groups.io> wrote:


Roger,


I finally worked him just now on 10.131 but I was NOT in f/h mode, although he is in f/h mode, unless he switched on the fly, go figure??

Called him at 1500 and he did not call me to his freq but we exchanged reports and got a RR73 from him..


73,

W9RF - Joe








On Sunday, November 15, 2020, 6:52:45 PM CST, Roger M via groups.io <ac6bw=yahoo.com@groups.io> wrote:


Joe,
OK, fair enough. Yes, it does seem strange.
All I can suggest is keep trying. Are you using WSJT-X, or JTDX? I recently switched over to JTDX, because it has better decode sensitivity, as well as some other features that I like. If you have both programs installed, perhaps you can try one or the other in F/H mode, and see if that makes a difference.
Also, it's possible that something is not configured correctly on the Fox end, but I wouldn't know exactly what. There are a lot of settings that the Fox can enable.
--
73,
Roger
AC6BW


locked Re: unsuccessful contacts with 7q7ru

Joe - W9RF
 

Roger,




For what it's worth here is another update on my unsuccessful confirmation with 7q7ru in F/H mode.

Yesterday evening the problem on 30 meters F/H mode was remedied buy switching out of F/H mode.


Same thing happened to me today.

While calling them at 18.095 F/H mode I was answered with a +1 report both ways and after a few exchanges I was thrown up to the 500+ slot and they began calling other calls.

I took Jtalert/WSJT-X out of F/H mode and called again with plain FT8 at 1325, third try they answered me, did NOT pull me down to their freq, and after 2 exchanges they gave me a confirmation (RR73)


SO, if anyone is having the same problem I have been experiencing I would suggest giving a plain FT8 a try.


I feel the only answer is software incompatibility at some level.

and before anyone asks, this is what I understand to be F/H  mode.

182145 Tx 1325 ~ 7Q7RU W9RF EM57

182200 1 0.1 286 ~ K4PX RR73; NB2P <7Q7RU> -10

182200 1 0.1 346 ~ W9RF 7Q7RU +01

182215 Tx 1325 ~ 7Q7RU W9RF R+01

182230 1 0.1 346 ~ W9RF 7Q7RU +01

182245 Tx 1325 ~ 7Q7RU W9RF R+01

182300 6 0.1 286 ~ W9RF RR73; W1KG <7Q7RU> -04








On Sunday, November 15, 2020, 9:07:50 PM CST, ray cathode via groups.io <ray_cathode1@...> wrote:


Roger,


I finally worked him just now on 10.131 but I was NOT in f/h mode, although he is in f/h mode, unless he switched on the fly, go figure??

Called him at 1500 and he did not call me to his freq but we exchanged reports and got a RR73 from him..


73,

W9RF - Joe








On Sunday, November 15, 2020, 6:52:45 PM CST, Roger M via groups.io <ac6bw@...> wrote:


Joe,
OK, fair enough. Yes, it does seem strange.
All I can suggest is keep trying. Are you using WSJT-X, or JTDX? I recently switched over to JTDX, because it has better decode sensitivity, as well as some other features that I like. If you have both programs installed, perhaps you can try one or the other in F/H mode, and see if that makes a difference.
Also, it's possible that something is not configured correctly on the Fox end, but I wouldn't know exactly what. There are a lot of settings that the Fox can enable.
--
73,
Roger
AC6BW


locked Re: States-Wanted Boxes Auto-Untick?

Jim N6VH
 


On 11/15/2020 11:51 PM, Patrick Hung wrote:
Laurie,

Thanks for the very clear explanation; I've chosen to require confirmation prior to deleting a State alert. There are three checkboxes to the right of "Confirmation": Card, eQSL, LoTW - with all three checked to mean that any of the three would suffice?
--
Patrick - W2TAR
_._,_._,_


Patrick,

If you are interested in the ARRL WAS (or DXCC, etc) award, then don't tick "eQSL". The eQSL confirmations are not valid for ARRL awards. If you are interested in the eQSL awards, that's a different matter.

Incidentally, getting WAS confirmed on LOTW is fairly easy. I have 8 band WAS, all confirmed on LOTW.

73,

Jim N6VH


locked Re: States-Wanted Boxes Auto-Untick?

HamApps Support (VK3AMA)
 

On 16/11/2020 6:51 pm, Patrick Hung wrote:
There are three checkboxes to the right of "Confirmation": Card, eQSL, LoTW - with all three checked to mean that any of the three would suffice?

Yes. Its an "OR" operation.

eg. If all three are enabled, that indicates that "Card" OR "Lotw" OR "Eqsl" confirmed QSOs found in the Log during the scan are candidates for considering the Entity as no longer needed.

de Laurie VK3AMA


locked Re: Text message window

HamApps Support (VK3AMA)
 

On 17/11/2020 3:33 am, Guy G4DWV 4X1LT wrote:
Hi Laurie,
I have attached what shows at startup and at random times.
--
73 de Guy G4DWV 4X1LT

Uncheck the "Restore window on JTAlert start" setting



de Laurie VK3AMA


locked JTAlert did stop reporting QSO upload to HRD #HRD

asobel@...
 

Laurie

My JTAlert v2.16.15 did stop the display of the QSO upload report to HRD. This did happen after a change to the HRD logbook database machine.

How do I get it back. It is very useful.

Amos 4X4MF


locked Re: Text message window

Guy G4DWV 4X1LT
 

Hi Laurie,
I have attached what shows at startup and at random times.
--
73 de Guy G4DWV 4X1LT


locked Re: unsuccessful contacts with 7q7ru

Guy G4DWV 4X1LT
 

Hi,
I find getting a new one for the log, even rare ones, like shooting fish in a barrel. Here is how I do it.
First, I use JTDX and would advise using it, but not just for its better coding ability.
Second, one HAS to work split all the time, I do. Joe, there is no need for calling to a freq.
Finally, there is no such thing as 'tail gating' in any JT mode or any similarly timed mode. I only mention this as this way of working DX was mentioned by somebody held in high regard in the JT community and indeed by me. How can there be such a thing when everybody TXs at exactly the same time? It is logistically impossible.
Working split is the key as I think the majority calls the DX stn on their TX freq making it difficult for the DX to tell who is calling. I park my TX freq in a silent part of the band. I stop TXing now and then to check if the freq I am using is still silent. I just keep my call going and get a hit before my 6min WD stops the TX. JTDX has a feature where the RMB click will place the TX freq on the graph and a LMB click will place the RX freq. The latter is not needed much but the RMB functionality is indispensable.
This is particularly useful for UK stations working FT8 as we only have the first 10MHz of the FT8 band.
--
73 de Guy G4DWV 4X1LT


locked Re: States-Wanted Boxes Auto-Untick?

Patrick Hung
 

Laurie,

Thanks for the very clear explanation; I've chosen to require confirmation prior to deleting a State alert. There are three checkboxes to the right of "Confirmation": Card, eQSL, LoTW - with all three checked to mean that any of the three would suffice?
--
Patrick - W2TAR


locked Re: DXCC

asobel@...
 

Laurie

 

This is good news

 

Please apply this to Wanted Callsign and Ignored Callsign too. It will be  very useful. For example: I want to QSO an unconfirmed  station on all bands but I get it alarmed on already worked bands.

 

Amos 4X4MF

 

 

From: Support@HamApps.groups.io <Support@HamApps.groups.io> On Behalf Of HamApps Support (VK3AMA)
Sent: Monday, November 16, 2020 8:35 AM
To: Support@HamApps.groups.io
Subject: Re: [HamApps] DXCC

 

On 16/11/2020 4:03 pm, Michael Black via groups.io wrote:

Is there a way to distinguish new DXCC from new DXCC-on-band?

New DXCC would take priority so would be nice to make it unique.

 

Mike W9MDB


NO. This would require additional ATNO alert lists which would have to be updated by addition log queries (the existing sql queries are not suitable). This atno alerting is however already part of the as yet unreleased JTAlertV3. While I am bringing some JTAlertV3 functionality into JTAlertV2, this is unlikely to be one of them.

From the current JTAlertV3 DXCC Alert settings...


Note the ATNO allows for a different color combination from the non-ATNO. Also the "Flash" checkbox allows for an ATNO alerted callsign to flash (alternate) its colors as an attention-grabbing mechanism, distinguishing it from a non-ATNO alert.

de Laurie VK3AMA


locked Re: DXCC

HamApps Support (VK3AMA)
 

On 16/11/2020 4:03 pm, Michael Black via groups.io wrote:
Is there a way to distinguish new DXCC from new DXCC-on-band?
New DXCC would take priority so would be nice to make it unique.

Mike W9MDB

NO. This would require additional ATNO alert lists which would have to be updated by addition log queries (the existing sql queries are not suitable). This atno alerting is however already part of the as yet unreleased JTAlertV3. While I am bringing some JTAlertV3 functionality into JTAlertV2, this is unlikely to be one of them.

From the current JTAlertV3 DXCC Alert settings...


Note the ATNO allows for a different color combination from the non-ATNO. Also the "Flash" checkbox allows for an ATNO alerted callsign to flash (alternate) its colors as an attention-grabbing mechanism, distinguishing it from a non-ATNO alert.

de Laurie VK3AMA

2261 - 2280 of 34373