Date   

locked Re: JTSDK-QT Upgrade (major changes)

Michael Black
 

I didn't have JTSDK-DOC so I downloaded it from https://www.mail-archive.com/wsjt-devel@.../msg00013.html

Installed it.

 

CD JTSSK-DOC

Ran jtsdk-docenv.bat

It said I need to "svn co…." so I did that.

Re-ran jtsdk-docenv.bat

It dumped in the "doc" subdir.

svn update of course did nothing since I just checked out the project

 

update then said this:

******************************

     MASTER SCRIPT UPDATE

******************************

 

.. Checking For Pkg-Config Installation

The system cannot find the path specified.

.. Not Found, Installing Pkg-Config v0.28

cp: cannot stat `pkg-config.7z': No such file or directory

The system cannot find the path specified.

.. Cleaning Up After Pkg-Config Install

rm: cannot remove `pkg-config.7z': No such file or directory

.. Finished Pkg-Config Installation

The system cannot find the path specified.

.. Checking For NSIS Package Installation

The system cannot find the path specified.

.. Not Found, Installing NSIS v0.03a2

cp: target `C:\\JTSDK-QT\\' is not a directory: No such file or directory

The system cannot find the path specified.

.. Cleaning Up After Install

rm: cannot remove `NSIS.7z': No such file or directory

The system cannot find the path specified.

.. Finished NSIS Installation

Done

 

I installed on D: and not C:.

So moved it all to C:

Then it updated OK.

 

Does it have to depend on being on C: ??  I couldn't find where it referred to the driver letter at all.

 

Mike W9MDB

 

 

 

 

From: HamApps@... [mailto:HamApps@...]
Sent: Wednesday, September 03, 2014 4:23 PM
To: WSJT software development; wsjtgroup; HamApps@...; wsjtx@...
Subject: [HamApps] JTSDK-QT Upgrade (major changes)

 

 

Hello All,

For those of you using JTSDK-QT to build WSJT-X, WSPR-X or MAP65 on
Windows, I posted a series of changes this afternoon to the SDK. The
changes fix a major concern in building WSJT-X with Cmake (Hamlib3
related), add / correct some functionality omissions and fix a few
problems that were causing issues elsewhere.

The following outlines the upgrade instructions and provides a bit more
detail on the changes. As always, if you experience issues with the
upgrade, or with any of the functionality, send them to the
wsjt-dev-list or feel free to contact me off-list.

*UPGRADE INSTRUCTIONS*

JTSDK-DOC should be used to perform the upgrade, as the script uses
a combination Unix & Windows commands, and the archive files are
compressed with 7z which may or may not be installed on the users
system.

Open JTSKD-DOC ( C:\JTSDK-DOC\jtsdk-docenv.bat )
At the prompt, update from SVN .. svn update
At the prompt, run update ....... update

That is all. ( install-scripts.bat ) should copy the new scripts
and install NSIS + Pkg-Config to the correct location(s).

Please report any issues you experience with the upgrade process
or SDK functionality

*MAJOR CHANGES*

* ADDED Pkg-Config-Lite v0.28:
This solves an issue during the Cmake Build process for WSJT-X.
Pkg-Config (which Findhamlib.cmake relies on) was not being found
and causing problems with Hamlib3 library locations. Thus, several
users were having trouble with Hamlib post build. The root of the
problem points to the missing pkg-config package.

* ADDED NSIS v0.3a2 Installer Software:
WSJT-X has a target to build a Windows Installer and uses NSIS as
the tool. We can now build the Windows Installer with a simple cmake
invocation or via the build script:

Build Script ... build wsjtx package
Command-line ... cmake --build . --target package
Output File .... wsjtx-1.4.0-win32.exe

* Default File Locations:
This should not have been in the build script at all, as it is a
CmakeLists.txt option which is defaulted to on. Changing it too
"off" was causing problems with later version of JT-Alerts-X, not to
mention, the implementation was wrong to begin with. If a user needs
to change Cmake config Options, it should be done using the cmake-gui,
QtCreator or manually editing / configuring from the command-line.

* New Build Invocations:
Previously, the build script simply built the Install Target. Now,
we can configure the Build Tree, build the Install Target or build
the NSIS Package Target. For Build Tree Configuration and Install
targets, both Debug and Release are available. The NSIS Package Target
is only available for WSJT-X as MAP65 and WSPR-X do not have package
targets in their CmakeLists.txt files. Help files are provided which
list the new invocations, in the event a user inputs the wrong
the instruction set. The user can also list them by simply typing:
( build-help ) in the JTSDK-QT environment.

* Dev Guide Updates:
The JTSDK-QT section needs to be fully re-written, and many
additional features added. As Time Allows, I will get to this but I want
flush out any issues of the update in parallel.

---
73's
Greg, KI7MT


locked JTSDK-QT Upgrade (major changes)

KI7MT <ki7mt@...>
 

Hello All,

For those of you using JTSDK-QT to build WSJT-X, WSPR-X or MAP65 on
Windows, I posted a series of changes this afternoon to the SDK. The
changes fix a major concern in building WSJT-X with Cmake (Hamlib3
related), add / correct some functionality omissions and fix a few
problems that were causing issues elsewhere.

The following outlines the upgrade instructions and provides a bit more
detail on the changes. As always, if you experience issues with the
upgrade, or with any of the functionality, send them to the
wsjt-dev-list or feel free to contact me off-list.

*UPGRADE INSTRUCTIONS*

JTSDK-DOC should be used to perform the upgrade, as the script uses
a combination Unix & Windows commands, and the archive files are
compressed with 7z which may or may not be installed on the users
system.

Open JTSKD-DOC ( C:&#92;JTSDK-DOC&#92;jtsdk-docenv.bat )
At the prompt, update from SVN .. svn update
At the prompt, run update ....... update

That is all. ( install-scripts.bat ) should copy the new scripts
and install NSIS + Pkg-Config to the correct location(s).

Please report any issues you experience with the upgrade process
or SDK functionality

*MAJOR CHANGES*

* ADDED Pkg-Config-Lite v0.28:
This solves an issue during the Cmake Build process for WSJT-X.
Pkg-Config (which Findhamlib.cmake relies on) was not being found
and causing problems with Hamlib3 library locations. Thus, several
users were having trouble with Hamlib post build. The root of the
problem points to the missing pkg-config package.

* ADDED NSIS v0.3a2 Installer Software:
WSJT-X has a target to build a Windows Installer and uses NSIS as
the tool. We can now build the Windows Installer with a simple cmake
invocation or via the build script:

Build Script ... build wsjtx package
Command-line ... cmake --build . --target package
Output File .... wsjtx-1.4.0-win32.exe

* Default File Locations:
This should not have been in the build script at all, as it is a
CmakeLists.txt option which is defaulted to on. Changing it too
"off" was causing problems with later version of JT-Alerts-X, not to
mention, the implementation was wrong to begin with. If a user needs
to change Cmake config Options, it should be done using the cmake-gui,
QtCreator or manually editing / configuring from the command-line.

* New Build Invocations:
Previously, the build script simply built the Install Target. Now,
we can configure the Build Tree, build the Install Target or build
the NSIS Package Target. For Build Tree Configuration and Install
targets, both Debug and Release are available. The NSIS Package Target
is only available for WSJT-X as MAP65 and WSPR-X do not have package
targets in their CmakeLists.txt files. Help files are provided which
list the new invocations, in the event a user inputs the wrong
the instruction set. The user can also list them by simply typing:
( build-help ) in the JTSDK-QT environment.

* Dev Guide Updates:
The JTSDK-QT section needs to be fully re-written, and many
additional features added. As Time Allows, I will get to this but I want
flush out any issues of the update in parallel.

---
73's
Greg, KI7MT


locked Re: : RE: Re:: Problem Running JT-Alert with WSJT-X 1.4

chas cartmel
 

Paraphrasing from a response from the developers of WSJt_X

“Wsjt-X is deemed as an ALPHA and has not been officially released. The copies being used are either compiled by the user themselves or have been provided by a 3rd party without the appropriate installer”

 

73

Charlie

www.G4EST.me.uk

 

From: HamApps@... [mailto:HamApps@...]
Sent: 02 September 2014 12:36
To: HamApps@...
Subject: RE: : RE: [HamApps] Re:: Problem Running JT-Alert with WSJT-X 1.4

 

 

Are you running HRD?  There's a problem with running WSJT-X and HRD Logger or DM780 for example as they all try to use the HRD TCP port. And there's a bug with HRD that causes WSTX to lose data.

I'm working with Bill trying to fix this.  You need to say how you're hooked up to your radio and what radio.

And this software should be called "alpha" since it hasn't been release for general testing yet.

 

And are you saying you HAVE to set it zero or else you had this problem with WSTX-1.3?  Does 1.3 work OK and 1.4 doesn’t'?  Could you explain your issue a little clearer?

 

Mike W9MDB

 

From: HamApps@... [mailto:HamApps@...]
Sent: Monday, September 01, 2014 11:00 PM
To: HamApps@...
Subject: Re:: RE: [HamApps] Re:: Problem Running JT-Alert with WSJT-X 1.4

 

 

Bill,

 

I tried a copy of v1.4 I got from someone and found that the polling time could not be set to zero. With this, I would get an error that shut off each transmission when the radio would not respond to polling requests. As you said, this is a beta but I did not know if you all were aware of that issue.

 

Fred - KK5AA

EM25xh


locked Re: : HamApps Database 14.09.01 Error

Laurie, VK3AMA <groups06@...>
 

Tom,

Another possibility is that your Virus/Malware software is preventing the Registry writes that occur during an application install/upgrade.

de Laurie VK3AMA
   

On 3/09/2014 7:25 AM, ve3ii@... [HamApps] wrote:


Hi Laurie...

No, there is no error number associated with the error box.  Theres the caution symbol and then the error message but no error number.  So, I dunno...

It may be a Windows issue because, well, it's Windows :)  Anyways, it's not a big issue for me.  I'll wait for the next update and see if it installs then.  If it fails, I'll have to go through things and see if I can track it down.  It might be a permission thing but no time to hunt right now.

73 and thanks...

Tom


locked Re: : Re: Problem Running JT-Alert with WSJT-X 1.4

Joe Subich, W4TV
 

The point is not to install a development environment. However, when
there is semi-regular discussion of a new version of WSJT-X and I get
questions about its operation with microHAM interfaces it is a problem
when I don't know what's going on with the software.

73,

... Joe, W4TV

On 2014-08-31 3:59 PM, ki7mt ki7mt@yahoo.com [HamApps] wrote:
If you need instruction for installing JTSDK-QT / JTSDK-DOC, let me know
and we can get you up an running to build all the WSJT Apps on Wndows.
The Linux JTSDK is still in WIP, but does build WSJT-X and WSPR.

73's
Greg, KI7MT


On 08/31/2014 01:46 PM, 'Joe Subich, W4TV' lists@subich.com [HamApps]
wrote:


And if one does not have the necessary development environment?

73,

... Joe, W4TV

On 2014-08-31 3:02 PM, we2s.jim@gmail.com [HamApps] wrote:
It can be compiled from files available on Source Forge.

Jim


locked Re: : HamApps Database 14.09.01 Error

Michael Black
 

Did you run the fixit from the Microsoft website reference you were provided?

Mike W9MDB

 

From: HamApps@... [mailto:HamApps@...]
Sent: Tuesday, September 02, 2014 4:26 PM
To: HamApps@...
Subject: [HamApps] Re:: HamApps Database 14.09.01 Error

 

 

Hi Laurie...

No, there is no error number associated with the error box.  Theres the caution symbol and then the error message but no error number.  So, I dunno...

It may be a Windows issue because, well, it's Windows :)  Anyways, it's not a big issue for me.  I'll wait for the next update and see if it installs then.  If it fails, I'll have to go through things and see if I can track it down.  It might be a permission thing but no time to hunt right now.

73 and thanks...

Tom


locked Re: : HamApps Database 14.09.01 Error

Tom Job
 

Hi Laurie...

No, there is no error number associated with the error box.  Theres the caution symbol and then the error message but no error number.  So, I dunno...

It may be a Windows issue because, well, it's Windows :)  Anyways, it's not a big issue for me.  I'll wait for the next update and see if it installs then.  If it fails, I'll have to go through things and see if I can track it down.  It might be a permission thing but no time to hunt right now.

73 and thanks...

Tom


locked Re: Side lobes

Joe Subich, W4TV
 

Check the power supplies for your radio and your sound card.


73,

... Joe, W4TV

On 2014-09-02 5:00 PM, 'Michael Black' mdblack98@yahoo.com [HamApps] wrote:
I had found that if I notched the main signal the lobes disappeared. So
it's my end.

I did a master reset on my radio so I'll see if that helps me. I was seeing
way too many of these side lobes that last week or so.

Mike W9MDB



From: HamApps@yahoogroups.com.au [mailto:HamApps@yahoogroups.com.au]
Sent: Tuesday, September 02, 2014 3:24 PM
To: HamApps@yahoogroups.com.au
Subject: RE: [HamApps] Side lobes





I see it from time to time with good propagation (and very strong signals),
but usually those side lobes are more than 20 dB down. This one is only 10
dB down and that's bad, but it can be hard to tell if it's generated on the
TX end or an overload on the receive end. The sidelobe is about 180 Hz off
from the main signal, the 3rd harmonic of 60 Hz.

_________
73,
Jim - N4ST

From: HamApps@yahoogroups.com.au [mailto:HamApps@yahoogroups.com.au]
Sent: Tuesday, September 2, 2014 14:23
To: HamApps@yahoogroups.com.au
Subject: [HamApps] Side lobes


Is anybody else seeing side lobes (multiple decodes) on signals lately?
All of a sudden I'm seeing them quite frequently on strong signals where I
didn't before.

For example just had this on 15M

1816 -1 0.5 271 # OE6ANG KK4TLG EM82
1816 -11 0.5 449 # OE6ANG KK4TLG EM82

Didn't pick up the lower side lobe as it would be off-scale.

I've seen up to 5 decodes on one message due to this (main plus 2 side lobes
each side).

Mike W9MDB





locked Re: Side lobes

Michael Black
 

I had found that if I notched the main signal the lobes disappeared.  So it's my end.

I did a master reset on my radio so I'll see if that helps me.  I was seeing way too many of these side lobes that last week or so.

Mike W9MDB

 

From: HamApps@... [mailto:HamApps@...]
Sent: Tuesday, September 02, 2014 3:24 PM
To: HamApps@...
Subject: RE: [HamApps] Side lobes

 

 

I see it from time to time with good propagation (and very strong signals),
but usually those side lobes are more than 20 dB down. This one is only 10
dB down and that’s bad, but it can be hard to tell if it’s generated on the
TX end or an overload on the receive end. The sidelobe is about 180 Hz off
from the main signal, the 3rd harmonic of 60 Hz.

_________
73,
Jim – N4ST

From: HamApps@... [mailto:HamApps@...]
Sent: Tuesday, September 2, 2014 14:23
To: HamApps@...
Subject: [HamApps] Side lobes

 
Is anybody else seeing side lobes (multiple decodes) on signals lately?
All of a sudden I'm seeing them quite frequently on strong signals where I
didn't before.
 
For example just had this on 15M
 
1816 -1 0.5 271 # OE6ANG KK4TLG EM82
1816 -11 0.5 449 # OE6ANG KK4TLG EM82
 
Didn't pick up the lower side lobe as it would be off-scale.
 
I've seen up to 5 decodes on one message due to this (main plus 2 side lobes
each side).
 
Mike W9MDB
 


locked Re: Side lobes

Jim - N4ST
 

I see it from time to time with good propagation (and very strong signals),
but usually those side lobes are more than 20 dB down. This one is only 10
dB down and that’s bad, but it can be hard to tell if it’s generated on the
TX end or an overload on the receive end. The sidelobe is about 180 Hz off
from the main signal, the 3rd harmonic of 60 Hz.

_________
73,
Jim – N4ST


From: HamApps@yahoogroups.com.au [mailto:HamApps@yahoogroups.com.au]
Sent: Tuesday, September 2, 2014 14:23
To: HamApps@yahoogroups.com.au
Subject: [HamApps] Side lobes

 
Is anybody else seeing side lobes (multiple decodes) on signals lately?
All of a sudden I'm seeing them quite frequently on strong signals where I
didn't before.
 
For example just had this on 15M
 
1816 -1 0.5 271 # OE6ANG KK4TLG EM82
1816 -11 0.5 449 # OE6ANG KK4TLG EM82
 
Didn't pick up the lower side lobe as it would be off-scale.
 
I've seen up to 5 decodes on one message due to this (main plus 2 side lobes
each side).
 
Mike W9MDB


locked Re: : Problem Running JT-Alert with WSJT-X 1.4

KI7MT <ki7mt@...>
 

Hi Dan,

Well your miles ahead of me then. I can spell C++ and that's about it
;-). Joe, Bill and the others are the developers. I just try to cobble
together a layman's way of building the apps ( doesn't always work out
as planned ) to help in testing and things. If it weren't for Bill hand
holding me all the time, I'd be seriously lost.

73's
Greg, KI7MT

On 9/2/2014 19:47, 'Dan Malcolm' dmalcolm24@mchsi.com [HamApps] wrote:


It did help Greg and thanks. I have Omnirig installed now.



Even I am a developer (retired but still keep my hand in) my cpp
experience is a decade or more in past so I can’t consider myself to be
knowledgeable. If I ask a dumb question, please be patient.



____________________________

Dan Malcolm CFI/II

K4SHQ



The best prayer ever said: "Lord please make me the
kind of person my dog thinks I am."



*From:*HamApps@yahoogroups.com.au [mailto:HamApps@yahoogroups.com.au]
*Sent:* Tuesday, September 02, 2014 11:58 AM
*To:* HamApps@yahoogroups.com.au
*Subject:* Re: [HamApps] Re:: Problem Running JT-Alert with WSJT-X 1.4





Hi Dan,

If your using the JTSDK-QT build script, the build trees an install
target locations are fixed for all 3 apps. The script is intended for a
quick build and does not lend itself to a high degree of configuration (
without manually editing of the build script ). The outputs for a WSJT-X
Release build are as follows:

SRC Dir (SVN Checkouts / Updates) = C:&#92;JTSDK-QT&#92;src&#92;wsjtx

BUILD TREE & INSTALL TARGET LOCATION:
Build Tree: C:&#92;JTSDK-QT&#92;wsjtx&#92;Relesae&#92;build
Install Target: C:&#92;JTSDK-QT&#92;wsjtx&#92;Relesae&#92;install&#92;{bin,lib}

FINAL BINARY LOCATION:
Binary: C:&#92;JTSDK-QT&#92;wsjtx&#92;Relesae&#92;install&#92;bin&#92;wsjtx.exe

NSIS PACKAGE INSTALLER ( WSJT-X Only )
This will be available in the next build script update and will produce
a standard Windows Installer. The functionality is present and works
well using command line arguments:

EXAMPLE ( after an initial build tree configuration ):
cd C:&#92;JTSDK-QT&#92;wsjtx&#92;build&#92;Release

cmake --build . --target package

That should produce an NSIS Windows installer, located in:
C:&#92;JTSDK-QT&#92;wsjtx&#92;build&#92;Release&#92;wsjtx-1.4.0-win32.exe

Based on feedback from Bill ( G4WJS ), I'm in the process of changing
several aspects of the build script to enable more control over how the
script configures and builds the different elements / targets. It should
be available in the next few days.

If you want more control over workflows and configuration parameters
(enable debugging elements, change output locations etc), there are far
better solutions than using the script. QtCreator, cmake-gui and command
line tools ( all available in JTSDK-QT ) provide full control over
input, output and build tree configuration. However, using them requires
a higher level of knowledge on the target application.

As for OmniRig, I'm uncertain as to why the script would build
successfully on the first run, then fail on the second. Maybe Bill can
shed some light on that one. The OmniRig installer is included in
JTSDK-QT, under:

C:&#92;JTSDK-QT&#92;tools&#92;OmniRigSetup.exe

Or you can download it from the DX Atlas Website:

http://www.dxatlas.com/omnirig

Hope this help clear things up a bit.

73's
Greg, KI7MT

On 9/2/2014 13:37, 'Dan Malcolm' dmalcolm24@mchsi.com
<mailto:dmalcolm24@mchsi.com> [HamApps] wrote:


OK because I am a developer, I installed the JTSDK-QT kits, and the SVN
kit. I got one sort of successful compile. The build script reported
success and pointed to the file location as
“C:&#92;JTSDK-QT&#92;wsjtx&#92;install&#92;Release” plus a couple more directories that
I’ve now lost track of and can’t find because the quoted path is all
there is. Subsequent builds now report an error and tells me to install
OmniRig on my computer. Ok I can do that, I am just puzzled why I got a
success message on the first run and then the errors show up.



BTW. I am just satisfying my curiousity with this. I have no intention
of doing any developing on WSJT et al.



____________________________

Dan Malcolm CFI/II

K4SHQ



The best prayer ever said: "Lord please make me the
kind of person my dog thinks I am."



*From:*HamApps@yahoogroups.com.au [mailto:HamApps@yahoogroups.com.au]
*Sent:* Sunday, August 31, 2014 8:35 PM
*To:* HamApps@yahoogroups.com.au <mailto:HamApps@yahoogroups.com.au>
*Subject:* [HamApps] Re:: Problem Running JT-Alert with WSJT-X 1.4





Thanks for your reply. Greg, KI7MT suggested this also. It seems to
have solved the problem.



Jim

--
73's
Greg, KI7MT

--
73's
Greg, KI7MT


locked Re: : Problem Running JT-Alert with WSJT-X 1.4

Dan Malcolm <dmalcolm24@...>
 

It did help Greg and thanks.  I have Omnirig installed now. 

 

Even I am a developer (retired but still keep my hand in) my cpp experience is a decade or more in past so I can’t consider myself to be knowledgeable.  If I ask a dumb question, please be patient.

 

____________________________

Dan Malcolm CFI/II

K4SHQ

 

The best prayer ever said: "Lord please make me the
kind of person my dog thinks I am."

 

From: HamApps@... [mailto:HamApps@...]
Sent: Tuesday, September 02, 2014 11:58 AM
To: HamApps@...
Subject: Re: [HamApps] Re:: Problem Running JT-Alert with WSJT-X 1.4

 

 

Hi Dan,

If your using the JTSDK-QT build script, the build trees an install
target locations are fixed for all 3 apps. The script is intended for a
quick build and does not lend itself to a high degree of configuration (
without manually editing of the build script ). The outputs for a WSJT-X
Release build are as follows:

SRC Dir (SVN Checkouts / Updates) = C:\JTSDK-QT\src\wsjtx

BUILD TREE & INSTALL TARGET LOCATION:
Build Tree: C:\JTSDK-QT\wsjtx\Relesae\build
Install Target: C:\JTSDK-QT\wsjtx\Relesae\install\{bin,lib}

FINAL BINARY LOCATION:
Binary: C:\JTSDK-QT\wsjtx\Relesae\install\bin\wsjtx.exe

NSIS PACKAGE INSTALLER ( WSJT-X Only )
This will be available in the next build script update and will produce
a standard Windows Installer. The functionality is present and works
well using command line arguments:

EXAMPLE ( after an initial build tree configuration ):
cd C:\JTSDK-QT\wsjtx\build\Release

cmake --build . --target package

That should produce an NSIS Windows installer, located in:
C:\JTSDK-QT\wsjtx\build\Release\wsjtx-1.4.0-win32.exe

Based on feedback from Bill ( G4WJS ), I'm in the process of changing
several aspects of the build script to enable more control over how the
script configures and builds the different elements / targets. It should
be available in the next few days.

If you want more control over workflows and configuration parameters
(enable debugging elements, change output locations etc), there are far
better solutions than using the script. QtCreator, cmake-gui and command
line tools ( all available in JTSDK-QT ) provide full control over
input, output and build tree configuration. However, using them requires
a higher level of knowledge on the target application.

As for OmniRig, I'm uncertain as to why the script would build
successfully on the first run, then fail on the second. Maybe Bill can
shed some light on that one. The OmniRig installer is included in
JTSDK-QT, under:

C:\JTSDK-QT\tools\OmniRigSetup.exe

Or you can download it from the DX Atlas Website:

http://www.dxatlas.com/omnirig

Hope this help clear things up a bit.

73's
Greg, KI7MT

On 9/2/2014 13:37, 'Dan Malcolm' dmalcolm24@... [HamApps] wrote:
>
>
> OK because I am a developer, I installed the JTSDK-QT kits, and the SVN
> kit. I got one sort of successful compile. The build script reported
> success and pointed to the file location as
> “C:\JTSDK-QT\wsjtx\install\Release” plus a couple more directories that
> I’ve now lost track of and can’t find because the quoted path is all
> there is. Subsequent builds now report an error and tells me to install
> OmniRig on my computer. Ok I can do that, I am just puzzled why I got a
> success message on the first run and then the errors show up.
>
>
>
> BTW. I am just satisfying my curiousity with this. I have no intention
> of doing any developing on WSJT et al.
>
>
>
> ____________________________
>
> Dan Malcolm CFI/II
>
> K4SHQ
>
>
>
> The best prayer ever said: "Lord please make me the
> kind of person my dog thinks I am."
>
>
>
> *From:*HamApps@... [mailto:HamApps@...]
> *Sent:* Sunday, August 31, 2014 8:35 PM
> *To:* HamApps@...
> *Subject:* [HamApps] Re:: Problem Running JT-Alert with WSJT-X 1.4
>
>
>
>
>
> Thanks for your reply. Greg, KI7MT suggested this also. It seems to
> have solved the problem.
>
>
>
> Jim
>
>

--
73's
Greg, KI7MT


locked Side lobes

Michael Black
 

Is anybody else seeing side lobes (multiple decodes) on signals lately?

All of a sudden I'm seeing them quite frequently on strong signals where I didn't before.

 

For example just had this on 15M

 

1816 -1 0.5 271 # OE6ANG KK4TLG EM82

1816 -11 0.5 449 # OE6ANG KK4TLG EM82

 

Didn't pick up the lower side lobe as it would be off-scale.

 

I've seen up to 5 decodes on one message due to this (main plus 2 side lobes each side).

 

Mike W9MDB

 


locked Re: : Problem Running JT-Alert with WSJT-X 1.4

KI7MT <ki7mt@...>
 

Hi Dan,

If your using the JTSDK-QT build script, the build trees an install
target locations are fixed for all 3 apps. The script is intended for a
quick build and does not lend itself to a high degree of configuration (
without manually editing of the build script ). The outputs for a WSJT-X
Release build are as follows:

SRC Dir (SVN Checkouts / Updates) = C:&#92;JTSDK-QT&#92;src&#92;wsjtx

BUILD TREE & INSTALL TARGET LOCATION:
Build Tree: C:&#92;JTSDK-QT&#92;wsjtx&#92;Relesae&#92;build
Install Target: C:&#92;JTSDK-QT&#92;wsjtx&#92;Relesae&#92;install&#92;{bin,lib}

FINAL BINARY LOCATION:
Binary: C:&#92;JTSDK-QT&#92;wsjtx&#92;Relesae&#92;install&#92;bin&#92;wsjtx.exe

NSIS PACKAGE INSTALLER ( WSJT-X Only )
This will be available in the next build script update and will produce
a standard Windows Installer. The functionality is present and works
well using command line arguments:

EXAMPLE ( after an initial build tree configuration ):
cd C:&#92;JTSDK-QT&#92;wsjtx&#92;build&#92;Release

cmake --build . --target package

That should produce an NSIS Windows installer, located in:
C:&#92;JTSDK-QT&#92;wsjtx&#92;build&#92;Release&#92;wsjtx-1.4.0-win32.exe

Based on feedback from Bill ( G4WJS ), I'm in the process of changing
several aspects of the build script to enable more control over how the
script configures and builds the different elements / targets. It should
be available in the next few days.

If you want more control over workflows and configuration parameters
(enable debugging elements, change output locations etc), there are far
better solutions than using the script. QtCreator, cmake-gui and command
line tools ( all available in JTSDK-QT ) provide full control over
input, output and build tree configuration. However, using them requires
a higher level of knowledge on the target application.

As for OmniRig, I'm uncertain as to why the script would build
successfully on the first run, then fail on the second. Maybe Bill can
shed some light on that one. The OmniRig installer is included in
JTSDK-QT, under:

C:&#92;JTSDK-QT&#92;tools&#92;OmniRigSetup.exe

Or you can download it from the DX Atlas Website:

http://www.dxatlas.com/omnirig

Hope this help clear things up a bit.

73's
Greg, KI7MT

On 9/2/2014 13:37, 'Dan Malcolm' dmalcolm24@mchsi.com [HamApps] wrote:


OK because I am a developer, I installed the JTSDK-QT kits, and the SVN
kit. I got one sort of successful compile. The build script reported
success and pointed to the file location as
“C:&#92;JTSDK-QT&#92;wsjtx&#92;install&#92;Release” plus a couple more directories that
I’ve now lost track of and can’t find because the quoted path is all
there is. Subsequent builds now report an error and tells me to install
OmniRig on my computer. Ok I can do that, I am just puzzled why I got a
success message on the first run and then the errors show up.



BTW. I am just satisfying my curiousity with this. I have no intention
of doing any developing on WSJT et al.



____________________________

Dan Malcolm CFI/II

K4SHQ



The best prayer ever said: "Lord please make me the
kind of person my dog thinks I am."



*From:*HamApps@yahoogroups.com.au [mailto:HamApps@yahoogroups.com.au]
*Sent:* Sunday, August 31, 2014 8:35 PM
*To:* HamApps@yahoogroups.com.au
*Subject:* [HamApps] Re:: Problem Running JT-Alert with WSJT-X 1.4





Thanks for your reply. Greg, KI7MT suggested this also. It seems to
have solved the problem.



Jim

--
73's
Greg, KI7MT


locked Re: : Problem Running JT-Alert with WSJT-X 1.4

Dan Malcolm <dmalcolm24@...>
 

OK because I am a developer, I installed the JTSDK-QT kits, and the SVN kit.  I got one sort of successful compile.  The build script reported success and pointed to the file location as “C:\JTSDK-QT\wsjtx\install\Release” plus a couple more directories that I’ve now lost track of and can’t find because the quoted path is all there is.  Subsequent builds now report an error and tells me to install OmniRig on my computer.  Ok I can do that, I am just puzzled why I got a success message on the first run and then the errors show up.

 

BTW.  I am just satisfying my curiousity with this.  I have no intention of doing any developing on WSJT et al.

 

____________________________

Dan Malcolm CFI/II

K4SHQ

 

The best prayer ever said: "Lord please make me the
kind of person my dog thinks I am."

 

From: HamApps@... [mailto:HamApps@...]
Sent: Sunday, August 31, 2014 8:35 PM
To: HamApps@...
Subject: [HamApps] Re:: Problem Running JT-Alert with WSJT-X 1.4

 

 

Thanks for your reply.  Greg, KI7MT suggested this also.  It seems to have solved the problem.

 

Jim


locked Re: : RE: Re:: Problem Running JT-Alert with WSJT-X 1.4

Michael Black
 

Are you running HRD?  There's a problem with running WSJT-X and HRD Logger or DM780 for example as they all try to use the HRD TCP port. And there's a bug with HRD that causes WSTX to lose data.

I'm working with Bill trying to fix this.  You need to say how you're hooked up to your radio and what radio.

And this software should be called "alpha" since it hasn't been release for general testing yet.

 

And are you saying you HAVE to set it zero or else you had this problem with WSTX-1.3?  Does 1.3 work OK and 1.4 doesn’t'?  Could you explain your issue a little clearer?

 

Mike W9MDB

 

From: HamApps@... [mailto:HamApps@...]
Sent: Monday, September 01, 2014 11:00 PM
To: HamApps@...
Subject: Re:: RE: [HamApps] Re:: Problem Running JT-Alert with WSJT-X 1.4

 

 

Bill,

 

I tried a copy of v1.4 I got from someone and found that the polling time could not be set to zero. With this, I would get an error that shut off each transmission when the radio would not respond to polling requests. As you said, this is a beta but I did not know if you all were aware of that issue.

 

Fred - KK5AA

EM25xh


locked Re: : RE: Re:: Problem Running JT-Alert with WSJT-X 1.4

kk5aa_fred
 

Bill,


I tried a copy of v1.4 I got from someone and found that the polling time could not be set to zero. With this, I would get an error that shut off each transmission when the radio would not respond to polling requests. As you said, this is a beta but I did not know if you all were aware of that issue.


Fred - KK5AA

EM25xh


locked Re: HamApps Database 14.09.01 Error

Laurie, VK3AMA <groups06@...>
 

Hi Tom,

I have been unable to reproduce this when installing or upgrading the databases on my Win8.1 test VM.

What was the Error number? Was it Error 1606?

Google shows many hits for the string "Could not access network location" displayed when installing a .msi package. It appears to be a Windows issue and is not limited to a specific Application. See this Microsoft KB 886549 for general details and a Fix-It utility that may or may-not help.

de Laurie VK3AMA
   

On 2/09/2014 1:04 AM, ve3ii@... [HamApps] wrote:


Good day...

I tried to install the updated database and I get an error saying "Could not access network location \".  I'm guessing thats the root of the hard drive but I'm no expert.  Retry fails (same message) and Cancel finishes without any update.

I have tried installing it from within JT-Alert without any luck.  I then closed JT-Alert, JT65-HF and JT-Macros,  downloaded the update file from the HamApps website and tried to install it alone but got the same error. 

Uisng Windows 8.1 with the latest version of JT-Alert. 

Any help would be great.  Thanks....Tom




locked Re: : RE: Re:: Problem Running JT-Alert with WSJT-X 1.4

g4wjs
 

There is no need to create any folders, they will be created by the application.

Note this is not an official release of any kind and doesn't come from an official installer which would present the licence for acceptance, create desktop icons, register an uninstaller and provide documentation links. I can say that Mike has proven to be capable of building the application for testing successfully and he is not publishing something that will infect your computer AFAIK.

Although any issue reports are of course welcome, no support is available for v1.4 until at least an official beta release is made.

We, the developers, are well aware that a replacement for WSJT-X v1.3 is eagerly awaited by many WSJT-X users, v1.4 as it stands is not deemed to be stable enough or complete enough to warrant a beta release just yet.

If you install this release then you are in the same place as any programmer who chooses to build and run the latest sources from the WSJT repository, i.e. if it breaks then you are expected to either fix it yourself or at least report the issue on the WSJT developer list so it can be addressed.

73
Bill
G4WJS.


locked Re: : RE: Re:: Problem Running JT-Alert with WSJT-X 1.4

ki7mt@...
 

Just FYI, 

The newer SVN versions store items in C:\User\%USERNAME%\%APPDATA%\Local\WSJT-X.

This folder contains, among other things, WSJTX.INI, .log, .adi and ..\save\samples 

You may need to create the paths \ folders  for WSJT-X to write too. I've not tried simply transferring a pre-built app directory, it may work out of the box, but just in case.


73's
Greg, KI7MT

---In HamApps@..., <mdblack98@...> wrote :

Here's the most recent version as of today for Windows.  I'm using it with JT-Alert successfully.

I can't guarantee anything of course but it works for me on Windows 7 32-bit

https://www.dropbox.com/s/0wiemr0e3304d6a/wsjtx-1.4.4239..zip?dl=0

 

There's a "bin" and "lib" directory in this zipfile so you need to extract it to another folder.

 

 

From: HamApps@... [mailto:HamApps@...]
Sent: Monday, September 01, 2014 10:26 AM
To: HamApps@...
Subject: [HamApps] Re:: Problem Running JT-Alert with WSJT-X 1.4

 

 

Indeed, where is v1.4 ? Is'nt this available in a form where the user does'nt have to or is unable to compile it himself ?

Jeff M1BCM