Date   

locked Re: Numerous glitches with my upgrade to 2.3.1 #FT8 #IssueReport

Gary - AG0N
 



On Apr 7, 2021, at 8:36 AM, Jim Simon <jhsw1yy@...> wrote:

On a random basis, all the signals on the waterfall spectrum spontaneously shift to the right half of the view, leaving the left essentially empty with all the signals crammed together on the right. Then after a few minutes, without any action on my part, the signals on the spectrum shift back to a normal spread. What could be causing this?

Take a look around when that happens and see if the radio and/or the frequency indication in WSJT-X have changed.  It sounds like you are shifting frequency on receive.  I assume you are running CAT control and choosing the correct “channel” frequency.

Gary - AG0N


locked Re: Contesting with WSJT-X, JTAlert, and DXKeeper #networking #ContestMode #FT8 #logging

Bill Somerville
 

On 07/04/2021 17:27, Pete Ritter via groups.io wrote:
Contesting with WSJT-X, JTAlert, DXKeeper
What is the best way to work contests with the above software?  I want JTAlert's worked B4, WSJT-X's coloring, etc to be relevant to the contest only. Should I save my adif file before the contest begins and start a new one and then on contest close, merge the two?  I know to set the appropriate contest mode in WSJT-X. Is there anything else I need to do?
Hi Pete,

yes that is the recommend strategy.

73
Bill
G4WJS.


locked Re: ADIF Master and wsjt_log.adi compatibility #WSJTX_config

Radivoj Kar, f6gnz
 

Hi Carl,
Thanks for the response. You said ADIF Master is not needed. But then which application to use to open the wsjt_log.adi , cut QSOs from certain date blocks and create two new .adi files, one containing remaining QSOs and other cut and pasted QSO groups.
Now, Windows opens the log with ADIF Master as default application, but I am not sure that if I save logs from ADIF Master if the resulting logs would be legitimate for wsjtx !
Please clarify.
73, Radi f6gnz


locked #fst4 packtext77 / mp_short_ops subroutines #FST4

Andy Talbot
 

Help I'm tearing my hair out :-(
Trying to understand the plain text encoding, the 'packtext77' routine  in the 'packjt77' module. and getting totally flummoxed by the mp_short ops.   Specifically ...init, ...add and ...mult which are needed in the packing process.

I have the Fortran manual to hand;  the equivalence statement makes sense, interpreting the same memory space as either integers and characters.

But what it's actually doing doesn't seem to make sense
I'm guessing the 'mp' start of the subroutine name stands for "multiple precision"?Only a guess, but it makes sense in context of the packing process.

Can someone help and explain in plain English what the packtext77 routine is actually doing.   Or , at least what those mp_short bits are doing - the code that calls them seems obvious enough.

Backgroud :
I want to write my own code, in my programming language of choice, for generating the symbols for a small subset of FST4 / FST4W messages.    Specifically WSPR type 1,  Telemetry and plain text messages.  Those are the only three I'm interested in.
I currently have the first two sorted but totally lost on plain text.

Was pleased at how simple the encoding process was;  I get symbol sets that agree perfectly with those generated from FST4SIM for WSPR Type 1 and Telemetry format messages.   Missed the rvec scrambling at first, but spotted it just before asking here why my results were total rubbish.

Hoping it may be possible to do the encoding in a PIC, but it'll have to be one with plenty of program memory to hold the parity generating tables.   Apart from that memory aspect, it looks to be  simpler than encoding JT4/JT9 in a PIC processor.


locked Contesting with WSJT-X, JTAlert, and DXKeeper #networking #ContestMode #FT8 #logging

Pete Ritter K5CPR
 

Contesting with WSJT-X, JTAlert, DXKeeper
 
What is the best way to work contests with the above software?  I want JTAlert's worked B4, WSJT-X's coloring, etc to be relevant to the contest only. Should I save my adif file before the contest begins and start a new one and then on contest close, merge the two?  I know to set the appropriate contest mode in WSJT-X. Is there anything else I need to do?


locked Re: Numerous glitches with my upgrade to 2.3.1 #FT8 #IssueReport

Bill Somerville
 

On 07/04/2021 15:36, Jim Simon wrote:
I've encountered some problems since upgrading from 2.2 to 2.3.1:

1) When I click on the up arrow to change frequency on the waterfall, about 20% of the time on a seemingly random basis, I get an error message "Rig Control Error - Do you want to reconfigure the radio interface?" When I click through that, I get the Radio page under Settings, I click "OK" without making any changes, and things return to normal. Any ideas why this is happening?

2) On a random basis, all the signals on the waterfall spectrum spontaneously shift to the right half of the view, leaving the left essentially empty with all the signals crammed together on the right. Then after a few minutes, without any action on my part, the signals on the spectrum shift back to a normal spread. What could be causing this?

Thanks.

Jim  W1YY
Hi Jim,

what rig are you using, and how is it connected to you PC for CAT and PTT control?

73
Bill
G4WJS.


locked Numerous glitches with my upgrade to 2.3.1 #FT8 #IssueReport

Jim Simon
 

I've encountered some problems since upgrading from 2.2 to 2.3.1:

1) When I click on the up arrow to change frequency on the waterfall, about 20% of the time on a seemingly random basis, I get an error message "Rig Control Error - Do you want to reconfigure the radio interface?" When I click through that, I get the Radio page under Settings, I click "OK" without making any changes, and things return to normal. Any ideas why this is happening?

2) On a random basis, all the signals on the waterfall spectrum spontaneously shift to the right half of the view, leaving the left essentially empty with all the signals crammed together on the right. Then after a few minutes, without any action on my part, the signals on the spectrum shift back to a normal spread. What could be causing this?

Thanks.

Jim  W1YY


locked Uncertainty about what DX station is using #FoxAndHound

John, K9MM
 

Occasionally, a DX station will show up using FT-8 on a non-standard frequency, and the question then becomes "Is he using F/H mode or standard mode"? That situation popped up yesterday when EP2LSH was on 14095 and not using F/H at the same time that C92RU was also operating in that segment.

It took me a few minutes of watching what was going on to convince me that EP2LSH was not using F/H. But afterwards, I was wondering if there is anything in the WSJT-X program which would have prevented me from working him if I was using F/H mode as Hound (assuming that he was transmitting even since I would be forced to transmit odd)? When a rare station pops up, pileups grow quickly, so time if of the essence.

73,

John, K9MM


locked Re: Format of Reports #GeneralGroupInfo

Julian
 

Thanks,

Julian,G3YGF

On 07/04/2021 14:15, Bill Somerville wrote:
Hi Julian,

you have it correct. Dual messages are also used for compound callsigns, in that case the "Prefer Type 1 Messages" is not relevant.

73
Bill
G4WJS.

On 07/04/2021 13:40, Julian wrote:

Ok, thanks.

Does that mean that if you tick the type 1 box, it will only send a callsign/4 digit locator and power, whether or not you enter a 6 digit locator in the settings box?

Presumably, if it only sends 4 digit locators, the distance will be to the centre of the IO80 square?

Is the "preferred type 1" actually a mandatory instruction to use type 1 then, or are there circumstances where it can still do otherwise?

Julian, G3YGF

On 06/04/2021 21:01, Bill Somerville wrote:
On 06/04/2021 20:16, Julian wrote:

Can someone please explain the significance of the callsigns being in <angle brackets>, the Locator getting truncated when the callsign is not in angle brackets, and the distance alternating, (58km is the correct one) on every alternate period on wsjt and FST4W 120/300?

I can't see any explanation in the manual...

Hi Julian,

if a user enters a 6 character gridlocator into WSJT-X then the 50-bit WSPR payload cannot covey that extra information, instead the single message WSPR format is switched to a dual message format where the callsign, 4 character gridsquare, and transmitter power are sent in the first, and a hash code representing the callsign, the 6 character gridlocator, and the power are sent in the second. So long as you have received the first message at some point, the hash code in the second message will be translated back to a callsign. The angle brackets tell you that the call was not in the message received.

If you have entered a 6 character gridslocator into WSJT-X but do not want to send the two message protocol then you can check the "Prefer Type 1 messages" option, as you have done.

73
Bill
G4WJS.






locked Re: Format of Reports #GeneralGroupInfo

Bill Somerville
 

Hi Julian,

you have it correct. Dual messages are also used for compound callsigns, in that case the "Prefer Type 1 Messages" is not relevant.

73
Bill
G4WJS.

On 07/04/2021 13:40, Julian wrote:

Ok, thanks.

Does that mean that if you tick the type 1 box, it will only send a callsign/4 digit locator and power, whether or not you enter a 6 digit locator in the settings box?

Presumably, if it only sends 4 digit locators, the distance will be to the centre of the IO80 square?

Is the "preferred type 1" actually a mandatory instruction to use type 1 then, or are there circumstances where it can still do otherwise?

Julian, G3YGF

On 06/04/2021 21:01, Bill Somerville wrote:
On 06/04/2021 20:16, Julian wrote:

Can someone please explain the significance of the callsigns being in <angle brackets>, the Locator getting truncated when the callsign is not in angle brackets, and the distance alternating, (58km is the correct one) on every alternate period on wsjt and FST4W 120/300?

I can't see any explanation in the manual...

Hi Julian,

if a user enters a 6 character gridlocator into WSJT-X then the 50-bit WSPR payload cannot covey that extra information, instead the single message WSPR format is switched to a dual message format where the callsign, 4 character gridsquare, and transmitter power are sent in the first, and a hash code representing the callsign, the 6 character gridlocator, and the power are sent in the second. So long as you have received the first message at some point, the hash code in the second message will be translated back to a callsign. The angle brackets tell you that the call was not in the message received.

If you have entered a 6 character gridslocator into WSJT-X but do not want to send the two message protocol then you can check the "Prefer Type 1 messages" option, as you have done.

73
Bill
G4WJS.



locked Re: Format of Reports #GeneralGroupInfo

Julian
 

Ok, thanks.

Does that mean that if you tick the type 1 box, it will only send a callsign/4 digit locator and power, whether or not you enter a 6 digit locator in the settings box?

Presumably, if it only sends 4 digit locators, the distance will be to the centre of the IO80 square?

Is the "preferred type 1" actually a mandatory instruction to use type 1 then, or are there circumstances where it can still do otherwise?

Julian, G3YGF

On 06/04/2021 21:01, Bill Somerville wrote:
On 06/04/2021 20:16, Julian wrote:

Can someone please explain the significance of the callsigns being in <angle brackets>, the Locator getting truncated when the callsign is not in angle brackets, and the distance alternating, (58km is the correct one) on every alternate period on wsjt and FST4W 120/300?

I can't see any explanation in the manual...

Hi Julian,

if a user enters a 6 character gridlocator into WSJT-X then the 50-bit WSPR payload cannot covey that extra information, instead the single message WSPR format is switched to a dual message format where the callsign, 4 character gridsquare, and transmitter power are sent in the first, and a hash code representing the callsign, the 6 character gridlocator, and the power are sent in the second. So long as you have received the first message at some point, the hash code in the second message will be translated back to a callsign. The angle brackets tell you that the call was not in the message received.

If you have entered a 6 character gridslocator into WSJT-X but do not want to send the two message protocol then you can check the "Prefer Type 1 messages" option, as you have done.

73
Bill
G4WJS.





locked #txaudio Elad FDM-Duo audio level #txaudio

Andy Talbot
 

I was reminded just now about some measurements I made on audio drive level to the Tx soundcard in the Elad  FDM-Duo.   

There is a small amount of ALC implemented close to max drive making the audio drive slider on WSJT-X give odd results on TF level out if it's varied during a Tx period.    

Just set it to maximum and don't play around with iut :-)


locked Re: Want to work a contest mode... #ContestMode

Jim Shepherd
 

Hi John,
  The WSJT modes are not allowed for the 7QP. You can run RTTY or PSK31 and that would make those running Digital happy with making a contact with you in Arizona.
73
Jim W6US
7QP Nevada Captain.


locked Re: Format of Reports #GeneralGroupInfo

Bill Somerville
 

On 06/04/2021 20:16, Julian wrote:

Can someone please explain the significance of the callsigns being in <angle brackets>, the Locator getting truncated when the callsign is not in angle brackets, and the distance alternating, (58km is the correct one) on every alternate period on wsjt and FST4W 120/300?

I can't see any explanation in the manual...
Hi Julian,

if a user enters a 6 character gridlocator into WSJT-X then the 50-bit WSPR payload cannot covey that extra information, instead the single message WSPR format is switched to a dual message format where the callsign, 4 character gridsquare, and transmitter power are sent in the first, and a hash code representing the callsign, the 6 character gridlocator, and the power are sent in the second. So long as you have received the first message at some point, the hash code in the second message will be translated back to a callsign. The angle brackets tell you that the call was not in the message received.

If you have entered a 6 character gridslocator into WSJT-X but do not want to send the two message protocol then you can check the "Prefer Type 1 messages" option, as you have done.

73
Bill
G4WJS.


locked Format of Reports #GeneralGroupInfo

Julian
 

Can someone please explain the significance of the callsigns being in <angle brackets>, the Locator getting truncated when the callsign is not in angle brackets, and the distance alternating, (58km is the correct one) on every alternate period on wsjt and FST4W 120/300?

I can't see any explanation in the manual...

Julian, G3YGF


locked Re: Want to work a contest mode... #ContestMode

Ron W3RJW
 

Further, if you were to read the rules, the exchange could be a 10 digit plus slash for a station operating on a county-line (i.e. UTRIC/IDBEA).   The rules permit 'digital' but in the context of this particular contest digital means PSK and RTTY.

Common sense must prevail.

http://ws7n.net/7qp/new/page.asp?content=rules
--
73
Ron  W3RJW

FTdx-5000, Timewave Navigator, WSJT-x 2.3.0, JTAlert 2.16.17, HRD Deluxe v6.7
FTdx-3000, SignaLink USB


locked Re: CQ MACRO #GeneralGroupInfo

Gary - AG0N
 



On Apr 6, 2021, at 9:37 AM, Karza <kari.sillanmaki@...> wrote:

OM. Just ditch the dots, ie enter "CQ USA yourcall yorlocator" into the TX6 field

Don’t forget to hit return after typing it in, or it won’t be saved for next time you want it.  Afterward, all you need to do is click the dropdown for TX6 and select it.

Gary - AG0N


locked Re: Push WSPRD on to GPU? #WSPR #raspberryPi

John
 


locked Re: CQ MACRO #GeneralGroupInfo

Karza
 

On 6.4.2021 10.50, Pedro Alonso via groups.io wrote:
How do I add U.S.A. To my CQ call?  I try saving it but it does not come out in the CQ call like other stations 
Thanks

OM. Just ditch the dots, ie enter "CQ USA yourcall yorlocator" into the TX6 field.

73's de Kari, oh2gqc



locked Re: Windows 10 installed programs list #install

Richard K0RDG
 

Generally speaking, if there are leftover listings in the add/remove programs list, and you click on uninstall, Win10 will first try to uninstall the program listed in the registry, and...not finding that version...will tell you that the program you are trying to uninstall does not exist and ask if you want to remove it from the add/remove programs list.  This just cleans up the leftover registry entry.

12881 - 12900 of 36727