Re: [wsjt-devel] FST4 Quick Start reference 2?

The reference says "in preparation", so it is probably not prepared yet. It will come when prepared. Frode, LA6VQ Virusfri.www.avast.com

Re: [wsjt-devel] Release Candidate WSJT-X 2.7.0-rc5

Thanks a lot, Joe. Looking forward to try it. The User Guide translation is in progress. 73, Frode LA6VQ man. 1. juli 2024, 21:11 skrev Joe Taylor : > Hi Frode, > > On 7/1/2024 2:25 PM, Frode Igland LA6VQ wrote: > > Thanks for the new and exciting version. > > How

Re: [wsjt-devel] Release Candidate WSJT-X 2.7.0-rc5

Thanks a lot, Joe. Looking forward to try it. The User Guide translation is in progress, 73, Frode LA6VQ man. 1. juli 2024, 22:19 skrev Charles Suckling via wsjt-devel < wsjt-devel@lists.sourceforge.net>: > Hi Lloyd > > Here's a quick start guide for setting up SDRC to support QMAP. > > > https:/

Re: [wsjt-devel] Release Candidate WSJT-X 2.7.0-rc5

Thanks for the new and exciting version. How do we get to practice SuperHound operation? Will there practice sessions with a designated SuperFox, or will we have wait for N5J to be able to test for bugs and improvement proposals? 73, Frode LA6VQ man. 1. juli 2024, 20:19 skrev Joe Taylor via wsjt-d

[wsjt-devel] WSJT-X 2.7.0-rc2imp: TIME_ON = TIME_OFF when I am the called station #adif #IssueReport

Using WSJT-X 2.7.0-rc2imp I experience this as a new "feature": When a counterpart responds to my CQ, or he/she tailends a QSO I am finishing, both start time and end time are logged with TIME_OFF only, i.e a duration of 0 seconds. However, when I respond to stations calling CQ, or I tail-end a Q

Re: [wsjt-devel] WSJTX Cabrillo log time

Regarding logged time in cabrillo. Let's reason backwards: 1. Cabrillo is a file format used for submitting contest logs only. 2. Cabrillo is a file format normally created from an ADIF file that is created by specialized logging software, say N1MM Logger+, WinTest or some other contest software. 3

Re: [wsjt-devel] 3Y0J F/H operation - highlight Fox messages

Forgive me for asking, but why would you need to highlight Fox messages in addition to the easily observable characteristics of Fox/Hound mode? As this is the WSJT-X dev forum, I assume that you are talking about the WSJT-X software and "real" Fox/Hound, not any multi-stream operation. When you are

Re: [wsjt-devel] UDP Status message defect. WD status not set when in Hound mode.

able Tx" button. That should be doable without UDP messaging. Frode ons. 18. jan. 2023 kl. 17:18 skrev Laurie, VK3AMA via wsjt-devel < wsjt-devel@lists.sourceforge.net>: > > > On 19/01/2023 1:45 am, Frode Igland wrote: > > this tells that the WD timer in Hound mode is de

Re: [wsjt-devel] UDP Status message defect. WD status not set when in Hound mode.

The User Manual for FT8 DX-pedition mode, "Detailed Instruction for Hounds" # 11 at the top of page 5, says: > You will need to re-activate Enable Tx (or hit > Enter on the keyboard) at least once every two minutes. (This restriction > is to > ensure that an operator is present and paying attentio

Re: [wsjt-devel] Missing input sanitation for TX_PWR field in ADIF log

To permanently fix this issue and prevent further > similar problems in combination with other software I would therefore > welcome it if the WSJT-X software could be adapted such that the generated > ADIF file always complies with the specifications. > > Regards > Roman HB9HDN &g

Re: [wsjt-devel] Missing input sanitation for TX_PWR field in ADIF log

Q tor. 20. okt. 2022 kl. 00:25 skrev Laurie, VK3AMA via wsjt-devel < wsjt-devel@lists.sourceforge.net>: > > > On 20/10/2022 12:05 am, Frode Igland via wsjt-devel wrote: > > I have used the "Tx power" field in the WSJT-X logging window for most > > of my tens of th

Re: [wsjt-devel] Missing input sanitation for TX_PWR field in ADIF log

Hi, Roman. My experience is that the ADIF format accepts more than the ADIF specifications may indicate. I have used the "Tx power" field in the WSJT-X logging window for most of my tens of thousands of WSJT-X QSOs. Whether I enter "40 W", "40W" or "40", it hits my HRD Logbook as "40", i.e. a clean

Re: [wsjt-devel] WSJT-X 2.6.0-rc4: Sudden shut-down, "CQ: Max Dist" doesn't work, "CQ: None" stops working

WSJT will > > select the DL station to call. > > > > Dennis W1UE > > > > > > On Thu, Oct 13, 2022 at 8:21 AM jan0--- via wsjt-devel < > > wsjt-devel@lists.sourceforge.net> wrote: > > > > > I can confirm problem 1, as it happened to

Re: [wsjt-devel] WSJT-X 2.6.0-rc4: Sudden shut-down, "CQ: Max Dist" doesn't work, "CQ: None" stops working

ect the DL station to call. > > Dennis W1UE > > > On Thu, Oct 13, 2022 at 8:21 AM jan0--- via wsjt-devel < > wsjt-devel@lists.sourceforge.net> wrote: > >> I can confirm problem 1, as it happened to me less than an hour ago, >> including the orphaned JT9 decoding ap

[wsjt-devel] WSJT-X 2.6.0-rc4: Sudden shut-down, "CQ: Max Dist" doesn't work, "CQ: None" stops working

I have used -rc4 since it was released and have found it quite stable with three notable exceptions: *1. Sudden closing in FT8 after extended periods of operation* After an extended period of use in FT8 mode (normally more than two hours), WSJT-X may close down abruptly. The closing happens at the

[wsjt-devel] WSJT-X 2.4.0 User Guide: Where to send translations? Proposals for corrections/updates.

Thanks to the WSJT-X Development Team for WSJT-X 2.4.0. *Where to send translations?* I have downloaded and tried WSJT-X 2.4.0 as well as the User Guide. I have also reviewed the WSJT-X 2.4.0 User Guide for translation and have completed the Norwegian translation. Having submitted a number of tra

Re: [wsjt-devel] WSJT-x Icom CI-V Issue?

John, As the change of mode happens on tune or transmit, have you checked for RFI? I am not familiar with the IC-7300 settings, but in a couple of IC-7600 I have seen RFI change the of mode (e.g. from USB-D1 or USB to LSB) when transmitting. Change of TX filter width has also happened simultaneous

Re: [wsjt-devel] WSJTX-X 2.4.0 rcX split

Joe, Whilst reviewing the User Guide, would you take a look at two issues: 1. The former section 10.2 Button Row has now been reduced to: === Button Row // Status=edited Is this a deliberate change? 2. Section 17.2.10, Table 7 The Bandwidth for FST4-15 is given as 67.7 Hz. Should that be 66.

Re: [wsjt-devel] r2.2.2 Minor Issue with "short" calls that use DX

Steve, My apologies that I hadn't noticed that Reino had already explained the invalid call sign. I should have read all the messages this morning before I responded to your e-mail. I guess that we may wish that the WSJT-X algorithm for identifying the DXCC entity should have had a checkpoint that

Re: [wsjt-devel] r2.2.2 Minor Issue with "short" calls that use DX

qrz.com/db/n7c ) is a VERY valid and sought after call. I was > able to make contact with that station but not this one ! > > > > 73 > > > > Steve I > > VK3VM / Vk3SIR > > > > > > *From:* Frode Igland > *Sent:* Tuesday, 18 August 2020 9:08 PM > *To:*

Re: [wsjt-devel] r2.2.2 Minor Issue with "short" calls that use DX

Steve, I guess that your statement "WSJT-X will not pick up this call" means that WSJT-X will not *automatically *enter this call into the "DX Call" field, nor the locator into the "DX Grid" field. That is true, but WSJT-X will certainly pick up the call and grid as decoded if you enter it manually

Re: [wsjt-devel] strange response

In the Log QSO window the call sign is changed from W5KDJ to 1W. Did that happen automatically as that was the "call sign" in the RR73 message that initiated the logging procedure, or is that entered manually by K0VM? 73 Frode LA6VQ man. 13. jul. 2020 kl. 17:56 skrev Bill Somerville : > On 13/0

Re: [wsjt-devel] Bug Report: Four Letter Suffix in WSPR

Onno, There is nothing wrong with your call sign of four characters in the suffix. It is just too long to fit within the restrictions of WSJT-X if you want to use WSJT-X in the standard way. Mind you, you can still use WSJT-X, just not in the standard way. WSJT-X was never created to work smoothl

Re: [wsjt-devel] FT8 F/H mode - am I out of step ?

It seems just right. According to the "RX Frequency" window you did not transmit 091645 and 091715 (no yellow line). That is the times when you see in the "Band Activity" window what was going on from all the other chasers you were able to decode. They did the same on all other 15 and 45, but you d

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

As I read Rich's message in digest format, a response may already be given, so my apologies if I repeat a previous reply. It seems like the check box under Settings - General - "Disable Tx after sending 73" repeatedly creates some confusion. The mouse-over help text describes exactly what checking

Re: [wsjt-devel] FT8 F/H. NO CQ. CANNOT CALL

The spotter may not have decoded 3DA0AO in a CQ, but in a QSO. Being quite rare, I guess 3DA0AO was quite busy, with callers front, back, left and right, not requiring CQs to conduct QSOs. Nevertheless, it is of course best practice to make a CQ call every now and then. Another issue may be that 3

Re: [wsjt-devel] Special callsign

Hi Svend Aage, Adding the IOTA Reference to the CQ will be understood by WSJT-X as a free text message, and will be limited to 13 character. I tried to figure out the same some weeks ago, for my holiday in EU-055, but found no working solution that would allow me to add the IOTA Reference to any of

Re: [wsjt-devel] WSJT-X 2.0.1: Bug-fix Release

... and as soon as I sent the e-mail, the v2.0.1 User Guide was up and ruinning. Thanks. Frode Den man. 25. feb. 2019 kl. 18:20 skrev Frode Igland : > Thanks to Joe and the team for v2.0.1. > > The link to the v2.0.1 User Guide is not working yet. Updated translations > will be

Re: [wsjt-devel] WSJT-X 2.0.1: Bug-fix Release

Thanks to Joe and the team for v2.0.1. The link to the v2.0.1 User Guide is not working yet. Updated translations will be forthcoming swiftly on receipt of the updated User guide. 73 Frode LA6VQ Den man. 25. feb. 2019 kl. 16:17 skrev Joe Taylor : > The WSJT Development Group is pleased to annou