Re: [wsjt-devel] Suggestions: New updates field and automatically RX QRG reset

[Gary McDuffie]

On Dec 13, 2018, at 19:26, Bill Somerville  wrote:this is not correct, don;t do that. The Rx offset goes your QSO partners frequency for two reasons, firstly because that directs messages decoded at that offset to the Rx Frequency decodes window, and more importantly the decoder tries first and harder to decode at that offset. This is possible because more resources can be spent on decoding the most likely spot before trying everywhere else in the decoder passband.I’m aware that the receive frequency receives priority resulting in a slight improvement in sensitivity and also gets decoded first.  It was/is my understanding that this is only a slight improvement in sensitivity.If you do not want to see decodes in the Rx Frequency windows then drag the splitter bar between the windows to the right until you can't see it any more, that way you will not be crippling the decoder whenever you work another station.Sounds good on paper, but then I can’t see what I want to see there.  :)No problem, Bill.  I thought I would bring it up.  I would just prefer to see no traffic other than something to or from myself on the right side.  Everything else is available on the left.  Not a show stopper at all.73, Gary - AG0N
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] TX not moving on double-clcik

[Jim Shorney]

Thanks for the reply Bill. It's been long enough now that I don't recall if ESC 
was one of the things I tried. If it happens again I will give it a try.

GA release working fine here so far, although I have not worked it much since I 
am mainly a DXer. Great work gentlemen!

73

-Jim
NU0C


On Thu, 13 Dec 2018 22:52:22 +
Bill Somerville  wrote:

> On 02/12/2018 01:46, Jim Shorney wrote:
> > I have noticed a specific scenario that has happened several times during 
> > the contest. This happens when I have called a CQing station two or three 
> > times with no reply and I bail and go call another. Then I see the first 
> > station replying to me with TX3 while I am calling the new one. So I bail 
> > on that call and try to go back to work the first station with a 
> > double-click on the message. This moves the RX back to the first station's 
> > frequency, but not the TX. It is acting like Hold TX is on, but it is not. 
> > I tried toggling Hold TX. and shift-doubleclick, but the TX refuses to move 
> > until I use one those "confusing" arrows. (j/k, I'm not confused  - much).
> >
> > Maybe I'm just a bad op. I know we are supposed to offset our signals and 
> > call split, but that doesn't seem to be happening. At any rate, it seems 
> > like the TX should move in this scenario, otherwise I end up QRMing the 
> > second op until I remember where I am.  
> 
> Hi Jim,
> 
> sorry for the delay on addressing this.
> 
> You should be able to clear the QSO you are abandoning by hitting ESC 
> and/or F4, after that WSJT-X should have forgotten you were in a QSO.
> 
> 73
> Bill
> G4WJS.


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

Re: [wsjt-devel] Suggestions: New updates field and automatically RX QRG reset

[Stan Gammons]

I use Hold Tx Freq, pick a clear spot in the waterfall and start with Tx 
and Rx together. That way I can see if someone occupies that spot before 
I decide to transmit there.  When I complete a QSO, I either click on 
the down arrow to put Tx and Rx back like they were, or ctrl click on 
the red bracket Tx bracket in the waterfall.


That's the way I do it.  I'm sure everyone has their own way of operating.


73

Stan
KM4HQE


On 12/13/18 8:26 PM, Bill Somerville wrote:

On 14/12/2018 02:18, Gary McDuffie wrote:
In fact, I’d rather not have it go to the location where I double 
click to answer someone’s CQ.  I don’t need it there.


Hi Gary,

this is not correct, don;t do that. The Rx offset goes your QSO 
partners frequency for two reasons, firstly because that directs 
messages decoded at that offset to the Rx Frequency decodes window, 
and more importantly the decoder tries first and harder to decode at 
that offset. This is possible because more resources can be spent on 
decoding the most likely spot before trying everywhere else in the 
decoder passband.


If you do not want to see decodes in the Rx Frequency windows then 
drag the splitter bar between the windows to the right until you can't 
see it any more, that way you will not be crippling the decoder 
whenever you work another station.


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

[wsjt-devel] PSK Reporter Spotting & intermittent internet connection

[Julian VK4CMV]

Hi -

This issue has been around a while, so not a V2 GA one specifically.

I'm off the beaten track at my QTH - consequently no ADSL or permanent
connection to the internet. I use an iPhone which gets a beautiful signal
from the towers on the hillsides around me - and I use a hotspot from that
to provide internet around the house. Works like a charm.

If I start WSJT-X up and subsequently activate my internet connection - my
station fails to report signals to PSK Reporter. The way to fix this is to
restart WSJT-X (not un-click and click the box in Settings-->Reporting)

Likewise, if I wander away from the house and my station loses the signal
from the iPHone, PSK reporting stops again, not to return until I
re-establish the hotspot and restart WSJT-X

Should I really need to restart WSJT-X?

No big deal - because I've learnt to work around it.


On another topic, there's a good opening in VK and ZL on 6m this morning -
and all the signal traces I have see are in the new 77 bit format. Which is
good!

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

Re: [wsjt-devel] Suggestions: New updates field and automatically RX QRG reset

[Bill Somerville]

On 14/12/2018 02:18, Gary McDuffie wrote:

In fact, I’d rather not have it go to the location where I double click to 
answer someone’s CQ.  I don’t need it there.


Hi Gary,

this is not correct, don;t do that. The Rx offset goes your QSO partners 
frequency for two reasons, firstly because that directs messages decoded 
at that offset to the Rx Frequency decodes window, and more importantly 
the decoder tries first and harder to decode at that offset. This is 
possible because more resources can be spent on decoding the most likely 
spot before trying everywhere else in the decoder passband.


If you do not want to see decodes in the Rx Frequency windows then drag 
the splitter bar between the windows to the right until you can't see it 
any more, that way you will not be crippling the decoder whenever you 
work another station.


73
Bill
G4WJS.



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

Re: [wsjt-devel] Suggestions: New updates field and automatically RX QRG reset

[Gary McDuffie]

> On Dec 13, 2018, at 18:52, Bill Somerville  wrote:
> 
> The Rx audio offset is automatically moved to a station you choose to answer 
> when you double-click their decoded message.

I’ve been thinking of commenting on this action myself.  I’m glad someone else 
brought it up.  While my desires wouldn’t necessarily be the same as someone 
else’s, it could be a configuration check mark.  See below.

I don’t care to see random text in the right part of the screen, just because 
someone lands on a frequency where the green RX bracket happens to  be.  In 
fact, I’d rather not have it go to the location where I double click to answer 
someone’s CQ.  I don’t need it there.  If he answers me, the program will 
recognize that and decode it without moving the receive focus.  My normal 
routine is the park the receive frequency well above the highest incoming 
signal (i.e. 2900).  I only want to see my own and the text of the station 
sending text to me on the right side of the screen.  Anything else can be seen 
on the left.  To accomplish this, I double click on the station I want to 
answer and then immediately move the receive bracket to 2900 or higher.  It 
would be nice to have a check box that would allow me to set it where I want it 
and have it stay there, even when double clicking someone to call them.  It 
would be just like the Hold Tx Frequency check box.

I realize this may not be something everyone would want to do, but Allan’s post 
brought it to the top again, so I’m running it up the flag.

Gary - AG0N

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

Re: [wsjt-devel] Suggestions: New updates field and automatically RX QRG reset

[Bill Somerville]

Hi Allan,

comments in line below.

On 14/12/2018 01:31, m...@oz5xn.dk wrote:

Herewith two suggestions for improvements in upcoming versions:
A message field from the development group "NEW UPDATES" (flashing) in 
red. It seems that it takes some time before many users update. 
Someone may not have access to Facebook or other immediate information 
about WSJT, and there are actually still people running with older 
versions than 1.9.
Upgrading in unison is not normally as critical as for v2.0.0 FT8 users 
where there is a incompatible protocol change, but yes we are 
considering options that are not too complex to implement and will not 
make our application more attractive to AV software trying to disable it.


And a check mark for whether you want the RX frequency (green post) to 
be automatically reset to own TX frequency at a new CQ call after a 
QSO. This keeps the RX frequency list virtually free of anything other 
than own correspondence. This can of course be done manually, but an 
automation option would be practical.
The Rx audio offset is automatically moved to a station you choose to 
answer when you double-click their decoded message. If you want move the 
Rx audio offset to the Tx audio offset it only takes one click even when 
choosing a new Tx frequency (CTRL+click on the waterfall). We prefer to 
only automate actions when it is necessary, the idea is that you the 
operator are still in charge for all the important decisions. Moving the 
Rx offset just because a CQ is being sent may surprise many users who 
had deliberately set it somewhere else.


Maybe one more thing: Why not make “Auto seq” and “Call 1^st” a 
possibility also on JT9/65 etc? I usually forget to answer when I’m 
(quite seldom) running JT65 because I’m used to FT8. And I’m not alone 
on that - I think. J


This tends to fall into the category of unnecessary automation, you have 
plenty of time to choose a QSO partner from caller(s) in those modes. If 
your attention is elsewhere then perhaps you shouldn't be calling CQ in 
the first place?


We did add "Auto Seq" for JT65 an QRA64 in v1.9 as the microwave EME 
users often have a lot of workload between T/R periods with dishes to 
point and other things like Doppler correction adjustments, somehow it 
has gone AWOL in v2.0.0 but there would be no urgency to put it back for 
HF/VHF/UHF users who don't have the same workload during QSOs.




73, Allan


73
Bill
G4WJS.

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

[wsjt-devel] Suggestions: New updates field and automatically RX QRG reset

[mail]

Herewith two suggestions for improvements in upcoming versions:
A message field from the development group "NEW UPDATES" (flashing) in red.
It seems that it takes some time before many users update. Someone may not
have access to Facebook or other immediate information about WSJT, and there
are actually still people running with older versions than 1.9.

And a check mark for whether you want the RX frequency (green post) to be
automatically reset to own TX frequency at a new CQ call after a QSO. This
keeps the RX frequency list virtually free of anything other than own
correspondence. This can of course be done manually, but an automation
option would be practical.

Maybe one more thing: Why not make "Auto seq" and "Call 1st" a possibility
also on JT9/65 etc? I usually forget to answer when I'm (quite seldom)
running JT65 because I'm used to FT8. And I'm not alone on that - I think. J


73, Allan



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

[wsjt-devel] WSJT-X V2.0.0 Startup Item

[Rick]

Good evening all,

I have noticed that the Windows installation of WSJT-X V2.0.0 does not 
have F Tol set to 200 out of the gate. I've seen several complaints that 
"It doesn't work".  Of course, once F Tol is set to 200, it DOES work.


Just a suggestion ... is it possible to set the default F Tol to 200 in 
the next release? (Insert comments about reading the manual, and so on).


Thanks and 73

Rick



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

Re: [wsjt-devel] TX not moving on double-clcik

[Bill Somerville]

On 02/12/2018 01:46, Jim Shorney wrote:

I have noticed a specific scenario that has happened several times during the contest. 
This happens when I have called a CQing station two or three times with no reply and I 
bail and go call another. Then I see the first station replying to me with TX3 while I am 
calling the new one. So I bail on that call and try to go back to work the first station 
with a double-click on the message. This moves the RX back to the first station's 
frequency, but not the TX. It is acting like Hold TX is on, but it is not. I tried 
toggling Hold TX. and shift-doubleclick, but the TX refuses to move until I use one those 
"confusing" arrows. (j/k, I'm not confused  - much).

Maybe I'm just a bad op. I know we are supposed to offset our signals and call 
split, but that doesn't seem to be happening. At any rate, it seems like the TX 
should move in this scenario, otherwise I end up QRMing the second op until I 
remember where I am.


Hi Jim,

sorry for the delay on addressing this.

You should be able to clear the QSO you are abandoning by hitting ESC 
and/or F4, after that WSJT-X should have forgotten you were in a QSO.


73
Bill
G4WJS.



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

Re: [wsjt-devel] PSKReporter Antenna Strings

[Philip Gladstone]

I filtered down to WSJT* only and counted by unique callsigns:

+---+--+
| antennaInformation    | count(distinct callsign) |
+---+--+
| 43' Vertical  |    5 |
| 43 FOOT VERTICAL  |    5 |
| STEPPIR   |    5 |
| 40m OCF Dipole    |    5 |
| 3 element Beam    |    5 |
| FD4   |    5 |
| SteppIR BigIR |    5 |
| SteppIR Vertical  |    5 |
| End fed dipole    |    5 |
| INV-L |    5 |
| 3 element Yagi    |    5 |
| 40M dipole    |    5 |
| Half wave vertical    |    5 |
| Tribander |    5 |
| Butternut HF9V    |    5 |
| 5 ele yagi    |    5 |
| Vertical Dipole   |    5 |
| 2 |    5 |
| Horizontle Loop   |    5 |
| AV-640    |    6 |
| mag loop  |    6 |
| G5RV Jr   |    6 |
| 43 ft Vertical    |    6 |
| GAP Titan Vertical    |    6 |
| multiband dipole  |    6 |
| inv V |    6 |
| 3 ele yagi    |    6 |
| inv vee   |    6 |
| Hustler 5BTV Vertical |    6 |
| HyEndFed  |    6 |
| Wire  |    6 |
| 5 element Yagi    |    6 |
| DELTA |    6 |
| GAP Titan |    6 |
| 2 EL YAGI |    6 |
| R8 Vertical   |    6 |
| Rotatable Dipole  |    7 |
| RX Op32   |    7 |
| Magloop   |    7 |
| 5 el Yagi |    7 |
| 1/4 wave vertical |    7 |
| Hustler 5BTV  |    7 |
| ENDFED    |    7 |
| 80M Loop  |    7 |
| CushCraft MA5B    |    7 |
| Double Bazooka    |    7 |
| Moxon |    8 |
| 3el Yagi  |    8 |
| 10mH DP   |    8 |
| 7 el at 85 ft |    8 |
| HB9CV |    8 |
| VERT  |    8 |
| Rotary dipole |    8 |
| 4ele Yagi |    8 |
| W3DZZ |    8 |
| Steppir 3 element.    |    8 |
| RX Op05   |    9 |
| Yagi  |   10 |
| Random Wire   |   10 |
| wire dipole   |   10 |
| LOOP  |   10 |
| GAP Titan DX  |   11 |
| INV L |   11 |
| 4el Yagi @ 25m    |   11 |
| Attic Dipole  |   11 |
| Fan Dipole    |   11 |
| Carolina Windom   |   11 |
| End Fed Wire  |   11 |
| RX Op2    |   12 |
| 3 El Yagi |   12 |
| OCFD  |   13 |
| End Fed   |   13 |
| HUSTLER 6BTV  |   13 |
| Inverted V Dipole |   13 |
| Sloper    |   13 |
| inverted Vee  |   14 |
| Cobweb    |   14 |
| Magnetic Loop |   14 |
| EFHW  |   14 |
| longwire  |   15 |
| LW    |   15 |
| Doublet   |   15 |
| DP    |   17 |
| ZS6BKW    |   17 |
| Delta Loop    |   25 |
| Dipol |   26 |
| hex beam  |   26 |
| GP    |   27 |
| SIM31 (New Mode)  |   31 |
| LONG WIRE |   33 |
| 

Re: [wsjt-devel] PSKReporter Antenna Strings

[Bill Somerville]

On 13/12/2018 21:59, Philip Gladstone wrote:

there are a lot of unique strings below this


Some of them wet!

73
Bill
G4WJS.

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

[wsjt-devel] PSKReporter Antenna Strings

[Philip Gladstone]

The stats for the most common antennas used over the last 7 days are:


++--+

| antennaInformation | count(*) |

++--+

| ZS6BKW|32 |

| SLOPER|32 |

| Magnetic Loop|33 |

| RX Op05|37 |

| DP|39 |

| RX Op32|43 |

| Hex Beam|45 |

| LW|47 |

| LONG WIRE|54 |

| Dipol|60 |

| Hexbeam|63 |

| Inverted V|65 |

| Delta Loop|65 |

| V-DELTADUNKEL.SU |67 |

| RX Op2|68 |

| Inverted L|70 |

| OCF Dipole|71 |

| GP|77 |

| WINDOM|83 |

| SIM31 (New Mode)|138 |

| G5RV|200 |

| Vertical|234 |

| SIM31Mode|851 |

| Dipole|1679 |

||3335 |

++--+


As you might expect, there are a lot of unique strings below this.

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

Re: [wsjt-devel] WSJT-X versions distribution as per: https://pskreporter.info/cgi-bin/pskstats.pl

[Paul Bramscher]

> On December 13, 2018 at 12:53 PM Bill Somerville  
> wrote:
> 
> On 13/12/2018 18:38, Paul Bramscher wrote:
> 
> > > 
> > Is it possible to infer operating system from the version 
> > "signature" as reported on pskreporter?  I see that the heaviest example of 
> > 2.0.0 usage is "WSJT-X v2.0.0 784f75".  Judging from the file download 
> > stats on SourceForge, I would presume that to be the Windows build/release?
> > 
> > 
> > Only a few dozen of us are showing up concisely as "WSJT-X v2.0.0". 
> >  Again judging from the download activity (and my own case) I would presume 
> > these are folks who built from source?
> > 
> > 
> > > 
> Hi Paul,
> 
> we do not distinguish by platform in spotted data, why should we the 
> application is the same on all platforms. We do have a rough feel for 
> distribution across platforms from the SourceForge download stats. Although 
> many download from the project web site where stats are not kept and those 
> with RPM type Linux distributions may get their fresh versions from COPR and 
> soon from the official repos.
> 
> the version tag is just that, it is the git SHA of the tag that defines 
> the version's sources in the repository:
> 
> https://sourceforge.net/p/wsjt/wsjtx/ci/wsjtx-2.0.0/tree/
> 
> Its there in the Tree address at the top. Again it is the same for all 
> platforms as they are built from the same tag.
> 
> You are correct about builds from the source tarball, the tag is not 
> included, mainly because it may have been patched since we have no control on 
> exactly what is built in that case.
> 
> 73
> Bill
> G4WJS.
> 

Hi Bill,


I'm just generally interested in Linux adoption in amateur radio for 
casual/selfish reasons.  More useful operating information (to me) passed to 
pskreporter is when people take the trouble to describe antennas in WSJT.  But 
that free text field can't be easily normalized for any sort of broad 
statistical use -- such as influencing one's next purchase or installation 
decision.  Mainly I'm just very grateful that you can tell at a glance whether 
a band is open.


73, KD0KZE / Paul
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] TX function lost, then have Task Manager problem

[bergeracb--- via wsjt-devel]

Thanks for the responces to the problem. Sorry for you guys but glad I am not 
alone.The CAT seems to be working just fine 6700 goes into Transmit (RED light) 
and wsjt-x indicatesa message is being sent but DAX shows no audio. 15 seconds 
later RED light goes out. Itdoes seem to be related to the time of being on 
without transmitting, just monitoring, as it isusually after one or more hours 
before it gets noticed. But something in wsjt-x must change or it would not go 
into background tasks. Probably changes just after hitting the mouse to enable 
TX.Al,  N4ABby the way this is a great program for old guys whose CW 
ears/fingers are not working that well anymore.In a message dated 12/13/2018 
10:54:50 Eastern Standard Time, geo...@molnar.tv writes:

FWIW, Using a Flex 6600 and MacOS Mojave, xDAX and xCAT - no problems like 
those reported below. CPU usage is in line with previous versions, CAT and DAX 
operation, even via SmartLink, work smoothly.
Geo/KF2T


On Dec 13, 2018, at 10:27 AM, Al  wrote:


I also have seen the problem and have come to believe that it related the CAT.. 
If I use a traditional CAT ( comport) with Kenwood TS480, I do not have this 
problem. If is use the Flex interface for CAT  this problem returns.. 
You should also note that the CPU usage for the WSJT task is about 10 times 
normal, which might indicate some kind of looping fault in the program.

AL, K0VM

On 12/12/2018 2:53 PM, bergeracb--- via wsjt-devel wrote:Have not seen my 
problem listed yet, so I will try to explain what I see.
Every once in a while operating, the TX function stops working. The Transmitter 
goes into transmit but there is no audio drive so no RF is produced. WSJT-X 
thinks it is working. If I shut down WSJT-X and try to restart the program I 
get the message that their is another instanceof WSJT-X running and the program 
won't start. Checking the task manager under the Running APPS shows no WSJT-X 
app listed.However if I look in the Running BACKGROUND tasks, WSJT-X
has been moved from the APPS to the BACKGROUND tasks.using END TASK there and 
then I can restart the program and use the transmitter again. Can't decide if 
it is a WSJT-X problem or aFLEX 6700 and DAX problem. but I have tried shutting 
 down andrestarting DAX several times without any success. Of course 
shuttingdown and restarting the 6700 (after the background WSJT-X task is 
closed)  also fixes the problem.  I'm wondering if any of the other
Flex owner see this problem? I have the work around so right now it is just a 
nuisance.73 Al Berger N4AB

___
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] Multiple QSO B4 "problem"

[Attila Kocis]

Here the next one:
[cid:image001.png@01D49329.0BCB92E0]

No other station is involved.
Call 1st is active here, I'm only calling CQ.
I did not click any callsing.
When I am sending RR73 "Enable TX" goes off and the log prompt appears.
I click OK to log the qso and enable the "Enable TX" button again that he can 
call CQ again when QSO is over.

This happens several times a day This was the 5th appearance today and I 
have been qrv only 3 or 4 hours today.
I don't think this is an coincidence.

73
Attila

Von: Bill Somerville 
Gesendet: Donnerstag, 13. Dezember 2018 18:32
An: wsjt-devel@lists.sourceforge.net
Betreff: Re: [wsjt-devel] Multiple QSO B4 "problem"

On 13/12/2018 15:51, Attila Kocis wrote:

we (me and dg3ncz) are using v2.0 with the special callsign DF1000ZEIL on all 
Bands.



We saw that if often happens, that the same station is calling us several times 
in series.

So making a QSO, sending RR73 and and get a CQ CALL as response, so the qso is 
logged again.

It reapeats if no one stops this.

So I made today a qso wit one station 2 times and stopped the 3rd time he 
called.



This is the last appearance of this behavior:

[cid:image002.png@01D49329.0BCB92E0]



There are experienced FT8 users, so I don't think they do something wrong.



For any reason some stations are not replying with 73, but with a new CQ-answer.



Any Ideas? Maybe our call too long?

HI Attila,

it looks like "Call 1st" is being triggered when it should not be. I think it 
would have been ok if you had double-clicked the message:

 EU1FQ

at 154015 when EU1FQ tried to tail-end you QSO with DL1NEO.

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

Re: [wsjt-devel] WSJT-X versions distribution as per: https://pskreporter.info/cgi-bin/pskstats.pl

[Bill Somerville]

On 13/12/2018 18:38, Paul Bramscher wrote:


Is it possible to infer operating system from the version "signature" 
as reported on pskreporter?  I see that the heaviest example of 2.0.0 
usage is "WSJT-X v2.0.0 784f75".  Judging from the file download stats 
on SourceForge, I would presume that to be the Windows build/release?



Only a few dozen of us are showing up concisely as "WSJT-X v2.0.0".  
Again judging from the download activity (and my own case) I would 
presume these are folks who built from source?




Hi Paul,

we do not distinguish by platform in spotted data, why should we the 
application is the same on all platforms. We do have a rough feel for 
distribution across platforms from the SourceForge download stats. 
Although many download from the project web site where stats are not 
kept and those with RPM type Linux distributions may get their fresh 
versions from COPR and soon from the official repos.


the version tag is just that, it is the git SHA of the tag that defines 
the version's sources in the repository:


https://sourceforge.net/p/wsjt/wsjtx/ci/wsjtx-2.0.0/tree/

Its there in the Tree address at the top. Again it is the same for all 
platforms as they are built from the same tag.


You are correct about builds from the source tarball, the tag is not 
included, mainly because it may have been patched since we have no 
control on exactly what is built in that case.


73
Bill
G4WJS.

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

Re: [wsjt-devel] Question on UDP message in v2

[F6BHK]

clear. thanks a million Bill for the info.
cheers
serge

Envoyé de mon iPad

> Le 13 déc. 2018 à 19:16, Bill Somerville  a écrit :
> 
>> On 13/12/2018 17:37, F6BHK wrote:
>> Hello,
>> 
>> A quick question on "Status" UDP messages sent by WSJT-X v2.
>> 
>> WSJT sent me a message where the length of the DXCall is -1. This is new for 
>> me: I didn't notice this behavior in v 1.9.1.
>> 
>> Here is an example of the frame after a conversion to hex :
>> 
>> [000b57534a542d58202d207632009aa9c346543800032d313500034654380105dc05dc0005463642484b00064a4e3234697800]
>>  
>> 
>> See after the mode (FT8) I have , then follows the report in UTF8 
>> format.
>> 
>> It looks to me I should have received a UTF8 string instead of . 
>> Well I might have misinterpreted the NetworkMessage.hpp contents where 
>> DXCall is UTF8 formatted between the mode and the report.
>> 
>> Or is it a way to deal with empty string?
>> 
>> Thanks for your help
>> 
>> Cheers
>> 
>> Serge
> 
> Hi Serge,
> 
> as documented here http://doc.qt.io/qt-5/datastreamformat.html the 
> serialization of a QString variable can have a length of 0x (it is 
> unsigned) and that signifies a null value. You may wish to treat zero-length 
> and null strings as equivalent as mentioned in the documentation here: 
> https://sourceforge.net/p/wsjt/wsjtx/ci/master/tree/NetworkMessage.hpp#l42 in 
> the second paragraph down.
> 
> A null or empty DX Call field in s a status update simply means the DX Call 
> field is empty or has just been cleared.
> 
> 73
> Bill
> G4WJS.
> 
> 
> 
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel



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

Re: [wsjt-devel] WSJT-X versions distribution as per: https://pskreporter.info/cgi-bin/pskstats.pl

[Paul Bramscher]

> On 13/12/2018 15:07, Marco Calistri wrote:
> 
> > > 
> > Interesting result (in the attached file)
> > 
> > -- 73 de Marco, PY1ZRJ
> > 
> > > 
> Hi Marco,
> 
> I assume that is derived from the stats page of PSKReporter.info, you 
> should be aware that there are some skews in that data source. It tends to 
> double report for a while after a station switches versions, I assume because 
> records sent by users of old versions are kept for a while and still count 
> even after they have upgraded. There are also an unknown number of users who 
> may never have enabled PSKReporter spotting (only the spotting station record 
> has version used data) and others may switch it off or not have Internet 
> connectivity.
> 
> Thanks for the data.
> 
> 73
> Bill
> G4WJS.
> 


Is it possible to infer operating system from the version "signature" as 
reported on pskreporter?  I see that the heaviest example of 2.0.0 usage is 
"WSJT-X v2.0.0 784f75".  Judging from the file download stats on SourceForge, I 
would presume that to be the Windows build/release?


Only a few dozen of us are showing up concisely as "WSJT-X v2.0.0".  Again 
judging from the download activity (and my own case) I would presume these are 
folks who built from source?


Thanks again, Bill, for the e-mail exchanges a few weeks ago re:Debian.  I've 
successfully built all the RC's and now the final release, for Debian 9.6 
"stretch" (the current version) without trouble.  I sort of emulated the old 
JTSDK's directory layout, and can have multiple versions compiled, making 
allowance for future minor dot releases.  This way I can revert back to an 
older 2.x if I encounter future issues without having to rebuild anything.


73, KD0KZE / Paul
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] wsjt-devel Digest, Vol 58, Issue 232

[Al Pawlowski]

Can not remember the specific thing I was doing when it bugged me last - 
probably experimenting with virtual audio, and radio, connection changes. In 
any case, it seems to me that locking the program is overkill for the 
triggering condition. 


Al Pawlowski, K6AVP
Los Osos, CA USA



> Date: Thu, 13 Dec 2018 17:59:36 +
> From: Bill Somerville mailto:g4...@classdesign.com>>
> To: wsjt-devel@lists.sourceforge.net 
> Subject: Re: [wsjt-devel] Rig Connection Warning Window Suggestion
> Message-ID: <8d36dcd9-87f3-eaf0-553f-4d4db095d...@classdesign.com 
> >
> Content-Type: text/plain; charset=utf-8; format=flowed
> 
> On 13/12/2018 17:52, Al Pawlowski wrote:
>> I would like to see the Rig Connection Warning window functionality 
>> changed so that it can be closed/dismissed without closing the whole 
>> program if a rig connection problem is not fixed. At times, the 
>> current ?shutdown or lockup only? operation can be pretty annoying.
>> 
>> 
>> Al Pawlowski, K6AVP
>> Los Osos, CA USA
> 
> Hi Al,
> 
> that's what the "Ok" button is for, it takes you back to the setting 
> page where you can fix the problem. What else would you want to do?
> 
> 73
> Bill

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

Re: [wsjt-devel] Question on UDP message in v2

[Bill Somerville]

On 13/12/2018 17:37, F6BHK wrote:

Hello,

A quick question on "Status" UDP messages sent by WSJT-X v2.

WSJT sent me a message where the length of the DXCall is -1. This is 
new for me: I didn't notice this behavior in v 1.9.1.


Here is an example of the frame after a conversion to hex :

[000b57534a542d58202d207632009aa9c346543800032d313500034654380105dc05dc0005463642484b00064a4e3234697800] 



See after the mode (FT8) I have , then follows the report in 
UTF8 format.


It looks to me I should have received a UTF8 string instead of 
. Well I might have misinterpreted the NetworkMessage.hpp 
contents where DXCall is UTF8 formatted between the mode and the report.


Or is it a way to deal with empty string?

Thanks for your help

Cheers

Serge 


Hi Serge,

as documented here http://doc.qt.io/qt-5/datastreamformat.html the 
serialization of a QString variable can have a length of 0x (it 
is unsigned) and that signifies a null value. You may wish to treat 
zero-length and null strings as equivalent as mentioned in the 
documentation here: 
https://sourceforge.net/p/wsjt/wsjtx/ci/master/tree/NetworkMessage.hpp#l42 
in the second paragraph down.


A null or empty DX Call field in s a status update simply means the DX 
Call field is empty or has just been cleared.


73
Bill
G4WJS.



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

Re: [wsjt-devel] Patch for wsjt_log.adi file last line blank/empty

[Bill Somerville]

On 13/12/2018 17:49, avt wrote:
I periodically submit an .adi file manually to LoTW. I create that 
file from the wsjt_log.adi file, which I have marked with a blank line 
(a CR/LF) to show the last place I have previously excerpted QSOs for 
submission.


The problem is that v2.0.0 GA now objects to that blank line at the 
end of the wsjt_log.adi file at startup.


The patch is *very* simple: Detect end-of-file, stop processing, 
allowing the last line(s) to be blank. See below.


73
Andy
K9AVT
Wyoming USA


Hi Andy,

thanks for the patch, that issue is already resolved for the next 
release, in fact the ADIF parsing has been relaxed considerably since at 
least one logging program spits out very dubious ADIF records. The fail 
on white space at the end was a defect since it is perfectly legal ADIF 
format.


Don't let this rejection put you off submitting other patches, they are 
always welcome.


73
Bill
G4WJS.



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

[wsjt-devel] Patch for wsjt_log.adi file last line blank/empty

[avt]

I periodically submit an .adi file manually to LoTW. I create that file
from the wsjt_log.adi file, which I have marked with a blank line (a CR/LF)
to show the last place I have previously excerpted QSOs for submission.

The problem is that v2.0.0 GA now objects to that blank line at the end of
the wsjt_log.adi file at startup.

The patch is *very* simple: Detect end-of-file, stop processing, allowing
the last line(s) to be blank. See below.

73
Andy
K9AVT
Wyoming USA
-
Author: k9avt 
Date:   Wed Dec 12 17:32:17 2018 -0700

Allow last line(s) of .adi file to be blank

diff --git a/logbook/WorkedBefore.cpp b/logbook/WorkedBefore.cpp
index 160e1fa8..7bbaf146 100644
--- a/logbook/WorkedBefore.cpp
+++ b/logbook/WorkedBefore.cpp
@@ -320,6 +320,10 @@ namespace
   }
   }
 while ((end_position = buffer.indexOf ("", 0,
Qt::CaseInsensitive)) < 0 && !in.atEnd ());
+if (in.atEnd ())//avt 12/13/18 prevent "Invalid ADIF
record" case
+  {
+break;
+  }
 if (end_position < 0)
   {
 throw LoaderException (std::runtime_error {"Invalid
ADIF record starting at: " + buffer.left (40).toStdString ()});
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Message aggregator

[Bill Somerville]

On 13/12/2018 17:43, ai...@use.startmail.com wrote:
Wow. I really bombed this one. Never occurred to me that someone might 
mistake my opinion of the sourceforge "mailman" interface as a slur 
against the development team or its efforts. In retrospect, I did not 
specify WHICH interface, and I must take 100% responsibility for that. 
That is utterly mea culpa and I do hope you'll accept an apology for 
the words that caused this misunderstanding. I assure you that I have 
nothing but respect for the entire team. With utmost sincerity: I'm 
sorry.


Hi Jim,

don't worry, Joe will not take offence once he realized he too 
misunderstood, hi hi.


Like everything else on the web Google indexes this list. You can use 
Google to search the list by prefixing your search like this:


site:https://sourceforge.net/p/wsjt/mailman/wsjt-devel message_aggregator

Try it out, you may be pleasantly surprised. Once you find a relevant 
post you can navigate the containing message thread using the mailman 
web service.


73
Bill
G4WJS.



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

Re: [wsjt-devel] Rig Connection Warning Window Suggestion

[Bill Somerville]

On 13/12/2018 17:52, Al Pawlowski wrote:
I would like to see the Rig Connection Warning window functionality 
changed so that it can be closed/dismissed without closing the whole 
program if a rig connection problem is not fixed. At times, the 
current “shutdown or lockup only” operation can be pretty annoying.



Al Pawlowski, K6AVP
Los Osos, CA USA


Hi Al,

that's what the "Ok" button is for, it takes you back to the setting 
page where you can fix the problem. What else would you want to do?


73
Bill
G4WJS.



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

[wsjt-devel] Rig Connection Warning Window Suggestion

[Al Pawlowski]

I would like to see the Rig Connection Warning window functionality changed so 
that it can be closed/dismissed without closing the whole program if a rig 
connection problem is not fixed. At times, the current “shutdown or lockup 
only” operation can be pretty annoying.


Al Pawlowski, K6AVP
Los Osos, CA USA



> Date: Wed, 12 Dec 2018 15:36:07 -0500
> From: Joe Taylor mailto:j...@princeton.edu>>
> To: WSJT software development  >,
>   Svend Aage Jessen mailto:la6...@savednet.com>>
> Subject: Re: [wsjt-devel] Message box at startup
> 
> 
> Hi Svend,
> 
> . the next program release 
> will no longer bother you with having to make one extra click each time 
> you start the program or select a new Configuration.

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

Re: [wsjt-devel] Message aggregator

[ai4fu]

Actually, I meant this for Joe, not Bill. I think it's time for me to 
bow out with what little dignity I have left. Thank you all for all of 
the assistance and education.


73 de AI4FU(Jim)
 
On Thursday, December 13, 2018 at 12:43 PM, ai...@use.startmail.com 
wrote:

 

Bill,

Wow. I really bombed this one. Never occurred to me that someone 
might mistake my opinion of the sourceforge "mailman" interface as a 
slur against the development team or its efforts. In retrospect, I 
did not specify WHICH interface, and I must take 100% responsibility 
for that. That is utterly mea culpa and I do hope you'll accept an 
apology for the words that caused this misunderstanding. I assure you 
that I have nothing but respect for the entire team. With utmost 
sincerity: I'm sorry.


Jim

 
On Thursday, December 13, 2018 at 10:57 AM, Joe Taylor 
 wrote:

 

Jim --

On 12/13/2018 10:44 AM, ai...@use.startmail.com wrote:
After finding the exe in the bin folder, I searched the online 
guide for
the term "aggregator" and came up empty. A search through the 
mailing

list turns up some hits, but the interface is utterly tedious
... Is that a complete air ball or what?
Please respect that the WSJT-X development group is tiny.  We do 
what we
can manage, in time available.  We document the tools we provide in 
ways

we consider adequate for intended users.

A number of programming-savvy users have found the 
message_aggregator

very useful as an example of using the UDP broadcasts from WSJT-X.

If you find the interface too "utterly tedious", please feel free to
write your own, document it, and contribute it for the benefit of 
others.


-- Joe, K1JT


___
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] Sample rates for legacy modes

[Joe Taylor]

On 12/13/2018 12:19 PM, Conrad PA5Y wrote:
Once upon a time it was recommended that FSK441 and JT65 should use a 44.1kHz sample rate and the newer modes such as MSK144 and FT8 should use 48kHz? What about JT6M? 


WSJT-X *always* requests data sampled at 48 kHz.  That's true for all 
supported modes.  Any other necessary sample rate conversion is done 
within WSJT-X.



Or so we just rely on a sample rate converter for the legacy modes and always 
run 48kHz now? Could one of the developers please advise?


Not sure just what "we just rely on a sample rate converter ...?" means. 
 With WSJT-X it's all transparent to the user.


-- 73, Joe, K1JT


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

Re: [wsjt-devel] Message aggregator

[ai4fu]

Bill,

Wow. I really bombed this one. Never occurred to me that someone might 
mistake my opinion of the sourceforge "mailman" interface as a slur 
against the development team or its efforts. In retrospect, I did not 
specify WHICH interface, and I must take 100% responsibility for that. 
That is utterly mea culpa and I do hope you'll accept an apology for 
the words that caused this misunderstanding. I assure you that I have 
nothing but respect for the entire team. With utmost sincerity: I'm 
sorry.


Jim

 
On Thursday, December 13, 2018 at 10:57 AM, Joe Taylor 
 wrote:

 

Jim --

On 12/13/2018 10:44 AM, ai...@use.startmail.com wrote:
After finding the exe in the bin folder, I searched the online guide 
for
the term "aggregator" and came up empty. A search through the 
mailing

list turns up some hits, but the interface is utterly tedious
... Is that a complete air ball or what?
Please respect that the WSJT-X development group is tiny.  We do what 
we
can manage, in time available.  We document the tools we provide in 
ways

we consider adequate for intended users.

A number of programming-savvy users have found the message_aggregator
very useful as an example of using the UDP broadcasts from WSJT-X.

If you find the interface too "utterly tedious", please feel free to
write your own, document it, and contribute it for the benefit of 
others.


-- Joe, K1JT


___
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] Sample rates for legacy modes

[Bill Somerville]

On 13/12/2018 17:19, Conrad PA5Y wrote:

Once upon a time it was recommended that FSK441 and JT65 should use a 44.1kHz 
sample rate and the newer modes such as MSK144 and FT8 should use 48kHz? What 
about JT6M? Or so we just rely on a sample rate converter for the legacy modes 
and always run 48kHz now? Could one of the developers please advise?

Regards

Conrad PA5Y


Hi Conrad,

it is not so much the modes but the application used.

WSJT uses an 11025 Hz base rate so 44100 Hz sample rate is appropriate 
as that divides down without fractional remainders.


WSJT-X uses a 12000 Hz base rate so 48000 Hz, 96000Hz, or 192000 Hz are 
all suitable for the for the same reason.


Using 44100 Hz with WSJT-X or 48000 Hz with WSJT will work (I think - 
definitely for WSJT-X) but there will be small rounding errors in the 
sample rate conversion which equate to noise or other distortion and you 
don't want that when you are interested in the weakest signals.


73
Bill
G4WJS.



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

[wsjt-devel] Sample rates for legacy modes

[Conrad PA5Y]

Once upon a time it was recommended that FSK441 and JT65 should use a 44.1kHz 
sample rate and the newer modes such as MSK144 and FT8 should use 48kHz? What 
about JT6M? Or so we just rely on a sample rate converter for the legacy modes 
and always run 48kHz now? Could one of the developers please advise?

Regards

Conrad PA5Y

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

[wsjt-devel] Multiple QSO B4 "problem"

[Attila Kocis]

Hi again



we (me and dg3ncz) are using v2.0 with the special callsign DF1000ZEIL on all 
Bands.



We saw that if often happens, that the same station is calling us several times 
in series.

So making a QSO, sending RR73 and and get a CQ CALL as response, so the qso is 
logged again.

It reapeats if no one stops this.

So I made today a qso wit one station 2 times and stopped the 3rd time he 
called.



This is the last appearance of this behavior:

[cid:image001.png@01D49304.0D8C0760]



There are experienced FT8 users, so I don't think they do something wrong.



For any reason some stations are not replying with 73, but with a new CQ-answer.



Any Ideas? Maybe our call too long?



73

Attila dl1nux


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

Re: [wsjt-devel] Save Directory filling up?

[Saku]

Bill Somerville kirjoitti 13.12.2018 klo 16.21:
I recommend that you add an item to your monthly housekeeping  to do 
list (LoTW uploads, QSL cards, dust the shack, click 
"Menu->File->Delete all *.wav & *.c2 files in SaveDir", ...). You 
could even use the o/s scheduler application to run a script or batch 
file to do this automatically.


If you are concerned about SSD wear (personally I wouldn't be) then 
you should have a spinning disk on your system as well and you can 
direct WSJT-X for save .WAV files in a directory on that.


73
Bill
G4WJS.


Bill's idea to use scheduler for cleaning is very good (with windows) . 
For Linux the same is user crontab.


Sometimes you might be interested to replay some of decodings. Then best 
selection is "save decoded". It makes lot of files but using 
scheduler/crontab you can limit this.


I'm using this with linux:

cd ~/.local/share/WSJT-X/save/;eval $(find *.wav -mtime +2 -type f | awk 
'{print "/bin/rm -f "$1}')


When running timed via crontab (hourly, could be daily if crontab runs 
"missed" jobs when starting up) it will keep today's and 2 days old 
files, but delete all older ones.

It can also be used from command line.

I have used SSD with this PC now about 3 years running all kind of 
programs including wsjt-x, logging, fldigi, programming etc. SSDs seems 
to be rather long-lived. Just remember to do full backups few times a 
year and email. documents etc. backup more often. (Same as with all HDs).
In my server PC I use spinning HD because it is running all the time. 
SSD is best if you shut down PC daily. Booting up is lot more faster.


--
Saku
OH1KH



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

Re: [wsjt-devel] WSJT-X versions distribution as per: https://pskreporter.info/cgi-bin/pskstats.pl

[Marco Calistri]

Il 13/12/18 14:36, Bill Somerville ha scritto:
> On 13/12/2018 16:28, Marco Calistri wrote:
>> Also I discovered some "ACME LABS ONLY" version used by K1JT and K9AN
>> ;-)   WSJT-X v2.0.1-rc1 e76f33
> 
> Hi Marco,
> 
> we do do real testing before releasing new versions and bug fixes ;)
> 
> 73
> Bill
> G4WJS.
> 

Many KUDOS to all of you at dev-team!
-- 

73 de Marco, PY1ZRJ


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

Re: [wsjt-devel] WSJT-X versions distribution as per: https://pskreporter.info/cgi-bin/pskstats.pl

[Marco Calistri]

Il 13/12/18 13:31, Bill Somerville ha scritto:
> On 13/12/2018 15:07, Marco Calistri wrote:
>> Interesting result (in the attached file)
>>
>> -- 73 de Marco, PY1ZRJ
> 
> Hi Marco,
> 
> I assume that is derived from the stats page of PSKReporter.info, you
> should be aware that there are some skews in that data source. It tends
> to double report for a while after a station switches versions, I assume
> because records sent by users of old versions are kept for a while and
> still count even after they have upgraded. There are also an unknown
> number of users who may never have enabled PSKReporter spotting (only
> the spotting station record has version used data) and others may switch
> it off or not have Internet connectivity.
> 
> Thanks for the data.
> 
> 73
> Bill
> G4WJS.

Hi Bill,

Thanks again for the clarification, yes undoubtedly these results are
not representing the "real life" regarding WSJT-X usage by version, in
any case it is interesting to notice how much version 1.91 is still
resulting the top used around the globe.

As per PSKReporter.info states, the retention of these information last
7 days, I would like to come back there in two or more weeks to see if
version 2.0 is still behind 1.91 in the list.

Also I discovered some "ACME LABS ONLY" version used by K1JT and K9AN
;-)  WSJT-X v2.0.1-rc1 e76f33

-- 

73 de Marco, PY1ZRJ

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

Re: [wsjt-devel] Message aggregator

[Joe Taylor]

Jim --

On 12/13/2018 10:44 AM, ai...@use.startmail.com wrote:
After finding the exe in the bin folder, I searched the online guide for 
the term "aggregator" and came up empty. A search through the mailing 
list turns up some hits, but the interface is utterly tedious
... Is that a complete air ball or what? 


Please respect that the WSJT-X development group is tiny.  We do what we 
can manage, in time available.  We document the tools we provide in ways 
we consider adequate for intended users.


A number of programming-savvy users have found the message_aggregator 
very useful as an example of using the UDP broadcasts from WSJT-X.


If you find the interface too "utterly tedious", please feel free to 
write your own, document it, and contribute it for the benefit of others.


-- Joe, K1JT


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

Re: [wsjt-devel] Message aggregator

[Bill Somerville]

On 13/12/2018 15:44, ai...@use.startmail.com wrote:
After finding the exe in the bin folder, I searched the online guide 
for the term "aggregator" and came up empty. A search through the 
mailing list turns up some hits, but the interface is utterly tedious. 
I was playing with things I probably should keep my nose out of and 
found that when first started, the message aggregator has a window 
with a field named "temporary grid". Can anyone shed any light on 
this? My impression is that it can send a temporary grid to WSJT-X for 
"use this grid this time only until program exits" so that the 
settings page does not have to be changed. Is that a complete air ball 
or what? I can make use of this if it is what I think, but I can't 
find any actual usage documentation.


Any help/links at all highly appreciated.

73 de AI4FU(Jim)


Hi Jim,

the two applications message_aggregator and udp_daemon are built 
versions of some reference source code intended for developers who might 
make use of the WSJT-X UDP message protocol in their applications. The 
message_aggregator in particular exercises every facet of the message 
protocol, neither are intended to be useful applications, they are just 
a vehicle for demonstrating the code used to participate in the protocol.


The temporary grid field is as you guess, the message that is used to 
set that is documented here: 
https://sourceforge.net/p/wsjt/wsjtx/ci/master/tree/NetworkMessage.hpp#l349 
along with all of the WSJT-X message protocol documentation in that file.


73
Bill
G4WJS.



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

Re: [wsjt-devel] TX function lost, then have Task Manager problem

[George J. Molnar]

FWIW, Using a Flex 6600 and MacOS Mojave, xDAX and xCAT - no problems like 
those reported below. CPU usage is in line with previous versions, CAT and DAX 
operation, even via SmartLink, work smoothly.

Geo/KF2T

> On Dec 13, 2018, at 10:27 AM, Al  wrote:
> 
> I also have seen the problem and have come to believe that it related the 
> CAT.. 
> If I use a traditional CAT ( comport) with Kenwood TS480, I do not have this 
> problem. If is use the Flex interface for CAT  this problem returns.. 
> You should also note that the CPU usage for the WSJT task is about 10 times 
> normal, which might indicate some kind of looping fault in the program.
> 
> AL, K0VM
> 
> On 12/12/2018 2:53 PM, bergeracb--- via wsjt-devel wrote:
>> Have not seen my problem listed yet, so I will try to explain what I see.
>> Every once in a while operating, the TX function stops working. The
>> Transmitter goes into transmit but there is no audio drive so no RF is
>> produced. WSJT-X thinks it is working. If I shut down WSJT-X and try
>> to restart the program I get the message that their is another instance
>> of WSJT-X running and the program won't start. Checking the task
>> manager under the Running APPS shows no WSJT-X app listed.
>> However if I look in the Running BACKGROUND tasks, WSJT-X
>> has been moved from the APPS to the BACKGROUND tasks.
>> using END TASK there and then I can restart the program and use
>> the transmitter again. Can't decide if it is a WSJT-X problem or a
>> FLEX 6700 and DAX problem. but I have tried shutting  down and
>> restarting DAX several times without any success. Of course shutting
>> down and restarting the 6700 (after the background WSJT-X task is
>> closed)  also fixes the problem.  I'm wondering if any of the other
>> Flex owner see this problem? I have the work around so right now
>> it is just a nuisance.
>> 73 Al Berger N4AB
>> 
>> 

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

[wsjt-devel] Message aggregator

[ai4fu]

After finding the exe in the bin folder, I searched the online guide 
for the term "aggregator" and came up empty. A search through the 
mailing list turns up some hits, but the interface is utterly tedious. 
I was playing with things I probably should keep my nose out of and 
found that when first started, the message aggregator has a window with 
a field named "temporary grid". Can anyone shed any light on this? My 
impression is that it can send a temporary grid to WSJT-X for "use this 
grid this time only until program exits" so that the settings page does 
not have to be changed. Is that a complete air ball or what? I can make 
use of this if it is what I think, but I can't find any actual usage 
documentation.


Any help/links at all highly appreciated.

73 de AI4FU(Jim)
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] WSJT-X versions distribution as per: https://pskreporter.info/cgi-bin/pskstats.pl

[Bill Somerville]

On 13/12/2018 15:07, Marco Calistri wrote:

Interesting result (in the attached file)

-- 73 de Marco, PY1ZRJ


Hi Marco,

I assume that is derived from the stats page of PSKReporter.info, you 
should be aware that there are some skews in that data source. It tends 
to double report for a while after a station switches versions, I assume 
because records sent by users of old versions are kept for a while and 
still count even after they have upgraded. There are also an unknown 
number of users who may never have enabled PSKReporter spotting (only 
the spotting station record has version used data) and others may switch 
it off or not have Internet connectivity.


Thanks for the data.

73
Bill
G4WJS.

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

Re: [wsjt-devel] TX function lost, then have Task Manager problem

[Al]

I also have seen the problem and have come to believe that it related 
the CAT..
If I use a traditional CAT ( comport) with Kenwood TS480, I do not have 
this problem. If is use the Flex interface for CAT  this problem returns..
You should also note that the CPU usage for the WSJT task is about 10 
times normal, which might indicate some kind of looping fault in the 
program.


AL, K0VM

On 12/12/2018 2:53 PM, bergeracb--- via wsjt-devel wrote:

Have not seen my problem listed yet, so I will try to explain what I see.
Every once in a while operating, the TX function stops working. The
Transmitter goes into transmit but there is no audio drive so no RF is
produced. WSJT-X thinks it is working. If I shut down WSJT-X and try
to restart the program I get the message that their is another instance
of WSJT-X running and the program won't start. Checking the task
manager under the Running APPS shows no WSJT-X app listed.
However if I look in the Running BACKGROUND tasks, WSJT-X
has been moved from the APPS to the BACKGROUND tasks.
using END TASK there and then I can restart the program and use
the transmitter again. Can't decide if it is a WSJT-X problem or a
FLEX 6700 and DAX problem. but I have tried shutting  down and
restarting DAX several times without any success. Of course shutting
down and restarting the 6700 (after the background WSJT-X task is
closed)  also fixes the problem.  I'm wondering if any of the other
Flex owner see this problem? I have the work around so right now
it is just a nuisance.
73 Al Berger N4AB




___
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] problems with Configurations in wsjtx-2.0.0

[Bill Somerville]

On 13/12/2018 15:07, Rich Griffiths wrote:
When I encountered this behavior, I checked the WSJT-X.ini file. I 
found that some of the new Configuration entries were in the file, but 
not all.  And there were a few new entries that had %26 in the name.


I tried deleting the bogus entries from the file, but the program just 
put similar ones back the next time I ran it.


Hi Rich,

the %26 characters are ok, they would be & characters since the Qt 
settings facility URL encodes keys and %26 is the URL encoded form for a 
& character. & characters are legal in configuration names, they will 
make an key accelerator for the following character (shown by an 
underline of the accelerator character), if you want a real & in a 
configuration name then you must type && and that will escape the 
accelerator function leaving just a & printed.


When I have seen this defect happen it seems to be other WSJT-X menu 
entry text that ends up in the configuration keys, I have no idea why or 
how but he configuration switching does some quite complex processing to 
re-write the whole of the settings file so anything is possible. So far 
I have not found a way to reliably reproduce the issue so I can work out 
where it is going wrong.


73
Bill
G4WJS.



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

Re: [wsjt-devel] problems with Configurations in wsjtx-2.0.0

[Rich Griffiths]

Bill:

When I encountered this behavior, I checked the WSJT-X.ini file. I found 
that some of the new Configuration entries were in the file, but not 
all.  And there were a few new entries that had %26 in the name.


I tried deleting the bogus entries from the file, but the program just 
put similar ones back the next time I ran it.


73

... Rich   W2RG


On 12/13/2018 09:35 AM, Bill Somerville wrote:

On 13/12/2018 13:56, Marco Calistri wrote:

Some volunteer can give a check, I bet the configuration settings are
not stored as expected.


Hi Marco,

if you are concerned about configurations becoming corrupted after an 
upgrade you can always backup the settings, it is all in a single 
file, WSJT-X.ini for the default instance (started with no '-r' 
option). On Linux it is in the configuration directory which is 
~/.config/


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

[wsjt-devel] WSJT-X versions distribution as per: https://pskreporter.info/cgi-bin/pskstats.pl

[Marco Calistri]

Interesting result (in the attached file)

-- 

73 de Marco, PY1ZRJ


WSJT-X_versions.ods
Description: WSJT-X_versions.ods
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] problems with Configurations in wsjtx-2.0.0

[Marco Calistri]

Il 13/12/18 12:35, Bill Somerville ha scritto:
> On 13/12/2018 13:56, Marco Calistri wrote:
>> Some volunteer can give a check, I bet the configuration settings are
>> not stored as expected.
> 
> Hi Marco,
> 
> if you are concerned about configurations becoming corrupted after an
> upgrade you can always backup the settings, it is all in a single file,
> WSJT-X.ini for the default instance (started with no '-r' option). On
> Linux it is in the configuration directory which is ~/.config/
> 
> 73
> Bill
> G4WJS.

Hi Bill,

Thanks for the guideline, in any case I saved a *.ini file as backup,
just in case.


-- 

73 de Marco, PY1ZRJ

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

Re: [wsjt-devel] Save Directory filling up?

[Black Michael via wsjt-devel]

I think Bill's answer is more likelybut you should only see one file for 
every time you close WSJT-X.

But if the virus scanner has the file open for reading when WSJT-X tries to 
delete it the delete will silently fail.
Mike


 

On Thursday, December 13, 2018, 8:32:59 AM CST, Lahra Svare KT9X 
 wrote:  
 
 Hi, Mike,
Thanks for replying with some thoughts. Are you saying that a virus scanner can 
cause wsjtx audio files to be saved to my wsjtx save directory?  Can you 
explain that further?  I can’t imagine that’s possible. But, then again, I 
can’t seem to stop it from happening, so there must be some unusual answer.
73 de KT9X, Flip

Message: 3
Date: Thu, 13 Dec 2018 14:10:18 + (UTC)
From: Black Michael 
To: WSJT software development 
Subject: Re: [wsjt-devel] Save Directory filling up?
Message-ID: <1525311691.3694205.1544710218...@mail.yahoo.com>
Content-Type: text/plain; charset="utf-8"

Everybody should make sure you exclude the WSJT-X configuration directory from 
your virus scanner.? Otherwise it can be reading files and causing such problem 
and just slowing down your system scanning ALL.TXT and such.
Your virus scanner may be causing this problem.
de Mike W9MDB




   On Thursday, December 13, 2018, 8:03:14 AM CST, Lahra Svare KT9X 
 wrote:  

I do not save any audio files. Yet when I go to the save directory it?s always 
full of new wave files I have to delete. I have SAVE set to none, but still 
these files are being saved to the save directory and I have to delete them. 

I read the manual and found no further information to help me. Does anyone know 
how to stop these files or if they just build up on perpetuity?

73 de KT9X 
Flip (Lahra)







Lahra

Sent from Flip’s iPhone

___
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] problems with Configurations in wsjtx-2.0.0

[Bill Somerville]

On 13/12/2018 13:56, Marco Calistri wrote:

Some volunteer can give a check, I bet the configuration settings are
not stored as expected.


Hi Marco,

if you are concerned about configurations becoming corrupted after an 
upgrade you can always backup the settings, it is all in a single file, 
WSJT-X.ini for the default instance (started with no '-r' option). On 
Linux it is in the configuration directory which is ~/.config/


73
Bill
G4WJS.



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

Re: [wsjt-devel] Save Directory filling up?

[Bill Somerville]

On 13/12/2018 13:59, Lahra Svare KT9X wrote:

I do not save any audio files. Yet when I go to the save directory it’s always 
full of new wave files I have to delete. I have SAVE set to none, but still 
these files are being saved to the save directory and I have to delete them.

I read the manual and found no further information to help me. Does anyone know 
how to stop these files or if they just build up on perpetuity?

73 de KT9X
Flip (Lahra)


Hi Flip,

there will always be a few, they should not take too much space. It is 
important for diagnosing issues that .WAV files are always saved to 
disk, for example when they cause a decoder crash. Also it is possible 
to force the retention of the last saved .WAV file using ALT+V even when 
"Menu->Save->None" is selected. For all these reasons the way WSJT-X 
works is that it always writes a .WAV file but deletes it roughly 3/4 of 
the time through the next T/R period if save "None" is selected, if 
"Save decoded" is selected and there were decodes, or if ALT+V is hit 
before deletion is due.


Closing down WSJT-X in the first 3/4 of a T/R period will likely cause 
the last .WAV file not to be saved, and we will not be changing that as 
the reason for the close down may not be user action and may be due to a 
software issue that can be diagnosed using the .WAV file.


I recommend that you add an item to your monthly housekeeping  to do 
list (LoTW uploads, QSL cards, dust the shack, click "Menu->File->Delete 
all *.wav & *.c2 files in SaveDir", ...). You could even use the o/s 
scheduler application to run a script or batch file to do this 
automatically.


If you are concerned about SSD wear (personally I wouldn't be) then you 
should have a spinning disk on your system as well and you can direct 
WSJT-X for save .WAV files in a directory on that.


73
Bill
G4WJS.



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

Re: [wsjt-devel] Save Directory filling up?

[Black Michael via wsjt-devel]

Everybody should make sure you exclude the WSJT-X configuration directory from 
your virus scanner.  Otherwise it can be reading files and causing such problem 
and just slowing down your system scanning ALL.TXT and such.
Your virus scanner may be causing this problem.
de Mike W9MDB


 

On Thursday, December 13, 2018, 8:03:14 AM CST, Lahra Svare KT9X 
 wrote:  
 
 I do not save any audio files. Yet when I go to the save directory it’s always 
full of new wave files I have to delete. I have SAVE set to none, but still 
these files are being saved to the save directory and I have to delete them. 

I read the manual and found no further information to help me. Does anyone know 
how to stop these files or if they just build up on perpetuity?

73 de KT9X 
Flip (Lahra)







Lahra



Sent from Flip’s iPhone




___
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] LOTW file suggestion

[Bill Somerville]

On 13/12/2018 13:55, Black Michael via wsjt-devel wrote:
I really don't think it's dodging the issue to tell the user what they 
need to look at rather than giving them a useless-to-them message.

The same "go look at section XXX of manual" would apply to any SSL link.

I'm not going to hold my breath on lobbying the guv'ment either

The email list had degenerated to insulting people for asking this 
question and it gets VERY annoying to see that behavior to the point 
I'm about ready to unsubscribe.
Seeing this same question and the rude replies for all eternity does 
not appeal to me in the least (or I would imagine to you and Joe where 
some frustration has been noted where people don't search the list or 
read the manual)


de Mike W9MDB


Hi Mike,

sorry, I can't fix the list subscribers, hi hi. I don't have a problem 
with the multiple posts, we will never get users to search prior posts 
while the standard of posting is so low. Everyone posting a question 
should be more aware that the subject they use and the way they ask a 
question is paramount for others that come alone later with the same 
issue. We are considering a "know issues" list on the project web page, 
even that will take a long time to become the source of truth on 
outstanding issues. In this day of instant communications and a 
multitude of social media sites that are largely full of inaccurate 
information there is little we can do but keep answering the questions 
in a single relevant place.


I tend to take the view that there are no stupid questions, just poor 
answers.


P.S. one of my pet hates is videos posted on YouTube or similar which 
are no more than demonstrating running an application for the very first 
time (first time for the author of the video!) yet claiming to be an 
experts view on how to configure and use. Not only are they often full 
on inaccuracies, they rarely get taken down so persist for ever getting 
more and more views spreading the garbage far and wide.


73
Bill
G4WJS.



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

[wsjt-devel] Intra Program Communications Capability for WSJT-X

[Mike]

Hello,

Using the new version 2 and very impressed with it - thanks!

This is just to offer a suggestion for the future. I see people complaining
about the pop-up boxes letting them know about important concerns. Also I
think it's hard-coded into the program and won't go away until a new
version is released. You may want to consider adding a simple one-way
intra-program messaging system (perhaps wrong terminology) such as the one
that the BOINC client uses -

https://boinc.berkeley.edu/

It lets the developers send one-way messages to all the clients anytime
they want, and offers the user a little note -

Notice (1)

at the top of the window letting them know that a message is available to
read. Messages such as "We have a new version available it's time to
upgrade!" :-)

Just a thought thanks for the work you do!

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

Re: [wsjt-devel] Split operation

[Bill Somerville]

On 13/12/2018 08:17, Tom Ramberg via wsjt-devel wrote:

NB! Don't mark the "Split setting" in WSJT-X as RIG or FAKE. Mark as "None" in 
settings.


Hi Tom,

I am surprised that works and it is certainly not a good suggestion for 
all users. I would expect WSJT-X to disable SPLIT on your rig if you 
have CAT control and "Settings->Radio->Split Operating" as "None", it is 
meant to do that and if it isn't then it is a defect!


The only certain way to do this is to disable CAT by having 
"Settings->Radio->Rig" set to "None".


We may extend the working frequency presets in WSJT-X to allow different 
Rx and Tx frequencies at some point. It is not a trivial enhancement, 
not least as to how to show and enter split frequencies on the main 
windows band/frequency control.


73
Bill
G4WJS.



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

[wsjt-devel] Save Directory filling up?

[Lahra Svare KT9X]

I do not save any audio files. Yet when I go to the save directory it’s always 
full of new wave files I have to delete. I have SAVE set to none, but still 
these files are being saved to the save directory and I have to delete them. 

I read the manual and found no further information to help me. Does anyone know 
how to stop these files or if they just build up on perpetuity?

73 de KT9X 
Flip (Lahra)







Lahra



Sent from Flip’s iPhone




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

Re: [wsjt-devel] LOTW file suggestion

[Black Michael via wsjt-devel]

I really don't think it's dodging the issue to tell the user what they need to 
look at rather than giving them a useless-to-them message.The same "go look at 
section XXX of manual" would apply to any SSL link.

I'm not going to hold my breath on lobbying the guv'ment either
The email list had degenerated to insulting people for asking this question and 
it gets VERY annoying to see that behavior to the point I'm about ready to 
unsubscribe.
Seeing this same question and the rude replies for all eternity does not appeal 
to me in the least (or I would imagine to you and Joe where some frustration 
has been noted where people don't search the list or read the manual)
de Mike W9MDB


 

On Thursday, December 13, 2018, 7:04:44 AM CST, Bill Somerville 
 wrote:  
 
 On 13/12/2018 12:42, Black Michael via wsjt-devel wrote:
> May I suggest that if the LOTW color coding option is not checked (and 
> it looks like it defaults to off) that WSJT-X not download the lotw 
> user file.
>
> Otherwise this question about the SSL error is going to go on forever 
> for every new user that downloads WSJT-X.
>
> Then...when it's enabled pop up a box that says "Please read section 
> 3.1 in the Users Guide about the SSL libraries need for this option.
>
> Same thing when an error happens downloading it to cover the bases.
>
> de Mike W9MDB

Mike,

that is dodging the real issue. The OpenSSL libraries are required for 
Qt to access *any* secure Internet URL, it doesn't just apply to the 
LoTW users data file. By putting off the issue as you suggest then 
exactly the problem you cite will happen every time a new Internet 
resource we use switches to secure access only. What we are doing now is 
trying to get as many WSJT-X Windows users into the same place that 
Linux and Mac users are in without having to install an extra package.

The real problem is your Government who insist that they can control the 
use of strong cryptography by imposing export restrictions. You need to 
lobby them for change, not here. If they changed then we could bundle 
OpenSSL libraries in the WSJT-X installer for Windows, Microsoft might 
even abandon the proprietary WinInet module and use OpenSSL themselves. 
Not holding my breath on that last point though.

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] problems with Configurations in wsjtx-2.0.0

[Marco Calistri]

Il 13/12/18 11:35, Bill Somerville ha scritto:
> On 13/12/2018 13:11, Marco Calistri wrote:
>> I have a WSJT-X MS Windows too, but I'm using the Linux version 99% of
>> time.
> 
> Hi Marco,
> 
> did the problem with configurations occur on Windows or on Linux?
> 
> 73
> Bill
> G4WJS.

Bill,

My previous configuration problem report was for WSJT-X RC Linux.

I have not yet tried with WSJT-X GA because it is a bit annoying to set
the configuration parameters again.

>From what I saw I guess this "bug" - if I can call it this way -, is
present at least since version WSJT-X 1.9.

Some volunteer can give a check, I bet the configuration settings are
not stored as expected.

Regards,

-- 

73 de Marco, PY1ZRJ

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

Re: [wsjt-devel] LOTW file suggestion

[Tom Melvin]

All comments noted and from that point of view makes sense.

Tom

P.S.

>> As I said to Mike, lobby your Government, that is what needs fixing.

Well as you and I have the same government and it has a few things on it’s 
plate just now will give that a miss :-)




On 13 Dec 2018, at 13:34, Bill Somerville  wrote:

> On 13/12/2018 13:19, Tom Melvin wrote:
>> Quick question, if the wsjt download site was hosted outside the US then I 
>> believe the export restrictions do not apply - users in the US are importing 
>> the software.
>> 
>> Are there thoughts on this and including the appropriate libraries within 
>> the installer for the future.
>> 
>> Tom
>> 
>> --
>> 
>> 73’s
>> 
>> Tom
>> GM8MJV (IO85)
>> 
>> 
> Hi Tom,
> 
> WSJT-X downloads are hosted on the project web site which is based at 
> Princeton and on SourceForge which has many servers Worldwide including in 
> NA. Giving up either of those resources is not likely to happen, mainly but 
> not solely for cost reasons I expect, SF is free for open source projects 
> like WSJT-X and I suspect the Princeton Physics Dept. server is too.
> 
> Hosting outside NA might be possible if the OpenSSL libraries are 
> "clean-room" developed outside of the U.S., I believe this may be the case 
> but I would have to check.
> 
> There are some projects that do bundle OpenSSL, I believe it is possible to 
> sign various U.S. export documentation to allow that but I would think that 
> doing so would shift responsibility to us to ensure that export restrictions 
> are not broken, a responsibility we do not want to bear, nor any cost in 
> processing such paperwork.
> 
> IMHO this is not worth bothering about, it is easy to install OpenSSL on 
> Windows if your jurisdiction allows it and we give manual workarounds for 
> those that can't, so those in EP or P5 lands etc. (although I haven't seen P5 
> on yet) can use WSJT-X without annoying the US government.
> 
> As I said to Mike, lobby your Government, that is what needs fixing.
> 
> 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] LOTW file suggestion

[Bill Somerville]

On 13/12/2018 13:19, Tom Melvin wrote:

Quick question, if the wsjt download site was hosted outside the US then I 
believe the export restrictions do not apply - users in the US are importing 
the software.

Are there thoughts on this and including the appropriate libraries within the 
installer for the future.

Tom

--

73’s

Tom
GM8MJV (IO85)



Hi Tom,

WSJT-X downloads are hosted on the project web site which is based at 
Princeton and on SourceForge which has many servers Worldwide including 
in NA. Giving up either of those resources is not likely to happen, 
mainly but not solely for cost reasons I expect, SF is free for open 
source projects like WSJT-X and I suspect the Princeton Physics Dept. 
server is too.


Hosting outside NA might be possible if the OpenSSL libraries are 
"clean-room" developed outside of the U.S., I believe this may be the 
case but I would have to check.


There are some projects that do bundle OpenSSL, I believe it is possible 
to sign various U.S. export documentation to allow that but I would 
think that doing so would shift responsibility to us to ensure that 
export restrictions are not broken, a responsibility we do not want to 
bear, nor any cost in processing such paperwork.


IMHO this is not worth bothering about, it is easy to install OpenSSL on 
Windows if your jurisdiction allows it and we give manual workarounds 
for those that can't, so those in EP or P5 lands etc. (although I 
haven't seen P5 on yet) can use WSJT-X without annoying the US government.


As I said to Mike, lobby your Government, that is what needs fixing.

73
Bill
G4WJS.



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

Re: [wsjt-devel] problems with Configurations in wsjtx-2.0.0

[Bill Somerville]

On 13/12/2018 13:11, Marco Calistri wrote:

I have a WSJT-X MS Windows too, but I'm using the Linux version 99% of time.


Hi Marco,

did the problem with configurations occur on Windows or on Linux?

73
Bill
G4WJS.



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

Re: [wsjt-devel] problems with Configurations in wsjtx-2.0.0

[Marco Calistri]

Il 13/12/18 11:04, Bill Somerville ha scritto:
> On 13/12/2018 12:46, Marco Calistri wrote:
>> I faced same issue too and I have already reported here some times ago.
>> (email attached).
>>
>> I suppose it not being a "new-bug" specific for version 2.0 but most
>> likely an "old-bug" which has been always present into the WSJT-X code.
> 
> Hi Marco,
> 
> are you using WSJT-X on MS Windows?
> 
> 73
> Bill
> G4WJS.
> 
> 
> 
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Hi Bill,

I have a WSJT-X MS Windows too, but I'm using the Linux version 99% of time.

Regards,
-- 

73 de Marco, PY1ZRJ

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

Re: [wsjt-devel] LOTW file suggestion

[Tom Melvin]

Bill

Quick question, if the wsjt download site was hosted outside the US then I 
believe the export restrictions do not apply - users in the US are importing 
the software.

Are there thoughts on this and including the appropriate libraries within the 
installer for the future.

Tom

--

73’s

Tom
GM8MJV (IO85)





On 13 Dec 2018, at 13:00, Bill Somerville  wrote:

> On 13/12/2018 12:42, Black Michael via wsjt-devel wrote:
>> May I suggest that if the LOTW color coding option is not checked (and it 
>> looks like it defaults to off) that WSJT-X not download the lotw user file.
>> 
>> Otherwise this question about the SSL error is going to go on forever for 
>> every new user that downloads WSJT-X.
>> 
>> Then...when it's enabled pop up a box that says "Please read section 3.1 in 
>> the Users Guide about the SSL libraries need for this option.
>> 
>> Same thing when an error happens downloading it to cover the bases.
>> 
>> de Mike W9MDB
> 
> Mike,
> 
> that is dodging the real issue. The OpenSSL libraries are required for Qt to 
> access *any* secure Internet URL, it doesn't just apply to the LoTW users 
> data file. By putting off the issue as you suggest then exactly the problem 
> you cite will happen every time a new Internet resource we use switches to 
> secure access only. What we are doing now is trying to get as many WSJT-X 
> Windows users into the same place that Linux and Mac users are in without 
> having to install an extra package.
> 
> The real problem is your Government who insist that they can control the use 
> of strong cryptography by imposing export restrictions. You need to lobby 
> them for change, not here. If they changed then we could bundle OpenSSL 
> libraries in the WSJT-X installer for Windows, Microsoft might even abandon 
> the proprietary WinInet module and use OpenSSL themselves. Not holding my 
> breath on that last point though.
> 
> 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] problems with Configurations in wsjtx-2.0.0

[Bill Somerville]

On 13/12/2018 12:46, Marco Calistri wrote:

I faced same issue too and I have already reported here some times ago.
(email attached).

I suppose it not being a "new-bug" specific for version 2.0 but most
likely an "old-bug" which has been always present into the WSJT-X code.


Hi Marco,

are you using WSJT-X on MS Windows?

73
Bill
G4WJS.



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

Re: [wsjt-devel] 2 Bugs or maybe features?

[Bill Somerville]

On 13/12/2018 12:45, Attila Kocis wrote:


My RTS is high because CAT will not work i fit is not on high. I don’t 
use any interface, it’s a direct serial connection from the TS 2000 to 
the computer.



Hi Attila,

for that you should select "Settings->Radio->Handshake->Hardware", the 
"Force Control Lines" options are only for interface hardware that is 
powered using one of the RTS or DTR signals.


73
Bill
G4WJS.

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

Re: [wsjt-devel] LOTW file suggestion

[Bill Somerville]

On 13/12/2018 12:42, Black Michael via wsjt-devel wrote:
May I suggest that if the LOTW color coding option is not checked (and 
it looks like it defaults to off) that WSJT-X not download the lotw 
user file.


Otherwise this question about the SSL error is going to go on forever 
for every new user that downloads WSJT-X.


Then...when it's enabled pop up a box that says "Please read section 
3.1 in the Users Guide about the SSL libraries need for this option.


Same thing when an error happens downloading it to cover the bases.

de Mike W9MDB


Mike,

that is dodging the real issue. The OpenSSL libraries are required for 
Qt to access *any* secure Internet URL, it doesn't just apply to the 
LoTW users data file. By putting off the issue as you suggest then 
exactly the problem you cite will happen every time a new Internet 
resource we use switches to secure access only. What we are doing now is 
trying to get as many WSJT-X Windows users into the same place that 
Linux and Mac users are in without having to install an extra package.


The real problem is your Government who insist that they can control the 
use of strong cryptography by imposing export restrictions. You need to 
lobby them for change, not here. If they changed then we could bundle 
OpenSSL libraries in the WSJT-X installer for Windows, Microsoft might 
even abandon the proprietary WinInet module and use OpenSSL themselves. 
Not holding my breath on that last point though.


73
Bill
G4WJS.



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

Re: [wsjt-devel] How to get DXCC form cty.dat wsjtx v2.0

[Bill Somerville]

On 13/12/2018 12:40, ja2bqx wrote:

Please tell me the source cord which acquires DXCC Entity from  a callsign 
using cty.dat in wsjtx v2.0.

Logqso.cpp


Hi Nobu san,

you will need a pointer to the LogBook object instance, I suggest you 
change the LogQSO class constructor to take a new argument of type 
'LogBook const *' and store that in a new data member of the same type. 
You would pass _logBook to the LogQSO constructor call in the 
MainWindow member initialization list.


Having made the LogBook object instance available then the call you 
require is:


auto entity_record = m_logbook->countries ().lookup (callsign);

For that you will need to include:

#include "logbook/logbook.h"
#include "logbook/AD1CCty.hpp"

and look in the second of those for the definition of the record 
returned by the lookup call. E.g. you need entity_record.entity_name .


73
Bill
G4WJS.



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

Re: [wsjt-devel] problems with Configurations in wsjtx-2.0.0

[Marco Calistri]

Il 13/12/18 00:02, Rich Griffiths ha scritto:
> I finally got around to installing the GA version of 2.0.0 today. I
> cleaned the system of all old files in the .config, .local, /usr etc.
> directories before starting.  I used the tarball under Debian stretch
> (v9), and it seemed to install without problems using the directions in
> the INSTALL file.
> 
> However, the Configurations are behaving badly.  For example, I cloned
> the Default into a new FT8-HF and an MSK144-6m.  These operations led to
> multiple new listings on the Configuration tab, typically with names
> like  and FT8-  And none of the new items had settings in the
> General, Radio, or Audio tabs.  If I try to delete one, another will pop
> up to take its place.
> 
> What am I missing?
> 
> ... Rich    W2RG

Hello Rich,

I faced same issue too and I have already reported here some times ago.
(email attached).

I suppose it not being a "new-bug" specific for version 2.0 but most
likely an "old-bug" which has been always present into the WSJT-X code.


-- 

73 de Marco, PY1ZRJ
--- Begin Message ---
Hello,

I would have a bug or maybe a unexpected behavior to report to devs.

I was attempting to decode FT8 using WSJT-X RC4 but I had to switch my
previous settings, saved using WSJT-X 1.9.1 with my call-sign - (1.9.1
was using hamlib to manage the CAT) - to default settings because I had
not "rigctld" process on-line (in fact it is being started automatically
by CQRLOG, when I use WSJT-X 1.9.1).

The weird thing is that my saved settings are not there anymore!

If I click on drop-down Configurations menu, I find several options as:

. Default
. Default
. PY1ZRJ
. Default
. PY1ZRJ
. PY1ZRJ
. PY1ZRJ

But by selecting everyone of these in turn, I never get back on my saved
settings "PY1ZRJ" which were using hamlib CAT and serial cable PTT controls.

Regards,

-- 

73 de Marco, PY1ZRJ
--- End Message ---
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] 2 Bugs or maybe features?

[Attila Kocis]

Hi Bill

My RTS is high because CAT will not work i fit is not on high. I don’t use any 
interface, it’s a direct serial connection from the TS 2000 to the computer.

I‘ve now checked "Settings->General->Monitor returns to last used frequency" 
and this sets the mode now correct. But otherwise I never had checked this 
option, worked always without it. I can reproduce this. Everytime I start 
wsjtx, it changed USB to LSB (when USB was active before).
I think it has something to do with the cat connection, because sometimes it is 
bevahing very special. But I just have this in wsjtx. All other software 
programmes are working very well.

But never mind, this option now helpes me a lot.
Thanks again and 73
Attila

Von: Bill Somerville 
Gesendet: Donnerstag, 13. Dezember 2018 13:08
An: wsjt-devel@lists.sourceforge.net
Betreff: Re: [wsjt-devel] 2 Bugs or maybe features?

On 13/12/2018 08:06, Attila Kocis wrote:
The box isn’t checked:
[cid:image001.png@01D492E9.068FCE30]
I can reproduce this by any start of wsjtx.

But I now found the problem I think.
When I start WSJTX, it turns the transceiver into LSB mode, and there are not 
ft8 signals down there 
After selecting a frequency it stays in USB mode correctly.
I am using Kenwood TS2000 with CAT over RS232 cable. It worked great in the 
last versions.
Maybe there was a change in Hamlib?

Hi Attila,

you need to check the "Settings->General->Monitor returns to last used 
frequency" option if you want WSJT-X to set the rig when it starts. This option 
is there to allow starting the application without disturbing the rig.

I note you have RTS forced high on your CAT serial port configuration, does 
your interface require that?

I also note you have not selected one of the active "Settings->Radio->Split 
Operating" options, you will get better performance if you do.

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

[wsjt-devel] LOTW file suggestion

[Black Michael via wsjt-devel]

May I suggest that if the LOTW color coding option is not checked (and it looks 
like it defaults to off) that WSJT-X not download the lotw user file.
Otherwise this question about the SSL error is going to go on forever for every 
new user that downloads WSJT-X.
Then...when it's enabled pop up a box that says "Please read section 3.1 in the 
Users Guide about the SSL libraries need for this option.
Same thing when an error happens downloading it to cover the bases.
de Mike W9MDB
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

[wsjt-devel] How to get DXCC form cty.dat wsjtx v2.0

[ja2bqx]

Hi,

Please tell me the source cord which acquires DXCC Entity from  a callsign 
using cty.dat in wsjtx v2.0.

Logqso.cpp

  // allow auto logging in Fox mode and contests
  accept();
}
  else
{
  show();

 // I'd like to add a code here and acquire Entity in DXCC from 
 // a call sign more than cty.dat.

//For example.
//   JA2BQX  ==> JA
//   4Q1AAA  ==> 4S

}
}


de JA2BQX nobu





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

[wsjt-devel] Request to all subscribers

[Bill Somerville]

Hi All,

please start a new topic when necessary. It is all too common for 
messages sent to be written as replies to an existing message thread 
with a changed title. This practice is not good as those of us with 
threaded e-mail clients will not see your message if we have closed or 
marked as answered the original message thread.


Some background. Whenever you send an email it is given a message ID and 
also it has other IDs referencing the message(s) it is a reply to. This 
is all normally invisible to you, you can reveal this detail by showing 
the full headers. Email clients use these message IDs and link IDs to 
present the conversation threads in a logical tree. Just changing the 
subject line does not start a new message thread. Please don't do that, 
start with a new message and address it to the list address 
(wsjt-devel@lists.sourceforge.net).


73
Bill
G4WJS.



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

Re: [wsjt-devel] 2 Bugs or maybe features?

[Bill Somerville]

On 13/12/2018 08:30, Attila Kocis wrote:


I deinstalled 1.1.1 and installed 1.0.2 light and then it worked 
perfectly.


Version 1.1.1 does not work with WSJTX.

These different numbers are really confusing me…. 


Hi Attila,

the version 1.1 OpenSSL libraries have different names and a different 
calling interface, they are incompatible with the version 1.0.2 
libraries. Both versions can be installed on the same system but only 
the 1.0.2 versions will be used by the Qt libraries that WSJT-X uses for 
secure Internet protocols.


73
Bill
G4WJS.

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

Re: [wsjt-devel] 2 Bugs or maybe features?

[Bill Somerville]

On 13/12/2018 08:06, Attila Kocis wrote:


The box isn’t checked:

I can reproduce this by any start of wsjtx.

But I now found the problem I think.

When I start WSJTX, it turns the transceiver into LSB mode, and there 
are not ft8 signals down there 


After selecting a frequency it stays in USB mode correctly.

I am using Kenwood TS2000 with CAT over RS232 cable. It worked great 
in the last versions.


Maybe there was a change in Hamlib?


Hi Attila,

you need to check the "Settings->General->Monitor returns to last used 
frequency" option if you want WSJT-X to set the rig when it starts. This 
option is there to allow starting the application without disturbing the 
rig.


I note you have RTS forced high on your CAT serial port configuration, 
does your interface require that?


I also note you have not selected one of the active 
"Settings->Radio->Split Operating" options, you will get better 
performance if you do.


73
Bill
G4WJS.

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

Re: [wsjt-devel] 2 Bugs or maybe features?

[Attila Kocis]

Hi Bill,

the SSL issue ….

I installed MS library 2013 32 bit (inly 64bit was installed) and nothing 
changed.
Then I checked the OpenSSL page again and I saw that there are different 
versions for download.
I had downloaded Version 1.1.1a Light and not 1.0.2 light.
I deinstalled 1.1.1 and installed 1.0.2 light and then it worked perfectly.
Version 1.1.1 does not work with WSJTX.
These different numbers are really confusing me…. 

Thanks for your help.
73
Attila

Von: Bill Somerville 
Gesendet: Donnerstag, 13. Dezember 2018 02:26
An: wsjt-devel@lists.sourceforge.net
Betreff: Re: [wsjt-devel] 2 Bugs or maybe features?

Hi Attila,

comments below.

On 12/12/2018 20:24, Attila Kocis wrote:

Hi



I'm using 2.0 GA (on Win10 1803 64bit) now the third day and it works great, 
except of two problems which don't want to go away.



The first is, the SSL/LOTW error message won't disappear, also not after 
installing the SSL Tool which is mentioned in the manual. It still appears on 
every start.
Please refer to the Windows installation instructions in the User 
Guide
 particularly the part about what to do if installing the OpenSSL libraries 
does not fix the issue.






The second is, when I start WSJTX, the waterfall is always empty. No signal can 
be seen there and nothing is decoding. The signals are shown only when I select 
first a frequency in the dropdown menu or go to settings menu and back to 
WSJTX. Then the signals are showing and decoding. This wasn't happening in any 
beta RC version.
Do you have the option "Settings->General->Monitor off at startup" checked? 
That would stop receiving until you clicked "Monitor" or selected a working 
frequency. It is intended to allow you to start WSJT-X without disturbing the 
rig.






73 de dl1nux

Attila

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

Re: [wsjt-devel] Split operation

[Tom Ramberg via wsjt-devel]

Bill, I’ve discussed this with Keijo, and this method of working split also 
worked fine, at least with the FT-1000Mp and FTdx3000. I see no reason why it 
shouldn’t work on any radio with dual vfos:

To operate SPLIT (to work JA) on 160 meters:
In WSJT-X set freq. to 1,908 Mhz - will set ur VFO A to 1,908. Set your VFO B 
to 1.840 Mhz. 
Look at manual to see how operate FT-1000MP or FTdx3000 in "SPLIT-FREQUENCY 
OPERATION" - set it op to TX on VFO B and RX on A. 
In that way WSJT-X thinks it's tx' ing on 1908. 
NB! Don't mark the "Split setting" in WSJT-X as RIG or FAKE. Mark as "None" in 
settings. 

73 de Tom OH6VDA

Sendt fra min iPhone

> 12. des. 2018 kl. 20:10 skrev Bill Somerville :
> 
>> On 12/12/2018 17:45, OG55W wrote:
>> I have tried to find how to operate with split..
>> JA-stations are calling me in 1908 as I am transmitting in 1840, and I do 
>> not hear them as my RX or TX change the frequency.
>> I am not allowed to transmit in 1908.
> 
> Hi Keijo,
> 
> WSJT-X does not support this using CAT control, it conflicts with the way 
> that WSJT-X uses CAT control to clean up Tx signals and extend Tx coverage to 
> at least the Rx pass band.
> 
> You can do what you wish by creating a new configuration 
> ("Menu->Configurations") and in that new configuration turn off CAT control 
> ("Settings->Radio->RIg" as "None"). You can then use SPLIT on your rig just 
> like you would for a CW or phone QSO. Don't forget to set WSJT-X to the 
> correct band so that QSOs get logged on the correct band and PSKReporter 
> spots are accurate. I recommend setting WSJT-X to the Tx dial frequency so 
> that spots are in the JA band segment where the DX is transmitting.
> 
> 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] 2 Bugs or maybe features?

[Attila Kocis]

Hi Bill

The box isn’t checked:
[cid:image001.png@01D492C2.D34656A0]
I can reproduce this by any start of wsjtx.

But I now found the problem I think.
When I start WSJTX, it turns the transceiver into LSB mode, and there are not 
ft8 signals down there 
After selecting a frequency it stays in USB mode correctly.
I am using Kenwood TS2000 with CAT over RS232 cable. It worked great in the 
last versions.
Maybe there was a change in Hamlib?
There are my CAT settings:
[cid:image002.png@01D492C3.2808CB50]

Any idea what this causes?

73
Attila

Von: Bill Somerville 
Gesendet: Donnerstag, 13. Dezember 2018 02:26
An: wsjt-devel@lists.sourceforge.net
Betreff: Re: [wsjt-devel] 2 Bugs or maybe features?

Hi Attila,

comments below.

On 12/12/2018 20:24, Attila Kocis wrote:

Hi



I'm using 2.0 GA (on Win10 1803 64bit) now the third day and it works great, 
except of two problems which don't want to go away.



The first is, the SSL/LOTW error message won't disappear, also not after 
installing the SSL Tool which is mentioned in the manual. It still appears on 
every start.
Please refer to the Windows installation instructions in the User 
Guide
 particularly the part about what to do if installing the OpenSSL libraries 
does not fix the issue.






The second is, when I start WSJTX, the waterfall is always empty. No signal can 
be seen there and nothing is decoding. The signals are shown only when I select 
first a frequency in the dropdown menu or go to settings menu and back to 
WSJTX. Then the signals are showing and decoding. This wasn't happening in any 
beta RC version.
Do you have the option "Settings->General->Monitor off at startup" checked? 
That would stop receiving until you clicked "Monitor" or selected a working 
frequency. It is intended to allow you to start WSJT-X without disturbing the 
rig.






73 de dl1nux

Attila

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