|
locked
Clarification for Hound Mode
reg williams
I have used WSJT-X for some months now and have enjoyed using it. I have never used the fox/hound mode, so this is my first use of it, to try and work VP8PJ ft8 mode. I have set up hound mode correctly for the software and radio settings and will be transmitting higher up from 1000Hz. The radio is set for split operation. My best band for monitoring appears to be 40m so I have been listening very late at night for some hours. I see many stations being worked by VP8PJ in the band activity column but as of yet I have not seen the operator calling cq. I guess this is because his signal is to weak at my qth, which, at the moment I cannot detect any signal in his portion of the band 200Hz - 1000Hz, so until his signal is strong enough with me I will not get that cq call for me to respond and be able to join the crowd to work him. Just some clarification please to see if I am interpreting the situation correctly.
Reg
|
|
|
|
locked
Re: Working DX Stations
Jim Cooper
On 26 Feb 2020 at 21:20, Irwin Darack wrote:
Today I attempted to work the VP8PJThe fox will always be BELOW 1000 Hz, and callers have to be above 1000 Hz ... At least at my QTH, VP8PJ is always quite week ... I never saw them stronger than about -11 db ... They can use anywhere from one to five channels, and their signal goes down a lot when they use more than one channel (notice, they always call CQ using one channel !!) If you don't copy the fox between about 250 Hz and 650 Hz then you are probably not receiving them, in which case there is no point in calling them. fwiw, I spent all afternoon and most of the early evening Wednesday getting DECENT copy on VP8PJ but was never able to get even a first response from them ... I guess 40 watts to a hex beam just ain't makin' it !! w2jc
|
|
|
|
locked
Re: Station already worked, clarification
See attached. Do you use JTAlert? It's great. I let JTAlert do the coloring in conjunction with WSJTX. Green for new CQ. Grayed out for Worked B4. Red to LOTW. Works great for me. 73, Herb WB8ASI
On February 26, 2020 at 4:37 PM "Ryan Trullinger (KC0QNB)" <rt83021@...> wrote:
|
|
|
|
locked
Re: Alternate F1-F6 bindings
Hank Garretson
Thanks Steve. Contest Exuberantly, Hank, W6SX
On Wed, Feb 26, 2020 at 3:10 PM Steven Weeks via Groups.Io <swweeks=yahoo.com@groups.io> wrote:
|
|
|
|
locked
Re: Set up cq for specific area
I've seen calls for 2 states without a space....CQ NYMI....CQ NDWY... It doesn't take long to figure it out. Then poor Delaware need 3 characters...CQ DEL... or CQ DE just looks like a normal CQ. GL & 73, Herb WB8ASI
On February 26, 2020 at 7:56 PM Bruce Goldstein <wa3afs@...> wrote:
|
|
|
|
locked
Re: Working DX Stations
neil_zampella
Are you using DXPedition mode (Fox & Hound) ? You may want
to review the DXpedition User Guide found here: https://physics.princeton.edu/pulsar/K1JT/FT8_DXpedition_Mode.pdf
On 2/26/2020 9:20 PM, Irwin Darack
wrote:
|
|
|
|
locked
Re: Working DX Stations
First ensure you are in Fox/Hound mode.
toggle quoted messageShow quoted text
The Fox (DX Station) will ALWAYS transmit first/even. If you don’t hear him, don’t call. You must call above above 1000 Hz and have CAT control set up. When the DX responds to you, you will be shifted out of the pileup to a working frequency to complete the QSO. Watchdog times are much shorter. George J Molnar Arlington, Virginia, USA (702) 767-5420 KF2T - FM18lu
|
|
|
|
locked
Re: Whoops my log disappeared
George Armstrong
James,
In WSJT-X, click File, click "Open Log Directory". Drag your adi onto the log directory; you are done.
GA
From: WSJTX@groups.io <WSJTX@groups.io> on behalf of James Mockley via Groups.Io <jmockley@...>
Sent: Wednesday, February 26, 2020 8:42 PM To: WSJTX@groups.io <WSJTX@groups.io> Subject: [WSJTX] Whoops my log disappeared I accidentally removed my adi file from the app.
I still have the file on my desktop but can’t see a way to restore it.
|
|
|
|
locked
Whoops my log disappeared
Jim W7JMM
I accidentally removed my adi file from the app.
I still have the file on my desktop but can’t see a way to restore it.
|
|
|
|
locked
Working DX Stations
Irwin Darack
Today I attempted to work the VP8PJ station on 14.090. I am pretty good at FT8, but totally confused on the protocol. In the Decode box I see all the stations calling, but do not see the VP8PJ responding or calling. Any suggestions where to look would be appreciated. Thanks, Irwin KD3TB -- Irwin KD3TB
|
|
|
|
It is up to the operator to ensure the accuracy of what goes into your log. Always.
73 -Jim NU0C On Wed, 26 Feb 2020 08:12:59 -0800 "Steinar Fremme" <steinar@...> wrote: Sure I can , but why should it be necessary - I classify it as a bug in functionality.
|
|
|
|
locked
Re: WSJT-X stopped transmitting
Check under SETUP-FILE-AUDIO for the input and output and make sure the CODEC ones are picked. -- 73 de Amir K9CHP ARRL, Emergency Coordinator, Onondaga County, NY Radio Amateurs of Greater Syracuse www.ragsclub.org Wilderness SAR www.wsar.org (ret.) Eagle Valley Search Dogs www.evdogs.org (ret.)
On Wed, Feb 26, 2020, 18:05 <911eric@...> wrote: Hi guys,
|
|
|
|
locked
Re: Set up cq for specific area
Bruce Goldstein
Thank you for the suggestion. Will try it next time.
73
-- Bruce Goldstein, WA3AFS
AEC, Albany County ASEC, Eastern NY SKYWARN Regional Coordinator, NWS, Albany, NY Net Manager, ENY ARES/RACES Section Net
|
|
|
|
locked
Re: Set up cq for specific area
Gary - AG0N
On Feb 26, 2020, at 16:39, Bill Somerville <g4wjs@...> wrote:Thanks for the clarification on that Bill. I know there was a lot of discussion on that at the time but I didn’t realize where it finalized. 73, Gary - AG0N
|
|
|
|
locked
Re: Set up cq for specific area
Gary - AG0N
I’m pretty sure you can only use one at a time. — Gary - AG0N
toggle quoted messageShow quoted text
On Feb 26, 2020, at 16:25, Gilbert Baron <w0mn00@...> wrote:
|
|
|
|
locked
Re: Set up cq for specific area
On 26/02/2020 22:21, AG0N-3055 wrote:
On Feb 25, 2020, at 13:35, Martin G0HDB <marting0hdb@...> wrote: For example, you could edit the Tx6 message so that it reads 'CQ ASIA KC0QNB <yourgrid>' or, to call North Dakota, 'CQ ND KC0QNB <yourgrid>’.Too many characters. That’s why CQ AS…… works better. AS and others are “built-in” to the program and are recognized and dealt with. Gary - AG0N Gary, that's not correct for the FT8, FT4, and MSK144 modes. Those accept any word of up to four letters between the CQ and own callsign. They also accept a three digit number in the same place, that is for specifying a listening frequency in kHz within the MHz that the call is made in. You can test this behaviour with the useful command line utility ft8code that is shipped alongside the WSJT-X executable. Here are some examples: c:\>c:\WSJT\wsjtx\bin\ft8code "cq a g4wjs io91"
Message Decoded Err i3.n3
----------------------------------------------------------------------------------------------------
1. CQ A G4WJS IO91 CQ A G4WJS IO91 1. Standard msg
Message bits:
00000000000000000011111011000000010010001000000001111010000011111000010011001
Channel symbols (tones):
3140652000000744005530024507405422623140652735730242517204160442767132533140652
c:\>c:\WSJT\wsjtx\bin\ft8code "cq ab g4wjs io91"
Message Decoded Err i3.n3
----------------------------------------------------------------------------------------------------
1. CQ AB G4WJS IO91 CQ AB G4WJS IO91 1. Standard msg
Message bits:
00000000000000000100000010000000010010001000000001111010000011111000010011001
Channel symbols (tones):
3140652000001005005530024507405431733140652606135021640063310541100656723140652
c:\>c:\WSJT\wsjtx\bin\ft8code "cq abc g4wjs io91"
Message Decoded Err i3.n3
----------------------------------------------------------------------------------------------------
1. CQ ABC G4WJS IO91 CQ ABC G4WJS IO91 1. Standard msg
Message bits:
00000000000000000110111111010000010010001000000001111010000011111000010011001
Channel symbols (tones):
3140652000001674505530024507405423533140652572104547125470773723257563653140652
c:\>c:\WSJT\wsjtx\bin\ft8code "cq abcd g4wjs io91"
Message Decoded Err i3.n3
----------------------------------------------------------------------------------------------------
1. CQ ABCD G4WJS IO91 CQ ABCD G4WJS IO91 1. Standard msg
Message bits:
00000000000001010110110101010000010010001000000001111010000011111000010011001
Channel symbols (tones):
3140652000036663505530024507405432043140652146543333340075641012755734153140652
c:\>c:\WSJT\wsjtx\bin\ft8code "cq 456 g4wjs io91"
Message Decoded Err i3.n3
----------------------------------------------------------------------------------------------------
1. CQ 456 G4WJS IO91 CQ 456 G4WJS IO91 1. Standard msg
Message bits:
00000000000000000001110010110000010010001000000001111010000011111000010011001
Channel symbols (tones):
3140652000000256505530024507405437153140652367210375052735331742427254373140652
c:\>
Note that mixed letters and numbers are not permitted, nor are
symbols like '/', '.', or '?'. 73
|
|
|
|
locked
Re: Set up cq for specific area
It would be helpful if all of these built in codes were documented clearly. Maybe they are and I missed it.. While working for FT8 WAS I tried such as CQ ND WY or CQ NE ND SD or other things like that but some did not work As were too many characters.
FT8 is really great for increasing contact count and entity count but the 13 character limit is often very frustrating. For instance I would at times like to send a thank you or some short message with the final 73.
Outlook Laptop Gil W0MN Hierro candente, batir de repente 44.08226N 92.51265W EN34rb
From: WSJTX@groups.io <WSJTX@groups.io> On Behalf Of neil_zampella
Sent: Wednesday, February 26, 2020 17:10 To: WSJTX@groups.io Subject: Re: [WSJTX] Set up cq for specific area
I'm fairly sure that ASIA, DEL, and so on will work with the most recent versions of WSJT-X. On 2/26/2020 5:21 PM, AG0N-3055 wrote: On Feb 25, 2020, at 13:35, Martin G0HDB <marting0hdb@...> wrote:For example, you could edit the Tx6 message so that it reads 'CQ ASIA KC0QNB <yourgrid>' or, to call North Dakota, 'CQ ND KC0QNB <yourgrid>’.Too many characters. That’s why CQ AS…… works better. AS and others are “built-in” to the program and are recognized and dealt with.Gary - AG0N -- W0MN EN34rb 44.08226 N 92.51265 W Hierro candente, batir de repente HP Laptop
|
|
|
|
locked
Re: Alternate F1-F6 bindings
Steven Weeks <swweeks@...>
"I've
searched documentation and have found nothing on Alternate F1-F6 bindings. I can
select it under Settings/General, but what does it do. How does one use it in
various situations?"
I had the same
problem but finally found this in another document describing FT4 on the
website:
For keyboard control of transmitted messages, check the box Alternate F1–F6 bindings on the Settings | General tab. In typical contest-style operation you can then hit function key F1 to solicit a QSO by sending CQ. To respond to a CQ and send your contest exchange, double-click on the decoded message. Alternatively, you can click on Best S+P and let the selection algorithm choose a station to call. Auto Seq and Call 1st checkboxes behave as in FT8, and thus the remainder of a minimal QSO can continue without further operator action. Function keys F2 – F5 may be used to send messages displayed in entry fields for Tx2 – Tx5 on tab 1, at bottom right of the main window. Function key F6 toggles the checked status of Call 1st, and key combination Alt+B can be used to toggle the armed status of Best S+P.
73, Steve AA8SW
|
|
|
|
locked
Re: Set up cq for specific area
neil_zampella
I'm fairly sure that ASIA, DEL, and so on will work with the
most recent versions of WSJT-X.
On 2/26/2020 5:21 PM, AG0N-3055 wrote:
On Feb 25, 2020, at 13:35, Martin G0HDB <marting0hdb@...> wrote: For example, you could edit the Tx6 message so that it reads 'CQ ASIA KC0QNB <yourgrid>' or, to call North Dakota, 'CQ ND KC0QNB <yourgrid>’.Too many characters. That’s why CQ AS…… works better. AS and others are “built-in” to the program and are recognized and dealt with. Gary - AG0N
|
|
|
|
locked
RX issue in WSJT-X with 7300
n5lzb@...
Greetings from Seattle. My WSJT-X on Win 10, and with my 7300, were working fine until -- the decoding stopped working. I rechecked all of the settings and configurations are as they should be for my rig. I also switched the USB cable and verified that it is not the cable. I am able to TX and the two test buttons indicate proper connections.
|
|
|