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

2023-07-26 Thread Frode Igland via wsjt-devel
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

Re: [wsjt-devel] WSJTX Cabrillo log time

2023-05-13 Thread Frode Igland via wsjt-devel
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.

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

2023-02-17 Thread Frode Igland via wsjt-devel
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

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

2023-01-18 Thread Frode Igland via wsjt-devel
I have nothing against getting WD reporting in the UDP Status message, but I guess the most important part of the WD in Hound mode is that the "Enable Tx" button is deactivated, and that the operator must be able to maintain an attention span of two minutes to reactivate the "Enable Tx" button.

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

2023-01-18 Thread Frode Igland via wsjt-devel
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

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

2022-10-21 Thread Frode Igland via wsjt-devel
rmanently 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

2022-10-21 Thread Frode Igland via wsjt-devel
r. 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 thousan

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

2022-10-19 Thread Frode Igland via wsjt-devel
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

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

2022-10-13 Thread Frode Igland via wsjt-devel
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 me less than an hour

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

2022-10-13 Thread Frode Igland via wsjt-devel
ion 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 application. Run

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

2022-10-13 Thread Frode Igland via wsjt-devel
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