[wsjt-devel] Fwd: TX1 double click does not survive change of configuration

2020-07-13 Thread Peter Sumner
Seems my original send did not make it to the list as it has been extremely quiet for the last 5 days here. Hello Dev team, the function to skip over sending a 'TX1' message is lost when I change configuration to another mode, then come back to the original configuration I started on, in this cas

Re: [wsjt-devel] wsjt x stale lock file error

2020-07-13 Thread Laurie, VK3AMA
On 14/07/2020 7:30 am, Tripp Sanders wrote: I didn’t have jtalert Setup to Auto Start wsjt x but I after uninstalling jtalert and restarting it seems fixed. If JTAlert was not set to auto-start WSJT-X, than JTAlert is not the cause. If JTAlert was set to auto-start WSJT-X that action woul

Re: [wsjt-devel] wsjt x stale lock file error

2020-07-13 Thread Tripp Sanders
I didn’t have jtalert Setup to Auto Start wsjt x but I after uninstalling jtalert and restarting it seems fixed. On Mon, Jul 13, 2020 at 4:25 PM Black Michael via wsjt-devel < wsjt-devel@lists.sourceforge.net> wrote: > JTAlert can autostart programs > > Mike W9MDB > > > > > On Monday, July 13

Re: [wsjt-devel] wsjt x stale lock file error

2020-07-13 Thread Black Michael via wsjt-devel
JTAlert can autostart programs Mike W9MDB On Monday, July 13, 2020, 04:19:31 PM CDT, Tripp Sanders wrote: I looked through the Autoruns and there is  nothing that should be starting it there I also use jtalert. Would that do something? On Mon, Jul 13, 2020 at 4:14 PM Bill Somerv

Re: [wsjt-devel] wsjt x stale lock file error

2020-07-13 Thread Tripp Sanders
I looked through the Autoruns and there is nothing that should be starting it there I also use jtalert. Would that do something? On Mon, Jul 13, 2020 at 4:14 PM Bill Somerville wrote: > Hi Tripp, > > if there is a wsjtx process running after a reboot then something must be > starting it, WSJT-X

Re: [wsjt-devel] wsjt x stale lock file error

2020-07-13 Thread Bill Somerville
Hi Tripp, if there is a wsjtx process running after a reboot then something must be starting it, WSJT-X will not start spontaneously. 73 Bill G4WJS. On 13/07/2020 22:04, Tripp Sanders wrote: I have an icom 718 being controlled directly through wsjt x. it’s been running for at least 3+ hours

Re: [wsjt-devel] wsjt x stale lock file error

2020-07-13 Thread Tripp Sanders
I have an icom 718 being controlled directly through wsjt x. it’s been running for at least 3+ hours after closing the wsjt x And survived 2 reboots. On Mon, Jul 13, 2020 at 3:51 PM Bill Somerville wrote: > On 13/07/2020 21:42, Tripp Sanders wrote: > > I have been having problems with wsjt x hav

Re: [wsjt-devel] wsjt x stale lock file error

2020-07-13 Thread Bill Somerville
On 13/07/2020 21:42, Tripp Sanders wrote: I have been having problems with wsjt x having a stale lock file error after closing the program normally restarting my pc fixes it but it happened and restarting didn’t work. I looked on some stuff online and i tried deleting the lock file but even wit

[wsjt-devel] wsjt x stale lock file error

2020-07-13 Thread Tripp Sanders
I have been having problems with wsjt x having a stale lock file error after closing the program normally restarting my pc fixes it but it happened and restarting didn’t work. I looked on some stuff online and i tried deleting the lock file but even with admin privileges it did not work I then chec

Re: [wsjt-devel] strange response

2020-07-13 Thread Al
Ok... Just wanted to bring it to your attention.. AL, K0VM On 7/13/2020 2:10 PM, Bill Somerville wrote: Hi Frode and Al, OK, I missed that obvious issue. WSJT-X has interpreted the non-standard free text message as containing two calls 'R' and '1W'. This is an unfortunate side effect of allow

Re: [wsjt-devel] strange response

2020-07-13 Thread Al
Yes, but why did my last TX (73) change his call sign to 1W.  I did not change his call sign manually. AL, K0VM On 7/13/2020 12:16 PM, Franz (OE3FVU _ PE0WGA) wrote: He is informing you that his power is 1 Watt. Best 73 Franz - OE3FVU (also PE0WGA, ex-PE3FVU, ex-PA0WGA) /_144MHz DX statio

Re: [wsjt-devel] strange response

2020-07-13 Thread Bill Somerville
Hi Frode and Al, OK, I missed that obvious issue. WSJT-X has interpreted the non-standard free text message as containing two calls 'R' and '1W'. This is an unfortunate side effect of allowing free text messages containing the word 73 to be substitutable with standard 73 messages. I think th

Re: [wsjt-devel] strange response

2020-07-13 Thread Franz (OE3FVU _ PE0WGA)
He is informing you that his power is 1 Watt. Best 73 Franz - OE3FVU (also PE0WGA, ex-PE3FVU, ex-PA0WGA) 144MHz DX stations meet at www.on4kst.com From: Frode Igland Sent: Monday, July 13, 2020 7:02 PM To: WSJT software development Subject: Re: [wsjt-devel] st

Re: [wsjt-devel] strange response

2020-07-13 Thread Frode Igland
In the Log QSO window the call sign is changed from W5KDJ to 1W. Did that happen automatically as that was the "call sign" in the RR73 message that initiated the logging procedure, or is that entered manually by K0VM? 73 Frode LA6VQ man. 13. jul. 2020 kl. 17:56 skrev Bill Somerville : > On 13/0

Re: [wsjt-devel] strange response

2020-07-13 Thread Bill Somerville
On 13/07/2020 16:44, Bill Somerville wrote: On 13/07/2020 16:21, Al wrote: (wsjt-x 2.2.2 Win10 2004 ) FYI.. This sequence ended strangely.. AL, K0VM Hi Al, nothing strange there. You QSO partner acknowledged your report to him, on the third resend with a non-standard message, something he

Re: [wsjt-devel] strange response

2020-07-13 Thread Bill Somerville
On 13/07/2020 16:21, Al wrote: (wsjt-x 2.2.2 Win10 2004 ) FYI.. This sequence ended strangely.. AL, K0VM Hi Al, nothing strange there. You QSO partner acknowledged your report to him, on the third resend with a non-standard message, something he can do as his callsign is sufficiently short

[wsjt-devel] strange response

2020-07-13 Thread Al
(wsjt-x 2.2.2 Win10 2004 ) FYI.. This sequence ended strangely.. AL, K0VM ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Issue: v2.2.2 (and earlier) Invalid Hardware frequency ranges trying to be addressed and the handling of such anomalies #bug

2020-07-13 Thread Stephen VK3SIR
Bill, Ø are you sure you have waited long enough… Absolutely sure. I’ve been sitting on this for around 2 weeks now and have tested almost every combo possible. It has been back tested with 2.2.1 and also with the “model” Hamlib sources from 2.2.1 and 2.2.2… but based around the “master” rep

Re: [wsjt-devel] Issue: v2.2.2 (and earlier) Invalid Hardware frequency ranges trying to be addressed and the handling of such anomalies #bug

2020-07-13 Thread Bill Somerville
On 13/07/2020 10:01, Stephen VK3SIR wrote: Hi Everyone, I have noted that when you select a frequency to operate on that hardware is not capable of then a Hamlib disconnect (i.e. The Settings/Radio configuration widgets) is thrown without any console error messages being recorded. i.e. I r

Re: [wsjt-devel] Bug in FT8 Decoding Timestamp

2020-07-13 Thread Bill Somerville
On 13/07/2020 02:48, David Bean (KC2WUF) via wsjt-devel wrote: I haven't yet figured out what sequence is causing what I am seeing, but there are times when the new FT8 decoding for a new time sequence will timestamp the decodes with the previous decoding timestamp. During Field Day this was fi

[wsjt-devel] Issue: v2.2.2 (and earlier) Invalid Hardware frequency ranges trying to be addressed and the handling of such anomalies #bug

2020-07-13 Thread Stephen VK3SIR
Hi Everyone, I have noted that when you select a frequency to operate on that hardware is not capable of then a Hamlib disconnect (i.e. The Settings/Radio configuration widgets) is thrown without any console error messages being recorded. i.e. I run a FT-897D and an old IC-725 here… With either