APRS: Uploading APRS frame ke APRS-IS - Revision history

Onnowpurbo: /* Langkah 2 - Connect ke Server */

2013-11-20T05:52:55Z

Langkah 2 - Connect ke Server

Onnowpurbo at 05:47, 20 November 2013

2013-11-20T05:47:40Z

Onnowpurbo at 05:35, 20 November 2013

2013-11-20T05:35:48Z

Onnowpurbo at 03:07, 20 November 2013

2013-11-20T03:07:18Z

Onnowpurbo at 03:04, 20 November 2013

2013-11-20T03:04:57Z

Onnowpurbo at 03:01, 20 November 2013

2013-11-20T03:01:58Z

Onnowpurbo: New page: This guided is intended for developers that would like to write client-side software, which accesses the APRS system via the Ethernet and uploads received frames. This is useful for device...

2013-11-20T02:37:51Z

New page: This guided is intended for developers that would like to write client-side software, which accesses the APRS system via the Ethernet and uploads received frames. This is useful for device...

New page

This guided is intended for developers that would like to write client-side software, which accesses the APRS system via the Ethernet and uploads received frames. This is useful for devices, such as I-gates, which receive APRS packets from and RF front-end and deliver them to the APRS network for wider information distribution.

This part of the guide, Part I, will address the subject of gaining access to APRS-IS. I found the documentation on APRS-Is to be a little ambiguous. Or maybe that's just me... Anyway, this is a pretty straightforward process if you have some to explain it to you clearly.
Contents
[hide]

1 Step 1 - Learn Just a Tiny Bit About the Servers
2 Step 2 - Connect to a Server
3 Step 3 - Get a Passcode
4 Step 4 - Connect and Login With Passcode
5 Step 5 - Send Some Data to APRS
6 Step 6 - Write an Application

Step 1 - Learn Just a Tiny Bit About the Servers

The APRS system is a set of servers and clients that is built around 3 "Core" servers, cleverly named "First", "Second", and "Third." APRS traffic is fed to these servers through a number of sources. I-Gates, for example, pass along data received on RF receivers along to these servers. There are also ~20000 Tier-2 servers that act as middle-men between I-Gates and the Core servers. Clients can connect to both Core and Tier-2 servers. Servers produce streams of APRS data that is sent to clients. Clients can request the data from the server to be filtered to a certain data type or geographic area. Clients can also upload data to the APRS server through this connection. Uploading requires passcode validation to protect the APRS infrastructure from abuse.

File:Aprs-is.png

This tutorial will show how to connect to a Core server, and I am making the assumption that the same process applies to
Step 2 - Connect to a Server

The APRS servers open several ports for various types of traffic. You can visit the status page by of each server on port 14501. In this example, we will be connecting to second.aprs.net. Thus the status url would be: [http://second.aprs.net:14501/]. Scrolling down this page, you will see status, mostly irrelevant stastitics, a list of ports, and connected users. You'll notice that each of the ports serves a particular use-case. If you want a feed of all of the traffic on the APRS network, ports like 20151 and 20152 provide such data. I am not interested in looking at data, just uploading packets to the network. I will pick a port that will generate less traffic. 20157 limits the traffic to a 100 km radius of my location. Anyway, pick your port and type the following into a terminal [Ubuntu]:

john@homepc:~/src/APRS-post$ nc second.aprs.net 20157
# javAPRSSrvr 3.15b06

For those not familiar with netcat (nc), we have just connected to second.aprs.net with on port 20157 using TCP/IP. On connection, the server sent us a friendly message, informing us that javAPRSSrvr is running. Now, its time to log into the server using a callsign, or if you're not a ham, a nickname.

In the nc terminal we will type:

user KI4MTT pass -1 ver "manual login"

To which the server responds:

# logresp KI4MTT unverified, server CORE-2

Great, so now we have connected to the server, and logged in with KI4MTT and a passcode of -1. Using this invalid passcode allows us to receive the APRS networks data feed, but will not let us upload frames. You can also verify your presence on the APRS network by going to [http://second.aprs.net:14501/] and doing a search for your call sign. The column to the right shows a yes/no verified status. Since I have not entered a valid passcode, I am not verified.

Also, one thing I noticed is that the APRS server is not sending any data. This is probably because I have not specified my location, and the APRS server does not know what traffic is within a 100 km radius.
Step 3 - Get a Passcode

The APRS system uses an algorithm that generates a five-digit passcode based on the user's call sign. The exact algorithm is simple and has been semi-public knowledge since the 90's. Up until a few months ago, there were easily accessible websites that would generate this passcode. After some unfortunate abuse of the APRS system, the community has made an effort to make passcodes harder to generate. I will say that you can find some Windows-based freeware to generate these passcodes, but I will not provide a link. The legit way to get a password is to e-mail pete@ae5pl.net, providing your callsign/login name for the algorithm the consume.
Step 4 - Connect and Login With Passcode

Next, we log into APRS using the valid pass code we got from Step 3:

john@homepc:~/src/APRS-post$ nc second.aprs.net 20157
# javAPRSSrvr 3.15b06
user KI4MTT pass 12345 ver "manual login"
# logresp KI4MTT verified, server CORE-2

Of course, you need to replace 'KI4MTT' and '12345' with your callsign and valid passcode. You'll notice the server reports a verified login. If you take another look at [http://second.aprs.net:14501/] and search for your callsign, you'll notice that you callsign also shows a verified status in the table.
Step 5 - Send Some Data to APRS

Now, I'm likely violating some terms of use by doing this, but I am going to send a single, spoofed APRS packet for the purposes of demonstration. In the terminal, I copy and paste the following line:

KI4MTT-1>APRS,TCPIP*:=3449.13N/12153.55W-KI4MTT Spoofed Position 2

If you happen to be running through this tutorial, be cool and replace my callsigns after you copy-paste.

Now, if we check [http://second.aprs.net:14501/], and look in the "packets received" column, it should show that your login has produce one packet (assuming you did only paste that line one.). We can also hop over to aprs.fi to see if we're really showing up on the network:

Looks like my spoofed position is in the middle of the Pacific... Don't mind the high velocity the image shows. That's just because I spoofed another position far away just a few seconds before that. There are probably some hams getting upset that I'm send fake positions here. Please accept my apologies...
Step 6 - Write an Application

Obviously, logging into the APRS system with netcat, and manually typing APRS packets isn't very practical. I went through this exercise after I tried to write a simple Python app that would format GPS data in an APRS frame and send it to the network. The app was failing, but didn't really have an visibility to the issue. As guessed, I wasn't using the correct login credentials and format. Taking these simple steps in the terminal helped me sort out the issues.

Now, the really interesting thing is to put together something funtional, like an i-gate or GPS client... So, let's head over to Uploading ARPS Frames to APRS-IS - Part II

This page will provide some links and other information to download a set of simple Python applications that can be used to log-in to APRS-IS and upload APRS frames. The intent of these examples is to show developers how to interface with APRS-IS with their own applications. This short tutorial assumes you are running Linux and you have Python + pertinent libraries installed.

This all should be applicable to Windows or MacOS environments with minor adjustments.

If you have any difficulty understanding material, and you haven't already done so, have a look at Uploading ARPS Frames to APRS-IS - Part I
Contents
[hide]

1 Step 1 - Get The Sample Code
2 Step 2 - Run First Sample Appliction
3 Step 3 - This is a really easy one...
4 Step 4 - My Excuses

Step 1 - Get The Sample Code

This is a simple step, and assumes you have git installed. In a terminal, type:

git clone https://github.com/jmalsbury/aprs-post.git

Step 2 - Run First Sample Appliction

Note - you need to change your callsign and password(passcode) for your own use. The Python script does not have a valid passcode entered, and thus, will not work. To get your own passcode to use with your corresponding callsign, e-mail Peter Lovevall, pete@ae5pl.net.

Anyway, change the callsigns and passcode and in then type this while in the source directory:

python aprs_example_1.py

Assuming you are able to connect to the server, you should be able to find your callsign with the specified location on sites like aprs.fi... If this is not the case, common errors are:

incorrect username and/or passcode. To test username passcode, follow instructions in ploading ARPS Frames to APRS-IS - Part I
packet doesn't conform to format restrictions [you modified something other than the callsigns in the packet string]

Feel free to e-mail john [at] jmalsbury [dot] com if you have questions
Step 3 - This is a really easy one...

Modify for your own purposes. = )
Step 4 - My Excuses

It's getting late, and I'm tired. I will create more examples when I have more time, but you're probably smart enough to take things from here.

==Referensi==

* http://www.jmalsbury.com/techwiki/index.php?title=Uploading_ARPS_Frames_to_APRS-IS_-_Part_I
* http://www.jmalsbury.com/techwiki/index.php?title=Uploading_ARPS_Frames_to_APRS-IS_-_Part_II

@@ Line 11: / Line 11: @@
 Client dapat tersambung ke Core and Tier-2 server.
 Server akan menghasilkan aliran data APRS yang dikirim ke client.
- Clients can request the data from the server to be filtered to a certain data type or geographic area. Clients can also upload data to the APRS server through this connection. Uploading requires passcode validation to protect the APRS infrastructure from abuse.
+==Langkah 2 - Connect ke Server==
-This tutorial will show how to connect to a Core server, and I am making the assumption that the same process applies to
+Server APRS membuka beberapa port untuk berbagai tipe traffic.
 The APRS servers open several ports for various types of traffic. You can visit the status page by of each server on port 14501. In this example, we will be connecting to second.aprs.net. Thus the status url would be: [http://second.aprs.net:14501/]. Scrolling down this page, you will see status, mostly irrelevant stastitics, a list of ports, and connected users. You'll notice that each of the ports serves a particular use-case. If you want a feed of all of the traffic on the APRS network, ports like 20151 and 20152 provide such data. I am not interested in looking at data, just uploading packets to the network. I will pick a port that will generate less traffic. 20157 limits the traffic to a 100 km radius of my location. Anyway, pick your port and type the following into a terminal [Ubuntu]:

@@ Line 6: / Line 6: @@
 ==Langkah 1 - Sedikit Tentang Server APRS IS==
-The APRS system is a set of servers and clients that is built around 3 "Core" servers, cleverly named "First", "Second", and "Third." APRS traffic is fed to these servers through a number of sources. I-Gates, for example, pass along data received on RF receivers along to these servers. There are also ~20000 Tier-2 servers that act as middle-men between I-Gates and the Core servers. Clients can connect to both Core and Tier-2 servers. Servers produce streams of APRS data that is sent to clients. Clients can request the data from the server to be filtered to a certain data type or geographic area. Clients can also upload data to the APRS server through this connection. Uploading requires passcode validation to protect the APRS infrastructure from abuse.
+APRS Sistem adalah sekumpulan server dan client yang dibangun berbasis pada 3 "Core" Server, yang dinamakan "First", "Second", dan "Third".
 File:Aprs-is.png

← Older revision		Revision as of 03:04, 20 November 2013
Line 4:		Line 4:


−	==Langkah 1 - ~~Learn Just a Tiny Bit About the Servers~~==	+	==Langkah 1 - Sedikit Tentang Server APRS IS==

	The APRS system is a set of servers and clients that is built around 3 "Core" servers, cleverly named "First", "Second", and "Third." APRS traffic is fed to these servers through a number of sources. I-Gates, for example, pass along data received on RF receivers along to these servers. There are also ~20000 Tier-2 servers that act as middle-men between I-Gates and the Core servers. Clients can connect to both Core and Tier-2 servers. Servers produce streams of APRS data that is sent to clients. Clients can request the data from the server to be filtered to a certain data type or geographic area. Clients can also upload data to the APRS server through this connection. Uploading requires passcode validation to protect the APRS infrastructure from abuse.		The APRS system is a set of servers and clients that is built around 3 "Core" servers, cleverly named "First", "Second", and "Third." APRS traffic is fed to these servers through a number of sources. I-Gates, for example, pass along data received on RF receivers along to these servers. There are also ~20000 Tier-2 servers that act as middle-men between I-Gates and the Core servers. Clients can connect to both Core and Tier-2 servers. Servers produce streams of APRS data that is sent to clients. Clients can request the data from the server to be filtered to a certain data type or geographic area. Clients can also upload data to the APRS server through this connection. Uploading requires passcode validation to protect the APRS infrastructure from abuse.

@@ Line 7: / Line 7: @@
 APRS Sistem adalah sekumpulan server dan client yang dibangun berbasis pada 3 "Core" Server, yang dinamakan "First", "Second", dan "Third".
-Traffic APRS dimasukan ke server ini melalui beberapa sumber. I-Gate,
+Traffic APRS dimasukan ke server ini melalui beberapa sumber. I-Gate, contoh, mengirim data yang di terima di penerima RF ke server.
-traffic is fed to these servers through a number of sources. I-Gates, for example, pass along data received on RF receivers along to these servers. There are also ~20000 Tier-2 servers that act as middle-men between I-Gates and the Core servers. Clients can connect to both Core and Tier-2 servers. Servers produce streams of APRS data that is sent to clients. Clients can request the data from the server to be filtered to a certain data type or geographic area. Clients can also upload data to the APRS server through this connection. Uploading requires passcode validation to protect the APRS infrastructure from abuse.
+ Clients can request the data from the server to be filtered to a certain data type or geographic area. Clients can also upload data to the APRS server through this connection. Uploading requires passcode validation to protect the APRS infrastructure from abuse.
-File:Aprs-is.png
+This tutorial will show how to connect to a Core server, and I am making the assumption that the same process applies to
-This tutorial will show how to connect to a Core server, and I am making the assumption that the same process applies to
+==Langkah 2 - Connect ke Server==
 The APRS servers open several ports for various types of traffic. You can visit the status page by of each server on port 14501. In this example, we will be connecting to second.aprs.net. Thus the status url would be: [http://second.aprs.net:14501/]. Scrolling down this page, you will see status, mostly irrelevant stastitics, a list of ports, and connected users. You'll notice that each of the ports serves a particular use-case. If you want a feed of all of the traffic on the APRS network, ports like 20151 and 20152 provide such data. I am not interested in looking at data, just uploading packets to the network. I will pick a port that will generate less traffic. 20157 limits the traffic to a 100 km radius of my location. Anyway, pick your port and type the following into a terminal [Ubuntu]:
@@ Line 34: / Line 36: @@
 Also, one thing I noticed is that the APRS server is not sending any data. This is probably because I have not specified my location, and the APRS server does not know what traffic is within a 100 km radius.
-Step 3 - Get a Passcode
 The APRS system uses an algorithm that generates a five-digit passcode based on the user's call sign. The exact algorithm is simple and has been semi-public knowledge since the 90's. Up until a few months ago, there were easily accessible websites that would generate this passcode. After some unfortunate abuse of the APRS system, the community has made an effort to make passcodes harder to generate. I will say that you can find some Windows-based freeware to generate these passcodes, but I will not provide a link. The legit way to get a password is to e-mail pete@ae5pl.net, providing your callsign/login name for the algorithm the consume.
-Step 4 - Connect and Login With Passcode
 Next, we log into APRS using the valid pass code we got from Step 3:
@@ Line 47: / Line 51: @@
 Of course, you need to replace 'KI4MTT' and '12345' with your callsign and valid passcode. You'll notice the server reports a verified login. If you take another look at [http://second.aprs.net:14501/] and search for your callsign, you'll notice that you callsign also shows a verified status in the table.
-Step 5 - Send Some Data to APRS
 Now, I'm likely violating some terms of use by doing this, but I am going to send a single, spoofed APRS packet for the purposes of demonstration. In the terminal, I copy and paste the following line:
@@ Line 58: / Line 63: @@
 Looks like my spoofed position is in the middle of the Pacific... Don't mind the high velocity the image shows. That's just because I spoofed another position far away just a few seconds before that. There are probably some hams getting upset that I'm send fake positions here. Please accept my apologies...
-Step 6 - Write an Application
 Obviously, logging into the APRS system with netcat, and manually typing APRS packets isn't very practical. I went through this exercise after I tried to write a simple Python app that would format GPS data in an APRS frame and send it to the network. The app was failing, but didn't really have an visibility to the issue. As guessed, I wasn't using the correct login credentials and format. Taking these simple steps in the terminal helped me sort out the issues.

@@ Line 1: / Line 1: @@
-This guided is intended for developers that would like to write client-side software, which accesses the APRS system via the Ethernet and uploads received frames. This is useful for devices, such as I-gates, which receive APRS packets from and RF front-end and deliver them to the APRS network for wider information distribution.
+Tulisan ini ditujukan untuk developer yang ingin mengembangkan software di sisi client yang ingin megakses APRS dan mengupload frame yang di terima-nya.
-Step 1 - Learn Just a Tiny Bit About the Servers
+==Langkah 1 - Learn Just a Tiny Bit About the Servers==
 The APRS system is a set of servers and clients that is built around 3 "Core" servers, cleverly named "First", "Second", and "Third." APRS traffic is fed to these servers through a number of sources. I-Gates, for example, pass along data received on RF receivers along to these servers. There are also ~20000 Tier-2 servers that act as middle-men between I-Gates and the Core servers. Clients can connect to both Core and Tier-2 servers. Servers produce streams of APRS data that is sent to clients. Clients can request the data from the server to be filtered to a certain data type or geographic area. Clients can also upload data to the APRS server through this connection. Uploading requires passcode validation to protect the APRS infrastructure from abuse.