public:radio:2024:hf-vhf_xgate
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| public:radio:2024:hf-vhf_xgate [29/03/24 09:18 GMT] – [Initial try at 2-digit memory channels] john | public:radio:2024:hf-vhf_xgate [06/03/25 06:49 GMT] (current) – external edit 127.0.0.1 | ||
|---|---|---|---|
| Line 206: | Line 206: | ||
| I've updated the '' | I've updated the '' | ||
| - | There' | + | There' |
| |24/3/24 |{{ : | |24/3/24 |{{ : | ||
| Line 214: | Line 214: | ||
| ===== Mobile Cross-band repeat access ===== | ===== Mobile Cross-band repeat access ===== | ||
| - | If the X-gate is set to '' | + | === 29/3/24 === |
| + | |||
| + | If the X-gate is set to '' | ||
| + | |||
| + | This extends the range of the '' | ||
| + | |||
| + | If you are within UHF simplex range of the V/UHF cross-band repeater (usually | ||
| I am beginning tests on this using a [[public: | I am beginning tests on this using a [[public: | ||
| + | |||
| + | |||
| + | From the RSGB Band Plan | ||
| + | |||
| + | * 144.500 MHz Image Modes (SSTV, Fax etc) | ||
| + | * 144.600 MHz Data Centre of Activity (MGM, RTTY etc) | ||
| + | * 433.8000-434.2500 MHz | ||
| + | |||
| + | On 2m an appropriate place seems to be between 144.500 and 144.600, where there don't seem to be any prior '' | ||
| + | |||
| + | |||
| + | I'll use 144.575MHz. | ||
| + | |||
| + | |||
| + | On 70cm an appropriate place seems to be between 433.800 and 434.250 - // | ||
| + | |||
| + | |||
| + | I'll use 433.825MHz | ||
| + | |||
| + | |||
| + | * X-Gate uplink changed to '' | ||
| + | |||
| + | ===== 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 // | ||
| + | |||
| + | At the end of the //warning// time the VHF port sends " | ||
| + | |||
| + | At the end of the //timeout// period the // | ||
| + | |||
| + | 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' | ||
| + | |||
| + | 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 " | ||
| + | |||
| + | |||
| + | === Ideas === | ||
| + | |||
| + | Make the Watchdog timer user switchable - be able to disable it if required. | ||
| + | |||
| + | * Added new DTMF Commands " | ||
| + | * Use these to write to the " | ||
| + | * The watchdog process can check the status file to decide whether to take action or not | ||
| + | * Tested and it works as expected | ||
| + | |||
| + | === Problems === | ||
| + | |||
| + | 29/3/24 | ||
| + | |||
| + | * Found that the IC-M710 HF radio has poor receive sensitivity - well below spec. 12dB SINAD should be at 0.5uV but it needs more like 3uV (or more) which is quite poor | ||
| + | * X-Gate taken out of use until I can either repair the '' | ||
| + | |||
| + | |||
| + | |||
| ===== Further Information ===== | ===== Further Information ===== | ||
public/radio/2024/hf-vhf_xgate.1711703932.txt.gz · Last modified: (external edit)
