Re: [wsjt-devel] VP6D on wrong time slot

[John Zantek]

I just worked him on 40M, George, and he was transmitting on EVEN.  I’m 
assuming there’s only one operator and he’s running two stations.

 

John W7CD

 

From: WB5JJJ [mailto:wb5...@gmail.com] 
Sent: Monday, October 22, 2018 7:02 AM
To: wsjt-devel@lists.sourceforge.net
Subject: [wsjt-devel] VP6D on wrong time slot

 

Right now on 20m (14.090) VP6D is transmitting on the ODD time slot.  About 
half of the callers are on EVEN and the others on ODD.  How is the happening?  
He's using DX Fox according to what I'm seeing from him.  



-- 

George Cotton, WB5JJJ

 

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

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

[RC]

Also another problem is LOTW fails with Rc3. Downgraded and now all 
works well.


/*73’s Rod KI8A*/

/*Cell: 517-404-6554*/

/*Fax: 888-371-0292*/

On 10/22/2018 6:44 PM, Bill Somerville wrote:

On 22/10/2018 23:38, Anders LA9NKA wrote:
Since communication between WSJT-X and 3rd-party software like 
JTalert are sent by udp packets, could it perhaps be that during the 
hours of unattended monitoring, your computer puts the network 
interface to sleep (power saving), and thus preventing these udp 
packets getting trough, causing the program to hang...?


Hi Anders,

that is unlikely as UDP datagrams are "fire and forget" there is no 
acknowledgement and no buffering, if they can't be delivered then they 
are lost.


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] Recurring problem with WSJT-X v2.0.0-rc3

[Bill Somerville]

On 22/10/2018 23:38, Anders LA9NKA wrote:
Since communication between WSJT-X and 3rd-party software like JTalert 
are sent by udp packets, could it perhaps be that during the hours of 
unattended monitoring, your computer puts the network interface to 
sleep (power saving), and thus preventing these udp packets getting 
trough, causing the program to hang...?


Hi Anders,

that is unlikely as UDP datagrams are "fire and forget" there is no 
acknowledgement and no buffering, if they can't be delivered then they 
are lost.


73
Bill
G4WJS.



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

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

[Anders LA9NKA]

Hello.

Since communication between WSJT-X and 3rd-party software like JTalert 
are sent by udp packets, could it perhaps be that during the hours of 
unattended monitoring, your computer puts the network interface to sleep 
(power saving), and thus preventing these udp packets getting trough, 
causing the program to hang...?


I'm using Ubuntu Linux myself, and have seen error messages popping up 
sometimes if I loose network connection (complaining about not being 
able to send reports to PskReporter), but never experienced the program 
becoming unresponsive.


Just a thought...

*73... Anders, LA9NKA*
E-mail: la9...@kvalvaag.net 

Den 21.10.2018 20:27, skrev 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] Major Crash with Ver 2.0.0-rc3

[Joe Taylor]

Tom --

Your problem has been described a number of times already on this email 
list.  The work-around solution is simple: run the program from a 
command-prompt window.


-- 73, Joe, K1JT

On 10/22/2018 5:40 PM, Tom Harson wrote:

Hello

I am experiencing a program crash with RC3 (*This does not happen in RC2*)

Also this does not happen when running wsjt alone.


System / Operating information

Using Mint linux ver. 19.0

wsjtx ver. 2.0.0-rc3_amd64.deb

Logging Program - CQRLOG

The program crashes upon DECODE


Here's the Dump


Running: /usr/bin/jt9 -s WSJT-X -w 1 -m 3 -e /usr/bin -a 
/home/tom/.local/share/WSJT-X -t /tmp/WSJT-X
At line 145 of file /home/bill/wsjtx-prefix/src/lib/ft8_decode.f90 (unit 
= 81)

Fortran runtime error: Cannot open file 'fort.81': Permission denied

Error termination. Backtrace:
#0  0x7f1513f8d31a
#1  0x7f1513f8dec5
#2  0x7f1513f8e68d
#3  0x7f1514100c3d
#4  0x7f151410796c
#5  0x5562ffd3fb80
#6  0x5562ffd33d79
#7  0x5562ffd2c565
#8  0x5562ffd2b2a8
#9  0x5562ffd29bde
#10  0x7f1513034b96
#11  0x5562ffd29cd9
#12  0x


Thanks de Tom K5VJZ






___
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] Major Crash with Ver 2.0.0-rc3

[Tom Harson]

Hello

I am experiencing a program crash with RC3 (*This does not happen in RC2*)

Also this does not happen when running wsjt alone.


System / Operating information

Using Mint linux ver. 19.0

wsjtx ver. 2.0.0-rc3_amd64.deb

Logging Program - CQRLOG

The program crashes upon DECODE


Here's the Dump


Running: /usr/bin/jt9 -s WSJT-X -w 1 -m 3 -e /usr/bin -a 
/home/tom/.local/share/WSJT-X -t /tmp/WSJT-X
At line 145 of file /home/bill/wsjtx-prefix/src/lib/ft8_decode.f90 (unit 
= 81)

Fortran runtime error: Cannot open file 'fort.81': Permission denied

Error termination. Backtrace:
#0  0x7f1513f8d31a
#1  0x7f1513f8dec5
#2  0x7f1513f8e68d
#3  0x7f1514100c3d
#4  0x7f151410796c
#5  0x5562ffd3fb80
#6  0x5562ffd33d79
#7  0x5562ffd2c565
#8  0x5562ffd2b2a8
#9  0x5562ffd29bde
#10  0x7f1513034b96
#11  0x5562ffd29cd9
#12  0x


Thanks de Tom K5VJZ


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

Re: [wsjt-devel] WSJT-X & JTSDK future?

[Adam Schaible]

Buonasera Marco,

OpenSUSE Tumbleweed you say? Sure I can handle that. Here is a tested and 
working script to build WSJT-X 2.0.0 RC3 on that distro. 

First, disclaimers/notes and then, the script:

1) I am NOT a WSJT-X developer, I am just a regular ham radio operator who 
loves Linux. (I did meet K1JT once a few years ago at a speech he gave, it was 
fun!) So if you run my script below and it breaks your computer don't blame the 
wonderful WSJT-X devs, blame only me. By the way I have never tried Tumbleweed 
before today and I am very impressed, enough so that I may even use it to make 
a few contacts in WSJT-X :)

2) You do know there is an .rpm binary download of WSJT-X 2.0.0 RC3 available 
right? So we don't actually "need" to do any of this except for "educational" 
purposes. 
 
3) The WSJT-X 2.0.0 RC3 build script below is tested and working on a 6 hours 
old bare metal install of OpenSUSE Tumbleweed (KDE) on my Lenovo ThinkPad T440. 
For purpose of comparison I also built it on OpenSUSE Leap 15 running in a VM 
(AWS t2.micro), process was almost identical with just a few small differences 
that keep it from being able to run as a non-interactive script on Leap (repo 
update and devel-basis install both need command-line interventions, and Leap 
compilers are g++-7/gfortran-7), but it still builds fine. Given these positive 
results, without any further knowledge I can only guess your previous build 
issues were caused by (as usual) missing dependencies.

GL es 73 de Adam KB3ZUV


#!/bin/bash
#-wsjtx2rc3-opensuseTW-build-script.sh---
#--RUN ME WITH SUDO-
#
#first the obligatory OS patching
#since this is Tumbleweed we do full distro upgrade
zypper ref && zypper dup -y
#add user to dialout group allowing rig CAT control on next login
#(if you use VOX you don't actually need this)
usermod -a -G dialout $SUDO_USER
#install a whole bunch of dependencies to compile WSJT-X
#g++, git, and automake are all in devel_basis
zypper in -y --type pattern devel_basis && zypper in -y fftw3-devel \
fftw3-threads-devel gcc-fortran cmake libqt5-qtbase-devel \
libqt5-qtmultimedia-devel libqt5-qtconnectivity-devel \
libqt5-qtserialport-devel libusb-1_0-devel asciidoc hamlib-devel \
ruby2.5-rubygem-asciidoctor libpulse-devel libudev-devel
#create some directories for WSJT-X
sudo -u $SUDO_USER mkdir /home/$SUDO_USER/jtsource 
sudo -u $SUDO_USER mkdir /home/$SUDO_USER/.wsjtx
#grab and unzip the source code from Princeton
wget --no-check-certificate \
https://physics.princeton.edu/pulsar/k1jt/wsjtx-2.0.0-rc3.tgz
sudo -u $SUDO_USER tar -xzvf wsjtx-2.0.0-rc3.tgz \
-C /home/$SUDO_USER/jtsource
cd /home/$SUDO_USER/jtsource/wsjtx-2.0.0-rc3
#set build options
sudo -u $SUDO_USER cmake -D CMAKE_CXX_COMPILER="/usr/bin/g++-8" \
-D CMAKE_Fortran_COMPILER="/usr/bin/gfortran-8" \
-D CMAKE_INSTALL_PREFIX=/home/$SUDO_USER/.wsjtx .
#build WSJT-X on OpenSUSE
sudo -u $SUDO_USER cmake --build . --target install
#after build, to run wsjtx2 RC3 type:  ~/.wsjtx/bin/wsjtx
#-EOF---

-- 
  Adam Schaible
  kb3...@schibes.com

On Mon, Oct 22, 2018, at 9:04 AM, Marco Calistri via wsjt-devel wrote:
> 
> 
> Il 21/10/18 07:22, Adam Schaible ha scritto:
> > Good morning Linux WSJT-X fans,
> >
> > Awesome discussion going on in this thread, using all the feedback so far 
> > I've gone and hacked up some build scripts for RC3 on a couple different 
> > Linux distros (Debian and Solus). First some banter and then, the scripts.
> >
> > 1) Scripts use Paul's cmake flags and attempt to be compliant with Bill's 
> > statement on build permissions. You do still need to run the scripts as 
> > sudo to install dependencies up top but I've reduced permissions down below 
> > where the actual build takes place. 
> >
> > 2) Scripts are tested and working on stock Debian 9 (AWS t2.micro 
> > instance), Raspbian Stretch (this is for you Evariste, I compiled it on my 
> > Pi 3+), and Solus 3. (my Dell laptop). Bill will probably be able to 
> > find several more superfluous packages in my script(s) beyond what Paul has 
> > mentioned but those can always be cleaned up later on, I just want to get 
> > something up and running to share with everyone ASAP. 
> >
> > 3) What is Solus? It's a new, cheerfully minimalist Linux distro that uses 
> > neither .deb nor .rpm files, so there is no other way to get WSJT-X RC3 
> > running on it other than to build from source. I had been using Mint for 
> > over five years and while Stan is considering migrating to it, I've moved 
> > completely off because of some very bad experiences upgrading to Mint 19 a 
> > couple months ago (particularly the new "Timeshift" feature which 
> > bludgeoned my hard drive almost beyond recognition). Hopefully Stan has 
> > better luck than I did. Meanwhile I plan on contacting the Solus devs to 
> > see if they will consider packaging WSJT-X in their own ".eopkg" format for 
> > when 2.0 is officially released, and if not, I'll probably move over 

[wsjt-devel] VP6D: 20m QSO swallowed by DXA

[Dr . Alwin Güdesen]

Hi all,

...DXA really gives reason to worry. My definite QSO never showed up... along with some 
others while I was watching the system. It reminds me of earlier pitfalls with this 
system... .


By the way: It was unbelievable to see how many callers did not realize that they were in 
the wrong period.

Of course this rises the question why VP6D was on the 'wrong' peroid...

--
With kind regards:
   Alwin/DJ9KG
 
__




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

[wsjt-devel] DXPedition TX1 below 1000

[Black Michael via wsjt-devel]

Noticing a few operators calling TX1 below 1000.Is that now blocked in V2.0?  
Or should it be?  At best they are wasting their time and at worst causing 
interference to others.





>From the guide for those that aren't aware:
Hounds make initial calls anywhere in the range 1000 – 4000 Hz.  
Fox will not respond to Hounds initially calling below 1000 Hz.  Hounds 
acknowledge having been called and send their “R+rpt” messages at the same 
frequency at which they were called by Fox, nominally in the range 300 – 540 Hz.
de Mike W9MDB
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] VP6D on wrong time slot

[iain macdonnell - N6ML]

On Mon, Oct 22, 2018 at 9:09 AM Iztok Saje  wrote:
> It is VP6D, not casual Fox.
> Yes, I tried for some time but give up: VP6D was -17 at best, so 20 minutes 
> is enough.
> And they faded out.
>
> For people in wrong TS (or correct one), I've seen it all:
> - people calling below 1 kHz
> - people calling with TX2, obviously not F/H mode
> - people not receiving answer(those few I decoded)
> - people sending TX3 above 1 kHz
> - people calling them on their frequency (and wrong TS, so they block it for 
> me)

Also seen, in just a few mins of watching:

- people calling the wrong DXpedition (VK9XG)
- people trying to start QSOs with other hounds


> I guess most people got info on DX cluster and start calling without ever 
> hearing them.
> Others try to do their first FT8/WSJTX QSO ever to get ATNO.
>
>
> It is well known that if you shout enough you can compensate not hearing the 
> other side.
> (I missed this lesson a while ago, so I do not understand it:
> but it is common on any pile up so it must be true).

I skipped that day of DXing school also :/


> Nothing to be done in SW. It is part of DXers life on CW/SSB for years.
>
> Again: VP6D. Not casual Fox.

Indeed. Glad they're easy to work (prop-wise) from here (2 calls on
20m, and 4 calls on 12m)... now I can sit back and decide whether to
laugh or cry 

BTW, seems that only some of the 20m QSOs are showing up on DXA, and
none of the 12m ones so-far.

GL/73,

~iain / N6ML


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

Re: [wsjt-devel] VP6D not logging

[iain macdonnell - N6ML]

On Mon, Oct 22, 2018 at 9:15 AM David Kjellquist  wrote:
>
> Weird,worked VP6D on 40M and 20M FT8 today.  Received a +03 report,
> Gave them a R+xx report, AND received their RR73 but I'm not appearing
> in their DXA log!! While others are.

Same here. Just a wild guess .. maybe DXA can't handle multiple QSOs
on the same band/mode slot at the exact same time (to the second).

73,

~iain / N6ML


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

[wsjt-devel] VP6D not logging

[David Kjellquist]

Weird,    worked VP6D on 40M and 20M FT8 today.  Received a +03 report,  
Gave them a R+xx report, AND received their RR73 but I'm not appearing 
in their DXA log!! While others are.


--
Dave, WB5NHL
5BDXCC, 307 countries confirmed
@dkjellqu



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

Re: [wsjt-devel] VP6D on wrong time slot

[Iztok Saje]

Hi!

It is VP6D, not casual Fox.
Yes, I tried for some time but give up: VP6D was -17 at best, so 20 minutes is 
enough.
And they faded out.

For people in wrong TS (or correct one), I've seen it all:
- people calling below 1 kHz
- people calling with TX2, obviously not F/H mode
- people not receiving answer(those few I decoded)
- people sending TX3 above 1 kHz
- people calling them on their frequency (and wrong TS, so they block it for me)

I guess most people got info on DX cluster and start calling without ever 
hearing them.
Others try to do their first FT8/WSJTX QSO ever to get ATNO.


It is well known that if you shout enough you can compensate not hearing the 
other side.
(I missed this lesson a while ago, so I do not understand it:
but it is common on any pile up so it must be true).

Nothing to be done in SW. It is part of DXers life on CW/SSB for years.

Again: VP6D. Not casual Fox.

73 gl
Iztok, s52d







Pravni pogoji / Legal disclaimer
Telekom Slovenije, d.d., Ljubljana 


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

Re: [wsjt-devel] VP6D on wrong time slot

[jarmo]

Mon, 22 Oct 2018 10:14:29 -0500
WB5JJJ  kirjoitti:

> If you try CTL-E or Shift-E, it will toggle the time slot even when
> grayed out.  This should have been removed in F/H mode, but was not.

But most funniest thing is,that half world calling wrong period. Don't
watch what's happening on band activity window :)

Like my mistake with ctrl-e. VP6D answered to me once, but that qso went
to bit heaven, aaargh!

And now seems AURORA rising, so can wait nothing on bands during few
days ahead..

Jarmo, oh1mrr


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

Re: [wsjt-devel] VP6D on wrong time slot

[WB5JJJ]

If you try CTL-E or Shift-E, it will toggle the time slot even when grayed
out.  This should have been removed in F/H mode, but was not.

On Mon, Oct 22, 2018 at 10:12 AM jarmo  wrote:

> Mon, 22 Oct 2018 09:36:05 -0500
> "Ted Gisske"  kirjoitti:
>
> > He is using V1.9.1. You are likely using V2.0 RCx. Reinstall V1.9.1
> > and all will be well.
>
> I have 1.9.1 and impossible work hound, tx even..
>
> Jarmo, oh1mrr
>
>
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>


-- 
George Cotton, WB5JJJ
PO Box 1025
Russellville, AR  72811

479.968.7737 Home
479.857.7737 Cell

DMR K5CS (Local Repeater) - 310515, CC1, TS2
DMR Arkansas - 3105

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

[wsjt-devel] VP6D

[jarmo]

Ok, ctrl-E, it works, BUT!
Why did they started with odd?

Jarmo, oh1mrr


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

Re: [wsjt-devel] VP6D on wrong time slot

[jarmo]

Mon, 22 Oct 2018 09:36:05 -0500
"Ted Gisske"  kirjoitti:

> He is using V1.9.1. You are likely using V2.0 RCx. Reinstall V1.9.1
> and all will be well. 

I have 1.9.1 and impossible work hound, tx even..

Jarmo, oh1mrr


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

Re: [wsjt-devel] VP6D on wrong time slot

[George J. Molnar]

Clicking on their (odd sequence) CQ does put my Hound into TX first, and seems 
to work okay. The checkbox IS greyed out, so I can’t manually change it.

Ver 1.9.1 running Mac OS.



George J Molnar
Arlington, Virginia, USA
KF2T   -   FM18lv












> On Oct 22, 2018, at 10:46 AM, WB5JJJ  wrote:
> 
> Those options should have been removed for the F/H mode.  Perhaps, they 
> triggered this by accident.  
> 
> On Mon, Oct 22, 2018 at 9:41 AM Sam W2JDB via wsjt-devel 
> mailto:wsjt-devel@lists.sourceforge.net>> 
> wrote:
> Ctrl-E - Turns on TX Even
> Shift-E - Turns off TX Even
>  
> good luck
>  
> Sam W2JDB
> 
>  
>  
> -Original Message-
> From: WB5JJJ mailto:wb5...@gmail.com>>
> To: wsjt-devel  >
> Sent: Mon, Oct 22, 2018 10:32 am
> Subject: Re: [wsjt-devel] VP6D on wrong time slot
> 
> Yes, you are correct.  
> 
> I think what we are seeing is a glitch in the software on their end, which 
> was an occurrence even I experienced where I was not able to UNCHECK the EVEN 
> box as it was grayed out.  Restarting WSJTx solved the problem and it's never 
> returned.  But how are so many guys transmitting on the EVEN time slot?  They 
> must be using v1.8.x which, if I remember, would allow choosing time slot.  
> What's funny, is all the guys transmitting on ODD with no chance of being 
> heard by VP6D.  
> 
> Time to move on to another frequency and let this run it's course.  
> 
> On Mon, Oct 22, 2018 at 9:22 AM Jay Hainline > wrote:
> I am seeing this too George as of 1415z on 14090. I remember where this could 
> happened in an earlier version but thought it had been fixed. 
> 
> Jay KA9CFD
> 
> 
> 
> Sent from my U.S.Cellular© Smartphone
> 
>  Original message 
> From: WB5JJJ >
> Date: 10/22/18 09:01 (GMT-06:00)
> To: wsjt-devel@lists.sourceforge.net <>
> Subject: [wsjt-devel] VP6D on wrong time slot
> 
> Right now on 20m (14.090) VP6D is transmitting on the ODD time slot.  About 
> half of the callers are on EVEN and the others on ODD.  How is the happening? 
>  He's using DX Fox according to what I'm seeing from him.  
> 
> -- 
> George Cotton, WB5JJJ
> 
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net <>
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel <>
> 
> 
> -- 
> George Cotton, WB5JJJ
> PO Box 1025
> Russellville, AR  72811
> 
> 479.968.7737 Home
> 479.857.7737 Cell
> 
> DMR K5CS (Local Repeater) - 310515, CC1, TS2
> DMR Arkansas - 3105
> 
> 4
> ___
> 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 
> 
> 
> 
> -- 
> George Cotton, WB5JJJ
> PO Box 1025
> Russellville, AR  72811
> 
> 479.968.7737 Home
> 479.857.7737 Cell
> 
> DMR K5CS (Local Repeater) - 310515, CC1, TS2
> DMR Arkansas - 3105
> 
> 4
> ___
> 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] VP6D on wrong time slot

[WB5JJJ]

Those options should have been removed for the F/H mode.  Perhaps, they
triggered this by accident.

On Mon, Oct 22, 2018 at 9:41 AM Sam W2JDB via wsjt-devel <
wsjt-devel@lists.sourceforge.net> wrote:

> Ctrl-E - Turns on TX Even
> Shift-E - Turns off TX Even
>
> good luck
>
> Sam W2JDB
>
>
>
> -Original Message-
> From: WB5JJJ 
> To: wsjt-devel 
> Sent: Mon, Oct 22, 2018 10:32 am
> Subject: Re: [wsjt-devel] VP6D on wrong time slot
>
> Yes, you are correct.
>
> I think what we are seeing is a glitch in the software on their end, which
> was an occurrence even I experienced where I was not able to UNCHECK the
> EVEN box as it was grayed out.  Restarting WSJTx solved the problem and
> it's never returned.  But how are so many guys transmitting on the EVEN
> time slot?  They must be using v1.8.x which, if I remember, would allow
> choosing time slot.  What's funny, is all the guys transmitting on ODD with
> no chance of being heard by VP6D.
>
> Time to move on to another frequency and let this run it's course.
>
> On Mon, Oct 22, 2018 at 9:22 AM Jay Hainline  wrote:
>
> I am seeing this too George as of 1415z on 14090. I remember where this
> could happened in an earlier version but thought it had been fixed.
>
> Jay KA9CFD
>
>
>
> Sent from my U.S.Cellular© Smartphone
>
>  Original message 
> From: WB5JJJ 
> Date: 10/22/18 09:01 (GMT-06:00)
> To: wsjt-devel@lists.sourceforge.net
> Subject: [wsjt-devel] VP6D on wrong time slot
>
> Right now on 20m (14.090) VP6D is transmitting on the ODD time slot.
> About half of the callers are on EVEN and the others on ODD.  How is the
> happening?  He's using DX Fox according to what I'm seeing from him.
>
> --
> George Cotton, WB5JJJ
>
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>
>
>
> --
> George Cotton, WB5JJJ
> PO Box 1025
> Russellville, AR  72811
>
> 479.968.7737 Home
> 479.857.7737 Cell
>
> DMR K5CS (Local Repeater) - 310515, CC1, TS2
> DMR Arkansas - 3105
>
> 4
> ___
> 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
>


-- 
George Cotton, WB5JJJ
PO Box 1025
Russellville, AR  72811

479.968.7737 Home
479.857.7737 Cell

DMR K5CS (Local Repeater) - 310515, CC1, TS2
DMR Arkansas - 3105

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

Re: [wsjt-devel] VP6D on wrong time slot

[WB5JJJ]

Nope.  They said they were using v1.9.1 and that's what I'm running.

The option to transmit on EVEN is grayed out since v1.9.0 rc2 ( I just
reloaded all previous versions to see ).  In v1.8.x, the F/H option is not
there yet.
I see there is a code that allows CTRL-E and SHIFT-E to switch time slots.
This should have been disabled in F/H mode.


On Mon, Oct 22, 2018 at 9:39 AM Ted Gisske  wrote:

> He is using V1.9.1. You are likely using V2.0 RCx. Reinstall V1.9.1 and
> all will be well.
>
> 73,
>
> Ted
>
> K9IMM
>
>
>
> *From:* WB5JJJ [mailto:wb5...@gmail.com]
> *Sent:* Monday, October 22, 2018 9:02 AM
> *To:* wsjt-devel@lists.sourceforge.net
> *Subject:* [wsjt-devel] VP6D on wrong time slot
>
>
>
> Right now on 20m (14.090) VP6D is transmitting on the ODD time slot.
> About half of the callers are on EVEN and the others on ODD.  How is the
> happening?  He's using DX Fox according to what I'm seeing from him.
>
>
> --
>
> George Cotton, WB5JJJ
>
>
>
>
>
>
> 
>
> Virus-free. www.avg.com
> 
>
>
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>


-- 
George Cotton, WB5JJJ
PO Box 1025
Russellville, AR  72811

479.968.7737 Home
479.857.7737 Cell

DMR K5CS (Local Repeater) - 310515, CC1, TS2
DMR Arkansas - 3105

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

Re: [wsjt-devel] VP6D on wrong time slot

[Sam W2JDB via wsjt-devel]

Ctrl-E - Turns on TX Even
Shift-E - Turns off TX Even
 
good luck
 

Sam W2JDB



 
 
-Original Message-
From: WB5JJJ 
To: wsjt-devel 
Sent: Mon, Oct 22, 2018 10:32 am
Subject: Re: [wsjt-devel] VP6D on wrong time slot



Yes, you are correct.  



I think what we are seeing is a glitch in the software on their end, which was 
an occurrence even I experienced where I was not able to UNCHECK the EVEN box 
as it was grayed out.  Restarting WSJTx solved the problem and it's never 
returned.  But how are so many guys transmitting on the EVEN time slot?  They 
must be using v1.8.x which, if I remember, would allow choosing time slot.  
What's funny, is all the guys transmitting on ODD with no chance of being heard 
by VP6D.  



Time to move on to another frequency and let this run it's course.  



On Mon, Oct 22, 2018 at 9:22 AM Jay Hainline  wrote:


I am seeing this too George as of 1415z on 14090. I remember where this could 
happened in an earlier version but thought it had been fixed. 


Jay KA9CFD







Sent from my  U.S.Cellular© Smartphone




 Original message 
From: WB5JJJ  
Date: 10/22/18  09:01  (GMT-06:00) 
To: wsjt-devel@lists.sourceforge.net 
Subject: [wsjt-devel] VP6D on wrong time slot 



Right now on 20m (14.090) VP6D is transmitting on the ODD time slot.  About 
half of the callers are on EVEN and the others on ODD.  How is the happening?  
He's using DX Fox according to what I'm seeing from him.  


-- 








George Cotton, WB5JJJ









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



-- 








George Cotton, WB5JJJ
PO Box 1025
Russellville, AR  72811

479.968.7737 Home
479.857.7737 Cell


DMR K5CS (Local Repeater) - 310515, CC1, TS2
DMR Arkansas - 3105


4








___
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] VP6D on wrong time slot

[Ted Gisske]

He is using V1.9.1. You are likely using V2.0 RCx. Reinstall V1.9.1 and all 
will be well. 

73,

Ted

K9IMM

 

From: WB5JJJ [mailto:wb5...@gmail.com] 
Sent: Monday, October 22, 2018 9:02 AM
To: wsjt-devel@lists.sourceforge.net
Subject: [wsjt-devel] VP6D on wrong time slot

 

Right now on 20m (14.090) VP6D is transmitting on the ODD time slot.  About 
half of the callers are on EVEN and the others on ODD.  How is the happening?  
He's using DX Fox according to what I'm seeing from him.  



-- 

George Cotton, WB5JJJ

 

 


 

 

Virus-free.  

 www.avg.com 

 

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

Re: [wsjt-devel] VP6D on wrong time slot

[WB5JJJ]

Yes, you are correct.

I think what we are seeing is a glitch in the software on their end, which
was an occurrence even I experienced where I was not able to UNCHECK the
EVEN box as it was grayed out.  Restarting WSJTx solved the problem and
it's never returned.  But how are so many guys transmitting on the EVEN
time slot?  They must be using v1.8.x which, if I remember, would allow
choosing time slot.  What's funny, is all the guys transmitting on ODD with
no chance of being heard by VP6D.

Time to move on to another frequency and let this run it's course.

On Mon, Oct 22, 2018 at 9:22 AM Jay Hainline  wrote:

> I am seeing this too George as of 1415z on 14090. I remember where this
> could happened in an earlier version but thought it had been fixed.
>
> Jay KA9CFD
>
>
>
> Sent from my U.S.Cellular© Smartphone
>
>  Original message 
> From: WB5JJJ 
> Date: 10/22/18 09:01 (GMT-06:00)
> To: wsjt-devel@lists.sourceforge.net
> Subject: [wsjt-devel] VP6D on wrong time slot
>
> Right now on 20m (14.090) VP6D is transmitting on the ODD time slot.
> About half of the callers are on EVEN and the others on ODD.  How is the
> happening?  He's using DX Fox according to what I'm seeing from him.
>
> --
> George Cotton, WB5JJJ
>
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>


-- 
George Cotton, WB5JJJ
PO Box 1025
Russellville, AR  72811

479.968.7737 Home
479.857.7737 Cell

DMR K5CS (Local Repeater) - 310515, CC1, TS2
DMR Arkansas - 3105

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

Re: [wsjt-devel] VP6D on wrong time slot

[Jay Hainline]

I am seeing this too George as of 1415z on 14090. I remember where this could 
happened in an earlier version but thought it had been fixed. 
Jay KA9CFD


Sent from my  U.S.Cellular© Smartphone
 Original message From: WB5JJJ  Date: 
10/22/18  09:01  (GMT-06:00) To: wsjt-devel@lists.sourceforge.net Subject: 
[wsjt-devel] VP6D on wrong time slot 
Right now on 20m (14.090) VP6D is transmitting on the ODD time slot.  About 
half of the callers are on EVEN and the others on ODD.  How is the happening?  
He's using DX Fox according to what I'm seeing from him.  

-- 
George Cotton, WB5JJJ

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

[wsjt-devel] VP6D on wrong time slot

[WB5JJJ]

Right now on 20m (14.090) VP6D is transmitting on the ODD time slot.  About
half of the callers are on EVEN and the others on ODD.  How is the
happening?  He's using DX Fox according to what I'm seeing from him.

-- 
George Cotton, WB5JJJ
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] WSJT-X & JTSDK future?

[Marco Calistri via wsjt-devel]

Il 21/10/18 07:22, Adam Schaible ha scritto:
> Good morning Linux WSJT-X fans,
>
> Awesome discussion going on in this thread, using all the feedback so far 
> I've gone and hacked up some build scripts for RC3 on a couple different 
> Linux distros (Debian and Solus). First some banter and then, the scripts.
>
> 1) Scripts use Paul's cmake flags and attempt to be compliant with Bill's 
> statement on build permissions. You do still need to run the scripts as sudo 
> to install dependencies up top but I've reduced permissions down below where 
> the actual build takes place. 
>
> 2) Scripts are tested and working on stock Debian 9 (AWS t2.micro instance), 
> Raspbian Stretch (this is for you Evariste, I compiled it on my Pi 3+), and 
> Solus 3. (my Dell laptop). Bill will probably be able to find several 
> more superfluous packages in my script(s) beyond what Paul has mentioned but 
> those can always be cleaned up later on, I just want to get something up and 
> running to share with everyone ASAP. 
>
> 3) What is Solus? It's a new, cheerfully minimalist Linux distro that uses 
> neither .deb nor .rpm files, so there is no other way to get WSJT-X RC3 
> running on it other than to build from source. I had been using Mint for over 
> five years and while Stan is considering migrating to it, I've moved 
> completely off because of some very bad experiences upgrading to Mint 19 a 
> couple months ago (particularly the new "Timeshift" feature which bludgeoned 
> my hard drive almost beyond recognition). Hopefully Stan has better luck than 
> I did. Meanwhile I plan on contacting the Solus devs to see if they will 
> consider packaging WSJT-X in their own ".eopkg" format for when 2.0 is 
> officially released, and if not, I'll probably move over to the Arch Linux 
> distro family and write/maintain a WSJT-X 2.0 PKGBUILD for the AUR (Arch User 
> Repository) if someone else doesn't beat me to the punch.
>
> Tnx es 73 de Adam KB3ZUV
>
>
> #!/bin/bash
> #-wsjtx2rc3-debian-build-script.sh---
> #---RUN ME WITH SUDO-
> #
> #first the obligatory OS patches
> apt update && apt upgrade -y
> #add user to dialout group allowing rig CAT control on next login
> #(if you use VOX you don't actually need this)
> usermod -a -G dialout $SUDO_USER
> #install a whole bunch of dependencies to compile WSJT-X
> #g++ is in build-essential along with lots of other good stuff
> apt install -y build-essential gfortran-6 libfftw3-dev \
> libqt5x11extras5-dev libtool libudev-dev libusb-1.0.0-dev \
> python-pkgconfig python-pyqt5 qtmultimedia5-dev texinfo \
> libqt5serialport5 libqt5serialport5-dev cmake automake asciidoc \
> asciidoctor libxslt1-dev docbook-xsl xsltproc libxml2-utils git
> #create some directories for WSJT-X
> sudo -u $SUDO_USER mkdir /home/$SUDO_USER/jtsource
> sudo -u $SUDO_USER mkdir /home/$SUDO_USER/.wsjtx
> #grab and unzip the source code from Princeton
> wget --no-check-certificate \
> https://physics.princeton.edu/pulsar/k1jt/wsjtx-2.0.0-rc3.tgz
> sudo -u $SUDO_USER tar -xzvf wsjtx-2.0.0-rc3.tgz \
> -C /home/$SUDO_USER/jtsource
> cd /home/$SUDO_USER/jtsource/wsjtx-2.0.0-rc3
> #set build options
> sudo -u $SUDO_USER cmake -D CMAKE_CXX_COMPILER="/usr/bin/g++" \
> -D CMAKE_Fortran_COMPILER="/usr/bin/gfortran-6" \
> -D CMAKE_INSTALL_PREFIX=/home/$SUDO_USER/.wsjtx .
> #build WSJT-X on Debian
> sudo -u $SUDO_USER cmake --build . --target install
> #-EOF---
>
>
> #!/bin/bash
> #-wsjtx2rc3-solus-build-script.sh---
> #--RUN ME WITH SUDO-
> #
> #first the obligatory OS patches
> eopkg -y up
> #add user to dialout group allowing rig CAT control on next login
> #(if you use VOX you don't actually need this)
> usermod -a -G dialout $SUDO_USER
> #install a whole bunch of dependencies to compile WSJT-X
> #g++ is in system.devel along with lots of other good stuff
> eopkg -y it -c system.devel && eopkg -y it git fftw-devel \
> qt5-multimedia-devel qt5-connectivity-devel qt5-serialport-devel \
> ruby-devel libusb-devel asciidoc
> #asciidoctor is not in Solus repo and has to be added as a Ruby gem
> gem install asciidoctor
> #create some directories for WSJT-X
> sudo -u $SUDO_USER mkdir /home/$SUDO_USER/jtsource 
> sudo -u $SUDO_USER mkdir /home/$SUDO_USER/.wsjtx
> #grab and unzip the source code from Princeton
> wget --no-check-certificate \
> https://physics.princeton.edu/pulsar/k1jt/wsjtx-2.0.0-rc3.tgz
> sudo -u $SUDO_USER tar -xzvf wsjtx-2.0.0-rc3.tgz \
> -C /home/$SUDO_USER/jtsource
> cd /home/$SUDO_USER/jtsource/wsjtx-2.0.0-rc3
> #set build options
> sudo -u $SUDO_USER cmake -D CMAKE_CXX_COMPILER="/usr/bin/g++" \
> -D CMAKE_Fortran_COMPILER="/usr/bin/gfortran" \
> -D CMAKE_INSTALL_PREFIX=/home/$SUDO_USER/.wsjtx .
> #build WSJT-X on Solus
> sudo -u $SUDO_USER cmake --build . --target install
> #-EOF---
>
Sirs,

Unluckily on my openSUSE Tumbleweed 64bits the WSJTX  source compiling
attempt has failed repeatedly, also by using