Re: [wsjt-devel] WSJT-X 2.5.2 GA Release

[Dan Malcolm via wsjt-devel]

I downloaded the 64 bit version first with MS Edge.  Even after I told Edge 
that it's safe and reported my opinion to MS, Edge refused to allow me to 
download the file.  Chrome however doesn't evoke Win Defender so it downloaded 
fine with Chrome, the new WSJT-X installed and ran correctly.  BTW I use ESET 
for virus protection and Defender is and has been turned off.  Edge paid no 
attention to my wishes.

__
Dan - K4SHQ
CFI/II

-Original Message-
From: Joe Taylor via wsjt-devel  
Sent: Thursday, November 4, 2021 1:03 PM
To: WSJT software development 
Cc: Joe Taylor 
Subject: [wsjt-devel] WSJT-X 2.5.2 GA Release

We are pleased to announce the General Availability (GA) release of WSJT-X 
version 2.5.2.  This is mostly a bug-fix release.  A full list of changes can 
be found in the Release Notes:
https://physics.princeton.edu//pulsar/k1jt/Release_Notes.txt

IMPORTANT: If you expect to use the JT65 or Q65 modes to make weak-signal QSOs 
that involve a nonstandard callsign, be sure to upgrade to WSJT-X 2.5.2!

Links to WSJT-X 2.5.2 installation packages for Windows, Linux, and Macintosh 
are available here:
http://physics.princeton.edu/pulsar/k1jt/wsjtx.html

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.

The authors and Copyright holders of WSJT-X request that derivative works 
should not publish programs based on features in WSJT-X before those features 
are made available in a General Availability (GA) release of WSJT-X.  We will 
cease making public Release Candidate (RC) pre-releases for testing and user 
early access purposes if this request is ignored.

Bugs should be reported by following instructions found here in the User
Guide:

https://www.physics.princeton.edu//pulsar/K1JT/wsjtx-doc/wsjtx-main-2.5.2.html#_bug_reports

We hope you will enjoy using WSJT-X 2.5.2.

  -- 73 from Joe, K1JT; Bill, G4WJS; Steve, K9AN; and Nico, IV3NWV


___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel


___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

[wsjt-devel] WSJT-X v2.4.0 ** WSJT-X\status-file.txt

[Dan Malcolm via wsjt-devel]

Win10.

After running a few hours, I begin getting error messages from WSJT-X saying it 
can't find "C:\Users\\AppData\Local\Temp\WSJT-X".  That folder is indeed 
missing.  No surprise since it's in a "temp" folder.  What is a surprise is 
that the missing folder should be under constant use and therefore, I would 
assume, protected as long as WSJT-X is running and re-established when WSJT-X 
is once again operational.  If my assumption is correct, then why is it 
disappearing?  Is there a way to either protect it, or move it to another 
folder?

__
Dan - K4SHQ
CFI/II

___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Hamlib 4.0 error with rigctld/IC706: Invalid parameter while exchanging VFOs

[Dan Malcolm]

Not sure if my problem has anything to do with this discussion.  If not I’ll 
start with a fresh thread.  I installed rc3 yesterday and it worked fine.  This 
morning rc-3 and v2.2.2 will not connect to the virtual COM port.  I have 
rebooted & reinstalled vspMgr to no avail.  See the attached screen capture for 
the error message.

__
Dan – K4SHQ
CFI/II

From: Black Michael via wsjt-devel 
Sent: Wednesday, January 6, 2021 11:57 AM
To: wsjt-devel@lists.sourceforge.net
Cc: Black Michael 
Subject: Re: [wsjt-devel] Hamlib 4.0 error with rigctld/IC706: Invalid 
parameter while exchanging VFOs

Maybe I should move up the 4.1 release date or do a 4.0.1?

Mike W9MDB




On Wednesday, January 6, 2021, 07:40:05 AM CST, Bill Somerville 
mailto:g4...@classdesign.com>> wrote:


On 06/01/2021 13:28, Black Michael via wsjt-devel wrote:
> There is a binary incompatibility that happened under shared library
> use so if you use the rigctld-wsjtx from WSJTX it should hopefully
> worknot the rigctld from hamlib-4.0
>
> There's a future fix that will hopefully be in the 2.3.0 GA release
> that fixes this problem.
>
>
> Mike W9MDB
>
Mike,

those changes will not be in WSJT-X v2.3.0 GA, mainly because Hamlib 4.0
has a regression that breaks rigs with no get frequency CAT commands. I
expect the changes to be in a future WSJT-X release that is able to be
built against a Hamlib shared library that allows safe linking, I guess
that will be Hamlib v4.1.

73
Bill
G4WJS.




___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] WSJT-X 2.3.0-rc3

[Dan Malcolm]

Thanks Joe.  FYI I've successfully downloaded, installed and have just had my 
first FT8 QSO with rc-3.  I also checked the ALL.TXT file and the formatting is 
correct.  Thanks again.

__
Dan - K4SHQ
CFI/II

-Original Message-
From: Joe Taylor  
Sent: Tuesday, January 5, 2021 8:42 AM
To: WSJT software development 
Subject: [wsjt-devel] WSJT-X 2.3.0-rc3

The third public candidate release of WSJT-X 2.3.0 is now available for 
download and use by beta testers.  Changes from the second release candidate 
include an improved FST4W decoder and fixes for several defects and 
regressions. Additional details are described in the Release
Notes:
http://physics.princeton.edu/pulsar/k1jt/Release_Notes.txt

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.3.0-rc3".

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.3.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.3.0-rc3.html#_bug_reports

  -- 73 from Joe, K1JT; Bill, G4WJS; Steve, K9AN; and Nico, IV3NWV


___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel


___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] WSJT-X won't connect to a COM Port

[Dan Malcolm]

I’m getting a protocol error

__
Dan – K4SHQ
CFI/II

From: Black Michael via wsjt-devel 
Sent: Friday, November 6, 2020 6:47 AM
To: wsjtx-devel (wsjt-devel@lists.sourceforge.net) 

Cc: Black Michael 
Subject: Re: [wsjt-devel] WSJT-X won't connect to a COM Port

What kind of error are you getting?

Works fine herebut I'm using EltimaI'll get a copy of VSPMgr and make 
sure it works too.

Mike W9MDB




On Friday, November 6, 2020, 06:41:27 AM CST, Dan Malcolm 
mailto:k4...@outlook.com>> wrote:



If I run either PowerSDR or Thetis as an interface to my ANAN 100D, WSJT-X will 
not connect to either end of the virtual COM port.  I’m using vspMgr to create 
the virtual COM ports.  Before anyone asks; yes my Win10 was recently upgraded.





__

Dan – K4SHQ

CFI/II


___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net<mailto:wsjt-devel@lists.sourceforge.net>
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

[wsjt-devel] WSJT-X won't connect to a COM Port

[Dan Malcolm]

If I run either PowerSDR or Thetis as an interface to my ANAN 100D, WSJT-X will 
not connect to either end of the virtual COM port.  I'm using vspMgr to create 
the virtual COM ports.  Before anyone asks; yes my Win10 was recently upgraded.


__
Dan - K4SHQ
CFI/II

___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] WSJT-X 2.1.2 Status File Error

[Dan Malcolm]

Bill,
Agree, but not the point.  Storage in a temporary file or folder is just that, 
temporary.  That said, obviously something is doing what you said, but my 
Malwarebytes and anti-virus and CCleaner are all set to leave that temporary 
subdirectory and file alone.  

I can manually fix the problem by recreating the WSJT-X sub-folder and then 
restarting WSJT-X or changing something in WSJT-X.  One of the errors occurred 
on WSJT-X startup.  I can live with it, because the errors happen 
intermittently and not frequently.  This started as just a question.  Why, when 
WSJT-X finds the error, can't it re-establish the folder and file.  If the 
developers view this as an extremely low priority, that's fine.  You are busy 
and frankly if I were one of you, it wouldn't be high on my radar either.  So 
it's just a question.

__
Dan - K4SHQ
CFI/II


-Original Message-
From: Bill Somerville [mailto:g4...@classdesign.com] 
Sent: Monday, December 16, 2019 6:55 PM
To: wsjt-devel@lists.sourceforge.net
Subject: Re: [wsjt-devel] WSJT-X 2.1.2 Status File Error

On 17/12/2019 00:41, Dan Malcolm wrote:
> Thanks Jim.
>
> Yes I do have Malwarebytes and an anti-virus running but both have the temp 
> WSJT-X folder and file exempted.  It probably is something that's running but 
> if WSJT-X can't find that directory inside a temp directory, it should just 
> re-create it.  Temp folders and files are by their nature volatile and 
> temporary.
>
> __
> Dan - K4SHQ
> CFI/II

Dan,

this sort of error can happen on Windows when one application holds a file or 
directory open while another deletes a parent directory. Windows appears to 
complete the deletion of the directory but the directory is invisibly preserved 
until the first application closes the file or directory it has open. There is 
no problem with this until a new application instance tries to recreate the 
deleted directory which then fails. WSJT-X deletes it's temporary directory and 
contents upon exit and creates it on entry. I guess some other application is 
holding that directory or a directory or file under it open and interfering 
with WSJT-X's best efforts to use it's own temporary files.

Temporary files are not volatile by nature, they are simply files that are 
created and used by an application until it has finished with them. 
They should not be opened by other applications which have no business meddling 
with internal WSJT-X data.

73
Bill
G4WJS.



___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel


___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] WSJT-X 2.1.2 Status File Error

[Dan Malcolm]

Thanks Jim.  

Yes I do have Malwarebytes and an anti-virus running but both have the temp 
WSJT-X folder and file exempted.  It probably is something that's running but 
if WSJT-X can't find that directory inside a temp directory, it should just 
re-create it.  Temp folders and files are by their nature volatile and 
temporary.

__
Dan - K4SHQ
CFI/II

-Original Message-
From: Jim Preston [mailto:jprest...@cox.net] 
Sent: Monday, December 16, 2019 3:11 PM
To: wsjt-devel@lists.sourceforge.net
Subject: Re: [wsjt-devel] WSJT-X 2.1.2 Status File Error

Dan,

AFAIK, the wsjtx_status.txt file is created every time wsjt-x is started, and 
is deleted every time wsjt-x is closed. If it is disappearing while wsjt-x is 
running, it might well be some other program is deleting it. The same is true 
for the entire subfolder. Stop any other running programs that might do this, 
and see if that makes a difference. Do you have Malwarebytes running at the 
same time as your AV? Is CCleaner running all the time? Do you have some 
program set to automatically delete tmp files or directories? Thse would all be 
places to check.

If it is a case of some program automatically deleting tmp files and folders, 
this can probably be turned off, or adjusted so that it doesn't happen as often.

73,

Jim N6VH

On 12/14/2019 5:15 PM, Dan Malcolm wrote:
> I keep getting an error reporting that WSJT-X can't find its status 
> file.  The reported path is 
> "C:/Users//AppData/Local/Temp/WSJT-X/wsjtx_status.txt".  I 
> can see why it can't find it and that's because the ".Temp/WSJT-X" 
> subfolder is missing.  Obviously something on my Win10 system is 
> removing it.  I don't know what application is doing it, but it's 
> probably CCleaner or my anti-virus or Malwarebytes.  I can probably 
> figure that out.  My question though is; shouldn't WSJT-X be a little more 
> fault tolerant?
> Anything in a temp directory is subject to disappearing.  If the 
> sub-folder can't be found, recreate it.
> 
> I know from past experience with this fault, that manually creating 
> the WSJT-X sub-folder in "Temp" will fix the problem.  I can recreate 
> the problem by changing bands in WSJT-X, after a successful launch, in 
> which I don't have the problem.  The problem appears intermittently, 
> but keeps happening until I do a manual fix.
> 
> __
> 
> Dan - K4SHQ
> 
> CFI/II
> 
> 
> 
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
> 


___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel


___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

[wsjt-devel] WSJT-X 2.1.2 Status File Error

[Dan Malcolm]

I keep getting an error reporting that WSJT-X can't find its status file.  The 
reported path is 
"C:/Users//AppData/Local/Temp/WSJT-X/wsjtx_status.txt".  I can see why 
it can't find it and that's because the "...Temp/WSJT-X" subfolder is missing.  
Obviously something on my Win10 system is removing it.  I don't know what 
application is doing it, but it's probably CCleaner or my anti-virus or 
Malwarebytes.  I can probably figure that out.  My question though is; 
shouldn't WSJT-X be a little more fault tolerant?  Anything in a temp directory 
is subject to disappearing.  If the sub-folder can't be found, recreate it.

I know from past experience with this fault, that manually creating the WSJT-X 
sub-folder in "Temp" will fix the problem.  I can recreate the problem by 
changing bands in WSJT-X, after a successful launch, in which I don't have the 
problem.  The problem appears intermittently, but keeps happening until I do a 
manual fix.

__
Dan - K4SHQ
CFI/II

___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

[wsjt-devel] WSJT-X & ALL.TXT

[Dan Malcolm]

I have read the release notes.  Because it could affect some of my programming, 
I’d like to know if there are any changes to the ALL.TXT format.  I understand 
there may be some in the future, and I will cross that bridge when it happens.  
Release notes say nothing about it, but there is a statement about some minor 
fixes that is unspecified.

__
Dan – K4SHQ

___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] WSJT-X 2.1.0: GA release

[Dan Malcolm]

Joe, thanks to you and all the developer/contributors for this new GA
version of 2.1.0.  So far it is working just fine, and I had no problem
downloading the 64 bit version.
__
Dan - K4SHQ

-Original Message-
From: Joe Taylor [mailto:j...@princeton.edu] 
Sent: Monday, July 15, 2019 9:05 AM
To: WSJT software development 
Subject: [wsjt-devel] WSJT-X 2.1.0: GA release

The WSJT Development Group is pleased to announce the general availability
(GA) release of WSJT-X Version 2.1.0.

WSJT-X 2.1 is a major upgrade that introduces FT4, a new protocol for HF
contesting.  Improvements have also been made in the following areas:

   - FT8 waveform generation using GMSK, fully backward compatible
   - user options for low-sidelobe waterfall and spectrum display
   - UDP messaging for inter-program communication
   - accessibility

... as well as many minor enhancements and bug fixes.

We now provide a separate installation package for 64-bit Windows, offering
significant improvements in decoding speed.


A more detailed list of program changes since WSJT-X 2.0.1 can be found 
in the cumulative Release Notes:
http://physics.princeton.edu/pulsar/k1jt/Release_Notes.txt

Upgrading from earlier versions of WSJT-X should be seamless.  There is 
no need to uninstall a previous version or move any files.

Please do not continue to use any release candidate -- that is, any beta 
release with "-rc#" in the version name.

Links to installation packages for Windows, Linux, and Macintosh are 
available here:
http://physics.princeton.edu/pulsar/k1jt/wsjtx.html

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 WSJT-X Version 2.1.0.

  -- 73, Joe, K1JT, for the WSJT Development Group


___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel



___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] clock patch

[Dan Malcolm]

My $0.02 worth.  I have the exact same GPS Hasan has.  I’m also running 
Meinberg.  I have the advantage of running Meinberg with internet time pools 
alongside the GPS.  While the GPS show significant jitter, its availability to 
Meinberg consistently yields <5ms offset from time.is.  Without the GPS, offset 
from time.is will run to 10-15ms.  I realize that is not a problem for WSJT-X, 
but my point is that even with jitter, the UPS GPS does improve my time 
accuracy, even if only a smidgen (note the techno speak ☺ )

__
Dan – K4SHQ

From: Roeland Jansen [mailto:roeland.janse...@gmail.com]
Sent: Wednesday, July 3, 2019 10:07 AM
To: WSJT software development 
Subject: Re: [wsjt-devel] clock patch

be aware of that if a) is 500 ms ahead and b) is 500 behind, the time skew is 
already 1 second between the signals.

Anything more than a few ms is not good imho. Anyways, use whatever deems 
suitable for you.


On Wed, Jul 3, 2019 at 4:33 PM Hasan al-Basri 
mailto:hbasri.schie...@gmail.com>> wrote:
Yep, I'm aware of the potential latency issues, again, 500 ms is quite 
acceptable for the X suite...and I see far better than that.

I haven't seen anywhere close to 500 ms errors against GPSDO (not usb) with my 
USB GPS. ..and that's with days of data collected and subject to statistical 
analysis. See the attached graphic.

Not perfect, but way better and way cheaper than most other alternatives, 
especially if stuck away from home. 73, N0AN
Hasan


On Wed, Jul 3, 2019 at 9:16 AM Roeland Jansen 
mailto:roeland.janse...@gmail.com>> wrote:
the issue is not the device but the USB protocol -- it's well known for latency 
issues. It's super that it works for you.

We have in .nl a few synchronized receivers and transmitters for repeaters and 
no way USB can be used there.

But hey -- if it works for you, it's ok. But be aware of the mentioned issues. 
And 500+ms wrong times are seen more.
I would not even consider it myself.


On Wed, Jul 3, 2019 at 3:57 PM Hasan al-Basri 
mailto:hbasri.schie...@gmail.com>> wrote:
Not all USB based GPS have issues. Not all software is the same. NMEATime2 does 
not show the issues you describe with a USB GPS. while the BKT software does. 
(for me)

This one, from Amazon works. I have two of them.

GlobalSat BU-353-S4 USB GPS Receiver (Black)

The above USB based GPS used with NMEATime2, is certainly accurate enough for 
all the WSJT-X suite of programsand many of us have the DT to prove it.

Please don't throw the baby out with the bath water, with a pursuit of 
unnecessary perfection.

73, N0AN
Hasan


On Wed, Jul 3, 2019 at 3:07 AM Matthew Miller 
mailto:mmill...@mail.umw.edu>> wrote:
Beware those GPS receivers – I got one (unstable latency was throwing me off by 
as much as 550mS on NTP) and I found that when I tried to set up ntpd to use 
GPS it was showing jitter of around 0.8 seconds.

Further research, USB GPS is a BAD IDEA because there is often buffering in the 
serial-USB converter chips as well as overhead with the USB protocol.  
Depending on what port you use it may also be connected thru one or more hubs 
adding additional overhead and latency.  You may not “see” a hub but many 
computers now have internal USB hubs for touchpad, keyboard, webcams, 
touchscreens, Bluetooth, and a variety of other “built in” features that now 
all hang off internal hubs.

If you are going to go with a proper GPS time sync you really need a non-USB 
serial GPS and PPS input…which is not trivial.

Its not cheap, but I solved my problem with one of these…its plug and play then 
just set your computer to point at its IP address.  I now have a reliable 
source that indicates it has only 0.5mS jitter and 3mS latency even going thru 
multiple network switches and a fairly busy WiFi network.
https://timemachinescorp.com/product/gps-time-server-tm1000a/

There are also other cheaper DIY Raspberry Pi projects (which have some of 
their own challenges I didn’t feel like dealing with right now) that can be 
built for under $100 to make a stratum-1 time server that works without 
Internet but PLEASE PLEASE do not tell people to use USB GPS for time, its 
going to increase the problems not fix them!

-Matt / KK4NDE

From: Neal Pollack [mailto:nea...@gmail.com]
Sent: Wednesday, June 26, 2019 12:08 PM
To: WSJT software development
Subject: Re: [wsjt-devel] clock patch

Only some are due to lack of internet.
USB GPS receivers are now approx $12 USD on Ebay.  I have tested a few and they 
work fine with NMEAtime2. Which is none simple software.
The message could suggest what to do for both internet connected and off-grid 
users.  But really, to keep the message short, it should point to a help page 
or file that is specific to time setting options, rather than a huge user 
guide, since the public no longer reads very much.

With regard to time setting software, I really can't recommend BKTtimeSync for 
the same reasons we are discussing this issue:  It works for me but 

Re: [wsjt-devel] ALL.TXT (again)

[Dan Malcolm]

Because I want to search via my webserver, I have a separate PHP script that 
does the search.  Probably not as fast as MongoDB.  I do get good cohesive 
reports though.  I get a report for example that will show me just one of my 
QSO's, and will store results in a text file.  That makes it useful to refer to 
later, or to include in an email to my QSO partner.

All that said I would like to explore MongoDB.  The idea that query via js 
script may mean that I can still have private web access.  I use IIS on Win10 
and just the local machine can access it.

__
Dan – K4SHQ


-Original Message-
From: Greg Beam [mailto:ki7m...@gmail.com] 
Sent: Monday, July 1, 2019 3:47 PM
To: wsjt-devel@lists.sourceforge.net
Subject: Re: [wsjt-devel] ALL.TXT (again)

Hello All,

Here's an example from today's log:

Results: https://paste.ubuntu.com/p/382VVMth4S/

The query takes about (2) seconds or so using a $regex search on
7,390,224 logged events matching two callsigns; this is without being indexed 
nor field splitting. It is one string per line imported to a one field document 
in MongDB

I can post the script I used as a gist, if anyone is interested:

- Copies the ALL.TXT to $temp_file
- Converts it to CSV
- Generates two helper JS scripts
- Generates one example JS query
- Drops, then re-imports the alltext collection
- Runs the a sample Query.

Note: for incremental (daily) updates, there is no need to drop the collection 
(alltext) before inserting new events. I just do that for performance testing.

It's a simple one-line query command that would work on Win/Linux/Mac:

mongo < example.js

You can, if desired, write any number of commands to perform stats, lookup(s), 
whatever, and use the same easy method to query the DB. 
However, as this is a single sting entry, much of the analytical value would be 
missing, as the fields / categories are not captured.

73's
Greg, KI7MT



On 7/1/19 1:27 AM, Claude Frantz wrote:
> On 7/1/19 7:59 AM, Claude Frantz wrote:
> 
> Just as an example of code extract in perl:
> 
> if ($line =~ m/^(\d{4})-([A-Z][a-z]{2})-(\d{2})\b/ ) {
>  $day = $3 ;
>  $month_alpha = $2 ;
>  $year = $1 ;
> }
> elsif ($line =~ m/^(\d\d)(\d\d)(\d\d)_\d{6}\b/ ) {
>  $day = $3 ;
>  $month_num = $2 ;
>  $year = 2000 + $1 ;
> }
> elsif ($line =~ m/^(\d{4})-(\d\d)-(\d\d)\b/ ) {
>  $day = $3 ;
>  $month_num = $2 ;
>  $year = $1 ;
>  }
> 
> I have not tested it, I hope there is no error. This allow to decode 
> the
> 3 formats of ALL.TXT about which ones I remember about. Please note 
> that the month can be numeric or alpha. If alpha, you have to convert 
> to numeric, if you want to compare to a numeric value. Please note 
> also, that the mode switching was an extra line in previous formats.
> 
> Best wishes,
> Claude (DJ0OT)
> 
> 
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel


___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel


___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] ALL.TXT (again)

[Dan Malcolm]

That’s correct Claude.  

But my PHP program has to deal with both formats in 2019.  Given that one of 
the formats will  be found, all I have to detect is a change in month, which 
comes after the date is harvested from the line (string).

__
Dan – K4SHQ

-Original Message-
From: Claude Frantz [mailto:claude.fra...@bayern-mail.de] 
Sent: Sunday, June 30, 2019 12:50 PM
To: wsjt-devel@lists.sourceforge.net
Subject: Re: [wsjt-devel] ALL.TXT (again)

On 6/30/19 5:41 PM, Dan Malcolm wrote:

Hi Dan,

> Good point Mike.  Right now I’m using the PHP regex function and 
> “(\d{4})-(\d{2})-(\d{2})”.  That worked until the format change.  The 
> function returns a T/F status and sticks the result into an array.

This doesn't match with the current format.

> Claude recommended a regex '^\d{6}_\d{6}\b' to detect the new format.  
> I think both will work.

The regex, which I have mentioned, works fine with the current format, but not 
with previous ones.

Best wishes,
Claude (DJ0OT)


___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel


___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] ALL.TXT (again)

[Dan Malcolm]

Good point Mike.  Right now I’m using the PHP regex function and 
“(\d{4})-(\d{2})-(\d{2})”.  That worked until the format change.  The function 
returns a T/F status and sticks the result into an array.

Claude recommended a regex '^\d{6}_\d{6}\b' to detect the new format.  I think 
both will work.  I’ll do some research to see which method would be quickest 
and to see if PHP has a ‘sscanf’ comparable function.  I’ll have to use both 
for the time being as 2019’s ALL.TXT will have both formats.

Thanks to both of you.

__
Dan – K4SHQ

From: Black Michael [mailto:mdblac...@yahoo.com]
Sent: Sunday, June 30, 2019 7:53 AM
To: 'WSJT software development' ; Dan Malcolm 

Subject: Re: [wsjt-devel] ALL.TXT (again)

This logic should work until the format changes in 2099 or so unless it's just 
allowed to roll over in which case it will still work.
You just need to get the current yymm instead of a "saved" date.
If the yymm changes that will allow you to track any idle period correctly.


#include 
#include 

int main(int nargs, char *argv[])
{
  int yymmsave = 0;
  char buf[256];

  FILE *fp = fopen(argv[1], "r");
  if (fp == NULL)
  {
perror(argv[1]);
exit(1);
  }

  while (fgets(buf, sizeof(buf), fp))
  {
int yymm, dd, time;
int n = sscanf(buf, "%4d%2d_%6d", , , );

if (n == 3 && yymm != yymmsave)
{
  printf("%04d\n", yymm);
  yymmsave = yymm;
}
  }

  fclose(fp);
}

de Mike W9MDB










On Saturday, June 29, 2019, 11:32:47 PM CDT, Dan Malcolm 
mailto:k4...@outlook.com>> wrote:



I’m thinking that if I know I’m in year ‘19’ and the month changes from ’02 to 
GT ‘02’ then I can count that as a month change.  Not likely but I can envision 
where I wounn’t be on the air for a month or more.



__

Dan – K4SHQ



From: Black Michael via wsjt-devel [mailto:wsjt-devel@lists.sourceforge.net]
Sent: Saturday, June 29, 2019 10:39 PM
To: wsjtx-devel 
mailto:wsjt-devel@lists.sourceforge.net>>
Cc: Black Michael mailto:mdblac...@yahoo.com>>
Subject: Re: [wsjt-devel] ALL.TXT (again)



There's nothing special about the month rollover



The format is YYMMDD so here's the Feb-Mar rollover in my file for example.



190228_23594514.074 Rx FT8 -3  0.9 2255 WB4HMA HC2AO -11

190301_0014.074 Rx FT8-13  0.9 2598 VE1DBM LU1JAO -08



de Mike W9MDB





On Saturday, June 29, 2019, 09:35:19 PM CDT, Dan Malcolm 
mailto:k4...@outlook.com>> wrote:





I am aware that ALL.TXT data formatting changed in late February this year.  I 
am trying to write a PHP program to split All.TXT in monthly text files.  I 
have program that does this for 2018, but it only finds January and February of 
2019.  The problem is probably a format change. Can anyone help me find the 
first entry of the month format?  Is it MMDD_”time”? or something similar?



__

Dan – K4SHQ



___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net<mailto:wsjt-devel@lists.sourceforge.net>
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] ALL.TXT (again)

[Dan Malcolm]

I’m thinking that if I know I’m in year ‘19’ and the month changes from ’02 to 
GT ‘02’ then I can count that as a month change.  Not likely but I can envision 
where I wounn’t be on the air for a month or more.

__
Dan – K4SHQ

From: Black Michael via wsjt-devel [mailto:wsjt-devel@lists.sourceforge.net]
Sent: Saturday, June 29, 2019 10:39 PM
To: wsjtx-devel 
Cc: Black Michael 
Subject: Re: [wsjt-devel] ALL.TXT (again)

There's nothing special about the month rollover

The format is YYMMDD so here's the Feb-Mar rollover in my file for example.

190228_23594514.074 Rx FT8 -3  0.9 2255 WB4HMA HC2AO -11
190301_0014.074 Rx FT8-13  0.9 2598 VE1DBM LU1JAO -08

de Mike W9MDB


On Saturday, June 29, 2019, 09:35:19 PM CDT, Dan Malcolm 
mailto:k4...@outlook.com>> wrote:



I am aware that ALL.TXT data formatting changed in late February this year.  I 
am trying to write a PHP program to split All.TXT in monthly text files.  I 
have program that does this for 2018, but it only finds January and February of 
2019.  The problem is probably a format change. Can anyone help me find the 
first entry of the month format?  Is it MMDD_”time”? or something similar?



__

Dan – K4SHQ


___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net<mailto:wsjt-devel@lists.sourceforge.net>
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

[wsjt-devel] ALL.TXT (again)

[Dan Malcolm]

I am aware that ALL.TXT data formatting changed in late February this year.  I 
am trying to write a PHP program to split All.TXT in monthly text files.  I 
have program that does this for 2018, but it only finds January and February of 
2019.  The problem is probably a format change. Can anyone help me find the 
first entry of the month format?  Is it MMDD_”time”? or something similar?

__
Dan – K4SHQ

___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Monthly ALL.TXT archives

[Dan Malcolm]

I use a combination of the ALL.TXT breakup techniques.  I keep it yearly as I’m 
not quite so active as Gary.  My ALL.TXT file ran to 1.2 TB last year.  I use a 
PHP app I wrote that suits me.  It allows me to search by year including the 
current year.  About 0100 I have a scheduled copy of the current ALL.TXT copied 
to a search directory.  In the event I need to search since then I have a 
trivial batch file that can copy the most current version.  All searches are 
performed on copies, not the live file.  My searches are probably complicated 
more than need be because the rig and WSJT-X runs 24/7 unless there is a 
thunder storm or I’m on vacation.

__
Dan – K4SHQ

From: Gary Hinson [mailto:g...@isect.com]
Sent: Wednesday, June 26, 2019 5:36 PM
To: 'WSJT software development' 
Subject: Re: [wsjt-devel] Monthly ALL.TXT archives

Hi Roy.

I am very active on FT8, clocking up about 900 FT8 QSOs per month and 
monitoring open HF FT8 subbands all ZL day while I work on the adjacent screen.

My ALL.TXT typically grows to more than 30 Mb per month e.g.:

[cid:image001.png@01D52C51.0A1E2AE0]

Early each new month, I manually add the previous month’s ALL.TXT to a ZIP 
archive.  Luckily the ALL.TXT data structure is very simple so it compresses 
down neatly to about 40 Mb per year:

[cid:image003.png@01D52C51.0A1E2AE0]

I sometimes need to check through my ALL.TXT for details of a QSO that someone 
has claimed on a QSL card or by email, but doesn’t appear in my Logger32 
station log.  It’s easy to open the relevant month’s ALL.TXT section from the 
ZIP archive and search for the QSO in question … and almost always I find a 
nearly-completed or completed QSO that for some reason wasn’t transferred to 
Logger32.

If you try opening the current ALL.TXT file in, say, Notepad while WSJT-X or 
JTDX is still running, you’ll probably get pop-up warnings every 15 seconds 
that the file has been updated when new decodes are written to it: that doesn’t 
happen if you are using a closed/archived ALL.TXT file.

So, monthly ALL.TXTs are worthwhile for highly active stations … and I think 
they would be useful for almost everyone.

73
Gary  ZL2iFB

From: Roy Gould mailto:roygou...@gmail.com>>
Sent: 27 June 2019 03:52
To: WSJT software development 
mailto:wsjt-devel@lists.sourceforge.net>>
Subject: Re: [wsjt-devel] Monthly ALL.TXT archives

Thanks for the education. Before you started discussing the ALL.TXT file I did 
not know it existed. So I decided to check it out and see what it was all 
about. Here are some things that I found out about it in my case.

The file in my computer was nearly 24 MB in size. I double clicked on it and it 
immediately came into Notepad on my Windows 10 computer so I could take a look 
at it. I tried Finding things such as CQ FD and it found several of those. I 
searched for my call sign (W7IDM) and it found it. I discovered that beginning 
on 19/02/27 that the format of the data stored was radically different and put 
into a much better format. So I deleted all of the previous entries leaving 
only the new format and that became the file that I am currently using. This 
file is about 6 MB in length.

I tried loading the file into EXCEL from Office 365 and EXCEL said that it 
looks like this data is in fixed width columns and asked if I agreed. I said 
yes and the data came in just fine. Now that it is in EXCEL format I have the 
ability to use the powerful EXCEL data base functions to do a lot of different 
types of analysis.

I don't see any particular need to want to break it into monthly segments. 
Perhaps it would be good to save it in yearly segments. It appears that I can 
easily work with a whole year of data at a time, so why break it up monthly?

So, for what it is worth, these are my observations...

73, Roy, W7IDM


On Tue, Jun 25, 2019 at 11:55 AM Sam W2JDB via wsjt-devel 
mailto:wsjt-devel@lists.sourceforge.net>> 
wrote:
Hi,

I recompiled the program with "openread" and "sharedenynone" but it seems that 
when wsjtx attempts to append to the file I received the same error message.

BTW, I open the file and close the file as soon as I finish scanning the file. 
It is only at the end of the decode when wsjtx is attempting to append to the 
file while alltext.exe is still parsing the file that the error pops up. If the 
scan finishes before wsjtx attempts to append to the file, there is no error.

Sorry, but that is the best that I can do. As I posted before, I do not use the 
alltext.exe while wsjtx is running.

Sam W2JDB



-Original Message-
From: DG2YCB, Uwe mailto:dg2...@gmx.de>>
To: 'WSJT software development' 
mailto:wsjt-devel@lists.sourceforge.net>>
Sent: Tue, Jun 25, 2019 12:13 pm
Subject: Re: [wsjt-devel] Monthly ALL.TXT archives
Sam,
alltext.exe works great, BUT there is one big disadvantage: Once the ALL.txt 
file is opened with alltext.exe, the ALL.TXT file is locked by Windows. And due 
to that WSJT-X is showing error messages “Cannot open …ALL.TXT” 

Re: [wsjt-devel] Observation on decoding

[Dan Malcolm]

Michael,
One issue I found, was that even though I followed your instructions, I had my 
Win10 set to 2 channel 48Khz for recording.  Audio cleaned up very well once I 
set it to 1 channel 48Khz

__
Dan – K4SHQ

From: Black Michael via wsjt-devel [mailto:wsjt-devel@lists.sourceforge.net]
Sent: Thursday, June 6, 2019 7:15 AM
To: David Kaplan via wsjt-devel 
Cc: Black Michael 
Subject: Re: [wsjt-devel] Observation on decoding

Gary -- I've work on a dozens of rigs...probably including all the ones you 
have.

If you are unable to get at least 90W with no ALC then something in your audio 
path is incorrect.

I'd like to work with you and ensure that either my directions need updating or 
your settings need updating.

Did you follow the procedure in the document I sent?  That has worked on every 
rig/audio combo I've tested which is over 300 operators now.

Can you call me an we can hook up and figure this out?  Gotta' make sure the 
info I'm putting out is as inclusive as possible.

321-690-2551
Mike W9MDB




On Thursday, June 6, 2019, 1:24:58 AM CDT, Gary - K7EK via wsjt-devel 
mailto:wsjt-devel@lists.sourceforge.net>> 
wrote:


Absolutely. I own six different Icom HF rigs. All of them put out minuscule 
power unless there is a significant deflection on the ALC meter. The no ALC 
warning does NOT apply to all rigs. I agree with RTFM. You cannot go wrong.
Best regards,
Gary, K7EK
Radcliff, KY (EM77at)

Sent from BlueMail
On Jun 5, 2019, at 15:42, Ron WV4P mailto:wv4...@gmail.com>> 
wrote:
Contrary to common belief..  You better feed that 7300 some ALC if you want it 
to perform. All radios are NOT the same and some need ALC. Ron, WV4P

On Wed, Jun 5, 2019, 2:34 PM Tom Ramberg via wsjt-devel < 
wsjt-devel@lists.sourceforge.net> 
wrote:
Sorry for posting this in the wrong thread. Now Trying to delete it and repost-

OH6VDA Tom

Sendt fra min iPad Air 2

5. jun. 2019 kl. 22:26 skrev Tom Ramberg < 
oh6...@yahoo.com>:
I just checked my computer soundcard settings and followed your procedure to 
set up the radio, the computer and the tranceiver, resulting in a seemingly 
dramatic enhancement of operation efficiency. For one thing (operator error, no 
doubt), I've never checked that the sound card sample rate was  48kHz 16-bit 
before, and of course it was not. Thanks a lot!

73 de Tom OH6VDA

Sendt fra min iPad Air 2

5. jun. 2019 kl. 15:01 skrev Black Michael via wsjt-devel < 
wsjt-devel@lists.sourceforge.net>:
For the IC-7300 you want the ALC meter to show no action at all.  So if it ever 
bumps up at all you've got too much audio going into the rig and need to back 
off the USB Mod Level.

You should be able to transmit 100W with no ALC (or very close to 100W).

That is the goal of all rigssome of the newer rigs will show < 0dB ALC 
(e.g. K3) though so it pays to learn what your ALC meter is really telling you. 
 The way you do that is set your rig for 100W, WSJT-X power slider at -3dB, 
computer audio out at 0dB, then adjust rig/external sound to show 50W tranmit 
power going out.  That should be 0dB ALC and shows you what to expect when 
transmitting close to the 100W.  Many rigs cannot do 100W with no ALC so have 
to back off to 95W maximum or such.  So as you gradually increase the power 
slider in WSJT-X (use the up cursor key) watch your ALC as you approach 100W.  
If you start seeing ALC you have to back off the audio level at the rig or 
external sound card so the WSJT-X slider can be at 0dB and no ALC showing.

de Mike W9MDB




On Tuesday, June 4, 2019, 12:06:34 PM CDT, Black Michael via wsjt-devel < 
wsjt-devel@lists.sourceforge.net> 
wrote:


If you reduce power from WSJT-X (not from the rig) does your ALC drop?  If 
so...that's too much audio.

Mike




On Tuesday, June 4, 2019, 11:57:44 AM CDT, Gene Marsh < 
w8...@me.com> wrote:


Mike,

My ALC is ~25% @80W.  But, I have no issues with transmit.  Only observing the 
double decode.  Everything else is good.

73 de W8NET Miles / “ Gene”
Secretary, Portage County Amateur Radio Service (PCARS)
3905 Century Club - Master #47
DV2/W8NET in the Philippines
Licensed since 1974

On Jun 4, 2019, at 12:46 PM, Black Michael < 
mdblac...@yahoo.com> wrote:
I do believe 63% audio on the IC7300 is wayy too much audio.  What does 
your ALC meter say?

de Mike W9MDB




On Tuesday, June 4, 2019, 11:44:04 AM CDT, Gene Marsh via wsjt-devel < 
wsjt-devel@lists.sourceforge.net> 
wrote:


Joe,

My setup:

Windows 10 Pro - see the pic:




-rc7
IC-7300
USB audio codec @66% volume

Need more info?

I will try to save a wav file next time I see it.


73 de W8NET Miles / “ Gene”
Secretary, Portage County Amateur Radio Service (PCARS)
3905 Century Club - Master #47
DV2/W8NET in the 

Re: [wsjt-devel] K4SHQ audio question

[Dan Malcolm]

Yep.  I have already done that and found you are right.  Problem fixed.  I 
still have an echo problem with Audio Enhancements Off.  But that’s not a 
problem for this forum.

Thanks Bill

__
Dan – K4SHQ

From: Bill Turner via wsjt-devel [mailto:wsjt-devel@lists.sourceforge.net]
Sent: Monday, April 29, 2019 7:29 PM
To: WSJT software development 
Cc: Bill Turner 
Subject: [wsjt-devel] K4SHQ audio question

Sounds like an update issue, time to reboot the computer.

Bill, W4WNT

On Monday, April 29, 2019, 8:01:13 PM EDT, Dan Malcolm 
mailto:k4...@outlook.com>> wrote:


Voicemeeter Banana

__
Dan – K4SHQ


-Original Message-
From: Bill Somerville 
[mailto:g4...@classdesign.com<mailto:g4...@classdesign.com>]
Sent: Monday, April 29, 2019 4:52 PM
To: wsjt-devel@lists.sourceforge.net<mailto:wsjt-devel@lists.sourceforge.net>
Subject: Re: [wsjt-devel] WSJT-X 2.1.0-rc5

On 29/04/2019 22:43, Dan Malcolm wrote:
> Just installed WSJT-X 2.1.0 RC5 x64 on my Win10 x64 machine.  Tx works and 
> seems to be OK, but something rerouted audio from VMB to my system speakers.  
> No audio received by WSJT-X (either in RC5 or 2.0.2 ) , but I can sure hear 
> the caterwauling in the speakers.  The best I can tell, Win10's wonderful 
> audio routing system (App volume and device preferences) is set correctly.  
> FWIW I am running VMB 2.0.4.7.
>
> Prior to installing RC5 everything was working fine.
>
> __
> Dan – K4SHQ

Hi Dan,

what is VMB?

73
Bill
G4WJS.



___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net<mailto:wsjt-devel@lists.sourceforge.net>
https://lists.sourceforge.net/lists/listinfo/wsjt-devel



___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net<mailto:wsjt-devel@lists.sourceforge.net>
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] WSJT-X 2.1.0-rc5

[Dan Malcolm]

All is not without problems.  I didn't have any know pending updates, and 
WSJT-X 2.0.1 is working again but I am left with an echo.  Audio enhancements 
are turned off, and the echo persists.  Unless you have something off the top 
of your head, I rather not eat up forum bandwidth on this issue.  I will find a 
fix somewhere.

Thanks Bill

__
Dan – K4SHQ

-Original Message-
From: Bill Somerville [mailto:g4...@classdesign.com] 
Sent: Monday, April 29, 2019 7:19 PM
To: wsjt-devel@lists.sourceforge.net
Subject: Re: [wsjt-devel] WSJT-X 2.1.0-rc5

Hi Dan,

glad to here that as I have nothing else! Windows 10 seems to behave very badly 
when there are pending updates to install.

73
Bill
G4WJS.

On 30/04/2019 01:15, Dan Malcolm wrote:
> Should have done this before asking. A reboot of the computer did the trick.  
> Thanks Bill.
>
> __
> Dan – K4SHQ
>
> -Original Message-
> From: Dan Malcolm [mailto:k4...@outlook.com]
> Sent: Monday, April 29, 2019 6:58 PM
> To: 'WSJT software development' 
> Subject: Re: [wsjt-devel] WSJT-X 2.1.0-rc5
>
> Voicemeeter Banana
>
> __
> Dan – K4SHQ
>
>
> -Original Message-
> From: Bill Somerville [mailto:g4...@classdesign.com]
> Sent: Monday, April 29, 2019 4:52 PM
> To: wsjt-devel@lists.sourceforge.net
> Subject: Re: [wsjt-devel] WSJT-X 2.1.0-rc5
>
> On 29/04/2019 22:43, Dan Malcolm wrote:
>> Just installed WSJT-X 2.1.0 RC5 x64 on my Win10 x64 machine.  Tx works and 
>> seems to be OK, but something rerouted audio from VMB to my system speakers. 
>>  No audio received by WSJT-X (either in RC5 or 2.0.2 ) , but I can sure hear 
>> the caterwauling in the speakers.  The best I can tell, Win10's wonderful 
>> audio routing system (App volume and device preferences) is set correctly.  
>> FWIW I am running VMB 2.0.4.7.
>>
>> Prior to installing RC5 everything was working fine.
>>
>> __
>> Dan – K4SHQ
> Hi Dan,
>
> what is VMB?
>
> 73
> Bill
> G4WJS.



___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel


___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] WSJT-X 2.1.0-rc5

[Dan Malcolm]

Voicemeeter Banana

__
Dan – K4SHQ


-Original Message-
From: Bill Somerville [mailto:g4...@classdesign.com] 
Sent: Monday, April 29, 2019 4:52 PM
To: wsjt-devel@lists.sourceforge.net
Subject: Re: [wsjt-devel] WSJT-X 2.1.0-rc5

On 29/04/2019 22:43, Dan Malcolm wrote:
> Just installed WSJT-X 2.1.0 RC5 x64 on my Win10 x64 machine.  Tx works and 
> seems to be OK, but something rerouted audio from VMB to my system speakers.  
> No audio received by WSJT-X (either in RC5 or 2.0.2 ) , but I can sure hear 
> the caterwauling in the speakers.  The best I can tell, Win10's wonderful 
> audio routing system (App volume and device preferences) is set correctly.  
> FWIW I am running VMB 2.0.4.7.
>
> Prior to installing RC5 everything was working fine.
>
> __
> Dan – K4SHQ

Hi Dan,

what is VMB?

73
Bill
G4WJS.



___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel


___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] WSJT-X 2.1.0-rc5

[Dan Malcolm]

Just installed WSJT-X 2.1.0 RC5 x64 on my Win10 x64 machine.  Tx works and 
seems to be OK, but something rerouted audio from VMB to my system speakers.  
No audio received by WSJT-X (either in RC5 or 2.0.2 ) , but I can sure hear the 
caterwauling in the speakers.  The best I can tell, Win10's wonderful audio 
routing system (App volume and device preferences) is set correctly.  FWIW I am 
running VMB 2.0.4.7. 

Prior to installing RC5 everything was working fine.

__
Dan – K4SHQ

-Original Message-
From: Christoph Berg [mailto:c...@df7cb.de] 
Sent: Monday, April 29, 2019 4:16 PM
To: wsjt-devel@lists.sourceforge.net
Subject: Re: [wsjt-devel] WSJT-X 2.1.0-rc5

Re: James Shaver 2019-04-29 
> I’m on 20 meters - After about 2-3 minutes of operating, I’m seeing the mode 
> getting changed back to FT8 and my frequency is jumping to 14.074.  This 
> appears to be random (though it still shows the “FT4” configuration as being 
> selected).  Selecting FT4 as the mode does not put me back to 14.080 but 
> closing the program and reopening brings me back to where I need to be. A 
> reboot appears to have cured this but FYI in case anyone else is 
> experiencing a similar issue.  

I have a similar problem. I was manually tuning to 7,047 and everything seemed 
normal (apart from the occasional "Rig control error" popups that I had always 
popping up every 10 minutes or so).
But when I added the FT4 freqs to the configuration, the program started 
randomly changing bands, mostly after the end of the TX cycle.
I could complete a few QSOs on 30m and 20m, but after every second TX cycle or 
so, it would jump to the 80m or 40m FT4 freqs.

Maybe my rig control is much more instable than the occasional "Rig control 
error" popups suggest, but wsjtx 2.0.x was able to ignore most of them. Now it 
seems that it jumps bands on each of them.

I have true rig split mode active, which worked fine in 2.0.x.

Christoph


___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel


___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] ALL.TXT - a suggestion

[Dan Malcolm]

Thanks Claude,
Most changes won't matter, because my utility will still find what I'm looking 
for.  What I'm having to correct is my reporting format.  

__
Dan – K4SHQ

-Original Message-
From: Claude Frantz [mailto:claude.fra...@bayern-mail.de] 
Sent: Thursday, April 11, 2019 11:04 AM
To: wsjt-devel@lists.sourceforge.net
Subject: Re: [wsjt-devel] ALL.TXT - a suggestion

On 4/11/19 3:43 PM, Dan Malcolm wrote:

> Missed this in the release notes, but I see it now.  I found:
> 
> “Better formatting for the files ALL.TXT and ALL_WSPR.TXT”
> 
> Since I’ve written an ALL.TXT utility in PHP, the new format will 
> require some coding on my part.  Not a bad thing really.  I’m sure a 
> review of my code will reveal better ways of performing some things.  
> It looks like now the ‘df’ offset is recorded in ALL.TXT for both ‘Tx’ and 
> ‘Rx.

Hi Dan,

The format of the ALL.TXT file has changed more that once. Be prepared to 
encounter more changes in the future.

Best wishes,
Claude (DJ0OT)


___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel


___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] ALL.TXT - a suggestion

[Dan Malcolm]

Missed this in the release notes, but I see it now.  I found:



“Better formatting for the files ALL.TXT and ALL_WSPR.TXT”

Since I’ve written an ALL.TXT utility in PHP, the new format will require some 
coding on my part.  Not a bad thing really.  I’m sure a review of my code will 
reveal better ways of performing some things.  It looks like now the ‘df’ 
offset is recorded in ALL.TXT for both ‘Tx’ and ‘Rx.

__
Dan – K4SHQ

From: Black Michael via wsjt-devel [mailto:wsjt-devel@lists.sourceforge.net]
Sent: Thursday, April 11, 2019 7:38 AM
To: WSJT software development 
Cc: Black Michael 
Subject: Re: [wsjt-devel] ALL.TXT - a suggestion

If you are perusing you can use Windows "find" or Unix's "grep"

For example, to get all messages with your callsign and redirect the output to 
a file.
find "G0HDB" all.txt >g0hdb.txt

Or all Tx messages
find "Tx" all.txt >mytx.txt

On Unix just substitute "grep" for "find".
de Mike W9MDB




On Thursday, April 11, 2019, 4:02:42 AM CDT, Martin Davies G0HDB 
mailto:marting0...@gmail.com>> wrote:


Running WSJT-X v2.0.1 7ddcb7 on a Win 7 Pro (32-bit) Dell Optiplex 780.

Although I like much of the new format for the information in the ALL.TXT file, 
it's now
relatively difficult to quickly identify my outgoing transmissions amidst the 
mass of 'Rx'
records in the file.

In the previous version(s) of ALL.TXT, a transmission was very clearly 
identified by the
'Transmitting' label, which resulted in much-extended lines of text that were 
immediately
apparent when perusing the file, whereas in the new file format the 
transmissions are now
designated solely by the 'Tx' label which are extremely difficult to spot 
amongst all the 'Rx'
labels.

Could consideration please be given to reverting to using the 'Transmitting' 
label, or some
other means (eg. colour-coding?) of more clearly differentiating the 
transmissions in the
ALL.TXT file.

73, and thanks in advance,

---
Martin, G0HDB


---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus



___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Someone released an Auto CQ mod - my 2 cents

[Dan Malcolm]

Correction: If all you is to collect QSO’s without actually being involved, 
makes no sense to me.  Seems like buying a good book just to look at, without 
reading it.

__
Dan – K4SHQ

From: Dan Malcolm [mailto:k4...@outlook.com]
Sent: Sunday, March 31, 2019 2:25 PM
To: 'WSJT software development' 
Subject: Re: [wsjt-devel] Someone released an Auto CQ mod - my 2 cents

Regulations aside, why did we become hams?  If all you want is to collect QSO’s 
without being actually involved, why spend the time and money on education and 
equipment?  Sorry, I vote against further animation of FT8 or any other 
protocol.  Some automation is helpful, too be sure, but there is such a thing 
as too much.

Just my $0.02.
__
Dan – K4SHQ

From: w2ctx [mailto:w2...@comcast.net]
Sent: Sunday, March 31, 2019 1:49 PM
To: WSJT software development 
mailto:wsjt-devel@lists.sourceforge.net>>
Subject: Re: [wsjt-devel] Someone released an Auto CQ mod - my 2 cents

How does the system know the frequency is not in use before transmitting?




Sent from my Verizon, Samsung Galaxy smartphone

 Original message 
From: Dave AA6YQ mailto:aa...@ambersoft.com>>
Date: 3/31/19 2:30 PM (GMT-05:00)
To: 'WSJT software development' 
mailto:wsjt-devel@lists.sourceforge.net>>
Subject: Re: [wsjt-devel] Someone released an Auto CQ mod - my 2 cents

+ AA6YQ comments below

Why not. Amateur Radio was supposed to be experimental.

+ The experiment could be conducted without making it easy for users to setup 
unattended 7x24 CQing and QSO completion. Think the FT8 "watering holes" are 
packed now? Wait until there are several thousand unattended stations around 
the world continuously CQing and attempting to work every callsign they haven't 
yet worked.





___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net<mailto:wsjt-devel@lists.sourceforge.net>
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Someone released an Auto CQ mod - my 2 cents

[Dan Malcolm]

Regulations aside, why did we become hams?  If all you want is to collect QSO’s 
without being actually involved, why spend the time and money on education and 
equipment?  Sorry, I vote against further animation of FT8 or any other 
protocol.  Some automation is helpful, too be sure, but there is such a thing 
as too much.

Just my $0.02.
__
Dan – K4SHQ

From: w2ctx [mailto:w2...@comcast.net]
Sent: Sunday, March 31, 2019 1:49 PM
To: WSJT software development 
Subject: Re: [wsjt-devel] Someone released an Auto CQ mod - my 2 cents

How does the system know the frequency is not in use before transmitting?




Sent from my Verizon, Samsung Galaxy smartphone

 Original message 
From: Dave AA6YQ mailto:aa...@ambersoft.com>>
Date: 3/31/19 2:30 PM (GMT-05:00)
To: 'WSJT software development' 
mailto:wsjt-devel@lists.sourceforge.net>>
Subject: Re: [wsjt-devel] Someone released an Auto CQ mod - my 2 cents

+ AA6YQ comments below

Why not. Amateur Radio was supposed to be experimental.

+ The experiment could be conducted without making it easy for users to setup 
unattended 7x24 CQing and QSO completion. Think the FT8 "watering holes" are 
packed now? Wait until there are several thousand unattended stations around 
the world continuously CQing and attempting to work every callsign they haven't 
yet worked.





___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Possible change to UDP interface - set TX audio offset

[Dan Malcolm]

Just had to but in, in support of what Bill has said.  The WSJT-X development 
team has done us all a great service in improving WSJT-X.  The automation that 
accompanies FT8 are a godsend for that relatively fast paced protocol.  
However, there can be too much of a good thing.  I participate in this hobby 
because I enjoy it.  That means I need to participate, not set up an auto-QSO 
system that will perform and log QSO's even when I'm sleeping.  I think the 
developers have hit on just the right amount of automation/user participation 
for FT8.

Just my $0.02 worth.  73 

__
Dan – K4SHQ

-Original Message-
From: Bill Somerville [mailto:g4...@classdesign.com] 
Sent: Tuesday, January 22, 2019 6:28 AM
To: wsjt-devel@lists.sourceforge.net
Subject: Re: [wsjt-devel] Possible change to UDP interface - set TX audio offset

On 22/01/2019 11:07, Mike Chamberlain wrote:
> If ‘Hold TX Frequency’ is checked, to avoid interference it is 
> necessary to check that the transmit offset frequency last used by my 
> station is still clear in the period that I wish to use it – that 
> requires bringing WSJT-X back into focus and a visual inspection, 
> which is time consuming.

Hi Mike,

the final part of  your point above makes it hard to justify such a change. The 
WSJT-X UDP protocol was never intended to be a remote control interface to 
WSJT-X and if it is changed such that WSJT-X can remain minimized for all or 
part of a QSO then I think that is beyond the scope of the intended use. That 
combined with many thousands of QSOs having been initiated using the UDP Reply 
message by JTAlert and other software users yet yours is the first request for 
a Tx offset setting facility. There is also another objection in that operators 
must be aware of users of other modes that might suffer QRM from a poor choice 
of Tx offset, an external application does not see or analyse the waterfall 
display other than by the information provided in decoded messages. There is no 
substitute for having an eye on the waterfall display to avoid any deliberate 
QRM to other users.

73
Bill
G4WJS.



___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel


___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] wrong time logged

[Dan Malcolm]

FWIW I am running both WSJT-X v2 and JTAlert 2.12.10.  I rarely shut down 
either program and my computer and rig run 24/7.  I never have this problem.  
Of course saying it just now may cause it to start (Murphy’s Law).

__
Dan – K4SHQ

From: m...@handgunrepairshop.com [mailto:m...@handgunrepairshop.com]
Sent: Friday, January 11, 2019 1:04 PM
To: k...@arrl.net; WSJT software development 
Subject: Re: [wsjt-devel] wrong time logged

I have also experienced this logging start time issue many times, at least back 
as far as v1.8, usually after an aborted/incomplete or abandoned QSO. I have no 
idea why the previously aborted QSO start time does not clear when the Esc. or 
F4 key is used to clear the QSO from the DX Call & DX Grid boxes.
It does seem a bit ironic to me that a program that depends on 1 second time 
correctness for decodes, and always correctly logs the Tx frequency to 1 Hz 
accuracy, has a problem keeping up with the actual current QSO start time?
I am not a computer programmer, but apparently fixing this ongoing logging 
issue is more than the dev team wants to deal with.
Having said that, I do want to express my thanks to all the dev team for this 
software. My log has grown over 4,000 more QSOs since beginning to use WSJT-X!

73 de KV4ZY, Doug

 Original Message 
Subject: [wsjt-devel] wrong time logged
From: Al mailto:k...@arrl.net>>
Date: Fri, January 11, 2019 11:41 am
To: wsjt-devel@lists.sourceforge.net

(WSJT-X V2.0.0, W 10 )
This may have been reported before ??

I was on earlier today and made several 80 contacts ending at 1319.
I left the radio running  and came back at ~16:17 and changed bands to 17m.
My first contact on 17m was at 16:19 but the logs recorded that contact time at 
13:21.

AL, K0VM


___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] strange non-qso

[Dan Malcolm]

I understand Serge, but one way to find out is to see if you are in his
logbook via QRZ.  I agree it's difficult just looking at the QSO text, and I
appreciate Bill's comment.  I also agree with Bill that logging the QSO
makes the most sense.

__
Dan - K4SHQ


-Original Message-
From: F6BHK [mailto:f6...@f6bhk.org] 
Sent: Tuesday, December 25, 2018 10:29 AM
To: wsjt-devel@lists.sourceforge.net
Subject: Re: [wsjt-devel] strange non-qso

Dan

Thank you for your answer, however my questioning is on the software side,
not on the call itself.

With the following messages from WSJT-X, I feel - I can be wrong, but - I
feel that I cannot decide whether the QSO is completed or not completed.
See, the last message I read from the 4X station is not clear as to whether
this message is for me or for someone else.


73

Serge


On 25/12/2018 17:14, Dan Malcolm wrote:
> A search of QRZ found 4X19HNY and there is a pointer to their live log 
> on that page.
>
> __
> Dan - K4SHQ
>
> -Original Message-
> From: F6BHK [mailto:f6...@f6bhk.org]
> Sent: Tuesday, December 25, 2018 9:30 AM
> To: WSJT software development 
> Subject: [wsjt-devel] strange non-qso
>
> Merry Xmas to all!
>
> The following QSO seems to me "strange":
>
> 151630 -17  0.4 1694 ~  CQ 4X19HNY
> 151646  Tx  1694 ~  <4X19HNY> F6BHK
> 151715  Tx  1694 ~  <4X19HNY> F6BHK
> 151730 -17  0.4 1694 ~  F6BHK <4X19HNY> -22
> 151745  Tx  1694 ~  <4X19HNY> F6BHK R-17
> 151815  Tx  1694 ~  <4X19HNY> F6BHK R-17
> 151800 -22  0.4 1693 ~  F6BHK <4X19HNY> -22
> 151816  Tx  1694 ~  <4X19HNY> F6BHK R-22
> 151845  Tx  1694 ~  <4X19HNY> F6BHK R-22
> 151900 -19  0.3 1693 ~  <...> 4X19HNY RR73
> 151915 -16  1.1 1694 ~  <4X19HNY> SQ2BNM -15
>
> in the sense I am not able to be sure 4X19HNY has got my report. I 
> would have expected <...> being  instead.
>
> 73
>
> Serge
>
>

-- 

73, de Serge
F6BHK, ex-VR2LL, G5BHT, FM5GC
PUY SAINT MARTIN, 26 DROME, FRANCE
JN24LP



___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel



___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] strange non-qso

[Dan Malcolm]

A search of QRZ found 4X19HNY and there is a pointer to their live log on
that page.

__
Dan - K4SHQ

-Original Message-
From: F6BHK [mailto:f6...@f6bhk.org] 
Sent: Tuesday, December 25, 2018 9:30 AM
To: WSJT software development 
Subject: [wsjt-devel] strange non-qso

Merry Xmas to all!

The following QSO seems to me "strange":

151630 -17  0.4 1694 ~  CQ 4X19HNY
151646  Tx  1694 ~  <4X19HNY> F6BHK
151715  Tx  1694 ~  <4X19HNY> F6BHK
151730 -17  0.4 1694 ~  F6BHK <4X19HNY> -22
151745  Tx  1694 ~  <4X19HNY> F6BHK R-17
151815  Tx  1694 ~  <4X19HNY> F6BHK R-17
151800 -22  0.4 1693 ~  F6BHK <4X19HNY> -22
151816  Tx  1694 ~  <4X19HNY> F6BHK R-22
151845  Tx  1694 ~  <4X19HNY> F6BHK R-22
151900 -19  0.3 1693 ~  <...> 4X19HNY RR73
151915 -16  1.1 1694 ~  <4X19HNY> SQ2BNM -15

in the sense I am not able to be sure 4X19HNY has got my report. I would
have expected <...> being  instead.

73

Serge


-- 

73, de Serge
F6BHK, ex-VR2LL, G5BHT, FM5GC
PUY SAINT MARTIN, 26 DROME, FRANCE
JN24LP



___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel



___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] File Open Error

[Dan Malcolm]

Bill,
That’s my guess too.  I have in the past excluded the WSJT-X directories from 
virus scans, but perhaps I missed one.  Thanks

__
Dan – K4SHQ

From: Bill Somerville [mailto:g4...@classdesign.com]
Sent: Thursday, December 20, 2018 7:11 AM
To: wsjt-devel@lists.sourceforge.net
Subject: Re: [wsjt-devel] File Open Error

On 20/12/2018 12:52, Dan Malcolm wrote:
affected file is ALL.TXT.  I will proceed with tracking down the offending 
application, but it would have been helpful if there was a timestamp on the 
error dialog.  That would narrow down the things to look at.  Thanks.

__
Dan – K4SHQ

Hi Dan,

I would guess at either a scheduled backup or a virus scan is locking the fie 
while you have decodes running.

73
Bill
G4WJS.
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

[wsjt-devel] File Open Error

[Dan Malcolm]

I have been getting a File Open Error from v2.0.  It occurs every night, and 
I’ll have multiple notifications.  The affected file is ALL.TXT.  I will 
proceed with tracking down the offending application, but it would have been 
helpful if there was a timestamp on the error dialog.  That would narrow down 
the things to look at.  Thanks.

__
Dan – K4SHQ

___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Is it just me? v2.0?

[Dan Malcolm]

Not the squelch, but it was my PC’s time sync program that quit working.  It 
was BkTimeSync and was on trial, doing a good job, till last night, when it 
locked up.  I normally use Meinberg.  I think I’ll go back to it.

__
Dan – K4SHQ

From: John Scheuer [mailto:johnusche...@gmail.com]
Sent: Tuesday, December 11, 2018 2:26 PM
To: wsjt-devel@lists.sourceforge.net
Subject: Re: [wsjt-devel] Is it just me? v2.0?

I can appreciate what you're going through Dan believe me. HI.  Is it possible 
that the squelch is involved, this could cause it to act erratic. Since it 
works some of the time it got me thinking.

John

On Tue, Dec 11, 2018 at 2:34 PM Dan Malcolm 
mailto:k4...@outlook.com>> wrote:
Thanks John,
I usually call CQ 10 or more times, after setting tx/rx to a clear spot.  My 
power meter shows power out, so I am at least transmitting.  I am on 7.074 as 
Joe suggested, but I have my tx/rx bandwidth set to 4k so I can see well up the 
band.  One of the advantages of an SDR.  Sound card setting are as they should 
be and that verified because I can transmit and receive.  The waterfall shows 
more than a dozen signals but none are decoded.  I should mention that I had a 
similar experience on 20m this morning.

After posting the original email, I tried stepping bat to c1.9.1.  No help.  I 
am running VM Banana for Virtual Audio and it’s been solid since installation 
several months ago.

__
Dan – K4SHQ

From: John Scheuer 
[mailto:johnusche...@gmail.com<mailto:johnusche...@gmail.com>]
Sent: Tuesday, December 11, 2018 1:11 PM
To: wsjt-devel@lists.sourceforge.net<mailto:wsjt-devel@lists.sourceforge.net>
Subject: Re: [wsjt-devel] Is it just me? v2.0?

Dan,
What freq are you using on 40. I always use 7075. My freq gets changed once in 
a while and I find I am not on the freq I think I am. hi.

I use PSK Reporter. Might give that  a try and see if it shows anything 
different.

When the rig is keyed does it show out put power. I had a problem a while back. 
The rig was keyed but no out put.

One other thing you may want to check is your sound cards. I had a problem with 
erratic behavior and found for some unknown reason the cards were changing. I 
don't know if I ever figured out why but it's been working fine for some time 
now.

When you call cq it may take a while. If you are only calling 3 or 4 times I 
think you're a bit optimistic. hi
I look on the waterfall for what apears to be a clear spot and set my receive 
and xmit there.

Hope that helps,
John-NA6Y

I am also running 2.0



On Tue, Dec 11, 2018 at 1:47 PM Dan Malcolm 
mailto:k4...@outlook.com>> wrote:
Yesterday I downloaded and installed v2.0.  No issue installing, and made a QSO 
on the first run.  Made several other QSO’s during the day, and thought all was 
well.  This morning?  Nada…..nothing….sort of.  I am getting a few decodes on 
40 and 20 but it’s sparse.  Enough to indicate decoding is working.  Then I 
tried calling CQ several time with no results whatever.  Even HamSpots says 
that I haven’t been heard in more than a day.

So do I just be patient and wait for a bigger v2.0 population or do I have a 
problem?  I suspect I am just being impatient.

__
Dan – K4SHQ

___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net<mailto:wsjt-devel@lists.sourceforge.net>
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net<mailto:wsjt-devel@lists.sourceforge.net>
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Is it just me? v2.0?

[Dan Malcolm]

Uwe,
Yes.  That was the problem.  I had just discovered and fixed that, and found 
your email.  For some unknown reason BkTimeSync had stopped working.  It was on 
trial anyway, and was doing a good job.  However when I was running Meinberg, I 
never had a seconds trouble.

Thanks Uwe/

__
Dan – K4SHQ

From: DG2YCB, Uwe [mailto:dg2...@gmx.de]
Sent: Tuesday, December 11, 2018 1:43 PM
To: 'WSJT software development' 
Subject: Re: [wsjt-devel] Is it just me? v2.0?

Dan, does your PC time eventually need to be synchronized? Check deviation at 
https://time.is/

73 de Uwe, DG2YCB

Von: Dan Malcolm [mailto:k4...@outlook.com]
Gesendet: Dienstag, 11. Dezember 2018 20:30
An: 'WSJT software development'
Betreff: Re: [wsjt-devel] Is it just me? v2.0?

Thanks John,
I usually call CQ 10 or more times, after setting tx/rx to a clear spot.  My 
power meter shows power out, so I am at least transmitting.  I am on 7.074 as 
Joe suggested, but I have my tx/rx bandwidth set to 4k so I can see well up the 
band.  One of the advantages of an SDR.  Sound card setting are as they should 
be and that verified because I can transmit and receive.  The waterfall shows 
more than a dozen signals but none are decoded.  I should mention that I had a 
similar experience on 20m this morning.

After posting the original email, I tried stepping bat to c1.9.1.  No help.  I 
am running VM Banana for Virtual Audio and it’s been solid since installation 
several months ago.

__
Dan – K4SHQ

From: John Scheuer [mailto:johnusche...@gmail.com]
Sent: Tuesday, December 11, 2018 1:11 PM
To: wsjt-devel@lists.sourceforge.net<mailto:wsjt-devel@lists.sourceforge.net>
Subject: Re: [wsjt-devel] Is it just me? v2.0?

Dan,
What freq are you using on 40. I always use 7075. My freq gets changed once in 
a while and I find I am not on the freq I think I am. hi.

I use PSK Reporter. Might give that  a try and see if it shows anything 
different.

When the rig is keyed does it show out put power. I had a problem a while back. 
The rig was keyed but no out put.

One other thing you may want to check is your sound cards. I had a problem with 
erratic behavior and found for some unknown reason the cards were changing. I 
don't know if I ever figured out why but it's been working fine for some time 
now.

When you call cq it may take a while. If you are only calling 3 or 4 times I 
think you're a bit optimistic. hi
I look on the waterfall for what apears to be a clear spot and set my receive 
and xmit there.

Hope that helps,
John-NA6Y

I am also running 2.0



On Tue, Dec 11, 2018 at 1:47 PM Dan Malcolm 
mailto:k4...@outlook.com>> wrote:
Yesterday I downloaded and installed v2.0.  No issue installing, and made a QSO 
on the first run.  Made several other QSO’s during the day, and thought all was 
well.  This morning?  Nada…..nothing….sort of.  I am getting a few decodes on 
40 and 20 but it’s sparse.  Enough to indicate decoding is working.  Then I 
tried calling CQ several time with no results whatever.  Even HamSpots says 
that I haven’t been heard in more than a day.

So do I just be patient and wait for a bigger v2.0 population or do I have a 
problem?  I suspect I am just being impatient.

__
Dan – K4SHQ

___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net<mailto:wsjt-devel@lists.sourceforge.net>
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Is it just me? v2.0?

[Dan Malcolm]

Thanks John,
I usually call CQ 10 or more times, after setting tx/rx to a clear spot.  My 
power meter shows power out, so I am at least transmitting.  I am on 7.074 as 
Joe suggested, but I have my tx/rx bandwidth set to 4k so I can see well up the 
band.  One of the advantages of an SDR.  Sound card setting are as they should 
be and that verified because I can transmit and receive.  The waterfall shows 
more than a dozen signals but none are decoded.  I should mention that I had a 
similar experience on 20m this morning.

After posting the original email, I tried stepping bat to c1.9.1.  No help.  I 
am running VM Banana for Virtual Audio and it’s been solid since installation 
several months ago.

__
Dan – K4SHQ

From: John Scheuer [mailto:johnusche...@gmail.com]
Sent: Tuesday, December 11, 2018 1:11 PM
To: wsjt-devel@lists.sourceforge.net
Subject: Re: [wsjt-devel] Is it just me? v2.0?

Dan,
What freq are you using on 40. I always use 7075. My freq gets changed once in 
a while and I find I am not on the freq I think I am. hi.

I use PSK Reporter. Might give that  a try and see if it shows anything 
different.

When the rig is keyed does it show out put power. I had a problem a while back. 
The rig was keyed but no out put.

One other thing you may want to check is your sound cards. I had a problem with 
erratic behavior and found for some unknown reason the cards were changing. I 
don't know if I ever figured out why but it's been working fine for some time 
now.

When you call cq it may take a while. If you are only calling 3 or 4 times I 
think you're a bit optimistic. hi
I look on the waterfall for what apears to be a clear spot and set my receive 
and xmit there.

Hope that helps,
John-NA6Y

I am also running 2.0



On Tue, Dec 11, 2018 at 1:47 PM Dan Malcolm 
mailto:k4...@outlook.com>> wrote:
Yesterday I downloaded and installed v2.0.  No issue installing, and made a QSO 
on the first run.  Made several other QSO’s during the day, and thought all was 
well.  This morning?  Nada…..nothing….sort of.  I am getting a few decodes on 
40 and 20 but it’s sparse.  Enough to indicate decoding is working.  Then I 
tried calling CQ several time with no results whatever.  Even HamSpots says 
that I haven’t been heard in more than a day.

So do I just be patient and wait for a bigger v2.0 population or do I have a 
problem?  I suspect I am just being impatient.

__
Dan – K4SHQ

___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net<mailto:wsjt-devel@lists.sourceforge.net>
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

[wsjt-devel] Congrats to the WSJT-X development team

[Dan Malcolm]

Congratulation on the rc4 release of WSJT-X v2.

The only thing I’ve noticed is a decrease in decoded traffic.  Since we are now 
using FT8 77 bit, that seems normal to me.  As far as I’m concerned, everything 
is fine and you guys are on track for a final release.

Keep up the good work.

__
Dan – K4SHQ

___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

[wsjt-devel] Recurring problem with WSJT-X v2.0.0-rc3

[Dan Malcolm]

My rig is up 24/7.  Quite often after running overnight, or sitting idle during 
the day, the “Decode” button will just stay on.  Typically when this happens I 
don’t get any decodes showing up in JTAlert.  The fix is fairly simple, I just 
have to kill WSJT-X and restart it.  No error is thrown by the application, at 
least none I have seen.  My system is fairly new and robust so I don’t believe 
it’s being caused by a lack of computing resources.

I have seen the problem in earlier versions but it would be days or weeks 
between occurrences.  This time it’s a once or twice daily occurrence.

Aside from just letting the program run doing nothing but decode (no Tx ops) I 
have no idea how to cause it.  Tx still works with the Decode button stuck, and 
that’s probably normal.

73
__
Dan – K4SHQ

___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Why73 - RRR or RR73 ---isn't it a waste of time ?

[Dan Malcolm]

FWIW I agree with the pro-73 group.  It may be only a courtesy, but are we
so enamored of getting the next QSO that courtesy is unnecessary?  Contests
are a different animal, but in day to day operation, I appreciate the
courtesy.  In addition the need is documented in the several places, not the
least of which is the WSJT-X documentation, and as someone mentioned, may be
required for QSO credit for an award.

__
Dan – K4SHQ

-Original Message-
From: OG55W [mailto:og...@oh2j.info] 
Sent: Tuesday, October 16, 2018 4:04 AM
To: WSJT software development 
Subject: Re: [wsjt-devel] Why73 - RRR or RR73 ---isn't it a waste of time ?

73 is only a compliment! QSO is OK, if both stations have given R .

73 Keijo OG55W

-Alkuperäinen viesti- 
From: oe1...@oevsv.at
Sent: Tuesday, October 16, 2018 11:47 AM
To: wsjt-devel@lists.sourceforge.net
Subject: Re: [wsjt-devel] Why73 - RRR or RR73 ---isn't it a waste of time ?


Am 16.10.2018 um 09:04 schrieb IK1HJS Carlo De Mari:

[snipped]

Hi Carlo!

In my opinion I would prefer 73's from both partners as confirmation of
the QSO. Only then a QSO (in digital modes) is to be classified as being
complete for me.

vy73
Enrico, OE1EQW



___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel 



___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel



___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] WSJT-X 2.0.0-rc2 and JTAlertX Broken

[Dan Malcolm]

Broken here in Win10

__
Dan – K4SHQ

From: Bill Barrett [mailto:w2pky...@gmail.com]
Sent: Tuesday, September 25, 2018 4:23 PM
To: Black Michael ; WSJT software development 

Subject: Re: [wsjt-devel] WSJT-X 2.0.0-rc2 and JTAlertX Broken

Hello Mike;
Seems to be an issue on Windows 7Pro.
Doubled checked  on several times.

Bill
W2PKY

On Tue, Sep 25, 2018 at 4:47 PM Black Michael via wsjt-devel 
mailto:wsjt-devel@lists.sourceforge.net>> 
wrote:
Nope...works fine here on WIndows 10.

de Mike W9MDB



On Tuesday, September 25, 2018, 3:34:14 PM CDT, Gene H 
mailto:ghin...@gmail.com>> wrote:


I have seen a problem with today's release of -rc2 whereby when I click
on a valid JTAlertX callsign the information is not being received and
processed by WSJT-X 2.0.0-rc2. Are others seeing the same problem? It
was working correctly on the -rc1 release. Also, I verified this is now
broken on two different Win7 computers and a friends station computer.
The JTAlertX version is 2.12.5.

Thanks for any feedback.

73 K5PA



___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Subprocess Error: Subprocess failed with exit code 2

[Dan Malcolm]

I hate bringing this up again, but I was unable to find a resolution on my own, 
and a search of the wsjt-devel messages didn’t reveal anything either except 
that others have this problem.  I do find the file ‘houndcallers.txt’ does 
exist while wsjt-x is running.  When the error occurs the file has been 
deleted.  A search of Win10’s Event Viewer logs had no note of that file.  It 
appears something is deleting the file.

It’s my understanding the file exists to support FT8 DXpeditions.  I haven’t 
recently participated in any, nor have I turned on the FT8 settings to 
accommodate that.

So why do I need ‘houndcallers.txt’, what is deleting it, and who is ‘bill’ 
that keeps showing up in the error text?

I am running WSJT-X v1.9.1 and not any of the beta versions.  Until about 3 
weeks ago I had only read about the error but had experienced it.

__
Dan – K4SHQ

From: Black Michael via wsjt-devel [mailto:wsjt-devel@lists.sourceforge.net]
Sent: Thursday, June 14, 2018 5:52 PM
To: WSJT software development 
Cc: Black Michael 
Subject: Re: [wsjt-devel] Subprocess Error: Subprocess failed with exit code 2

Maybe your antivirus is getting in the way?
Can you put an exclusion on the directory?

de Mike W9MDBH




On Thursday, June 14, 2018, 4:54:13 PM CDT, Steve Sacco NN4X 
mailto:n...@embarqmail.com>> wrote:



Same as always.  Please let me know how I can assist.





Running: C:\WSJT\wsjtx\bin\jt9 -s WSJT-X -w 1 -m 3 -e C:\WSJT\wsjtx\bin -a 
C:\Users\Steve\AppData\Local\WSJT-X -t C:\Users\Steve\AppData\Local\Temp\WSJT-X

At line 81 of file C:\Users\bill\src\wsjt-svn\lib\decoder.f90 (unit = 19)

Fortran runtime error: Cannot open file 
'C:\Users\Steve\AppData\Local\Temp\WSJT-X/houndcallers.txt': No such file or 
directory
[cid:image001.png@01D43572.313E7E30]





--

Steve Sacco

NN4X

Narcoossee, FL

EL98jh
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! 
http://sdm.link/slashdot___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

[wsjt-devel] split frequency logging

[Dan Malcolm]

I am running WSJT-X v1.8.0 with “Hold Tx Freq” checked, and allow Rx frequency 
to float.  So most of my QSO’s have Rx frequencies different from my Tx 
frequencies.  During normal logging operations, the differences are captured, 
as they should be.  Every once in a while I will need to reconstruct a QSO for 
one reason or another.  Fortunately not that often.  When I do I use ALL.TXT 
because that is the only record of the QSO I have.  WSJT-X logs are only 
completed if log a QSO in near real time.

My problem is that only the Rx frequency offset is recorded in ALL.TXT.  I can 
live with it, and it’s not a huge problem, but are there any plans to include 
audio frequency offset in the Tx data entries in ALL.TXT?

__
Dan – K4SHQ

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] v1.8 release building

[Dan Malcolm]

Thanks Joe,
I have seen your posts to that effect before, but I occasionally see posts
that seem to hint at a v1.8 devel thread.  Guess I was misinterpreting those
posts.  Sorry about the unnecessary traffic.

__
Dan – K4SHQ

-Original Message-
From: Joe Taylor [mailto:j...@princeton.edu] 
Sent: Tuesday, December 19, 2017 11:56 AM
To: WSJT software development <wsjt-devel@lists.sourceforge.net>
Subject: Re: [wsjt-devel] v1.8 release building

Hi Dan,

On 12/19/2017 12:44 PM, Dan Malcolm K4SHQ wrote:
> I have obviously missed something.  I still have JTSDK and it still 
> builds v1.7.1 r.  But that is not for prime time code.  How to I 
> set things to build v1.8 devel releases?

As has been stated here several times before, the development branch is NOT
presently suitable for general use.  In due course there will probably be a
v1.8.1 release with minor bug fixes and perhaps some minor enhancements.

On a somewhat longer time scale, you may expect v1.8.2 (or possibly
v1.9) to be released, with many more feature additions.

How long is "somewhat longer"?  We can't tell you that.  In general we work
as fast as our available time allows.

For now, you should be using Version 1.8.0.

-- 73, Joe, K1JT


--
Check out the vibrant tech community on one of the world's most engaging
tech sites, Slashdot.org! http://sdm.link/slashdot
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel


--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

[wsjt-devel] v1.8 release building

[Dan Malcolm]

I have obviously missed something.  I still have JTSDK and it still builds 
v1.7.1 r.  But that is not for prime time code.  How to I set things to 
build v1.8 devel releases?

__
Dan – K4SHQ

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Split frequency logging

[Dan Malcolm]

Very cool Mike.  Thanks

__
Dan – K4SHQ

From: Black Michael via wsjt-devel [mailto:wsjt-devel@lists.sourceforge.net]
Sent: Saturday, November 25, 2017 6:55 AM
To: WSJT software development <wsjt-devel@lists.sourceforge.net>
Cc: Black Michael <mdblac...@yahoo.com>
Subject: Re: [wsjt-devel] Split frequency logging

That change is in beta testing for JTAlert right now.  And it's working

[Inline image]

de Mke W9MDB

On Saturday, November 25, 2017, 5:48:59 AM CST, Dan Malcolm 
<k4...@outlook.com<mailto:k4...@outlook.com>> wrote:


Claude et al,
Exactly.  That's why this is a development question.  The ADIF fields are
there, and apparently not being used, or I missed a setting somewhere.

I agree in principle with Karl.  Too much automation is not a good thing.
But as long as frequency is being logged, it should be done with the correct
frequencies.  If the WSJT-X developers don't want to deal with it fine.
Just say so and I'll continue manual corrections.  Not a big deal, but was
curious.

__
Dan – K4SHQ

-Original Message-
From: Claude Frantz 
[mailto:claude.fra...@bayern-mail.de<mailto:claude.fra...@bayern-mail.de>]
Sent: Wednesday, November 22, 2017 9:43 AM
To: wsjt-devel@lists.sourceforge.net<mailto:wsjt-devel@lists.sourceforge.net>
Subject: Re: [wsjt-devel] Split frequency logging

On 11/22/2017 02:25 PM, Dan Malcolm wrote:

Hi Dan & all,

> WSJT-X is pretty good at running QSO’s with ‘split’ frequency
> operation.  JTAlert is essential for smooth QSO tracking and logging.
> What I am missing is logging the separate frequencies for a split QSO.
> I suspect that most ops don’t track the different Tx and Rx
> frequencies, but I do.  Perhaps the data manager in me.
The ADIF specification defines a FREQ field containing the TX frequency in
MHz and an additional FREQ_RX field containing the RX frequency in MHz, in
the case of split operation.

Best wishes,
Claude (DJ0OT)


--
Check out the vibrant tech community on one of the world's most engaging
tech sites, Slashdot.org! http://sdm.link/slashdot
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net<mailto:wsjt-devel@lists.sourceforge.net>
https://lists.sourceforge.net/lists/listinfo/wsjt-devel



--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net<mailto:wsjt-devel@lists.sourceforge.net>
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Split frequency logging

[Dan Malcolm]

Claude et al,
Exactly.  That's why this is a development question.  The ADIF fields are
there, and apparently not being used, or I missed a setting somewhere.  

I agree in principle with Karl.  Too much automation is not a good thing.
But as long as frequency is being logged, it should be done with the correct
frequencies.  If the WSJT-X developers don't want to deal with it fine.
Just say so and I'll continue manual corrections.  Not a big deal, but was
curious.

__
Dan – K4SHQ

-Original Message-
From: Claude Frantz [mailto:claude.fra...@bayern-mail.de] 
Sent: Wednesday, November 22, 2017 9:43 AM
To: wsjt-devel@lists.sourceforge.net
Subject: Re: [wsjt-devel] Split frequency logging

On 11/22/2017 02:25 PM, Dan Malcolm wrote:

Hi Dan & all,

> WSJT-X is pretty good at running QSO’s with ‘split’ frequency 
> operation.  JTAlert is essential for smooth QSO tracking and logging.
> What I am missing is logging the separate frequencies for a split QSO. 
> I suspect that most ops don’t track the different Tx and Rx 
> frequencies, but I do.  Perhaps the data manager in me.
The ADIF specification defines a FREQ field containing the TX frequency in
MHz and an additional FREQ_RX field containing the RX frequency in MHz, in
the case of split operation.

Best wishes,
Claude (DJ0OT)


--
Check out the vibrant tech community on one of the world's most engaging
tech sites, Slashdot.org! http://sdm.link/slashdot
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel


--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

[wsjt-devel] FW: Split frequency logging

[Dan Malcolm]

WSJT-X is pretty good at running QSO’s with ‘split’ frequency operation.  
JTAlert is essential for smooth QSO tracking and logging.  What I am missing is 
logging the separate frequencies for a split QSO.  I suspect that most ops 
don’t track the different Tx and Rx frequencies, but I do.  Perhaps the data 
manager in me.  WSJT-X v18 display the frequencies set for Rx and Tx, but they 
don’t seem to propagate through JTAlert 2.10.4 to Log4OM.  The Tx frequency 
does and I can manually fix the Rx frequency which is just a copy of the Tx 
when logged.

Am I missing some setting?  If not are there any plans to propagate actual Rx 
frequencies separate from Tx?

__
Dan – K4SHQ

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

[wsjt-devel] Split frequency logging

[Dan Malcolm]

WSJT-X is pretty good at running QSO’s with ‘split’ frequency operation.  
JTAlert is essential for smooth QSO tracking and logging.  What I am missing is 
logging the separate frequencies for a split QSO.  I suspect that most ops 
don’t track the different Tx and Rx frequencies, but I do.  Perhaps the data 
manager in me.  WSJT-X v18 display the frequencies set for Rx and Tx, but they 
don’t seem to propagate through JTAlert 2.10.4 to Log4OM.  The Tx frequency 
does and I can manually fix the Rx frequency which is just a copy of the Tx 
when logged.

Am I missing some setting?  If not are there any plans to propagate actual Rx 
frequencies separate from Tx?

__
Dan – K4SHQ

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] WSJT-X 1.7.1 r8164

[Dan Malcolm]

Thanks Joe.  That's what I suspected, but its better coming from someone who
actually knows.

__
Dan – K4SHQ


-Original Message-
From: Joe Taylor [mailto:j...@princeton.edu] 
Sent: Friday, October 13, 2017 10:51 AM
To: WSJT software development 
Subject: Re: [wsjt-devel] WSJT-X 1.7.1 r8164

Hi Dan,

> I also have a question.  The FMT analysis program initially had an 
> error and referred to bad data.  The online manual does say to edit 
> the fmt.all file and remove bad data.  I did that and the analysis ran 
> without error.  I made a judgement call as to what constitutes “bad 
> data”, in this case anything more than 1.9 deviation was bad.  Is 
> there a better rule of thumb for “bad data”?

Happy to hear that you like the new capabilities for Frequency Calibration.

As for removing "bad data" from the file fmt.all: with a bit of accumulated
experience, your own judgment will continue to be the best guideline.

Data in the file look something like this (I have added the headings and
separator line):

   UTC  Freq CAL Offset  fMeas   DFLevel   S/N
   (kHz)  ?  (Hz) (Hz)  (Hz)(dB)   (dB)
--
14:35:09660  1  1500  1500.890 0.890  -11.6   19.2  *
14:35:11660  1  1500  1500.861 0.861  -16.4   39.7
14:35:13660  1  1500  1500.859 0.859  -18.7   42.2

For each calibration-station frequency "Freq" (here 660 kHz), the measured
audio frequencies "fMeas" and frequency offsets "DF" will typically agree to
within 1 Hz or better -- usually *much* better. 
Delete any outliers.  Measurements with estimated S/N less than 20 dB will
be flagged with an asterisk.  These are worth examining individually,
because they might be bad.  The one flagged above is OK.

-- 73, Joe, K1JT


--
Check out the vibrant tech community on one of the world's most engaging
tech sites, Slashdot.org! http://sdm.link/slashdot
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel


--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

[wsjt-devel] WSJT-X 1.7.1 r8164

[Dan Malcolm]

I just ran the new FMT in WSJT-X.  I like this better than the old way.  I do 
have one observation though.  The tooltip for slope and intercept refers reader 
to the WSPR documentation and it should reference section 13.  The correction 
should be made, but can be done the next time one of the developers is in the 
mood for documentation duty.

I also have a question.  The FMT analysis program initially had an error and 
referred to bad data.  The online manual does say to edit the fmt.all file and 
remove bad data.  I did that and the analysis ran without error.  I made a 
judgement call as to what constitutes “bad data”, in this case anything more 
than 1.9 deviation was bad.  Is there a better rule of thumb for “bad data”?

__
Dan – K4SHQ

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] current build?

[Dan Malcolm]

Thanks Erik.  That will save questions later.

__
Dan – K4SHQ

From: Erik - [mailto:erikcarl...@live.com]
Sent: Wednesday, October 11, 2017 8:34 AM
To: WSJT software development <wsjt-devel@lists.sourceforge.net>
Subject: Re: [wsjt-devel] current build?

You can know by checking 
https://sourceforge.net/p/wsjt/activity/?page=0=100#59d7acd35fcbc9472c435463

Erik

From: Dan Malcolm [mailto:k4...@outlook.com]
Sent: 11 October 2017 13:08
To: wsjtx-devel 
<wsjt-devel@lists.sourceforge.net<mailto:wsjt-devel@lists.sourceforge.net>>
Subject: [wsjt-devel] current build?

I make a new build of the WSJT-X devel branch nearly every day.  For the last 
several days, all I get back after a build is the same r8164.  Did I miss 
something or is that right?

__
Dan – K4SHQ

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

[wsjt-devel] current build?

[Dan Malcolm]

I make a new build of the WSJT-X devel branch nearly every day.  For the last 
several days, all I get back after a build is the same r8164.  Did I miss 
something or is that right?

__
Dan – K4SHQ

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Unable to Build

[Dan Malcolm]

That did it Richard.  Sometimes a little judicial brute force is all that's
needed.  Thanks.

__
Dan - K4SHQ


-Original Message-
From: Richard Stanley via wsjt-devel
[mailto:wsjt-devel@lists.sourceforge.net] 
Sent: Friday, September 29, 2017 5:14 PM
To: WSJT software development <wsjt-devel@lists.sourceforge.net>
Cc: Richard Stanley <m0c...@blueyonder.co.uk>
Subject: Re: [wsjt-devel] Unable to Build

It is a corrupt file somewhere, rename
C:/JTSDK/src/wsjtx to say C:/JTSDK/src/wsjtx1 Then try build-wsjtx rinstall
and it will build just fine and update after that.

Richard g7oed


-Original Message-----
From: Dan Malcolm
Sent: Friday, September 29, 2017 7:37 PM
To: 'WSJT software development'
Subject: Re: [wsjt-devel] Unable to Build

Bill,
I have the exact same problem.  If I skip the svn update, r8123 will compile
just fine.  It's only svn that seems to not work.  I tried just 'svn
cleanup' which (no surprise) did nothing, but then I don't know what
arguments to give it.  I'm sure there is a path as part of the cleanup
arguments.

__
Dan - K4SHQ


-Original Message-
From: Bill Somerville [mailto:g4...@classdesign.com]
Sent: Friday, September 29, 2017 7:05 AM
To: wsjt-devel@lists.sourceforge.net
Subject: Re: [wsjt-devel] Unable to Build

On 29/09/2017 12:10, Paul Maciel wrote:
> I'm not able to build the latest release and keep getting the message 
> that sourceforge is down even though they appear to be back up.

Hi Paul,

I have checked the SF svn servers a few times over the last hour or so and
they seem to be up and stable. You could try running the `svn cleanup`
command on your checked out working area:

$ svn help cleanup
cleanup: Recursively clean up the working copy, removing locks, resuming
unfinished operations, etc.
usage: cleanup [WCPATH...]

Valid options:
   --diff3-cmd ARG  : use ARG as merge command

Global options:
   --username ARG   : specify a username ARG
   --password ARG   : specify a password ARG
   --no-auth-cache  : do not cache authentication tokens
   --non-interactive: do no interactive prompting (default is to
prompt
  only if standard input is a terminal device)
   --force-interactive  : do interactive prompting even if standard
input
  is not a terminal device
   --trust-server-cert  : accept SSL server certificates from unknown
  certificate authorities without prompting (but
only
  with '--non-interactive')
   --config-dir ARG : read user configuration files from directory
ARG
   --config-option ARG  : set user configuration option in the format:
  FILE:SECTION:OPTION=[VALUE]
  For example:
  servers:global:http-library=serf

if that doesn't help; then try the option in the JTSDK to scrap and
re-checkout your workspace.

73
Bill
G4WJS.



--
Check out the vibrant tech community on one of the world's most engaging
tech sites, Slashdot.org! http://sdm.link/slashdot
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel



--
Check out the vibrant tech community on one of the world's most engaging
tech sites, Slashdot.org! http://sdm.link/slashdot
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel 


---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus



--
Check out the vibrant tech community on one of the world's most engaging
tech sites, Slashdot.org! http://sdm.link/slashdot
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel


--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Unable to Build

[Dan Malcolm]

Bill,
I have the exact same problem.  If I skip the svn update, r8123 will compile
just fine.  It's only svn that seems to not work.  I tried just 'svn
cleanup' which (no surprise) did nothing, but then I don't know what
arguments to give it.  I'm sure there is a path as part of the cleanup
arguments.

__
Dan - K4SHQ


-Original Message-
From: Bill Somerville [mailto:g4...@classdesign.com] 
Sent: Friday, September 29, 2017 7:05 AM
To: wsjt-devel@lists.sourceforge.net
Subject: Re: [wsjt-devel] Unable to Build

On 29/09/2017 12:10, Paul Maciel wrote:
> I'm not able to build the latest release and keep getting the message 
> that sourceforge is down even though they appear to be back up.

Hi Paul,

I have checked the SF svn servers a few times over the last hour or so and
they seem to be up and stable. You could try running the `svn cleanup`
command on your checked out working area:

$ svn help cleanup
cleanup: Recursively clean up the working copy, removing locks, resuming
unfinished operations, etc.
usage: cleanup [WCPATH...]

Valid options:
   --diff3-cmd ARG  : use ARG as merge command

Global options:
   --username ARG   : specify a username ARG
   --password ARG   : specify a password ARG
   --no-auth-cache  : do not cache authentication tokens
   --non-interactive: do no interactive prompting (default is to
prompt
  only if standard input is a terminal device)
   --force-interactive  : do interactive prompting even if standard
input
  is not a terminal device
   --trust-server-cert  : accept SSL server certificates from unknown
  certificate authorities without prompting (but
only
  with '--non-interactive')
   --config-dir ARG : read user configuration files from directory
ARG
   --config-option ARG  : set user configuration option in the format:
  FILE:SECTION:OPTION=[VALUE]
  For example:
  servers:global:http-library=serf

if that doesn't help; then try the option in the JTSDK to scrap and
re-checkout your workspace.

73
Bill
G4WJS.



--
Check out the vibrant tech community on one of the world's most engaging
tech sites, Slashdot.org! http://sdm.link/slashdot
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel


--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

[wsjt-devel] Can't access svn

[Dan Malcolm]

I still can’t get an svn update from Sourceforge, even though it appears to be 
up.  If I skip updating, and run with ‘clean’ enabled, WSJT-X builds just fine, 
but remains stuck at r8123.  Prior to Sourceforge being down for a couple of 
days this worked perfectly.  Maintenance reports v0706 Release 710 and was just 
updated/upgraded this morning.
__
Dan – K4SHQ

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Lost logging times

[Dan Malcolm]

Agree Joe, but hence the questions on this forum.  Given that we users are
not paying for this, I am appreciative of you and the rest of the
development teams efforts.  But sometimes I don't know why something works
the way it does.  I do think we users need to some research before a
question is asked.  I have seen many times on this forum where the same
question is asked over and over.  

-73
___
Dan - K4SHQ

-Original Message-
From: Joe Taylor [mailto:j...@princeton.edu] 
Sent: Thursday, September 21, 2017 11:09 AM
To: WSJT software development <wsjt-devel@lists.sourceforge.net>
Subject: Re: [wsjt-devel] Lost logging times

Hi Dan,

On 9/21/2017 11:54 AM, Dan Malcolm wrote:
> Joe, Michael,
> I don't disagree.  I do have a problem being the cognizant human being 
> at times, and yes it is my responsibility.  I just didn't realize how 
> things worked until now.  The online guide says nothing about this 
> behavior however (yes I did read it).
> 
> 'Nuff said.  It's on my head now.

No problem...

On the User Guide:

We put a lot of effort into this document.  We want people to read it,
because WSJT-X is a complex program.  Many people don't read it, as you can
tell from some traffic here and on the wsjtgroup email list.  In part this
may be because the Guide is already some 90 pages long.  We don't have the
space (nor the inclination) to describe of every detail of every program
function.

-- Joe, K1JT


--
Check out the vibrant tech community on one of the world's most engaging
tech sites, Slashdot.org! http://sdm.link/slashdot
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel


--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Lost logging times

[Dan Malcolm]

Joe, Michael,
I don't disagree.  I do have a problem being the cognizant human being at
times, and yes it is my responsibility.  I just didn't realize how things
worked until now.  The online guide says nothing about this behavior however
(yes I did read it).

'Nuff said.  It's on my head now.

Dan - K4SHQ

-Original Message-
From: Joe Taylor [mailto:j...@princeton.edu] 
Sent: Thursday, September 21, 2017 10:34 AM
To: WSJT software development <wsjt-devel@lists.sourceforge.net>
Subject: Re: [wsjt-devel] Lost logging times

Dan --

On 9/21/2017 11:21 AM, Dan Malcolm wrote:
> Yes I did log it twice because the first attempt failed.  But since the
QSO is reflected in the log entry, the times should still be correct.

WSJT-X does not attempt to replace the cognizant human being using it. 
All logging information is presented to you for review, before you click
"OK".

As station operator it's your responsibility to maintain your log as you
want it maintained.

-- Joe, K1JT


--
Check out the vibrant tech community on one of the world's most engaging
tech sites, Slashdot.org! http://sdm.link/slashdot
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel


--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Lost logging times

[Dan Malcolm]

Yes I did log it twice because the first attempt failed.  But since the QSO is 
reflected in the log entry, the times should still be correct.

Dan – K4SHQ

From: Black Michael via wsjt-devel [mailto:wsjt-devel@lists.sourceforge.net]
Sent: Thursday, September 21, 2017 10:09 AM
To: WSJT Software Development <wsjt-devel@lists.sourceforge.net>
Cc: Black Michael <mdblac...@yahoo.com>
Subject: Re: [wsjt-devel] Lost logging times

Looks to me like you logged it twice.
The times reset after you log it so logging it a 2nd time without a QSO will 
use the current time in both.

de Mike W9MDB


On Thursday, September 21, 2017, 10:00:17 AM CDT, Dan Malcolm 
<k4...@outlook.com<mailto:k4...@outlook.com>> wrote:



I just noticed that QSO start/stop times are getting logged more as logging 
times rather than the times encompassing the QSO.  The QSO shown in the screen 
capture wasn’t logged until a few minutes later.  Checking the Log4OM entry,  
both start & stop times were 14:44:00.  The WSJT-X log shows two lines, since I 
didn’t have Log4OM running the first logging attempt (my bad):



2017-09-21,14:30:15,2017-09-21,14:31:15,VE1JS,FN64,14.074968,FT8,+03,-02,,,

2017-09-21,14:44:13,2017-09-21,14:44:13,VE1JS,FN64,14.074968,FT8,+03,-02,,,



The first line has the correct start/stop times, but the second line is 
obviously wrong, and that’s what got sent to Log4OM.



__

Dan – K4SHQ


--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! 
http://sdm.link/slashdot___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net<mailto:wsjt-devel@lists.sourceforge.net>
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

[wsjt-devel] Lost logging times

[Dan Malcolm]

I just noticed that QSO start/stop times are getting logged more as logging 
times rather than the times encompassing the QSO.  The QSO shown in the screen 
capture wasn’t logged until a few minutes later.  Checking the Log4OM entry,  
both start & stop times were 14:44:00.  The WSJT-X log shows two lines, since I 
didn’t have Log4OM running the first logging attempt (my bad):

2017-09-21,14:30:15,2017-09-21,14:31:15,VE1JS,FN64,14.074968,FT8,+03,-02,,,
2017-09-21,14:44:13,2017-09-21,14:44:13,VE1JS,FN64,14.074968,FT8,+03,-02,,,

The first line has the correct start/stop times, but the second line is 
obviously wrong, and that’s what got sent to Log4OM.

__
Dan – K4SHQ

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] WSJTX Problem with FT8 Config

[Dan Malcolm]

Found the problem.  I caused it but not sure why.  In setting->Frequencies in 
the Station Information block, I had entered an offset of 14.074.000.  That 
should be left at zero.  Never the less, in a dialog box labeled “Station 
Information”, I didn’t think the offset would affect anything except what was 
reported to PSKReporter.  I knew there was something odd about the set 
frequency being double what was called for.

 

From: Black Michael via wsjt-devel [mailto:wsjt-devel@lists.sourceforge.net] 
Sent: Monday, August 07, 2017 12:33 PM
To: WSJT software development <wsjt-devel@lists.sourceforge.net>
Cc: Black Michael <mdblac...@yahoo.com>
Subject: Re: [wsjt-devel] WSJTX Problem with FT8 Config

 

Have you rebuilt hamlib recently?

 

I'm running r8013 on an ANAN 100 and don't see this behavior.

 

And have you tried resetting the default frequencies?  Seems that cures all 
sort of strange frequency behavior.

 

File/Settings/Frequences and right-click in the Working Frequencies and select 
Reset.

 

de Mike W9MDB

 

 

  _____  

From: Dan Malcolm <dan.malcol...@gmail.com <mailto:dan.malcol...@gmail.com> >
To: wsjtx-devel <wsjt-devel@lists.sourceforge.net 
<mailto:wsjt-devel@lists.sourceforge.net> > 
Sent: Monday, August 7, 2017 12:26 PM
Subject: [wsjt-devel] WSJTX Problem with FT8 Config

 

 

I am running WSJT-X 1.7.1 r8013 (and can run v1.8 RC1 and v1.7.1).  I have both 
an Apache ANAN 100D and a Yaesu FT-950.  This just started this morning and I 
don’t know the cause.  The problem actually started while running r8003.  If 
you look at the screen captures please look at them in pairs.  The “FT8 Config” 
pair go together, as does the “JT65 Config” pair.

 

I am at a loss to explain the cause.  While using the “FT8 Config” WSJT-X is 
only happy when it shows 14.074 in the frequency window, or any other frequency 
selected by WSJT-X.  With 14.074 in the WSJT-X frequency window,  PowerSDR is 
set at 28.148 Mhz.  With any other WSJT-X selected frequency, both WSJT-X and 
PowerSDR agree and are happy.  Only 14.074 shows an issue.  The problem is also 
only exhibited while using the Apache ANAN 100D.  If I switch to the FT-950 
everything works perfectly.

 

If I use the PowerSDR controls to set 14.074Mhz in PowerSDR,  WSJT-X shows all 
zero’s with a red background.

 

My first thought was something had happened to the PowerSDR database, so I 
rebuilt that from scratch.  No help.  Uninstalled and rebooted and then 
reinstalled PowerSDR.  No help.  Built a fresh this morning WSJT-X v1.7.1 
r8013.  No help.

 

I’m not yet done with the weirdness.  If I use the ANAN 100D and WSJT-X but 
switch to the JT65/9 Mode it all works just fine.  The one common item seems to 
be the “FT8 Config”.  I cloned the working “JT65-9  Config” and made it the 
“FT8 Config”.  The problem remains.  The only constant left is FT8 and 14.074 
while using the Kenwood TS-2000 radio model (which has always worked fine).  So 
I tried the TS-50S. No help. 

 

I’m out of ideas.  I’m not entirely sure at this point that the WSJTX beta 
software is at fault, but being beta it’s a place to start.

 

_

Dan Malcolm – K4SHQ

CFI/II

 

Whoever said life is hard was wrong; life's only hard when you
get off the couch and actually do stuff.

 

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! 
http://sdm.link/slashdot___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net <mailto:wsjt-devel@lists.sourceforge.net> 
https://lists.sourceforge.net/lists/listinfo/wsjt-devel



--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] WSJTX Problem with FT8 Config

[Dan Malcolm]

I rebuilt HamLib about a week ago.  Right after the build changes were 
implemented.  I have reset the default frequencies 3 or 4 times today.  Since 
it has been a few days for HamLib3,  I’ll go ahead and build it again.

 

Dan – K4SHQ

 

From: Black Michael via wsjt-devel [mailto:wsjt-devel@lists.sourceforge.net] 
Sent: Monday, August 07, 2017 12:33 PM
To: WSJT software development <wsjt-devel@lists.sourceforge.net>
Cc: Black Michael <mdblac...@yahoo.com>
Subject: Re: [wsjt-devel] WSJTX Problem with FT8 Config

 

Have you rebuilt hamlib recently?

 

I'm running r8013 on an ANAN 100 and don't see this behavior.

 

And have you tried resetting the default frequencies?  Seems that cures all 
sort of strange frequency behavior.

 

File/Settings/Frequences and right-click in the Working Frequencies and select 
Reset.

 

de Mike W9MDB

 

 

  _____  

From: Dan Malcolm <dan.malcol...@gmail.com <mailto:dan.malcol...@gmail.com> >
To: wsjtx-devel <wsjt-devel@lists.sourceforge.net 
<mailto:wsjt-devel@lists.sourceforge.net> > 
Sent: Monday, August 7, 2017 12:26 PM
Subject: [wsjt-devel] WSJTX Problem with FT8 Config

 

 

I am running WSJT-X 1.7.1 r8013 (and can run v1.8 RC1 and v1.7.1).  I have both 
an Apache ANAN 100D and a Yaesu FT-950.  This just started this morning and I 
don’t know the cause.  The problem actually started while running r8003.  If 
you look at the screen captures please look at them in pairs.  The “FT8 Config” 
pair go together, as does the “JT65 Config” pair.

 

I am at a loss to explain the cause.  While using the “FT8 Config” WSJT-X is 
only happy when it shows 14.074 in the frequency window, or any other frequency 
selected by WSJT-X.  With 14.074 in the WSJT-X frequency window,  PowerSDR is 
set at 28.148 Mhz.  With any other WSJT-X selected frequency, both WSJT-X and 
PowerSDR agree and are happy.  Only 14.074 shows an issue.  The problem is also 
only exhibited while using the Apache ANAN 100D.  If I switch to the FT-950 
everything works perfectly.

 

If I use the PowerSDR controls to set 14.074Mhz in PowerSDR,  WSJT-X shows all 
zero’s with a red background.

 

My first thought was something had happened to the PowerSDR database, so I 
rebuilt that from scratch.  No help.  Uninstalled and rebooted and then 
reinstalled PowerSDR.  No help.  Built a fresh this morning WSJT-X v1.7.1 
r8013.  No help.

 

I’m not yet done with the weirdness.  If I use the ANAN 100D and WSJT-X but 
switch to the JT65/9 Mode it all works just fine.  The one common item seems to 
be the “FT8 Config”.  I cloned the working “JT65-9  Config” and made it the 
“FT8 Config”.  The problem remains.  The only constant left is FT8 and 14.074 
while using the Kenwood TS-2000 radio model (which has always worked fine).  So 
I tried the TS-50S. No help. 

 

I’m out of ideas.  I’m not entirely sure at this point that the WSJTX beta 
software is at fault, but being beta it’s a place to start.

 

_

Dan Malcolm – K4SHQ

CFI/II

 

Whoever said life is hard was wrong; life's only hard when you
get off the couch and actually do stuff.

 

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! 
http://sdm.link/slashdot___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net <mailto:wsjt-devel@lists.sourceforge.net> 
https://lists.sourceforge.net/lists/listinfo/wsjt-devel



--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] WSJT-X logging error

[Dan Malcolm]

Bill,

Yes you do make hard work for yourselves.  Sigh.  I guess you'll just have
to live with talent, skill and success.  I for one am grateful you guys do
this.  Thanks.

 

Dan - K4SHQ

 

From: Bill Somerville [mailto:g4...@classdesign.com] 
Sent: Wednesday, August 02, 2017 8:25 AM
To: wsjt-devel@lists.sourceforge.net
Subject: Re: [wsjt-devel] WSJT-X logging error

 

On 02/08/2017 14:16, Dan Malcolm wrote:

 

I have not seen this before.  I am running WSJT-X 1.7.1-devel r7972. 

 

I had a FT8 QSO with NP3DM.  Just off my frequency was another QSO going on
with K5GA and VE3FON.  No problem as the decoder seemed to handle both QSO's
separately.  When logging time came however, VE3FON was logged to Log4OM no
NP3DM.  See attached screen captures.  The logging chain starts with WSJT-X
and WSJT-X is only offering VE3FON.  The last line of wsjtx.log is this
line:
"2017-08-02,12:50:00,2017-08-02,12:52:15,VE2FON,,14.075312,FT8,-01,-19,20,FT
8  Sent: -01  Rcvd: -19,"

Hi Dan,

this is a slightly tricky situation to deal with. We accept any message with
the word 73 as a sign off that triggers logging but in this case it also
picked up the callsign even though the message was not for you. This
behaviour is only when the decode is +/- 10Hz of your frequency and it just
crept in. Looks like we will have to detect that it is a standard 73 message
but not for you, that will stop it sending 73 to a station that you didn't
work as well.

We make hard work for ourselves by having such a good decoder that can
disentangle signals on top of each other.

73
Bill
G4WJS.

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

[wsjt-devel] Thumbs up

[Dan Malcolm]

 

I saw this mentioned on the forum, and now see it in action with r7958.
When answering a CQ and the CQ'ing station replies to another station,
WSJT-X disables "Enable Tx" taking me out of the loop.  I like it.  Reduces
QRM.  Big thumbs up to the developers.

 

73

 

Dan Malcolm = K4SHQ

 

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] WSJT-X: How to handle using RR73 as a final message

[Dan Malcolm]

Bill,
I'm sure I'm not alone, but I require some acknowledgement of receipt of
signal report.  I'm not hard over about what that is, be it 73 or RR73.
Personally I like a 73 term from both stations but I think it's logical for
the original CQ station to terminate the QSO with RR73.  At that point call
signs, grids, and RST's have been exchanged and acknowledged.  Therefore
sending RR73 should be treated the same as sending 73.  That's fine for the
original CQ station, and his QSO partner who receives the RR73/73.  However,
the QSO partner who doesn't decode a RR73/73 is left hanging.  In my case, I
resend R+dB, and so should the software.  Waiting a decode cycle after
sending RR73/73 to ensure QSO completion seems like a good scenario.  If
either nothing or 73 is received from the answering CQ partner, the original
CQ station can assume the RR73/73 was received.  The same would be true if
the answering CQ stations call sign is spotted in another QSO or calling CQ.

That's my logic.  I hope it's clear.  In the end, the individual op is going
to have to pay attention and perhaps apply their own logic in any given
situation.

-Original Message-
From: Bill Somerville [mailto:g4...@classdesign.com] 
Sent: Thursday, July 20, 2017 7:18 AM
To: WSJT software development 
Subject: [wsjt-devel] WSJT-X: How to handle using RR73 as a final message

Hi All,

we are looking at changing the WSJT-X logic such that a grid message of the
form:

"  RR73"

is treated as a sign off message.

This has several implications and I need some clarification so that I can
adjust the code. For now I will put aside any potential issues for holders
of compound callsigns as I have not analysed the impact for them yet.

The first change is already in place, sending such an RR73 message is
treated the same as sending a standard 73 message or any free text message
containing the word "73". This means that, if prompt to log after 73 is set
the log QSO window will be popped up, and if
"Settings->General->Behavior->Disable Tx after 73" is checked, auto transmit
will be disabled and the next message to be sent will be moved on to Tx6 (CQ
message). This part is straightforward.

I propose to add a check box option to "Settings->General->Behavior" 
along the lines of "Use RR73 in place of RRR", when checked this would
generate the above RR73 message for the Tx4 (RRR) message, thus formalizing
the usage of RR73 as a final QSO message.

So now the questions. If we have disabled auto Tx and switched the next
message to Tx6/CQ, how do we proceed if no "73" message is received from
ones QSO partner. Listening on the bands it seems that sending an RR73
message has some special significance in that it is always assumed to be
received by ones QSO partner. This may be reasonable in propagation such
that any subsequent messages can be taken by ones QSO partner to mean that
the QSO is indeed complete even if the RR73 message was never decoded.

For example if you have called a station calling CQ, received a report, sent
a R+report and then get no decode from them in the next period; then the
next decode from the other station is a CQ call or them giving a report to a
different station or even calling another station on a different frequency,
then are we safe to assume that our QSO was complete and there is no
requirement to repeat the R+report message (the normal action if an RRR
message is not decoded) or even send a 73 message ourselves? BTW this does
beg the question of how a station running a frequency completes their last
QSO on a band, do we take silence to be an indication that a missed RR73
decode was in fact sent.

The above is fairly easy to implement in that, if an RR73 message is
received from ones QSO partner ones next message will be set to Tx5/73 (note
not RR73) and if prompt to log is checked the log QSO window will pop up.
Also if "Settings->General->Behavior->Disable Tx after 73" is checked, auto
transmit will be disabled. In other words, receiving an
RR73 message will be treated exactly the same as receiving a 73 message
(note this would not be optional).

Note the implication of the above is that no reply would be sent to an
RR73 message if one is received. I suppose this is the intent of the
original calling station and they might expect a tail-end caller to utilize
the period after they send RR73 without you QRMing such a caller by sending
a 73 message. This raises an issue of what to do when an expected RRR or
RR73 message is not received or decoded since it is impossible to know if
the original caller received ones R+report message, or whether they sent RRR
and are expecting a 73 message, or whether they repeated their report and
are expecting an R+report message, or they actually sent RR73 and expect
that the QSO is over. How can the software and indeed the operator deal with
this scenario? It would seem that resending the R+report message is the only
deterministic option which makes a 

Re: [wsjt-devel] Ver 1.8 RC1 audio in slider problem

[Dan Malcolm]

Mike, Bill,

FWIW I’d like to keep the slider.  I like the idea of encouraging users to read 
the manual.

 

From: Black Michael via wsjt-devel [mailto:wsjt-devel@lists.sourceforge.net] 
Sent: Tuesday, July 18, 2017 10:37 PM
To: WSJT software development 
Cc: Black Michael 
Subject: Re: [wsjt-devel] Ver 1.8 RC1 audio in slider problem

 

There were those that still wanted the waterfall adjustment for the fast graph 
handy so leaving it as an option would be the only solution.

 

I submitted some tooltip changes a while ago to make it pretty much 
in-your-face on the meter tooltip.

Then we need to spice up the documentation so be more in-your-face too.  
"Transceiver setup" as an index title is not intuitive but hopefully most know 
how to use search for keywords.  I tried to see if you could put a hyperlink in 
a tool tip but appears not.  Though about doing a ctrl-click on the meter or 
such to bring up the relevant section in the manual then put the ctrl-click 
info in the tooltip.

 

de Mike W9MDB

 

  _  

From: Bill Somerville  >
To: wsjt-devel@lists.sourceforge.net   
Sent: Tuesday, July 18, 2017 5:54 PM
Subject: Re: [wsjt-devel] Ver 1.8 RC1 audio in slider problem

 

On 18/07/2017 23:32, Black Michael via wsjt-devel wrote:

I'd say the vast majority have no use for the slider anymore.

So let's hide it by default and have an enable checkbox in the config.

 

I'll do that patch if you think that's acceptable...we'll still end up with 
"what happened to..." but se la vie... 

Hi Mike,

if you are going to do a patch then remove the slider altogether, that is 
probably the best option. It is of limited value and will always be 
misunderstood by many who don't understand the underlying realities of digital 
samples. Unfortunately the result may well be that those who miss the slider 
will revert to using the operating system sliders which are effectively the 
same thing and equally pointless (even harmful at extreme settings) as the 
WSJT-X slider.

 

73
Bill
G4WJS.

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot

___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net  
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

 

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] TQSL's config.xml

[Dan Malcolm]

Thanks Dave, I was already aware of that and have done it.  The question was 
more for information that real intent.

 

Dan – K4SHQ

 

From: Dave AA6YQ [mailto:aa...@ambersoft.com] 
Sent: Tuesday, July 18, 2017 12:21 PM
To: 'WSJT software development' <wsjt-devel@lists.sourceforge.net>
Subject: Re: [wsjt-devel] TQSL's config.xml

 

You can configure TQSL to automatically “map” FT8 QSOs to DATA now, which will 
enable LoTW to accept them. See

 

https://lotw.arrl.org/lotw-help/pref-adi/

 

 73,

 

   Dave, AA6YQ

 

 

 

From: Greg Beam [mailto:ki7m...@gmail.com] 
Sent: Tuesday, July 18, 2017 1:00 PM
To: 'WSJT software development'
Subject: Re: [wsjt-devel] TQSL's config.xml

 

You could ask Rick M., Dave, or one of the other Trusted QSL developers, but, I 
would think that adjustments to the client-side will have little to no 
affect—other than mapping the mode to data—until the server-side model has been 
updated to accommodate the new mode. 

 

Even if the ADIF spec is released today, the backend work would still need to 
be done before correct mapping of FT8 QSO’s could be realized. I don’t know 
what the LoTW eng/test/production release process is, but I would suspect work 
has already begun adding changes to the server model based on the proposed ADIF 
changes. 

 

I don’t really understand the urgency here. All one must do is hold back their 
FT8 QSO’s until the LoTW server is ready to accept them (as FT8 QSO’s that is). 
This situation “is not new”, it happens with every new mode / sub-mode 
introduction.

 

73’s

Greg, KI7MT

 

From: Black Michael via wsjt-devel [mailto:wsjt-devel@lists.sourceforge.net] 
Sent: Tuesday, July 18, 2017 10:15 AM
To: WSJT software development <wsjt-devel@lists.sourceforge.net 
<mailto:wsjt-devel@lists.sourceforge.net> >
Cc: Black Michael <mdblac...@yahoo.com <mailto:mdblac...@yahoo.com> >
Subject: Re: [wsjt-devel] TQSL's config.xml

 

3.0.6 has not had finally approval yet.

eQSL is just implementing it early.

I doubt ARRL will ever touch a draft ADIF spec.

 

de Mike W9MDB

 

 

  _  

From: Dan Malcolm <dan.malcol...@gmail.com <mailto:dan.malcol...@gmail.com> >
To: wsjtx-devel <wsjt-devel@lists.sourceforge.net 
<mailto:wsjt-devel@lists.sourceforge.net> > 
Sent: Tuesday, July 18, 2017 11:05 AM
Subject: [wsjt-devel] TQSL's config.xml

 

A question for smarter people than me.

 

TQSL’s config.xml contains all the modes acceptable to TQSL.  Instead of 
mapping FT8->DATA in TQSL, could I accomplish something similar but more 
accurate by inserting a new XML coded line in config.xml?

Insert a line like: “FT8”

 

This might even be moot, since the new ADIF spec is out and includes FT8.  

* LoTW’s website shows config.xml’s latest iteration is v11.0.  No 
mention of which ADIF spec.

* ADIF.ORG’s website still shows v3.0.5 as the latest. 

* eQSL says it’s using ADIF spec 3.0.6.

 

It’s entirely possible that ARRL will update config.xml soon on its own.

 

Dan – K4SHQ

 

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! 
http://sdm.link/slashdot___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net <mailto:wsjt-devel@lists.sourceforge.net> 
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] TQSL's config.xml

[Dan Malcolm]

Greg,

My question was more for information than for a real intent.  I have already 
done the FT8 mapping, and it is working quit well

Dan-K4SHQ

 

From: Greg Beam [mailto:ki7m...@gmail.com] 
Sent: Tuesday, July 18, 2017 12:00 PM
To: 'WSJT software development' <wsjt-devel@lists.sourceforge.net>
Subject: Re: [wsjt-devel] TQSL's config.xml

 

You could ask Rick M., Dave, or one of the other Trusted QSL developers, but, I 
would think that adjustments to the client-side will have little to no 
affect—other than mapping the mode to data—until the server-side model has been 
updated to accommodate the new mode. 

 

Even if the ADIF spec is released today, the backend work would still need to 
be done before correct mapping of FT8 QSO’s could be realized. I don’t know 
what the LoTW eng/test/production release process is, but I would suspect work 
has already begun adding changes to the server model based on the proposed ADIF 
changes. 

 

I don’t really understand the urgency here. All one must do is hold back their 
FT8 QSO’s until the LoTW server is ready to accept them (as FT8 QSO’s that is). 
This situation “is not new”, it happens with every new mode / sub-mode 
introduction.

 

73’s

Greg, KI7MT

 

From: Black Michael via wsjt-devel [mailto:wsjt-devel@lists.sourceforge.net] 
Sent: Tuesday, July 18, 2017 10:15 AM
To: WSJT software development <wsjt-devel@lists.sourceforge.net 
<mailto:wsjt-devel@lists.sourceforge.net> >
Cc: Black Michael <mdblac...@yahoo.com <mailto:mdblac...@yahoo.com> >
Subject: Re: [wsjt-devel] TQSL's config.xml

 

3.0.6 has not had finally approval yet.

eQSL is just implementing it early.

I doubt ARRL will ever touch a draft ADIF spec.

 

de Mike W9MDB

 

 

  _  

From: Dan Malcolm <dan.malcol...@gmail.com <mailto:dan.malcol...@gmail.com> >
To: wsjtx-devel <wsjt-devel@lists.sourceforge.net 
<mailto:wsjt-devel@lists.sourceforge.net> > 
Sent: Tuesday, July 18, 2017 11:05 AM
Subject: [wsjt-devel] TQSL's config.xml

 

A question for smarter people than me.

 

TQSL’s config.xml contains all the modes acceptable to TQSL.  Instead of 
mapping FT8->DATA in TQSL, could I accomplish something similar but more 
accurate by inserting a new XML coded line in config.xml?

Insert a line like: “FT8”

 

This might even be moot, since the new ADIF spec is out and includes FT8.  

* LoTW’s website shows config.xml’s latest iteration is v11.0.  No 
mention of which ADIF spec.

* ADIF.ORG’s website still shows v3.0.5 as the latest. 

* eQSL says it’s using ADIF spec 3.0.6.

 

It’s entirely possible that ARRL will update config.xml soon on its own.

 

Dan – K4SHQ

 

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! 
http://sdm.link/slashdot___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net <mailto:wsjt-devel@lists.sourceforge.net> 
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] TQSL's config.xml

[Dan Malcolm]

Mike, 

I agree with that assessment.  I did not realize that ADIF 3.0.6 was still 
draft, but since it is, that explains a lot.  While changing my end is easy, 
that doesn’t make it the right thing to do.  I will stay with what I have until 
ARRL makes the change.

 

From: Black Michael via wsjt-devel [mailto:wsjt-devel@lists.sourceforge.net] 
Sent: Tuesday, July 18, 2017 11:15 AM
To: WSJT software development <wsjt-devel@lists.sourceforge.net>
Cc: Black Michael <mdblac...@yahoo.com>
Subject: Re: [wsjt-devel] TQSL's config.xml

 

3.0.6 has not had finally approval yet.

eQSL is just implementing it early.

I doubt ARRL will ever touch a draft ADIF spec.

 

de Mike W9MDB

 

 

  _____  

From: Dan Malcolm <dan.malcol...@gmail.com <mailto:dan.malcol...@gmail.com> >
To: wsjtx-devel <wsjt-devel@lists.sourceforge.net 
<mailto:wsjt-devel@lists.sourceforge.net> > 
Sent: Tuesday, July 18, 2017 11:05 AM
Subject: [wsjt-devel] TQSL's config.xml

 

A question for smarter people than me.

 

TQSL’s config.xml contains all the modes acceptable to TQSL.  Instead of 
mapping FT8->DATA in TQSL, could I accomplish something similar but more 
accurate by inserting a new XML coded line in config.xml?

Insert a line like: “FT8”

 

This might even be moot, since the new ADIF spec is out and includes FT8.  

* LoTW’s website shows config.xml’s latest iteration is v11.0.  No 
mention of which ADIF spec.

* ADIF.ORG’s website still shows v3.0.5 as the latest. 

* eQSL says it’s using ADIF spec 3.0.6.

 

It’s entirely possible that ARRL will update config.xml soon on its own.

 

Dan – K4SHQ

 

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! 
http://sdm.link/slashdot___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net <mailto:wsjt-devel@lists.sourceforge.net> 
https://lists.sourceforge.net/lists/listinfo/wsjt-devel



--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] TQSL's config.xml

[Dan Malcolm]

Bill,

I had that same thought, hence my query.  While changing my end is easy,
that doesn't make it the right thing to do.  I will stay with what I have
until ARRL makes the change.

Thanks

 

Dan - K4SHQ

 

From: Bill Somerville [mailto:g4...@classdesign.com] 
Sent: Tuesday, July 18, 2017 11:08 AM
To: wsjt-devel@lists.sourceforge.net
Subject: Re: [wsjt-devel] TQSL's config.xml

 

On 18/07/2017 17:02, Dan Malcolm wrote:

TQSL's config.xml contains all the modes acceptable to TQSL.  Instead of
mapping FT8->DATA in TQSL, could I accomplish something similar but more
accurate by inserting a new XML coded line in config.xml?

Insert a line like: "FT8"

Hi Dan,

I doubt that will work as it probably has to match capability on the LotW
server which will not be prepared to accept ADIF records from you specifying
the mode as FT8. I would take the tQSL configuration file as private to the
LotW developers and leave it alone.

73
Bill
G4WJS.

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

[wsjt-devel] TQSL's config.xml

[Dan Malcolm]

A question for smarter people than me.

 

TQSL's config.xml contains all the modes acceptable to TQSL.  Instead of
mapping FT8->DATA in TQSL, could I accomplish something similar but more
accurate by inserting a new XML coded line in config.xml?

Insert a line like: "FT8"

 

This might even be moot, since the new ADIF spec is out and includes FT8.  

* LoTW's website shows config.xml's latest iteration is v11.0.  No
mention of which ADIF spec.

* ADIF.ORG's website still shows v3.0.5 as the latest. 

* eQSL says it's using ADIF spec 3.0.6.

 

It's entirely possible that ARRL will update config.xml soon on its own.

 

Dan - K4SHQ

 

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] FT8 and "Call 1st"

[Dan Malcolm]

Thanks Joe.  Since you're looking for opinions, hers's mine:
1. I like FT8.  I like the fast exchange.  I also like the automation so
far.  I agree that I would not want a "QSO machine".  If that's what I
wanted, I'd just turn off my mind and sit in front of the TV all day.
However I like the degree of automation you have at this point.  That gives
the operator a leg up in this fast mode, but it also allows him choice in
how he wants to operate.  Completely manual is still a choice.  Those of us
who are "aged" to perfection, do not have the reflexes that the "non-aged"
community enjoys, so the leg up is appreciated.  In short, I think the
current level of automation, but no more, is the way to go.
2. I like "Call 1st" but would also like "Weak".  That would be good for
encouraging low power and for capturing DX on a less than perfect
propagation day. 
3. The 60Hz shift and perhaps a choice of +/- would be nice for a trial. I
know I often stay out of the JT65 pileup because it's frustrating try to
have a QSO adjacent to a stronger signal than my QSO partner.  I am often
amazed the QSO's happen at all.  That's when I go to JT9.  I think for FT8
it would have to be tried, before viability can be assessed.  That 60Hz
shift could inadvertently put you right on top of someone else.

Thanks again Joe.

Dan - K4SHQ



-Original Message-
From: Joe Taylor [mailto:j...@princeton.edu] 
Sent: Tuesday, July 11, 2017 10:42 AM
To: WSJT software development 
Subject: [wsjt-devel] FT8 and "Call 1st"

Hi all,

WSJT-X v1.8.0-rc1 includes an optional feature that is a significant
departure from all previous WSJT-related software.

When you call CQ in FT8 mode with both "Auto Seq" and "Call 1st" 
checked, the program automatically selects the first decoded response to
your CQ and starts a QSO with the selected station.  The effect is the same
as if you had double-clicked on the caller's message.  Subsequent
transmissions will then continue automatically through the standard QSO
sequence.

When the contact is complete the CQ message (Tx6 on Tab 1) is selected but
"Tx Enable" is turned OFF.  This choice is intentional.  We want WSJT-X to
be a tool for assisting contacts between human operators, not an "Automatic
QSO Machine".

For a mode with 15-second T/R sequences and very little time for selecting
reply messages, there are obvious merits of the approach we have tentatively
adopted.  However, there are also some obvious consequences that might not
be considered desirable.  Do we want a computer algorithm to take part in
choosing our QSO partners?

It seems like a good idea to have some public discussion on whether "Call
1st" already goes too far in the direction of QSO automation.

Some of you noticed that a "Weak" box appeared briefly beside "Call 1st" 
(but was not yet implemented).  The idea was that when two or more replies
were received to one's CQ, this option would select the one with lower S/N
-- potentially encouraging people to keep their power turned down, as
appropriate for conditions.

We are interested in feedback from users on the question of partial QSO
automation.  Should "Call 1st" be changed or removed?

One more point: FT8 signals occupy the frequency/time plane more "densely"
than JT65.  For this reason, even when we have implemented signal
subtraction and multi-pass decoding, overlapping signals will be less likely
to decode than is the case with JT65.  You may soon discover that it often
pays to respond to a CQ "off frequency" by 60 Hz or more. 
We might consider offering a tool to make this easier to do.

-- Joe, K1JT


--
Check out the vibrant tech community on one of the world's most engaging
tech sites, Slashdot.org! http://sdm.link/slashdot
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel


--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] FT8: IMPORTANT NOTICE

[Dan Malcolm]

Thanks Joe.  I know you and your fellow developers have been hard at it, and
we appreciate the effort, and the great results.

One issue I am seeing that during a QSO, my QSO partners replies show up in
Band Activity fine, but get doubled in Rx Frequency.  I have screen shots,
and will provide them if you need them.  Thanks again.

Dan - K4SHQ

-Original Message-
From: Joe Taylor [mailto:j...@princeton.edu] 
Sent: Friday, July 07, 2017 6:54 PM
To: WSJT software development 
Subject: Re: [wsjt-devel] FT8: IMPORTANT NOTICE

To:  Users of FT8
From:WSJT Development Team
Subject: IMPORTANT NOTICE ABOUT FT8

If you are building WSJT-X for yourself from source code, you may now
upgrade to r7812 and recompile. You will then have access to the latest
version of FT8 plus some new features for setting default operating
frequencies by mode and IARU region.  The program built in this way will be
called WSJT-X v1.7.1 r7812.

Note that essentially the same program will soon be packaged for wider
distribution as as "WSJT-X Version 1.8.0-rc1" (release candidate 1), see
below).

Remember that FT8 in code revisions 7812 are higher is NOT COMPATIBLE with
that in 7782 and earlier.  To use FT8 you must upgrade to r7812.
If you see FT8 signals that do not decode, they may be using the obsolete
protocol.

About the Default Working Frequencies
=

FT8 will likely be popular with MF and HF users as well as the VHF multi-hop
sporadic-E DXers it was designed for.  After consultation with the user
community, we have reworked the suggested operating frequency defaults to
include FT8.  This was not easy on every relevant band; where possible, we
have suggested a 2 kHz range for exclusive FT8 use. 
(Exclusivity is important, as the T/R period is 15 s which will not mix well
with mode that use one-minute sequences.)

In general the FT8 frequencies are set 2kHz below the current JT65
allocation.  This should allow operation using a normal SSB filter width
without too much interference from strong JT65 signals up the band.  On some
bands that has not been possible since JT65 sits at the lowest usable narrow
band data mode frequency, when considering all international band plans.

For the 660 m and 2200 m  bands we have not assigned separate frequencies
for JT65/JT9/FT8, and just expect users to coordinate themselves.  The
numbers of active operators will probably be low enough that this will not
cause issues.

For 160 m we assume that the JT65 and JT9 sub-bands can be squeezed to
1 kHz each, and FT8 can sit above using up to another 1 kHz.

Previous 80 m use of JT modes has done a disservice to JA operators, who
have no privileges on the current WSPR/JT65/JT9 allocations.  To correct
this we have moved the allocations to a part of the band where JAs can
operate.  Obviously this change will impact other non-WSJT-X users, so for
now we suggest that if you intend to operate on 80 m JT65/JT9/WSPR then you
manually change the working frequencies in WSJT-X
("Settings->Frequencies") back to the old allocations until a general
availability release of WSJT-X v1.8.0 is published. This will allow time for
other software teams to coordinate with us.

The old allocations are:

JT65 3.567 MHz
JT9  3.578 MHz
WSPR 3.5926 MHz

For 6 m we understand that the IARU Region 1 band plan is not to the liking
of DX chasers around the world and largely ignored by Region 1 users.
However we cannot reasonably continue to set working frequency suggestions
that drive traffic to parts of the band that are not supposed to be used for
narrow band data modes.  The v1.8.0 release will allow Region-specific
working frequencies as well as globally coordinated ones.  Consequently we
have set the Region 1 working frequencies roughly in line with the band
plan.  If you do not like the allocations then do not complain to us, but
complain to your Region 1 band coordinator along with reasons why you think
it should change.  The proposed Region 1 working frequencies are usable
globally wherever 6m data mode operation is permitted so we have set them as
global rather than Region 1 specific.  Region 2 and 3 operators will have
both local and global frequencies offered.

Other changes are in line with current usage.


Finally, if you are waiting for pre-built installation packages:

We plan to post a release candidate for WSJT-X v1.8.0-rc1 configured for
Windows, Linux, and OS X very soon -- probably early next week.  Thanks for
your patience!

 -- 73, Joe, K1JT (for the WSJT Development Team)


--
Check out the vibrant tech community on one of the world's most engaging
tech sites, Slashdot.org! http://sdm.link/slashdot
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Preparation for WSJT-X v1.8.0-rc1

[Dan Malcolm]

Mike,

I discovered this change and made changes to my soundcard levels.  But I have 
to confess that the slider looks like it controls levels also.  First it is 
adjacent to the level meter on the left bottom, and second it is not labeled.  
Personally if it controls something waterfall it should be on the waterfall.  
In the end though it needs something to indicate that its effect is on the 
waterfall, and there is a tooltip to indicate that.  Perhaps a note in the 
change notes is warrented.

 

From: Black Michael via wsjt-devel [mailto:wsjt-devel@lists.sourceforge.net] 
Sent: Thursday, July 06, 2017 11:08 AM
To: WSJT software development 
Cc: Black Michael 
Subject: Re: [wsjt-devel] Preparation for WSJT-X v1.8.0-rc1

 

What change?  The meter shows the recording level now instead of the waterfall 
level.  The slider controls the waterfall and not the meter anymore (it never 
should have).

We talked about removing the slider and putting it on the waterfall but some 
wanted it to remain on the main screen.

 

de Mike W9MDB

 

 

  _  

From: "char...@sucklingfamily.free-online.co.uk 
 " 

To: WSJT software development  > 
Sent: Thursday, July 6, 2017 11:00 AM
Subject: Re: [wsjt-devel] Preparation for WSJT-X v1.8.0-rc1

 

Hi Joe

Perhaps worth mentioning the change to the audio level setting to avoid
inadvertent clipping - folks now have to adjust soundcard level controls,
radio level  or external 'attenuator'.

Charlie

  > Hi all,
>
> I'm compiling a list of important new features and other changes that
> will be in WSJT-X v1.8.
>
> 1.  New mode called FT8: QSOs 4 times faster than JT9, JT65
> 2.  New mode for Frequency Calibration
> 3.  Improved performance of decoders for JT65, QRA64, and MSK144
> 4.  New utility programs: msk144code, fmeasure, fmtave, fcal, ft8sim,
>  ft8d.
> 5.  Options to minimize sizes of Main window and Wide Graph window.
> 6.  New default table of recommended operating frequencies
> 7.  Improved CAT control for many rigs, including operation through
>  Commander and OmniRig
> 8.  Many minor bug fixes and tweaks to the user interface
>
> Have I omitted anything that should be in this list?
>
> -- Joe, K1JT
>
> --
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net  
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel


>



--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net  
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

 

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Frequency doesn't shift when changing configurations

[Dan Malcolm]

Neil,
It works for me with Configurations name "FT8 Config" & "JT65-JT9 Config".
Not sure why a renaming would make it work.  All I know is it works for me @
r7782.

Dan - K4SHQ

-Original Message-
From: Neil Zampella [mailto:ne...@techie.com] 
Sent: Tuesday, July 04, 2017 4:08 PM
To: WSJT software development 
Subject: Re: [wsjt-devel] Frequency doesn't shift when changing
configurations

Urp .. sent this reply directly to Bill .. so I'm including that here, along
with this update below:


On 7/4/2017 4:16 PM, Neil Zampella wrote:
> On 7/4/2017 2:07 PM, Bill Somerville wrote:
>> On 04/07/2017 18:52, Neil Zampella wrote:
>>>
>>> OK ..  Scenario I often use is this;  I'm monitoring JT65/JT9 on 
>>> 20M, I want to switch over to FT8 to see what is happening so I 
>>> change config.   I'm thinking that the program on restart should 
>>> check the band and/or mode to verify the freq setting.
>>>
>>> OK .. just tested this:   in my FT8 configuration, I check the 
>>> setting for 'last used freq',  then switched to my JT65/JT9 config 
>>> and did the same.
>>>
>>> I then switched the config back to my FT8 settings, then selected 
>>> 40M.  OK -  freq is at 7.079.   I switch to JT65/JT9 config, the 
>>> freq doesn't change it stays on 7.079, doesn't change until I 
>>> re-select the band, or re-select the mode. So I'm at the jt65/jt9 
>>> freq of 7.076, I switch back to FT8, the freq changes to 7.079 as it 
>>> should.   So the freq isn't changing when I go back to the jt65/jt9 
>>> config.
>>>
>> Hi Neil,
>>
>> I know you want to stick with Commander and I do have sympathy with 
>> you on that, I use DX Lab Suite myself and I have foregone Commander 
>> when using the fast modes and FT8.
>>
>> Can you try, just for a test, changing your configurations to use 
>> direct rig control and see if the problem still happens. You will 
>> have to close Commander before starting WSJT-X.
>>
>> 73
>> Bill
>> G4WJS.
>>
>>
>>
> Hi Bill,
>
> OK I switched from Commander to the K3/KX3 settings in WSJT-X on both 
> configurations, closing the program in the FT8 configuration.I 
> reopen the program, it starts in 20M at the FT8 freq.   I move to 40M, 
> it changes properly, I then switch to the default (JT65/JT9) config, 
> and the frequency does not change from the FT8 frequency.I have to 
> select 40M in order to get the 7.076 freq for jt65/jt9.
>
> Does this help?
>
> Neil, KN3ILZ

Did a build to bring my program up to r7782, works the same. Switch 
config to the FT8 one, changes the freq.   Switch back to the default 
(JT65/JT9) configuration, no change in frequency.As I mentioned 
before, it appears that on the switch from the default to the saved 
config for FT8, the system verifies the mode and makes the change.  
Going back to the default it doesn't.

I can live with it, but should it do that ??

Neil, KN3ILZ


--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel


--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Frequency doesn't shift when changing configurations

[Dan Malcolm]

Bill, Neil,

That works for me now with r7782.

 

Dan – K4SHQ

 

From: Bill Somerville [mailto:g4...@classdesign.com] 
Sent: Tuesday, July 04, 2017 12:17 PM
To: wsjt-devel@lists.sourceforge.net
Subject: Re: [wsjt-devel] Frequency doesn't shift when changing configurations

 

On 04/07/2017 15:21, Neil Zampella wrote:

Hi Neil, 

I forgot to mention that the two options in WSJT-X "Settings->General" "Monitor 
off at startup" and "Monitor returns to last used frequency" control what 
happens when you start WSJT-X. Switching configurations is equivalent to 
starting WSJT-X again. 

73 
Bill 
G4WJS 


Hmmm ... not a factor in my case Bill, as I have neither one of those checked 
in any of my configurations. 

Hi Neil,

you need "Monitor returns to last used frequency" checked if you are expecting 
WSJT-X to change frequency on startup or configuration switch (in the 
destination configuration in the case of configuration switches).

73
Bill
G4WJS.

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Frequency doesn't shift when changing configurations

[Dan Malcolm]

Bill,
I see the same problem Neil sees.  I have tried both with and without
"Monitor returns to last used frequency" checked and see no difference.  I
still have to manually change the frequency from the dropdown list.

Dan Malcolm - K4SHQ

-Original Message-
From: Bill Somerville [mailto:g4...@classdesign.com] 
Sent: Tuesday, July 04, 2017 4:08 AM
To: wsjt-devel@lists.sourceforge.net
Subject: Re: [wsjt-devel] Frequency doesn't shift when changing
configurations

On 04/07/2017 03:08, Neil Zampella wrote:
> Switching configurations from what I have setup for FT8 to the 
> 'normal' JT65/JT9 setup, the frequency does not move from the FT8 to 
> the JT modes frequency.  This also occurs going the other way. The 
> only way to reset the frequency is to either re-select the mode from 
> the mode menu where its already set in the saved configuration, or 
> re-select the band from the drop down.
>
> I already have two configurations setup for use.  The 'normal' 
> configuration for JT65/JT9 slow modes, and the FT8 configuration. 

Hi Neil,

I forgot to mention that the two options in WSJT-X "Settings->General" 
"Monitor off at startup" and "Monitor returns to last used frequency" 
control what happens when you start WSJT-X. Switching configurations is
equivalent to starting WSJT-X again.

73
Bill
G4WJS.



--
Check out the vibrant tech community on one of the world's most engaging
tech sites, Slashdot.org! http://sdm.link/slashdot
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel


--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

[wsjt-devel] FT8 online logging

[Dan Malcolm]

I suspect I am not the only one with logging problems to eQSL and LoTW.
Thanks to a hint from another ham on this forum, I can now trick TQSL into
uploading FT8 QSO's.  I just heard from an eQSL support volunteer, who in
essence says that they are aware of the new mode, but are constrained by
ADIF.ORG.  I suspect LoTW has the same constraint but there is a workaround.
QRZ seems to be handling all this in stride.

 

What is the common practice now for eQSL?  I have on a few occasions,
changed the mode to SSB, but that brings issues too.  One is that signal
reports won't match the mode.  All this will get sorted out in time but has
anyone come up with a better solution than mine?  At the moment I am just
holding off on sending FT8 QSO's to eQSL.

 

Dan Malcolm

K4SHQ

 

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] r7776 Split problem

[Dan Malcolm]

I just tested my last reply to you, and it appears I understand "split mode"
better.  Thanks.

 

From: Bill Somerville [mailto:g4...@classdesign.com] 
Sent: Sunday, July 02, 2017 11:33 AM
To: wsjt-devel@lists.sourceforge.net
Subject: Re: [wsjt-devel] r7776 Split problem

 

On 02/07/2017 17:29, Dan Malcolm wrote:

I think I understand, but perhaps I didn't communicate well.  Prior to r7776
the B BFO did the Tx (and A BFO does the Rx) and shifted frequency to
14.078.500 as I expected, in compliance with the recommend split mode
setting.  Now, Tx still occurs on the B VFO, but does not shift to
14.078.500 as it did previously.  The B VFO remains at 14.079.000 during Tx.
This seems to be a change in Tx split mode behavior.  I understand the DF
frequency will change depending on the Tx DF, but I thought the TX shift
using split mode was supposed to keep audio frequencies in 1200-2000Hz range
and to do that required a 500Hz downshift during Tx.

Hi Dan,

what is your Tx DF when you observe the Tx dial frequency (VFO B) at 14.079
?

73
Bill
G4WJS.

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] r7776 Split problem

[Dan Malcolm]

Bill,

At the moment it's 1636.  Perhaps the light is dawning.  Would split mode
only shift the Tx frequency in order to keep the audio frequency in bounds,
and not to shift if Tx frequency is already in bounds?

 

From: Bill Somerville [mailto:g4...@classdesign.com] 
Sent: Sunday, July 02, 2017 11:33 AM
To: wsjt-devel@lists.sourceforge.net
Subject: Re: [wsjt-devel] r7776 Split problem

 

On 02/07/2017 17:29, Dan Malcolm wrote:

I think I understand, but perhaps I didn't communicate well.  Prior to r7776
the B BFO did the Tx (and A BFO does the Rx) and shifted frequency to
14.078.500 as I expected, in compliance with the recommend split mode
setting.  Now, Tx still occurs on the B VFO, but does not shift to
14.078.500 as it did previously.  The B VFO remains at 14.079.000 during Tx.
This seems to be a change in Tx split mode behavior.  I understand the DF
frequency will change depending on the Tx DF, but I thought the TX shift
using split mode was supposed to keep audio frequencies in 1200-2000Hz range
and to do that required a 500Hz downshift during Tx.

Hi Dan,

what is your Tx DF when you observe the Tx dial frequency (VFO B) at 14.079
?

73
Bill
G4WJS.

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] r7776 Split problem

[Dan Malcolm]

Bill,

I think I understand, but perhaps I didn't communicate well.  Prior to r7776
the B BFO did the Tx (and A BFO does the Rx) and shifted frequency to
14.078.500 as I expected, in compliance with the recommend split mode
setting.  Now, Tx still occurs on the B VFO, but does not shift to
14.078.500 as it did previously.  The B VFO remains at 14.079.000 during Tx.
This seems to be a change in Tx split mode behavior.  I understand the DF
frequency will change depending on the Tx DF, but I thought the TX shift
using split mode was supposed to keep audio frequencies in 1200-2000Hz range
and to do that required a 500Hz downshift during Tx.

 

From: Bill Somerville [mailto:g4...@classdesign.com] 
Sent: Sunday, July 02, 2017 11:17 AM
To: wsjt-devel@lists.sourceforge.net
Subject: Re: [wsjt-devel] r7776 Split problem

 

On 02/07/2017 17:13, Dan Malcolm wrote:

I just compiled r7776 and found that there is a "split" problem.  In
Settings under the Radio tab I have enabled Rig for Split Operation.  I am
running Kenwood TS-2000 for the Rig model.  That setting has been working
well until I compiled the new WSJT-X 1.7.1-devel r7776.  Prior to this Tx
occurred on the B CFO at 14.78.500Mhz.  Now it is still using the B VFO but
no offset occurs.  I may have confused things a bit because I also
recompiled HamLIb3.

 

Dan Malcolm

K4SHQ

Hi Dan,

the Tx VFO dial frequency is not fixed, it depends on the Tx DF you select.
If you control-click around the waterfall you should see that each 500Hz
section uses a different Tx VFO dial frequency. That is assuming you are
using one of the multi-decode modes JT9, JT65 or FT8.

73
Bill
G4WJS.

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] K4SHQ FT8 Notes

[Dan Malcolm]

Thanks David.  Got that done and in the process found there is an updated
TQSL 2.3.1.

 

From: David Tiller [mailto:dtil...@captechconsulting.com] 
Sent: Friday, June 30, 2017 8:05 PM
To: WSJT software development <wsjt-devel@lists.sourceforge.net>
Subject: Re: [wsjt-devel] K4SHQ FT8 Notes

 

In TSQL, under preferences there's a tab called "ADIF Modes". In there you
can add an FT8  --> DATA mapping. 

 

Here's mine:

 



--

David Tiller

Sr. Architect/Lead Consultant | CapTech

(804) 304-0638 | dtil...@captechconsulting.com
<mailto:dtil...@captechconsulting.com> 

 

 

 

On Jun 30, 2017, at 8:58 PM, Dan Malcolm <dan.malcol...@gmail.com
<mailto:dan.malcol...@gmail.com> > wrote:





Thanks David. Log4OM does indeed use TQSL under the hood.  Just where in
TQSL do enter FT8-->DATA?

BTW I have found that QRZ will accept FT8.

 

From: David Tiller [ <mailto:dtil...@captechconsulting.com>
mailto:dtil...@captechconsulting.com] 
Sent: Friday, June 30, 2017 7:47 PM
To: WSJT software development < <mailto:wsjt-devel@lists.sourceforge.net>
wsjt-devel@lists.sourceforge.net>
Subject: Re: [wsjt-devel] K4SHQ FT8 Notes

 

Re: the second part of item #2: You still can't upload to eQSL or LoTW with
FT8.

 

If Log4OM is anything like the macOS software I use, it actually uses TSQL
under the covers to do the digital signing and upload. At least in my case,
if you add the FT8 --> DATA mapping in TSQL, the upload works.

 

Might be worth a try.

 

--

David Tiller

Sr. Architect/Lead Consultant | CapTech

(804) 304-0638 |  <mailto:dtil...@captechconsulting.com>
dtil...@captechconsulting.com

 

 

 

On Jun 30, 2017, at 8:37 PM, Dan Malcolm < <mailto:dan.malcol...@gmail.com>
dan.malcol...@gmail.com> wrote:






1.   Log4OM can be made to accept FT8 as a mode.  But while it accepts
it as a mode, RST reports are set '59'. 

2.   Reference #1 above. Making Log4OM accept FT8 is trivial but moot.
You still can't upload to eQSL or LoTW with FT8.

3.   Log4OM also does not auto upload to eQSL when the mode is FT8.

4.   In order to capture the RST values I include them in my JTAlert-X
"QSL Message" text window using Laurie's replaceable tokens.  Check the
JTAlert Help file under Logging in the "Comments and QSL Message Text
Substitutions" section.

 

All short comings and disconnects will probably be resolved in time as FT8
moves into its own.  Again congrats to the devel team.  This is exciting.

 

I am running an Apache ANAN 100D.  There has been discussion of what to call
the "split" mode.  I didn't understand WSJT's use of it until it was
explained on this forum just recently.  Now I do understand and approve.  My
rig likes it just fine but I understand other rigs do not.  I do think we
need another name for it so as not to confuse WSJT "split" with the other
"split".  I offered "Audio Purity Offset", but will be happy with whatever
the devel team decides.

 

Since FT8 is still beta, it is too soon to approach the on line logbooks
about allowing FT8.  But that time is approaching.

 

 

 


--
Check out the vibrant tech community on one of the world's most
engaging tech sites,  <http://slashdot.org/> Slashdot.org!
<http://sdm.link/slashdot___>
http://sdm.link/slashdot___
wsjt-devel mailing list
 <mailto:wsjt-devel@lists.sourceforge.net> wsjt-devel@lists.sourceforge.net
 <https://lists.sourceforge.net/lists/listinfo/wsjt-devel>
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

 


--
Check out the vibrant tech community on one of the world's most
engaging tech sites,  <http://slashdot.org/> Slashdot.org!
<http://sdm.link/slashdot___>
http://sdm.link/slashdot___
wsjt-devel mailing list
 <mailto:wsjt-devel@lists.sourceforge.net> wsjt-devel@lists.sourceforge.net
 <https://lists.sourceforge.net/lists/listinfo/wsjt-devel>
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

 

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] K4SHQ FT8 Notes

[Dan Malcolm]

Thanks David. Log4OM does indeed use TQSL under the hood.  Just where in
TQSL do enter FT8-->DATA?

BTW I have found that QRZ will accept FT8.

 

From: David Tiller [mailto:dtil...@captechconsulting.com] 
Sent: Friday, June 30, 2017 7:47 PM
To: WSJT software development <wsjt-devel@lists.sourceforge.net>
Subject: Re: [wsjt-devel] K4SHQ FT8 Notes

 

Re: the second part of item #2: You still can't upload to eQSL or LoTW with
FT8. 

 

If Log4OM is anything like the macOS software I use, it actually uses TSQL
under the covers to do the digital signing and upload. At least in my case,
if you add the FT8 --> DATA mapping in TSQL, the upload works.

 

Might be worth a try.

 

--

David Tiller

Sr. Architect/Lead Consultant | CapTech

(804) 304-0638 | dtil...@captechconsulting.com
<mailto:dtil...@captechconsulting.com> 

 

 

 

On Jun 30, 2017, at 8:37 PM, Dan Malcolm <dan.malcol...@gmail.com
<mailto:dan.malcol...@gmail.com> > wrote:





1.   Log4OM can be made to accept FT8 as a mode.  But while it accepts
it as a mode, RST reports are set '59'. 

2.   Reference #1 above. Making Log4OM accept FT8 is trivial but moot.
You still can't upload to eQSL or LoTW with FT8.

3.   Log4OM also does not auto upload to eQSL when the mode is FT8.

4.   In order to capture the RST values I include them in my JTAlert-X
"QSL Message" text window using Laurie's replaceable tokens.  Check the
JTAlert Help file under Logging in the "Comments and QSL Message Text
Substitutions" section.

 

All short comings and disconnects will probably be resolved in time as FT8
moves into its own.  Again congrats to the devel team.  This is exciting.

 

I am running an Apache ANAN 100D.  There has been discussion of what to call
the "split" mode.  I didn't understand WSJT's use of it until it was
explained on this forum just recently.  Now I do understand and approve.  My
rig likes it just fine but I understand other rigs do not.  I do think we
need another name for it so as not to confuse WSJT "split" with the other
"split".  I offered "Audio Purity Offset", but will be happy with whatever
the devel team decides.

 

Since FT8 is still beta, it is too soon to approach the on line logbooks
about allowing FT8.  But that time is approaching.

 

 

 


--
Check out the vibrant tech community on one of the world's most
engaging tech sites,  <http://slashdot.org/> Slashdot.org!
<http://sdm.link/slashdot___>
http://sdm.link/slashdot___
wsjt-devel mailing list
 <mailto:wsjt-devel@lists.sourceforge.net> wsjt-devel@lists.sourceforge.net
 <https://lists.sourceforge.net/lists/listinfo/wsjt-devel>
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

 

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

[wsjt-devel] K4SHQ FT8 Notes

[Dan Malcolm]

1.   Log4OM can be made to accept FT8 as a mode.  But while it accepts
it as a mode, RST reports are set '59'.  

2.   Reference #1 above. Making Log4OM accept FT8 is trivial but moot.
You still can't upload to eQSL or LoTW with FT8.

3.   Log4OM also does not auto upload to eQSL when the mode is FT8.

4.   In order to capture the RST values I include them in my JTAlert-X
"QSL Message" text window using Laurie's replaceable tokens.  Check the
JTAlert Help file under Logging in the "Comments and QSL Message Text
Substitutions" section.

 

All short comings and disconnects will probably be resolved in time as FT8
moves into its own.  Again congrats to the devel team.  This is exciting.

 

I am running an Apache ANAN 100D.  There has been discussion of what to call
the "split" mode.  I didn't understand WSJT's use of it until it was
explained on this forum just recently.  Now I do understand and approve.  My
rig likes it just fine but I understand other rigs do not.  I do think we
need another name for it so as not to confuse WSJT "split" with the other
"split".  I offered "Audio Purity Offset", but will be happy with whatever
the devel team decides.

 

Since FT8 is still beta, it is too soon to approach the on line logbooks
about allowing FT8.  But that time is approaching.

 

 

 

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] FT8 - build 7752 and rig control

[Dan Malcolm]

FYI.  I just tried the “split” mode in WSJT-X for an FT8 QSO.  My Apache 100D 
seems to like it just fine.

 

From: Black Michael via wsjt-devel [mailto:wsjt-devel@lists.sourceforge.net] 
Sent: Friday, June 30, 2017 12:04 PM
To: WSJT software development 
Cc: Black Michael 
Subject: Re: [wsjt-devel] FT8 - build 7752 and rig control

 

What if we just named that box "Audio Split Operation" and improve the tooltips?

 

Tooltip on groupbox: Special split ops for cleaner audio -- see help file

Tooltip on None: No split

Tooltip on Rig:  Use rig split capability

Tooltip on FakeIt:Split occurs on VFOA during transmit 

 

Might have to improve the help a bit to explain these things better.

 

de Mike W9MDB

 

  _  

From: George J Molnar  >
To: WSJT software development  > 
Sent: Friday, June 30, 2017 11:40 AM
Subject: Re: [wsjt-devel] FT8 - build 7752 and rig control

 

(Sorry Joe - posted this to you instead of the group - apologies for the double 
message)

 

Hi Joe,

 

I was just about to send an “amen” to Mike’s comments - he hit it on the head. 

 

The nut here seems to be with the use of the term “split.” It implies two 
different frequencies are being used for the contact. This threw me, and 
probably some others.

 

We also use the “split” terminology to describe MSK144’s use of "CQ nnn” to 
indicate a true split between calling and operating frequency. That makes 
plenty of sense, but isn’t what we’re doing for FT8, for example. 

 

As for “needing” a “solution.” it’s really neither a need, nor a solution. I 
don’t want to see my dial frequency move without explicit command by me. 
Personal preference, really. It’s not wrong either way, so technically doesn’t 
need a solution. Just a preference that I suspect others may share. Having CAT 
enabled for PTT and proper logging is very desirable, though, so I don’t want 
to disable it.

 

BTW, the manual is an excellent guide. I fear that most don’t read it line by 
line, or even at all. We can’t count on the very clear text (and it is) making 
it to all users before they get frustrated or vent their feelings on-line. The 
more we can make intuitive and transparent, the better for everyone.

 

/opinion

 

George J Molnar

Nevada, USA
KF2T  @GJMolnar

 

 

 

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot

___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net  
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

 

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] FT8 - build 7752 and rig control

[Dan Malcolm]

I'd like to weigh in on the "what to call it" discussion.  Not that I have 
anything really better, but since we already have a well understood "split 
mode", called this a split confuses one function with another.  Can we say 
something like "Audio Purity Offset"?

I have not used it before I'm willing to give it a try.  I let you know what my 
Apache 100D thinks about it.

-Original Message-
From: Joe Taylor [mailto:j...@princeton.edu] 
Sent: Friday, June 30, 2017 11:21 AM
To: WSJT software development ; George J 
Molnar 
Subject: Re: [wsjt-devel] FT8 - build 7752 and rig control

Hi George,

> Still feel like the way this is being implemented is counter-intuitive 
> for most operators. After your explanation, I get it. That said, I’ve 
> made 10,000 JT-mode QSOs and it never occurred to me when I saw this. 
> I think we might see a fair number of folks fall into the same 
> confusion that I felt. It’s made more difficult since it’s not 
> standardized across the platform.

The WSJT-X User Guide includes the following text in Section 4.2:

"Split Operation: Significant advantages result from using Split mode (separate 
VFOs for Rx and Tx) if your radio supports it. If it does not, WSJT-X can 
emulate such behavior. Either method will result in a cleaner transmitted 
signal, by keeping the Tx audio always in the range 1500 to
2000 Hz so that audio harmonics cannot pass through the Tx sideband filter. 
Select Rig to use the radio’s Split mode, or Fake It to have WSJT-X adjust the 
VFO frequency as needed, when T/R switching occurs. 
Choose None if you do not wish to use split operation."

I'm not sure what we could write that would be any more clear.

I have no idea what you mean by "it’s not standardized across the platform".

> Not sure what the solution is. For me, I will probably just build a 
> configuration that prevents split for FT8, since my Flex is pretty 
> flat across the passband and no audio card is involved.

Why do you need any "solution"?  Solution to what problem? For FT8, or for any 
other mode??

-- Joe, K1JT

--
Check out the vibrant tech community on one of the world's most engaging tech 
sites, Slashdot.org! http://sdm.link/slashdot 
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel


--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] FT8: Potential new mode for fast QSOs

[Dan Malcolm]

The Log4OM Forum is currently off line, or I would not bother you guys, and
feel free to tell me to suck it up.  Is there a way to get Log4OM to accept
the FT8 mode?

-Original Message-
From: Laurie, VK3AMA [mailto:_vk3a...@vkdxer.net] 
Sent: Thursday, June 29, 2017 6:28 PM
To: wsjt-devel@lists.sourceforge.net >> WSJT software development

Subject: Re: [wsjt-devel] FT8: Potential new mode for fast QSOs



On 30/06/2017 9:10 AM, Joe Taylor wrote:
> Is anyone using "T10"? When I've checked recently, usage seemed to be 
> close to zero.
>
> In any eveny, we had no idea that "~" was being used to flag a T10 
> decode.  (Or, for that metter, that you were using those flags in
> JTAlert.)
>
> Maybe you can tell it's FT8 because I (mistakenly) left two spaces 
> between "~" and the start of message, rather than one. :-)
>
> -- Joe, K1JT

Joe,

The 2 spaces hack is not really suitable, since JTAlert uses the mode field
passed in the UDP decode packet. I'd rather not code a fix based on a source
code error that will likely be corrected in the future.

A JTAlert fix is rather trivial, as I already know if the UDP packet is
coming from WSJT-X or JTDX, so its a simple application test to determine
the true mode.

I'll be posting a new JTAlert later today with the fix.

Regarding T10 usage, there is only a small number of users, primarily EU
based. I have not seen any significant uptake of the mode, there appears to
be only a small number of regular spotters of the mode.

de Laurie VK3AMA



--
Check out the vibrant tech community on one of the world's most engaging
tech sites, Slashdot.org! http://sdm.link/slashdot
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel


--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] FT8: Potential new mode for fast QSOs

[Dan Malcolm]

I am also having problems with logging.  FT8 is not recognized (yet).  I
listed it as 'SSB' and put "Mode=FT8" in the remarks, but that is just a
stop gap measure.  Log4OM initially accepted but then rejected FT8, and I
haven't found a way to make that acceptable to Log4OM.  I have to say though
that I am very pleased with the auto-sequencing.

-Original Message-
From: Laurie, VK3AMA [mailto:_vk3a...@vkdxer.net] 
Sent: Thursday, June 29, 2017 5:36 PM
To: WSJT software development <wsjt-devel@lists.sourceforge.net>
Subject: Re: [wsjt-devel] FT8: Potential new mode for fast QSOs



On 30/06/2017 7:41 AM, Dan Malcolm wrote:
> I also notice that there is a
> tilde between "Freq" and "Message" in the "Band Activity" window.  Is 
> that an FT8 encoding indicator or a place holder?

The "~" mode character will be a problem. It is the character chosen by JTDX
for the T10 mode and would explain an earlier message that indicated that a
FT8 spot on HamSpots appeared as T10 (likely came from JTAlert which spots
"~" decodes as T10).

de Laurie VK3AMA



--
Check out the vibrant tech community on one of the world's most engaging
tech sites, Slashdot.org! http://sdm.link/slashdot
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel


--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] FT8: Potential new mode for fast QSOs

[Dan Malcolm]

Thanks Bill. I had forgotten you could do that with the frequency list.  I
generally don't keep anything but defaults.  I also notice that there is a
tilde between "Freq" and "Message" in the "Band Activity" window.  Is that
an FT8 encoding indicator or a place holder?

-Original Message-
From: Bill Somerville [mailto:g4...@classdesign.com] 
Sent: Thursday, June 29, 2017 4:27 PM
To: wsjt-devel@lists.sourceforge.net
Subject: Re: [wsjt-devel] FT8: Potential new mode for fast QSOs

On 29/06/2017 22:19, Dan Malcolm wrote:
> I also noticed that the
> dropdown band list did not have an entry for 20m FT8.  I was a simple 
> matter to add it.  I assume some of this is because FT8 is new and 
> just in the experimental stage.  Presumably these things will be taken 
> care of in due course and I understand you developers have more 
> important matters to attend to.

HI Dan,

the suggested frequencies listed by Joe are in the defaults but you will
have to reset the frequency list to see them. Resetting the frequency list
will remove any you have added manually so you may wish to just add them
yourself for now.

When we do the next official release we will probably force a reset. 
More refined tools for frequency list management will probably be available
from the next release.

73
Bill
G4WJS.



--
Check out the vibrant tech community on one of the world's most engaging
tech sites, Slashdot.org! http://sdm.link/slashdot
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel


--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] FT8: Potential new mode for fast QSOs

[Dan Malcolm]

I was able to compile v1.7.1-devel with the new mode.  Once up and running I
did spot FA1ABL calling CQ @ 14.079+1300.  I wanted to just lurk awhile
first so I didn't answer him but hoped he would find someone to QSO with.
He didn't.  A while later he spotted me and reported it through HamSpots.
I wasn't sure if it would be reported or not but I was glad to see it was.
The odd thing was that it was reported as Mode T10.  I also noticed that the
dropdown band list did not have an entry for 20m FT8.  I was a simple matter
to add it.  I assume some of this is because FT8 is new and just in the
experimental stage.  Presumably these things will be taken care of in due
course and I understand you developers have more important matters to attend
to.  Thanks for your efforts. 

-73
Dan - K4SHQ

-Original Message-
From: Joe Taylor [mailto:j...@princeton.edu] 
Sent: Thursday, June 29, 2017 10:33 AM
To: WSJT software development 
Subject: [wsjt-devel] FT8: Potential new mode for fast QSOs

Dear Development Colleagues,

Steve (K9AN) and I have developed a potential new mode for WSJT-X. 
We're calling the mode "FT8" (Franke-Taylor design, 8-FSK modulation).

FT8 is designed for situations like multi-hop Es where signals may be weak
and fading, openings may be short, and you want fast completion of reliable,
confirmable QSOs.

Important characteristics of FT8:

   - T/R sequence length: 15 s
   - Message length: 75 bits + 12-bit CRC
   - FEC code: LDPC(174,87)
   - Modulation: 8-FSK, keying rate = tone spacing = 5.86 Hz
   - Waveform: Continuous phase, constant envelope
   - Occupied bandwidth: 47 Hz
   - Synchronization: three 7x7 Costas arrays (start, middle, end of Tx)
   - Transmission duration: 79*2048/12000 = 13.48 s
   - Decoding threshold: -20 dB (perhaps -24 dB with AP decoding, TBD)
   - Operational behavior: similar to HF usage of JT9, JT65
   - Multi-decoder: finds and decodes all FT8 signals in passband
   - Auto-sequencing after manual start of QSO

*Comparison with slow modes JT9, JT65, QRA64:*  FT8 is a few dB less
sensitive but allows completion of QSOs four times faster.  Bandwidth is
greater than JT9, but about 1/4 of JT65A and less than 1/2 QRA64.

*Comparison with fast modes JT9E-H:*  FT8 is significantly more sensitive,
has much smaller bandwidth, uses the vertical waterfall, and offers
multi-decoding over the full displayed passband.

*Still to come, not yet implemented:*  We plan to implement signal
subtraction, two-pass decoding, and use of "a priori" (already known)
information as it accumulates during a QSO.

Three extra bits are available in the message payload, with uses yet to be
defined.  We have in mind special message formats that might be used in
contests, and the like.  Your considered suggestions for use of these bits
are very welcome!

K1JT, K9AN, and G4WJS have conducted on-the-air tests of FT8 with excellent
results.  We're now at a stage where tests under a wider range of conditions
are desirable.  If you can build WSJT-X from source code revision r7750 or
later, and would like to help, please do so and report your results to us!
Pre-built installation packages will be made available after further testing
is completed.

Suggestions for FT8 setup and examples of use can be found in a screen shot
posted here: http://physics.princeton.edu/pulsar/k1jt/ft8.png

We look forward to receiving your feedback.

-- 73, Joe, K1JT


--
Check out the vibrant tech community on one of the world's most engaging
tech sites, Slashdot.org! http://sdm.link/slashdot
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel


--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Hamlib3 compile error

[Dan Malcolm]

Bill,
This is getting ridiculous.  I really appreciate your patience and
expertise, but it seems that what is supposed to be there just isn't.  Now I
can run rebaseall from dash.exe but not as /bin/rebaseall, but as rebaseall.
In addition rebaseall errors out saying it can't find 'lib'.  I am also
having to substitute mingw32 for mingw because there is no mingw in JTSDK.

A long time ago I set up and maintained a Slackware Linux mail server, so I
am familiar with but by no means an expert with UNIX.  Still, I appreciate
the 'fork' explanation.  I didn't know there was a difference between UNIX
and Windows in how they share libraries.

What to do?  Since I have the MinGW Installation Manager I guess I could
install everything it offers, but it may be installed in the wrong place to
do any good.  Thinking of our email exchanges it seems you expect a lot of
utilities to be available and available in a particular place.  Is it
possible that something went missing during my initial package installation?
Several months ago when I first installed JTSDK, it all just
worked.until it all of sudden didn't.  Uninstalled and deleted the JTSDK
directory, and started over.  The problem didn't change.  You've seen my
list of installed packages.  Did I miss something?  Should I wipe it out and
start over?  Should I install all of MinGW?  Fortunately the one thing I do
have is plenty of HD space with a 1TB SSD and more than half empty.

I really appreciate your time and advice

_
Dan Malcolm CFI/II
K4SHQ


-Original Message-
From: Bill Somerville [mailto:g4...@classdesign.com] 
Sent: Monday, March 06, 2017 5:54 AM
To: wsjt-devel@lists.sourceforge.net
Subject: Re: [wsjt-devel] Hamlib3 compile error

On 06/03/2017 03:50, Dan Malcolm wrote:
> Got that and installed it.  MIngw-get still failed but a search found 
> the program under C:\JTSDK\mingw32\bin so I used the full path from 
> the JTSDK MYS prompt.  That ran and seemed to install a few pages.  
> Closed all JTSDK windows and then found dash.exe right where you said 
> it would be.  It opened a window and /bin/rebaseall gave me this error:
> $ /bin/rebaseall
> /bin/rebaseall: 207: find: not found
> /bin/rebaseall: 207: grep: not found
> /bin/rebaseall: 207: find: not found
> /bin/rebaseall: 207: grep: not found

Hi Dan,

Hmmm, this may become a bit lengthy. Let me try and explain why rebaseall is
needed. Unix like systems use a system call named fork() to create all new
processes by exactly copying the memory content of the current process to
make a new child process, this is fundamental to how shells run programs.
Because msys is the MinGW (GNU gcc compilers on
Windows) shell and is based on Unix principles it needs an emulation of
fork() for Windows. Windows has a different way of creating processes with
the CreateProcess[Ex]() system call which does something very different. One
behaviour of Unix like systems is that in a forked child process any
references shared libraries (like DLLs) are loaded at exactly the same
virtual address in the new process as the old one. This is an
oversimplification as Unix like systems really use a technique called
position independent code but it amounts to the same thing. This means that
code pre-compiled to call shared library routines will continue to work in
the child process. In Windows this can go wrong as DLL code can appear at
different addresses in different processes. The rebase action fixes up the
msys and MinGW DLLs so that does not happen.

So what to do? I suspect that you can install enough of the msys system to
allow the rebseall command to work but it might take a few attempts. 
At least you have the mingw-get tool available now to install new packages.
Try this from a JTSDK msys prompt:

mingw-get install msys-base

and if it works try the procedure to run rebaseall from a dash shell again.

73
Bill
G4WJS.



--
Check out the vibrant tech community on one of the world's most engaging
tech sites, SlashDot.org! http://sdm.link/slashdot
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel


--
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Hamlib3 compile error

[Dan Malcolm]

The very first step failed with 'bash.exe: mingw-get: command not found'. 
_
Dan Malcolm CFI/II
K4SHQ


-Original Message-
From: Bill Somerville [mailto:g4...@classdesign.com] 
Sent: Sunday, March 05, 2017 6:00 PM
To: wsjt-devel@lists.sourceforge.net
Subject: Re: [wsjt-devel] Hamlib3 compile error

On 05/03/2017 23:31, Dan Malcolm wrote:
> The build log is attached.

Hi Dan,

try the following:-

Open a JTSDK MSYS prompt and type:

mingw-get install msys-rebase

Exit the MSYS window and any other MSYS window that might be open -- this
step is important.

In Windows open a File Explorer window (Windows-Key+E) and navigate to the
MSYS bin folder. It will be something like:

C:\JTSDK\MinGW\msys\1.0\bin

Scroll down until you locate dash.exe and double click it. A small command
window should open. Type the following:

/bin/rebaseall

then hit ENTER. It should take a minute or so to complete.

Quit the dash window by tying CTRL+D.

Now try the build again.

73
Bill
G4WJS.



--
Check out the vibrant tech community on one of the world's most engaging
tech sites, SlashDot.org! http://sdm.link/slashdot
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel


--
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Hamlib3 compile error

[Dan Malcolm]

Greg,
Bill thinks adding V=1 to the make command line may show something.  Neither
of us know how to do that in JTSDK.  Can you help with that?

_
Dan Malcolm CFI/II
K4SHQ


-Original Message-
From: Greg Beam [mailto:ki7m...@gmail.com] 
Sent: Sunday, March 05, 2017 10:46 AM
To: wsjt-devel@lists.sourceforge.net
Subject: Re: [wsjt-devel] Hamlib3 compile error

Hi Dan,

I was mistaken on the msys-64int. I checked my version of Perl via different
method that only yields the version number. Using --version on my
installation also returns 64int in the name. I also checked the dll headers
with dumpbin and it's definitely a 32 bit dll, so you can take that rabbit
trail off the table, sorry about that.

I've tried several methods to reproduce the error your seeing, but, have had
no luck thus far. At present, I am at a loss as to what is causing your
error.

73's
Greg, KI7MT



> On 03/04/2017 06:35 PM, Dan Malcolm wrote:
>> Ok Bill,
>> That's no problem if someone can tell me how exactly.  I found the 
>> Autoconf file but the text says not to directly edit it, so I didn't.  
>> I also didn't find any place to edit the make command line.
>>
>> _
>> Dan Malcolm CFI/II
>> K4SHQ
>>
>>
>> -Original Message-
>> From: Bill Somerville [mailto:g4...@classdesign.com]
>> Sent: Saturday, March 04, 2017 1:57 PM
>> To: wsjt-devel@lists.sourceforge.net
>> Subject: Re: [wsjt-devel] Hamlib3 compile error
>>
>> On 04/03/2017 19:21, Dan Malcolm wrote:
>>> v5.8.8 built for msys-64int
>>
>> Hi Dan,
>>
>> ok, that also is fine. I need to see the full and verbose Hamlib 
>> build output. Problem is I'm not sure how to do that with the JTSDK, 
>> maybe Greg is lurking and can help out. What is needed is to add V=1 
>> to the Hamlib make command and also to redirect all the output 
>> (stderr and
>> stdout) to a log file. Then zip and send me that file please?
>>
>> 73
>> Bill
>> G4WJS.
>>


--
Check out the vibrant tech community on one of the world's most engaging
tech sites, SlashDot.org! http://sdm.link/slashdot
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel


--
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Hamlib3 compile error

[Dan Malcolm]

Actually I was surprised to see it was 64 bit also, but since there is a lot
I don't know about JTSDK, I thought that was normal.  At least until I read
your email I did.  This info is on a fresh install.  When this problem
started and rebooting didn't solve it, I uninstalled JTSDK, downloaded all
new packages from Sourceforge, and then reinstalled.  The packages I
downloaded are:
JTSDK-2.0.0-u1-win32.exe
JTSDK-2.0.0-u2-win32.exe
JTSDK-2.0.0-u3-win32.exe
JTSDK-2.0.0-u4-win32.exe
JTSDK-2.0.0-win32.exe

_
Dan Malcolm CFI/II
K4SHQ


-Original Message-
From: KI7MT [mailto:ki7m...@gmail.com] 
Sent: Sunday, March 05, 2017 12:15 AM
To: wsjt-devel@lists.sourceforge.net
Subject: Re: [wsjt-devel] Hamlib3 compile error

Hi Dan, Bill,

I'm not sure how Dan got a 64-bit version of MSYS Perl installed, as the
installer I created had 32bit MSYS. All of the software in JTSDK is 32bit,
as are the WSJT packages it creates, unless something has changed.

Dan, Are you sure that Perl is 64bit and not 32bit?

73's
Greg, KI7MT

On 03/04/2017 06:35 PM, Dan Malcolm wrote:
> Ok Bill,
> That's no problem if someone can tell me how exactly.  I found the 
> Autoconf file but the text says not to directly edit it, so I didn't.  
> I also didn't find any place to edit the make command line.
> 
> _________
> Dan Malcolm CFI/II
> K4SHQ
> 
> 
> -Original Message-
> From: Bill Somerville [mailto:g4...@classdesign.com]
> Sent: Saturday, March 04, 2017 1:57 PM
> To: wsjt-devel@lists.sourceforge.net
> Subject: Re: [wsjt-devel] Hamlib3 compile error
> 
> On 04/03/2017 19:21, Dan Malcolm wrote:
>> v5.8.8 built for msys-64int
> 
> Hi Dan,
> 
> ok, that also is fine. I need to see the full and verbose Hamlib build 
> output. Problem is I'm not sure how to do that with the JTSDK, maybe 
> Greg is lurking and can help out. What is needed is to add V=1 to the 
> Hamlib make command and also to redirect all the output (stderr and
> stdout) to a log file. Then zip and send me that file please?
> 
> 73
> Bill
> G4WJS.
> 


--
Check out the vibrant tech community on one of the world's most engaging
tech sites, SlashDot.org! http://sdm.link/slashdot
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel


--
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Hamlib3 compile error

[Dan Malcolm]

Ok Bill, 
That's no problem if someone can tell me how exactly.  I found the Autoconf
file but the text says not to directly edit it, so I didn't.  I also didn't
find any place to edit the make command line.  

_
Dan Malcolm CFI/II
K4SHQ


-Original Message-
From: Bill Somerville [mailto:g4...@classdesign.com] 
Sent: Saturday, March 04, 2017 1:57 PM
To: wsjt-devel@lists.sourceforge.net
Subject: Re: [wsjt-devel] Hamlib3 compile error

On 04/03/2017 19:21, Dan Malcolm wrote:
> v5.8.8 built for msys-64int

Hi Dan,

ok, that also is fine. I need to see the full and verbose Hamlib build
output. Problem is I'm not sure how to do that with the JTSDK, maybe Greg is
lurking and can help out. What is needed is to add V=1 to the Hamlib make
command and also to redirect all the output (stderr and
stdout) to a log file. Then zip and send me that file please?

73
Bill
G4WJS.



--
Check out the vibrant tech community on one of the world's most engaging
tech sites, SlashDot.org! http://sdm.link/slashdot
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel


--
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Hamlib3 compile error

[Dan Malcolm]

v5.8.8 built for msys-64int

_
Dan Malcolm CFI/II
K4SHQ


-Original Message-
From: Bill Somerville [mailto:g4...@classdesign.com] 
Sent: Saturday, March 04, 2017 6:28 AM
To: wsjt-devel@lists.sourceforge.net
Subject: Re: [wsjt-devel] Hamlib3 compile error

On 04/03/2017 03:38, Dan Malcolm wrote:
> >From JTSDK-MSYS prompt 'which perl' yields '/bin/perl.exe'

Hi Dan,

Ok, that seems fine. Next try:

perl --version

from the same command shell.

73
Bill
G4WJS.



--
Check out the vibrant tech community on one of the world's most engaging
tech sites, SlashDot.org! http://sdm.link/slashdot
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel


--
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Hamlib3 compile error

[Dan Malcolm]

All,
The very first error encountered is "Win32 error 998" which is translated as
"Invalid access to memory location".  Reading the Win10 Application log I
find the faulting application is perl.exe and faulting module is
msys-perl5_8.dll subsequent errors fault the same file or state 'unknown'.
So far I have lots of indicator messages, but I don't yet have a handle on
the problem.

Prior to yesterday I have been able to compile the devel package just fine,
and did so every week or so.  Obviously something changed on my computer.

_________
Dan Malcolm CFI/II
K4SHQ

-Original Message-
From: Greg Beam [mailto:ki7m...@gmail.com] 
Sent: Friday, March 03, 2017 5:44 PM
To: WSJT software development <wsjt-devel@lists.sourceforge.net>
Subject: Re: [wsjt-devel] Hamlib3 compile error

Hi Dan, All,

I'm not sure what's going on here either. My version of Perl, via MSYS, is
5.8.8. I was able to build Hamlib3 from MSYS directly, and JTSDK-QT via QT
5.2 and 5.5 without error.

As Bill suggested, log the build and post it. To eliminate JTSDK-QT ENV, use
the JTSDK-MSYS terminal, then:

 From JTSDK-MSYS Terminal, type the command:

build-hamlib3 |tee -a hamlib3-build.log

or

build-hamlib3 >> hamlib3-build.log

The first command allows you to watch the build progress. Then post that
file to the dev list.

As best I can tell, there are no versions of Perl associated with QT, so
that should not be a conflict of any sort. The update process within JTSDK
does not alter the MSYS installation. So, if the build worked at some point
in the past, something has changed in one of the environments on your
system. What, and where would be a question only you could answer.

73's
Greg, KI7MT

On 3/3/2017 10:58 AM, Dan Malcolm wrote:
> Bill,
>
> Reboot didn't help and the Windows Event Log messages just reported 
> what was already known.  I uninstalled JTSDK and then deleted the 
> folder.  I downloaded fresh files from SourceForge, and did a complete
reinstall.
> The problem is not fixed.  See the attached capture image.  WSJT-X 
> compilation also failed under JTSDK-QT.  There were so many error 
> lines that I could not scroll back far enough to see the first one.
> Experience has taught me to fix the first reported failure first.  Are 
> these problems related?
>
>
>
> _
>
> Dan Malcolm CFI/II
>
> K4SHQ
>
>
>
> *From:*Bill Somerville [mailto:g4...@classdesign.com]
> *Sent:* Thursday, March 02, 2017 10:21 AM
> *To:* wsjt-devel@lists.sourceforge.net
> *Subject:* Re: [wsjt-devel] Hamlib3 compile error
>
>
>
> On 02/03/2017 16:06, Dan Malcolm wrote:
>
> Seems the offending module is: Faulting module path:
> C:\JTSDK\msys\bin\msys-perl5_8.dll.
>
> The problem seems to be inability to find a file
>
> It appears I am using Perl5_8.  If memory serves, there was a
> discussion about which Perl version should be used.  Could 5.8 be
> the problem?
>
> HI Dan,
>
> the message is telling us that the version of perl being used is the 
> one in the JTSDK. That should be fine. The errors were memory access 
> and copy errors. It could possibly be a corrupted file in the JTSDK. 
> If rebooting does not sort this out and there is nothing in the 
> Windows Event Log then it may be worth trying to re-install the JTSDK.
>
> 73
> Bill
> G4WJS.


--
Check out the vibrant tech community on one of the world's most engaging
tech sites, SlashDot.org! http://sdm.link/slashdot
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel


--
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Hamlib3 compile error

[Dan Malcolm]

I know its my specific to my system.  Just not sure what it is.  There were
no install errors.  I still have the question: Are these two failures
(Hamlib3 and WSJTX) related?  I think not, but you know the architecture
better than I do. 



Dan Malcolm CFI/II

K4SHQ

 

From: Bill Somerville [mailto:g4...@classdesign.com] 
Sent: Friday, March 03, 2017 12:07 PM
To: wsjt-devel@lists.sourceforge.net
Subject: Re: [wsjt-devel] Hamlib3 compile error

 

On 03/03/2017 17:58, Dan Malcolm wrote:

There were so many error lines that I could not scroll back far enough to
see the first one.  Experience has taught me to fix the first reported
failure first.  Are these problems related?

Hi Dan,

this is something specific to your system, no one else is reporting similar
issues.

To see the first error you need to redirect the build output to a file. Try:

build-command >build.log 2>&1

73
Bill
G4WJS.

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] error on building WSJT-x with JTSDK

[Dan Malcolm]

Yep. That fixed my problem too.  Thanks Greg.

_
Dan Malcolm CFI/II
K4SHQ

-Original Message-
From: Greg Beam [mailto:ki7m...@gmail.com] 
Sent: Monday, December 12, 2016 3:55 PM
To: WSJT software development <wsjt-devel@lists.sourceforge.net>
Subject: Re: [wsjt-devel] error on building WSJT-x with JTSDK

Hi Bill,

Everything is back to normal, thanks.

73's

Greg, KI7MT



On 12/12/2016 11:27 AM, Bill Somerville wrote:
> On 12/12/2016 12:50, Jay Hainline wrote:
>> Attached is an error message I received this morning when trying to 
>> build to the latest version of WSJT-x 1.7.0-rc3.
> Hi Jay,
>
> sorry about that, a small issue compatibility with older versions of Qt.
> Should be ok as of r7380.
>
> 73
> Bill
> G4WJS.
>
>
> --
>  Check out the vibrant tech community on one of the world's 
> most engaging tech sites, SlashDot.org! http://sdm.link/slashdot 
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel



--
Check out the vibrant tech community on one of the world's most engaging
tech sites, SlashDot.org! http://sdm.link/slashdot
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel


--
Check out the vibrant tech community on one of the world's most 
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

[wsjt-devel] Build error on RC3

[Dan Malcolm]

I have been building the v1.7.0 threat for many months now, refreshing my
build environment at least every couple of weeks.  I did that this afternoon
and received the following error list:

 

CMakeFiles\wsjt_qt.dir\build.make:92: recipe for target
'CMakeFiles/wsjt_qt.dir/MessageBox.cpp.obj' failed

mingw32-make.exe[2]: *** [CMakeFiles/wsjt_qt.dir/MessageBox.cpp.obj] Error
-1073741819

mingw32-make.exe[2]: *** Waiting for unfinished jobs

CMakeFiles\Makefile2:1622: recipe for target 'CMakeFiles/wsjt_qt.dir/all'
failed

mingw32-make.exe[1]: *** [CMakeFiles/wsjt_qt.dir/all] Error 2

makefile:136: recipe for target 'all' failed

mingw32-make.exe: *** [all] Error 2

 

This is a Win10 x64 computer and v1.7,0-rc3 r7367 compiled and ran just
fine.  I noticed that someone else had a problem that was fixed by enabling
QT5.5.  My options list shows QT5.5 not enabled.  Could this be my problem?

 

___

Dan Malcolm

K4SHQ


Politicians are people who, when they see light at the end
of the tunnel, go out and buy some more tunnel.

 

--
Check out the vibrant tech community on one of the world's most 
engaging tech sites, SlashDot.org! http://sdm.link/slashdot___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] ALL.txt idea

[Dan Malcolm]

Am I missing something?  I don't get any date indicators in ALL.TXT.  I get
time in 24 hour format, and of course whatever else appears in the "Band
Activity" window, but no date.  IMHO the date (in ISO format) would be a
useful piece of information, but so far I have gotten along without it.

_____
Dan Malcolm CFI/II
K4SHQ


-Original Message-
From: Alessandro Gorobey [mailto:algi...@libero.it] 
Sent: Tuesday, November 08, 2016 3:12 PM
To: wsjt-devel@lists.sourceforge.net
Subject: Re: [wsjt-devel] ALL.txt idea

Hi Claude and All,

ALL.TXT is borne to dump all the lines in receive window.

I think that insert in a database is very expansive as space and processor
and lost the simplicity of search with preferred programs.

The format of file is changed in years and actually use some more characters
after introduction of new decoders.

Sincerely I not like the months names in the markers and a ISO 8601 format
will be preferable, using machines with different languages.

2013-lug-06 16:24  14.078 MHz  JT9
2013-jul-06 16:24  14.078 MHz  JT9
2013-07-06 16:24  14.078 MHz  JT9  <== ISO

Sincerely I think that ALL.TXT without the nationalization strings is good
for the work.

--
73
Sandro
IW3RAB

Il 08/11/2016 16:49, Claude Frantz ha scritto:
> On 11/07/2016 06:11 PM, Roger Rehr W3SZ wrote:
>
> Hi Roger,
>
> Writing such simple structures in a SQL database is overkill, in my 
> humble opinion. Concerning the ADIF log, there is no general 
> definition of a SQL Database mapping outside of specific logging 
> programs. The new alternative XML definition of ADIF 3.* is not of 
> great help because XML based databases are a very special matter.
>
> Previously, I have pointed to the problem of the ADIF TIME_ON field 
> which contains the data which should be in the TIME_OFF and to the 
> problems around this matter. Up to now, I have found no response.
>
> Best 88 de Claude (DJ0OT)
>
> --
>  Developer Access Program for Intel Xeon Phi Processors Access 
> to Intel Xeon Phi processor-based developer platforms.
> With one year of Intel Parallel Studio XE.
> Training and support from Colfax.
> Order your platform today. http://sdm.link/xeonphi 
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>

--
73
Sandro
IW3RAB


--
Developer Access Program for Intel Xeon Phi Processors Access to Intel Xeon
Phi processor-based developer platforms.
With one year of Intel Parallel Studio XE.
Training and support from Colfax.
Order your platform today. http://sdm.link/xeonphi
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel


--
Developer Access Program for Intel Xeon Phi Processors
Access to Intel Xeon Phi processor-based developer platforms.
With one year of Intel Parallel Studio XE.
Training and support from Colfax.
Order your platform today. http://sdm.link/xeonphi
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel