Date   

locked Re: FT8 V 1.9 and 2.0 #FT8

mike <ipaforme@...>
 




    Yes Gary I just did running an IC-7200 and all seemed to be fine.

mine was .rc4 that I last ran before the move to 2.0 after I sorted a dependency issue with linux.

/Mike  Ki7PNG


On 12/11/18 3:17 PM, Gary K6JAJ via Groups.Io wrote:
Has any one now tried using the two different programs on one computer using the same cat
settings??
Gary K6JAJ


locked Can't update to 2.0,0 from xxx.rc4 on Debian 9 Stretch #install

mike <ipaforme@...>
 

I think I met all dependencies on the list from the INSTALL readme except ONE!  (it's always something).
That would be the gfortran-4.8.2  'or newer'.  I can install 4.6.3.0-4 but since it's too old I haven't.  Instead
I have gfortran-6 (6.3.0-18+deb9u1 ) and gfortran-6-aarch64-linux-gnu but CMake complains about no Fortran compiler.
I tried specifying the path to the gfortran-6 file with the 'FC' variable but with the same result.  No success.  It wants
the plain gfortran version.  I wish Debian would release a 'dist-upgrade', I think it's about due.  I seemed to do OK adding the other dependencies manually, like I did to build .rc4.

It's normally so damn stable I don't want to leave it. (debian that is ..) 

TIA for any tips.   73,

Mike


locked #log_issues

Bob
 

Experimenting with WSJT-X 2.0, and no matter how hard I click on the 'Log automatically' checkbox (I see the checkmark), I am still prompted to log the QSO.  Do I need a new mouse?  73.


locked Many stops a day of FT8 sessions in WSJT-X 2.0 GA in FT8Startup multisession startup

Sven SM6FMB
 

Hi!
 
I am running a program, FT8Startup, admitting me to start up, up to 8 instances, very quick, of WSJT-X with my Red Pitaya. No need to start up indivdual HDSDR to cover up the receiver side.
 
Program was running for months without any problem, But upgrading from 1.9.1 to 2.0 GA a problem occured!
 
Problem occurs randomly, many times a day message saying:
 
Running: C:\wsjt\wsjtx\bin\jt9 -s "WSJT-X - Rig4ForRBN" -w 1 -m 3 -e C:\wsjt\wsjtx\bin -a "C:\Users\Sven\AppData\Local\WSJT-X - Rig4ForRBN" -t "C:\Users\Sven\AppData\Local\Temp\WSJT-X - Rig4ForRBN"
 
Program received signal SIGSEGV: Segmentation fault - invalid memory reference.
 
Backtrace for this error:
#0  6f617f5e
#1  6f69bc5b
#2  004776925cef2bf4
 
Rig4ForRBN is one session/one frequency inside the FT8Startup startup sequence. 
 
I have already in the RBN-OPS forum asked the question and nobody knows anything about this issue. Seems to be a WSJT-X issue!
 
73 de Sven SM6FMB


locked Bug Report: c2fox' above upper bound

Doc Global
 

Encountered this same error twice now on latest v2 build (program stops):

WSJT-X v2.0.0 Build 784f75 (latest build) on MacBook Pro High Sierra
 
Running: /Applications/wsjtx.app/Contents/MacOS/jt9 -s WSJT-X -w 1 -m 3 -e /Applications/wsjtx.app/Contents/MacOS -a "/Users/WSJT/Library/Application Support/WSJT-X" -t /var/folders/pz/9sshl_91735_7mgxj120nc3c0000gw/T/WSJT-X
At line 543 of file /Users/bill/wsjtx-prefix/src/lib/decoder.f90
Fortran runtime error: Index '1001' of dimension 1 of array 'c2fox' above upper bound of 1000
 
Error termination. Backtrace:
#0  0x1168758b6
#1  0x116876188
#2  0x116876495
#3  0x10e76bdb8
#4  0x10e73cb2b
#5  0x10e76d4a7
 
 
Running: /Applications/wsjtx.app/Contents/MacOS/jt9 -s WSJT-X -w 1 -m 3 -e /Applications/wsjtx.app/Contents/MacOS -a "/Users/WSJT/Library/Application Support/WSJT-X" -t /var/folders/pz/9sshl_91735_7mgxj120nc3c0000gw/T/WSJT-X
At line 543 of file /Users/bill/wsjtx-prefix/src/lib/decoder.f90
Fortran runtime error: Index '1001' of dimension 1 of array 'c2fox' above upper bound of 1000
 
Error termination. Backtrace:
#0  0x11136b8b6
#1  0x11136c188
#2  0x11136c495
#3  0x109267db8
#4  0x109238b2b
#5  0x1092694a7


locked Re: #RESCAN

l41.46n-106.82@...
 

>>the ADIF log file parser has been made stricter, a choice I am beginning to regret. 

I have a patch for that. What is the procedure for submitting it? The next release will relax the stricter parsing. 

73
Andy
K9AVT


locked #sequencing #QSO_practices

Bob
 

There is an option 'Notify on accepted UDP request'.  I have studied the documentation, but can not find reference to this anywhere.  Any ideas where the message/field is hidden?  73.


locked Configuration and dupe checking question when running N1MM+ with WSJTX/JTAlertX? #ft8 #N1MM+ #FT8

Rich Erlichman
 

Posted also on the N1MM+ forum;
I am trying to setup for the ARRL RTTY Roundup this coming January. I played a little in the FT8 RU a couple of weekends ago using N1MM+ and WSJT-X (and JTAlertX). I was only able to run full rig control from WSJT-X and had set the normal Rig Control path for N1MM+ to "None" to make the two apps play together. The result was OK with respect to running the contest, and with logging via the UDP transfer feature from JTAlert-X over to N1MM+. The only dupe checking capability I had was from JTAlert-X, since the UDP transfers to N1MM+ were essentially after the fact.
I would like to be able to run the RTTY mode from N1MM+, in addition to FT8 in the upcoming contest. However, this causes me to create separate ".INI" files for N1MM+ where one has the rig control (when running RTTY) and the other is set to "None" (when running FT8). Is there a more elegant solution where I don't have to shut things down and launch what I need from different short cuts, or reconfigure things on the fly, when changing modes?
Any suggestions?
73, 
Rich, ND4G


locked Waterfall clarity in Version 2.0 WSJT-X #FT8

n8mdp
 

Hi,

I upgraded from V1.8 to 2.0 last week. Nice to see that everything worked fine. However, I noticed that the waterfall plot is not as crisp and clear compared to V1.8 (noticed the same thing in 1.9 when I tried that). Did something change in the waterfall plot that would have changed the clarity of the waterfall plot? 

1st image below is the waterfall in V2.0. The second image is in V1.8.

Are there settings I can adjust to make the waterfall plot clearer or sharper.

Thanks.
John
N8MDP


locked WSJT-X 2.0.0 macOS, no countries shown?

Matt Gumbley
 

Hi,

I've upgraded to 2.0.0 from 1.8 (on macOS 10.11 El Capitan), and now am not seeing the country being shown alongside the CQ decodes. I see 'NA' or 'EU' when 'Show DXCC, grid, and worked-before status' is selected in Preferences/General. Selecting 'Show principal prefix instead of country name' does not make any difference to the left-hand received decode list. The choice in the Preferences dialog is persisted to settings; it doesn't seem to effect any changes in display content..
I wondered if the 2.0.0 was misinterpreting 1.8's WSJT-X.ini, so deleted that and recreated it, but this did not fix the problem.

Is there some element of configuration I'm missing here?

Thank you for all the improvements in 2.0.0!

Kind regards & 73,
Matt Gumbley M0CUV


locked Brackets Around Call Letters

Bill <k2wh@...>
 

What do the brackets <K2WH> indicate?
--
49 Year Ham.


locked Can include the two OpenSSL DLLs in WSJT-X install?

l41.46n-106.82@...
 

These fix the error at startup reading the LoTW member status, available at indy.fulgan.com/SSL

libeay32.dll
eayssl32.dll

Copy to the bin folder used by WSJT-X.

Andy
K9AVT


locked Bootup Doesn't Read My Rig Frequency

Bill <k2wh@...>
 

Thanks for letting me join.

I have one remaining issue with ver. 2.0 and unlike the prior version, on starting the program, it would read my rig's frequency and or band.

This ver. 2.0 does not and comes up with what seems to be a default of 2 meters, 145mhz segment.

Rig is a Yaesu FTdx3000 with USB port to talk between rig and computer.

Thanks,

Bill
K2WH


locked Status File Error wsjtx_status.txt

Doc.George
 

Hello

I'm running brand new WSJT-X 2.0, on Windows 10 totally updated. My radio is a Flex 6600
After installed 2.0 I began to see a randon crash, stops decode , and when i tray to change  band
PC shows a dialog box  Status file error
As you can see at picture attached


locked Minimal Decodes

tom
 

Long time user of WSJT-X, mostly all FT8 since its invention. I know that this topic has been beat to death, but...

Everything was working perfectly until 2 days ago.  All of a sudden, I stopped getting all sigs decoded, some but not all.  They appear in the waterfall, ie. 15-20 good sigs, but I'm only decoding 1 to 6.  Don't think it is a time problem as most sigs show DT of .1 or .2. I have been running NTP. Unistalled it. Installed Dimension 4. Uninstalled D4, reinstalled Meinburg.  db sigs show the spectrum, -20 to + sigs on the few decodes I do get. VFO is spot on as I can see everything on the waterfall.

Reset WSJT-X to default config. No change. Reinstalled WSJT-X, no change.  Reset the KW 590SG to factory default settings. No change. Installed last working config from May 2018, no change. 

Delved into Win 10 and fiddled with all audio settings.  Ran the rig in both native audio using its soundcard and installed my SignaLink USB as soundcard. No change. Swapped USB cables. No change.

I checked all rig settings for low cut (zero), hi cut (2700), AGC off, No filters on. Data off. USB (20M). PTT works fine. The rig xmits. Calling CQ yields no response, likely because I'm not decoding them.  

It is 11:30 AM EST, 1630 UTC and 20M has 21 signals on the waterfall. I decoded 1.  Interestingly, I did notice that there are no pink new callsigns or hot pink new DX callsigns being decoded.  That's not right either.  Clue?  I've experimented with every setting in WSJT-X with no resolution.  

I use a 2018 Dell XPS 13 running an i7 with 16gigs of RAM and 512gig SSD drive.  I checked CPU and RAM usage. They are just loping along at 15 and 30%, respectively. 

I also run a Plugable USB-C 4k docking station.  I'm going out to buy a new USB-C to B cable to go direct from the PC, which only has USB-C ports. to the rig.

Windows sound setting are unchanged but I double checked both native rig and SignaLink in Win 10 and both are running and test as expected. 

I was changing nothing and only operating when this happened.

I'm at a total loss as I have exhausted my knowledge of what else to try.  ANY suggestions would be most welcome.
73,
Tom
KE0ABA


locked Messages to the group not showing and not receiving via email #NewUser

Bill <k2wh@...>
 

What's the problem, the site shows nothing by me and I don't get any emails either.

Not having a cell phone, I do not know what a "Hashtag" is either.

Bill
--
49 Year Ham.


locked Configuration and dupe checking question when running N1MM+ with WSJTX/JTAlertX? #WSJTX_config #ft8 #N1MM+ #WSJTX_config #FT8

Rich Erlichman
 

I am trying to setup for the RTTY Roundup this coming January. I played a little in the FT8 RU last weekend using N1MM+ and WSJTX (and JTAlertX). I was only able to run full rig control from WSJTX and had set the normal Rig Control path for N1MM+ to "None" to make the two apps play together. The result was OK with respect to running the contest, and with logging via the UDP transfer feature from JTAlertX over to N1MM+. The only dupe checking capability I had was from JTAlertX, since the UDP transfers to N1MM+ were essentially after the fact.
I would like to be able to run the RTTY mode in addition to FT8 in the upcoming contest. Is there an elegant solution where I don't have to reconfigure things on the fly, when changing modes?
Could there be and Radio setting added for WSJTX to piggy back on the N1MM+ setting, similar to the Ham Radio Deluxe (HRD) selection setting?
In non-contests, I use WSJTX with my main logging in HRD, and both apps run very seamlessly together.
The other issue I miss is entering a callsign into N1MM+ for instant dupe checking. It would be nice when selecting a callsign in WSJTX, it appears in the N1MM+ entry window automatically, and thus I would be informed of a possible dupe immediately.
Any suggestions or solution on the horizon?
73, 
Rich, ND4G


locked Re: #sequencing during contact #QSO_practices

Ron Haltermon WA4HWN
 

I operate with Auto sequence and check reply first, and have found, fairly often the same issues you are describing.  I think it is just a matter of the other station not copying your reply, or visa versa.  If someone else is on one or the other's same frequency, then the signal may be blocked.  I will often move my frequency, or keeping an eye on the waterfall, move my receive frequency to get around this.  Of course, this requires you to have checked the 'move frequency when transmitting' box.  This works for me most of the time.  When the band is crowded and open you may never know who is on your frequency, or the other stations frequency....
73 and good DXing!
Ron WA4HWN

On 12/11/2018 09:34 AM, Geary McDowell wrote:
I read on people's QRZ pages their preferred sequence of what to do.

I have read and read the manual figuring I have missed something but have not found it if I have.

When I run the Auto Seq, which I do 99% of the time, often I get a station that will keep sending the Tx 2 information and I have to manually send the Tx 2 quickly when I receive their TX, as my computer jumps to Tx 3 for the R-? and we seem to be in a loop.  Once we get to the R-? from the other station or RRR it usually moves on fine, but sometimes it still seems to be in a loop.

I wonder if I have a setting I need to correct (I check/reset my clock often during the day, restarting my computer too before my day's HAMming, I use Network Time Sync and is set to automatically check every 15 minutes.

Of if I am getting a lot of stations that are automated and not attended properly.

Or are other stations I am having this issue with are using something other than WSJT-X?

This problem has been the same on all the WSJT-X versions I have used in 2018.  WSJT 1.9.1, V2 rc 3, V2 rc4, V2 rc5 and even V 2.0.0

Any positive information that might/will help is appreciated.

Geary, KE5IRK
Lawton-Fort Sill, OK


--
Please Note: If you forward this message, in the interest of reducing spamming and e-mail address harvesting, please remove my name and address. Thank you!

Ron Haltermon - WA4HWN

Dothan, Al

Deep in the Heart of Wire Grass Country

The Peanut Capitol of the World

The secure operating system! For info, check out my Website featuring Linux Operating System Information at http://qsl.net/wa4hwn


locked Re: #sequencing during contact #QSO_practices

Geary McDowell (owner)
 

That makes sense Mike, thanks.  
And when things go smoothly that is what happens.  
Maybe when I keep getting and probably sending the same step, one or both systems are not receiving or decoding the signal.  HUmmmm, always learning.
Geary KE5IRK

On Tue, Dec 11, 2018 at 9:48 AM Michael Black via Groups.Io <mdblack98=yahoo.com@groups.io> wrote:
Maybe you don't understand the sequencing?

You send 1/3/5
They send 2/4/5
So when they send Tx2 you are supposed to send Tx3 which is what the autosequencer is doing.

de Mike W9MDB




On Tuesday, December 11, 2018, 9:34:46 AM CST, Geary McDowell <ke5irk@...> wrote:


I read on people's QRZ pages their preferred sequence of what to do.

I have read and read the manual figuring I have missed something but have not found it if I have.

When I run the Auto Seq, which I do 99% of the time, often I get a station that will keep sending the Tx 2 information and I have to manually send the Tx 2 quickly when I receive their TX, as my computer jumps to Tx 3 for the R-? and we seem to be in a loop.  Once we get to the R-? from the other station or RRR it usually moves on fine, but sometimes it still seems to be in a loop.

I wonder if I have a setting I need to correct (I check/reset my clock often during the day, restarting my computer too before my day's HAMming, I use Network Time Sync and is set to automatically check every 15 minutes.

Of if I am getting a lot of stations that are automated and not attended properly.

Or are other stations I am having this issue with are using something other than WSJT-X?

This problem has been the same on all the WSJT-X versions I have used in 2018.  WSJT 1.9.1, V2 rc 3, V2 rc4, V2 rc5 and even V 2.0.0

Any positive information that might/will help is appreciated.

Geary, KE5IRK
Lawton-Fort Sill, OK


locked #wsjtx Colors in Sttings

John GM6BRU
 

Hello folks. I have some observations on the new FT8 colors:
1 There seem to be too many information colors, Each QSO over is only 15 seconds long so too much information is being thrown at the operator (even though FT8 is worked in Auto Sequence mode).
2 The color of New Contact and New Grid is too close to the color of My Call in message and can be misinterpreted.
3 Many of us older operators do have a certain amount of vision impairment that makes the new colors for version 2.0.0 very difficult to interpret. The number and choice of colors provided in version 1.9.1 seem to be adequate for both visual and operational purposes.
4 Please would it be possible to revert to the version 1.9.1 colors?
My observations are not meant as criticisms, more as a request to simplify the user interface. It is appreciated that you guys have worked very hard to provide an excellent data program and I hope that you find my input useful.
73 John GM6BRU