Radarcape:Requirements: Difference between revisions

From Beast Wiki
Jump to navigation Jump to search
← Older edit
imported>Dl4mea
 
(15 intermediate revisions by 4 users not shown)
Line 2: Line 2:
For normal operation a Radarcape requires
For normal operation a Radarcape requires
* a dry place with moderate temperatures
* a dry place with moderate temperatures
* AC power supply 110V or 230V, alternatively 5V/1A DC supply
* AC power 100V-240V 50-60Hz, alternatively 5V/1A DC supply
* An ethernet connection with a DHCP server
* Ethernet connection
 
The following optional services are dependent on Internet connection:
 
{| class="wikitable"
|-
! Protocol !! Transport !! Destination<br>Hostname !! Port !! style="text-align:left;" | Service !! Radarcape !! Airsquitter !! FLOX
|-
| HTTPS || style="text-align:center;" | TCP || jetvision.de || style="text-align:center;" | 443 || Download of software upgrades, registration and flightroutes databases || style="text-align:center;" | • || style="text-align:center;" | • || style="text-align:center;" | •
|-
| HTTPS || style="text-align:center;" | TCP || ddb.glidernet.org || style="text-align:center;" | 443 || Download of OGN database || style="text-align:center;" | • || style="text-align:center;" | • ||
|-
| Wireguard || style="text-align:center;" | UDP || link.jetvision.de || style="text-align:center;" | 8251 || Remote support (on request) || style="text-align:center;" | • || style="text-align:center;" | • || style="text-align:center;" | •
|-
| NTP || style="text-align:center;" | UDP || * ¹ || style="text-align:center;" | 123 || Backup system time syncronization || style="text-align:center;" | • || style="text-align:center;" | • || style="text-align:center;" | •
|-
| MLAT || TCP + UDP || mlat.jetvision.de || style="text-align:center;" | 10011 || jetvision MLAT flight tracking network || style="text-align:center;" | • || style="text-align:center;" | • ||
|-
| APRS  || style="text-align:center;" | TCP || aprs.glidernet.org || 14580 || OGN SDR decoder || || style="text-align:center;" | • ² || style="text-align:center;" | • ²
|}
 
¹ NTP server is configurable in network settings<br>² Regular case, may be hidden for security and privacy


===Software Requirements===
===Software Requirements===
Line 12: Line 33:


It depends on the users preferences how he wants to get access
It depends on the users preferences how he wants to get access
* The internal aircraft list (database) can be viewed with any kind of web browsers. It can be sorted by various parameters (filtering in preparation) and will update automatically in a configurable time.
* The internal aircraft list (database) and the Live 2D Map can be viewed with any kind of web browsers. The list can be sorted by various parameters (filtering in preparation) and will update automatically in a configurable time.
* KML files such as they are used by Google Earth will be provided and contain current positions and track information. Update rate (and later also contents) of these is also configurable.
* KML files such as they are used by Google Earth will be provided and contain current positions and track information. Update rate (and later also contents) of these is also configurable.
* Support for 2nd level software is provided by access methodes to the raw received data or port 30003 protocol data. Such is beeing used by [[Radarcape:Planeplotter|Planeplotter]], [[Radarcape:Globe-S|Globe-S]] and more.
* Support for 2nd level software is provided by access methodes to the raw received data or port 30003 protocol data. Such is beeing used by [[Radarcape:Planeplotter|Planeplotter]], [[Radarcape:Globe-S|Globe-S]] and more.


====Maintenance and Debugging Software====
Note that all services are accessible in parallel without major interaction.
 
As long as the user web interface does not support all configuration and maintenance tasks you may need to access to the internal Linux system. If necessary, we will describe all steps to be done here in detail, so you should not be afraid about that. We strongly recommend [http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html putty] for this task, as it supports the back side serial port as well as networking SSH connections.


===Antenna Requirements===
===Antenna Requirements===
Line 26: Line 45:
Due to the high sensitivity of the Radarcape a preamplifier normally is not recommended. Only if your cable attenuation exceeds 6dB, you may consider using one. The cables we supply with the Radarcape do even with 10m length hold the so called "3dB rule" and can be used without doubts.
Due to the high sensitivity of the Radarcape a preamplifier normally is not recommended. Only if your cable attenuation exceeds 6dB, you may consider using one. The cables we supply with the Radarcape do even with 10m length hold the so called "3dB rule" and can be used without doubts.


The antenna connector of the Radarcape is a standard SMA female connector on the back side.
The antenna connector of the Radarcape is a standard SMA female connector on the back side.
 
===Running without DHCP===
For direct connection to a PC we will provide methodes how to install the Radarcape with a fixed IP address and without need of a DHCP server soon.

Latest revision as of 10:21, 6 November 2024

Radarcape Requirements

For normal operation a Radarcape requires

  • a dry place with moderate temperatures
  • AC power 100V-240V 50-60Hz, alternatively 5V/1A DC supply
  • Ethernet connection

The following optional services are dependent on Internet connection:

Protocol Transport Destination
Hostname		 Port Service Radarcape Airsquitter FLOX
HTTPS TCP jetvision.de 443 Download of software upgrades, registration and flightroutes databases • • •
HTTPS TCP ddb.glidernet.org 443 Download of OGN database • •
Wireguard UDP link.jetvision.de 8251 Remote support (on request) • • •
NTP UDP * ¹ 123 Backup system time syncronization • • •
MLAT TCP + UDP mlat.jetvision.de 10011 jetvision MLAT flight tracking network • •
APRS TCP aprs.glidernet.org 14580 OGN SDR decoder • ² • ²

¹ NTP server is configurable in network settings
² Regular case, may be hidden for security and privacy

Software Requirements

Aircraft Data Access

Since the Radarcape does not have it's own display, external software is required for displaying the aircraft data that it receives.

It depends on the users preferences how he wants to get access

  • The internal aircraft list (database) and the Live 2D Map can be viewed with any kind of web browsers. The list can be sorted by various parameters (filtering in preparation) and will update automatically in a configurable time.
  • KML files such as they are used by Google Earth will be provided and contain current positions and track information. Update rate (and later also contents) of these is also configurable.
  • Support for 2nd level software is provided by access methodes to the raw received data or port 30003 protocol data. Such is beeing used by Planeplotter, Globe-S and more.

Note that all services are accessible in parallel without major interaction.

Antenna Requirements

The antenna should be placed as high as possible and as free as possible. Nearby metallic parts should be avoided or have a minimum distance of about 50cm. Big metallic surfaces around, for example metallic chimney casing, may cause reflections and degrade reception in some cases.

Due to the high sensitivity of the Radarcape a preamplifier normally is not recommended. Only if your cable attenuation exceeds 6dB, you may consider using one. The cables we supply with the Radarcape do even with 10m length hold the so called "3dB rule" and can be used without doubts.

The antenna connector of the Radarcape is a standard SMA female connector on the back side.

Retrieved from "https://wiki.jetvision.de/index.php?title=Radarcape:Requirements&oldid=3776"