Date   

locked Re: #QSO_practices #QSO_practices

NR4U Bob AFMARS
 

On 2/24/2021 05:23, David Ackrill wrote:
With Q65 the "Call 1st" setting doesn't seem to work properly yet, you
have to double click the station that calls you. As you can see by the
way that the boxes TX1 to TX4 are blank.
Yes, I am noticing this also

--
73
Bob KD7YZ


--
--
Bob KD7YZ in NE Kentucky


locked Re: Adding to Frequencies lists #Q65

David Ackrill
 
Edited

OK, so I deleted all the existing clones, leaving just "Default" in the drop down. Closed all instances of WSJT-X and then followed steps 1 to 4.

On reopening V2.3.0, after having used Q65 on 50.305MHz for a couple of TX/RX periods with V2.4.0-rc1, V2.3.0 then starts in JT9 mode and the configuration for Q65 appears in the drop down and is selected (which is why it goes to JT9 on start up, I guess?) under the Settings>Frequencies tab a new entry for All modes with a frequency of 50.305MHz has been added.  I had made sure it was deleted before I started the process.

Just to be sure, I deleted the Q65 configuration, deleted the "All" entry with the frequency 50.305MHz, closed WSJT-X completely and carried out the procedure again.  This time I added a clone for FT8 in WSJT-X V2.3.0 as well as one for Q65. Followed the procedure for going to V2.4.0-rc1 again and setting up the Q65 clone for that mode and adding an entry in Frequencies for "Region 1, Q65, 50.305MHz" and closed WSJT-X down.

On going back to V2.3.0 it opened in JT9 again, I swapped to the FT8 clone and the frequency did not change to 50.313, both clones for Q65 and FT8 were in the configurations drop down and there was an entry for All modes, 50.305MHz in the Frequencies list again.

I took some screen shots as I worked through the procedure the second time, just in case anyone wants to see them.

Cheers - Dave (G0DJA)

 


locked Re: QSY +0.055Khz #WSJTX_config

Bill Somerville
 

On 26/02/2021 16:08, Franco wrote:
Hi Bill
Thanks for the info.
 
Now I use a FTDX101MP always with OMNIRIG and the problem is equal.
As you wrote, I always "correct" the frequency with the dropdown list to bring it back, but I often forget, even if it is not big problem.
I think you can fix it easily: that I use other soft and similar to WSJTx, I also open MSHV, and they don't do this + 055Hz shift.
Similar JTdx has the same problem but I think it depends on the main WSJTx source.
 
Bill, do you think it can be updated or corrected in the future?

73
Franco

Franco,

perhaps I was not clear, the problem lies with Omni-Rig.

73
Bill
G4WJS.


locked Re: QSY +0.055Khz #WSJTX_config

Frank
 

Hi Bill
Thanks for the info.
 
Now I use a FTDX101MP always with OMNIRIG and the problem is equal.
As you wrote, I always "correct" the frequency with the dropdown list to bring it back, but I often forget, even if it is not big problem.
I think you can fix it easily: that I use other soft and similar to WSJTx, I also open MSHV, and they don't do this + 055Hz shift.
Similar JTdx has the same problem but I think it depends on the main WSJTx source.
 
Bill, do you think it can be updated or corrected in the future?

73
Franco


locked Re: Lost Tab 2 TX Messages #FT8 #WSJTX_config

Bill Somerville
 

On 26/02/2021 15:52, greg5ta via groups.io wrote:
So now there is only one way to generate tx messages?  The user guide still shows tab2 populated.  If tab 2 has been removed, why is it a possible selection.  Tab 3 which was previously available was removed in its entirety.  Just trying to understand?
OM,

perhaps you did not take much notice of previous versions. Since FT8 DX-pedition mode was introduced there was a Tab 3, now Tab 2 messages have been removed the old Tab 3 (Fox messages) has become Tab 2.

As I said, Tab 2 messages have been removed. Tab 1 message provide all he features that Tab 2 messages had, and more.

The documentation updates are in hand, the next release will have new text and images to match.

73
Bill
G4WSJ.


locked Re: Lost Tab 2 TX Messages #FT8 #WSJTX_config

greg5ta
 

So now there is only one way to generate tx messages?  The user guide still shows tab2 populated.  If tab 2 has been removed, why is it a possible selection.  Tab 3 which was previously available was removed in its entirety.  Just trying to understand?


locked Re: Why couldn't I log this contact? #logging

Larry Banks
 

Agree Joe,

I have changed to Consolas where I can. The main GUI could use it too.

73 -- Larry -- W1DYJ

-----Original Message-----
From: Joe Subich, W4TV
Sent: Friday, February 26, 2021 9:37
To: main@WSJTX.groups.io
Subject: Re: [WSJTX] Why couldn't I log this contact? #logging


Exactly why the UI should use a typeface (like Consolas) that has a
slashed zero. The text was clear and obvious E zero one zero while
the screen shot was ambiguous (particularly at a reduced size in
an e-mail attachment).

73,

... Joe, W4TV


On 2021-02-25 9:58 PM, JP Tucson, AZ wrote:
It's NOT E zero 10 (his was a typo)...

If you look at his attached image, it shows EO10 (E, OH, ONE, ZERO)
which is a valid GS.



73 - John - N7GHZ

On Thu, Feb 25, 2021, 7:25 PM Joe Subich, W4TV <lists@...
<mailto:lists@...>> wrote:


> The E010 in the Exch sent box is my grid square.

E zero 10 is not a valid grid square. Grid squares are two alpha
characters followed by two numeric characters then two alpha and
two numeric, etc.

73,

... Joe, W4TV


On 2021-02-25 7:02 PM, ve4cy wrote:
> Hi Reino:
>
> Thanks for the 'second set of eyes'. The E010 in the Exch sent
box is my grid square.. I think you're right, it probably shouldn't
have been there.
>
> Not sure how it did get there. When the QSO was complete, I just
clicked on OK to confirm the contact. I never edited any of the
info. I'll look for a wayward grid entry should it happen again.
>
> Thanks again !
>
> 73 de Jim VE4CY
>
> ----- Original Message -----
>
> From: "Reino Talarmo" <reino.talarmo@...
<mailto:reino.talarmo@...>>
> To: main@WSJTX.groups.io <mailto:main@WSJTX.groups.io>
> Sent: Thursday, February 25, 2021 11:45:11 AM
> Subject: Re: [WSJTX] Why couldn't I log this contact? #logging
>
>
>
> Hi Jim,
>
> I have not used Q65 and may be totally wrong. In any case I
assume you did not use any contest mode. The EO10 in Exch sent field
seems odd to me. Normally there is nothing except in contest modes.
Perhaps just removing that information would permit you to log the
QSO. If the EO10 is something to do with Q65, then I assume there
should be also something in the Rcvd field, I don’t know.
>
> 73, Reino OH3mA
>
>
>
> From: main@WSJTX.groups.io <mailto:main@WSJTX.groups.io>
[mailto:main@WSJTX.groups.io <mailto:main@WSJTX.groups.io>] On
Behalf Of ve4cy
> Sent: 25. helmikuuta 2021 18:42
> To: main@WSJTX.groups.io <mailto:main@WSJTX.groups.io>
> Subject: [WSJTX] Why couldn't I log this contact? #logging
>
>
>
> I was doing some Q65 on 70cm the other night using an Icom
IC-9700. and WSJT-X v2.4.0-rc1 I logged several stations
successfully. Then, with the next station I worked... The "Click OK
to Log contact" window popped up as usual. I clicked OK, but this
time a small error message popped up asking me to check my exchange
times. I can't see anything in the log window that is 'wrong'. See
attached image: My clock was 'Exact' per https://time.is/
<https://time.is/>
>
>
>
> This is the first time this has ever happened. Any idea why I
couldn't get this station in my log?
>
>
>
>
>
>
>
> 73 de Jim VE4CY
>









locked Re: FT4 contest #FT4

Bill Somerville
 

On 26/02/2021 07:59, Dave Tucker Nu4N wrote:
The FT4 contest is this weekend. How do i set up for the contest. Tried the available contest available in WSJT-x Got the my state but no report 599. The exchange RST/STATE.
Thanks in advance
73's de NU4N/Dave
Hi Dave,

the contest mode exchanges for each of the special contest modes supported by WSJT-X are documented in the WSJT-X User Guide:

https://physics.princeton.edu/pulsar/K1JT/wsjtx-doc/wsjtx-main-2.3.0.html#COMP-CALL

73
Bill
G4WJS.


locked Re: FT4 contest #FT4

JP Tucson, AZ
 

You just input the state code.

The program will provide the rst when it logs.  It converts the dB to rst automatically.

73 - John - N7GHZ


On Fri, Feb 26, 2021, 7:29 AM Dave Tucker Nu4N <dwtucker19@...> wrote:
Hello John. I opened up the advanced field and checked arrl ru. I put KY in for my state but can't put in the RST 599??
Is that all one can do ?? I checked the FT4 contest page and to rules of course is state/rst. On that site the guy had an example of setup for the contest. and that's the way to do it I guess??

73's de NU4N/Dave



locked Re: Why couldn't I log this contact? #logging

Joe Subich, W4TV
 

Exactly why the UI should use a typeface (like Consolas) that has a
slashed zero. The text was clear and obvious E zero one zero while
the screen shot was ambiguous (particularly at a reduced size in
an e-mail attachment).

73,

... Joe, W4TV

On 2021-02-25 9:58 PM, JP Tucson, AZ wrote:
It's NOT E zero 10 (his was a typo)...
If you look at his attached image, it shows EO10  (E, OH, ONE, ZERO) which is a valid GS.
73 - John - N7GHZ
On Thu, Feb 25, 2021, 7:25 PM Joe Subich, W4TV <lists@... <mailto:lists@...>> wrote:
 > The E010 in the Exch sent box is my grid square.
E zero 10 is not a valid grid square.  Grid squares are two alpha
characters followed by two numeric characters then two alpha and
two numeric, etc.
73,
    ... Joe, W4TV
On 2021-02-25 7:02 PM, ve4cy wrote:
> Hi Reino:
>
> Thanks for the 'second set of eyes'. The E010 in the Exch sent
box is my grid square.. I think you're right, it probably shouldn't
have been there.
>
> Not sure how it did get there. When the QSO was complete, I just
clicked on OK to confirm the contact. I never edited any of the
info. I'll look for a wayward grid entry should it happen again.
>
> Thanks again !
>
> 73 de Jim VE4CY
>
> ----- Original Message -----
>
> From: "Reino Talarmo" <reino.talarmo@...
<mailto:reino.talarmo@...>>
> To: main@WSJTX.groups.io <mailto:main@WSJTX.groups.io>
> Sent: Thursday, February 25, 2021 11:45:11 AM
> Subject: Re: [WSJTX] Why couldn't I log this contact? #logging
>
>
>
> Hi Jim,
>
> I have not used Q65 and may be totally wrong. In any case I
assume you did not use any contest mode. The EO10 in Exch sent field
seems odd to me. Normally there is nothing except in contest modes.
Perhaps just removing that information would permit you to log the
QSO. If the EO10 is something to do with Q65, then I assume there
should be also something in the Rcvd field, I don’t know.
>
> 73, Reino OH3mA
>
>
>
> From: main@WSJTX.groups.io <mailto:main@WSJTX.groups.io>
[mailto:main@WSJTX.groups.io <mailto:main@WSJTX.groups.io>] On
Behalf Of ve4cy
> Sent: 25. helmikuuta 2021 18:42
> To: main@WSJTX.groups.io <mailto:main@WSJTX.groups.io>
> Subject: [WSJTX] Why couldn't I log this contact? #logging
>
>
>
> I was doing some Q65 on 70cm the other night using an Icom
IC-9700. and WSJT-X v2.4.0-rc1 I logged several stations
successfully. Then, with the next station I worked... The "Click OK
to Log contact" window popped up as usual. I clicked OK, but this
time a small error message popped up asking me to check my exchange
times. I can't see anything in the log window that is 'wrong'. See
attached image: My clock was 'Exact' per https://time.is/
<https://time.is/>
>
>
>
> This is the first time this has ever happened. Any idea why I
couldn't get this station in my log?
>
>
>
>
>
>
>
> 73 de Jim VE4CY
>


locked Re: FT4 contest #FT4

 

Hello John. I opened up the advanced field and checked arrl ru. I put KY in for my state but can't put in the RST 599??
Is that all one can do ?? I checked the FT4 contest page and to rules of course is state/rst. On that site the guy had an example of setup for the contest. and that's the way to do it I guess??

73's de NU4N/Dave


locked WSPR Band hopping V2.4.0 RC1 not working on Yaesu FT450D with SCU-17 #WSPR #IssueReport

Erwin - PE3ES - F4VTQ
 

I thought the band hopping issue had been solved after V2.2.2 but when I started a complete schedule (all HF bands active for all 4 timeframes) with my FT450D connected via SCU-17 interface the rig stayed on 1 band.

I tried V2.3.0 and same issue, no WSPR band hopping

I tried V2.2.0 and the known sub process error crashed WSJTx

CAT works and band changes when asked to by hand.
Decoding works etc.

Connected PC is Windows10

Any other things I would need to try or check for confirmation?

Thanks
--
PE3ES / F4VTQ
de Erwin


locked Re: Lost Tab 2 TX Messages #FT8 #WSJTX_config

Bill Somerville
 

On 26/02/2021 13:37, greg5ta via groups.io wrote:
I installed 2.3 and I have TX messages in the Tab 1 box but tab 2 box is empty. Also I could not find explanations for the additional selections when that tab is selected.
OM,

Tab 2 messages have been removed, see the WSJT-X v2.3.0 release notes. Tab 1 messages have all the same functionality and more.

73
Bill
G4WJS.


locked Lost Tab 2 TX Messages #FT8 #WSJTX_config

greg5ta
 

I installed 2.3 and I have TX messages in the Tab 1 box but tab 2 box is empty.  Also I could not find explanations for the additional selections when that tab is selected.


locked Re: QSY +0.055Khz #WSJTX_config

Bill Somerville
 

On 26/02/2021 13:12, Franco wrote:
On Tue, Oct 8, 2019 at 08:06 AM, Bill Somerville wrote:
this is a known issue with WSJT-X interoperating with Omni-Rig, it is related to Omni-Rig returning a status that indicates the rig has gone "offline" for no apparent reason. Hopefully we will have a fix for the next release of WSJT-X.
Hi Bill

I apologize if I take back the old message of 2019 but even with this latest version, when I load the WSJTx, using OMNIRIG as radio configuration, it always always moves the frequency by + 055Hz .... still with the WSJTx 2.3.0 maybe it is not been fixed? Like previous versions frequency 14074.000, the WSJTx program starts and I always find myself at 14.074.055 which I always have to correct. I use all CAT soft connected always with OMNIRIG but only the WSJTx shifts the frequency when it starts. Not a problem but annoying especially when I use it remotely. Bobby & Gary: I have them all SLOPE and INTERCEPT set to zero, never used "Frequency Calibration Tools." and as Bill confirms, this should be the known problem to be solved...

Is there a new solution now maybe I can use to solve? Thanks
Franco

Hi Franco,

when WSJT-X starts a rig control session it makes a small frequency change in order to determine the frequency resolution of the rig, it restores the original frequency once that is complete. it seems that either the initial read of the frequency, or the restore to that frequency are failing. As the FTdx3000 has a 1Hz frequency resolution you can probably ignore the issue and set the rig to the desired frequency using the working frequencies drop down list, by direct entry, or using the rig;s VFO knob.

73
Bill
G4WJS.


locked Re: FT4 contest #FT4

 

Hey John tnx for the reply. I may or may not call cq. Probably will tho.
Maybe someone has some other idea.

--
73's de NU4N/Dave


locked Re: QSY +0.055Khz #WSJTX_config

Frank
 

On Tue, Oct 8, 2019 at 08:06 AM, Bill Somerville wrote:
this is a known issue with WSJT-X interoperating with Omni-Rig, it is related to Omni-Rig returning a status that indicates the rig has gone "offline" for no apparent reason. Hopefully we will have a fix for the next release of WSJT-X.
Hi Bill

I apologize if I take back the old message of 2019 but even with this latest version, when I load the WSJTx, using OMNIRIG as radio configuration, it always always moves the frequency by + 055Hz ....
still with the WSJTx 2.3.0 maybe it is not been fixed? Like previous versions frequency 14074.000, the WSJTx program starts and I always find myself at 14.074.055 which I always have to correct. I use all CAT soft connected always with OMNIRIG but only the WSJTx shifts the frequency when it starts. Not a problem but annoying especially when I use it remotely.
Bobby & Gary: I have them all SLOPE and INTERCEPT set to zero, never used "Frequency Calibration Tools." and as Bill confirms, this should be the known problem to be solved...

Is there a new solution now maybe I can use to solve?

Thanks
Franco


locked Re: FT4 contest #FT4

JP Tucson, AZ
 

Dave,

Try running as RTTY ROUNDUP; which uses rst/state..
.But, it also places 'RU'  in tx6 CQ message.

Settings>advanced> RTTY ROUNDUP & put your state in rtty ru block in lower right corner

73 - John - N7GHZ


On Fri, Feb 26, 2021, 1:48 AM Dave Tucker Nu4N <dwtucker19@...> wrote:
The FT4 contest is this weekend. How do i set up for the contest. Tried the available contest available in WSJT-x Got the my state but no report 599. The exchange RST/STATE.
Thanks in advance
73's de NU4N/Dave



locked FT4 contest #FT4

 

The FT4 contest is this weekend. How do i set up for the contest. Tried the available contest available in WSJT-x Got the my state but no report 599. The exchange RST/STATE.
Thanks in advance
73's de NU4N/Dave


locked Re: Why couldn't I log this contact? #logging

JP Tucson, AZ
 

It's NOT E zero 10 (his was a typo)...

If you look at his attached image, it shows EO10  (E, OH, ONE, ZERO) which is a valid GS.



73 - John - N7GHZ


On Thu, Feb 25, 2021, 7:25 PM Joe Subich, W4TV <lists@...> wrote:

 > The E010 in the Exch sent box is my grid square.

E zero 10 is not a valid grid square.  Grid squares are two alpha
characters followed by two numeric characters then two alpha and
two numeric, etc.

73,

    ... Joe, W4TV


On 2021-02-25 7:02 PM, ve4cy wrote:
> Hi Reino:
>
> Thanks for the 'second set of eyes'. The E010 in the Exch sent box is my grid square.. I think you're right, it probably shouldn't have been there.
>
> Not sure how it did get there. When the QSO was complete, I just clicked on OK to confirm the contact. I never edited any of the info. I'll look for a wayward grid entry should it happen again.
>
> Thanks again !
>
> 73 de Jim VE4CY
>
> ----- Original Message -----
>
> From: "Reino Talarmo" <reino.talarmo@...>
> To: main@WSJTX.groups.io
> Sent: Thursday, February 25, 2021 11:45:11 AM
> Subject: Re: [WSJTX] Why couldn't I log this contact? #logging
>
>
>
> Hi Jim,
>
> I have not used Q65 and may be totally wrong. In any case I assume you did not use any contest mode. The EO10 in Exch sent field seems odd to me. Normally there is nothing except in contest modes. Perhaps just removing that information would permit you to log the QSO. If the EO10 is something to do with Q65, then I assume there should be also something in the Rcvd field, I don’t know.
>
> 73, Reino OH3mA
>
>
>
> From: main@WSJTX.groups.io [mailto:main@WSJTX.groups.io] On Behalf Of ve4cy
> Sent: 25. helmikuuta 2021 18:42
> To: main@WSJTX.groups.io
> Subject: [WSJTX] Why couldn't I log this contact? #logging
>
>
>
> I was doing some Q65 on 70cm the other night using an Icom IC-9700. and WSJT-X v2.4.0-rc1 I logged several stations successfully. Then, with the next station I worked... The "Click OK to Log contact" window popped up as usual. I clicked OK, but this time a small error message popped up asking me to check my exchange times. I can't see anything in the log window that is 'wrong'. See attached image: My clock was 'Exact' per https://time.is/
>
>
>
> This is the first time this has ever happened. Any idea why I couldn't get this station in my log?
>
>
>
>
>
>
>
> 73 de Jim VE4CY
>





15521 - 15540 of 38026