Portsdown 4 Pluto - Revision history

G8GKQ: /* Suitable Pluto Firmware */

2025-10-18T19:38:58Z

Suitable Pluto Firmware

G8GKQ: /* Suitable Pluto Firmware */

2025-10-18T19:38:28Z

Suitable Pluto Firmware

G0MJW: /* Suitable Pluto Firmware */

2024-12-10T22:15:03Z

Suitable Pluto Firmware

G8GKQ: /* Powering the Pluto */

2023-10-11T19:18:14Z

Powering the Pluto

G8GKQ: /* Suitable Pluto Firmware */

2022-09-24T16:22:47Z

Suitable Pluto Firmware

G8GKQ: /* Pluto Output Level */

2022-09-24T16:22:20Z

Pluto Output Level

G8GKQ: /* Limitations */

2022-09-24T16:22:07Z

Limitations

G8GKQ: /* Suitable Pluto Firmware */

2022-09-24T16:18:44Z

Suitable Pluto Firmware

G4FRE: /* Limitations */

2022-02-12T08:05:10Z

Limitations

G8GKQ: /* Limitations */

2021-12-03T13:02:51Z

Limitations

@@ Line 17: / Line 17: @@
 All initial testing was done using F5OEO's "for the brave" Pluto firmware (FIRM2101RC of 5 February 2020).  Extract the firmware from this zip file''' [[:File:FIRM2101RC.zip]] '''and follow the instructions on this web page '''VERY CAREFULLY''' [https://wiki.analog.com/university/tools/pluto/users/firmware#mass_storage_update Analog Devices Firmware Upgrade Instructions].   The Pluto must already have been modified for extended frequency range, and it is worth enabling the second processor.
-An alternative, more capable, firmware is version 2110 which does not suffer fronm the maximum 4.2 GHz frequency limitation of version 2101.  This can be downloaded from here: [[:File:FIRM2110.zip]].  This firmware allows transmissions in the 5.7 GHz band (thanks to Gareth g4XAT for discovering this).
+An alternative, more capable, firmware is version 2110 which does not suffer fronm the maximum 4.2 GHz frequency limitation of version 2101.  This can be downloaded from here: [[:File:FIRM2110.zip]].  This firmware allows transmissions in the 5.7 GHz band (thanks to Gareth G4XAT for discovering this).
 Note that the more recent Revision C (outside label) (marked as Revision D on the PCB) Plutos need an extra environment variable setting for the frequency extension.  In addition to the other commands, at the command line of the Pluto enter

@@ Line 15: / Line 15: @@
 ===Suitable Pluto Firmware===
-All testing has been done using F5OEO's "for the brave" Pluto firmware (FIRM2101RC of 5 February 2020).  Extract the firmware from this zip file''' [[:File:FIRM2101RC.zip]] '''and follow the instructions on this web page '''VERY CAREFULLY''' [https://wiki.analog.com/university/tools/pluto/users/firmware#mass_storage_update Analog Devices Firmware Upgrade Instructions].   The Pluto must already have been modified for extended frequency range, and it is worth enabling the second processor.
+All initial testing was done using F5OEO's "for the brave" Pluto firmware (FIRM2101RC of 5 February 2020).  Extract the firmware from this zip file''' [[:File:FIRM2101RC.zip]] '''and follow the instructions on this web page '''VERY CAREFULLY''' [https://wiki.analog.com/university/tools/pluto/users/firmware#mass_storage_update Analog Devices Firmware Upgrade Instructions].   The Pluto must already have been modified for extended frequency range, and it is worth enabling the second processor.
 Note that the more recent Revision C (outside label) (marked as Revision D on the PCB) Plutos need an extra environment variable setting for the frequency extension.  In addition to the other commands, at the command line of the Pluto enter
   fw_setenv compatible ad9364
-You can check that you have the correct Firmware loaded from the "Pluto Configuration Menu" (reached from Menu 3).  It should report Firmware version v0.31-4-g9ceb-dirty.
+You can check that you have the correct Firmware loaded from the "Pluto Configuration Menu" (reached from Menu 3).  It should report Firmware version v0.31-4-g9ceb-dirty or v0.32-dirty.
 ===Powering the Pluto===

@@ Line 15: / Line 15: @@
 ===Suitable Pluto Firmware===
-All testing has been done using F5OEO's "for the brave" Pluto firmware (FIRM2101RC of 5 February 2020).  Extract the firmware from this zip file [[:File:FIRM2101RC.zip]] and follow the instructions on this web page '''VERY CAREFULLY''' [https://wiki.analog.com/university/tools/pluto/users/firmware#mass_storage_update Analog Devices Firmware Upgrade Instructions].   The Pluto must already have been modified for extended frequency range, and it is worth enabling the second processor.
+All testing has been done using F5OEO's "for the brave" Pluto firmware (FIRM2101RC of 5 February 2020).  Extract the firmware from this zip file''' [[:File:FIRM2101RC.zip]] '''and follow the instructions on this web page '''VERY CAREFULLY''' [https://wiki.analog.com/university/tools/pluto/users/firmware#mass_storage_update Analog Devices Firmware Upgrade Instructions].   The Pluto must already have been modified for extended frequency range, and it is worth enabling the second processor.
 Note that the more recent Revision C (outside label) (marked as Revision D on the PCB) Plutos need an extra environment variable setting for the frequency extension.  In addition to the other commands, at the command line of the Pluto enter

← Older revision		Revision as of 19:18, 11 October 2023
Line 25:		Line 25:

	The Raspberry Pi 4 has increased power capabilities on its USB ports, and the Pluto does not work well with USB Hubs, so it is recommended that you connect the Pluto directly to a USB3 port (the blue ones) on the Raspberry Pi 4. Do not use a USB hub or power the Pluto from its USB power port.		The Raspberry Pi 4 has increased power capabilities on its USB ports, and the Pluto does not work well with USB Hubs, so it is recommended that you connect the Pluto directly to a USB3 port (the blue ones) on the Raspberry Pi 4. Do not use a USB hub or power the Pluto from its USB power port.
		+
		+	The Pluto will sometimes refuse to connect to the Portsdown 4 if the voltage on the Raspberry Pi's USB port is above 5.0v. In contrast to the advice for the LimeSDR (where the Raspberry Pi should be supplied with 5.2 v), it is recommended that for Pluto operation the Raspberry Pi is run from 5.0 v. An alternative is to modify a USB lead for the Pluto with a Schottky rectifier diode in the positive supply line to drop about 0.25 v.

	===Current Functionality===		===Current Functionality===

@@ Line 17: / Line 17: @@
 All testing has been done using F5OEO's "for the brave" Pluto firmware (FIRM2101RC of 5 February 2020).  Extract the firmware from this zip file [[:File:FIRM2101RC.zip]] and follow the instructions on this web page '''VERY CAREFULLY''' [https://wiki.analog.com/university/tools/pluto/users/firmware#mass_storage_update Analog Devices Firmware Upgrade Instructions].   The Pluto must already have been modified for extended frequency range, and it is worth enabling the second processor.
-Note that the more recent Revision C (outside label) (marked as Revision D on the PCB) Plutos need an extra environment variable setting for the frequency extension.  At the command line of the Pluto enter
+Note that the more recent Revision C (outside label) (marked as Revision D on the PCB) Plutos need an extra environment variable setting for the frequency extension.  In addition to the other commands, at the command line of the Pluto enter
   fw_setenv compatible ad9364

@@ Line 49: / Line 49: @@
 ===Pluto Output Level===
-Thankks to DC1OP for this plot of Pluto output level
+Thanks to DC1OP for this plot of Pluto output level
 [[File:Pluto output.jpg|576px]]

← Older revision		Revision as of 16:22, 24 September 2022
Line 46:		Line 46:
	* An audio source (such as a webcam microphone or USB dongle) must be present and selected for DVB-S/S2 transmissions, otherwise the transmitter will not operate.		* An audio source (such as a webcam microphone or USB dongle) must be present and selected for DVB-S/S2 transmissions, otherwise the transmitter will not operate.
	* Transmitting only a carrier is not supported by the Pluto firmware		* Transmitting only a carrier is not supported by the Pluto firmware
		+
		+	===Pluto Output Level===
		+
		+	Thankks to DC1OP for this plot of Pluto output level
		+
		+	[[File:Pluto output.jpg\|576px]]

← Older revision		Revision as of 16:18, 24 September 2022
Line 16:		Line 16:

	All testing has been done using F5OEO's "for the brave" Pluto firmware (FIRM2101RC of 5 February 2020). Extract the firmware from this zip file [[:File:FIRM2101RC.zip]] and follow the instructions on this web page '''VERY CAREFULLY''' [https://wiki.analog.com/university/tools/pluto/users/firmware#mass_storage_update Analog Devices Firmware Upgrade Instructions]. The Pluto must already have been modified for extended frequency range, and it is worth enabling the second processor.		All testing has been done using F5OEO's "for the brave" Pluto firmware (FIRM2101RC of 5 February 2020). Extract the firmware from this zip file [[:File:FIRM2101RC.zip]] and follow the instructions on this web page '''VERY CAREFULLY''' [https://wiki.analog.com/university/tools/pluto/users/firmware#mass_storage_update Analog Devices Firmware Upgrade Instructions]. The Pluto must already have been modified for extended frequency range, and it is worth enabling the second processor.
		+
		+	Note that the more recent Revision C (outside label) (marked as Revision D on the PCB) Plutos need an extra environment variable setting for the frequency extension. At the command line of the Pluto enter
		+	fw_setenv compatible ad9364

	You can check that you have the correct Firmware loaded from the "Pluto Configuration Menu" (reached from Menu 3). It should report Firmware version v0.31-4-g9ceb-dirty.		You can check that you have the correct Firmware loaded from the "Pluto Configuration Menu" (reached from Menu 3). It should report Firmware version v0.31-4-g9ceb-dirty.

← Older revision		Revision as of 08:05, 12 February 2022
Line 42:		Line 42:
	* The maximum supported symbol rate for DVB-S or DVB-S2 with the Pluto is 1 MS. If you want higher SRs it is recommended that you use a LimeSDR Mini with the LimeDVB firmware.		* The maximum supported symbol rate for DVB-S or DVB-S2 with the Pluto is 1 MS. If you want higher SRs it is recommended that you use a LimeSDR Mini with the LimeDVB firmware.
	* An audio source (such as a webcam microphone or USB dongle) must be present and selected for DVB-S/S2 transmissions, otherwise the transmitter will not operate.		* An audio source (such as a webcam microphone or USB dongle) must be present and selected for DVB-S/S2 transmissions, otherwise the transmitter will not operate.
		+	* Transmitting only a carrier is not supported by the Pluto firmware

@@ Line 40: / Line 40: @@
 * In DVB-S mode, a bug prevents transmissions at FECs of 5/6 and 7/8.  All other FECs are OK.  There is no plan to fix this.
 * In DVB-S and DVB-S2 modes, if a callsign with a / is used (like G8GKQ/P), the Pluto will transmit "Service01" as the Provider ID.
 * An audio source (such as a webcam microphone or USB dongle) must be present and selected for DVB-S/S2 transmissions, otherwise the transmitter will not operate.