Re: [wsjt-devel] wsjtx-2.7.0-rc3

2024-01-24 Thread Black Michael via wsjt-devel
You must have old source code in your system somewhere and it's picking up and old yaesu.h file. That is defined in ft9000.c Hamlib/rigs/yaesu# grep ft9000Old_caps *.c *.hft9000.c:struct rig_caps ft9000Old_caps =yaesu.c:    rig_register(_caps);yaesu.h:extern struct rig_caps ft9000Old_caps;

[wsjt-devel] wsjtx-2.7.0-rc3

2024-01-24 Thread Greg Cook via wsjt-devel
Different cmake error but still problems on Pi3. No problems with 2.6.1 Greg g4cui Making all in tests libtool: link: gcc -Wall -g -O2 -fPIC -fdata-sections -ffunction-sections -Wl,--gc-sections -o rigctl rigctl-rigctl.o rigctl-rigctl_parse.o rigctl-dumpcaps.o rigctl-dumpstate.o

[wsjt-devel] EME Doppler Control without Monitoring Enabled + Q65-20M

2024-01-24 Thread Dwayne Sinclair via wsjt-devel
Our recent discussion on UHF/SHF (23cm) EME Q65 confirmed today the fastest mode available is Q65-30B. WSJT-X does an outstanding job of doppler control and can be used to control doppler for CW QSO’s via configuring Preferences/Radio/Mode to None so that the mode of the transceiver (in CW

Re: [wsjt-devel] Making F/H idiot proof

2024-01-24 Thread Jeff Stillinger via wsjt-devel
Having read and seen much of the same.   I agree that F/H needs some work.    Andy is spot on about the user base not reading and following instructions.   Therefore, we do need forced compliance with the message format.   Of course there will be a lot of whining about it, but the Clipperton

Re: [wsjt-devel] Making F/H idiot proof

2024-01-24 Thread Reino Talarmo via wsjt-devel
Hi, I think that the Fox simply ignores the “R+rpt” part of the message and takes it to be a Tx1 message. So Fox sends a report. The Hound station autoseq may not work correctly as it has not sent the Tx1 at all. A resending of the “R+rpt” should be a correct message. The Hound station sends

Re: [wsjt-devel] Making F/H idiot proof

2024-01-24 Thread Andy Durbin via wsjt-devel
Hi Brian, The screen shot and the discussion are in the Clipperton groups.io messages. Clipperton is certainly using WSJT-X and operating as Fox. It appears the "user" saw a TX5S CQ and replied with TX3. TX5S responded with TX2. ref - https://groups.io/g/Clipperton-2024/message/388 You may

Re: [wsjt-devel] Making F/H idiot proof

2024-01-24 Thread Brian Moran via wsjt-devel
Hi Andy; can you please help me understand the circumstances better? Under “normal” f/h operation, the hound calls with a grid. WSJT-X in fox mode can queue a caller with a grid. WSJT-X in fox mode doesn’t queue non-grid-supplying callers. If the “fox” replied to a signal report message as

[wsjt-devel] Making F/H idiot proof

2024-01-24 Thread Andy Durbin via wsjt-devel
As implemented in WSJT-X ver 2.6.1 the hound is able to select TX3 as their first transmission. One user has posted a screen shot showing that fox replied with a signal report but the QSO could not be completed. Since new WSJT-X ops seem reluctant to read the instructions would the developers