ownloc.txt  (Example for DE location)

Version History:

Version 1.6.1 released on 06.11.2019
Bug in 1.6.0 fixed (see below)

Version 1.6.0 released on 19.10.2019
Known error: It crashes when starting the program, if  the callsign.txt only contains the callsign.
It works with the additonal line e.g. LOGGING=OFF

New features in 1.6.0:

Changing between FT8 and FT4 changes the Mode in WSJT-X
(to avoid mode mismatch)

Band-Usage was changed to "Free-Channels"
The Band-Usage did not considered the fragmentation of the band. Now, the number of free channels shows how many continuous 50/75Hz segments are available. If no channel could be found, the FT8-Helper waits for a free slot.

Automatic RUN <-->  S/P switching
dd a new line to callsign.txt to overwrite the default limits of20:
MAX-S/P=10     ;will initiate switchover after 10 unsuccessful QSO attempts.
MAX-RUN=10   ;will initiate switchover after 10 unsuccessful attempts.
"'#" at the beginning of the line invalidates the line

Automatic stop of RUN in case of band inactivity
If no stations are received at the end of the "sleep" phase, the RUN-Modes is switched off automatially. If the Auto-RUN/SP feature is used, it switches to S/P and remains in S/P as long no messages received. If the band is alive again, the normal S/P-RUN switchover procedure is continued.

Limit the audio bandwidth:
t can help if older TCVRs are used without sufficient slope-control
dd a new line to callsign.txt to overwrite the default value (2800 Hz) :
MAX-AF=2100   ; will limit the bandwidth to 500-2100 Hz (lowest possible value is 1500)
For all commands in the callsign.txt: "'#" at the beginning of the line invalidates the line.

Additionally to the log written to the main screen, the log can be written into the file ../logs/log-YYYYMMDD.txt. For each day a new file is opened. To do it, add following line into the callsign.txt:

If you want log additionally the messages from the RX-Frequency window of WSJT-X, add the following line:
LOGGING=MSG     ; the LOGGING=ON is not required

For investigating incorrect behaviour, enter the following line:
LOGGING=EXPERT   ; send me the file for investigating what happened.

Version 1.4b released on 01.09.2019

Known Problem with 1.4b:
    The Wide-Graph window is blocked when the QRG is set (if Auto-Frq is used). Bug fix comes soon...

Bug fixes:
Accepting calls in S/P mode has been enhanced, calls are accepted now at the end of broken QSOs. too.

It seems that some (slow?) PCs require a small delay between the macro commands.
 If you receive a popup window with "Error-X, blocked session" without any reason, add a second line to the file
    callsign.txt:  delay=50. It will insert 50 ms delay between macro commands to give enough time for the macro execution.
    On run-up of the FT8-Helper this value will be indicated in the log field.

And now the most important bug fix:
eta-tester reported (thanks N1YU) that the FT8-Helper did not work with 12/h time setting. Now it has been fixed and any geographical Date/Time settings of the Windows OS are accepted.



Version 1.4 released on 21.08.2019
- FT-4 is supported with WSJT-X 2.1
- When started, the RUN and S/P boxes are green coloured
- Accepts calls from stations in S/P mode
- In S/P mode the strongest station is called if more than one station with the same priority colour is calling CQ.

Bug fixes:
- Accepts low case characters in callsign.txt
- Problems with RRR procedures are fixed
- Stations sending frames out of order should not confuse the FT8-Helper
- Timing error with fast computers and "Fast decoding" fixed
- Size of Log-session is set automatically (no need to preset it)
- Blocking of WSJT-X by modal (blocking) dialogs does not lead to unannounced crash

Version 1.3d
Bug fix:
FT8-Helper v1.3.d works now with both WSJT-X v2.0.1 and v2.1.0 (also 2.0.0 but not tested)
Problems with short callsign (e.g. A3B) and stations calling "CQ TEST" fixed. Side effect: callsigns like "RAEM" are not accepted.
Various crashes caused by blocked or nor reachable windows are catched and indicated to the user.

Verstion 1.3c
Problems were solved when using low resolution monitors. In S&P mode no Wide-Graph window required. The minimum monitor resolution is 1024 * 768 pixels. The text size for windows applications must be set to 100%. Read the short guide for hints using the FT8-Helper with low resolution monitors.