Satellite Wiki

User Tools

Site Tools

Trace:
en:plutoconverter:overview

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Next revision 		Previous revision
en:plutoconverter:overview [2022/04/04 00:33]
dj0abr created 		en:plutoconverter:overview [2022/04/04 12:19]
dj0abr [Program start]
Line 9: Line 9:
 ===== System Requirements ===== ===== System Requirements =====
  
-  * any Linux computer. E.g. a Raspberry or a PC with any Debian (Ubuntu) based Linux distribution. The computer just has to be fast enough to achieve the sample rate, which will usually work with a Raspberry PI 4. +  * any Linux computer. E.g. a Raspberry or a PC with any Debian (Ubuntu) based Linux distribution. The computer has to be fast enough to achieve the sample rate, which will usually work with a Raspberry PI 4. 
-  * an Adalmian Pluto. This can be connected to the computer via USB or Ethernet adapter.+  * an Adalm Pluto. Can be connected to the computer via USB or Ethernet adapter.
  
 ===== Connection ===== ===== Connection =====
  
-the RX input of the Pluto is connected to the signal source to be received+the RX input of the Pluto is connected to the signal source to be received.
  
 the TX output of the Pluto is connected to the amateur radio via a 40dB attenuator. the TX output of the Pluto is connected to the amateur radio via a 40dB attenuator.
  
-**the attenuator has two jobs. Firstly, it reduces the Pluto's output signal so that the radio receiver is not overloaded. On the other hand, it prevents damage to Pluto if you mistakenly "send into" Pluto**+**the attenuator has two jobs. Firstly, it reduces the Pluto's output signal so that the radio receiver is not overdriven. On the other hand, it prevents damage to the Pluto if you mistakenly "send into" Pluto**
  
 Such an attenuator can easily be built from three SMD resistors. Alternatively, the connection cable can be separated and the inner conductors left at a distance of 1 cm from each other. The exact value of the damping is irrelevant. Such an attenuator can easily be built from three SMD resistors. Alternatively, the connection cable can be separated and the inner conductors left at a distance of 1 cm from each other. The exact value of the damping is irrelevant.
 +
 +**Example:**
 +
 +{{:de:plutoconverter:bildschirmfoto_vom_2022-04-04_12-02-46.png?300|}}
 +{{:de:plutoconverter:dg40.png?300|}}
 +
 +this attenuator has just under 40dB and deliberately no match to 50 ohms, because the focus here is on safety in case of accidental transmission, which would not be guaranteed with a 50-ohm attenuator.
 ===== Installation ===== ===== Installation =====
  
Line 45: Line 52:
 ===PLUTO_ID=== ===PLUTO_ID===
 this ID is used to identify Pluto. There are three possible settings for this: this ID is used to identify Pluto. There are three possible settings for this:
-  * a single Pluto is connected via USB. This specification is meaningless here, since a single Pluto is automatically found on the USB. Example input:+  * a single Pluto is connected via USB. This specification is meaningless here, since a single Pluto is automatically found on USB. Example:
 <code> <code>
 PLUTO_ID 12345 PLUTO_ID 12345
 </code> </code>
-  * multiple Plutos are connected to USB. In this case, the Pluto's ID number must be specified. This can be printed out with the command: iio_info -s and then entered here. Example input:+  * multiple Plutos are connected to USB. In this case, the Pluto's ID number must be specified. This can be printed out with the command: iio_info -s and then entered here. Example:
 <code> <code>
 PLUTO_ID 1044730a199700191f001800f3647c5341 PLUTO_ID 1044730a199700191f001800f3647c5341
 </code> </code>
-  * Pluto is connected via Ethernet adapter and has a fixed IP address. Sample input (using Pluto's actual IP address, of course):+  * Pluto is connected via Ethernet adapter and has a fixed IP address. Sample (using Pluto's actual IP address, of course):
 <code> <code>
 PLUTO_ID ip:192.168.1.2 PLUTO_ID ip:192.168.1.2
Line 61: Line 68:
 This is Pluto's transmission frequency, here the NB transponder of QO100 should be output in the 70cm band (any other frequency in Pluto's working range is possible) This is Pluto's transmission frequency, here the NB transponder of QO100 should be output in the 70cm band (any other frequency in Pluto's working range is possible)
 <code> <code>
-TX_FREQ 435,450+TX_FREQ 435.450
 </code> </code>
  
Line 67: Line 74:
 this is the receiving frequency of Pluto, the NB transponder is downconverted to 739 MHz by an LNB if the LNB has the usual reference frequency of 25 MHz. this is the receiving frequency of Pluto, the NB transponder is downconverted to 739 MHz by an LNB if the LNB has the usual reference frequency of 25 MHz.
 <code> <code>
-RX_FREQ 739,450+RX_FREQ 739.450
 </code> </code>
  
Line 73: Line 80:
 the output power of the Pluto, adjustable from -40 to 0 dBm. If you have installed a PTT switch via GPO0 and GPO1, this value must be between -25 and 0 dBm, otherwise the PTT will not be switched. the output power of the Pluto, adjustable from -40 to 0 dBm. If you have installed a PTT switch via GPO0 and GPO1, this value must be between -25 and 0 dBm, otherwise the PTT will not be switched.
 <code> <code>
-TX_GAIN -5+TX_GAIN 0
 </code> </code>
  
 ===SAMPLERATE=== ===SAMPLERATE===
-this is the RX and TX sample rate. This must be slightly larger than twice the desired reception area. The NB transponder is 0.5MHz wide, so we choose 2 x 0.5 + 0.2 (reserve) = 1.2MHz for QO100.+this is the RX and TX sample rate. This must be slightly larger than twice the desired reception area. The NB transponder is 0.5MHz wide, so we choose 2 * 0.5 + 0.2 (reserve) = 1.2MHz for QO100.
 <code> <code>
 SAMPLE RATE 1.2 SAMPLE RATE 1.2
Line 97: Line 104:
 **Summary:** **Summary:**
  
-The file pluto_config.txt has the following content for QO100:+The file pluto_config.txt has the following (example) content for QO100:
 <code> <code>
 UDP_IPADDRESS 127.0.0.1 UDP_IPADDRESS 127.0.0.1
 PLUTO_ID 12345 PLUTO_ID 12345
-TX_FREQ 435,450 +TX_FREQ 435.450 
-RX_FREQ 739,450 +RX_FREQ 739.450 
-TX_GAIN -5+TX_GAIN 0
 SAMPLE RATE 1.2 SAMPLE RATE 1.2
 TX_BANDWIDTH 1 TX_BANDWIDTH 1
Line 120: Line 127:
 to start the program, type (still in the "Pluto" directory): to start the program, type (still in the "Pluto" directory):
 <code> <code>
-./Pluto+./pluto
 </code> </code>
  
-operating data that should be checked is displayed on the screen. If there is no error message, the Pluto downconverter is active and you should have reception.+The configuration data displayed on the screen should be verified. If there is no error message, the Pluto downconverter is active and you should have reception.
  
 The first QSO with a Pluto downconverter and an IC9700 took place on April 3, 2022 between PA0EKE and DJ0ABR. The first QSO with a Pluto downconverter and an IC9700 took place on April 3, 2022 between PA0EKE and DJ0ABR.
  
en/plutoconverter/overview.txt · Last modified: 2022/04/04 12:19 by dj0abr

Page Tools

Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Share Alike 4.0 International
CC Attribution-Share Alike 4.0 International Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki