Exploring Port 30003 and 30106


#1

.
(1) Configure PuTTY for Telnet to Pi port 30003
port-30003-logger-1

.
(2) Configure PuTTY to save data in a csv file (30003.csv)
port-30003-logger-2

.
(3) Data stream displayed on PuTTY
port-30003-logger-3

.
(4) Data saved in file 30003.csv, displayed in MS Excel

.
(5) Reference Table 1
port-30003-logger-5A
port-30003-logger-5B

.
(6) Reference Table 2
port-30003-logger-6

.

Source of Reference Tables:

http://woodair.net/sbs/Article/Barebones42_Socket_Data.htm

.


Silly question - Raw Messages
Get data from dump1090 via command line/python
Data logger
Identifying aircraft 250+ miles out
Accessing past data fed to Flightaware
#2

… the problem with the data from port 30003 is that you’ll miss all flightaware anonymized mlat


#3

not if you use modesmixer.
grab data from port 30005 and create outServer avrmlat (ascii hex) and msg (ascii text) and route it to excel.with a bit of VBA code you could get nice stats too. would be nice if MLAT had a provider stamp / id too like MLAT_FA or MLAT_PP or MLAT_XCHG.

/modesmixer4 --web 9988 --inConnect localhost:30005 --outServer avrmlat:33033 --outServer msg:33133


#4

true - but totally different story :slight_smile:


#5

Exploring Port 30106

.
SCREENSHOT 1 of 4
port-30106-logger-1

.
SCREENSHOT 2 of 4
port-30106-logger-2

.
SCREENSHOT 3 of 4
port-30106-logger-3

.
SCREENSHOT 4 of 4


#6

you’ll still miss all flightaware anonymized mlat + without input filter you could get about 20 millions of tablerows a day - probably a bit much for an excel file …


#7

Why do you think that? All mlat results are sent to 30105/30106, regardless of whether they’re anonymized or not.


#8

i thought the anonymized weren’t still sent to 30106 by default because using this protocol could mess up re-feeds - but obviously i was wrong!

nc 127.0.0.1 30106 | sed -n ‘/~/p’ proved that - no doubt - you were right :slight_smile:


#9

As an alternate to PuTTY, you can use Windows Command Prompt console to telnet and display data from port 30003 and 30106 of dump1090.

NOTE:
In Windows by default, the Telnet Client is NOT enabled.
You have to first enable Telnet Client then only you can use it.

The method is detailed below.

(A) Enabling Telnet on Windows 7, 8.1, & 10

  1. Click on Start button

  2. In search, type Control Panel, and click on Control Panel icon displayed to open Control Panel.

  3. In Control Panel:
    a. Switch to Category view
    b. Click on Programs
    c. Click on Windows features on or off
    d. In the pop-up window, select “Telnet Client” and place a check mark besides it
    e. Click OK. This will start enabling process which may take about 30 seconds to complete.

  4. Restart the computer. After restart, the Telnet client will be enabled and can be used.

(B) Displaying output data from dump1090 port 30003 on Windows Telnet console.

  1. After Windows restarts, click start button and in search type cmd.exe. Click on “cmd.exe” displayed to open Command Prompt.

  2. In command prompt window, type telent and press Enter key. If Telnet client was enabled, you will see “Welcome to Microsoft Telent Client” message, and a telnet prompt Microsoft Telnet> -.

  3. in telnet command type “open ip-of-pi 30003” and press Enter key. If dump1090+DVB-T are working ok, you will see flow of messages. When these fail, the message flow will stop and remain stopped even if you wait for long time.

.
.

.

.

enable-telnet-windows-4

.

enable-telnet-windows-5

.

enable-telnet-windows-6

.

enable-telnet-windows-7


PiAware: Fine for 4+ yrs and now it's not