Date   

locked Re: Station already worked, clarification

Bill Somerville
 

On 26/02/2020 21:37, Ryan Trullinger (KC0QNB) wrote:
I have the show DXCC, grid and worked before status checked, I have seen callsigns show up that I know that I have worked, before, what differentiates worked before status from a standard green CQ line? I'm a newbie, but it would make sense to make a worked before. I don't see an option in the Decode Highlighting dialog, to do that. I am looking at the manual this very minute, but not finding what i am looking for.


Ryan, KC0QNB, DN90WW. Gothenburg, NE
Hi Ryan,

the WSJT-X highlighting logic does not specifically highlight worked before stations, it highlights stations calling CQ or QRZ that you may want to work. If you enable the "New Call" and "New Call on Band" highlighting then you have the information you need. Worked before stations will not be highlighted as new calls, i.e. their CQ calls will be highlighted with the "CQ in Message" colouring (light green background by default).

Note that you get more information with this scheme that simply worked before. If a station has been worked before but not on the current band then you get the "New Call on Band" highlighting. If a station has not been worked before on any band then you will get the "New Call" highlighting. Optionally you can filter highlighting by the current mode or you can consider all modes as equivalent.

73
Bill
G4WJS.


locked Re: send redo

Gary - AG0N
 

On Feb 25, 2020, at 13:48, Augustine Brace <aug1021hunt@...> wrote:

Is it suppose to be this frequent almost every contact
Is there anything i can do

“More Power, Scotty!”

Gary - AG0N


locked Station already worked, clarification

Ryan Trullinger (KC0QNB)
 

I have the show DXCC, grid and worked before status checked, I have seen callsigns show up that I know that I have worked, before, what differentiates worked before status from a standard green CQ line? I'm a newbie, but it would make sense to make a worked before. I don't see an option in the Decode Highlighting dialog, to do that. I am looking at the manual this very minute, but not finding what i am looking for.


Ryan, KC0QNB, DN90WW. Gothenburg, NE


locked Re: F&H question

Joe
 

Hi John,

As mentioned in the WSJT-X User Guide:
"Be sure to read the operating instructions for FT8 DXpedition Mode."

 -- 73, Joe, K1JT


locked Re: ft8 fox and hound

neil_zampella
 

Are you saying that following your ODD Tx time, you see nothing on the EVENs, then the next ODD Tx time (evidently you disabled the Transmit button) you don't see anything either?

You may or may not see anything on the EVEN as that's when the FOX should be transmitting.  If you're not seeing anything from the FOX, you're not hearing the fox so you shouldn't be trying to reply to the fox.

Neil, KN3ILZ

On 2/26/2020 8:49 AM, oels@... wrote:


--
I use wsjtx 2.1.2 with Ic-7300 for Ft8 for a couple of years now, it works fine. I have an issue when I go to fox and hound. When I enable the transmit button after I make my call for 15 seconds it stops transmitting like it is suppose to, but then takes 30 seconds to hear receiving signals again or to see signals starting on the graph again. Any ideas Kb0wlt.

    


locked Re: Set up cq for specific area

 

Thanks Martin,

I don't normally have the TX1 etc tab open so I wasn't aware of it.

73 Phil GM3ZZA

On 25 Feb 2020 20:35, Martin G0HDB <marting0hdb@...> wrote:
You can edit the default Tx6 message of 'CQ KC0QNB <yourgrid>' and add up to 4 characters immediately after the CQ; the extra characters can be either numeric or alphabetic but not a mix of the two.

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>'.

The edited version of the Tx6 message will stick for the duration of a WSJT-X session but if you close and then restart WSJT-X then the Tx6 message will revert to the default.

HTH,

--
Martin G0HDB


--
73 Phil GM3ZZA


locked Re: F&H question

Ken - K4XL
 

John,
All of your questions...and probably some that you haven't thought of can be answered by having a quick read of this manual:
73,
Ken - K4XL


On Wed, Feb 26, 2020 at 11:53 AM John Morphet <jmorphet@...> wrote:
I am new to using fox and hound. I was trying it out yesterday. In hound mode, WSJT-X would transmit the TX1 message a few times and then stop. Is that normal? Should I just enable transmit again?

I also noticed that fox was changing frequency. What would be the best way to adjust so that the RX Frequency window will show what he is doing? Normally I would just double click on one of his calls, but I am not sure if that creates problems in fox and hound mode.

John, WØZI


--
Ken - K4XL
BoatAnchor Manual Archive
BAMA - http://bama.edebris.com


locked Re: Installing WSJT on Windows 10 computer

Herb Blue - WB8ASI
 

Tnx Dave,  I've got things back to normal.  Disconnected everything and got each working on its own.  Had to revise the new path to HamPrograms folder in a few places I missed the first time around.  Hooked everything back together one step at a time, and I'm back in business.  Haven't yet added OmniRig since it was a recent addition for me, and knew everything worked beforehand.  I'll try adding it again soon, but happy to be done pulling my hair out for now.  Also need to add back multiple displays, and hope that doesn't introduce problems.  73, Herb WB8ASI

On February 26, 2020 at 8:56 AM "Dave_G0WBX via Groups.Io" < g8kbvdave@...> wrote:


Dave,   I really like the sound of your suggestion to put all my ham
programs into their own folder.   I found that some don't give you a
choice.  So now I have some in my new HamPrograms folder, and some in
Programs 86 folder.   Now can't seem to get things working again.  Rig
goes to TX when I try to open WSJTX.  Rig goes into TX randomly.  Do my
ham apps need to be all in the same folder?  Right now I've got a mess.
Only just realized I don't have "restore point" turned on.  I'm still
good on CW, but any advice how to recover would be much appreciated. 
73, Herb WB8ASI

~ ~ ~

Herb.

The dedicated "HamPrograms" folder has worked well for me in the past,
when I was using Win7, as that OS too "protects" "Program Files" and
"Program Files(x86)" so that they can't write to their own folders, as
many older (and some newer but porly written) software tools do.

So long as the individual programs are working correctly, they can be in
any folder anywhere you want (within reason!)

The random TX'ing.

Is that when the machine starts up, and/or when a USB device is
introduced, or removed?  If so, then whatever device you have to key the
radio, is probably using a virtual serial port handshake line (RTS or
DTR) to work the PTT.  They will flap about whenever Windows (or Linux
for that matter!) "Re-Enumerates" (re-discovers) the attached USB devices.

Now, if you have a USB device that croaks in the presence of RF, that
will in essence "disappear" from view, so the OS may well go through the
re-enumerating process, and again when it recovers and re-presents itself.

I've seen that behaviour cause utter mayhem in a shack when a HF radio
was setup to use a 10FM repeater, the PC and radio went utterly potty to
say the least, until the rig was turned off.  (Other than the OS, no
other software was running on the computer.)

The only real cure, is to make sure that you have minimal RF in the
shack, and/or that all the USB devices (and other attached toys) are as
immune to RF as they can be.   Sadly, quite a few "big name" ham
accessories are not as immune to RF as you might expect.

Ground bonding does not always help.  In some cases, can actually make
things worse.  But if you try and keep the "Loop Area" formed between
multiple cables interconnecting things to a minimum, that does generally
help.

All the best..

Dave G0WBX.


--
Created on and sent from a Unix like PC running and using free and open source software:


locked FT4 and FT8 Contesting

Joe
 

Log checking for several recent contests that used the FT4 and FT8 modes has shown undesirably large numbers of claimed QSOs that receive not-in-log ("NIL") status from the other station. The WSJT development team has worked together with contest sponsors and log checkers to analyze the probable causes of these NILs. Our findings and some operating advice for future contests are posted here:
http://physics.princeton.edu/pulsar/k1jt/FT4_FT8_Contesting.pdf
and will also appear in the May-June 2020 issue of NCJ, the National Contest Journal.

73 from the authors of the study:

Steve Franke, K9AN
Don Hill, AA5AU
Ed Muns, W0YK
Iztok Saje S52D
Joe Taylor, K1JT


locked Re: Start-Time and End-Time of a FT8 QSO #FT8

Knut Steinar Fremme OE4KSF
 

Ok, I will try the Esc key , but I find also entries that do have other QSO's in between - that is what really concerns me .

I'm just sitting and editing my logs in MacLogger - and find 1 out of 100 (About) to be wrong - and most of them have other QSO's in between.

So if what you say is the case - then the problem is something else - that it doesn't record the correct start time - but pics something else .
I have checked the logs ALL.txt for a few of the wrong entries to see if the problem could be in transferring the log entry into MacLogger, but it's wrong also there - it has the correct start time for the new call in there. 
Luckily MacLogger is setting the time On column entry in Bold when it sees a timing wish is possible wrong - so now I'm looking for them 

73 Knut OE4KSF


locked F&H question

John Morphet
 

I am new to using fox and hound. I was trying it out yesterday. In hound mode, WSJT-X would transmit the TX1 message a few times and then stop. Is that normal? Should I just enable transmit again?

I also noticed that fox was changing frequency. What would be the best way to adjust so that the RX Frequency window will show what he is doing? Normally I would just double click on one of his calls, but I am not sure if that creates problems in fox and hound mode.

John, WØZI


locked ft8 fox and hound

oels@...
 


--
I use wsjtx 2.1.2 with Ic-7300 for Ft8 for a couple of years now, it works fine. I have an issue when I go to fox and hound. When I enable the transmit button after I make my call for 15 seconds it stops transmitting like it is suppose to, but then takes 30 seconds to hear receiving signals again or to see signals starting on the graph again. Any ideas Kb0wlt.


locked Re: Start-Time and End-Time of a FT8 QSO #FT8

Bill Somerville
 

On 26/02/2020 16:12, Steinar Fremme wrote:
Sure I can , but why should it be necessary - I classify it as a bug in functionality.

And yes - I just set the start time - 1 minute before end-time - and then all is ok.

Now when I know about - i'm checking everyone of them  -
and even started to edit old logs in QRZ - and are getting quite a few new confirmations - now that I'm aware of it.

But when you have a pile up - it takes time - and easy to overlook - and should not be necessary at all.
 
I have close to 17.000 FT8 QSO's now - and when the conditions on 20m is as it has been a few days now - easy to overlook this problem.

Also to mention - I have other QSO's in between the two with the same station - and impossible to remember if I have seen this station before today.

Well , that is my meaning anyway - and I still do classify it as an design flow 

73 Knut OE4KSF

Knut,

this will only happen if you have no intervening QSOs.

If you abandon a QSO then hit the ESC key, this will forget the abandoned QSO details.

73
Bill
G4WJS


locked Re: Start-Time and End-Time of a FT8 QSO #FT8

Knut Steinar Fremme OE4KSF
 

Sure I can , but why should it be necessary - I classify it as a bug in functionality.

And yes - I just set the start time - 1 minute before end-time - and then all is ok.

Now when I know about - i'm checking everyone of them  -
and even started to edit old logs in QRZ - and are getting quite a few new confirmations - now that I'm aware of it.

But when you have a pile up - it takes time - and easy to overlook - and should not be necessary at all.
 
I have close to 17.000 FT8 QSO's now - and when the conditions on 20m is as it has been a few days now - easy to overlook this problem.

Also to mention - I have other QSO's in between the two with the same station - and impossible to remember if I have seen this station before today.

Well , that is my meaning anyway - and I still do classify it as an design flow 

73 Knut OE4KSF


locked Re: Start-Time and End-Time of a FT8 QSO #FT8

Jim Cooper
 

On 25 Feb 2020 at 21:45, Steinar Fremme wrote:

> When I then look at the entries I
> find that the start-time for the log
> entry is the start time for the
> FIRST QSO, that did not succeed , and
> the end-time is the end-time for the
> QSO that did succeed

when the WSJT-X "Log QSO" window
pops up, there is a place to show both the
start and end time of the contest.

Why don't you just edit that before
you click OK ?

The problem I see is that you do not know
what time the other station is using to log
your exchange, but it is probably closer to
your END time ... since that is when the
contact is actually "real".

w2jc

graphic

  


locked Re: Tip for setting up your speakers with FT8, etc. #AudioIssues #AudioIssues

Mick
 

Lots of good stuff here, but I really like the cold cerveza tip
--
73
Mick VA3EPM


locked Re: Installing WSJT on Windows 10 computer

Dave_G0WBX
 

Dave,   I really like the sound of your suggestion to put all my ham
programs into their own folder.   I found that some don't give you a
choice.  So now I have some in my new HamPrograms folder, and some in
Programs 86 folder.   Now can't seem to get things working again.  Rig
goes to TX when I try to open WSJTX.  Rig goes into TX randomly.  Do my
ham apps need to be all in the same folder?  Right now I've got a mess.
Only just realized I don't have "restore point" turned on.  I'm still
good on CW, but any advice how to recover would be much appreciated. 
73, Herb WB8ASI

~ ~ ~

Herb.

The dedicated "HamPrograms" folder has worked well for me in the past,
when I was using Win7, as that OS too "protects" "Program Files" and
"Program Files(x86)" so that they can't write to their own folders, as
many older (and some newer but porly written) software tools do.

So long as the individual programs are working correctly, they can be in
any folder anywhere you want (within reason!)

The random TX'ing.

Is that when the machine starts up, and/or when a USB device is
introduced, or removed?  If so, then whatever device you have to key the
radio, is probably using a virtual serial port handshake line (RTS or
DTR) to work the PTT.  They will flap about whenever Windows (or Linux
for that matter!) "Re-Enumerates" (re-discovers) the attached USB devices.

Now, if you have a USB device that croaks in the presence of RF, that
will in essence "disappear" from view, so the OS may well go through the
re-enumerating process, and again when it recovers and re-presents itself.

I've seen that behaviour cause utter mayhem in a shack when a HF radio
was setup to use a 10FM repeater, the PC and radio went utterly potty to
say the least, until the rig was turned off.  (Other than the OS, no
other software was running on the computer.)

The only real cure, is to make sure that you have minimal RF in the
shack, and/or that all the USB devices (and other attached toys) are as
immune to RF as they can be.   Sadly, quite a few "big name" ham
accessories are not as immune to RF as you might expect.

Ground bonding does not always help.  In some cases, can actually make
things worse.  But if you try and keep the "Loop Area" formed between
multiple cables interconnecting things to a minimum, that does generally
help.

All the best..

Dave G0WBX.


--
Created on and sent from a Unix like PC running and using free and open source software:


locked Start-Time and End-Time of a FT8 QSO #FT8

Knut Steinar Fremme OE4KSF
 

Start-Time  and End-Time of a FT8 QSO
 
I have been using WSJT-X together with MacLoggerDX for a year now, and wherry happy about how it works.
 
But I have been a thing that I have not understood for a while, and that is why some of my QSO when sendt to QRZ was not confirmed when they should.
 
Yesterday I found the reason.
 
If I first have someone calling me, but in bad conditions and he is not receiving my RR73 or I’m not receiving his 73 
Then after 3 hours we try again - and at this time we do succeed - and RR73 + 73
I’m sending the QSO to MacLoggerDX - that again is sending the entry to QRZ and LoTW
 
When I then look at the entries I find that the start-time for the log entry is the start time for the FIRST QSO, that did not succeed , and the end-time is the end-time for the QSO that did succeed 
 
And when the caller is sending his entries to QRZ and/or LoTW - there is no match - because of the wrong Start-Time 

Regards and 73  Knut  OE4KSF


locked Re: Set up cq for specific area

Jim Campbell <jim@...>
 

Bruce,

I've been away from WSJT for a couple of years so I'm rusty but would USDE or DEUS perhaps work?

73

Jim - W4BQP
first licensed in 1953 as W4BQP/WN4BQP

On 2/25/2020 8:36 PM, Bruce Goldstein wrote:

I use 'directed' FT8 CQs quite often with mixed results....

I need Delaware on 15M for WAS and a CQ DE WA3AFS FN32 does not work very well as the DE is misunderstood a bit of the time and the result is that my log is filling rapidly with a lot of PY qsos (which I do not mind).  CQ DEL WA3AFS FN32 ends up with the same result!

I also need Vermont on 30M and even though I can just about see Vermont from my QTH I seem to collect a lot of EU qsos when CQ VT WA3AFS FN32.

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: send redo

Jim Brown
 

On 2/25/2020 5:09 PM, George J Molnar wrote:
I’d recommend three things.
Great advice on all counts, George!

I'll also add "RTFM" and study the ARRL Handbook to learn as much as possible about how radio and electronics work.

73, Jim K9YC