REMOTETRX(1)

πŸ“¦
version 24.02 Β· 3 versions
, in debian trixie, fedora 43, fedora 44, ubuntu questing

πŸ’– REMOTETRX πŸ’–

okay bestie, so this is the manual page for remotetrx β€” the SvxLink remote transceiver application, straight out of the User Manuals ✨


✨ NAME ✨

remotetrx β€” the SvxLink remote transceiver application, no cap πŸŽ€


πŸ¦‹ SYNOPSIS πŸ¦‹

remotetrx [--help] [--daemon] [--logfile=log file]
[--config=configuration file] [--pidfile=pid file] [--runasuser=user
name]

🌸 DESCRIPTION 🌸

so remotetrx is literally the SvxLink remote transceiver application πŸ’… it connects to a receiver and/or a transmitter, and then the main SvxLink server can connect to the remote transceiver server over TCP/IP to get audio to/from it. that's the whole vibe.

it also lowkey slaps via RF instead of TCP/IP πŸ‘‘ an example use of the latter would be if the repeater is placed in a remote location where there is no network. then networked remote receivers can be linked up to the repeater via RF from a link site where network is available. iconic workaround, honestly.

the setup is pretty straight forward 🫢 the setup of a receiver or a transmitter is done in the same way as in the SvxLink server, so use the svxlink.conf(5) manual page as a reference for that. the remotetrx-specific configuration is described in the remotetrx.conf(5) manual page. two pages, one mission ✨

on the SvxLink server side you need to configure a networked receiver/transmitter β€” that's described in the svxlink.conf(5) manual page in the Networked Receiver/Transmitter Section. and if you're using multiple receivers you also want to configure a voter and make proper calibration of the signal level detector on each receiver πŸ’€ don't skip the calibration bestie, it's giving attention to detail.


πŸŽ€ OPTIONS πŸŽ€

  • --help β€” print a help message and exit. little snapshot of the good stuff πŸ’–
  • --daemon β€” start the SvxLink remote receiver server as a daemon. background mode era ✨
  • --runasuser β€” start RemoteTrx as the specified user. the switch to the new user will happen after the log and pid files has been opened β€” timing matters, iykyk πŸ¦‹
  • --logfile=log file β€” specify a log file to put all output into. both stdout and stderr will be redirected to the log file 🌸
  • --pidfile=pid file β€” specify a pid file to write the process ID into πŸ‘‘
  • --config=configuration file β€” specify which configuration file to use. pick your fighter πŸŽ€

πŸ’œ FILES πŸ’œ

  • /etc/svxlink/remotetrx.conf (or deprecated /etc/remotetrx.conf) β€” the system wide configuration file. see remotetrx.conf(5) for further details ⭐
  • ~/.svxlink/remotetrx.conf β€” per user configuration file. see remotetrx.conf(5) for further details πŸ’…
  • /etc/svxlink/remotetrx.d/* β€” additional configuration files. this directory is setup by the CFG_DIR configuration variable 🌈

🧚 ENVIRONMENT 🧚

  • ASYNC_AUDIO_NOTRIGGER β€” set this environment variable to 1 if you get an error about ioctl: Broken pipe during remotetrx server startup when using OSS audio. the fix is right there bestie 😭
  • ASYNC_AUDIO_ALSA_ZEROFILL β€” set this environment variable to 0 to stop the Alsa audio code from writing zeros to the audio device when there is no audio to write available.
lowkey heads up: in the original page, the next variable got squished onto the end of this one β€” ASYNC_AUDIO_UDP_ZEROFILL set this environment variable to 1 to enable the UDP audio code to write zeros to the UDP connection when there is no audio to write available. πŸ’€ it's a whole separate var, she just got crowded.
  • HOME β€” used to find the per user configuration file 🏠

🌟 AUTHOR 🌟

Tobias Blomberg (SM0SVX) <sm0svx at svxlink dot org> β€” main character energy, fr fr πŸ‘‘


πŸ”₯ REPORTING BUGS πŸ”₯

bugs should be reported using the issue tracker at https://github.com/sm0svx/svxlink πŸ›

questions about SvxLink should not be asked using the issue tracker. instead use the group set up for this purpose at groups.io: https://groups.io/g/svxlink πŸ™ˆ (right channel for the right question, bestie, that's the whole assignment)


🌈 SEE ALSO 🌈

svxlink(1), remotetrx.conf(5), svxlink.conf(5), siglevdetcal(1) πŸ¦‹πŸ’–


and that's the page!! 🫢 this one was written for Linux and it's the AUGUST 2021 edition of REMOTETRX(1) β€” go forth and link some transceivers, bestie, periodt πŸ’…βœ¨πŸ“

πŸ“¦ where this page comes from