Date   

locked Re: V2.2.0 rc1 error on start up (32 bit)

neil_zampella <neilz@...>
 

Why didn't you install the 64 bit version, its actually faster than the 32 bit version, and will still work on Win7.

Neil,KN3ILZ

On 5/11/2020 5:38 PM, ny2ny wrote:
just installed the new 2.2  - 32 bit version on my 64 bit W7 machine - works FB, faster decodes...
--
jay ny2ny

    

Virus-free. www.avg.com


locked Re: WSJT-X 2.2.0-rc1

Alan James <alanmjames@...>
 

Herb, I will second that and my receive goal post is a dark green now and also hard to see because of the lack of contracting color.

73

Alan KZ6B

On Monday, May 11, 2020, 03:03:23 PM PDT, Herb Blue <wb8asi@...> wrote:


So far all is well running 2.2.0-rc1 with Log4OMv2 2.5.0.0 and JTAlert 2.16.5, on Win10 64bit.   Very quick decodes.  I need to get used to having a lot of decodes early and then the last few arriving at the end jumping the screen up.  I just need to relax more and let the screen populate.  My only suggestion thus far is to either raise the goal posts up a couple pixels so the green one has some small distance above the waterfall, or just turn the green one upside down so it stands out better.  Thanks.  Enjoying the newest version of WSJT. 73 Herb WB8ASI


locked Re: v2.2.0.rc1 settings and rig control problems

John - AI4FR
 

Ken,
    I don’t know what version of SSDR you are running but cat and dax have major issues in 2.5 and above. I’ve also found that I have less cat issues running the rig control in wsjt under kenwood ts-2000 instead of flex.
 
John / AI4FR
 
 
Sent: Monday, May 11, 2020 5:57 PM
Subject: Re: [WSJTX] v2.2.0.rc1 settings and rig control problems
 
Hi Bill,
 
I'm having settings problems with the new 2.2.0-rc1.  Both 32 bit and 64 bit behave the same. Tried both.  Have had no problems in the past.
 
In the following I'm running WSJT-X 2.2.0-rc1 64 bit with rig control to a Flex 6500 on Win 8.0.
 
Here's an example of what happens:
 
I've turned the 6500 output to zero, so no RFI issues.  WSJT-X Pwr set as per normal for audio drive..
 
I call CQ with a three minute time out.  Rig control is working.
 
After one or two CQs WSJT-X does a "Halt TX", disabling TX.  Much of the time this also disables the rig control and I get the "Rig Control Error" splash screen
 
I can OK that to go to the "Radio Setting" screen, OK again and I go back to the program and rig control works again. I need to hit "Enable TX" to continue. 
 
If I power up the 6500 and get a QSO going, WSJT-X will often disable TX again during the QSO so I have to manually re-Enable. And often I'll get the "Rig Control Error" again,
 
It seems settings are getting lost somehow along the way.  It's difficult to see a pattern.
 
Some of my "General" settings weren't carried over from 2.1.2 but once reset, they stay..
 
73,
Ken, AB1J


locked 2.2.0-rc1

Gary Gorniak
 

Installation of the 64 bit Windows version went flawlessly for me.  So far I have seen no issues.  One thing of note is that I seem to be decoding more signals that are close to the noise floor on the waterfall, in the -20 to -24 range.  Just an observation so far.  I have not quantified it.

 

As always, thanks to you and your team Joe for all the hard work!

 

73 de Gary – W9BS

 


locked Re: WSJT-X 2.2.0-rc1

Herb Blue - WB8ASI
 

So far all is well running 2.2.0-rc1 with Log4OMv2 2.5.0.0 and JTAlert 2.16.5, on Win10 64bit.   Very quick decodes.  I need to get used to having a lot of decodes early and then the last few arriving at the end jumping the screen up.  I just need to relax more and let the screen populate.  My only suggestion thus far is to either raise the goal posts up a couple pixels so the green one has some small distance above the waterfall, or just turn the green one upside down so it stands out better.  Thanks.  Enjoying the newest version of WSJT. 73 Herb WB8ASI


locked Re: v2.2.0.rc1 settings and rig control problems

Kermit Lehman
 

Hi Bill,

I'm having settings problems with the new 2.2.0-rc1.  Both 32 bit and 64 bit behave the same. Tried both.  Have had no problems in the past.

In the following I'm running WSJT-X 2.2.0-rc1 64 bit with rig control to a Flex 6500 on Win 8.0.

Here's an example of what happens:

I've turned the 6500 output to zero, so no RFI issues.  WSJT-X Pwr set as per normal for audio drive..

I call CQ with a three minute time out.  Rig control is working.

After one or two CQs WSJT-X does a "Halt TX", disabling TX.  Much of the time this also disables the rig control and I get the "Rig Control Error" splash screen.  

I can OK that to go to the "Radio Setting" screen, OK again and I go back to the program and rig control works again. I need to hit "Enable TX" to continue.  

If I power up the 6500 and get a QSO going, WSJT-X will often disable TX again during the QSO so I have to manually re-Enable. And often I'll get the "Rig Control Error" again,

It seems settings are getting lost somehow along the way.  It's difficult to see a pattern.

Some of my "General" settings weren't carried over from 2.1.2 but once reset, they stay..

73,
Ken, AB1J


locked Re: V2.2.0 rc1 error on start up (32 bit)

ny2ny
 

just installed the new 2.2  - 32 bit version on my 64 bit W7 machine - works FB, faster decodes...
--
jay ny2ny


locked Re: V2.2.0 rc1 error on start up (32 bit)

Gary - AG0N
 

On May 11, 2020, at 10:09, Bill Somerville <g4wjs@...> wrote:

Hi Bob,

ah, so not a hardware restriction, just an excuse to splash out on a shiny new rig, hi hi.

73
Bill
G4WJS.

Note to XYL: Hi Honey! Hey, it seems the Covid 19 virus has gotten into my old rig. I need to replace it right away, OK?

Gary - AG0N


locked Re: WSJT-X 2.2.0-rc1

JP Tucson, AZ
 

To tell how well this new decode system works...

73 - John - N7GHZ

On Mon, May 11, 2020, 12:04 PM Gary - AG0N <mcduffie@...> wrote:


> On May 11, 2020, at 11:40, JP Tucson, AZ <samcat88az@...> wrote:
>
> That way, we can see how many decodes per cycle & the total #

Why would it matter to the operator how many per cycle or even which cycle?

Gary - AG0N


locked Re: WSJT-X 2.2.0-rc1

Gary - AG0N
 

On May 11, 2020, at 11:40, JP Tucson, AZ <samcat88az@...> wrote:

That way, we can see how many decodes per cycle & the total #
Why would it matter to the operator how many per cycle or even which cycle?

Gary - AG0N


locked Re: FT8 Logging Problem!

W4AS
 

I agree with you Lance. If you’re on 6 meters for example, and there is an opening to EU, then skipping Tx1 is fine, since you can tell where someone is based on their call. But if you are calling me from the US, I have no idea where you are if you don’t send your grid.

Also, regardless of what some have said here, I don’t see the problem in someone calling me when I’m working someone else (so long as it’s not on my TX frequency). When I’m done with the QSO, I’ll do my best to get back to the other callers - but please don’t call on my TX frequency, that makes decoding very difficult, if not impossible, if there are multiple callers.

73 de Sebastian, W4AS

On May 11, 2020, at 12:52 PM, Lance Collister, W7GJ <w7gj@q.com> wrote:

On a somewhat related subject, hopefully more people - at least on the VHF and UHF
bands - will be encouraged to call with TX#1 (with their grid locator) so I can see
where they are! Last night I found I needed to move the antenna around to complete
with the weaker callers, but if they didn't call with their grid square, I had no
idea where to point for them :-( As the propagation fades, their signal faded out and
they disappeared before I could figure out where to move the antenna.

GL and VY 73, Lance


locked Re: JT Alert Question

Bill <k2wh@...>
 

OK guys, thanks, I was afraid that removing the All.txt file would affect my DXCC  saved entities but I now understand it is simply a reference file of my activities and band activities and the DXCC and States worked have nothing to do with WSJT-x.

I'll leave it alone, I thought the ALL file was a lookup file to determine if I had already worked a station as indicated in JTalert and if I removed the file that would all disappear and I would have to start all over.

I am not running out of disc space.

Thanks.
Bill
K2WH


locked Re: WSJT-X 2.2.0-rc1

JP Tucson, AZ
 

Number of new decodes...

Kinda buried...

if I may suggest,  I think It may be easier to find & look better & be more informative if you display as such:

In the band activity header:

UTC    dB  DT  Freq    Message           #decodes -  ##    ##    ##   Total ##

That way, we can see how many decodes per cycle & the total #.

This would also allow better feedback to you folks for refinement if we see issues.




On Mon, May 11, 2020 at 7:44 AM Joe <joe@...> wrote:
WSJT-X 2.2.0 will be a significant program upgrade offering many new
features.

The first candidate release, WSJT-X 2.2.0-rc1, is now available for
download and use by beta testers.  This candidate release is your first
chance to test the new features and provide feedback to the WSJT
Development Group.

A list of program changes since WSJT-X 2.1.2 can be found in the
cumulative Release Notes
http://physics.princeton.edu/pulsar/k1jt/Release_Notes.txt
... and also in the updated WSJT-X 2.2.0 User Guide here:
http://www.physics.princeton.edu/pulsar/K1JT/wsjtx-doc/wsjtx-main-2.2.0-rc1.html#NEW_FEATURES

Upgrading from earlier versions of WSJT-X should be seamless.  There is
no need to uninstall a previous version or move any files.  You might
want to install to a different directory from your WSJT-X 2.1.2
installation.

Links to installation packages for Windows, Linux, and Macintosh are
available here:
http://physics.princeton.edu/pulsar/k1jt/wsjtx.html
Scroll down to find "Candidate release:  WSJT-X 2.2.0-rc1".

You can also download the packages from our SourceForge site:
https://sourceforge.net/projects/wsjt/files/
It may take a short time for the SourceForge site to be updated.

WSJT-X is licensed under the terms of Version 3 of the GNU General
Public License (GPL).  Development of this software is a cooperative
project to which many amateur radio operators have contributed.  If you
use our code, please have the courtesy to let us know about it.  If you
find bugs or make improvements to the code, please report them to us in
a timely fashion.

We hope you will enjoy using this beta release of WSJT-X 2.2.0.  Please
report bugs by following instructions found here in the User Guide:
http://www.physics.princeton.edu/pulsar/K1JT/wsjtx-doc/wsjtx-main-2.2.0-rc1.html#_bug_reports

      -- 73 from Joe, K1JT, Steve, K9AN, and Bill, G4WJS, for the
                         WSJT Development Group



--
73 - John - N7GHZ



locked Re: WSJT-X 2.2.0-rc1

JP Tucson, AZ
 

Clarity...

"jumps up about a half an EMPTY line"

On Mon, May 11, 2020 at 10:12 AM JP Tucson, AZ via groups.io <samcat88az=gmail.com@groups.io> wrote:
Display jumps... ;  DT suggestion...

Hello, Just downloaded the new 2.2.0...

Definitely decoding faster...

However, I have noticed that during the second decode cycle, the band activity screen jumps up about a half a line, then upon the third, if there are more stations to display, it jumps more.  This makes trying to click on a station a bit difficult, and often causes the wrong station to be selected.

Secondly, I don't have color blindness -  thankfully; however, now the green bracket to me is too dark and nearly blends in with the waterfall, as I do have astigmatism.  Could you make an option to where we can select the waterfall bracket colors please? Thanks.

Still not seeing a selection for the Kenwood TS-440S; and it still does not work on my radio.  Did you guys get the message email I sent that included the IC-10 manual, for comparison to what you are sending out?

Is there anyway, you could program a way to 'zero out' the DT between two stations? This would be for those stations that are way off, yet still decode...   Right now, I am at .1 with most stations, yet, I have a guy here who is at 3.1 seconds & +04 signal, still decoding, but he doesn't respond as he appears not to see anyone calling back. I notice this too with a lot of foreign stations, and we lose QSO's due to excess DT.  



On Mon, May 11, 2020 at 7:44 AM Joe <joe@...> wrote:
WSJT-X 2.2.0 will be a significant program upgrade offering many new
features.

The first candidate release, WSJT-X 2.2.0-rc1, is now available for
download and use by beta testers.  This candidate release is your first
chance to test the new features and provide feedback to the WSJT
Development Group.

A list of program changes since WSJT-X 2.1.2 can be found in the
cumulative Release Notes
http://physics.princeton.edu/pulsar/k1jt/Release_Notes.txt
... and also in the updated WSJT-X 2.2.0 User Guide here:
http://www.physics.princeton.edu/pulsar/K1JT/wsjtx-doc/wsjtx-main-2.2.0-rc1.html#NEW_FEATURES

Upgrading from earlier versions of WSJT-X should be seamless.  There is
no need to uninstall a previous version or move any files.  You might
want to install to a different directory from your WSJT-X 2.1.2
installation.

Links to installation packages for Windows, Linux, and Macintosh are
available here:
http://physics.princeton.edu/pulsar/k1jt/wsjtx.html
Scroll down to find "Candidate release:  WSJT-X 2.2.0-rc1".

You can also download the packages from our SourceForge site:
https://sourceforge.net/projects/wsjt/files/
It may take a short time for the SourceForge site to be updated.

WSJT-X is licensed under the terms of Version 3 of the GNU General
Public License (GPL).  Development of this software is a cooperative
project to which many amateur radio operators have contributed.  If you
use our code, please have the courtesy to let us know about it.  If you
find bugs or make improvements to the code, please report them to us in
a timely fashion.

We hope you will enjoy using this beta release of WSJT-X 2.2.0.  Please
report bugs by following instructions found here in the User Guide:
http://www.physics.princeton.edu/pulsar/K1JT/wsjtx-doc/wsjtx-main-2.2.0-rc1.html#_bug_reports

      -- 73 from Joe, K1JT, Steve, K9AN, and Bill, G4WJS, for the
                         WSJT Development Group



--
73 - John - N7GHZ





--
73 - John - N7GHZ



locked Re: WSJT-X 2.2.0-rc1

JP Tucson, AZ
 

Display jumps... ;  DT suggestion...

Hello, Just downloaded the new 2.2.0...

Definitely decoding faster...

However, I have noticed that during the second decode cycle, the band activity screen jumps up about a half a line, then upon the third, if there are more stations to display, it jumps more.  This makes trying to click on a station a bit difficult, and often causes the wrong station to be selected.

Secondly, I don't have color blindness -  thankfully; however, now the green bracket to me is too dark and nearly blends in with the waterfall, as I do have astigmatism.  Could you make an option to where we can select the waterfall bracket colors please? Thanks.

Still not seeing a selection for the Kenwood TS-440S; and it still does not work on my radio.  Did you guys get the message email I sent that included the IC-10 manual, for comparison to what you are sending out?

Is there anyway, you could program a way to 'zero out' the DT between two stations? This would be for those stations that are way off, yet still decode...   Right now, I am at .1 with most stations, yet, I have a guy here who is at 3.1 seconds & +04 signal, still decoding, but he doesn't respond as he appears not to see anyone calling back. I notice this too with a lot of foreign stations, and we lose QSO's due to excess DT.  



On Mon, May 11, 2020 at 7:44 AM Joe <joe@...> wrote:
WSJT-X 2.2.0 will be a significant program upgrade offering many new
features.

The first candidate release, WSJT-X 2.2.0-rc1, is now available for
download and use by beta testers.  This candidate release is your first
chance to test the new features and provide feedback to the WSJT
Development Group.

A list of program changes since WSJT-X 2.1.2 can be found in the
cumulative Release Notes
http://physics.princeton.edu/pulsar/k1jt/Release_Notes.txt
... and also in the updated WSJT-X 2.2.0 User Guide here:
http://www.physics.princeton.edu/pulsar/K1JT/wsjtx-doc/wsjtx-main-2.2.0-rc1.html#NEW_FEATURES

Upgrading from earlier versions of WSJT-X should be seamless.  There is
no need to uninstall a previous version or move any files.  You might
want to install to a different directory from your WSJT-X 2.1.2
installation.

Links to installation packages for Windows, Linux, and Macintosh are
available here:
http://physics.princeton.edu/pulsar/k1jt/wsjtx.html
Scroll down to find "Candidate release:  WSJT-X 2.2.0-rc1".

You can also download the packages from our SourceForge site:
https://sourceforge.net/projects/wsjt/files/
It may take a short time for the SourceForge site to be updated.

WSJT-X is licensed under the terms of Version 3 of the GNU General
Public License (GPL).  Development of this software is a cooperative
project to which many amateur radio operators have contributed.  If you
use our code, please have the courtesy to let us know about it.  If you
find bugs or make improvements to the code, please report them to us in
a timely fashion.

We hope you will enjoy using this beta release of WSJT-X 2.2.0.  Please
report bugs by following instructions found here in the User Guide:
http://www.physics.princeton.edu/pulsar/K1JT/wsjtx-doc/wsjtx-main-2.2.0-rc1.html#_bug_reports

      -- 73 from Joe, K1JT, Steve, K9AN, and Bill, G4WJS, for the
                         WSJT Development Group



--
73 - John - N7GHZ



locked Re: Band activity refresh issue

Reino Talarmo
 

Thanks Bill,

I’ll do.

Reino

 

From: WSJTX@groups.io [mailto:WSJTX@groups.io] On Behalf Of Bill Somerville
Sent: 11. toukokuuta 2020 19:56
To: WSJTX@groups.io
Subject: Re: [WSJTX] Band activity refresh issue

 

On 11/05/2020 17:53, Reino Talarmo wrote:

Hi development group,

Thanks for the rc1. Up to now it is working nicely in my Windows 10 64bit version. Only drawback I noted is the refreshment of the Band activity window. I have the ‘Start new period decodes at top’ ticked and it does that once the first decoding period proceeds as expected, but it clears the display almost immediately and start at the top with the rest of decodes, perhaps twice as I see only low level signals most of the time. I assume that it should start only at the beginning of the first decodes of that timeslot and then continue with the rest of decodes.

73, Reino OH3mA

Hi Reino,

this is a known defect in WSJT-X v2.2.0-rc1, we are working on a fix. For now please uncheck "Settings->General->Start new decodes at top", sorry for the inconvenience.

73
Bill
G4WJS.


locked Re: FT8 Logging Problem!

Reino Talarmo
 

Hi Lance,
If it were EU VHF contest, then at least there you can fill the missing information into the received report box. I think that it accepted also e.g. R-10 or -15, which are not in the EU VHF format 539001. I have had that and managed to log the QSO. Cannot exactly remember how, hi!
73, Reino OH3mA

-----Original Message-----
From: WSJTX@groups.io [mailto:WSJTX@groups.io] On Behalf Of Lance Collister, W7GJ
Sent: 11. toukokuuta 2020 19:53
To: WSJTX@groups.io
Subject: Re: [WSJTX] FT8 Logging Problem!

Hi Reino,

Yes, my point was this: I was unable to log the contact at all. Yes, they probably were not in the contest - they probably just needed my grid. But the way WSJT-X is/was set up, it was impossible to log the contact :-( It would be GREAT if such a contact without a grid was NOT added to the contest log, but you were not prevented from logging the contact in the regular log :-)

On a somewhat related subject, hopefully more people - at least on the VHF and UHF bands - will be encouraged to call with TX#1 (with their grid locator) so I can see where they are! Last night I found I needed to move the antenna around to complete with the weaker callers, but if they didn't call with their grid square, I had no idea where to point for them :-( As the propagation fades, their signal faded out and they disappeared before I could figure out where to move the antenna.

GL and VY 73, Lance


On 5/11/2020 08:23:25, Reino Talarmo wrote:

Steve,

Now I read the whole chain and understood your point. Perhaps they did
not even wanted participate the contest, but only wished to get a QSO
with you? I have had that kind of ‘nuisance’ as those contact do
not count as they will not send their log in and of course it is not a
valid contest QSO due to the missing locator, hi!

73, Reino OH3mA


--
Lance Collister, W7GJ(ex WA3GPL, WA1JXN, WA1JXN/C6A, ZF2OC/ZF8, E51SIX, 3D2LR, 5W0GJ, E6M, TX5K, KH8/W7GJ, V6M, T8GJ, VK9CGJ, VK9XGJ, C21GJ, CP1GJ, S79GJ, TX7MB) P.O. Box 73
Frenchtown, MT 59834-0073
USA
TEL: (406) 626-5728
QTH: DN27ub
URL: http://www.bigskyspaces.com/w7gj
Skype: lanceW7GJ
2m DXCC #11/6m DXCC #815

Interested in 6m EME? Ask me about subscribing to the Magic Band EME email group, or just fill in the request box at the bottom of my web page (above)!


locked Re: JT Alert Question

John Morphet
 

Good to know, that should answer Bill, K2WH. He must have thought there was a connection.

 

John, WØZI

 

From: WSJTX@groups.io <WSJTX@groups.io> On Behalf Of Bill Somerville
Sent: Monday, May 11, 2020 10:51 AM
To: WSJTX@groups.io
Subject: Re: [WSJTX] JT Alert Question

 

John,

 

JTAlert does not read the WSJT-X ALL.TXT file. It reads the WSJT-X settings file at startup, all of the rest of the communication with WSJT-X is via the WSJT-X UDP Message Protocol.

 

73
Bill
G4WJS.

 

On 11/05/2020 17:47, John Morphet wrote:

This depends if JTAlert uses all.txt. I would ask the question on the JTalert forum. Secondly, If you really have to delete it, I would not. I would save it off somewhere else and start with a fresh file. What about the WSJTX_log.adi file? Are you really having a space problem? Most modern operating systems today can handle a very large file size. If you are running out of hard drive space. There are probably much larger candidates you could look at or get a larger hard drive.

 

John, WØZI

 

From: WSJTX@groups.io <WSJTX@groups.io> On Behalf Of Bill
Sent: Monday, May 11, 2020 9:26 AM
To: WSJTX@groups.io
Subject: [WSJTX] JT Alert Question

 

I know I'm on the wrong forum, but I don't see how to post on the JTAlert forum.

My question is simple and it has to do with the "All.txt" file.

It is getting very large and would like to know, what happens, if anything if I erase it ?

Bill
K2WH

 


locked Re: Band activity refresh issue

Bill Somerville
 

On 11/05/2020 17:53, Reino Talarmo wrote:

Hi development group,

Thanks for the rc1. Up to now it is working nicely in my Windows 10 64bit version. Only drawback I noted is the refreshment of the Band activity window. I have the ‘Start new period decodes at top’ ticked and it does that once the first decoding period proceeds as expected, but it clears the display almost immediately and start at the top with the rest of decodes, perhaps twice as I see only low level signals most of the time. I assume that it should start only at the beginning of the first decodes of that timeslot and then continue with the rest of decodes.

73, Reino OH3mA

Hi Reino,

this is a known defect in WSJT-X v2.2.0-rc1, we are working on a fix. For now please uncheck "Settings->General->Start new decodes at top", sorry for the inconvenience.

73
Bill
G4WJS.


locked Band activity refresh issue

Reino Talarmo
 

Hi development group,

Thanks for the rc1. Up to now it is working nicely in my Windows 10 64bit version. Only drawback I noted is the refreshment of the Band activity window. I have the ‘Start new period decodes at top’ ticked and it does that once the first decoding period proceeds as expected, but it clears the display almost immediately and start at the top with the rest of decodes, perhaps twice as I see only low level signals most of the time. I assume that it should start only at the beginning of the first decodes of that timeslot and then continue with the rest of decodes.

73, Reino OH3mA