Re: [wsjt-devel] WSJT-X 1.6.0 - duplicate UDP Status message at 50 secs.

On 24/12/2015 21:22, Bill Somerville wrote: > Otherwise I should be able to come up with a fairly simple generic > solution by comparing the whole byte array of the packed message rather > than doing this at the individual field level. Hi Laurie & Mike, turns out this was so trivial that I'm not

Re: [wsjt-devel] JTSDK-Win32 Upgrade Available - (Import Update)

Hi Doc, Well that's not a very nice Xmas present is it. It should eb noted, this issue in particular will not affect any builds, but needs resolved nonetheless. First sign of trouble there is "537", the branch is definitely at 543 with the root sitting at 554. Formatting is not quite right

Re: [wsjt-devel] JTSDK-Win32 Upgrade Available - (Import Update)

I'm used to coal in my stocking! (Why I started wearing stockings, I'll never know!) I abbreviated the info from "version" just to make it more compact. Attached is the screen shot of what "version" returns. MD5 matches perfectly. Could this be related to the directories I

Re: [wsjt-devel] WSJT-X 1.6.0 - duplicate UDP Status message at 50 secs.

On 24/12/2015 20:46, Laurie, VK3AMA wrote: These Status packets are being sent when there is NO change in status. * What is the purpose of these status packets sent at the 50 seconds (just prior to decode processing it appears)? * What is the purpose of sending a second duplicate status

Re: [wsjt-devel] JTSDK-Win32 Upgrade Available - (Import Update)

Hi Doc, I installed JTSDK from scratch ( main installer + all updates ) on two different boxes, and I've not been able to reproduce your problem. I'll email you offline with some additional suggestions, as I don't think there is a problem with the upgrade path at this point. 73's Greg, KI7MT

Re: [wsjt-devel] WSJT-X 1.6.0 - duplicate UDP Status message at 50 secs.

On 24/12/2015 21:13, Michael Black wrote: > Bill, how about the attached to eliminate duplicate status updates? > This isn't tested. > Seems like it should do the job. > > Do any of these need initialization (QStrings???) > Hi Mike, that's ok but I would rather not add yet another maintenance

Re: [wsjt-devel] JTSDK-Win32 Upgrade Available - (Import Update)

Hi Doc, Ok, Somehting is amiss here. I have to take off for a few hours, I'll look into this a bit more when I get back home this evening. 73's Greg, KI7MT On 12/24/2015 17:11, Dave 'Doc' Corio wrote: > This looks a little better. However, looking at version under JTSDK > Maint. still

[wsjt-devel] JTSDK-Win32 Upgrade Available - (Import Update)

Hello All, First, Happy Hols to everyone !! JTSDK-Win32 Upgrade (4) is a small but important update. It moves user updates off development ^/trunk/win32 and onto a more stable released branch, in this case ^/tags/jtsdk-win-2.03. *TO UPGRADE* - Close All JTSDK Terminals, QT, PY, MSYS, Maint

Re: [wsjt-devel] WSJT-X 1.6.0 - duplicate UDP Status message at 50 secs.

Bill, how about the attached to eliminate duplicate status updates? This isn't tested. Seems like it should do the job. Do any of these need initialization (QStrings???) 73 Mike W9MDB On Thu, Dec 24, 2015 at 2:52 PM, Bill Somerville wrote: > On 24/12/2015 20:46,

Re: [wsjt-devel] JTSDK-Win32 Upgrade Available - (Import Update)

This looks a little better. However, looking at version under JTSDK Maint. still looks like the original I sent. Dave 'Doc' Corio Vice President, McKean County American Legion Riders http://legionriders.wix.com/americanlegion Look Twice - Motorcycles are Everywhere! On 12/24/2015 7:04 PM,

Re: [wsjt-devel] JTSDK-Win32 Upgrade Available - (Import Update)

Couple of hopefully minor problems with this upgrade. When installing the patch I get the error " Windows cannot find 'svn'. Please be sure." Also, when checking the version info, I get the following: Version - 2.0.3 Last Rev - 537 URL -

Re: [wsjt-devel] JTSDK-Win32 Upgrade Available - (Import Update)

Hi Doc, Ok, that's the right formatting. Builds will be fine, and no this has nothing to do with the cache issue. Your repo version is not updating automatically, why I am mot exactly sure, however, you should be able to do this manually. To make sure JTSDK-Maint is not getting in the way

Re: [wsjt-devel] v1.7.0 r6311

On 24/12/2015 18:33, Josh Rovero wrote: > Turns off "Enable Tx" on every band change. So no transmitting at all... > Hi Josh, r6312 should fix this regression. 73 & Seasons Greetings Bill G4WJS. --

Re: [wsjt-devel] WSJT-X 1.6.0 - duplicate UDP Status message at 50 secs.

On 24/12/2015 10:23 PM, Bill Somerville wrote: On 24/12/2015 08:44, Laurie VK3AMA wrote: Using WSJT-X 1.6.0, I am receiving two (2) identical UDP status messages being sent at the 50 second mark. Is this a defect or by design? Hi Laurie, neither, there are several points in the WSJT-X source

[wsjt-devel] v1.7.0 r6311

In WS{R mode, 20% Tx cycle and band-hopping Turns off "Enable Tx" on every band change. So no transmitting at all... -- P.J. "Josh" Rovero http://www.roveroresearch.org Ham Radio: KK1D http://www.roveroresearch. net http://www.roveroresearch.info

Re: [wsjt-devel] Error: Could not load cache

That did the trick, Greg! Thanks and Happy Holidays! 73 Dave 'Doc' Corio Vice President, McKean County American Legion Riders http://legionriders.wix.com/americanlegion Look Twice - Motorcycles are Everywhere! On 12/24/2015 11:41 AM, Greg Beam wrote: > Hi Doc, > > I had this issue as

Re: [wsjt-devel] v1.7.0 r6311

On 24/12/2015 18:33, Josh Rovero wrote: > Turns off "Enable Tx" on every band change. So no transmitting at all... Hi Josh, that's the new electricity saving mode! Sorry about that, I didn't think that change through very well. I will fix it shortly. 73 Bill G4WJS.

Re: [wsjt-devel] Error: Could not load cache

Hi Doc, I had this issue as well. I suspect one of the JTSDK commits I'd made in the past broke the package build portion of the build script. In any case, make sure your on the latest version as of today, then I removed both C:\JTSDK\src\wsjtx and C:\JTSDK\wsjtx and pulled a new checkout

Re: [wsjt-devel] WSJT-X 1.6.0 - duplicate UDP Status message at 50 secs.

On 24/12/2015 08:44, Laurie VK3AMA wrote: > Using WSJT-X 1.6.0, I am receiving two (2) identical UDP status messages > being sent at the 50 second mark. > > Is this a defect or by design? Hi Laurie, neither, there are several points in the WSJT-X source code where events are being processed

[wsjt-devel] Error: Could not load cache

Someone please let me know if this post is inappropriate for this list. Noticed with 1.7 6304 that the "package" qualifier no longer worked (build-wsjtx package), and the version was installed to the "Install" directory of JTSDK. Following that, with vers 6307 and up JTSDK

Re: [wsjt-devel] Watchdog patch#2

On 19/12/2015 16:20, Michael Black wrote: > Another one that resets the watchdog counter when you change bands. Hi Mike, thanks for that, included in r6311 in the trunk. Also disabled "Enable Tx" on band change as that seems sensible too. 73 Bill G4WJS.

[wsjt-devel] Suggestion

I just joined the developer's list yesterday and promptly built version 1.7.0 of WSJT-X. I am running 1.7.0 as I write this email and have encountered no serious problems so far. I have several years of WSJT and WSJT-X experience, however, so I am not a rookie. I have made over 9000 JT65 and

Re: [wsjt-devel] Suggestion

On 24/12/2015 14:03, Ed Wilson wrote: > It would be helpful for folks like me if the program defaulted to CQ > (Tx6) when it is first started. Welcome Ed! I believe the thinking behind this behaviour is that if the application crashes mid-QSO then it is easy to pick up where you were on

Re: [wsjt-devel] Suggestion

Bill, Thanks for your reply. What??? WSJT-X crashing! This is one of the most stable programs that I have encountered...solid as a rock! I have thought about using the option to clear DX information upon logging, but I often log before the end of the QSO if I have both signal reports and if the

Re: [wsjt-devel] Watchdog patch#2

Yeah,,,I was thinking the same thing...listen before transmit. Thought about resetting on offset change too or mode change. Seems pretty much any user interaction seems should reset the thing. I assume the only intent is really to halt tx if you walk away. RRR Mike W9MDB On Thu, Dec 24, 2015 at