Date   

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.


Pedro Alonso
 

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


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

Carl - WC4H
 

Bonjour Radi.

One nice thing about ADIF is that as long as each field contains he correct tag, the "structure" does not matter.  The fields could be in any sequence in the ADIF file.

Also, the easiest way I found to move the QSOs for specific dates from one file to the other is just to cut and paste.  ADIF Master is not needed for that.

À bientôt.
73.
Carl - WC4H


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

Jim Brown
 

On 4/5/2021 7:23 PM, JP Tucson, AZ wrote:
I am looking forward to working the 7QP (7th Area QSO Party) on May 1-2.
First, you should study the contest rules to learn if WSJT QSOs are accepted. Our 4-man team has been lighting up 6-7 rare counties in this event for about 5 years; we've had to skip last year and this because we live in along the California coast, and don't trust the folks who live in those remote counties to provide safe public accommodations we would need to us. We work CW and SSB only, and while I use JT modes a lot and contest a lot, the bug hasn't bit me to use them in HF contesting. On 6M, a lot. :)

73, Jim K9YC


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

neil_zampella
 

It sounds easy, but its not.       The Tx1 transmission can actually do more than 13 characters because its setup to use certain encode/decode 'codes' to keep the entire Tx in the 77 bit limit.     Adding all those letters is not possible as it would involve having to do major changes to the the system, and it would not be feasible.  

As the developers have said before, they added contest modes that are international in scope, and easily built into the existing system.   Trying to cover the rules for every single QSO 'party' would be a nightmare.

Neil, KN3ILZ

On 4/5/2021 9:23 PM, JP Tucson, AZ wrote:
Hello FT8 crew,

I am looking forward to working the 7QP (7th Area QSO Party) on May 1-2. 

However, a friend & mentor brought up this; "I’m not sure the FT
modes can handle the exchange, which is RS(T) plus 5 letter state/county code. For example if
you operate from Pima County, your exchange will be: 599 AZPMA."

In looking at how the Roundup works; which already uses RST, I would like to request please that it would be great if you could add an QSO Party mode to the Advanced section for contests.

If you replace the grid square with the 5 digit county/state code (the list is on the 7QP page) on the first call (TX1), and replace the R-xx with the RST as you do with the RU mode, it should be a very simple addition. 

I think we would all appreciate that, as I believe most, if not all QSO Parties use a similar layout.

Thank you, 

73 - John - N7GHZ




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

JP Tucson, AZ
 

Hello FT8 crew,

I am looking forward to working the 7QP (7th Area QSO Party) on May 1-2. 

However, a friend & mentor brought up this; "I’m not sure the FT
modes can handle the exchange, which is RS(T) plus 5 letter state/county code. For example if
you operate from Pima County, your exchange will be: 599 AZPMA."

In looking at how the Roundup works; which already uses RST, I would like to request please that it would be great if you could add an QSO Party mode to the Advanced section for contests.

If you replace the grid square with the 5 digit county/state code (the list is on the 7QP page) on the first call (TX1), and replace the R-xx with the RST as you do with the RU mode, it should be a very simple addition. 

I think we would all appreciate that, as I believe most, if not all QSO Parties use a similar layout.

Thank you, 

73 - John - N7GHZ


locked Push WSPRD on to GPU? #WSPR #raspberryPi

John
 

WSPRD is the WSPR decode program in WSJT-X. At times, in a single WSPR cycle, I decode 48 spots from 26 channels using KIWI sdr receivers and wsprdaemon by Rob Robinett, AI6VN. I use a Raspberry pi 4 for the control and decoding. The pi can run at 100% CPU  for 100 seconds when the bands are active.
The big spotters, more than 10,000 spots per day, use i7 x86 machines. I don't have a spare i7 machine. I do have an Nvidia Jetson Nano 4GB card with a GPU with 128 cores. The new 2GB card is $60 on Amazon. I am hopeful that someone will take the challenge to push wsprd code onto the GPU. I can dream of three Phases, any or all of which may receive the "No-Way" from Joe Taylor or others in the know.

Phase 1:  Keep the program in the current serial mode and only push DSP functions,(FFT) and the like down into the GPU. I am hopeful that the existing library functions will run the same functions at 1/10th the time. There could be time to run all 26 bands serially. 

Phase 2: Can the GPU run 2 or more copies of the wsprd code concurrently with all those cores?

Phase 3: recode so that sub-tasks run in parallel.

My programming abilities are far too aged to offer any help. I started in 1965 with IBM1401 Autocoder and retired with PLI, no help with C and GPUs.

Comments?
Offers to code?

John
73
TI4JWC
 
 


locked Re: Should I see my FT8 transmitted signal on the Wide Graph display? #transmit

km5gn@...
 

There was a bug here where if you tried to transmit using split on the rig it didn’t work.

On Apr 5, 2021, at 4:23 PM, Pat Turcotte via groups.io <patmail01@...> wrote:

I just downloaded WSJT-X. So I am a complete newbie.

I'm in an apartment using a Flex 6400 and a Buddistick antenna. When I CQ on FT8 I have been getting no responses. The rig thinks everything is working properly.

Should I see my transmitted signal on the Wide Graph display?

Thanks for your input.

73,
Pat - N4ENF

11581 - 11600 of 35420