[wsjt-devel] rc7 ADIF log file

Hi all, I see that whereas rc5 logged an FT4 QSO as "FT4", rc7 is logging it as "MFSK FT4". I assume this is intentional and ADIFically correct, but it has confused CQRlog 2.3.0 which is logging the QSO as MFSK. (Yes, I have added FT4 in CQRlog preferences.) I have reported this to the CQRlog

Re: [wsjt-devel] Bug report

Ubuntu MATE 18.04 LTS amd64 rc6 segfaults at startup. It's OK if I start from shell using --test-mode 73, Richard G4DYA ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] FT4 mock contest

On 09/05/2019 02:07, Edfel Rivera wrote:On 09/05/2019 02:07, Edfel Rivera wrote: > Hi Richard: > > Keep present clock diff have to be < .5. FT4 is more strict regarding time. > > 73' > > Edfel Hi Edfel. Thanks, but that was not the issue - my time is maintained to within a millisecond. 73,

Re: [wsjt-devel] FT4 mock contest

On 06/05/2019 15:45, Joe Taylor wrote: > One-hour "practice contest" sessions will be held this week and next > week using the FT4 mode and the ARRL RTTY Roundup rules. > > Thursday, May 9, -0100 UTC (Wednesday evening, May 8, NA time) Using Ubuntu MATE 18.04. Well I tried but didn't get

Re: [wsjt-devel] Specification for side band attenuation

On 07/12/2018 02:46, Simon wrote: > What is the guideline or specification for audio frequency signal > attenuation outside of the 50Hz (plus and minus 25 Hz from centre) band > width?   > > For example, signal should be x dB below carrier, at frequency plus > and minus 50 Hz from centre? In

[wsjt-devel] rc3: Call 1st doesn't work with directional CQ

Hi all, Ubuntu 18.04 amd64 WSJTX V2.0.0-rc3 8a1244 Working Japan FT8 160m split 1840 kHz Tx / 1908 kHz Rx. (Split operation set to 'none' in Settings/Radio for this configuration.) While calling with a directional CQ (CQ JA G4DYA IO82) entered into the Free msg box on Tab 2, Auto seq / Call 1st

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

On 05/04/18 15:49, Joe Taylor wrote: > I write to remind you of the second public test of *FT8 DXpedition Mode* > scheduled for Saturday, April 7, 1400-1600 UTC. WSJT-X 1.9.0-rc3 r8576 Ubuntu 16.04 LTS The watchdog timer in the bottom right-hand corner of the main window seems to be wrong. It's

Re: [wsjt-devel] WSJT-X v1.9.0-rc3: Testing of FT8 DXpedition Mode

On 30/03/18 08:50, Tsutsumi Takehiko wrote: > I with to hear comment about my suggestion to explore new harmonized spectrum > of narrow band digital on 160m at 1800-1810KHz, where IARU Region II table > has already allocated to narrow band digital. I believe this spectrum was > used for

Re: [wsjt-devel] FT8 DXpedition Mode

On 02/02/18 17:53, Joe Taylor wrote: > You have probably heard something about recent efforts to develop a > special "FT8 DXpedition Mode" in WSJT-X.  This message aims to bring you > up-to-date on our progress, and generally to make our plans more widely > known. Hi Joe. Thanks for this. For

Re: [wsjt-devel] Feature Request of FT8 TX Frequency limitation less than 2kHz

On 21/11/17 19:14, Black Michael via wsjt-devel wrote: > Don't you have any room at 2000-2500?  Or is it really so crowded there's no > space anywhere? Talking specifically about 80m ... It's usually possibly to find a slot, although 2000-2500 is often spoiled by audio harmonics from stations

Re: [wsjt-devel] Feature Request of FT8 TX Frequency limitation less than 2kHz

On 21/11/17 16:05, Libor Holouš wrote: > According this theme I'd like to ask about expanding the band possibility. > FT8 seems to be very popular these days and there are some DXpeditions > operating there, so 2 kHz is not enough space for all that traffic. The > extreme is 40 and 20m, but

Re: [wsjt-devel] r8270 compile error

On 02/11/17 11:13, Gary Rogers wrote: > I tried to build a couple of nights ago and got the message that 1.7.1 was > not ready for on air use after I built it. After clicking the ok I got a > fatal error message. Is this related? No. See Joe Taylor's post to this list of Oct 29, headed "Don't

Re: [wsjt-devel] Experimental changes in r8146

On 02/10/17 01:15, Joe Taylor wrote: > Hi David, > >> The real issue is the TX Enable.  I’d like to avoid having it set on >> the double click so I can pick the right time in the other QSO to send >> my message, on a split frequency. > > Why not simply uncheck the box "Double-click on call sets

Re: [wsjt-devel] Experimental changes in r8125

On 29/09/17 20:10, Bill Somerville wrote: > I am failing to see why most of the existing automatic behaviour when > double-clicking decodes has to be given up just for a number of > operators who think that by default one's Tx offset should not be moved > when replying to a CQ or QRZ call. To be

Re: [wsjt-devel] r8084: ADIF parser

On 16/09/17 14:18, Bill Somerville wrote: > yuck! I will sort it out. Great. Thanks. I noticed another minor bug while looking at adif.cpp, which is unlikely to be encountered in practice. The 60m amateur allocation in Somalia covers the whole of the Fixed Service band 5.06-5.45 MHz. So: -

[wsjt-devel] r8084: ADIF parser

r8084 Ubuntu MATE 16.04 Hi, Before starting wsjt-x, it's my habit to create a custom wsjtx_log.adi with just logging information for the band I'm about to use. This is produced by a script I wrote months ago. r8084 doesn't like the resultant ADIF, unless I stick at the beginning of it. (In the

Re: [wsjt-devel] Space between Message and DXCC too big

On 16/09/17 11:02, Bill Somerville wrote: [snip] Hi Bill and thank you, as always, for the detailed explanation. The extra space isn't a problem for me, BTW. I was just curious. 73, Richard G4DYA -- Check out the

Re: [wsjt-devel] Space between Message and DXCC too big

On 15/09/17 21:56, Bill Somerville wrote: > On 15/09/2017 21:08, DG2YCB, Uwe wrote>> Why is there now such a big space > between the Message text and the >> DXCC entity? It was better in the old version 1.7.0. > > before WSJT-X v1.8.0 RC2 the space was truncated but that can no longer > be done

Re: [wsjt-devel] WSPR-X in Fedora

On 03/09/17 10:54, Jaroslav Skarvada wrote: > two more problems which have been spotted during the WSJT-X package > Fedora review [1] and I think it's worth to report upstream: > > - jt9 binary has executable stack That reminds me. When running (r8067 under Ubuntu MATE 16.04) there seems to be a

[wsjt-devel] r8028 - links to User Guide don't work

Hi all, Ubuntu 16.04 1.8.0-rc2 r8028 Help->Online User Guide results in: The requested URL /pulsar/K1JT/wsjtx-doc/wsjtx-main-1.8.0-rc2.html was not found on this server. Help->Local User Guide doesn't bring up anything. 73, Richard G4DYA

Re: [wsjt-devel] Tx timing and protocol spec

On 10/08/17 13:21, Bill Somerville wrote: > On 10/08/2017 00:22, Richard Lamont wrote: >> In a perfect station, exactly how soon after the beginning of the >> 15-second (or whatever) window should the Tx start to radiate RF? Is a >> nominal amount of delay baked into the proto

[wsjt-devel] 1.8.0-rc1 User manual: FT8 protocol description

Hi all, Looking at Section 16.2.1 of the rc1 User Manual, it says in the first sentence that there are 75 information bits and 174 channel symbols. (Later in the paragraph it says there are 79 channel symbols.) AIUI, this should be 75 payload bits, 174 information-carrying bits and 79 channel

[wsjt-devel] Tx timing and protocol spec

In a perfect station, exactly how soon after the beginning of the 15-second (or whatever) window should the Tx start to radiate RF? Is a nominal amount of delay baked into the protocol(s) to allow for T/R switching, the default 0.2s before audio etc? 73, Richard G4DYA

[wsjt-devel] r8012 another FT8 quirk

1.8.0-rc2 r8012 Ubuntu 16.04 LTS After I finished a QSO, another station called me and used a non-standard message in place of the standard 73. This completely messed Auto Seq up. As well as replacing DxCall with RICHAR for my 73, it did the same when attempting to log the QSO. Rx Frequency

[wsjt-devel] r8012 FT8 quirk

1.8.0-rc2 r8012 Ubuntu 16.04 LTS After calling CQ and working a station in a straightforward QSO, my QSO partner repeated his 73, by which time I'd re-enabled TX for the next CQ. His second 73 appeared in the Band Activity Window but not the Rx Frequency window. Extracts from the two windows

Re: [wsjt-devel] User Guide updates for WSJT-X Version 1.8

On 02/08/17 20:42, Joe Taylor wrote: > Hi all, > > In preparation for a soon-to-come second candidate release of WSJT-X > Version 1.8, I committed a large number of updates to the WSJT-X User > Guide today. > 2. If you find something confusing, missing, or otherwise in need of > improvement,

Re: [wsjt-devel] r7969: AP: calls out of the blue

On 29/07/17 17:16, Steven Franke wrote: >> So - trying to find an explanation that fits all the known facts - and >> if I've understood correctly - VE3SMB probably called someone but >> probably not me. > > I would say “maybe” VE3SMB called someone, not “probably”. Perhaps Bill and I > differ a

Re: [wsjt-devel] r7969: AP: calls out of the blue

Hi Steve, On 29/07/17 15:32, Steven Franke wrote: > (i) The attached screenshot of the waterfall shows that the false decode at > 1055 Hz was produced based on a signal that existed for less than half of the > interval. > > Thus, at least half of the symbols were missing. Nevertheless, the

Re: [wsjt-devel] r7969: AP: calls out of the blue

On 29/07/17 09:40, Gordon Higgins wrote: > could he not have seen u spotting on psk reporter @ called on chance > richard iff i see dx station spotting i will call on chance often with > sussex Hi Gordon and thanks for the explanation. I do feed psk reporter. It had never occurred to me that

Re: [wsjt-devel] WSJT-X: review of message reply and sequencing logic

On 25/07/17 22:50, Steven Franke wrote: > FWIW, you may find that r7946 is somewhat faster than r7944, on all settings. > I have made a change that will reduce the number of non-viable candidates > that are sent to the decoders. Thanks Steve. Thanks also to Joe for the tip on timer.out. I've

Re: [wsjt-devel] Pwr slider - tooltip level indication wrong

On 19/07/17 20:28, Richard Lamont wrote: > I noticed that with the Pwr slider at maximum, the level of the tone on > 'Tune' was exactly 0 dBFS, as expected. However, when turning the level > down, the measured level went down 3 dB for every 1 dB indicated on the > tooltip shown

[wsjt-devel] Pwr slider - tooltip level indication wrong

v1.8.0-rc2-r7924 Ubuntu 16.04 amd64 I connected the Tx audio output from WSJT-X via Jack to a couple of audio test utilities - the jaaa spectrum analyser and the jnoisemeter RMS level meter. I noticed that with the Pwr slider at maximum, the level of the tone on 'Tune' was exactly 0 dBFS, as

Re: [wsjt-devel] Ver 1.8 RC1 audio in slider problem

On 18/07/17 23:52, Bill Somerville wrote: > if you are going to do a patch then remove the slider altogether +1 for removal from the main window. I'm not bothered whether something gets added to the waterfall window, as long as it doesn't duplicate what the existing four sliders do. 73, Richard

Re: [wsjt-devel] IARU Region selection in Settings > General is not 'sticking'

On 12/07/17 17:04, Bill Somerville wrote: > this has been reported by several users who are building from sources on > multiple platforms. I have not yet discovered what the reason is and I > cannot reproduce it myself. Yours is the first report, albeit third > party, that the official release

Re: [wsjt-devel] Disable TX if called stn answers other

On 12/07/17 19:19, Gary McDuffie wrote: > >> On Jul 12, 2017, at 8:08 AM, Rich - K1HTV wrote: >> >> For that reason, having the WSJT-X software halt your calling the station >> that answered someone else, I believe that the suggested feature be >> incorporated into future

Re: [wsjt-devel] FT8 and "Call 1st"

On 11/07/17 16:42, Joe Taylor wrote: > We are interested in feedback from users on the question of partial QSO > automation. Should "Call 1st" be changed or removed? I think "Call 1st" is necessary, because there isn't nearly enough time for an operator to decide manually. As long as TX Enable

Re: [wsjt-devel] wsjt-x v1.8.0-rc1 on raspbian = success.

On 11/07/17 14:18, Bill Somerville wrote: > On 11/07/2017 14:13, Richard Lamont wrote: >> On 11/07/17 13:44, Bill Somerville wrote: >> >>> I would appreciate reports of how well the Debian installer we have >>> provided with the WSJT-X v1.8.0 RC1 release works. As

Re: [wsjt-devel] wsjt-x v1.8.0-rc1 on raspbian = success.

On 11/07/17 13:44, Bill Somerville wrote: > I would appreciate reports of how well the Debian installer we have > provided with the WSJT-X v1.8.0 RC1 release works. As with the other > early release kits you will have to install dependencies manually and > use rpm/yum/dnf to install them. In your

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

On 11/07/17 01:57, George J Molnar wrote: > I can confirm Gary’s report on 7844 for MacOS. > > George J Molnar, KF2T > Nevada, USA I can confirm it on 7844, 7848 and rc1 for Ubuntu 16.04. 73, Richard G4DYA --

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

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

[wsjt-devel] r7841 - minor detail

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

[wsjt-devel] FT8: multiple responses to CQ

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

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

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

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

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

[wsjt-devel] r7829 Call 1st / weak

r7829 Ubuntu 16.04 I've been trying out the new UI feature for auto-responding to a CQ, for which many thanks Joe. The Call 1st option works like a champ. It enables a station to work a 'run' without any duplicated transmissions even if you're a bit slow on the uptake. I couldn't persuade

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

On 09/07/17 18:04, Bill Somerville wrote: > On 09/07/2017 17:40, Peter Pauly wrote: >> It takes a full 2 seconds before I hear audio come out of the radio >> during transmit. Is there any way to cut this down to something smaller? >> >> I'm using a Elecraft K3S over USB. >> WSJT-X is 1.7.1-devel

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

On 09/07/17 17:40, Peter Pauly wrote: > It takes a full 2 seconds before I hear audio come out of the radio during > transmit. Is there any way to cut this down to something smaller? > > I'm using a Elecraft K3S over USB. > WSJT-X is 1.7.1-devel r7818 > > The following settings are in effect: >

Re: [wsjt-devel] Double Display in Rx window

On 08/07/17 01:52, Neil Zampella wrote: > Seeing double entries for the replying station in the RX window, > r7812.See attached pic. Yes, I'm seeing it too. 73, Richard G4DYA -- Check out the vibrant tech community

[wsjt-devel] FT8 audio spacing - waterfall graticule

FT8 doesn't have a two-pass decoder. Even it it did, a signal that doesn't have another one overlapping it stands a better chance of being decoded. A regular spacing of (say) 60 Hz would help to keep things apart. I'm not suggesting that this should be forced on users by WSJT-X, but there is a

Re: [wsjt-devel] Frequency calibration - use of AM broadcasts

On 06/07/17 20:58, Joe Taylor wrote: > Richard -- > > On 7/6/2017 3:48 PM, Richard Lamont wrote: >> Is it a good idea to use AM broadcast transmitters as a frequency >> standard when the regulatory tolerance (ITU and many countries) for such >> transmitters is +/-

Re: [wsjt-devel] Frequency calibration - use of AM broadcasts

On 06/07/17 20:56, Bill Somerville wrote: > On 06/07/2017 20:48, Richard Lamont wrote: >> Is it a good idea to use AM broadcast transmitters as a frequency >> standard when the regulatory tolerance (ITU and many countries) for such >> transmitters is ± 10 Hz? Is that good e

[wsjt-devel] Frequency calibration - use of AM broadcasts

Is it a good idea to use AM broadcast transmitters as a frequency standard when the regulatory tolerance (ITU and many countries) for such transmitters is +/- 10 Hz? Is that good enough for the purpose? 73, Richard G4DYA

Re: [wsjt-devel] FT8: CW ID not a good idea

On 05/07/17 22:46, David Tiller wrote: > If you knew you had to send an ID with a packet, could you not reduce the > amplitude of the whole data packet by a db or so and re-allocate that power > to the CW ID? It certainly doesn't have to be loud, much like repeaters do > id-under-voice. That

Re: [wsjt-devel] FT8: CW ID not a good idea

On 05/07/17 22:10, David Tiller wrote: > Any chance of having the CW id run concurrently with a data packet, perhaps > at fDial + 100 Hz or so? It'd meet the id requirement without interfering > with QSOs. Doing it concurrently wouldn't be compatible with FT8 being a 'constant envelope' mode.

Re: [wsjt-devel] FT8 Feature Request

--- > 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.

Re: [wsjt-devel] r7777 - second 73 doesn't appear in RX window

On 03/07/17 16:20, Richard Lamont wrote: > r > Ubuntu 16.04 amd64 > > If I reply to a CQ and complete a QSO, the other station sends RRR, then > I send 73, and it appears that now the other station responds with a 73 > of his own in the standard auto-sequence (Ta

[wsjt-devel] r7777 - second 73 doesn't appear in RX window

r Ubuntu 16.04 amd64 If I reply to a CQ and complete a QSO, the other station sends RRR, then I send 73, and it appears that now the other station responds with a 73 of his own in the standard auto-sequence (Tab 2) before his TX is disabled. However, this new seventh exchange only appears in

Re: [wsjt-devel] Build 7754 notes

On 30/06/17 23:20, Richard Lamont wrote: > FT8 spots received by me don't seem to be appearing on PSK reporter. As others have noted, this is fixed in r7755. 73, Richard G4DYA -- Check out the vibrant tech commun