date:20160507

Re: [wsjt-devel] wsjt

2016-05-07 Thread Michael Durkin

k ... found v1.7 ... sigh... building

On Sat, May 7, 2016 at 5:19 PM, Michael Durkin  wrote:

> Ha  i was wrong  i can build   
>
> so, i thought latest does not need KVSAD decoder?
>
>
>
> On Sat, May 7, 2016 at 2:27 PM, Michael Durkin  wrote:
>
>> found the problem,but theres nothing i can do about it 
>>
>> libgles2-mesa-dev conflicts with mali video drivers and untill the messa
>> headder gets updated  im stuck .
>>
>> On Sat, May 7, 2016 at 9:32 AM, Michael Durkin  wrote:
>>
>>> Well ... i did not .. but did this morning 
>>> Dang ... i thought i was a bit more up to date on my packages ... but
>>> 1.3G of new packages ;)
>>>
>>> jtsdk seems to be running fine ... building wsjtx-exp ... by accident
>>> (kinda) .. didint mean to make a tarbal but once its done i guess i could
>>> share it with other SBC Odroid-C2 users out there  if all goes well ...
>>>
>>> I think a addition to the help files that are used within jtsdk. Like a
>>> "(RC = type of build)"
>>>
>>> I don't know what the differences are and a real short addition to the
>>> help file would be nice ..
>>>
>>> Id guess this afternoon ill have a working wsjtx . ill still need to
>>> get a loop-sink working ... ie snd-aloop i think is what its called ...
>>>
>>> I can Rx with wsjtx, I know that even before its build ... the monitor
>>> of my SDR speaker output is easy  Tx is another thing  i dont ever
>>> remember seeing a "monitor" option of the microphone (soundcard input) that
>>> the SDR uses that wsjtx could be pointed to.
>>>
>>> I usally use hamlib #2 with a port id  to controll Rx/Tx and
>>> frequency .
>>>
>>> looking forward to working VHF/UHF from my location . DN17jo
>>>
>>> On Fri, May 6, 2016 at 11:12 PM, T61AA Ross  wrote:
>>>
 Mike,

 There is a file listing all file dependencies that JTSDK needs, did you
 open this file and just do a copy and paste of and including "sudo apt-get
 install .."
 File is called README.pkg-lists

 73

 Ross

 Sent from my iPhone 6

 On 7 May 2016, at 05:22, Michael Durkin  wrote:

 jtsdk-nix did build and install 

 with 2 cavets ...

 must be exstracted to /home/

 and

 renamed to jtsdk

 now ... first error when installing might be a missing package ... not
 sure.
 oh .. i was using jtsdk to build hamlib3

 make[1]: Entering directory '/home/kc7noa/jtsdk/src/build/hamlib/doc'
 Updating /home/kc7noa/jtsdk/src/g4wjs-hamlib/doc/version.texi
   MAKEINFO /home/kc7noa/jtsdk/src/g4wjs-hamlib/doc/hamlib.info
   MAKEINFO hamlib.html
 /home/kc7noa/jtsdk/src/g4wjs-hamlib/build-aux/missing: line 81:
 makeinfo: command not found
 /home/kc7noa/jtsdk/src/g4wjs-hamlib/build-aux/missing: line 81:
 makeinfo: command not found
 WARNING: 'makeinfo' is missing on your system.
  You should only need it if you modified a '.texi' file, or
  any other file indirectly affecting the aspect of the manual.
  You might want to install the Texinfo package:
  
  The spurious makeinfo call might also be the consequence of
  using a buggy 'make' (AIX, DU, IRIX), in which case you might
  want to install GNU make:
  
 WARNING: 'makeinfo' is missing on your system.
  You should only need it if you modified a '.texi' file, or
  any other file indirectly affecting the aspect of the manual.
  You might want to install the Texinfo package:
  
  The spurious makeinfo call might also be the consequence of
  using a buggy 'make' (AIX, DU, IRIX), in which case you might
  want to install GNU make:
  
 Makefile:485: recipe for target 'hamlib.html' failed
 make[1]: *** [hamlib.html] Error 1
 make[1]: *** Waiting for unfinished jobs
 Makefile:451: recipe for target
 '/home/kc7noa/jtsdk/src/g4wjs-hamlib/doc/hamlib.info' failed
 make[1]: *** [/home/kc7noa/jtsdk/src/g4wjs-hamlib/doc/hamlib.info]
 Error 127
 make[1]: Leaving directory '/home/kc7noa/jtsdk/src/build/hamlib/doc'
 Makefile:564: recipe for target 'all-recursive' failed
 make: *** [all-recursive] Error 1
 kc7noa@odroid64:~/jtsdk-nix$



 kc7noa@odroid64:~/jtsdk-nix$ sudo apt-get install textinfo
 [sudo] password for kc7noa:
 Reading package lists... Done
 Building dependency tree
 Reading state information... Done
 E: Unable to locate package textinfo
 kc7noa@odroid64:~/jtsdk-nix$


 On Fri, May 6, 2016 at 9:17 PM, T61AA Ross  wrote:

> I might also add I'm running JTSDK and WSJTX 1.7.0 r6674 on another
> Linux 14.04 and two Win 1

Re: [wsjt-devel] wsjt

2016-05-07 Thread Michael Durkin

Ha  i was wrong  i can build   

so, i thought latest does not need KVSAD decoder?



On Sat, May 7, 2016 at 2:27 PM, Michael Durkin  wrote:

> found the problem,but theres nothing i can do about it 
>
> libgles2-mesa-dev conflicts with mali video drivers and untill the messa
> headder gets updated  im stuck .
>
> On Sat, May 7, 2016 at 9:32 AM, Michael Durkin  wrote:
>
>> Well ... i did not .. but did this morning 
>> Dang ... i thought i was a bit more up to date on my packages ... but
>> 1.3G of new packages ;)
>>
>> jtsdk seems to be running fine ... building wsjtx-exp ... by accident
>> (kinda) .. didint mean to make a tarbal but once its done i guess i could
>> share it with other SBC Odroid-C2 users out there  if all goes well ...
>>
>> I think a addition to the help files that are used within jtsdk. Like a
>> "(RC = type of build)"
>>
>> I don't know what the differences are and a real short addition to the
>> help file would be nice ..
>>
>> Id guess this afternoon ill have a working wsjtx . ill still need to
>> get a loop-sink working ... ie snd-aloop i think is what its called ...
>>
>> I can Rx with wsjtx, I know that even before its build ... the monitor of
>> my SDR speaker output is easy  Tx is another thing  i dont ever
>> remember seeing a "monitor" option of the microphone (soundcard input) that
>> the SDR uses that wsjtx could be pointed to.
>>
>> I usally use hamlib #2 with a port id  to controll Rx/Tx and
>> frequency .
>>
>> looking forward to working VHF/UHF from my location . DN17jo
>>
>> On Fri, May 6, 2016 at 11:12 PM, T61AA Ross  wrote:
>>
>>> Mike,
>>>
>>> There is a file listing all file dependencies that JTSDK needs, did you
>>> open this file and just do a copy and paste of and including "sudo apt-get
>>> install .."
>>> File is called README.pkg-lists
>>>
>>> 73
>>>
>>> Ross
>>>
>>> Sent from my iPhone 6
>>>
>>> On 7 May 2016, at 05:22, Michael Durkin  wrote:
>>>
>>> jtsdk-nix did build and install 
>>>
>>> with 2 cavets ...
>>>
>>> must be exstracted to /home/
>>>
>>> and
>>>
>>> renamed to jtsdk
>>>
>>> now ... first error when installing might be a missing package ... not
>>> sure.
>>> oh .. i was using jtsdk to build hamlib3
>>>
>>> make[1]: Entering directory '/home/kc7noa/jtsdk/src/build/hamlib/doc'
>>> Updating /home/kc7noa/jtsdk/src/g4wjs-hamlib/doc/version.texi
>>>   MAKEINFO /home/kc7noa/jtsdk/src/g4wjs-hamlib/doc/hamlib.info
>>>   MAKEINFO hamlib.html
>>> /home/kc7noa/jtsdk/src/g4wjs-hamlib/build-aux/missing: line 81:
>>> makeinfo: command not found
>>> /home/kc7noa/jtsdk/src/g4wjs-hamlib/build-aux/missing: line 81:
>>> makeinfo: command not found
>>> WARNING: 'makeinfo' is missing on your system.
>>>  You should only need it if you modified a '.texi' file, or
>>>  any other file indirectly affecting the aspect of the manual.
>>>  You might want to install the Texinfo package:
>>>  
>>>  The spurious makeinfo call might also be the consequence of
>>>  using a buggy 'make' (AIX, DU, IRIX), in which case you might
>>>  want to install GNU make:
>>>  
>>> WARNING: 'makeinfo' is missing on your system.
>>>  You should only need it if you modified a '.texi' file, or
>>>  any other file indirectly affecting the aspect of the manual.
>>>  You might want to install the Texinfo package:
>>>  
>>>  The spurious makeinfo call might also be the consequence of
>>>  using a buggy 'make' (AIX, DU, IRIX), in which case you might
>>>  want to install GNU make:
>>>  
>>> Makefile:485: recipe for target 'hamlib.html' failed
>>> make[1]: *** [hamlib.html] Error 1
>>> make[1]: *** Waiting for unfinished jobs
>>> Makefile:451: recipe for target '/home/kc7noa/jtsdk/src/g4wjs-hamlib/doc/
>>> hamlib.info' failed
>>> make[1]: *** [/home/kc7noa/jtsdk/src/g4wjs-hamlib/doc/hamlib.info]
>>> Error 127
>>> make[1]: Leaving directory '/home/kc7noa/jtsdk/src/build/hamlib/doc'
>>> Makefile:564: recipe for target 'all-recursive' failed
>>> make: *** [all-recursive] Error 1
>>> kc7noa@odroid64:~/jtsdk-nix$
>>>
>>>
>>>
>>> kc7noa@odroid64:~/jtsdk-nix$ sudo apt-get install textinfo
>>> [sudo] password for kc7noa:
>>> Reading package lists... Done
>>> Building dependency tree
>>> Reading state information... Done
>>> E: Unable to locate package textinfo
>>> kc7noa@odroid64:~/jtsdk-nix$
>>>
>>>
>>> On Fri, May 6, 2016 at 9:17 PM, T61AA Ross  wrote:
>>>
 I might also add I'm running JTSDK and WSJTX 1.7.0 r6674 on another
 Linux 14.04 and two Win 10 machines as well without issue.

 Sent from my iPhone 6

 > On 7 May 2016, at 01:17, T61AA Ross  wrote:
 >
 > I'm also running JTSDK and compiling and running WSJTX on a
 RaspberryPi B3 without

Re: [wsjt-devel] wsjt

2016-05-07 Thread Michael Durkin

found the problem,but theres nothing i can do about it 

libgles2-mesa-dev conflicts with mali video drivers and untill the messa
headder gets updated  im stuck .

On Sat, May 7, 2016 at 9:32 AM, Michael Durkin  wrote:

> Well ... i did not .. but did this morning 
> Dang ... i thought i was a bit more up to date on my packages ... but 1.3G
> of new packages ;)
>
> jtsdk seems to be running fine ... building wsjtx-exp ... by accident
> (kinda) .. didint mean to make a tarbal but once its done i guess i could
> share it with other SBC Odroid-C2 users out there  if all goes well ...
>
> I think a addition to the help files that are used within jtsdk. Like a
> "(RC = type of build)"
>
> I don't know what the differences are and a real short addition to the
> help file would be nice ..
>
> Id guess this afternoon ill have a working wsjtx . ill still need to
> get a loop-sink working ... ie snd-aloop i think is what its called ...
>
> I can Rx with wsjtx, I know that even before its build ... the monitor of
> my SDR speaker output is easy  Tx is another thing  i dont ever
> remember seeing a "monitor" option of the microphone (soundcard input) that
> the SDR uses that wsjtx could be pointed to.
>
> I usally use hamlib #2 with a port id  to controll Rx/Tx and frequency
> .
>
> looking forward to working VHF/UHF from my location . DN17jo
>
> On Fri, May 6, 2016 at 11:12 PM, T61AA Ross  wrote:
>
>> Mike,
>>
>> There is a file listing all file dependencies that JTSDK needs, did you
>> open this file and just do a copy and paste of and including "sudo apt-get
>> install .."
>> File is called README.pkg-lists
>>
>> 73
>>
>> Ross
>>
>> Sent from my iPhone 6
>>
>> On 7 May 2016, at 05:22, Michael Durkin  wrote:
>>
>> jtsdk-nix did build and install 
>>
>> with 2 cavets ...
>>
>> must be exstracted to /home/
>>
>> and
>>
>> renamed to jtsdk
>>
>> now ... first error when installing might be a missing package ... not
>> sure.
>> oh .. i was using jtsdk to build hamlib3
>>
>> make[1]: Entering directory '/home/kc7noa/jtsdk/src/build/hamlib/doc'
>> Updating /home/kc7noa/jtsdk/src/g4wjs-hamlib/doc/version.texi
>>   MAKEINFO /home/kc7noa/jtsdk/src/g4wjs-hamlib/doc/hamlib.info
>>   MAKEINFO hamlib.html
>> /home/kc7noa/jtsdk/src/g4wjs-hamlib/build-aux/missing: line 81: makeinfo:
>> command not found
>> /home/kc7noa/jtsdk/src/g4wjs-hamlib/build-aux/missing: line 81: makeinfo:
>> command not found
>> WARNING: 'makeinfo' is missing on your system.
>>  You should only need it if you modified a '.texi' file, or
>>  any other file indirectly affecting the aspect of the manual.
>>  You might want to install the Texinfo package:
>>  
>>  The spurious makeinfo call might also be the consequence of
>>  using a buggy 'make' (AIX, DU, IRIX), in which case you might
>>  want to install GNU make:
>>  
>> WARNING: 'makeinfo' is missing on your system.
>>  You should only need it if you modified a '.texi' file, or
>>  any other file indirectly affecting the aspect of the manual.
>>  You might want to install the Texinfo package:
>>  
>>  The spurious makeinfo call might also be the consequence of
>>  using a buggy 'make' (AIX, DU, IRIX), in which case you might
>>  want to install GNU make:
>>  
>> Makefile:485: recipe for target 'hamlib.html' failed
>> make[1]: *** [hamlib.html] Error 1
>> make[1]: *** Waiting for unfinished jobs
>> Makefile:451: recipe for target '/home/kc7noa/jtsdk/src/g4wjs-hamlib/doc/
>> hamlib.info' failed
>> make[1]: *** [/home/kc7noa/jtsdk/src/g4wjs-hamlib/doc/hamlib.info] Error
>> 127
>> make[1]: Leaving directory '/home/kc7noa/jtsdk/src/build/hamlib/doc'
>> Makefile:564: recipe for target 'all-recursive' failed
>> make: *** [all-recursive] Error 1
>> kc7noa@odroid64:~/jtsdk-nix$
>>
>>
>>
>> kc7noa@odroid64:~/jtsdk-nix$ sudo apt-get install textinfo
>> [sudo] password for kc7noa:
>> Reading package lists... Done
>> Building dependency tree
>> Reading state information... Done
>> E: Unable to locate package textinfo
>> kc7noa@odroid64:~/jtsdk-nix$
>>
>>
>> On Fri, May 6, 2016 at 9:17 PM, T61AA Ross  wrote:
>>
>>> I might also add I'm running JTSDK and WSJTX 1.7.0 r6674 on another
>>> Linux 14.04 and two Win 10 machines as well without issue.
>>>
>>> Sent from my iPhone 6
>>>
>>> > On 7 May 2016, at 01:17, T61AA Ross  wrote:
>>> >
>>> > I'm also running JTSDK and compiling and running WSJTX on a
>>> RaspberryPi B3 without issues on Ubuntu 16.04
>>> >
>>> > Sent from my iPhone 6
>>> >
>>> >> On 7 May 2016, at 00:52, KI7MT  wrote:
>>> >>
>>> >> Hi Michael,
>>> >>
>>> >> Can you expand a bit on the permission error; where and how does it
>>> >> manifest?
>>> >>
>>> >> I tested JTSDK v2.0.19 on an ARMHF

Re: [wsjt-devel] wsjt

2016-05-07 Thread Michael Durkin

Well ... i did not .. but did this morning 
Dang ... i thought i was a bit more up to date on my packages ... but 1.3G
of new packages ;)

jtsdk seems to be running fine ... building wsjtx-exp ... by accident
(kinda) .. didint mean to make a tarbal but once its done i guess i could
share it with other SBC Odroid-C2 users out there  if all goes well ...

I think a addition to the help files that are used within jtsdk. Like a
"(RC = type of build)"

I don't know what the differences are and a real short addition to the help
file would be nice ..

Id guess this afternoon ill have a working wsjtx . ill still need to
get a loop-sink working ... ie snd-aloop i think is what its called ...

I can Rx with wsjtx, I know that even before its build ... the monitor of
my SDR speaker output is easy  Tx is another thing  i dont ever
remember seeing a "monitor" option of the microphone (soundcard input) that
the SDR uses that wsjtx could be pointed to.

I usally use hamlib #2 with a port id  to controll Rx/Tx and frequency
.

looking forward to working VHF/UHF from my location . DN17jo

On Fri, May 6, 2016 at 11:12 PM, T61AA Ross  wrote:

> Mike,
>
> There is a file listing all file dependencies that JTSDK needs, did you
> open this file and just do a copy and paste of and including "sudo apt-get
> install .."
> File is called README.pkg-lists
>
> 73
>
> Ross
>
> Sent from my iPhone 6
>
> On 7 May 2016, at 05:22, Michael Durkin  wrote:
>
> jtsdk-nix did build and install 
>
> with 2 cavets ...
>
> must be exstracted to /home/
>
> and
>
> renamed to jtsdk
>
> now ... first error when installing might be a missing package ... not
> sure.
> oh .. i was using jtsdk to build hamlib3
>
> make[1]: Entering directory '/home/kc7noa/jtsdk/src/build/hamlib/doc'
> Updating /home/kc7noa/jtsdk/src/g4wjs-hamlib/doc/version.texi
>   MAKEINFO /home/kc7noa/jtsdk/src/g4wjs-hamlib/doc/hamlib.info
>   MAKEINFO hamlib.html
> /home/kc7noa/jtsdk/src/g4wjs-hamlib/build-aux/missing: line 81: makeinfo:
> command not found
> /home/kc7noa/jtsdk/src/g4wjs-hamlib/build-aux/missing: line 81: makeinfo:
> command not found
> WARNING: 'makeinfo' is missing on your system.
>  You should only need it if you modified a '.texi' file, or
>  any other file indirectly affecting the aspect of the manual.
>  You might want to install the Texinfo package:
>  
>  The spurious makeinfo call might also be the consequence of
>  using a buggy 'make' (AIX, DU, IRIX), in which case you might
>  want to install GNU make:
>  
> WARNING: 'makeinfo' is missing on your system.
>  You should only need it if you modified a '.texi' file, or
>  any other file indirectly affecting the aspect of the manual.
>  You might want to install the Texinfo package:
>  
>  The spurious makeinfo call might also be the consequence of
>  using a buggy 'make' (AIX, DU, IRIX), in which case you might
>  want to install GNU make:
>  
> Makefile:485: recipe for target 'hamlib.html' failed
> make[1]: *** [hamlib.html] Error 1
> make[1]: *** Waiting for unfinished jobs
> Makefile:451: recipe for target '/home/kc7noa/jtsdk/src/g4wjs-hamlib/doc/
> hamlib.info' failed
> make[1]: *** [/home/kc7noa/jtsdk/src/g4wjs-hamlib/doc/hamlib.info] Error
> 127
> make[1]: Leaving directory '/home/kc7noa/jtsdk/src/build/hamlib/doc'
> Makefile:564: recipe for target 'all-recursive' failed
> make: *** [all-recursive] Error 1
> kc7noa@odroid64:~/jtsdk-nix$
>
>
>
> kc7noa@odroid64:~/jtsdk-nix$ sudo apt-get install textinfo
> [sudo] password for kc7noa:
> Reading package lists... Done
> Building dependency tree
> Reading state information... Done
> E: Unable to locate package textinfo
> kc7noa@odroid64:~/jtsdk-nix$
>
>
> On Fri, May 6, 2016 at 9:17 PM, T61AA Ross  wrote:
>
>> I might also add I'm running JTSDK and WSJTX 1.7.0 r6674 on another Linux
>> 14.04 and two Win 10 machines as well without issue.
>>
>> Sent from my iPhone 6
>>
>> > On 7 May 2016, at 01:17, T61AA Ross  wrote:
>> >
>> > I'm also running JTSDK and compiling and running WSJTX on a RaspberryPi
>> B3 without issues on Ubuntu 16.04
>> >
>> > Sent from my iPhone 6
>> >
>> >> On 7 May 2016, at 00:52, KI7MT  wrote:
>> >>
>> >> Hi Michael,
>> >>
>> >> Can you expand a bit on the permission error; where and how does it
>> >> manifest?
>> >>
>> >> I tested JTSDK v2.0.19 on an ARMHF device (RPI2 Quad core) using
>> >> Ubuntu-Mate 15.04 and did not hit any permission problems.
>> >>
>> >> All the apps JTSDK can build worked as expected, but on a busy band
>> (20m
>> >> JT65 + JT9) sometimes the decodes would go into the next cycle. It may
>> >> have been my setup with dual pass and other advanced feature setting
>> >> causing the slowness, not sure.
>>

Re: [wsjt-devel] WSJT-X for eme?

2016-05-07 Thread Bill Somerville


On 07/05/2016 16:45, Mark Turner (EI3KD) wrote:

I think we're talking at cross-purposes Bill - the "issue" described in
the second paragraph (that of the default auto-generated messages being
different for JT65 in WSJT-X vs WSJT) has nothing to do with the first
paragraph, and nothing to do with short codes? I'm confused now:)


Hi Mark,

Yes, you are correct. I was confusing OOO messages with short codes. I 
hope I have the following correct having briefly scanned the WSJT code.


The way OOO messages are encoded uses no message bits for the "report" 
and allows type 1 or type 2 compound callsigns to be used, that is not 
possible with dB style reports where the bits used to include the report 
do not leave enough for compound callsigns to be encoded. So in answer 
to your question "will WSJT-X support OOO messages" the answer is yes 
and implementing them will allow compound callsigns to be used in those 
messages.


I believe Joe is currently doing just that but I do not expect to be 
completed for while as other priorities prevail.


73
Bill
G4WJS.

--
Find and fix application performance issues faster with Applications Manager
Applications Manager provides deep performance insights into multiple tiers of
your business applications. It resolves application problems quickly and
reduces your MTTR. Get your free trial!
https://ad.doubleclick.net/ddm/clk/302982198;130105516;z___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] WSJT-X for eme?

2016-05-07 Thread Mark Turner (EI3KD)

I think we're talking at cross-purposes Bill - the "issue" described in 
the second paragraph (that of the default auto-generated messages being 
different for JT65 in WSJT-X vs WSJT) has nothing to do with the first 
paragraph, and nothing to do with short codes? I'm confused now :)

Regards, Mark


On 07/05/2016 15:03, Bill Somerville wrote:
> Hi Mark,
>
> comments in line below.
>
> On 07/05/2016 14:58, Mark Turner (EI3KD) wrote:
>> lots snipped, but the clip below what was I was looking for; so my
>> understanding is that it will be possible to auto-generate the "RO",
>> "RRR", "73" short-code messages instead of reports+signal strengths,
>> etc, for Tx3/4/5 in WSJT-X for EME, if we choose?
> Yes.
>> I do understand about the prefixes, although this isn't how WSJT (any
>> version) works for JT65 right now with the European default message
>> templates. As it stands, WSJT generates (for example) a Tx2 of
>> "EA6/PA2CHR EI3KD OOO", and WSJT-X generates "PA2CHR EI3KD -21" (or
>> whatever the report is), with "EA6/PA2CHR" entered in the DX Call textbox.
> The short code messages do not actually contain the callsigns, what is
> printed at both ends is inferred from previous parts of the exchange.
>
> 73
> Bill
> G4WJS.
>

--
Find and fix application performance issues faster with Applications Manager
Applications Manager provides deep performance insights into multiple tiers of
your business applications. It resolves application problems quickly and
reduces your MTTR. Get your free trial!
https://ad.doubleclick.net/ddm/clk/302982198;130105516;z
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] wsjt

2016-05-07 Thread KI7MT

Hi Michael,

Here's the release notes for JTSDK v2.0.19:

https://sourceforge.net/projects/jtsdk/files/linux/2.0.0/documentation/release-notes/jtsdk-nix-2.0.19.html/download

Section 6 outlines installation methods either via PPA (which would have
been much easier) or from source.


73's
Greg, KI7MT

On 05/06/2016 11:22 PM, Michael Durkin wrote:
> jtsdk-nix did build and install 
> 
> with 2 cavets ...
> 
> must be exstracted to /home/
> 
> and
> 
> renamed to jtsdk
> 
> now ... first error when installing might be a missing package ... not sure.
> oh .. i was using jtsdk to build hamlib3
> 
> make[1]: Entering directory '/home/kc7noa/jtsdk/src/build/hamlib/doc'
> Updating /home/kc7noa/jtsdk/src/g4wjs-hamlib/doc/version.texi
>   MAKEINFO /home/kc7noa/jtsdk/src/g4wjs-hamlib/doc/hamlib.info
>   MAKEINFO hamlib.html
> /home/kc7noa/jtsdk/src/g4wjs-hamlib/build-aux/missing: line 81: makeinfo:
> command not found
> /home/kc7noa/jtsdk/src/g4wjs-hamlib/build-aux/missing: line 81: makeinfo:
> command not found
> WARNING: 'makeinfo' is missing on your system.
>  You should only need it if you modified a '.texi' file, or
>  any other file indirectly affecting the aspect of the manual.
>  You might want to install the Texinfo package:
>  
>  The spurious makeinfo call might also be the consequence of
>  using a buggy 'make' (AIX, DU, IRIX), in which case you might
>  want to install GNU make:
>  
> WARNING: 'makeinfo' is missing on your system.
>  You should only need it if you modified a '.texi' file, or
>  any other file indirectly affecting the aspect of the manual.
>  You might want to install the Texinfo package:
>  
>  The spurious makeinfo call might also be the consequence of
>  using a buggy 'make' (AIX, DU, IRIX), in which case you might
>  want to install GNU make:
>  
> Makefile:485: recipe for target 'hamlib.html' failed
> make[1]: *** [hamlib.html] Error 1
> make[1]: *** Waiting for unfinished jobs
> Makefile:451: recipe for target '/home/kc7noa/jtsdk/src/g4wjs-hamlib/doc/
> hamlib.info' failed
> make[1]: *** [/home/kc7noa/jtsdk/src/g4wjs-hamlib/doc/hamlib.info] Error 127
> make[1]: Leaving directory '/home/kc7noa/jtsdk/src/build/hamlib/doc'
> Makefile:564: recipe for target 'all-recursive' failed
> make: *** [all-recursive] Error 1
> kc7noa@odroid64:~/jtsdk-nix$
> 
> 
> 
> kc7noa@odroid64:~/jtsdk-nix$ sudo apt-get install textinfo
> [sudo] password for kc7noa:
> Reading package lists... Done
> Building dependency tree
> Reading state information... Done
> E: Unable to locate package textinfo
> kc7noa@odroid64:~/jtsdk-nix$
> 
> 
> On Fri, May 6, 2016 at 9:17 PM, T61AA Ross  wrote:
> 
>> I might also add I'm running JTSDK and WSJTX 1.7.0 r6674 on another Linux
>> 14.04 and two Win 10 machines as well without issue.
>>
>> Sent from my iPhone 6
>>
>>> On 7 May 2016, at 01:17, T61AA Ross  wrote:
>>>
>>> I'm also running JTSDK and compiling and running WSJTX on a RaspberryPi
>> B3 without issues on Ubuntu 16.04
>>>
>>> Sent from my iPhone 6
>>>
 On 7 May 2016, at 00:52, KI7MT  wrote:

 Hi Michael,

 Can you expand a bit on the permission error; where and how does it
 manifest?

 I tested JTSDK v2.0.19 on an ARMHF device (RPI2 Quad core) using
 Ubuntu-Mate 15.04 and did not hit any permission problems.

 All the apps JTSDK can build worked as expected, but on a busy band (20m
 JT65 + JT9) sometimes the decodes would go into the next cycle. It may
 have been my setup with dual pass and other advanced feature setting
 causing the slowness, not sure.

 73's
 Greg, KI7MT

>> On 05/06/2016 05:46 PM, Michael Durkin wrote:
>> I always got permission errors with the jtsdk ... least on the SBC
>> arm ...
>> On May 6, 2016 4:43 PM, "T61AA Ross"  wrote:
>>
>> Hi Bill and Mike,
>>
>> JTSDK will install all needed packages, you can also use synaptic to
>> see
>> what dependencies are needed.
>>
>> 73
>>
>> Ross
>> VN1UN/VK8UN/T61AA/6O0O
>> Sent from my iPhone 6
>>
 On 6 May 2016, at 23:09, Bill Somerville 
>> wrote:

 On 06/05/2016 23:45, Michael Durkin wrote:
 darn   cmake cant find Qt5Widgets  hummm
>>>
>>> Hi Michael,
>>>
>>> there are a few Qt5 packages you need to install, try:
>>>
>>> $ sudo apt-get install qtmultimedia5-dev liqt5serialport5-dev
>>> libqt5multimedia5-plugins libusb-dev libudev-dev
>>>
>>> 73
>>> Bill
>>> G4WJS
>>
>> --
>>> Find and fix application performance issues faster with Applications
>> Manager
>>> Applications Manager

Re: [wsjt-devel] rev 6674 - Lock TX/RX

2016-05-07 Thread f5jmh

Ah ok! Many thank's Bill I unchecked this option. Bye

73 Alain

- Mail original -
De: "Bill Somerville" 
À: wsjt-devel@lists.sourceforge.net
Envoyé: Samedi 7 Mai 2016 14:44:39
Objet: Re: [wsjt-devel] rev 6674 - Lock TX/RX

On 07/05/2016 12:46, f5...@free.fr wrote:
> I tested rev 6674 ver 1.7.0 on Ubuntu 14.04 LTS. Lock TX=RX checkbox and TX 
> listbox are disabled, both are grayed out and not operational. Is this normal 
> ?

Hi Alain,

that is normal if you have checked the "Enable VHF/UHF/Microwave 
features" option. On VHF and above the Tx audio offset is fixed at 1000Hz.

73
Bill
G4WJS.


--
Find and fix application performance issues faster with Applications Manager
Applications Manager provides deep performance insights into multiple tiers of
your business applications. It resolves application problems quickly and
reduces your MTTR. Get your free trial!
https://ad.doubleclick.net/ddm/clk/302982198;130105516;z
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

--
Find and fix application performance issues faster with Applications Manager
Applications Manager provides deep performance insights into multiple tiers of
your business applications. It resolves application problems quickly and
reduces your MTTR. Get your free trial!
https://ad.doubleclick.net/ddm/clk/302982198;130105516;z
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] WSJT-X for eme?

2016-05-07 Thread Bill Somerville

Hi Mark,

comments in line below.

On 07/05/2016 14:58, Mark Turner (EI3KD) wrote:
> lots snipped, but the clip below what was I was looking for; so my
> understanding is that it will be possible to auto-generate the "RO",
> "RRR", "73" short-code messages instead of reports+signal strengths,
> etc, for Tx3/4/5 in WSJT-X for EME, if we choose?
Yes.
>
> I do understand about the prefixes, although this isn't how WSJT (any
> version) works for JT65 right now with the European default message
> templates. As it stands, WSJT generates (for example) a Tx2 of
> "EA6/PA2CHR EI3KD OOO", and WSJT-X generates "PA2CHR EI3KD -21" (or
> whatever the report is), with "EA6/PA2CHR" entered in the DX Call textbox.

The short code messages do not actually contain the callsigns, what is 
printed at both ends is inferred from previous parts of the exchange.

73
Bill
G4WJS.


--
Find and fix application performance issues faster with Applications Manager
Applications Manager provides deep performance insights into multiple tiers of
your business applications. It resolves application problems quickly and
reduces your MTTR. Get your free trial!
https://ad.doubleclick.net/ddm/clk/302982198;130105516;z
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] WSJT-X for eme?

2016-05-07 Thread Mark Turner (EI3KD)

Thanks Bill,

lots snipped, but the clip below what was I was looking for; so my 
understanding is that it will be possible to auto-generate the "RO", 
"RRR", "73" short-code messages instead of reports+signal strengths, 
etc, for Tx3/4/5 in WSJT-X for EME, if we choose?

I do understand about the prefixes, although this isn't how WSJT (any 
version) works for JT65 right now with the European default message 
templates. As it stands, WSJT generates (for example) a Tx2 of 
"EA6/PA2CHR EI3KD OOO", and WSJT-X generates "PA2CHR EI3KD -21" (or 
whatever the report is), with "EA6/PA2CHR" entered in the DX Call textbox.

Anyway, I'm sure you guys have it all under control :)

Regards, Mark

On 07/05/2016 10:25, Bill Somerville wrote:
> Short code messages are being implemented for the JT65 mode, JT4 already
> has these in WSJT-X. These allow QSOs in one to one sked situations to
> be completed in the most marginal of conditions.

--
Find and fix application performance issues faster with Applications Manager
Applications Manager provides deep performance insights into multiple tiers of
your business applications. It resolves application problems quickly and
reduces your MTTR. Get your free trial!
https://ad.doubleclick.net/ddm/clk/302982198;130105516;z
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] rev 6674 - Lock TX/RX

2016-05-07 Thread Bill Somerville

On 07/05/2016 12:46, f5...@free.fr wrote:
> I tested rev 6674 ver 1.7.0 on Ubuntu 14.04 LTS. Lock TX=RX checkbox and TX 
> listbox are disabled, both are grayed out and not operational. Is this normal 
> ?

Hi Alain,

that is normal if you have checked the "Enable VHF/UHF/Microwave 
features" option. On VHF and above the Tx audio offset is fixed at 1000Hz.

73
Bill
G4WJS.


--
Find and fix application performance issues faster with Applications Manager
Applications Manager provides deep performance insights into multiple tiers of
your business applications. It resolves application problems quickly and
reduces your MTTR. Get your free trial!
https://ad.doubleclick.net/ddm/clk/302982198;130105516;z
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

[wsjt-devel] rev 6674 - Lock TX/RX

2016-05-07 Thread f5jmh

Hello

I tested rev 6674 ver 1.7.0 on Ubuntu 14.04 LTS. Lock TX=RX checkbox and TX 
listbox are disabled, both are grayed out and not operational. Is this normal ?

Many thank's

73 Alain
F5JMH 

--
Find and fix application performance issues faster with Applications Manager
Applications Manager provides deep performance insights into multiple tiers of
your business applications. It resolves application problems quickly and
reduces your MTTR. Get your free trial!
https://ad.doubleclick.net/ddm/clk/302982198;130105516;z
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] WSJT-X 1.7 r6674 UDP decode message leading space

2016-05-07 Thread f5jmh

Hello all

Many thank's for this information, i have a same problem with AlarmeJT. So I 
expect the next version of WSJT-X.

73 Alain
F5JMH


- Mail original -
De: "Bill Somerville" 
À: wsjt-devel@lists.sourceforge.net
Envoyé: Samedi 7 Mai 2016 02:17:11
Objet: Re: [wsjt-devel] WSJT-X 1.7 r6674 UDP decode message leading space

On 07/05/2016 00:59, Laurie VK3AMA wrote:
> Testing WSJT-X 1.7 r6674 here.
> The UDP decode packet has a space appended to the start of the decode 
> message.
> Is this a defect or by design?

Hi Laurie,

it is a defect. Several issues have arisen after adding a second 
character to the mode indicator ('#', '@' or '$') to indicate sync flips 
when using message averaging on VHF & up. I am working through testing 
all the modes and resolving these issues. The offset message text is 
collateral damage that will be sorted when I check in my changes. Once 
that is done the UDP messages will be exactly as before for HF decodes.

73
Bill
G4WJS.


--
Find and fix application performance issues faster with Applications Manager
Applications Manager provides deep performance insights into multiple tiers of
your business applications. It resolves application problems quickly and
reduces your MTTR. Get your free trial!
https://ad.doubleclick.net/ddm/clk/302982198;130105516;z
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

--
Find and fix application performance issues faster with Applications Manager
Applications Manager provides deep performance insights into multiple tiers of
your business applications. It resolves application problems quickly and
reduces your MTTR. Get your free trial!
https://ad.doubleclick.net/ddm/clk/302982198;130105516;z
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] WSJT-X for eme?

2016-05-07 Thread Charles Suckling

Hi Bill

If I remember right, the initial message for type 1 calls has no locator -
this is how it is working now in the current  development version if I enter
a type 1 call in the DX call box.

Auto message generation strips off the prefix in the remaining messages
since the DS decoder only works with the base callsign.  I think this gets
round the problem I had when operating as HA/G3WDG when other stations were
sending me reports that included the  in my call and DS did not then work.

73

Charlie

-Original Message-
From: Bill Somerville [mailto:g4...@classdesign.com] 
Sent: 07 May 2016 10:26
To: wsjt-devel@lists.sourceforge.net
Subject: Re: [wsjt-devel] WSJT-X for eme?

On 07/05/2016 08:39, Mark Turner (EI3KD) wrote:
> is it intended that the next incarnation of WSJT-X might be used for
> EME? If so, it might be appropriate to look at the messages created by
> "Generate Std Msgs", which currently seem fixed to the terrestrial
> format. I couldn't find a way to change that behaviour but I might have
> missed it.
>
> Probably as a consequence of the above, I noticed that with Dx Call set
> to EA6/PA2CHR the generated messages from Tx 2 upwards only get filled
> with PA2CHR (i.e. the EA6/ is stripped).
>
> Tests done usinf 6674 with VHF features enabled, JT65 only, submode B.
> Decoding works great, by the way!

Hi Mark,

most definitely yes WSJT-X v1.7 is intended to replace WSJT for many of 
the modes WSJT offers for VHF & up working including EME. For the VHF 
bands the new FT JT65 decoder described in Steve and Joe's QEX article 
(available here http://physics.princeton.edu/pulsar/K1JT/refs.html as 
#25). This decoder has been parametrized and tuned for both weak signal 
and HF working. For the microwave bands the wider JT65 modes have been 
optimized to cope with signal spreading. Work is still ongoing improving 
averaging and hinted decoding for even better sensitivity on the weakest 
signals.

With respect to the standard messages only a specified subset of all 
possible compound call prefixes and suffixes are encodable as standard 
messages, the so called type 1 and type 2 compound callsigns. Even with 
those the prefix or suffix cannot be included in all of the standard 
message forms so the generated messages you see are the best that are 
available and designed such that a QSO may be completed correctly with 
the full compound callsign being sent and confirmed within the normal 
exchanges.

Short code messages are being implemented for the JT65 mode, JT4 already 
has these in WSJT-X. These allow QSOs in one to one sked situations to 
be completed in the most marginal of conditions.

A lot of the current effort with WSJT-X is aimed at making WSJT-X a tool 
familiar to both HF and VHF & up operators with some of the convenient 
new features developed for HF and a slicker user interface while still 
looking familiar to WSJT users.

The is also more support for reflection type propagation or other 
unstable condition modes using fast repeating codes. One of which is 
JTMSK which is targeted mainly at 6m MS users adding FEC for robust and 
accurate decoding. There is also a lot of research going on looking for 
a better FEC type mode for reflection modes where pings are much shorter 
and therefore harder to utilize using a typical USB IF filter bandwidth.

73
Bill
G4WJS.

--
Find and fix application performance issues faster with Applications Manager
Applications Manager provides deep performance insights into multiple tiers
of
your business applications. It resolves application problems quickly and
reduces your MTTR. Get your free trial!
https://ad.doubleclick.net/ddm/clk/302982198;130105516;z
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

--
Find and fix application performance issues faster with Applications Manager
Applications Manager provides deep performance insights into multiple tiers of
your business applications. It resolves application problems quickly and
reduces your MTTR. Get your free trial!
https://ad.doubleclick.net/ddm/clk/302982198;130105516;z
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] WSJT-X for eme?

2016-05-07 Thread Bill Somerville

On 07/05/2016 08:39, Mark Turner (EI3KD) wrote:
> is it intended that the next incarnation of WSJT-X might be used for
> EME? If so, it might be appropriate to look at the messages created by
> "Generate Std Msgs", which currently seem fixed to the terrestrial
> format. I couldn't find a way to change that behaviour but I might have
> missed it.
>
> Probably as a consequence of the above, I noticed that with Dx Call set
> to EA6/PA2CHR the generated messages from Tx 2 upwards only get filled
> with PA2CHR (i.e. the EA6/ is stripped).
>
> Tests done usinf 6674 with VHF features enabled, JT65 only, submode B.
> Decoding works great, by the way!

Hi Mark,

most definitely yes WSJT-X v1.7 is intended to replace WSJT for many of 
the modes WSJT offers for VHF & up working including EME. For the VHF 
bands the new FT JT65 decoder described in Steve and Joe's QEX article 
(available here http://physics.princeton.edu/pulsar/K1JT/refs.html as 
#25). This decoder has been parametrized and tuned for both weak signal 
and HF working. For the microwave bands the wider JT65 modes have been 
optimized to cope with signal spreading. Work is still ongoing improving 
averaging and hinted decoding for even better sensitivity on the weakest 
signals.

With respect to the standard messages only a specified subset of all 
possible compound call prefixes and suffixes are encodable as standard 
messages, the so called type 1 and type 2 compound callsigns. Even with 
those the prefix or suffix cannot be included in all of the standard 
message forms so the generated messages you see are the best that are 
available and designed such that a QSO may be completed correctly with 
the full compound callsign being sent and confirmed within the normal 
exchanges.

Short code messages are being implemented for the JT65 mode, JT4 already 
has these in WSJT-X. These allow QSOs in one to one sked situations to 
be completed in the most marginal of conditions.

A lot of the current effort with WSJT-X is aimed at making WSJT-X a tool 
familiar to both HF and VHF & up operators with some of the convenient 
new features developed for HF and a slicker user interface while still 
looking familiar to WSJT users.

The is also more support for reflection type propagation or other 
unstable condition modes using fast repeating codes. One of which is 
JTMSK which is targeted mainly at 6m MS users adding FEC for robust and 
accurate decoding. There is also a lot of research going on looking for 
a better FEC type mode for reflection modes where pings are much shorter 
and therefore harder to utilize using a typical USB IF filter bandwidth.

73
Bill
G4WJS.

--
Find and fix application performance issues faster with Applications Manager
Applications Manager provides deep performance insights into multiple tiers of
your business applications. It resolves application problems quickly and
reduces your MTTR. Get your free trial!
https://ad.doubleclick.net/ddm/clk/302982198;130105516;z
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

[wsjt-devel] WSJT-X for eme?

2016-05-07 Thread Mark Turner (EI3KD)

Hi,

is it intended that the next incarnation of WSJT-X might be used for 
EME? If so, it might be appropriate to look at the messages created by 
"Generate Std Msgs", which currently seem fixed to the terrestrial 
format. I couldn't find a way to change that behaviour but I might have 
missed it.

Probably as a consequence of the above, I noticed that with Dx Call set 
to EA6/PA2CHR the generated messages from Tx 2 upwards only get filled 
with PA2CHR (i.e. the EA6/ is stripped).

Tests done usinf 6674 with VHF features enabled, JT65 only, submode B. 
Decoding works great, by the way!

Regards, Mark

--
Find and fix application performance issues faster with Applications Manager
Applications Manager provides deep performance insights into multiple tiers of
your business applications. It resolves application problems quickly and
reduces your MTTR. Get your free trial!
https://ad.doubleclick.net/ddm/clk/302982198;130105516;z
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] wsjt

Re: [wsjt-devel] wsjt

Re: [wsjt-devel] wsjt

Re: [wsjt-devel] wsjt

Re: [wsjt-devel] WSJT-X for eme?

Re: [wsjt-devel] WSJT-X for eme?

Re: [wsjt-devel] wsjt

Re: [wsjt-devel] rev 6674 - Lock TX/RX

Re: [wsjt-devel] WSJT-X for eme?

Re: [wsjt-devel] WSJT-X for eme?

Re: [wsjt-devel] rev 6674 - Lock TX/RX

[wsjt-devel] rev 6674 - Lock TX/RX

Re: [wsjt-devel] WSJT-X 1.7 r6674 UDP decode message leading space

Re: [wsjt-devel] WSJT-X for eme?

Re: [wsjt-devel] WSJT-X for eme?

[wsjt-devel] WSJT-X for eme?

16 matches

Site Navigation

Mail list logo

Footer information