FM APRS

[DU2XXR]

Thanks for the username change.

To clarify, this is an example of a message packet (as I sometimes manually hand-write it using KISS terminal)

Code: Select all

DU2XXR-7>APZIOR:WIDE1-1,WIDE2-1:APRSPH   :CQ #APRSThursday greetings to fellow packet radio enthusiasts!

DU2XXR-7 is the transmitting/origin station, which is my own DU2XXR callsign plus -7 SSID (which by convention means it's a portable device.

APZIOR is the "APRS destination" which is basically an identifier. I use this for my own APRSPH app/bot (code at https://github.com/jangelor/ioreth if anyone is interested to take a peek). This basically just means all of the packets that have this "destination" can be identified as coming from the same device. Yes, it's all arbitrary, but developers do follow the conventions for better organization.

WIDE1-1,WIDE2-1 is the digipath, which defines where the packet can and will be routed to. WIDE1-1 is basically for "fill-in" digipeaters. WIDE2-1 is the standard path for stationary stations, which means it gets digipeated 3x (a fill-in digipeater picks it up and digpeats it. A wider digipeater digipeats it, then decerements the path to WIDE2, which is then digipeated by another digipeater if one hears it). It would be good if this option can be user-defined, since different stations may need to specify different digipaths.

APRSPH is the actual recipient or addressee of the message. This is where the actual message is intended to be routed to.
Everything else after is the message content.

Now, that above is a message. This below is a packet, e.g., a status or beacon:

Code: Select all

APRSPH>APDW16,WIDE1-1,WIDE2-1:!1435.96ND12111.38E#PHG4560144.400MHz I'm a bot. HELP or NET[space]msg to join daily APRS Net http://aprsph.net DU2XXR/1

Similar to above, APRSPH is the origin station.

APDW16 is the "destination" which is actually the identifier. This particular packet is identified as coming from "direwolf 1.6" which automatically generates APDW16 as its APRS destination identifier.

WIDE1-1,WIDE2-1 is the digipath

Everything after the : is the packet content itself, including the encoded coordinates and position comment.

I changed your username


But... Can't AX25 packets be sent to any station (destination) , i.e the destination of the APRS packet could be set to VK3KYY-0 can't it.

Albeit I'm not running a packet receiver at the moment.

I changed your username


But... Can't AX25 packets be sent to any station (destination) , i.e the destination of the APRS packet could be set to VK3KYY-0 can't it.

Albeit I'm not running a packet receiver at the moment.

[SA0BUX]

Found this about the AX.25 destination.

But I must say that almost every instruction about setting up APRS I've seen for other radios mentioned APN000.

http://www.aprs.org/aprs11/tocalls.txt

In APRS, the AX.25 Destination address is not used for packet
routing as is normally done in AX.25. So APRS uses it for two
things. The initial APxxxx is used as a group identifier to make
APRS packets instanantly recognizable on shared channels. Most
applicaitons ignore all non APRS packets. The remaining 4 xxxx
bytes of the field are available to indicate the software version
number or application.

[VK3KYY]

Found this about the AX.25 destination.

But I must say that almost every instruction about setting up APRS I've seen for other radios mentioned APN000.

http://www.aprs.org/aprs11/toc

I can't access that link

[SA0BUX]

Found this about the AX.25 destination.

But I must say that almost every instruction about setting up APRS I've seen for other radios mentioned APN000.

http://www.aprs.org/aprs11/tocalls.txt

I can't access that link

Fixed,

[VK3KYY]

Thanks

[VK3KYY]

It looks like the list is mainly based around hardware manufactures with APK being Kenwood API Icon APY Yaseu etc

The key seems to be that the destination must start was AP

Looking at the APO*** it contains "Open" devices e.g.

Code: Select all

      
      APOAxx  OpenAPRS - Greg Carter
      APOCSG  For N0AGI's APRS to POCSAG project
      APOD1w  Open Track with 1 wire WX
      APOSBx  openSPOT3 by HA2NON at sharkrf.com
      APOSWx  openSPOT2
      APOTxx  Open Track
      APOU2k  Open Track for Ultimeter

Which appear to be quite different form each other

I searched for "OpenAPRS" and it seems to be PC software https://sourceforge.net/projects/openaprs/
OpenSpot is a hotspot, https://www.sharkrf.com/products/openspot-legacy/
Open Track seems to be APRS hardware that can connect to a transceiver
etc


So as far as I can see APOG77 would be valid and descriptive

[SA0BUX]

I tried some of the values: API92 , API910, APN001, APOSW0 didn't showed up in aprs.fi.

APK003 worked, APK004 didn't.

The digipeater is https://aprs.fi/info/SL3ZB-2

[VK3KYY]

I tried some of the values: API92 , API910, APN001, APOSW0 didn't showed up in aprs.fi.

APK003 worked, APK004 didn't.

The digipeater is https://aprs.fi/info/SL3ZB-2

Very interesting.

Thanks for testing.

Can you try

APOGD77

I just tried that, and it worked OK

Code: Select all

2023-08-28 21:04:27 AEST: VK3KYY>APOG77,WIDE1-1,WIDE2-1,qAO,VK3MDH-10:!3758.97S/14502.14E-

[1DangerMouse]

Was ever wondering if possible in a future if we can turn this Firmware APRS Feature into a Fill In Digipeater?

This be a Good Way to make a Portable Digi

Could This Be Possible?

[VK3KYY]

Was ever wondering if possible in a future if we can turn this Firmware APRS Feature into a Fill In Digipeater?

This be a Good Way to make a Portable Digi

Could This Be Possible?

This has been answered already several times.