Table of Contents

2024 Radio Topics

HF-VHF Xgate 2024

Revisiting an old project

Previously...

DTMF Commands on VHF Port

Plans for 2024

2024 Progress

23/3/24

TMUX Session

24/3/24 : Thoughts....

The current channels are: Memory Dictionary (4 digits)

Initial try at 2-digit memory channels

mem_dict = {
 
        "01" : ["5279.0","USB"],
        "02" : ["5320.0", "USB"],
        "03" : ["5366.5", "USB"],
        "04" : ["5371.5", "USB"],
        "05" : ["5378.0", "USB"],
        "06" : ["5395.0", "USB"],
        "07" : ["5398.5", "USB"],
        "08" : ["5450.0", "USB"],
        "09" : ["5505.0", "USB"],
        "10" : ["7160.0", "LSB"],
        }
 if len(command_two[2:]) == 4:
 

becomes

 if len(command_two[2:]) == 2:
 
 
                elif command_two[:2] == "*1":
                    write_file("Frequency / Memory")
                    #if len(command_two[2:]) == 4:
                    if len(command_two[2:]) == 2:
                        new_freq = float(mem_dict[command_two[2:]][0])
                        new_mode = mem_dict[command_two[2:]][1]
                        write_file("Memory Channel selected %s" % mem_dict[command_two[2:]])
                        set_frequency(new_freq)
                        set_mode(new_mode)
                        write_status("freq",str(new_freq))
                        write_status("mode",new_mode)
                    else:
                        new_freq = float(command_two[2:])/10
                        set_frequency(new_freq)
                        write_status("freq",str(new_freq))
./xgate_current.py s
./xgate_current.py d

I've updated the mercurial repository - added new files, committed recent changes and made a clone of it on the shack laptop - in Dropbox (which might be a bad idea?)

There's another page about simple Mercurial , as an aid to remembering how to do it each time.

24/3/24 xgate_m710.zip Xgate scripts

Mobile Cross-band repeat access

29/3/24

If the X-gate is set to simplex mode (single band control) on VHF it should be possible to access the system via a mobile cross-band repeater from a low power UHF handheld.

This extends the range of the local VHF network.

If you are within UHF simplex range of the V/UHF cross-band repeater (usually vehicle mounted) and the vehicle is located within VHF range of the X-Gate (e.g. on a suitable distant hill-top) it should be possible to access the X-Gate and log in/change frequency etc. and to operate through it on HF, from the UHF side of the vehicle's Cross-Band repeater.

I am beginning tests on this using a TM-D710 mobile and TH-D72 handheld.

From the RSGB Band Plan

On 2m an appropriate place seems to be between 144.500 and 144.600, where there don't seem to be any prior centre-of-activity channels carved out.

I'll use 144.575MHz.

On 70cm an appropriate place seems to be between 433.800 and 434.250 - experiments

I'll use 433.825MHz

Talkthrough Watchdog Timer

I found an old piece of the python code I'd written that adds a Talkthrough Timeout to the X-Gate. It detects the commencement of a Talkthrough period and starts a timer. The timeout of this watchdog is set in the code, as is a pre-timeout warning time.

At the end of the warning time the VHF port sends “di-dit” every 20 seconds superimposed over the talkthrough (HF Receive) audio, to warn the VHF user(s) that the talkthrough will terminate soon.

At the end of the timeout period the Talkthrough is turned off and the system returns to it's quiescent state.

The Barrett 2062 Crossgate has a 10 minute inactivity timeout, which closes the cross-connection (talkthrough) after 10 minutes with no user activity.

My X-Gate doesn't take into consideration user activity, as the VHF→HF PTT does not get monitored by the X-Gate, so it is not currently possible to quantify “user inactivity”, by observing if there's any traffic on the VHF port. The Watchdog as it stands is a safety precaution against talkthrough getting locked up in transmit (in either direction).

After a timeout it's a simple matter of logging in again via VHF DTMF and re-starting talkthrough if it's still required. The “warning pips” give notice that this action is soon to be needed. If talkthrough is no longer needed then no further action is required.

Ideas

Make the Watchdog timer user switchable - be able to disable it if required.

Problems

29/3/24

Further Information

GM4SLV XGate Status Page http://gm4slv.plus.com:42109/