Re: [wsjt-devel] Possible bug in 7818 thru 7844

On 11/07/2017 01:56, Dave 'Doc' Corio wrote: On 7844 here, the Settings/General returns to "All", however the frequencies persist for Region 2. Hi Doc, the "All" IARU region setting is not really meant for normal usage, it is just a handy initial value. If it is "All" then all working fr

Re: [wsjt-devel] Possible bug in 7818 thru 7844

At least for me, using r7844 under macOS 10.9, my IARU region starts put at 'Region 2' between app restarts. I do not use configurations, however. [cid:2D5CB16F-AFBC-419E-83CE-85DF8080DE8A] -- David Tiller Sr. Architect/Lead Consultant | CapTech (804) 304-0638 | dtil...@captechconsulting.com

Re: [wsjt-devel] Possible bug in 7818 thru 7844

> On Jul 10, 2017, at 6:53 PM, Gary McDuffie wrote: > > It isn’t that I can’t see it, Bill. It’s that it I change it to region 2, > close the program or change configurations, then come back to the one I > changed, and it is back at ALL again. My change isn’t sticking. Sorry Bill. I misrea

Re: [wsjt-devel] Possible bug in 7818 thru 7844

On 7844 here, the Settings/General returns to "All", however the frequencies persist for Region 2. 73 Dave - KB3MOW On 7/10/2017 8:46 PM, Bill Somerville wrote: On 11/07/2017 01:30, Gary McDuffie wrote: On Jul 10, 2017, at 6:09 PM, Bill Somerville wrote: that's not good, I will look int

Re: [wsjt-devel] Possible bug in 7818 thru 7844

I can confirm Gary’s report on 7844 for MacOS. George J Molnar, KF2T Nevada, USA > On Jul 10, 2017, at 5:53 PM, Gary McDuffie wrote: > > >> On Jul 10, 2017, at 6:46 PM, Bill Somerville wrote: >> >> I am not able to reproduce that. >> >> Is anyone else unable to set their IARU Region in "

Re: [wsjt-devel] Possible bug in 7818 thru 7844

> On Jul 10, 2017, at 6:46 PM, Bill Somerville wrote: > > I am not able to reproduce that. > > Is anyone else unable to set their IARU Region in "Settings->General” ? It isn’t that I can’t see it, Bill. It’s that it I change it to region 2, close the program or change configurations, then co

Re: [wsjt-devel] Possible bug in 7818 thru 7844

Unable to here. Using any version since I joined a few weeks ago. Ned/AA7A On 7/11/2017 12:46 AM, Bill Somerville wrote: On 11/07/2017 01:30, Gary McDuffie wrote: On Jul 10, 2017, at 6:09 PM, Bill Somerville wrote: that's not good, I will look into that. I assume you are clicking "Ok" to ex

Re: [wsjt-devel] Possible bug in 7818 thru 7844

On 11/07/2017 01:30, Gary McDuffie wrote: On Jul 10, 2017, at 6:09 PM, Bill Somerville wrote: that's not good, I will look into that. I assume you are clicking "Ok" to exit the settings window? Also you will have to set it in every configuration you have, configurations have independent setti

Re: [wsjt-devel] Possible bug in 7818 thru 7844

> On Jul 10, 2017, at 6:09 PM, Bill Somerville wrote: > > that's not good, I will look into that. I assume you are clicking "Ok" to > exit the settings window? Also you will have to set it in every configuration > you have, configurations have independent settings. Correct, Bill. click on OK

Re: [wsjt-devel] Possible bug in 7818 thru 7844

> that's not good, I will look into that. I assume you are clicking "Ok" to > exit the settings window? Also you will have to set it in every configuration > you have, configurations have independent settings. Hi Bill, I confirm Gary’s observation. Steve, k9an

Re: [wsjt-devel] Possible bug in 7818 thru 7844

On 11/07/2017 01:05, Gary McDuffie wrote: I don’t know where it would fall in priority, but several of us have noticed that when setting the IARU Region, it always changes back to all. Is this by design or something to be dealt with later? Hi Gary, that's not good, I will look into that. I

Re: [wsjt-devel] Possible bug in 7818 thru 7844

> On Jul 10, 2017, at 2:16 PM, Joe Taylor wrote: > > FYI: WSJT-X setup has become sufficiently complicated that most users find > the preferred way to switch Modes is to define and switch Configurations, > instead. Amen to that. I have mode configs and vhf/hf configs (a dozen so far). Joe,

Re: [wsjt-devel] FT8 + Autoseq + Free Text TX5

Should being the key word. I was working with another local ham last night, I was running 7833, he was 78 20somthing. I sent a TX5 that was "5W 160L TU 73" when he would have been expecting a generated 73 and his end didn't trigger the 73, he just kept sending the auto-generated RRR... 73, R

Re: [wsjt-devel] FT8 + Autoseq + Free Text TX5

Weird...was working and then stopped so I removed the link.   Working now...tx5 does not get changed until callsign changes. https://www.dropbox.com/s/jltxb6nbslesn5n/tx5_patch?dl=1 de Mike W9MDB -- Check out the

Re: [wsjt-devel] FT8 + Autoseq + Free Text TX5

Simple enough to keep getStdMsgs from being called unless callsign changed https://www.dropbox.com/s/dkqx1yrp9500hwf/tx5_patch?dl=0 de Mike W9MDB-- Check out the vibrant tech community on one of the world's most engagi

Re: [wsjt-devel] K3S Going Split???

Yep I had the same issue. If memory serves, HRD was not reporting back to the K3 to not go into Split mode. 73, Jim S. N2ADV > On Jul 10, 2017, at 3:51 PM, Jim - N4ST wrote: > > It may well be an "HRD thing", but it only happens when I tell WSJT-X to > "FAKE IT". With this not selected the

Re: [wsjt-devel] FT8 + Autoseq + Free Text TX5

On 10/07/17 21:24, George J Molnar wrote: > Would it be a better practice to support only standard messages in automatic > modes? I think so. A station responded to my CQ and he ended with a free text message without a 73 so the program didn't prompt me to log. By the time I realised what had h

Re: [wsjt-devel] FT8 + Autoseq + Free Text TX5

Would it be a better practice to support only standard messages in automatic modes? George J Molnar, KF2T Nevada, USA > On Jul 10, 2017, at 1:07 PM, Neil Zampella wrote: > > Hi Bill, > > Understood, the program is parsing the line to get the 73, but this needs to > be emphasized that a 73

Re: [wsjt-devel] Possible bug in 7818 thru 7844

On 7/10/2017 4:06 PM, David Tiller wrote: Dear dev team, FYI, this bug still exists in r7844, and happens any time you switch into MSK144 mode from FT8, JT4, JT9, JT9+JT65, JT65, or QRA64. ISCAT and WSPR seem ok. It sounds like the 'over' time isn't getting initialized when entering MSK144 mo

Re: [wsjt-devel] Any way to speed up interaction with the radio?

When WSJT-X is configured to operate your transceiver in split mode, VFO B's mode must be correctly set. This is a time-consuming operation on some transceivers, and WSJT-X waits to set VFO B's mode until you initiate transmission. WSJT-X provides the option to assume that you've manually set

Re: [wsjt-devel] FT8 + Autoseq + Free Text TX5

Hi Bill, Understood, the program is parsing the line to get the 73, but this needs to be emphasized that a 73 must be in the line (hopefully an RR73 won't cause a grid change) but I've seen stuff like QRZ 10W TU as a sign off nd that's it. Neil On 7/10/2017 3:58 PM, Bill Somerville wrote:

Re: [wsjt-devel] Possible bug in 7818 thru 7844

Dear dev team, FYI, this bug still exists in r7844, and happens any time you switch into MSK144 mode from FT8, JT4, JT9, JT9+JT65, JT65, or QRA64. ISCAT and WSPR seem ok. It sounds like the 'over' time isn't getting initialized when entering MSK144 mode. Screenshots here: https://drive.google.

[wsjt-devel] Mainwindow UI tooltips and misc

Here's a patch which updates the tooltips and the clock/freq background.Only one tooltip is longer than 2 lines now which is the power meter and put some emphasis on it to hopefully prompt people to read the docs to set their audio level correctly. Added some border/rounding to soften the clock

Re: [wsjt-devel] FT8 + Autoseq + Free Text TX5

I'll take a look at #2 with the callsign de Mike W9MDB From: Bill Somerville To: wsjt-devel@lists.sourceforge.net Sent: Monday, July 10, 2017 2:41 PM Subject: Re: [wsjt-devel] FT8 + Autoseq + Free Text TX5 On 10/07/2017 20:35, Black Michael via wsjt-devel wrote: #1 Disable

Re: [wsjt-devel] FT8 + Autoseq + Free Text TX5

On 10/07/2017 20:50, Neil Zampella wrote: Will using a non-standard message cause the receiving station's program to not trigger their reply ?? Hi Neil, there is no need for a reply to a sign off message but if it contains the word "73" it should work the same as a standard 73 message. 73

Re: [wsjt-devel] K3S Going Split???

It may well be an "HRD thing", but it only happens when I tell WSJT-X to "FAKE IT". With this not selected the K3 doesn't go split on WSJT-X initialization. 73, Jim - N4ST -Original Message- From: James Shaver (N2ADV) [mailto:n2...@windstream.net] Sent: Monday, July 10, 2017

Re: [wsjt-devel] FT8 + Autoseq + Free Text TX5

Will using a non-standard message cause the receiving station's program to not trigger their reply ?? On 7/10/2017 3:35 PM, Black Michael wrote: In autosequencing the system calls the genStdMsgs on every received message. This is a new capability and behavior is till being worked out. The m

Re: [wsjt-devel] FT8 + Autoseq + Free Text TX5

On 10/07/2017 20:35, Black Michael via wsjt-devel wrote: #1 Disable the genStdMsgs logic after an alternate Tx 5 is selected. #2 Break out of genStdMsgs early based on the message being transmitted. #3 Don't call genStdMsgs based on m_ntx Hi Mike, a better solution might be to not generate Tx5

Re: [wsjt-devel] FT8 + Autoseq + Free Text TX5

In autosequencing the system calls the genStdMsgs on every received message.   This is a new capability and behavior is till being worked out. The might be a couple ways to fix that problem: #1 Disable the genStdMsgs logic after an alternate Tx 5 is selected.#2 Break out of genStdMsgs early based

Re: [wsjt-devel] FT8 + Autoseq + Free Text TX5

On 10/07/2017 20:24, Jordan Sherer wrote: I have a few free text macros defined in TX5. One thing I've noticed is that when working a QSO with autoseq enabled, even if I've selected the TX5 macro choice well in advance, it reverts the text to the standard TX5 message syntax "[their call] [my ca

[wsjt-devel] FT8 + Autoseq + Free Text TX5

Howdy! I have a few free text macros defined in TX5. One thing I've noticed is that when working a QSO with autoseq enabled, even if I've selected the TX5 macro choice well in advance, it reverts the text to the standard TX5 message syntax "[their call] [my call] 73". Is this intended when autoseq

[wsjt-devel] r7841 - minor detail

I hesitate to mention something so piffling ... On the 'About WSJT-X' screen, the copyright notice needs updating from 2001-2016 to 2001-2017. 73, Richard G4DYA -- Check out the vibrant tech community on one of the worl

Re: [wsjt-devel] 7839 issues

Hi Alex We have seen the same as you, and some other behaviour re Enable AP for DX call being greyed out. One example is if Settings is opened and closed, Enable AP for DX call becomes greyed out (but still appears to operate). 73 Charlie > 1. when changing from FT8 (or other mode) to QRA64,

Re: [wsjt-devel] Sourceforge Update Error

Oh, hallelujah! Getting to the correct path was the secret! Thank you, Greg (and Bill, too). 73 John KE7B -Original Message- From: Greg Beam [mailto:ki7m...@gmail.com] Sent: Monday, July 10, 2017 11:45 AM To: 'WSJT software development' Subject: Re: [wsjt-devel] Sourceforge Update Err

Re: [wsjt-devel] Sourceforge Update Error

Not sure if I'm doing that correctly as you've indicated, Bill. When I launch QT on my Windoze machine, I get a prompt of (JTDSK-QT 5.2 ) C:\JTSDK And not $ Regardless, I entered 'svn cleanup', and it accepted it silently. Reentering 'build-wsjtx package' or 'build-wsjtx rinstall' still fails wit

[wsjt-devel] 7839 issues

1. when changing from FT8 (or other mode) to QRA64, Enable AP for DX call is greyed out, until restart wsjtx2. when changing from FT8 (or other mode) to ISCAT, click decode not working, until restart wsjtx3. when changing to QRA64, or restarting with QRA64, green Ftol bar on Wide Graph drawn wit

Re: [wsjt-devel] Sourceforge Update Error

Now ya don't it John, it's busted :-) You should be able to, from JTSDK-QT: cd C:\JTSDK\src\wsjtx svn cleanup svn up or remove C:\JTSDK\src\wsjtx then rebuild. Assuming of course, SF is not actually down. 73's Greg, KI7MT -Original Message- From: John Zantek [mailto:j...@zantek.ne

Re: [wsjt-devel] Sourceforge Update Error

On 10/07/2017 19:36, John Zantek wrote: I was building a new package and, unfortunately, had to interrupt the batch file. When I now respond 'y' when asked to Update from SVN Before Building, I get: Sourceforge Update Error Build-wsjtx was unable to update [ wsjtx ] Sourceforge. The service

[wsjt-devel] Sourceforge Update Error

I was building a new package and, unfortunately, had to interrupt the batch file. When I now respond 'y' when asked to Update from SVN Before Building, I get: Sourceforge Update Error Build-wsjtx was unable to update [ wsjtx ] Sourceforge. The service may be down or Undergoing maintenance. C

Re: [wsjt-devel] K3S Going Split???

I had this happen last year sometime with my K3. Bill and I were on Skype a couple times trying to track down the cause - ultimately we determined it was an HRD thing. My solution was to dump HRD. Not very helpful, I know (sorry) - maybe you'll have better luck tracking it down. Jim S. N2

[wsjt-devel] K3S Going Split???

I have the issue that when I start WSJT-X, or change configurations, it puts my Elecraft K3S in split mode. That causes the WSJT-X CAT comms to fail because I have "FAKE IT" selected and that mode cannot initiate when the rig is already in split mode. WSJT-X is setup to communicate with HRD 6.

Re: [wsjt-devel] FT8 and UDP

> On 10 Jul 2017, at 11:39, Bill Somerville wrote: > > On 09/07/2017 21:12, Bill Somerville wrote: >> I will have a look at the reply facility for FT8, you are probably the first >> to test it. > > Hi Anders, > > from revision 7830 things should be working more reliably for you. > > 73 > Bil

Re: [wsjt-devel] r 7836 Issue

Jim, That box was not checked...r7838 appears to have fixed the problem. Thanks for your suggestion. Ed, K0KC k0kc@arrl.nethttp://k0kc.us/ From: Jim Brown To: wsjt-devel@lists.sourceforge.net Sent: Monday, July 10, 2017 1:55 PM Subject: Re: [wsjt-devel] r 7836 Issue On 7/10/2017 10:

Re: [wsjt-devel] r 7836 Issue

On 7/10/2017 10:14 AM, Ed Wilson via wsjt-devel wrote: I have been testing FT8 for the past week or so and today decided to try to make a JT65 contact on six meters. I am using r7836, which I built this morning. I made a contact with WB5TUF near Houston with -01 at both ends and found an issue

Re: [wsjt-devel] Inconsistent Tool Tips on OS X

I tried this, but I get a compile error. The one item I changed in mainwindow.ui looks like this:

Check to enable automatic sequencing of Tx messages based on received messages

Re: [wsjt-devel] r 7836 Issue

Based upon a single contact on 20 meters, this issue seems to be fixed in r7838...thanks guys! Ed, K0KC k0kc@arrl.nethttp://k0kc.us/ From: Black Michael via wsjt-devel To: "wsjt-devel@lists.sourceforge.net" Cc: Black Michael Sent: Monday, July 10, 2017 1:17 PM Subject: Re: [wsjt-deve

Re: [wsjt-devel] Inconsistent Tool Tips on OS X

On 10/07/2017 18:47, Black Michael via wsjt-devel wrote: I noticed that on Windows the tooltips that do NOT have HTML code seem to display on one line whereas HTML ones break lines by default. The difference between Monitor and Stop for instance where Monitor has an HTML tooltip and Stop does no

Re: [wsjt-devel] Inconsistent Tool Tips on OS X

I noticed that on Windows the tooltips that do NOT have HTML code seem to display on one line whereas HTML ones break lines by default.The difference between Monitor and Stop for instance where Monitor has an HTML tooltip and Stop does not. de Mike W9MDB  - Forwarded Message - From: Bl

Re: [wsjt-devel] Inconsistent Tool Tips on OS X

The tooltip issue is related to the way the tooltip controls are added as children of the widgets and thus are contained by their parent bounding box. The only way I know of working around it is by adding an onEnter handler to the widgets, then creating a QTooltip manually after a short timeout,

Re: [wsjt-devel] Inconsistent Tool Tips on OS X

Try changing the tooltip to this and see if works OK on OS-X.On my Windows box this makes it wider and only lines high.We should be able for force the tooltip format like this hopefully on all platforms. Check to enable automatic sequencing of Tx messages based on received messages.  de Mike W9M

Re: [wsjt-devel] Inconsistent Tool Tips on OS X

I agree - I suspected it might be a Qt issue, and it is pretty minor. Thanks for the feedback! -Tim > On Jul 10, 2017, at 11:11 AM, John Nelson wrote: > > Hi Bill, > >> I'm not sure we can do anything about it, it is a matter for the Qt >> developers. > > In that case, I’m content to leave

Re: [wsjt-devel] r 7836 Issue

Thanks Bill and Mike...I will build r7838 right away but may not have time to test it as I have a doctor's appointment coming up pretty soon. I assume that the issue was not unique to six meters and that I can test it on a lower band? Ed, K0KC k0kc@arrl.nethttp://k0kc.us/ From: Bill Somerv

Re: [wsjt-devel] r 7836 Issue

This is fixed in 7838. de Mike W9MDB From: Ed Wilson via wsjt-devel To: "wsjt-devel@lists.sourceforge.net" Cc: Ed Wilson Sent: Monday, July 10, 2017 12:15 PM Subject: [wsjt-devel] r 7836 Issue I have been testing FT8 for the past week or so and today decided to try to make a JT65

Re: [wsjt-devel] r 7836 Issue

On 10/07/2017 18:14, Ed Wilson via wsjt-devel wrote: I have been testing FT8 for the past week or so and today decided to try to make a JT65 contact on six meters. I am using r7836, which I built this morning. I made a contact with WB5TUF near Houston with -01 at both ends and found an issue wi

Re: [wsjt-devel] Inconsistent Tool Tips on OS X

Hi Bill, > I'm not sure we can do anything about it, it is a matter for the Qt > developers. In that case, I’m content to leave things as they are…the group has enough to do without fixing Qt as well… r7838 is working well - especially with the correct calculation of start/stop times for the

[wsjt-devel] r 7836 Issue

I have been testing FT8 for the past week or so and today decided to try to make a JT65 contact on six meters. I am using r7836, which I built this morning. I made a contact with WB5TUF near Houston with -01 at both ends and found an issue with his transmissions NOT showing in the Rx Frequency w

Re: [wsjt-devel] Inconsistent Tool Tips on OS X

On 10/07/2017 18:00, John Nelson wrote: Tim is correct. It would be nice to have this (minor) problem tidy before rc1 goes public Hi John and Tim, I'm not sure we can do anything about it, it is a matter for the Qt developers. 73 Bill G4WJS. -

Re: [wsjt-devel] Inconsistent Tool Tips on OS X

Tim is correct. It would be nice to have this (minor) problem tidy before rc1 goes public — John G4KLA -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link

[wsjt-devel] Inconsistent Tool Tips on OS X

The tool tips on OS X are inconsistent - most of the time they cut off part of the text, but if you move the mouse back and forth over the control, eventually they do show the whole text. These examples are from r7836. Cut off text: Good text: This isn't a new issue - the same thing hap

[wsjt-devel] FT8: multiple responses to CQ

If a DX station calls CQ and gets multiple calls on his own frequency, and then chooses one to answer, it doesn't help if other unsuccessful callers repeat their response to his CQ. It might be worth adding a bit of logic so that: if ((DX station has responded to a call other than Mycall) && (my

Re: [wsjt-devel] Receive Window r7835

sri RRR On 7/10/2017 10:21 AM, Black Michael via wsjt-devel wrote: This link removed since Joe just fixed it. de Mike W9MDB *From:* Black Michael via wsjt-devel *To:* WSJT software development *Cc:* Black Michael *S

Re: [wsjt-devel] Receive Window r7835

Yes...removed it...Joe fixed the problem in 7838Do a new build and it should be OK now. Mike From: dgb To: Black Michael via wsjt-devel Sent: Monday, July 10, 2017 10:27 AM Subject: Re: [wsjt-devel] Receive Window r7835 From Dropbox That file isn’t here anymore Someone mi

[wsjt-devel] FT8

Greetings colleagues, very good day, with the FT8 modality, I noticed that many stations are delayed in their transmission, having to make several calls to be able to be decoded, for this same condition I saw in the need to place 1 second of delay to The transmission, among other things, the col

Re: [wsjt-devel] Receive Window r7835

From Dropbox That file isn’t here anymore Someone might’ve deleted the file or disabled the link. On 7/10/2017 10:15 AM, Black Michael via wsjt-devel wrote: Try this patchhave to test to ensure it doesn't hose all the other modes but it fixes the JT65/JT9 problem and appears to me to be t

Re: [wsjt-devel] Receive Window r7835

This link removed since Joe just fixed it. de Mike W9MDB From: Black Michael via wsjt-devel To: WSJT software development Cc: Black Michael Sent: Monday, July 10, 2017 10:18 AM Subject: Re: [wsjt-devel] Receive Window r7835 Try this patchhave to test to ensure it doesn't hose

Re: [wsjt-devel] Call 1st

Joe - I used it last night for quite a while on several HF bands, and it worked very well. I didn't notice the Enable Tx button going off after the end of the QSO, but don't mind it staying on. In any case, this is a welcome and very useful feature - thanks! Eric NC6K -Original Message- F

Re: [wsjt-devel] TQSL and LOTW handling of FT8

Thank you all for the clarification! 73, /Heimir W1ANT On Mon, Jul 10, 2017 at 9:05 AM Richard Lamont wrote: > On 10/07/17 15:50, Heimir Sverrisson wrote: > > > Hi all, > > I know this is a peripheral to the software development, but I decided to > > ask anyway. > > I had a handful of successful

Re: [wsjt-devel] TQSL and LOTW handling of FT8

On 10/07/17 15:50, Heimir Sverrisson wrote: > Hi all, > I know this is a peripheral to the software development, but I decided to > ask anyway. > I had a handful of successful QSO's using FT8 on Saturday. When uploading > the log using TQSL it said that FT8 was an illegal mode and asked if I > wan

Re: [wsjt-devel] TQSL and LOTW handling of FT8

Using TQSL, map FT8 to “data” George J Molnar, KF2T Nevada, USA > On Jul 10, 2017, at 7:50 AM, Heimir Sverrisson > wrote: > > Hi all, > I know this is a peripheral to the software development, but I decided to ask > anyway. > I had a handful of successful QSO's using FT8 on Saturday. When u

Re: [wsjt-devel] TQSL and LOTW handling of FT8

FT8 will be added to the next ADIF spec after which LOTW and eQSL should recognize them after a whileseveral weeks out I would imagine. For now you have to map FT8 to DATA for TQSL in File/Preferences/ADIF Modes de Mike W9MDB From: Heimir Sverrisson To: wsjt-devel@lists.sourceforge.ne

Re: [wsjt-devel] TQSL and LOTW handling of FT8

On 10/07/2017 15:50, Heimir Sverrisson wrote: I know this is a peripheral to the software development, but I decided to ask anyway. I had a handful of successful QSO's using FT8 on Saturday. When uploading the log using TQSL it said that FT8 was an illegal mode and asked if I wanted to upload t

[wsjt-devel] TQSL and LOTW handling of FT8

Hi all, I know this is a peripheral to the software development, but I decided to ask anyway. I had a handful of successful QSO's using FT8 on Saturday. When uploading the log using TQSL it said that FT8 was an illegal mode and asked if I wanted to upload the log anyway, which I did. My QSO count o

Re: [wsjt-devel] Call 1st

Hi Joe, I agree with John - using r7836, it worked great for three QSO’s I just made. This makes it MUCH easier to get a QSO going - thanks! One surprise was that it responded to a Tx1 made off-frequency compared to my CQ call, but when I think about it that should be the correct behavior. U

Re: [wsjt-devel] Call 1st

Tnx John! On 7/10/2017 10:15 AM, John Nelson wrote: Hi Joe, r7835 with revised Call 1st is working correctly.. — John G4KLA -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slas

Re: [wsjt-devel] Call 1st

Hi Joe, r7835 with revised Call 1st is working correctly.. — John G4KLA -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot __

[wsjt-devel] Call 1st

Hi all, I had not intended the "Weak" checkbox to be visible, just yet. Its function is not yet implemented. Code revision 7835 is yet another attempt to get the "Call 1st" logic just right. I think it should now do the following: 1. Decodes containing "MyCall" or falling within 10 Hz of R

Re: [wsjt-devel] Controlling the level of audio going into the sound card.

Thanks for the tip, Rick. I picked one up yesterday and installed it inline. Works great and I can see the difference on the waterfall. Best, Jordan KN4CRD On Jul 9, 2017, 10:57 AM -0400, K5GZR - Rick , wrote: > > I have a RigblasterPRO getting constant level audio from one of the > connectors

Re: [wsjt-devel] WSPR frequency on 80 meters

Hi Lloyd, 80m default frequency change including WSPR is addressed in the following memo from Joe on July 08 on this reflector. - Previous 80 m use of JT modes has done a disservice to J

Re: [wsjt-devel] WSPR frequency on 80 meters

On 10/07/2017 07:06, Lloyd Kirk wrote: I might have missed it somewhere but all my newer wsjtx builds now have 3.5726 as the wspr frequency. It was and (still being used) 3.5926 I do not know when it was changed. Lloyd Kirk WB5HUP Hi Lloyd, you did indeed miss the messages. When we switch th

Re: [wsjt-devel] FT8 Samples

On 10/07/2017 05:57, Black Michael via wsjt-devel wrote: One thing to add is some FT8 samples to the Download Samples menu item. Hi Mike, thanks for the reminder. The sample files are not tied to the releases any more and can be changed at any time. We will probably add some in parallel with

Re: [wsjt-devel] FT8 and UDP

On 09/07/2017 21:12, Bill Somerville wrote: I will have a look at the reply facility for FT8, you are probably the first to test it. Hi Anders, from revision 7830 things should be working more reliably for you. 73 Bill G4WJS. -

Re: [wsjt-devel] WSPR frequency on 80 meters

On 10/07/17 07:06, Lloyd Kirk wrote: > I might have missed it somewhere but all my newer wsjtx builds now have > 3.5726 as the wspr frequency. > It was and (still being used) 3.5926 I do not know when it was changed. On July 6, 2017 Bill G4WJS posted to this list in the thread "WSJT-X: Working fre

Re: [wsjt-devel] r7829 Call 1st / weak

and maybe call1st and weak greyed out unless auto seq is checked? I also see these checkboxes on other modes that do not use auto seq. Charlie _ From: Black Michael via wsjt-devel [mailto:wsjt-devel@lists.sourceforge.net] Sent: 10 July 2017 06:06 To: WSJT software development

Re: [wsjt-devel] r7829 Call 1st / weak

I have found that 1. Weak does not work 2. When 2 stations call and it picks up the 1st, after completion it does not start on the 2nd and requires operator intervention unless the 2nd calls again (but in that event there is the problem cited by Jim N4ST). I should add that only twice ha

Re: [wsjt-devel] FT8 Rx Window 7823 ->7824

I see that it's working again on 7833, thanks! Almost good for RC, go WSJTX! 73 de Alex - CT1GVN On Sunday, July 9, 2017, 10:47:16 PM GMT+1, Alexandre Moleiro via wsjt-devel wrote: Hi. In FT8 mode before 7824 RX Window would decode signals at the Green cursor freq.Since 7824 it stopped working

Re: [wsjt-devel] r7829 Call 1st / weak

If you are a rare DX and have many stations calling you, once auto-cq-reply starts it should not respond to any calls until you send TX4 or TX5.If it does then you can't complete any QSO. Also couldn't get weak to work here, call 1st worked fine. 73 de Alex - CT1GVN On Monday, July 10, 2017, 6: