[wsjt-devel] 2.2 RC Bugs

[Tom Melvin]

Windows 7 Pro, 64bit binary

If the a list anywhere of found/fixed defects in rc1?

I have been having problems with VERY slow (15sec) start up or in some case 
will not start due to rogue wsjtx.exe showing as running via task manager.

If been resolved great, if not can spend some time documenting it - if there 
was a visible list could check.

Would rather not do the work and get a response ‘ Yes known defect - fixed in 
next rc’  after spending time on it :-)


Regards

Tom

--
73

Tom
GM8MJV (IO85)





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

Re: [wsjt-devel] LF/MF possible new mode ?

[Tom Melvin]

This was asked over on the main WSJT mailing list just recently, there may be 
more details on that thread.

https://groups.io/g/WSJTX/message/6596

--
73’s

Tom
GM8MJV (IO85)





On 23 Feb 2020, at 12:35, Trevor Smithers  wrote:

> Back last August/September there was a brief post about a new
> WSJT mode in the early stages of development by K1JT and K9AN designed
> specifically for 136kHz, 472KHz and 160.
> 
> I thought it was to be based on JT65 (but it might have been JT9) and was
> hoped to be far more sensitive at the designated frequencies than current
> offerings.
> 
> Is this still under consideration ?
> 
> Trevor  G0KTN
> 
> 
> 
> ___
> 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] Crash in VHF-contest

[Tom Melvin]

Jari

What version of wsjt-X?, what were you doing at the time? - ft8 / ft4?

Will need a little more info rather than just the generic windows error.

Any wsjt error messages?

Tom

--
73’s

Tom
GM8MJV (IO85)





On 7 Jan 2020, at 20:11, Jari A  wrote:

> Problem signature:
>   Problem Event Name: APPCRASH
>   Application Name:   wsjtx.exe
>   Application Version:0.0.0.0
>   Application Timestamp:  5ddd4628
>   Fault Module Name:  ntdll.dll
>   Fault Module Version:   6.1.7601.24540
>   Fault Module Timestamp: 5ddf3f5f
>   Exception Code: c005
>   Exception Offset:   0002a365
>   OS Version: 6.1.7601.2.1.0.256.48
>   Locale ID:  1035
>   Additional Information 1:   b3a6
>   Additional Information 2:   b3a6807104b0408d3ac9b2061e15658a
>   Additional Information 3:   b01e
>   Additional Information 4:   b01e84fe8ed63eafb83277969ae99739
> 
> Win 7 pro, 64bit
> 
> Rgds,
> 
> : Jari / oh2fqv
> ___
> 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] Callsign lockout

[Tom Melvin]

Just another view on this - last night there was a UK contest - despite it 
being a ‘Normal’ mode contest a pile of people were using ‘EU Contest mode’. 
What was noticeable, yes WSJT switched modes to follow but in many cases while 
switching you ‘lost’ the report.

While the system went on to sent RR73 etc. and log the contact - it was not 
complete - so stations had to call again.  If there was yet another option to 
remember to switch off/on and both ends needing to recognise the need if one 
was ‘hidden’ 

Nope sorry leave it up to the operator.

Tom

P.S.   I could see on a QUIET band there would be benefit of suppressing the 
odd local - glance at screen if activity cool band opening work the band - the 
local 5 miles away (running in robot mode) makes it not that easy. Thankfully 
JTAlert can limit by distance but that is Windows only.  You would need to make 
sure the entries fully supported ‘wildcards’.

--
73’s

Tom
GM8MJV (IO85)





On 4 Dec 2019, at 05:37, Black Michael via wsjt-devel 
 wrote:

> It's not a lockout file.
> 
> The idea is very simple.
> 
> Right now call first always picks the 1st decode...ergo the problem
> 
> So the idea is that once a call is worked it gets put in a list (doesn't 
> matter whether or not you log it).  The call first logic checks the list and 
> ignores anybody in it.
> If call first does not trigger then the 1st entry that was detected would be 
> used.
> So it would all be completely transparent, only temporarily blocks calls, and 
> clears itself.
> 
> If you have 5 people calling you it will go 1,2,3,4,5 and start over again 
> whereas right now it's 1,1,1,1,1, ad nauseum.
> 
> For the most part nobody would even notice this was happening except the 1st 
> decode may not be the one chosen.
> 
> de Mike W9MDB
> 
> 
> 
> 
> On Tuesday, December 3, 2019, 11:28:30 PM CST, Jim Brown 
>  wrote:
> 
> 
> W9MDB wrote:
> 
> > I'm all ears for opinions from operators who have had a call pileup on them.
> 
> I've been a ham since 1955, General in '56, Extra '59. I've always been 
> primarily a CW op, mostly contesting and chasing DX. I've been the guy 
> on the DX end of pileups working CW in a major contest, no split 
> operation. I also work RTTY contests as part of a club that often wins 
> them. So far, I've not gotten interested in FT4/FT8 contesting on HF.
> 
> I'm near San Francisco and have a very good station. I use FT8 
> extensively on 160M during the winter to work EU, and both FT8 and 
> MSK144 on 6M chasing grids. I rarely call CQ, mostly tail-ending 
> stations I want to work, just as Dave does. That's smart operating.
> 
> The craziest I've seen FT8 is when 6M is open to JA, often with 
> JTAlert's 4x9 display nearly full of decodes. By far the best way to 
> work it is to call CQ with Call First off, Auto Seq on, Hold TX Freq on, 
> and pick the station I want to respond to.
> 
> As to this lockout thing -- IMO, the nuisance calls come from new folks 
> who have little HF experience, have massive receive noise, and never 
> realize the band is open for DX, only look at JTAlert, and are calling 
> the only signals strong enough to get through their noise. A library of 
> lockout calls is quite unlikely to work, because it's different new 
> folks every time! Indeed, those JA openings are almost the only time I 
> call CQ, and for that reason! The only folks I want calling me are the 
> DX I want to work, and I don't want guys who can't hear or don't have a 
> clue covering them up!
> 
> 73, Jim K9YC
> 
> 
> 
> ___
> 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 mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] FT8 Fox and Hound Mode - FOX Mode Operator enhancement request

[Tom Melvin]

Dave

There is not a lot of space under the 'Auto Seq' box - I will agree date and 
time could be smaller - but disagree as to the DX Call/Grid  - they need to be 
easily seen/entered for distance/Bearing - my eyes are not quite what the were 
a few years back and with all the different frequencies in use I really do need 
to see that easily at a glance.

See attached if it made it through



--
73’s

Tom
GM8MJV (IO85)





On 20 Nov 2019, at 00:25, David Gilbert  wrote:

> 
> If anyone was seriously concerned about real estate usage in the WSJT-X user 
> window there wouldn't be all that wasted space in the lower left corner for 
> any of the modes.  The Frequency display doesn't need to be anywhere near 
> that large, DX Call and DX Grid is mostly superfluous, the size of the 
> Date/Time box is ridiculous ...   and all of that could be resized and 
> repositioned under the Auto Seq and Call 1st buttons.
> 
> All of which has been brought up before.
> 
> Dave   AB7E
> 
> 
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] State QSO Parties

[Tom Melvin]

>> For non-US QSO parties, similar techniques might work. Consider a QSO party 
>> with the counties of England, Ireland, Scotland, and Wales as the activated 
>> counties. :-)

For RSGB it’s between 2 to 8 characters along with the obligatory signal report 
’59’  :-)

As has been pointed out it’s payload size - suspect will have to wait till the 
next major release FT9? (or FT10, FT11 ….) 

It’s not a simple task even if limited to USA.

Tom

73’s

Tom
GM8MJV (IO85)





On 26 Sep 2019, at 01:12, Bill Frantz  wrote:

> On 9/25/19 at 3:52 PM, g4...@classdesign.com (Bill Somerville) wrote:
> 
>> On 25/09/2019 23:42, Bill Somerville wrote:
>>> whereas the index into a table of 64 values (48 states + 14 provinces + DC 
>>> + DX) takes a mere 7 bits to store.
> 
> This is actually an interesting problem. We can divide the contesters into 
> those activating the counties and those trying to contact them. The worst 
> case I've heard is 252 Texas counties, but the 7QP will also have a big 
> number.
> 
> One other problem is that some of the state QSO parties take place on the 
> same weekend, and of course, some people try to make contacts in more than 
> one QSO party. If the sum of all counties involved is small enough, it might 
> be possible to support this behavior.
> 
> Lets assume: For the US state QSO parties, each station only activates 
> counties in one QSO party. (We do need to support rovers.) It will need to 
> receive locations from all the counties in that QSO party + the other 
> states/provinces. People sending to it will need to know which table it is 
> using.
> 
> We can select the table by the weekend data, and starting week before for 
> testing. There might also be a UI affordance which allows manual selection 
> for use in closed group testing. (For such testing, I suggest ditching the 
> radios and just using the built-in audio of several computers in the same 
> room.)
> 
> For non-US QSO parties, similar techniques might work. Consider a QSO party 
> with the counties of England, Ireland, Scotland, and Wales as the activated 
> counties. :-)
> 
> 73 Bill AE6JV
> 
> ---
> Bill Frantz| When all else fails: Voice   | Periwinkle
> (408)356-8506  | and CW.  | 16345 Englewood Ave
> www.pwpconsult.com |  | Los Gatos, CA 95032
> 
> 
> 
> ___
> 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] State QSO Parties

[Tom Melvin]

And for QSO parties that are NOT in the USA?

RSGB has a couple they introduced this year - doesn’t support FT? yet but it 
will come.

Pretty sure the abbreviations used for USA states will not match up with other 
countries.  The developers, if they are going to support QSO parties, will be 
looking at the global picture.

Tom

--
73’s

Tom
GM8MJV (IO85)





On 25 Sep 2019, at 22:19, Ron WV4P  wrote:

> As a coordinator for the Tennessee QSO Party we fielded the same questions 
> and had to respond the same. MANY wanted to use FT-X Modes. In kind, I don't 
> think TN would be any issue swapping to 3 Letter. Ron, WV4P 
> 
> On Wed, 25 Sep 2019 at 16:08, John Zantek  wrote:
> AKA "All I want for Christmas is something big for WSJT-X 2.2"
> 
> I just finished the 2019 Washington Salmon Run (our state QSO party), both as 
> a contestant and a coordinator.  My DX Club sponsors the event.  See 
> www.wwdxc.org/salmonrun
> 
> This year, we were inundated with inquiries of "Can we use FT8 or FT4?", all 
> of which I had to answer "No, sorry, not this year".  I see Nebraska 
> supported WSJT-X for their QSO party, but it required a totally separate log. 
>  Our Board felt the Salmon Run is too big and popular to create a whole 
> separate category and scoring system, and I didn't want to see the use of 
> FreeMsg frames being blasted blindly into the ether with unacknowledged 
> County exchanges.  I felt it was just abusive and counter to the vision of 
> WSJT-X's smart design.
> 
> I do believe that adding direct support to all the State QSO Parties could be 
> the 'next big thing' for WSJT-X.  Adding FD last year was a step in that 
> direction.  So rather than just ask, I thought "well, what would it require?"
> 
> CQ WAQP W7CD CN87
>W7CD K7ABC SPO(Spokane County)
> K7ABC W7CD R KITS   (Kitsap County)
>W7CD K7ABC RR73
> 
> Thus, I submit a blind start:
> 
> //  QRegExp message_alphabet {"[- A-Za-z0-9+./?]*"};
>   QRegularExpression message_alphabet {"[- @A-Za-z0-9+./?#<>]*"};
>   QRegularExpression WA_QSO_party_exchange {
> R"(
> (
>AL|AZ|AR|CA|CO|CT|DE|FL|GA  # 48 contiguous states
>   |ID|IL|IN|IA|KS|KY|LA|ME|MD
>   |MA|MI|MN|MS|MO|MT|NE|NV|NH|NJ
>   |NM|NY|NC|ND|OH|OK|OR|PA|RI|SC
>   |SD|TN|TX|UT|VT|VA|WA|WV|WI|WY
>   |NB|NS|QC|ON|MB|SK|AB|BC|NWT|NF  # VE provinces
>   |LB|NU|YT|PEI
>   |DC  # District of Columbia
>   |DX  # anyone else outside WA
>   |ADA|ASO|BEN|CHE|CLAL|CLAR|COL   # 39 WA counties
>   |COW|DOU|FER|FRA|GAR|GRAN|GRAY
>   |ISL|JEFF|KING|KITS|KITT|KLI
>   |LEW|LIN|MAS|OKA|PAC|PEND|PIE
>   |SAN|SKAG|SKAM|SNO|SPO|STE|THU
>   |WAH|WAL|SHA|WHI|YAK 
> )
>   )", QRegularExpression::CaseInsensitiveOption | 
> QRegularExpression::ExtendedPatternSyntaxOption};
> 
> 
> Of course, it's not just that simple, I knowbut I feel strongly enough 
> about the subject that I'm willing to try my hand at coding, something I've 
> not done since my FORTRAN77 and PDP-11 school days.
> 
> True, there are some arguments against putting in the effort.
> - Texas has 254 Counties.  My fingers ache just thinking about it.
> - Not every State has a QSO Party.  Out west, those states without the 
> support resources for their own QP (OR, MT, WY, etc) created the 7th Area QSO 
> Party (7QP), which is wildly popular.  It's exchange field requires a field 
> of 5 characters (2-ltr-State + 3-ltr County).
> -Instead of a QRegExp for each QP, a matrix of A through Z would 
> support any 5-ltr combo a particular State QP sponsor might devise.  Of 
> course, that leaves it to the end user to populate them in Settings/Advanced. 
>  Texans would think that insane.  7QP'ers would call it cruel and unusual 
> punishment.
> 
> Am I the only Voice in the Wilderness that thinks this would be worth it?  WA 
> is happily willing to shift from 4 letter County abbreviations to 3 letter if 
> it helps!
> 
> 73 John W7CD
> 
> 
> 
> 
> 
> 
> 
> ___
> 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 mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] v2.1.0 randomly stops decoding ft8

[Tom Melvin]

Alan

Just an observation - for many many people the software works well, the fact 
you cannot reproduce the issue does suggest IF it is an actual wsjtx bug it is 
pretty obscure.  

From doing software development in a different life these are the worst sort of 
issues - it could be rig setup, it could be other applications on the PC, could 
be latest windows (or whatever) update, supplier codex, etc. etc. - how much 
time is justified in tracking it down - you said it is a small team.

One option is to log the details, and then see how any others have issues over 
time, if more and more appear - is it same Rig? is it same version of the OS, 
is it the 32 or 64 bit version of the software (there are known issues with the 
64 bit that are tied to some dev libs) - you never actually mentioned which 
version you were using - if 64 have you tried the 32 bit?

While it may appear dev team are doing nothing it could be they are waiting to 
see if some common factor pops up - 1 week, 1 month, 1 year …  Your email seems 
to suggest you sort of expect the team to give it a higher priority (may be 
wrong but that was way I read the mail)

As to a bug list - yes there are a couple of issues I would like to see fixed - 
I know if a list was published there would be a flurry of activity (myself 
included)  ‘debating’ the severity/fix time scale - almost everyone would want 
their perceived bug higher up the list. All the dev team would end up doing is 
justifying the details.  I can see why no list is publicly available.

I’m sure when it can be reproduced it will be fixed.

Collect info, what is happening around the time of the freeze, are .wav files 
saved, anything running on PC at the time, time of day - how random is random, 
daily, weekly - collecting info in a little text file may provide pointers you 
can report to the team that may help.

Regards

Tom

--
73’s

Tom
GM8MJV (IO85)





On 28 Aug 2019, at 15:48, akirby03...@hotmail.com wrote:

> I assume that the development team uses some bug tracking package.  Is this 
> correct?
> 
> If so, was there a defect logged for the issue that I reported here?  If so, 
> what is the assigned severity and expected fix release?  If not, why not?
> 
> I, and many others, really appreciate the volunteer work done by the 
> development team on WSJT-X, but it would be really nice for users who report 
> a problem to know the status of their issue…
> 
> Thanks,
> 
> Alan / NX1W
> 
>> On Aug 26, 2019, at 4:02 PM, akirby03...@hotmail.com wrote:
>> 
>> Radio is an IC-7000. 
>> Audio is via USB audio dongle to radio ACC socket.  
>> 
>> 73
>> 
>>> On Aug 26, 2019, at 3:04 PM, Bill Somerville  wrote:
>>> 
>>> On 26/08/2019 19:19, Alan Kirby wrote:
 I have a PC continuously running WSJT-X FT8.  Once or twice each week, it 
 stops decoding all messages.  The clock is accurate to within 100ms and 
 the waterfall shows many signals.
  
 Restarting the program immediately fixes the problem.. I have observed 
 this issue with earlier versions of WSJT-X but had hoped the new version 
 would have fixed it.
  
 I cannot reproduce this at will – it appears to happen randomly.  I would 
 be happy to help the dev team collect data to diagnose this.
  
 Windows 10 (64 bit), Intel i5-6400, 2.7GHz 8GB DRAM
 WSJT-X v2.1.0
  
 Thanks,
  
 Alan (NX1W)
>>> Hi Alan,
>>> 
>>> which rig and how is it connected to your PC for audio?
>>> 
>>> 73
>>> Bill
>>> G4WJS.
>>> ___
>>> wsjt-devel mailing list
>>> wsjt-devel@lists.sourceforge.net
>>> https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.sourceforge.net%2Flists%2Flistinfo%2Fwsjt-develdata=02%7C01%7C%7Cc9b2173181844d73251c08d72a588c50%7C84df9e7fe9f640afb435%7C1%7C0%7C637024432130899006sdata=0jj5QtA%2Bna8d33AtgV4fg3ZED6Vc2XKH7Qu9xyHVysU%3Dreserved=0
>> 
> 
> ___
> 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] Field Day time problem

[Tom Melvin]

All

This posting by Fred gets my vote - easy, fool proof and does not distract the 
dev team.


--
73’s

Tom
GM8MJV (IO85)





On 24 Jun 2019, at 09:27, Fred Price  wrote:

> You are all overthinking the problem. There are programs to set your computer 
> clock by a GPS dongle. A good plug in dongle from Amazon is $12USD and the 
> program I use BktTimeSync is a free download.
> Also if the dev group keeps adding more n more WSJT will become bloatware. 
> I'd rather see improvements in what is in the software already. If you want a 
> color to denote a time that is getting out use JTAlert, it already has that 
> in it.
> 
> On Jun 24, 2019 4:07 AM, "DG2YCB, Uwe"  wrote:
> A very good idea to set up time beacons, Reino! I like this approach!
> 
>  
> However, as a short-term solution IMO dev team should find a way to use the 
> EXISTING data set of DT values for a pop-up saying that very likely time is 
> not synced correctly, plus an option to correct time by one click. Look the 
> following example. Only one station has a DT value which is totally out of 
> the average. Would be easy to detect such things by any well programmed 
> algorithm. Even the old JT65-HF software had two additional buttons, where 
> one could simply set PC clock + or – some 100 ms (until +- 2.5 s). Was very 
> helpful for fieldday activities. Just click on + or – as long as most of the 
> other stations have DT around 0. Simple approach, but worked 100%.
> 
>  
> 
> 
>  
> 73 de Uwe, DG2YCB
> 
>  
> -Ursprüngliche Nachricht-
> Hi,
> 
>  
> We are amateurs and could provide another time distribution experiment 
> especially during Field Day events. I mean setting up time beacon or beacons 
> that send e.g. every 15 s a short pulse, say 100 ms, on the base carrier 
> frequency e.g. 14.080 MHz. Timing of that pulse could be 'minute mark - 1 s' 
> or something similar agreed time. It would allow manual PC time setting in 
> the same manner as time marks of standard frequency stations. That 
> transmission would not disturb any FT8 message as nobody should transmit at 
> that time. It could be more useful, if the beacon frequency is set to 1 kHz 
> up (14.081), then you could hear it without detuning VFO and disturbing you 
> normal operation. Well, you could get same information from dT values 
> providing there are enough time accuracy in other stations and you timing is 
> good enough for decoding.
> 
>  
> Of course those beacons should be carefully synchronized to an accurate time 
> reference e.g. GPS. Depending on local regulations also a station identity 
> shall be sent at regular intervals using some applicable modulation perhaps 
> just before the time tick. I think that voluntary stations would provide this 
> service as needed.
> 
>  
> You could automate the time setting with a suitable program, if that could be 
> made safely and reliably (perhaps the pulses needs to be modulated for 
> identification), but that's next step if ever considered useful.
> 
>  
> 73 Reino oh3ma
> 
>  
>  
>  
> ___
> 
> 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 mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Plans for JT6m / FSK144

[Tom Melvin]

Hi

Thanks for update - much appreciated.

Tom


--
73’s

Tom
GM8MJV (IO85)





On 3 Jun 2019, at 16:33, Joe Taylor  wrote:

> Hi Tom,
> 
> There are no plans to support JT6m or FSK441 (which I assume you meant) in 
> WSJT-X.  These modes are deprecated because they have been superseded by 
> superior protocols.
> 
>   -- 73, Joe, K1JT
> 
> On 5/31/2019 7:10 PM, Tom Melvin wrote:
>> Hi Dev Team
>> WSJT supports JT6m and FSK144 while WSJT-X does not. There are a few people 
>> who, depending on mode / activity, still use those modes.
>> Can anyone tell me if adding those ‘older’ modes into WSJT-X is on the to-do 
>> list or will we still need to use V10 of WSJT?
>> 73’s
>> Tom
>> GM8MJV (IO85)
> 
> 
> ___
> 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] Plans for JT6m / FSK144

[Tom Melvin]

Hi Dev Team

WSJT supports JT6m and FSK144 while WSJT-X does not. There are a few people 
who, depending on mode / activity, still use those modes.

Can anyone tell me if adding those ‘older’ modes into WSJT-X is on the to-do 
list or will we still need to use V10 of WSJT? 

Thanks

Tom

--
73’s

Tom
GM8MJV (IO85)







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

Re: [wsjt-devel] Issue installing 2.1.0rc5

[Tom Melvin]

Hi OMOne of the main Mac maintainer’s lives in the UK - it is 4:30am here just now, you posting 4 hours ago - just after midnight local time.It can take a while for some posts to be answered, the Dev team are all volunteers and do need sleep :-)By the way have you checked the ‘Known Issues’ list:http://physics.princeton.edu/pulsar/k1jt/Reported_bugs.txt(see item 2 - it may help) - not saying it is what you are reporting but it may be easier to switch back to GA until a new Mac build is done.RegardsTom
--73’sTomGM8MJV (IO85)

On 2 May 2019, at 03:44, false via wsjt-devel  wrote: Hi, folks, hoping to get some help with this issue. I searched the 
Yahoo group archives and then sent this request to the group ~4 hours 
ago, have not received a response yet.  I renamed my old 
installation and installed the rc5 version;  the install process 
produced no errors but when I try to start the app, the below messages 
appear in Console. There are ~30 variations on the first message 
regarding varios frameworks when I initially attempt to start the app 
(after which the second message 
appears), any attempts to start the app again after the first attempt 
results only in the third error message. I have deleted the installation
 and reinstalled, with the same results. Any ideas? The 2.0 installation
 still functions... Mac Mini 2.3GHz i7 16GB running El Capitan (10.11.6)
 5/1/19 2:20:44.830 PM CoreServicesUIAgent[70277]: error -1 while 
removing quarantine data on path 
/Applications/wsjtx.app/Contents/Frameworks/QtWidgets.framework/Versions/Current
 5/1/19 2:20:44.887 PM com.apple.xpc.launchd[1]: 
(com.apple.xpc.launchd.oneshot.0x10bf.wsjtx[71512]) Service exited 
with abnormal code: 1 5/1/19 2:28:40.539 PM com.apple.xpc.launchd[1]: (org.k1jt.wsjtx.307232[71588]) Service exited with abnormal code: 1I'm attaching the full error message output as a text file.


5/1/19 2:20:44.817 PM CoreServicesUIAgent[70277]: error -1 while removing 
quarantine data on path 
/Applications/wsjtx.app/Contents/Frameworks/QtCore.framework/QtCore
5/1/19 2:20:44.817 PM CoreServicesUIAgent[70277]: error -1 while removing 
quarantine data on path 
/Applications/wsjtx.app/Contents/Frameworks/QtCore.framework/Resources
5/1/19 2:20:44.817 PM CoreServicesUIAgent[70277]: error -1 while removing 
quarantine data on path 
/Applications/wsjtx.app/Contents/Frameworks/QtCore.framework/Versions/Current
5/1/19 2:20:44.818 PM CoreServicesUIAgent[70277]: error -1 while removing 
quarantine data on path 
/Applications/wsjtx.app/Contents/Frameworks/QtDBus.framework/QtDBus
5/1/19 2:20:44.818 PM CoreServicesUIAgent[70277]: error -1 while removing 
quarantine data on path 
/Applications/wsjtx.app/Contents/Frameworks/QtDBus.framework/Resources
5/1/19 2:20:44.818 PM CoreServicesUIAgent[70277]: error -1 while removing 
quarantine data on path 
/Applications/wsjtx.app/Contents/Frameworks/QtDBus.framework/Versions/Current
5/1/19 2:20:44.819 PM CoreServicesUIAgent[70277]: error -1 while removing 
quarantine data on path 
/Applications/wsjtx.app/Contents/Frameworks/QtGui.framework/QtGui
5/1/19 2:20:44.819 PM CoreServicesUIAgent[70277]: error -1 while removing 
quarantine data on path 
/Applications/wsjtx.app/Contents/Frameworks/QtGui.framework/Resources
5/1/19 2:20:44.819 PM CoreServicesUIAgent[70277]: error -1 while removing 
quarantine data on path 
/Applications/wsjtx.app/Contents/Frameworks/QtGui.framework/Versions/Current
5/1/19 2:20:44.820 PM CoreServicesUIAgent[70277]: error -1 while removing 
quarantine data on path 
/Applications/wsjtx.app/Contents/Frameworks/QtMultimedia.framework/QtMultimedia
5/1/19 2:20:44.820 PM CoreServicesUIAgent[70277]: error -1 while removing 
quarantine data on path 
/Applications/wsjtx.app/Contents/Frameworks/QtMultimedia.framework/Resources
5/1/19 2:20:44.821 PM CoreServicesUIAgent[70277]: error -1 while removing 
quarantine data on path 
/Applications/wsjtx.app/Contents/Frameworks/QtMultimedia.framework/Versions/Current
5/1/19 2:20:44.821 PM CoreServicesUIAgent[70277]: error -1 while removing 
quarantine data on path 
/Applications/wsjtx.app/Contents/Frameworks/QtNetwork.framework/QtNetwork
5/1/19 2:20:44.821 PM CoreServicesUIAgent[70277]: error -1 while removing 
quarantine data on path 
/Applications/wsjtx.app/Contents/Frameworks/QtNetwork.framework/Resources
5/1/19 2:20:44.822 PM CoreServicesUIAgent[70277]: error -1 while removing 
quarantine data on path 
/Applications/wsjtx.app/Contents/Frameworks/QtNetwork.framework/Versions/Current
5/1/19 2:20:44.822 PM CoreServicesUIAgent[70277]: error -1 while removing 
quarantine data on path 
/Applications/wsjtx.app/Contents/Frameworks/QtPrintSupport.framework/QtPrintSupport
5/1/19 2:20:44.823 PM CoreServicesUIAgent[70277]: error -1 while removing 
quarantine data on path 
/Applications/wsjtx.app/Contents/Frameworks/QtPrintSupport.framework/Resources
5/1/19 2:20:44.823 PM CoreServicesUIAgent[70277]: error -1 while removing 
quarantine data on path 

Re: [wsjt-devel] The FT4 Protocol for Digital Contesting

[Tom Melvin]

Hi All

I don’t want to assume so will ask - FT4 aimed at ‘Contest Friendly digital 
modes’ - cool - BUT will it cater for the pile of weird contest rules that are 
out there. The abundance of requests for QSO Parties, Field Days where 
non-standards messages.  Heck for us UK VHF types - 6 character Locator squares 
etc.

Or … is this aimed specifically at the 'RTTY Contest types’

The docs on the web site for the RC does just refer to the RTTY contest - are 
other types in the pipeline?
If not then perhaps a subtle change to the description now before release may 
stop the multitude region/country contest requests hitting the reflector.

Tom

--
73’s

Tom
GM8MJV (IO85)





On 22 Apr 2019, at 16:34, Joe Taylor  wrote:

> To:   WSJT-X users interested in testing FT4
> From: K1JT, K9AN, and G4WJS
> 
> Soon after the "FT8 Roundup" held on December 1-2, 2018, we started serious 
> work on a faster, more contest-friendly digital mode that can compete with 
> RTTY-contesting QSO rates while preserving many of the benefits of FT8.  The 
> result is FT4 -- a new digital mode specifically designed for radio 
> contesting.
> 
> Over the past month a small group of volunteers have been conducting 
> on-the-air tests of FT4.  The early tests were very successful and helped us 
> to make a number of important design decisions.  We believe FT4 has 
> considerable promise for its intended purpose.
> 
> We'll soon be ready for testing by a larger group.  If you might be 
> interested in participating and offering your considered feedback, please 
> read the descriptive document "The FT4 Protocol for Digital Contesting", 
> posted here:
> http://physics.princeton.edu/pulsar/k1jt/FT4_Protocol.pdf
> 
> We plan to post downloadable installation packages for WSJT-X 2.1.0-rc5 on 
> April 29, one week from today.  The document linked above includes
> 
> - Instructions for installing WSJT-X 2.1.0-rc5 and FT4 configuration
> 
> - Operating instructions for FT4
> 
> - Basic description of the FT4 protocol, modulation, and waveform
> 
> - Detailed sensitivity measurements for FT4 under a wide variety of
>   simulated propagation conditions
> 
> - Schedule for upcoming test sessions
> 
> Please consider helping us to make FT4 a successful mode for digital 
> contesting
> 
> With best wishes and 73,
> 
>   -- Joe (K1JT), Steve (K9AN), and 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] FT8 DX Contest notices

[Tom Melvin]

What I can’t workout is why people are using EU VHF in the 1st place. 

It is not specifically in the rules page as Saku pointed out, but top of the 
contest page has a link to  FT8 settings, that clearly shows should be RTTY, 
the links to MSHV has a big page on contest setup, again says rtty - wsjt 
points to manual at contest settings.

So why are so many people using EU VHF?  - Hopefully as you all point out if it 
is specified on the same page as the rules it _may_ help.

Tom

--
73’s

Tom
GM8MJV (IO85)





On 14 Apr 2019, at 09:45, Saku  wrote:

> Neil Zampella kirjoitti 14.4.2019 klo 6.49:
>> That is something they will need to change if they decide to do another
>> one, declare what contest mode will be used.
>> 
>> Neil, KN3ILZ 
> 
> 
> Yes!
> 
> I agree!
> 
> 
> But it is bad thing that wsjt-x switches from RTTY RU to EU VHF automatic if 
> it detects that kind of answer.
> Backwards it does not do it. It just reminds that mode should be switched to 
> RTTY RU. But that needs user action via settings/advanced.
> 
> 
> And EU VHF is, I think, a little tested mode.  It is so unstabile.
> I did some UDP message testings a while ago with ft8sim and small mistakes 
> made wsjt-x crash with EU VHF. Mistakes means pressing wrong button at wrong 
> time. Sometimes crash kills also whole xwindow (LXDE) at same go.
> All other modes allow all kind of operations, but EU VHF is very sensible. 
> Everything must go in right order.
> 
> 
> -- 
> Saku
> OH1KH
> 
> 
> 
> ___
> 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] Someone released an Auto CQ mod

[Tom Melvin]

Hi All

Don’t want to get into a protected discussion on this as I suspect the Dev list 
is not suitable for some of it.

Take the automatic QSO Mod (I thought JTDX did that already) out of the 
equation, there are a couple of other features I saw in the posting that could 
be incorporated into the mainstream release:

Filter to exclude some prefixes - perhaps a local always on (JTDX Robot), want 
to filter, great add the callsign to a filter list, supports (simple) wildcard, 
want to ignore all Scotland, for example, add GM* - They won’t appear.

Noise issues - filter station above and below a certain Db reports.

Can’t cope with the colour settings, can display new calls only - filter out 
worked before to narrow down the ‘hit’ list.

Those three I can see being helpful and useful.

While I am against the Auto CQ option - would like to point out - the station 
posting on QRZ is European, in the UK at least, extract from Licence:

> 10(1) The Licensee may conduct Unattended Operation of Radio Equipment 
> provided that any such operation is consistent with the terms of this 
> Licence. Additional restrictions which apply to the Unattended Operation of 
> Beacons are specified in Schedule 2 to this Licence.



So in some parts of the world it’s legal, In looking at schedule 2 - I would 
watch calling WSPR a beacon. UK licence excludes any form of beacons between 
3.6Mhz and 28Mhz - even then the 80m and 10m bands it is only for DF hunting. 
Basically 4m upwards with a pile of other restrictions is ok - So any form of 
WSPR on HF is (as far as I can tell - would love to be corrected) illegal if 
its called a beacon.

Tom

P.S. I don’t like censorship so if the QRZ post has been removed it is a little 
worrying at what else are we not being told - It may be against FCC regs but 
not all of us are governed by them.


--
73’s

Tom
GM8MJV (IO85)





On 30 Mar 2019, at 15:23, Topher Petty  wrote:

> That's not only against the spirit of Amateur Radio, but it's also against 
> FCC rules regarding unattended operation. FT8 is NOT a beacon, and doesn't 
> fall under those rules.
> 
> Anyone who uses this deserves to be flogged repeatedly with a wet noodle, 
> and, if they're in the States, fined to the fullest extent of the regulations.
> 
> WSPR is a beacon, FT8 is not. This pisses me off to no end.
> 
> de AI8W, Chris
> 
> On Fri, Mar 29, 2019 at 2:28 PM Tag Loomis  wrote:
> Sorry, but some [expletive deleted] released an Auto CQ and Auto Responder 
> mod to WSJT-X
> 
> https://forums.qrz.com/index.php?threads/wsjt-x-full-auto-mod.652050/
> 
> I know there’s not much to be done about it, but man this makes me mad!
> 
> 
> -Stephen ‘Tag’ Loomis / N0TTL 
> ___
> 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 mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] [wsjtgroup] 70 Mhz Region 1 Freq

[Tom Melvin]

All

I have re-read what I posted and with hindsight I realise I was well over the 
top - there was no excuse.

I apologise to the groups (cross posted on purpose).

Would still like to get to the the bottom of a suitable frequency for 4m for 
those that have the allocation - yes 60m is similar.

Ron yes I know you can edit the frequencies - that is the little ‘niggle’ 
(which I blew out of proportion) - have already been through the exercise - all 
was working fine - for my area the _majority_ of users 70.154 fits - yes there 
is ZS which on Es may be possible - another couple of allocation is weird - but 
in general it worked.

Along comes an upgrade and woosh all the work gone - I can change it all back 
but what will happen on the next upgrade but that is in the future for just now.

Again I apologise to all

Regards

Tom
GM8MJV (IO85)





On 27 Feb 2019, at 12:02, 'vk3...@optusnet.com.au' vk3...@optusnet.com.au 
[wsjtgroup]  wrote:

> 
> Hi Tom
> I wish you would tell people what you think. 
> 
> It is not difficult to amend or add to  the frequencies although everyone in 
> your region will need to do that. Settings Frequencies add
> 
> We are still waiting for 60 m and a 4 m allocation is not getting any 
> attention now.
> 
> You live in luxury lad, lookshury.
> 
> 73
> Ron
> VK3AFW
> 
> 
> 
> Sent from my Telstra Signature™ Enhanced on the Telstra Mobile Network
> 
> -- Original message--
> From: Tom Melvin t...@tkrh.co.uk [wsjtgroup] /div>
> Date: Wed, 27 Feb 2019 10:42 PM
> To: wsjtgroup;
> Cc: WSJT software development;
> Subject:[wsjtgroup] 70 Mhz Region 1 Freq
> 
>  
> Ahhh
> 
> 
> What on earth made ‘you’ decide too reset used and recognised frequencies 
> from the list.
> 
> Region 1 FT8 on 70 Mhz 99.9% of people use 70.154 - this was pointed out to 
> one of the dev team end of January, poll was made on KST off region 1 users 
> and fed back - it looked as if there would be no issue in changing the 
> default. It would match up with majority of countries with 4m allocation, it 
> would fit in with other software implementations (where the default has 
> always been 70.154).
> 
> What do I find, no new default, in fact the latest upgrade will actually 
> remove the .154 (there was an edit option for that) and replace it with .100 
> 
> Lets cause no end of confusion - no wait, it will not affect the Americans or 
> affect the HF brigade so to heck with it - We are FT8 Gods the plebs WILL do 
> what we tell them.
> 
> Well done guys, software development at it’s best.
> 
> --
> 
> 73’s
> 
> Tom
> GM8MJV (IO85)
> 
> 
> 
> __._,_.___
> Posted by: "vk3...@optusnet.com.au" 
> Reply via web post•   Reply to sender •   Reply to group  •   
> Start a New Topic   •   Messages in this topic (3)
>  
> Have you tried the highest rated email app?
> With 4.5 stars in iTunes, the Yahoo Mail app is the highest rated email app 
> on the market. What are you waiting for? Now you can access all your inboxes 
> (Gmail, Outlook, AOL and more) in one place. Never delete an email again with 
> 1000GB of free cloud storage.
> To unsubscribe, send an email to:
> wsjtgroup-unsubscr...@yahoogroups.com
> VISIT YOUR GROUP
> • Privacy • Unsubscribe • Terms of Use
> 
> SPONSORED LINKS
> 
> 
> 
> .
>  
> 
> __,_._,___

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

[wsjt-devel] 70 Mhz Region 1 Freq

[Tom Melvin]

Ahhh

What on earth made ‘you’ decide too reset used and recognised frequencies from 
the list.

Region 1 FT8 on 70 Mhz 99.9% of people use 70.154 - this was pointed out to one 
of the dev team end of January, poll was made on KST off region 1 users and fed 
back - it looked as if there would be no issue in changing the default. It 
would match up with majority of countries with 4m allocation, it would fit in 
with other software implementations (where the default has always been 70.154).

What do I find, no new default, in fact the latest upgrade will actually remove 
the .154 (there was an edit option for that) and replace it with .100 

Lets cause no end of confusion - no wait, it will not affect the Americans or 
affect the HF brigade so to heck with it - We are FT8 Gods the plebs WILL do 
what we tell them.

Well done guys, software development at it’s best.

--

73’s

Tom
GM8MJV (IO85)

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

Re: [wsjt-devel] FT8 4m frequencies - was FT8 Freqs

[Tom Melvin]

Asked around on ON4KST and no-one has any strong view 

Lot of stations setting up skeds on 70.154 so would say unless there is a dev 
issue then for FT8 Region 1 it would be beneficial to set default in table to 
70.154


73’s

Tom
GM8MJV (IO85)





On 30 Jan 2019, at 16:21, Tom Melvin  wrote:

> Thanks for looking Bill
> 
> OK on SA bandplan - looking at 4m allocations - I _doubt_ will get a freq 
> that suits all.
> 
> Lets see if there is any feedback from other 4m users.
> 
> 
> 
> 73’s
> 
> Tom
> GM8MJV (IO85)
> 
> 
> 
> 
> 
> On 30 Jan 2019, at 13:12, Bill Somerville  wrote:
> 
>> On 30/01/2019 12:53, Tom Melvin wrote:
>>> All
>>> 
>>> Region 1 - UK 
>>> 
>>> While in the freq area - 70 Mhz - it’s set as 70.100  for FT8
>>> 
>>> However as this is not in the German allocation 99.9% of the FT8 4m 
>>> activity is centred around 70.154. Also 70.100 is right on the boundary of 
>>> the RSGB band Plan for ‘Personal Beacons’.
>>> 
>>> I see MSHV (which is popular over here due to the extra modes and is aimed 
>>> more at 50Mhz and above) has 4m FT8 preset at 70.154. Googling 70.100 and 
>>> 70.154 all the web pages  refer to 70.154 as FT8 freq - yes the odd proviso 
>>> that varying countries have different allocations so may never have one 
>>> freq that fits all on 70.
>>> 
>>> I would seem (IMHO) to have all the FT8 supported packages to have the same 
>>> frequency to save confusion once the Es session starts up.
>>> 
>>> Yes I know any one can edit the frequency table but half the users don’t 
>>> seem to know what the ‘Settings’ option actually does and where it is.
>>> 
>>> 
>>> 73’s
>>> 
>>> Tom
>>> GM8MJV (IO85)
>> Tom,
>> 
>> I consulted with some regular users of WSJT modes on 4m and was promised 
>> that they would get back to me with a best option for a 4m working frequency 
>> in IARU Region 1. They did not get back to me and I am still waiting. If 
>> 70.154 is the de facto working frequency in Region 1 then I will happily 
>> change the default in WSJT-X.
>> 
>> One thing that should be considered is compatibility with the South African 
>> band plan which appears to have 70.150 - 70.200 allocated to digital FM 
>> modes that would not interact well with FT8.
>> 
>> Comments from regular 4m digi-mode operators welcome.
>> 
>> 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 mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] FT8 4m frequencies - was FT8 Freqs

[Tom Melvin]

Thanks for looking Bill

OK on SA bandplan - looking at 4m allocations - I _doubt_ will get a freq that 
suits all.

Lets see if there is any feedback from other 4m users.



73’s

Tom
GM8MJV (IO85)





On 30 Jan 2019, at 13:12, Bill Somerville  wrote:

> On 30/01/2019 12:53, Tom Melvin wrote:
>> All
>> 
>> Region 1 - UK 
>> 
>> While in the freq area - 70 Mhz - it’s set as 70.100  for FT8
>> 
>> However as this is not in the German allocation 99.9% of the FT8 4m activity 
>> is centred around 70.154. Also 70.100 is right on the boundary of the RSGB 
>> band Plan for ‘Personal Beacons’.
>> 
>> I see MSHV (which is popular over here due to the extra modes and is aimed 
>> more at 50Mhz and above) has 4m FT8 preset at 70.154. Googling 70.100 and 
>> 70.154 all the web pages  refer to 70.154 as FT8 freq - yes the odd proviso 
>> that varying countries have different allocations so may never have one freq 
>> that fits all on 70.
>> 
>> I would seem (IMHO) to have all the FT8 supported packages to have the same 
>> frequency to save confusion once the Es session starts up.
>> 
>> Yes I know any one can edit the frequency table but half the users don’t 
>> seem to know what the ‘Settings’ option actually does and where it is.
>> 
>> 
>> 73’s
>> 
>> Tom
>> GM8MJV (IO85)
> Tom,
> 
> I consulted with some regular users of WSJT modes on 4m and was promised that 
> they would get back to me with a best option for a 4m working frequency in 
> IARU Region 1. They did not get back to me and I am still waiting. If 70.154 
> is the de facto working frequency in Region 1 then I will happily change the 
> default in WSJT-X.
> 
> One thing that should be considered is compatibility with the South African 
> band plan which appears to have 70.150 - 70.200 allocated to digital FM modes 
> that would not interact well with FT8.
> 
> Comments from regular 4m digi-mode operators welcome.
> 
> 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] FT8 Freqs

[Tom Melvin]

All

Region 1 - UK 

While in the freq area - 70 Mhz - it’s set as 70.100  for FT8

However as this is not in the German allocation 99.9% of the FT8 4m activity is 
centred around 70.154. Also 70.100 is right on the boundary of the RSGB band 
Plan for ‘Personal Beacons’.

I see MSHV (which is popular over here due to the extra modes and is aimed more 
at 50Mhz and above) has 4m FT8 preset at 70.154. Googling 70.100 and 70.154 all 
the web pages  refer to 70.154 as FT8 freq - yes the odd proviso that varying 
countries have different allocations so may never have one freq that fits all 
on 70.

I would seem (IMHO) to have all the FT8 supported packages to have the same 
frequency to save confusion once the Es session starts up.

Yes I know any one can edit the frequency table but half the users don’t seem 
to know what the ‘Settings’ option actually does and where it is.


73’s

Tom
GM8MJV (IO85)





On 30 Jan 2019, at 11:11, Bill Somerville  wrote:

> On 30/01/2019 05:56, Black Michael via wsjt-devel wrote:
>> I guess it was deliberate to include the JT9 frequencies in the FT8 
>> frequency list for 20M and 40M?
>> 
>>{14074000, Modes::FT8, IARURegions::ALL},
>>   {14076000, Modes::JT65, IARURegions::ALL},
>>   {14078000, Modes::FT8, IARURegions::ALL},
>>   {14078000, Modes::JT9, IARURegions::ALL},
>>{7038600, Modes::WSPR, IARURegions::ALL},
>>   {7074000, Modes::FT8, IARURegions::ALL},
>>   {7076000, Modes::JT65, IARURegions::ALL},
>>   {7078000, Modes::FT8, IARURegions::ALL},
>>   {7078000, Modes::JT9, IARURegions::ALL},
> Hi Mike,
> 
> yes but only for the v2.0.0 beta testing, they should have been removed 
> before GA. I have removed them for the next release. Thanks.
> 
> 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] Decode lite up - no decode

[Tom Melvin]

Hi All

Yes work around is to have all instances use the —rig-name=xxx option 


Joe - there are times I don’t want to run wsjtx on 6m (the instance with no 
—rig-name option) - I could be using jt6, FSK411 for MS (a lot of UK contests 
still don’t support FT8/MSK) which wsjtx does not support - so I just start HF 
to check conditions —rig-name=HF instance - work away. Finish with MSHV and 
switch back to wsjtx to use MSK/FT8 - that would kill the HF screen.

I have been running all night here with —rig-name=HF and —rig-name=VHF and all 
is 100% no mater what order I use.

I’m pretty sure the software could check for running wsjtx processes (jtalert 
does it well) and if there are none, other that the one just started, then kill 
the jt9  exe - if there are existing wsjtx processes don’t kill - that would 
deal with the rogue process and handle the —rig-name option.

73’s

Tom
GM8MJV (IO85)





On 29 Jan 2019, at 21:40, Joe Taylor  wrote:

> Hi Tom,
> 
>> Pretty daft to kill processes that may be needed on an assumption.
> 
> It's not daft, at all.  Probably 99% of WSJT-X users run only one instance.  
> In the rare but not unheard-of case where something caused a program crash, 
> jt9.exe may be left running.  When WSJT-X is re-started, that zombie jt9.exe 
> must be killed.
> 
> Surely it's easy enough for you to start your instances in the proper order?  
> The ~1% of users running multiple instances have been doing that for years, 
> with no issues.
> 
>   -- Joe, K1JT
> 



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

Re: [wsjt-devel] Decode lite up - no decode

[Tom Melvin]

Thanks Mike

So that means you MUST start the single instance first no matter what.  That 
does agree with what I am seeing - nothing in the docs to say there is a ‘start 
up’ order.

As a work around I will try to set all my wsjtx instances to use a —rig-name 
option and see if that will help keep things running.

Pretty daft to kill processes that may be needed on an assumption.

--

73’s

Tom
GM8MJV (IO85)





On 29 Jan 2019, at 17:54, Black Michael via wsjt-devel 
 wrote:

> It is coded that way.  When you start with --rig-name it knows to expect 
> multiple instances.  Without --rig-name it assumes you're running only one 
> and kills the jt9 process...but doesn't kill the wsjtx process...which seems 
> wrong.
> 
> I suppose it's possible to make that check a bit better to allow either 
> sequence
> 
> de Mike W9MDB
> 
> 
> 
> 
> On Monday, January 28, 2019, 4:36:51 PM CST, Tom Melvin  
> wrote:
> 
> 
> 
> Good day all
> 
> Posted over in general wsjtx list not much joy - Been playing and need some 
> advice
> 
> One PC, multiple Audio connections to two separate transceivers - wsjtx v2.0.0
> 
> Start one  wsjtx —rig-name=test   wsjt starts up and runs fine
> 
> Start another instance but no —rig-name - wsjtx starts up and runs fine but 
> the original instance has stopped decoding, icon on all the time.
> 
> This only happens if you start the —rig-name=xx instance BEFORE the plain 
> one. If you start the main instance first, then the —rig-name=xx and don’t 
> restart or change config both will work 100% ok. As soon as you restart or 
> change config on the ‘main’ instance the —rig-name instance will lock up.
> 
> Looking at task manager the jt9 process no longer exists on the 1st one.
> 
> Have tried this with main ham setup on windows 7, as a test loaded wsjtx on a 
> stand alone Windows 10 laptop and same problem.
> 
> Compiled from source, on windows 10 laptop and same problem.
> 
> I can reproduce this 100% on two different PC’s with different versions of 
> windows.
> 
> Is the a way I can see in a little more details what was happening that would 
> cause the jt9 process to die?
> 
> 
> 73’s
> 
> Tom
> GM8MJV (IO85)
> 
> 
> 
> 
> ___
> 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 mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

[wsjt-devel] Decode lite up - no decode

[Tom Melvin]

Good day allPosted over in general wsjtx list not much joy - Been playing and need some adviceOne PC, multiple Audio connections to two separate transceivers - wsjtx v2.0.0Start one      wsjtx —rig-name=test   wsjt starts up and runs fineStart another instance but no —rig-name - wsjtx starts up and runs fine but the original instance has stopped decoding, icon on all the time.This only happens if you start the —rig-name=xx instance BEFORE the plain one. If you start the main instance first, then the —rig-name=xx and don’t restart or change config both will work 100% ok. As soon as you restart or change config on the ‘main’ instance the —rig-name instance will lock up.Looking at task manager the jt9 process no longer exists on the 1st one.Have tried this with main ham setup on windows 7, as a test loaded wsjtx on a stand alone Windows 10 laptop and same problem.Compiled from source, on windows 10 laptop and same problem.I can reproduce this 100% on two different PC’s with different versions of windows.Is the a way I can see in a little more details what was happening that would cause the jt9 process to die?73’sTomGM8MJV (IO85)

___
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

[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] RC 5 issue entering Field Day info

[Tom Melvin]

Mike

Are we not talking about Winter Field day here NOT the Roundup thing.

Tom

--

73’s

Tom
GM8MJV (IO85)





On 30 Nov 2018, at 20:08, Black Michael via wsjt-devel 
 wrote:

> That's not the format for the FT8 Roundup
> It only takes the state in the exchange and a signal report.
> 
> Check paragraph 4 here.
> 
> https://www.rttycontesting.com/ft8-roundup/rules/
> 
> de Mike W9MDB
> 
> On Friday, November 30, 2018, 1:39:38 PM CST, Al Flapan  
> wrote:
> 
> 
> I went to settings and advanced to enter the info for the exchange and 
> was only able to enter the class !E and it would not let me enter the 
> rest which is the section info of SFL. I takes the info for the rtty 
> exchange with no problem.
> 
> Al AF4FA
> 
> 
> 
> ___
> 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 mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Post a "Know Issues" list?

[Tom Melvin]

Hi Richard


Well the LOTW problem , can’t decode 75 bit message are both in the 
Release/Quick Start guide - but that is beside the point

The new page would address it - the only source of the RC downloads is via the 
princeton site (mind you I think if it were hosted outside the US then the 
developers could include the ssl fix directly as it is no longer an export so 
gets past the restrictions).

But …. the full GA should be available shortly  - about couple of weeks … so 
lists and pages won’t apply this time.  

The dev guys may want to consider something for the next round of Beta tests in 
xx months.


73’s

Tom
GM8MJV (IO85)





On 23 Nov 2018, at 15:05, Richard Zwirko - K1HTV  wrote:

> 
> Tom,
>   Regarding your comments about the release notes, if fact almost all of the 
> issues that I addressed as examples are NOT covered in the latest released 
> notes.
> 
> I do like your idea of having to go to another page to read the list of known 
> issues (and then possibly having to check a box?)  before being able to 
> download the latest RC version. 
> 
> As far as maintenance of the list, it would take far less time for developers 
> like Joe, Bill(s), Mike, etc. to add a new known RC issue to the list than 
> having to compose separate replies to users, as is being done now.
> 
> 73,
> Rich - K1HTV
> 
> = = =
> 
> From: Richard Zwirko - K1HTV 
> To: "G4WJS, Bill" , WSJT 
> 
> Cc: 
> Bcc: 
> Date: Fri, 23 Nov 2018 04:01:04 -0500
> Subject: [wsjt-devel] Post a "Know Issues" list?
> Bill, et al,
> Wouldn't it be a good idea to post a list of known WSJT-X issues on a regular 
> basis? We all see SO MANY repeat posts complaining about problems being 
> experienced with release candidates. Hopefully, posting such a list would 
> greatly reduce repeat problem complaints.
> 
> Some known issues could include:
> > Colors for stations worked/needed, etc aren't working.
> > Poor RC4 sensitivity (Not a problem, RC4 can't copy 75 bit signals)
> > Why the error message about LOTW and how to fix it (Win32 Open SSL)
> > Not running split and wondering why stations don't copy TX tones above 2500 
> > HZ.
> > Etc, etc.
> 
> 73,
> Rich - K1HTV
> 
> 
> 
> -- Forwarded message --
> From: Tom Melvin 
> To: WSJT software development 
> Cc: 
> Bcc: 
> Date: Fri, 23 Nov 2018 10:38:20 +
> Subject: Re: [wsjt-devel] Post a "Know Issues" list?
> Do you think that would help 90% of the posters - sorry I don’t think so.
> 
> The 77 bit signal and LOTW errors are very clearly mentioned in the release 
> notes - which everyone is advised to read but don't
> 
> Those looking at the mailing lists - there is an archive/search option - even 
> just reading what was in last few hours in some cases would show the answer.
> 
> Posting a list - while many people will get a nice warm feeling of things 
> actually happening esp on some of the more obscure issues but don’t think 
> will affect the number of similar queries.
> 
> Many people do not understand the concept of beta tests - they think it is 
> just another upgrade, jump in with both feet and are surprised when there is 
> a slight issue, panic, scream and start reloading old versions and wasting so 
> much of their time in the process where a 1 mins check of the dreaded … 
> Release Notes - would have answered it.
> 
> Human nature is not to RTFM no getting away from it - posting a list of 
> known/fixed issues would be great to refer people to but won’t cut down 
> repetitive questions.
> 
> 73’s
> 
> Tom - GM8MJV
> 
> P.S. What may help is on the download page you have to go via another page of 
> ‘issues’ before being able to download but that would take maintenance and 
> the dev teams have better things to do.
> 
> 

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

Re: [wsjt-devel] Post a "Know Issues" list?

[Tom Melvin]

Do you think that would help 90% of the posters - sorry I don’t think so.

The 77 bit signal and LOTW errors are very clearly mentioned in the release 
notes - which everyone is advised to read but don't

Those looking at the mailing lists - there is an archive/search option - even 
just reading what was in last few hours in some cases would show the answer.

Posting a list - while many people will get a nice warm feeling of things 
actually happening esp on some of the more obscure issues but don’t think will 
affect the number of similar queries.

Many people do not understand the concept of beta tests - they think it is just 
another upgrade, jump in with both feet and are surprised when there is a 
slight issue, panic, scream and start reloading old versions and wasting so 
much of their time in the process where a 1 mins check of the dreaded … Release 
Notes - would have answered it.

Human nature is not to RTFM no getting away from it - posting a list of 
known/fixed issues would be great to refer people to but won’t cut down 
repetitive questions.

73’s

Tom - GM8MJV

P.S. What may help is on the download page you have to go via another page of 
‘issues’ before being able to download but that would take maintenance and the 
dev teams have better things to do.





On 23 Nov 2018, at 09:01, Richard Zwirko - K1HTV  wrote:

> Bill, et al,
> Wouldn't it be a good idea to post a list of known WSJT-X issues on a regular 
> basis? We all see SO MANY repeat posts complaining about problems being 
> experienced with release candidates. Hopefully, posting such a list would 
> greatly reduce repeat problem complaints.
> 
> Some known issues could include:
> > Colors for stations worked/needed, etc aren't working.
> > Poor RC4 sensitivity (Not a problem, RC4 can't copy 75 bit signals)
> > Why the error message about LOTW and how to fix it (Win32 Open SSL)
> > Not running split and wondering why stations don't copy TX tones above 2500 
> > HZ.
> > Etc, etc.
> 
> 73,
> Rich - K1HTV
> ___
> 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] RC4 Crash on Logging - observation

[Tom Melvin]

It seems to be due to the sent exchange field not being populated

See:  https://sourceforge.net/p/wsjt/mailman/message/36472011/

It applies to EU-Contest mode as well


73’s

Tom
GM8MJV (IO85)





On 21 Nov 2018, at 01:37, Neal Pollack  wrote:

> I noticed that I could 100% reproduce a crash (app windows vanish, no error 
> message) if
> I click on OK in the Log Prompting dialog pop-up box, WHILE the final 73 was 
> still transmitting.
> If I wait until transmit completes, and THEN click OK to the log dialog box, 
> the app is OK and
> does NOT crash.  I tried 30 additional contact this way with no crash.
> So the crash has something to do with clicking OK to log DURING transmit, on 
> windows ver 1803.
> Not tested with windows 10 ver 1809.
> 
> This is with windows 10 x64 version 1803.   (Not tested with windows 10 ver 
> 1809.)
> This is with core i7 CPU, 16GB memory, and using JTalert (latest version) and 
> using Ham Radio
> Deluxe logger, latest version.
> 
> To confirm, I did a second installation of WSJT-X ver 2 RC4 in a different 
> directory.
> It will also crash 100% of the time if you click on OK in the log dialog 
> pop-up box
> WHILE it is still transmitting the final 73.
> 
> Neal
> N6YFM
> ___
> 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] Fox at 7074 ?

[Tom Melvin]

It may be an older version of WSJT-X - couple of releases allowed that to 
happen.

--

73’s

Tom
GM8MJV (IO85)





On 8 Nov 2018, at 21:25, Pino Zollo  wrote:

> Wasn't it disabled on standard frequencies ?
> 
> 73 ZP4KFX
> 
> 
> 212100  Tx   752 ~  KH2F ZP4KFX GG14  
> 212045 -13  0.1 2493 ~  ZP4KFX UN3GX MN83
> 212115 -12  0.4  695 ~  ZP4KFX KH2F -25
> 212130  Tx   752 ~  KH2F ZP4KFX R-12  
> 212115 -10  0.1 2493 ~  ZP4KFX UN3GX MN83
> 212145  -9  0.3  695 ~  ZP4KFX RR73; SP9HZW  -22
> 212200  Tx   752 ~  KH2F ZP4KFX R-12   
> 
> ___
> 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] Possible bug (?) 1.9.1 with numeric msg

[Tom Melvin]

Feature

CQ NUMBER call

The system will as you saw QSY to that freq and carry on the QSO there.

It is a very common option on Meteor Scatter or when 6m Es taking place - keeps 
QRM on calling freq down.

It’s in the manual somewhere (not that obvious from memory) but is there.

Tom
GM8MJV


On 20 Oct 2018, at 16:04, Paul Bramscher  wrote:

> Running WSJT-X 1.9.1 r8747 compiled on Debian (AMD64) Linux.   A couple days 
> ago an operator on 20M FT8 was calling CQ 052 {his call | his grid}.  Out of 
> curiosity I clicked his message in the band activity pane.  My radio then 
> switched to 14.052 MHz and the freq. pane turned red (indicating a 
> non-standard FT8 freq.) .  In the Rx Frequency pane, I got purple messages 
> stating "QSY 14.052".
> 
> 
> 
> Is this a bug or a feature that I've not seen yet?
> 
> 
> 
> Regards,
> 
> 73, KD0KZE / Paul
> 
> ___
> 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] "L" instead of colors for LOTW

[Tom Melvin]

Ted

The ~ is used to say what mode you are in ~=FT8, #=JT64 etc.

The list of options is covered in section 12.2 of the manual

Tom
GM8MJV

On 19 Oct 2018, at 01:25, Ted Gisske  wrote:

> More importantly…Leave the colors to something that can be uniquely defined. 
> LoTW yes/no is important in a number of other categories, so muddies the 
> water if it is just assigned to a color. Perhaps replacing the “~” in the 
> decode with a L would work. I cannot figure out what the tilde does otherwise.
> 73,
> Ted
> K9IMM
>  
> From: Hasan al-Basri [mailto:hbasri.schie...@gmail.com] 
> Sent: Thursday, October 18, 2018 7:13 PM
> To: WSJT software development
> Cc: WSJT Group
> Subject: Re: [wsjt-devel] "L" instead of colors for LOTW
>  
> I agree, the colors are becoming so ubiquitous, that they end up diguising as 
> much as they highlight.
>  
> Some color is good, a lot of color can be overwhelming. I like a simple L for 
> LoTW user. Save the colors for things more dramatic that require immediate 
> notice like CQ, and My call
>  
>  
> 
> Hasan
>  
> On Thu, Oct 18, 2018, 5:09 PM Richard Zwirko - K1HTV  
> wrote:
> With the past few WSJT-X release candidates there have been a number of 
> concerns expressed about the use of colored letters over various colored 
> backgrounds to indicate decoded stations that use LOTW. In addition to the 
> visibility issues, the user now has to remember the meanings of the various 
> colors. 
>  
> If it is at all possible, why not get away from colors and KISS. Keep It 
> Simple   use a single letter "L" to indicate an LOTW using station. The 
> "L" could be placed on the far right side of the line after the country 
> prefix or name. RXCLUS, a program that I've been using for over a decade to 
> monitor DXcluster nodes, appends an "L" on the far right side of putouts for 
> LOTW users. It works great. If you don't want to see it, simply shrink the 
> right side of the display. 
>  
> I believe that the use of an "L" versus using various colors is a much more 
> effective and less confusing way to indicate FT8 stations that use LOTW.
>  
> 73, 
> Rich - K1HTV
>  
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>  
> 
> Virus-free. www.avg.com
>  
> ___
> 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] Autoseq on previous QSO

[Tom Melvin]

Would it not just be easier to Un-Tick the ‘Double Click on call sets TX 
Enable’  in Settings - you can click to your hearts content, do the DX lookup, 
play with QRZ etc.

Make sure they have finished and when you are happy with split/freq etc. just 
click Enable button

Lot less chance of making errors 

Tom
GM8MJV




On 15 Oct 2018, at 19:55, Carey Fisher  wrote:

> Yes, Gary's right. I would like a single click (or ???) to do the lookup so I 
> don't have to "quickly jab the Halt Tx button".
> 
> On Mon, Oct 15, 2018 at 2:39 PM Gary McDuffie  wrote:
> 
> 
> > On Oct 15, 2018, at 11:22, Black Michael via wsjt-devel 
> >  wrote:
> > 
> > Maybe we have a different opinion of the path-of-least-resistance here.
> 
> Personally, I often double click a line just to have the callsign looked up 
> and get the grid, whether I intend to work him or not.  I just have to 
> quickly jab the halt tx button to be sure it doesn’t go out or at least is 
> limited to a second or so transmit, if that.
> 
> Gary - AG0N
> 
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
> 
> 
> -- 
> Carey Fisher
> careyfis...@gmail.com
> 
> ___
> 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] Hold Tx freq

[Tom Melvin]

Report on v2 rc1
Windows 7

With cat control working well I find myself on 6m/4m/2m switching quickly 
between FT8 and MSK144 to check for activity.  

If I set up multiple configurations that is approx six different configuration 
options - as the config option can get ‘messed up’ if any changes made it is a 
lot easier and quicker just to use the mode menu option.

If ‘Hold TX Freq’ is ticked on FT8, you change to MSK144 then return to FT8 the 
‘Hold TX’ box is no longer ticked.

On an earlier version 1.9.x a similar issue existed except it was on ‘Call 
first' - this is OK with version 2.

Tom
GM8MJV




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

Re: [wsjt-devel] WSJT-X need to log the end time of QSO not the start

[Tom Melvin]

Jim

For your info - we don’t really need to keep a log unless asked to do so.

> 12(1) For the purposes of any interference investigation, to determine 
> compliance with the terms, conditions and limitations of this Licence, or for 
> any other matter concerning the enforcement of any relevant legislation, the 
> Licensee shall at the request of a person authorised by Ofcom, keep a 
> permanent record (a “log”) of such matters concerning the operation of the 
> Radio Equipment, over such period, and in such form, as the authorised person 
> may require.


However, it is handy in-case there are ‘interference’ or ‘Bad signal’ reports - 
in advance of being asked. Also with some of the longer communications methods 
- Meter Scatter etc. the ‘length of the QSO is handy.

73’s

Tom
GM8MJV



On 2 Aug 2018, at 17:28, Jim Brown  wrote:

> On 8/1/2018 6:00 PM, Ed Stallman wrote:
>> Love both FT8 and N1MM + logger,
> 
> So do I, but only for contest logging. My primary log is DXKeeper, which DOES 
> record start and stop times, and is designed to be a general purpose logger. 
> N1MM doesn't bother with start and stop times because contest QSOs are 
> intentionally too short for that to matter. WSJT-X integrates very well with 
> DXKeeper and with N1MM when used with JTAlert. I used it that way in the 
> recent CQWW VHF contest. Outside of contests, I log directly to DXKeeper.
> 
> I don't know the law in the UK, but the logging requirement for US hams was 
> eliminated MANY years ago.
> 
> 73, Jim K9YC
> 
> --
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
> 


--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] WSJT-X need to log the end time of QSO not the start

[Tom Melvin]

Ed,

Just my 2p worth

There will be a LOT of flack if wsjt was to just  log the end time - I want to 
know when I started the QSO not when finished - thankfully I use a ‘Normal’ 
logger that handles start/finish times and all works as it should. It keeps me 
within the terms of my licence - recording when ‘on’ the air. 

I have been monitoring the wsjt forums for quite a while now and this is the 
1st time seen this so I don’t think you will get much support for a change.

There is an obvious solution but as you have said you like using a contest 
logger and won’t change.  The N1MM software _could_ record both timestamps and 
only export the end time to the cabrillo log but looks like that is not an 
option either.



73’s
Tom
GM8MJV


On 2 Aug 2018, at 02:00, Ed Stallman  wrote:

> Please read from bottom up... I started this message with the Yahoo WSJT-X 
> group , I was told this  is an N1MM + issue . So I sent the message to the 
> N1MM + user group and as you can read below , I'm told the issue is with 
> WSJT=X 
> I'm only a user of N1MM + and WSJT-X FT8 mode !  In WSJT-X settings / 
> Reporting ( N1MM logger + Broadcast )  I have checked Enable logged contact 
> ADIF .. Now if the log time was at the end of the QSO , Club Log , LoTW and 
> the user's would all be happy.
> 
> Now all this is not really a big issue , I can mentally detect the QSO is 
> taking a long time and edit the time when QSO is  complete 
> Love both FT8 and N1MM + logger, Ed N5DG
> 
> 
> 
> Amplifying what Steve says, in a contest, a QSO must be *completed* before 
> the end of the contest.  If it is not, it doesn't count.  Since there is only 
> one timestamp in a Cabrillo log, it should be the ending time of the contact. 
> 
> 73, 
> 
> Tom - N1MM 
> 
> 
> On 8/1/2018 6:41 PM, Steve London wrote: 
> I have brought up this issue on WSJT-X forums in the context of the LoTW time 
> match window. When normally logging a QSO in N1MM+, without WSJT, the 
> completion time of the QSO is finished and logged. I consider that to be 
> correct. As you have noticed, WSJT sends the start time to N1MM+. IMHO, that 
> is not correct. WSJT-X folks have a different opinion. You really should take 
> up this issue with the WSJT-X folks. 
> 
> 73, 
> Steve, N2IC 
> 
> On 08/01/2018 04:29 PM, ed.n...@gmail.com wrote: 
> This may have  been discussed and I missed it . I worked and logged Z66X on 
> 10m FT8 , it was not an easy contact . I would stop and start again as QSB 
> permitted . After receiving  and sending 73's I clicked log it in the WSJT 
> program and WSJT sends the Q to N1MM plus . Now a few days later I'm filling 
> in date and time using Club Log   OQRS and I was not getting a match . I 
> remembered , I made a WSJT screenshot . My screenshot time was 26 minutes 
> later then the time WSJT / N1MM+ logged the QSO ! Entering the screenshot 
> time was a match in club log . 
> 
> Now I'm keeping a close eye on the WSJT log time and it appears to use  only 
> the start time when sending to N1MM+ or should I say N1MM only grabs the 
> start time 
> 
> I see WSJT has a start and end time so It would be great if N1MM+ would use 
> the end time , or both ... 
> 
> Now I know N1MM + is a contest log and I'm using iit as a general log but 
> that is because I like it and won't use any other logging software . I'm only 
> asking for a simple change and can't see it making a bit of difference for 
> contester logging the start or the end of the QSO . 
> 
> If I'm asking for to much , It's simple ... If my DX QSO is timely, I'll 
> change the time manually but I will not stop using N1MM Logger 
> 
> Thanks for reading, Good luck with ur contesting, Ed N5DG 
> 
> 
>   Virus-free. www.avg.com
> --
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! 
> http://sdm.link/slashdot___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] yaesu ftdx 3000 parameters

[Tom Melvin]

Hi   OM

It was not a wise crack answer - WHAT ERROR ARE YOU GETTING ?

Have scanned the mail for 6 months for your call - it is not there - so since I 
can’t find your earlier mail perhaps others as may have missed your mail.

There is some info on the general wsjt mailing list at:

https://groups.yahoo.com/neo/groups/wsjtgroup/conversations/topics/30198

That relates to the settings of the 1200 v 3000 - all I can offer without more 
details.

Tom
GM8MJV



On 2 Jul 2018, at 16:09,   wrote:

> well my mail must have gotten lost. and wisecrack answers like can't read my 
> mind turn me off. I have the latest version 1.9.1 as far as I know run 
> windows 10 on a hp I-5 and run AC log with CAT control mmty direct fsk and a 
> multitude of other digital modes. as I said I need some parameters for my 
> radio if you can't help say so don't insult me I've been on digital modes 
> over 25 years!!!
> 
>  Tom Melvin  wrote: 
>> See the details at the bottom of every mail 
>> 
>>>> wsjt-devel@lists.sourceforge.net
>>>> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>> 
>> 
>> It allows you to manage  your subscriptions yourself - no-one else can do it.
>> 
>> It may be worthwhile (have checked and you have never posted with that call 
>> before) to 
>> 
>> a) Tell us the error message you get
>> b) Which version of wsjt-x had you used in the past.
>> c) How about what OS and version
>> d) What have you tried so far.
>> 
>> I personally have never used the Yaesu 3000 or 5000 - so no idea about that 
>> side.
>> 
>> I do know if you do give people the chance to see what the problem is you 
>> will have a better chance at getting a response that just assuming someone 
>> will have miraculously read your mind and posted the answer.
>> 
>> Tom
>> GM8MJV
>> 
>> 
>> On 2 Jul 2018, at 14:23, kb...@neo.rr.com wrote:
>> 
>>> I originally joined this group to get the exact parameters for my yaesu 
>>> 3000. first of all it isn't listed in the drop down menu, I tried using the 
>>> 5000 instead and set everything I could find and it came back error so 
>>> since I can't seem to get this information and all the mails I see are not 
>>> of interest to me please drop me from the group. I have been wiring 
>>> computers to my radios since the mid 90's used almost every digital mode 
>>> out there and never had trouble accessing software before ft8 was fine til 
>>> you added the dxpedition mode then I could not get it to work. I've 
>>> thoroughly read all the instructions I'm not a dummy and still can't get 
>>> CAT control to my 3000. I will continue to use it as before through my 
>>> rigblaster but I give up on dxpedition mode. please remove me from future 
>>> mailings. 
>>> 
>>>  de KB3MI  @ kb...@neo.rr.com
>>> 
>>> --
>>> Check out the vibrant tech community on one of the world's most
>>> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>>> ___
>>> wsjt-devel mailing list
>>> wsjt-devel@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>>> 
>> 
>> 
>> --
>> Check out the vibrant tech community on one of the world's most
>> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>> ___
>> wsjt-devel mailing list
>> wsjt-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
> 
> 


--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] yaesu ftdx 3000 parameters

[Tom Melvin]

See the details at the bottom of every mail 

>> wsjt-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/wsjt-devel


It allows you to manage  your subscriptions yourself - no-one else can do it.

It may be worthwhile (have checked and you have never posted with that call 
before) to 

a) Tell us the error message you get
b) Which version of wsjt-x had you used in the past.
c) How about what OS and version
d) What have you tried so far.

I personally have never used the Yaesu 3000 or 5000 - so no idea about that 
side.

I do know if you do give people the chance to see what the problem is you will 
have a better chance at getting a response that just assuming someone will have 
miraculously read your mind and posted the answer.

Tom
GM8MJV


On 2 Jul 2018, at 14:23, kb...@neo.rr.com wrote:

> I originally joined this group to get the exact parameters for my yaesu 3000. 
> first of all it isn't listed in the drop down menu, I tried using the 5000 
> instead and set everything I could find and it came back error so since I 
> can't seem to get this information and all the mails I see are not of 
> interest to me please drop me from the group. I have been wiring computers to 
> my radios since the mid 90's used almost every digital mode out there and 
> never had trouble accessing software before ft8 was fine til you added the 
> dxpedition mode then I could not get it to work. I've thoroughly read all the 
> instructions I'm not a dummy and still can't get CAT control to my 3000. I 
> will continue to use it as before through my rigblaster but I give up on 
> dxpedition mode. please remove me from future mailings. 
> 
>   de KB3MI  @ kb...@neo.rr.com
> 
> --
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
> 


--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Save Log in Callsign-specific Location

[Tom Melvin]

I know it’s after the event but in case you need to manipulate ADFI files in 
the future have a look at:

http://www.dxshell.com/adif-master.html

It allows you too sort, cut, split ADFI files - pretty cool

Tom
GM8MJV



On 27 Jun 2018, at 00:10, Joshua (Josh) Lotfi  wrote:

> C) Want me to add a GUI option deciding what to do
> 
> Thanks for your time. My webmail client split this message unfortunately.
> 
> On Tue, Jun 26, 2018 at 6:10 PM, Joshua (Josh) Lotfi
>  wrote:
>> Greetings all,
>> 
>> During the course of operating this past ARRL Field Day, a few other
>> hams and I became a little frustrated with the process of uploading
>> logs of FT-8 contacts, with wsjt_log.adi containing all logs for all
>> callsigns despite the fact that each station needs its own separate
>> log for contesting purposes. Our solution thus far has been our text
>> editor's search functions and "copy and paste". Not elegant.
>> 
>> So I cloned into the repo, made some changes, and now WSJT-X saves the
>> log as wsjt_log_[call].adi . So, for example, if W1AW, K1JT, and
>> KB2GSD all operated FT-8 from the same software install, then the
>> program's log directory would contain the following files:
>>wsjt_log_k1jt.adi
>>wsjt_log_kb2gsd.adi
>>wsjt_log_w1aw.adi
>> 
>> I know it's just a simple little change, but it's convenient, at least
>> for us. So I just wanted to know if you all:
>>A) Don't care.
>>B) Want me to push this tiny little adjustment to git
> 
> --
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
> 


--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Save Log in Callsign-specific Location

[Tom Melvin]

Can we add 

D) Leave well alone 

So apps and scripts that look for wsjt_log.adi  will still continue working no 
matter what GUI options are messed with.

Tom
GM8MJV

 




On 27 Jun 2018, at 00:10, Joshua (Josh) Lotfi  wrote:

> C) Want me to add a GUI option deciding what to do
> 
> Thanks for your time. My webmail client split this message unfortunately.
> 
> On Tue, Jun 26, 2018 at 6:10 PM, Joshua (Josh) Lotfi
>  wrote:
>> Greetings all,
>> 
>> During the course of operating this past ARRL Field Day, a few other
>> hams and I became a little frustrated with the process of uploading
>> logs of FT-8 contacts, with wsjt_log.adi containing all logs for all
>> callsigns despite the fact that each station needs its own separate
>> log for contesting purposes. Our solution thus far has been our text
>> editor's search functions and "copy and paste". Not elegant.
>> 
>> So I cloned into the repo, made some changes, and now WSJT-X saves the
>> log as wsjt_log_[call].adi . So, for example, if W1AW, K1JT, and
>> KB2GSD all operated FT-8 from the same software install, then the
>> program's log directory would contain the following files:
>>wsjt_log_k1jt.adi
>>wsjt_log_kb2gsd.adi
>>wsjt_log_w1aw.adi
>> 
>> I know it's just a simple little change, but it's convenient, at least
>> for us. So I just wanted to know if you all:
>>A) Don't care.
>>B) Want me to push this tiny little adjustment to git
> 
> --
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
> 


--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Call 1st Bug Fix

[Tom Melvin]

Thanks Mike

I will download the current source and have a play.

Basic programming stuff is OK - the QT display stuff is a whole new area for me.

Regards

Tom
GM8MJV



On 26 Jun 2018, at 15:07, Black Michael via wsjt-devel 
 wrote:

> Nope...no todo list
> 
> If you want to test a fix try modifying 
> void MainWindow::on_actionFT8_triggered()
> 
> And add this line after the displayWidgets call.
> ui->cbFirst->setChecked(m_settings->value("CallFirst",true).toBool());
> 
> This will restore the checkbox to your saved settings.
> 
> Mike
> 
> 
> 
> On Tuesday, June 26, 2018, 8:37:28 AM CDT, Tom Melvin  wrote:
> 
> 
> Hi All
> 
> Is there a ‘to do’ list that is visible outside the dev team?
> 
> The annoying bug where you loose ‘call 1st’ - would like to see where (if at 
> all)  is in the system.
> 
> OS. Windows 7
> WSJT Version - every version since about 1.8rc1
> 
> To simulate:
> 
> In FT8 mode make sure 'Call 1st’ is ticked.
> Change mode to JT65
> Change Mode back to FT8 - ‘Call 1st’ no longer selected.
> 
> Last time mentioned it was ‘Just setup a new configuration’ - yes that works  
> but sometimes forget and just select mode - it’s also quicker.
> Would be one less thing to worry about.
> 
> Thanks
> 
> Tom
> GM8MJV
> 
> 
> 
> 
> 
> --
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
> --
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! 
> http://sdm.link/slashdot___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Start time, not end time, logged

[Tom Melvin]

Hi

I much prefer the start time - if it takes me 30 mins to work a station I am 
‘on the air’ for 30 mins - a) I need to log this to stay legal and b) it allows 
me to see historically how long QSO;s take.

73’s

Tom
GM8MJV


On 31 May 2018, at 16:36, Steve London  wrote:

> Version 1.9.0
> 
> When making a difficult QSO, many minutes can pass between the time the QSO 
> was initiated and the QSO was completed. These are identified in the log 
> screen as "Start Time" and "End Time". Currently, when a QSO is logged, the 
> Start Time is placed in the ADIF file, and sent to clients such as N1MM+. 
> This is not standard for logging programs, and will lead to non-QSO time 
> mismatches in LoTW. The End Time should be written to the ADIF file and sent 
> to clients.
> 
> 73,
> Steve, N2IC
> 
> --
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
> 


--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Second Public Test of FT8 DXpedition Mode: April 7, 1400-1600 UTC

[Tom Melvin]

Afternoon

Took part in 1st test - after 30 odd mins Fox found me, would rather the 2 min 
timeout was a little longer (4 mins or so - at least long enough to double 
check docs or look at Ping thingy on another screen) - Fox moved me to below 
1000 as expected - back and forward, Red Watchdog timeout kicked in - restarted 
- then some W1xx   :-)   started calling below 1000 - then all went to pot - 
lost the Fox, another TX Watchdog timeout - had to give up.

On the 2nd test - could not hear the fox at all.

Lot of time spent making sure was TX’ing  :-(

de Tom
GM8MJV


On 5 Apr 2018, at 15:49, Joe Taylor  wrote:

> Hi all,
> 
> I write to remind you of the second public test of *FT8 DXpedition Mode* 
> scheduled for Saturday, April 7, 1400-1600 UTC.  You are cordially invited to 
> participate -- the more participants, the better!
> 
> Our main goal is to simulate pileups in which many "Hounds" call and attempt 
> to work a desirable rare DX station, the "Fox".  The test will help us to 
> improve our software so as to maximize the practical QSO rate in such 
> situations.  We hope you can be there and try to work both Foxes.
> 
> Here's the detailed schedule:
> 
> Date  UTC   FrequencyFox Callsign  Operator
> ---
> April 7  1400   14.105 MHzW1/KH7Z   N1DG
> April 7  1500   14.105W7/KH7Z   AA7A
> 
> All participating stations must use program version WSJT-X v1.9.0-rc3. If you 
> don't yet have it, download links are available near the bottom of the page 
> here:
> https://physics.princeton.edu/pulsar/k1jt/wsjtx.html
> 
> [If you are compiling the program for yourself, be sure to use code revision 
> r8576 or later, taken from the repository's WSJT-X development branch.  All 
> revisions since r8576 will perform identically in FT8 DXpedition Mode.]
> 
> Detailed instructions for both Fox and Hound are posted here:
> http://physics.princeton.edu/pulsar/k1jt/FT8_DXpedition_Mode.pdf
> Some details in these instructions have changed, so be sure to read and 
> follow the latest instructions carefully!  Don't just try to wing it.
> 
> As you will know after reading the instructions, Fox can conduct up to 5 QSOs 
> simultaneously, using frequency slots spaced by 60 Hz.  Fox transmissions 
> always occur in the frequency range 300-900 Hz above dial frequency.
> 
> If you (as a Hound) can legitimately use more than one callsign -- your 
> spouse's call, club call, etc. -- feel free to work each Fox multiple times.  
> No dupe QSOs with the same call, though.
> 
> Real-time liaison will be available on the "Ping Jockey Relief" chat page 
> (PJB), https://www.pingjockey.net/cgi-bin/pingtalkB .  Everyone should 
> monitor this page for possible last-minute announcements of a frequency 
> change, etc.  To ensure that announcements from Fox stations are easily 
> visible, Hounds should monitor PJB but not post messages there during the 
> test.
> 
> The deepest pileups will help us tune the final-release software version for 
> optimum performance on both Fox and Hound sides.  After the test, please post 
> any comments you feel will be helpful to one of our two email forums, 
> wsjtgr...@yahoogroups.com or wsjt-devel@lists.sourceforge.net .  You will 
> need to be subscribed to the list in order to post there.
> 
> We sincerely hope you can join us for this test, and that you will work both 
> Foxes!
> 
>   -- 73, Joe, K1JT (for the WSJT Development Group)
> 
> 
> --
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
> 


--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] DXpedition Mode on 40 Meters?

[Tom Melvin]

Not going to work.

Taking 40m as example -  What is the ‘FT8 allocation’ ? - all that could be 
coded would be the MGM allocation - nothing says FT8 needs to be 7.074 - UK 
band plan has digi modes 7.053 - 7.060  and the rest of the 7 Mhz allocation is 
‘All Modes’.  PSK31 starts from 7.040 - which is actually well away from 7.071 
that was in use last night.

Yes there are a few 'centre of activities’, may vary slightly by region - heck 
a job to code all those into Dx mode esp the number of bands and regions there 
are these days.

How many ‘proper’ DX piditions will there be? - if you have your favourite chat 
freq on SSB suddenly taken over by an expedition do you throw toys out of pram 
and blame those that introduced SSB - no you realises it will be a few days or 
a week or so and you live with it.

The general usage of the watering holes will quieten down over time - not 
addressing that just the Dx Mode - 100% of the time it will be the expedition 
itself that specifies the frequencies they plan to use - it is those people you 
need to address this issue to.  Remind them there are others ‘watering holes’ 
in the all mode section they should avoid. Perhaps there should be a ‘Centre of 
activity’ on each band for DX operations?

73’
Tom 
GM8MJV




On 27 Mar 2018, at 13:15, mwbese...@cox.net wrote:

> Hasan,
> 
> Thank you for that very eloquent post!  I think your suggestions are spot-on 
> and I'd LOVE to see all of them implemented.
> 
> 73,
> 
> Mike
> WM4B
> 
>  
> 
> 
> On Tue, Mar 27, 2018 at 7:46 AM, Hasan al-Basri wrote:
> 
>  I agree with every point that Mike (WM4B) made. DXpedition mode is becoming 
> a scourge on the bands w/r to other modes. 
> 
> 
> Another person asked for suggestion instead of complaints.
> 
> 
> OK, try this on:
> 
> 
> 1.Disable the mode until real precautions are taken to observe the current 
> watering holes for other modes.
> 
> 
> 2. Recode so that DXp mode can ONLY be run in the normal FT8 band 
> space...that way, when these rogue or even legitimate DXp projects come on, 
> they will trash the normal FT8 sections ...see how much you like it when your 
> favorite operating (and agreed upon) frequencies are trashed by a bunch of 
> hysterical dx'ers.
> 
> 
> Since DXp largely requires CAT mode, it should be straightforward (and only 
> responsible on the part of the authors) to code in a requirement to run DXp 
> mode in the current FT8 Allotment. 
> They did it for WSPR...
> 
> 
> This would be especially fitting since the FT8 authors created this 
> monster...the FT8 crowd should be made to live with it.
> 
> 
> ...and it's easy to dismiss things as "not much of  a crisis" when it's 
> someone else's nest that's being fowled.
> 
> 
> Maybe it's time for the FT8 nest to be fowled. and see how much that is 
> appreciated. 
> 
> 
> 
> Hasan
> 
> On Tue, Mar 27, 2018 at 6:22 AM, < mwbese...@cox.net> wrote:
> Gary,
> 
> As I said, I've recently heard some very good conversation here about the 
> need to avoid QRM to other modes; that's part of the reason it was so 
> disappointing to see 40 meters get trashed last night all the way down to 
> 7068 - or perhaps lower.
> 
> The reason I address the developers is twofold.  First, I (for one) certainly 
> saw the potential for this to happen when DXpedition mode was first 
> discussed.  This is the genie they let out of the bottle and I can't believe 
> they didn't' foresee the potential consequences.  Second, as developers, they 
> should take some responsibility for how their product is used - and you'd 
> certainly think they'd want it to be used in a manner that would show them 
> and their product in a positive light.
> 
> Recent discussion suggested moving towards the underutilized JT frequencies, 
> and I think that makes sense.  Aside from low utilization, FT8 and the JT 
> modes share a father, so I think it's only fair that they live together as 
> family.
> 
> Nobody is asking for a curtailing of anything except for poor operating 
> practice.  Many PSK QSOs were QRM'd to the point of making communications 
> impossible last night, and I don't believe for a minute that the PSK activity 
> was not visible to the FT8 users.  There is no excuse for anyone on any mode 
> to spoil the fun of others, and yet it's happening daily.  I agree that 
> direction and guidance is needed, but I'm not so sure I agree with the 
> ability to self-regulate; we all know that the rules go out the window when 
> DX shows up.  If the shoe were on the other foot and some other mode were 
> causing interference to your mode-of-choice, I have to think you'd be upset 
> too.  I don't know what sort of guidance or discussion about being good 
> neighbors is occurring on other email reflectors, but I hope there is active 
> discussion about the problem.
> 
> As I stated in another email, PSK is alive and well and I believe it is 
> underreported by PSKReporter, based on observations of my own activity.
> 
> With regard to a crisis, 

Re: [wsjt-devel] Macro Expansion

[Tom Melvin]

Hi Mike

Just throwing it out there - ‘FD’ while may be common on cw etc for some 
contests the CQ xx characters are generally taken as State / Providence / 
Region - while FD is not a US State - it could well apply to another country.  
Hardcoding it into one app does cause more confusion.  

The X? may work (Assuming no country) - but did I not see issues with a station 
XE  in recent fox/hound test - If some authority somewhere decides they will 
use XD as call there will be a mad rush to release patches assuming developers 
are around.

I would hate for some (no offence intended)  cock and bull method that  is not 
fully thought out - where would sota ref go, what about IOTA and all the other 
niche events. No doubt the one ‘’ macro that is not added/supported will be 
the one that causes most moans and complaints. 

Yes there should be a solution to that along with 6 character grids and a way 
of passing a ‘reference’ - SOTA ref/Contest Number/IOTA code - what it is I 
can’t help with but shoe horning a solution for xx% of users is not it.

Again no offence - just my personal view.

Regards

Tom
GM8MJV


On 7 Mar 2018, at 17:34, Black Michael via wsjt-devel 
 wrote:

> What other applications?  Is anybody interpreting the directed calls for any 
> purpose besides JTAlert giving it a "#" ??
> 
> To me it's a tradeoff between "confusion" where non-macro users would see the 
> 2-letter code and wonder what it's for and possibly ask questionsand the 
> ability to have "CQ FOX..." show up in Dxpedition mode and other such special 
> calls to let people know what's going on.
> 
> This has been asked numerous times for field day, SOTA, and such with no 
> other solution that I've seen.
> 
> 
> --- 
> Michael D. Black
> 
> 
> On Wednesday, March 7, 2018, 11:27:40 AM CST, Bill Somerville 
>  wrote:
> 
> 
> On 07/03/2018 17:19, Black Michael via wsjt-devel wrote:
> > Is there a downside to doing a macro expansion like this?
> >
> Hi Mike,
> 
> the obvious one is other applications not following suit. Changing the 
> interpretation of messages unilaterally is a recipe for confusion. At 
> least with the "E9aa" mapping to "CQ aa" the effect is relatively 
> transparent and if an application doesn't translate i.e. WSJT, then 
> users soon get the picture that E9EU means CQ EU and so on, whereas your 
> proposed mappings are rather more opaque.
> 
> 73
> Bill
> G4WJS.
> 
> 
> 
> --
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
> --
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! 
> http://sdm.link/slashdot___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

[wsjt-devel] 1.9 RC2 - UI Suggestion

[Tom Melvin]

Hi All

Just a little observation on the new 1.9 rc2  (Windows OS) - Very minor but if 
anyone in the area.

The ‘Hold Tx Freq’ seems to sit on it’s own - I have limited screen real estate 
so it sticks out.

If the ‘Hold Tx Freq’ was dropped in line with ‘Report Box’ it would allow the 
bottom box to be slightly reduced - just ‘looks’ a little odd at present.

Thanks

Tom
GM8MJV




--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Tx freq shifts in FT8 if QSY is decoded

[Tom Melvin]

Hi Neil

Seen that a few times on another facebook group - yes FT8 mode definitely can 
do this and a lot of people are using it for EU to Japan where they have a 
different TX allocation on top band (not sure if a left over in coding or not 
but a useful feature never the less)

Tom

On 10 Jan 2018, at 07:44, Neil Zampella  wrote:

> Hi all ...
> 
> On Facebook, there's a report that a FT8 decode of QSY 7.084 was causing 
> WSJT-X to change the Tx frequency.I understand that this is a feature 
> found in MSK144, but should it work under FT8?
> 
> The box for "Allow Frequency Change while Tx" was NOT checked, nor were the 
> VHF/UHF/etc features checked.  Not sure if the listserv allows attachments, 
> but here's a screen capture of the event.
> 
> 
> Neil, KN3ILZ
> 
> --
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! 
> http://sdm.link/slashdot___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

[wsjt-devel] Call 1st un-ticked on mode change

[Tom Melvin]

Good day

There is an issue with having call 1st ticked in FT8, then change mode to JT65, 
when return to FT8 then call is un-ticked.

I have been caught out a few times now, increased interest in other modes has 
meant I have been jumping around looking at other modes - when I return to FT8 
keep forgetting to re-tick the option.

Is there a possibility of this moving up the fix list?

All people have suggested is set a separate configuration for each mode - seems 
rather long winded when Mode > JT65 is so easy.

Regards

Tom
GM8MJV
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] special charcheters

[Tom Melvin]

There is a setting - General Tab - 'Show DXCC entity and if worked before'

You have this ticked - the system will add the DXCC entity name at the end of 
the line -

Regards

Tom
GM8MJV


On 3 Sep 2017, at 20:00, ke0bkm  wrote:

> i did not make my self clear
> 
> the Tilde (~) and the exclamation point (!) and the country are what i am 
> talking about. 
> where do i add these I have tried using the macros but i can not add the 
> special characters
> 
> 
> Sent from my iPhone
> 
>> On Sep 3, 2017, at 13:36, Wolfgang  wrote:
>> 
>> Hello David,
>> 
>> how about searching in the online manual and finding 'Logging' ?
>> 
>> !  Default color bright purple: New DXCC entity
>> ~  Light pink: You have already worked this DXCC entity but not this station
>> 
>> 73 de Wolfgang
>> OE1MWW
>> 
>> 
>> Sunday, September 3, 2017, 8:20:53 PM, you wrote:
>> 
>>> in the decode window i see something like
>> 
>>> CQ KE0BKM EM27 ~U.S.A.
>> 
>>> OR
>> 
>>> CQ KE0BKM EM27   !U.S.A.
>> 
>>> i have searched and searched on what it means and how to send it but to no 
>>> avail.
>> 
>>> David
>>> KE0BKM
>> 
>> 
>>> Sent from my iPhone
>> 
>>> --
>>> Check out the vibrant tech community on one of the world's most
>>> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>>> ___
>>> wsjt-devel mailing list
>>> wsjt-devel@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>> 
>> 
>> 
>> 
>> --
>> Amateur radio is the most expensive type of free-of-charge communication!
>> Amateurfunk ist die teuerste Art der kostenlosen Kommunikation!
>> 
>> 
>> --
>> Check out the vibrant tech community on one of the world's most
>> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>> ___
>> wsjt-devel mailing list
>> wsjt-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>> 
> 
> 
> --
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
> 


--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

[wsjt-devel] UI Bug? TX=RX locked

[Tom Melvin]

Afternoon

This may be a known issue but just in case … 

Spotted this jumping around on 6m the status of the TX=RX locked box not 
preserved.


OS: Windows 7
Pgm:   WSJTX RC2

How to reproduce:

Start up system, in my case defaults to 50.313 FT8, lock TX=RX TICKED - as 
expected
Select Mode - MSK144 - system changes to 50.280 as expected 
Select Mode back to FT8 - Lock TX=RX NOT ticked but waterfall behaviour says 
otherwise 

Tom
GM8MJV




--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

[wsjt-devel] Build instructions

[Tom Melvin]

Hi

Simple question - or can someone point me at related docs.

Downloaded the JTSDK  (For Windows), followed details on and managed to compile 
wsjtx without error.

I used the build-wsjtx ‘rinstall' command to build a release version - is there 
a command that will build wsjtx and all required ‘add ons’ libs etc to allow me 
to upgrade an existing install.

Thanks

Tom GM8MJV


--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel