Date   

Re: Cat Control Yaesu FTDX-5000 #Cat_RigControl

Louis Alexander
 

Bill, 2 things here.  My Yaesu FTDX5000 has a CAT lite that is enabled when its com port is being used by WSJX and anytime CAT is on the lite stays on and second I am using Virtual Serial Port Emulator and I see all the com ports and there activity levels.  Looks like a good idea that you could cut the CAT control loose from WSJT but do not see any shortcut that actually does that.


Re: Cat Control Yaesu FTDX-5000 #Cat_RigControl

Bill Somerville
 

On 04/02/2021 11:08, Louis Alexander wrote:
For some reason or another that does not release the CAT, it just stops the software from receiving.  The way the older software worked for me was that if the frequency you shifted to was not in the frequency list then the green band button lite would turn red but nothing else would happen in the program.  I think v 2.2.2 was the last version that ran that way.  Once the FST4, etc versions came out then that's when I started to notice the change frequency problems.
Hi Louis,

what makes you think active CAT control is not relinquished when "Monitor" is not enabled?

73
Bill
G4WJS.


Re: Cat Control Yaesu FTDX-5000 #Cat_RigControl

Louis Alexander
 

For some reason or another that does not release the CAT, it just stops the software from receiving.  The way the older software worked for me was that if the frequency you shifted to was not in the frequency list then the green band button lite would turn red but nothing else would happen in the program.  I think v 2.2.2 was the last version that ran that way.  Once the FST4, etc versions came out then that's when I started to notice the change frequency problems.


Re: Multiple Instances of WSJTX .. #FT8 #WSJTX_config

Karza
 

Dave,

On 4.2.2021 0.10, Dave H wrote:
What I'm not clear on.? Will I end up with "2" wsjt-x adi files or is there a single shared file.

you will end up with 2 wsjtx_log.adi and wsjtx.log files.

73's de Kari, oh2gqc


Re: Multiple Instances of WSJTX .. #FT8 #WSJTX_config

Amos Sobel 4X4MF
 

Dave

 

I am using a instance of JtAlet with each instance of WSJT-X. JtAlert does log into common Log4OM.

 

Amos 4X4MF

 

 

From: main@WSJTX.groups.io <main@WSJTX.groups.io> On Behalf Of Dave H
Sent: Thursday, February 4, 2021 12:10 AM
To: main@WSJTX.groups.io
Subject: [WSJTX] Multiple Instances of WSJTX .. #FT8 #WSJTX_config

 

Hello,

I want to run multiple Instances of WSJTX, I found that I need to create 2 shortcuts with the following added

wsjtx --rig-name=FT-991 

wsjtx --rig-name=FT-891 

What I'm not clear on.? Will I end up with "2" wsjt-x adi files or is there a single shared file.

Just trying to think ahead for getting wsjt-x to Log into Log4OM

Thanks...


Re: Is this supposed to happen? #FoxAndHound #IssueReport

David Piersall
 

You've given a very good description of how Dxpedition mode works. Three strikes and you're out, as we say in the US. 
If the Fox doesn't complete with you, you get kicked into the weeds where you won't bother him any more. Immediately go back above 1000 and start over. I've certainly been there and done that.

Dave, N6ORB


Re: Call sign not being recognized as work before question #FT8 #logging

Pat
 

Hi Bill
2.2.2


Re: Call sign not being recognized as work before question #FT8 #logging

JP Tucson, AZ <samcat88az@...>
 

Hi Ken,

Thanks for pointing that out, about the 0 to 4 change in the adi, I forgot to mention that!

By the way, it happens on straightforward (no interruptions) qso's too! 

The manual correction is great, but we shouldn't have to do that; and frankly, it really bogs down the whole flow during a contest!



On Wed, Feb 3, 2021 at 6:32 PM Kenneth Williams <ken.williams@...> wrote:
I have also experienced the gridsquare problem. Here is a pointer to the info that I received about it: https://wsjtx.groups.io/g/main/topic/79467242#20294

Basically, it says that if a QSO  is not a pretty straightforward exchange, and has interruptions, then wsjt-x will not remember everything that happened in the past.  e.g., start a QSO, get interrupted by another one and then return to the original QSO, wsjt-x will not have remembered the gridquare.  When the logging window pops up, the grid will be empty and unless you plug in a value, the adif file will contain <gridsquare:0> and no value.

In certain cases, such as having had only one contact in a grid and failing to capture the grid in the log, the program probably  says "I don't have any contacts in that grid so therefor any new contact from that grid must also be a new contact' and reports this to you through the color of the CQ.

You can edit the adif file; just remember to change the '0' to '4' when adding the grid information (The number represents the number of characters in the grid).

I have since trained myself to be more diligent about manually entering the grid.

Ken
KC6PUQ




--
73 - John - N7GHZ



Re: #WSJTX_config #WSJTX_config

Monty Wilson, NR0A
 

Thanks Laurie,

 

Neil, KN3ILZ got be running again.  Now I can move on to getting JTAPPS and HRD logbook talking to each other again.

 

Cheers…. Monty, NR0A

 

From: main@WSJTX.groups.io <main@WSJTX.groups.io> On Behalf Of HamApps Support (VK3AMA)
Sent: Wednesday, February 3, 2021 06:24 PM
To: main@WSJTX.groups.io
Subject: Re: [WSJTX] #WSJTX_config

 

On 4/02/2021 9:45 am, Monty Wilson wrote:

Unable to communicate with the WSJT-X process.

  UDP Port : 2333

  IP Address : 239.255.0.0

  Values read from WSJT-X config file...

    C:\Users\jwils\AppData\Local\WSJT-X\WSJT-X.ini


Looks like you have been playing with your WSJT-X UDP settings. Port 2333 is the default for the secondary UDP Server (depreciated). JTAlert uses the primary settings, and according to your error message is reading 2333. That looks wrong. My guess, without see your actual settings dialog, is that you have both the primary and secondary UDP servers set to use port 2333. Try changing back to the defaults, 2237 for the primary and 2333 for the secondary and don't enable the secondary server.

   

de Laurie VK3AMA


Re: Call sign not being recognized as work before question #FT8 #logging

Kenneth Williams
 

I have also experienced the gridsquare problem. Here is a pointer to the info that I received about it: https://wsjtx.groups.io/g/main/topic/79467242#20294

Basically, it says that if a QSO  is not a pretty straightforward exchange, and has interruptions, then wsjt-x will not remember everything that happened in the past.  e.g., start a QSO, get interrupted by another one and then return to the original QSO, wsjt-x will not have remembered the gridquare.  When the logging window pops up, the grid will be empty and unless you plug in a value, the adif file will contain <gridsquare:0> and no value.

In certain cases, such as having had only one contact in a grid and failing to capture the grid in the log, the program probably  says "I don't have any contacts in that grid so therefor any new contact from that grid must also be a new contact' and reports this to you through the color of the CQ.

You can edit the adif file; just remember to change the '0' to '4' when adding the grid information (The number represents the number of characters in the grid).

I have since trained myself to be more diligent about manually entering the grid.

Ken
KC6PUQ


Re: Is this supposed to happen? #FoxAndHound #IssueReport

Dave Garber
 

I have had this done to me too, and believe it to be normal operation


Dave Garber
VE3WEJ / VE3IE


On Wed, Feb 3, 2021 at 7:06 PM Tony Collett via groups.io <tony.nbs=btinternet.com@groups.io> wrote:
Hi Group
I had an intriguing experience yesterday calling a Fox on 30m

When my call was selected my Tx was correctly moved to the Fox frequency but he was not seeing my report so he kept sending his report to me while I responded with his report for 3 periods.

On the 4th period he dropped my call and went on to work a different station - my first failure to work an F&H QSO !

What I didn't expect was that my transmitter was moved off the Fox frequency to a different one (but still below 1000Hz) and WSJT kept sending my report to the Fox. It continued to do this for some time and the timer didn't come into operation which it does when you are just calling the Fox. 

Eventually I manually stopped the transmission, moved my frequency back above 1000Hz and started calling anew.
Glad to say I was selected and completed a short while later....

My question - is it supposed to continuously send a report to the Fox after the QSO has been abandoned - (I can check my all.txt file to see just how long).
The Fox called CQ several times before I stopped WSJT sending the report as it was obvious he wasn't seeing me or going to come back with the RR73 I needed.
If I had let it continue would the Fox eventually have picked me up while transmitting a report in "no mans land"?

For the record I was using V2.2.2
Thanks
Tony G4NBS



Re: #Install #BugReport #WSJTX_config WSJT-X not working after 2.3.0 install #install #IssueReport #WSJTX_config

Jim Pruitt
 

That (plug in USB dongle or the onboard sound card) does not even show up!  The ONLY inputs and outputs listed is my Microsoft USB boom headphone/mic.  No other options appear now.  And I was not using the computer sound card I was using a plug in usb dongle!  I am using a plug in usb dongle soundcard and it was working but no longer an option so exactly what do I do since no sound card now shows up to pick from?

Thank you.

Jim Pruitt
WA7DUY


On 2/3/2021 3:07 PM, Bill Somerville wrote:
On 03/02/2021 21:34, Jim Pruitt wrote:
I was decoding using WSJT-X 2.2.2 (64 bit) and today I installed the newest 2.3.0 (64 bit)  When I did WSJTX stopped working.  The waterfall is totally blank (not a single signal showing up despite LOTS of activity on the frequency.  Looking at the configuration had the Audio Soundcard input first as Default device Not found and then it showed it as blank and now it is back to not found. The USB sound card dongle was working with 2.2.2 but is not even seen by 2.3.0 and the dongle is flashing with the audio input.  How do I get it working?  Or should I just re install 2.2.2?

Thank you.

Jim Pruitt
WA7DUY

Hi Jim,

to try and dissuade users from using the same sound card for WSJT-X and for operating system or other application audio, we no longer offer the default sound card as an option. You must select the sound card that is connected to your rig.

73
Bill
G4WJS.






Re: Cat Control Yaesu FTDX-5000 #Cat_RigControl

Bill Somerville
 

On 04/02/2021 00:44, Louis Alexander wrote:
Hey Bill, well sometimes when I am sitting here monitoring 630 meters or other frequencies I occasionally want to monitor another frequency.  In the older versions such as 2.2 or 1.8, this was allowed without upsetting the wsjt program.  But now it totally is a no no.  I have loaded the newest tonight, 2.4.0 rc-1 and at least it is working for me as long as I do not push the band stack buttons.  I suppose I will have to discipline myself to a new way of doing things. Thanks for all your tedious and hard work.  I have been using WSPR etc for a good while now and enjoy seeing the new modes develop.
Hi Louis,

if you want WSJT-X to relinquish active CAT control click the "Monitor" button, to re-enable click it again.

73
Bill
G4WJS.


Re: Cat Control Yaesu FTDX-5000 #Cat_RigControl

Louis Alexander
 

Hey Bill, well sometimes when I am sitting here monitoring 630 meters or other frequencies I occasionally want to monitor another frequency.  In the older versions such as 2.2 or 1.8, this was allowed without upsetting the wsjt program.  But now it totally is a no no.  I have loaded the newest tonight, 2.4.0 rc-1 and at least it is working for me as long as I do not push the band stack buttons.  I suppose I will have to discipline myself to a new way of doing things. Thanks for all your tedious and hard work.  I have been using WSPR etc for a good while now and enjoy seeing the new modes develop.


Re: Call sign not being recognized as work before question #FT8 #logging

JP Tucson, AZ <samcat88az@...>
 

Pat, 

I am having a very similar issue with situations like this.

Go to your .log file and search for your target station, as you reported... - K4TY
Once you find it; check that ALL of the needed QSO info is there!
I.e. date & time (virtually always there); frequency - ditto; mode - ditto, BOTH signal reports (sometimes NOT transferred), and
    the biggie for me that I have found over & over, check for his GRID SQUARE!  I have noticed A LOT of my qso's do NOT have the GS's recorded!
It happens especially a lot during contest modes - where the log box will NOT move on until you manually insert the signal report & grid square. 

They appear to not be getting transferred properly from the wsjtx program to ITS OWN log box!  It then doesn't get transferred to either the .log or the .adi file!

Without it being sent to the adi file, it won't register as being worked

IF you find this is the case, please report that back to the forum; as some people seem to think it isn't happening - despite the fact that folks are & have been reporting errors in logging, not being recorded as worked (as in your case), etc.

Also, if you do find that this is the case that say... the grid square isn't being logged as it should; you can easily - manually input the info into your .txt .log file. The adi file too, but to open it, you need to add a .txt to the end of the filename so you can open it with your text editor, again manually input the info & re-save the file. Don't forget to remove the .txt from the filename  that you previously added.

Then go into file>settings>COLORS, and in the lower right portion, hit the RESCAN ADIF button.  Once you do that, the next time you see K4TY, it should show as GREEN (assuming you having changed that color).

Good luck, I hope this helps you find & correct the issue.

John- N7GHZ


On Wed, Feb 3, 2021 at 5:06 PM Pat via groups.io <n7uvh=yahoo.com@groups.io> wrote:

I have one call sign that I have worked many many times many many times on the same band and I’m sure he’s getting tired of me. It is not recognized in the log as being worked before.  The call is K4TY.
I have looked in the log to see if it looks different than any other calls signs that are in the log of the program but I don’t see anything that’s different or weird. Just not being recognized anybody else experienced this? And my apology to the owner of the car sign for calling you when it says it’s a new one and I never worked before but in my log I think I got you 30 times. I’ve tried it with the software a standalone, and also with JT alert same thing. 

73
n7uvh






--
73 - John - N7GHZ



Re: Call sign not being recognized as work before question #FT8 #logging

Bill Somerville
 

On 04/02/2021 00:01, Pat via groups.io wrote:

I have one call sign that I have worked many many times many many times on the same band and I’m sure he’s getting tired of me. It is not recognized in the log as being worked before.  The call is K4TY.
I have looked in the log to see if it looks different than any other calls signs that are in the log of the program but I don’t see anything that’s different or weird. Just not being recognized anybody else experienced this? And my apology to the owner of the car sign for calling you when it says it’s a new one and I never worked before but in my log I think I got you 30 times. I’ve tried it with the software a standalone, and also with JT alert same thing.

73
n7uvh
Hi Pat,

which WSJT-X version are you using?

73
Bill
G4WJS.


Re: #WSJTX_config #WSJTX_config

HamApps Support (VK3AMA)
 

On 4/02/2021 9:45 am, Monty Wilson wrote:

Unable to communicate with the WSJT-X process.

  UDP Port : 2333

  IP Address : 239.255.0.0

  Values read from WSJT-X config file...

    C:\Users\jwils\AppData\Local\WSJT-X\WSJT-X.ini


Looks like you have been playing with your WSJT-X UDP settings. Port 2333 is the default for the secondary UDP Server (depreciated). JTAlert uses the primary settings, and according to your error message is reading 2333. That looks wrong. My guess, without see your actual settings dialog, is that you have both the primary and secondary UDP servers set to use port 2333. Try changing back to the defaults, 2237 for the primary and 2333 for the secondary and don't enable the secondary server.

   

de Laurie VK3AMA


Is this supposed to happen? #FoxAndHound #IssueReport

Tony Collett
 

Hi Group
I had an intriguing experience yesterday calling a Fox on 30m

When my call was selected my Tx was correctly moved to the Fox frequency but he was not seeing my report so he kept sending his report to me while I responded with his report for 3 periods.

On the 4th period he dropped my call and went on to work a different station - my first failure to work an F&H QSO !

What I didn't expect was that my transmitter was moved off the Fox frequency to a different one (but still below 1000Hz) and WSJT kept sending my report to the Fox. It continued to do this for some time and the timer didn't come into operation which it does when you are just calling the Fox. 

Eventually I manually stopped the transmission, moved my frequency back above 1000Hz and started calling anew.
Glad to say I was selected and completed a short while later....

My question - is it supposed to continuously send a report to the Fox after the QSO has been abandoned - (I can check my all.txt file to see just how long).
The Fox called CQ several times before I stopped WSJT sending the report as it was obvious he wasn't seeing me or going to come back with the RR73 I needed.
If I had let it continue would the Fox eventually have picked me up while transmitting a report in "no mans land"?

For the record I was using V2.2.2
Thanks
Tony G4NBS


Call sign not being recognized as work before question #FT8 #logging

Pat
 

I have one call sign that I have worked many many times many many times on the same band and I’m sure he’s getting tired of me. It is not recognized in the log as being worked before.  The call is K4TY.
I have looked in the log to see if it looks different than any other calls signs that are in the log of the program but I don’t see anything that’s different or weird. Just not being recognized anybody else experienced this? And my apology to the owner of the car sign for calling you when it says it’s a new one and I never worked before but in my log I think I got you 30 times. I’ve tried it with the software a standalone, and also with JT alert same thing. 

73
n7uvh


Re: #Install #BugReport #WSJTX_config WSJT-X not working after 2.3.0 install #install #IssueReport #WSJTX_config

Bill Somerville
 

On 03/02/2021 21:34, Jim Pruitt wrote:
I was decoding using WSJT-X 2.2.2 (64 bit) and today I installed the newest 2.3.0 (64 bit)  When I did WSJTX stopped working.  The waterfall is totally blank (not a single signal showing up despite LOTS of activity on the frequency.  Looking at the configuration had the Audio Soundcard input first as Default device Not found and then it showed it as blank and now it is back to not found. The USB sound card dongle was working with 2.2.2 but is not even seen by 2.3.0 and the dongle is flashing with the audio input.  How do I get it working?  Or should I just re install 2.2.2?

Thank you.

Jim Pruitt
WA7DUY

Hi Jim,

to try and dissuade users from using the same sound card for WSJT-X and for operating system or other application audio, we no longer offer the default sound card as an option. You must select the sound card that is connected to your rig.

73
Bill
G4WJS.

5701 - 5720 of 27218