-
Hi!
Congratulation for MicroDigi.
My MicroDigi not mark Path with my callsign.
py5bk updated
5 years ago
-
@nogy @ge0rg
Seems that the AFSK is sending maybe one 'flag' (0x7e) byte at EOT.
My though is that being able to tweak the number of 'flags' at EOT might increase transmission reliability. …
-
I believe it is presently hard coded to WIDE2-1. For use with mobile stations it is recommended to have WIDE1-1,WIDE2 as described here... http://wa8lmf.net/DigiPaths/NNNN-Digi-Demo.htm.
The rea…
-
Hello,
I'm trying Xastir and Soundmodem to make an APRS digipeater, on the Raspberry PI3 with Linux Debian software, can you please kindly explain the settings to make it work perfectly, or any sugge…
-
Recently I've been working on some projects where the digipeater path that a packet takes is of interest. While I would love to just use the logging feature to store the information I need, it doesn'…
-
Unless I am missing something it looks like aprx doesn't currently support compressed position in beacons. They can be achieved using the raw beacon feature but it would be nice if they were supported…
-
Hi,
The predefined value CONFIG_AFSK_PREAMBLE_LEN is, at least in my setup, too short.
I'm using aprx as digipeater software and I have not found any possibilities to get it to send CMD_TXDELAY over …
-
I'm using a US Interface Navigator here and I'm trying to use the serial by-id naming convention. The Navigator's six serial ports identify themselves with long names:
root@rpi3:/etc/ax25# ls -la …
-
Hi,
it would be great to have a packet radio terminal in aprsdroid.
At the moment I restart my TNC and use a BT serial terminal App to communicate with TNC in command mode. It works but it is not …
-
Hi,
The RF>IS igate in ArcticTracker seems to unnecessarily drop duplicate packets with a fairly simple algorithm (CRC16) which may drop some extra packets due to crc16 hash collisions.
https://…
hessu updated
7 years ago