Re: [wsjt-devel] Stations with bad clocks

A rubber clock feature would also be very helpful in situations where there is no internet connection available. Was one of the main reasons why I was using JT65-HF Comfort in earlier days. 73 de DG2YCB, Uwe Am 15. Mai 2018 18:19:31 schrieb Rich - K1HTV : Notifying a

Re: [wsjt-devel] Build environment macOS 10.13.4

Ahh ok.. I didn’t realise that it will switch to the appropriate branch and start over., Megan On Wed, 16 May 2018 at 2:53 pm, Greg Beam wrote: > Hello All, > > > > First, there’s been little to know development effort on WSJT in a good > while (2yrs or more maybe?).

Re: [wsjt-devel] Subprocess Error (full details captured)

There is if you build it yourselfotherwise you have to wait until the next release. de Mike W9MDB On Tuesday, May 15, 2018, 3:17:56 PM CDT, Steve Sacco NN4X wrote: Joe - Sorry about that - running 1.9.0-rc4 r8642...was not aware there was an update. On

Re: [wsjt-devel] Signal variation during test

Hi Dave, On 5/14/2018 5:19 AM, David Birnbaum K2LYV wrote: ... IIRC with multiple channels the amplitudes do not add directly but in quadrature since they are not phase coherent. Others on this list are bettervequipped to answer. No, that's not correct. As explained in the FT8 DXpedition

Re: [wsjt-devel] Subprocess Error (full details captured)

Joe - Sorry about that - running 1.9.0-rc4 r8642...was not aware there was an update. On 5/15/2018 3:44 PM, Joe Taylor wrote: Steve -- You don't mention what code revision you are running.  This bug was (supposedly?) fixed in code revision r8646. -- 73, Joe, K1JT On 5/15/2018 3:30

Re: [wsjt-devel] Subprocess Error (full details captured)

On 5/15/2018 3:45 PM, Steve Sacco NN4X wrote: I guess the problem is pretty obvious - the forward slash after "\WSJT-X" in the file name... :-) "...ocal\Temp\WSJT-X/houndcallers.txt'? No. Again: this bug was fixed several weeks ago, in r8646.

Re: [wsjt-devel] Subprocess Error (full details captured)

I guess the problem is pretty obvious - the forward slash after "\WSJT-X" in the file name...  :-) "...ocal\Temp\WSJT-X/houndcallers.txt'? 73, Steve On 5/15/2018 3:30 PM, Steve Sacco NN4X wrote: Greetings, all.

Re: [wsjt-devel] Subprocess Error (full details captured)

You don't say what version your are using but there was a probable fix in r8646 de Mike W9MDB On Tuesday, May 15, 2018, 2:32:30 PM CDT, Steve Sacco NN4X wrote: Greetings, all. This fired again.  Once again, I was away from the rig, and let WSJT-X continue

Re: [wsjt-devel] Subprocess Error (full details captured)

That's because it's a concatenation of a Window's environment variable and a suffix added to it. The forward or backslash doesn't matter.  They both work under Windows from an application. de Mike W9MDB On Tuesday, May 15, 2018, 2:40:53 PM CDT, Greg Beam wrote:

Re: [wsjt-devel] Subprocess Error (full details captured)

Steve -- You don't mention what code revision you are running. This bug was (supposedly?) fixed in code revision r8646. -- 73, Joe, K1JT On 5/15/2018 3:30 PM, Steve Sacco NN4X wrote: Greetings, all. This fired again.  Once again, I was away from the rig, and let WSJT-X continue

Re: [wsjt-devel] Subprocess Error (full details captured)

Hi Steve, Not sure if the is on point or not, but, the path to the file is a bit wonky: 'C:\Users\Steve\AppData\Local\Temp\WSJT-X/houndcallers.txt' Note the forward slash before houdcallers.txt. Could be something, or nothing. Just an observation. 73’s Greg, KI7MT From:

[wsjt-devel] Subprocess Error (full details captured)

Greetings, all. This fired again.  Once again, I was away from the rig, and let WSJT-X continue running, so I do not know what it was seeing when this occurred: Details: - Running: C:\WSJT\wsjtx\bin\jt9 -s WSJT-X -w 1 -m 3 -e

Re: [wsjt-devel] Stations with bad clocks

If they use JTAlert, you can send them a text message. Dave Sent from my waxed string and tin cans. On May 15, 2018, at 12:17 PM, Rich - K1HTV > wrote: Notifying a station whose timing is at the edge of decoding limits is problematic because once

[wsjt-devel] Stations with bad clocks

Notifying a station whose timing is at the edge of decoding limits is problematic because once his timing slips past the max tolerable limit, no helpful messages about his clock will be decoded by the station you are trying to alert. If WSJT-X had a rubber clock feature which would

Re: [wsjt-devel] an idea (low priority)

On Tue, 2018-05-15 at 11:43 +0100, Mark Turner via wsjt-devel wrote: > Having just watched another station sending a "CHK TIMING" message > in > FT8, which is obviously not likely to succeed... > > I was wondering if a non-timing-critical "message" could be added to > the > protocol, e.g. four

Re: [wsjt-devel] DxPediton Mode Development utilizing Weak signal favorites Resource

Hi Take, Thanks again for sharing your opinions. Perhaps your ideas for a single-carrier OFDM mode for high capacity (more than 10x) FOX station (and a congestion control mechanism applicable for emergency and disaster communication) will become part of some program in the future.

Re: [wsjt-devel] Another Test of DXpedition Mode

Hi Dick and all, On 5/12/2018 12:51 PM, Dick Hale W7PP wrote:    The test went fine here but.  I connected with the fox sending a -17 signal report without problem. The fox set me the RR73 and the program logged the contact... Then, and I don't know why, the program sent another -17

Re: [wsjt-devel] Another Test of DXpedition Mode

        The test went fine here but.  I connected with the fox sending a -17 signal report without problem. The fox set me the RR73 and the program logged the contact... Then, and I don't know why, the program sent another -17 report and the fox sent me another RR73 and the program logged

Re: [wsjt-devel] an idea (low priority)

This would be quite useful based on my recent observations on 6m. We all suffer when someone inadvertently transmits across two periods. I have on occasion sent something like PA0XX CLOCK or indeed DL0XX, ON0XX and G0XXX of course :-) It normally works but it feels wrong because the station

[wsjt-devel] an idea (low priority)

Having just watched another station sending a "CHK TIMING" message in FT8, which is obviously not likely to succeed... I was wondering if a non-timing-critical "message" could be added to the protocol, e.g. four continuous tones - or some such combination that is unlikely to happen randomly,

Re: [wsjt-devel] DxPediton Mode Development utilizing Weak signal favorites Resource

Hi Joe, Thank you for providing your comments. My “development schedule is controlled by DXCC marketers” comes from Bill’s (I am sorry not to mention as Bill in my previous memo. It is my typo.) comment, i.e. “but overall under time pressure to get the mode working” and your February 02 First