## 起因有和群友 BI4IZE 讨论 BI9ALM 关于 aprsdroid 上面发 aprs 信息相关事项的时候，对 APRS 进行了疏理，同时还自向 BG9EGA 咨询了一些内容。因为涉及的东西感觉会不会还有些用，因此整理了这篇贴子。但是本人也有些一知半解的，所以可能还有些错的，因此欢迎大家提出建议。 ## iGATE 的功能首先 iGATE / digipeater 通常会有 - 无线电到互联网：将 166.640 等频段收到的 APRS 的报文上报到互联网（然后就能在 aprs.tv 和 aprs.fi 上看到了） - 无线电到无线电：将接受到的 APRS 报文（按照一定规则）再次转发； - 互联网到无线电：将 APRS 网络上的 APRS 报文转发到无线电上； - 互联网到互联网：从一个 TCP APRS 客户端发送到另一个 TCP APRS 客户端。我想说的是，第一点是 APRSDroid 等使用 TCP APRS 的可能给其他的 TCP APRS 客户端的呼号发送消息。无线电到无线电也可以，但是基本上无从互联网给无线电发送消息，因为很少有从互联网到无线电的转发，所以目标可能根本收不到。第二点是，iGATE 要正确配置，尽量不要从互联网转发到无线电，因为容易出事。主要原因是互联网 APRS 报文可能特别多，不正确的设置，会把 APRS 信道都占满影响别人。第三点是，最好不要随便发 APRS message （尤其是源地址与目标地址中有基于无线设备的）APRS 消息可能会重复发送（如果报文通信的过程不完成的话）（我在测试的时候，手台就一直给自己的另一个设备发送消息。。从无线电） ## APRS 的地址 APRS 上报地址和发送消息的时候，会有两个地址。一个是源地址，就是大家自己的设备的呼号加上一个杠（-）和数字，这个就是 SSID，是 AX.25 中的概念。发送的目标地址则是一系列的 SSID。比如 APN00,WIDE1-1,WIDE1-2 或者 APN00,WIDE1-1,BI9ZZZ,BI3TTR-10。如果英文阅读能力不错的话，可以直接看： - https://hamradio.my/2024/09/understanding-aprs-wide-path-configurations-from-wide1-1-to-wide3-3/ - https://blog.aprs.fi/2020/02/how-aprs-paths-work.html?m=1 如果像简单理解的话，就看我下面的内容： ### 目标一系列 SSID 的含义目标一系列的 SSID 中，第一个是实际的目标的设备，余下的都是“digipeater”。目标 SSID 一般都是软件设置好的，照着抄就行，这个我不太清楚具体哪个合适。比如威诺手台设置的就是 APN000，安卓 aprsdroid 就是 APDR16，APRS.TV 则是 APRSTV。 digipeater 则说明了 AX.25 的传播路径，比如 APN00,BI9ZZA, BI9ZZB,BI9ZZC 就是设置报文沿着 BI9ZZA -> BI9ZZB -> BI9ZZC 的 digipeater 的路径转播，而在无线电层面，就是 BI9ZZA 收到发送过来的 AX.25 报文后，先对报文中传播的链路作标记（修改），然后在发送出去，，，接着BI9ZZB 收到这个报文，再以同样地方式发送给BI9ZZC，然后BI9ZZC在发送给APN00。整个过程都是无线电广播的形式，其他的 digipeater 是不理会的。上面的 BI9ZZ* 实际上可以被成 WIDEm-n 的形式，（m和n是数字）。简单来说 WIDE 就是非特定的转发 APRS 报文。 m 指的是最多转发的次数，然后 n 是“强制”转发的次数。至于 WIDE中 m-n 的设置，一般 n 是要小于等于 m，m最好不超过 2。还有一般的 igate 似乎会自动上报收到的 APRS 报文，即便“没有传播完”。但是 APRS 还是会显示这个路径。。 ## orz （水平有限，不喜无喷 orz）

http://www.findu.com/cgi-bin/entermsg.cgi 用这个能从 IS 网络给人发信息，如果对方所在附近的 iGate 开启了 IS2RF（并且 iGate 最近 X 分钟以内听到过他）他就能收到

建议详细阅读https://www.aprs.org/和https://aprs-is.net/两个官方网站，APRS和APRS-IS其实关系不是很大，至少APRS-IS是可以独立的存在。APRS-IS部分只是解决了RF->IS/IS-RF这部分闭环。

Some understanding of APRS

BI3TTR

Cause

During a discussion with friends about APRS and the related issues of sending APRS information on aprsdroid (BI9ALM), I also clarified some aspects of APRS and consulted with BG9EGA.

I've organized this post because I believe some of the information contained within might still be relevant. However, my knowledge is limited, so there may be inaccuracies. Therefore, I welcome any suggestions or corrections from others.

IGATE's functions

Firstly, iGATE / digipeater typically have

From Radio to Internet: Sending APRS messages received on frequencies like 166.640 to the internet (which allows viewing on sites like aprs.tv and aprs.fi)
Radio to Radio: Re-transmit received APRS messages (according to certain rules);
From the Internet to Radio: Forwarding APRS messages from the APRS network to a radio;
From Internet to Internet: Sending from one TCP APRS client to another TCP APRS client.

What I want to say is that the first point is that APRSDroid, and other systems using TCP APRS, may send messages with a specific call sign to other TCP APRS clients. This can also work between radios and radios, but essentially, there's no way for a radio to receive messages from the internet because there are very few relays from the internet to radios. Therefore, the target radio might not even be able to receive the message.
Secondly, the iGATE needs to be properly configured, and ideally should not be used as a direct internet-to-radio connection, as this can cause problems. The main reason is that internet APRS messages may be very frequent, and incorrect settings can fill up the APRS channel, affecting others.
Third, it's best to avoid sending APRS messages (especially those with source and destination addresses that include wireless device-specific information). These messages may be repeatedly sent if the communication process is not completed successfully. During my testing, I found that my handheld radio was constantly sending messages to another device.

APRS addresses

When reporting on APRS and sending messages, there are two addresses: the source address and the destination address. The source address consists of your device's call sign plus a hyphen (-) and a number, which is the SSID (Service Set Identifier) as defined in AX.25. The destination address is a series of SSIDs, such as APN00, WIDE1-1, WIDE1-2 or APN00, WIDE1-1, BI9ZZZ, BI3TTR-10.
If you have good English reading skills, you can read it directly:

https://hamradio.my/2024/09/understanding-aprs-wide-path-configurations-from-wide1-1-to-wide3-3/
https://blog.aprs.fi/2020/02/how-aprs-paths-work.html?m=1
If you want to understand it simply, please see the content below:

The goal is to understand the meaning of a series of SSIDs.

Among the target SSIDs, the first one represents the actual device, while the rest are "digipeaters".

The target SSIDs are typically set in the software, so you just need to copy them. I'm not sure which one is most suitable in each case. For example, Wino Handheld sets it as APN000, Android aprsdroid uses APDR16, and APRS.TV uses APRSTV.

The digipeater then illustrates the path of AX.25 propagation, for example, APN00, BI9ZZA, BI9ZZB, BI9ZZC are set to send messages along the route BI9ZZA -> BI9ZZB -> The path broadcasting of the digipeater for BI9ZZC, and on the radio side, is that BI9ZZA receives the transmitted AX.25 message and first marks (modifies) the link within the message, then sends it out. Subsequently, BI9ZZB receives this message and sends it to BI9ZZC in the same way. Finally, BI9ZZC sends it to APN00. The entire process is a radio broadcast, and other digipeaters ignore it.

The BI9ZZ* can actually be represented in the form of WIDEm-n, where m and n are numbers. In simpler terms, WIDE refers to a non-specific forwarded APRS message.
m refers to the maximum number of times a message can be forwarded, and n represents the number of "forced" forwards.

Regarding the setting of m-n within WIDE, typically n should be less than or equal to m, and it's best if m is no more than 2.

Additionally, a general Igate seems to automatically report received APRS messages, even if they are "incomplete." However, the APRS system still displays this path.

orz

(My skills are limited, and I don't like negativity orz)

BG2ELG

http://www.findu.com/cgi-bin/entermsg.cgi

Using this, you can send messages to people on the IS network. If the person is located near an iGate where IS2RF is enabled (and if the iGate has heard them within the last X minutes), they will receive the message.

BloodBlade

What I want to say is that the first point is that APRSDroid, and other systems using TCP APRS, may send messages with a specific call sign to other TCP APRS clients. This can also work between radios and radios, but essentially, there's no way for a radio to receive messages from the internet because there are very few relays from the internet to radios. Therefore, the target radio might not even be able to receive the message.
Secondly, the iGATE needs to be properly configured, and ideally should not be used as a direct internet-to-radio connection, as this can cause problems. The main reason is that internet APRS messages may be very frequent, and incorrect settings can fill up the APRS channel, affecting others.
Third, it's best to avoid sending APRS messages (especially those with source and destination addresses that include wireless device-specific information). These messages may be repeatedly sent if the communication process is not completed successfully. During my testing, I found that my handheld radio was continuously sending messages to another device.

That's not the case; at least, the design philosophy of APRS encourages two-way communication and the use of a TX iGate, rather than simply being used asVehicle trackerPlease use it. Now, take over the organization, APRS Foundation.InstructionsAs follows:

There are also two types of IGates: receive-only and transmitting IGates. Receive-only IGates are essentially useful only as satellite and ISS "ground stations," allowing those who contact a digipeater on the bird to view proof of that contact on a map website (or, in the case of the International Space Station, also on ariss.net), and save screenshots for bragging rights. Transmitting APRS packets from the Internet over RF is not needed due to the large footprint of the bird overhead, which covers thousands of miles anyway; everyone using its digipeater will be able to hear each other. RX IGates are discouraged on local terrestrial APRS networks because TX IGates allow global text messaging and receipt of responses from, for example, information server queries, allowing two-way communications, but receive IGates are essentially just feeding the map websites. Transmitting IGates may also act as digipeaters, although there is no requirement for them to do so.

A simple translation: The main function of the iGate is to act as a ground station for APRS satellites, providing recording services for amateur radio operators. It is not recommended to use the iGate solely as a ground station for a local APRS network because it cannot provide complete APRS functionality for users within that local network.

Furthermore, the number of times a message can be retried is limited. Therefore, there is no need to worry about repeatedly sending messages because the receiver did not return an ACK (acknowledgement). This only occurs if there is a problem with the device's software.

BI1NIZ

It is recommended to thoroughly read the two official websites: https://www.aprs.org/ and https://aprs-is.net/. APRS and APRS-IS are not closely related; at least, APRS-IS can exist independently. APRS-IS mainly addresses the RF->This closed-loop system for IS/IS-RF.

BG9JDI

My iGate has an "is-">RF🤤

闽ICP备2021006864号-7

闽公网安备35020602002794号互联网举报中心

用户协议隐私政策社区规范积分规则中继规则转载须知
更新日志联系我们常见问题友情链接运营报告赞助

浩奇科技（厦门）有限公司

是无线电，把我们联系在一起