Portsdown 4 new Pluto vs an old Pluto
Portsdown 4 new Pluto vs an old Pluto
I am referring to a thread in the WB chat addressing "new Pluto vs an Old Pluto". -> Manufacturer's details may be found here: https://wiki.analog.com/university/tool ... g/hardware
As the afore mentioned document says, there are 2 versions of Pluto in the market. When talking about Pluto it seems to be worth to name the version which is addressed.
Recently got a new Pluto to work with Portsdown 4. The sticker on Pluto's blue Box says Rev.C, while the board inside says Rev.D, so call it Rev.C/D.
Used the Portsdown 4 set-up description as per wiki to configure Pluto from Portsdown. Verified on Portsdown menu 15 that both CPUs are activated and the frequency range extension has been introduced. Portsdown and Pluto worked as expected, except at 146 and 71 MHz no output was delivered from Pluto with Portsdown not going to transmit mode i.e. PTT signal was not raised.
G8GTZ wrote in an earlier thread that an additional input is necessary for Pluto Rev.D to achieve the frequency extension: input
fw_setenv compatible ad9364
pluto_reboot reset
That's it, all working.
Access to Pluto via network is easy: connect the OTP directly to the USB connector next to the blue LEDs and feed 5V to Pluto via the PWR USB connector. (Also checked the Y-USB cable sollution: did not function in my case with Rev.C/D)
Furthermore tested the Pluto Rev.C/D output being controlled from Portsdown 4 Pluto PWR setting. (M1)
Suggest to amend the wiki to differentiate between the 2 Pluto versions in the market and to reflect the additional frequency extension input necessary for Pluto Rev.C/D in the write-up.
dc1op,Hubertus
As the afore mentioned document says, there are 2 versions of Pluto in the market. When talking about Pluto it seems to be worth to name the version which is addressed.
Recently got a new Pluto to work with Portsdown 4. The sticker on Pluto's blue Box says Rev.C, while the board inside says Rev.D, so call it Rev.C/D.
Used the Portsdown 4 set-up description as per wiki to configure Pluto from Portsdown. Verified on Portsdown menu 15 that both CPUs are activated and the frequency range extension has been introduced. Portsdown and Pluto worked as expected, except at 146 and 71 MHz no output was delivered from Pluto with Portsdown not going to transmit mode i.e. PTT signal was not raised.
G8GTZ wrote in an earlier thread that an additional input is necessary for Pluto Rev.D to achieve the frequency extension: input
fw_setenv compatible ad9364
pluto_reboot reset
That's it, all working.
Access to Pluto via network is easy: connect the OTP directly to the USB connector next to the blue LEDs and feed 5V to Pluto via the PWR USB connector. (Also checked the Y-USB cable sollution: did not function in my case with Rev.C/D)
Furthermore tested the Pluto Rev.C/D output being controlled from Portsdown 4 Pluto PWR setting. (M1)
Suggest to amend the wiki to differentiate between the 2 Pluto versions in the market and to reflect the additional frequency extension input necessary for Pluto Rev.C/D in the write-up.
dc1op,Hubertus
Re: Portsdown 4 new Pluto vs an old Pluto
Thanks Hub
I've updated the Wiki.
Dave
I've updated the Wiki.
Dave
Re: Portsdown 4 new Pluto vs an old Pluto
Hi Dave,
Can you clarify the connections, you say connect the OTP directly to the USB connector next to the blue LEDs and feed 5V to Pluto via the PWR USB connector.
do you connect the USB OTP port to portsdown 4 blue or black USB ports and also supply 5 volts the the pluto’s USB pwr connector.
Cheers
Brian G6HFS
Can you clarify the connections, you say connect the OTP directly to the USB connector next to the blue LEDs and feed 5V to Pluto via the PWR USB connector.
do you connect the USB OTP port to portsdown 4 blue or black USB ports and also supply 5 volts the the pluto’s USB pwr connector.
Cheers
Brian G6HFS
Re: Portsdown 4 new Pluto vs an old Pluto
Sorry I should of addressed this to Hubertus
Brian G6HFS
Brian G6HFS
Re: Portsdown 4 new Pluto vs an old Pluto
Hi Brian,
to load the additional line of code (to extend the frequency range) into the Pluto Rev.C/D via ethernet/ssh connection, the OTP is indeed plugged directly to the USB connector next to the blue LED and the 5V is fed via the Pluto PWR USB connector.
The OTP network input is then tied to a network/PC which enables access to Pluto.
For DATV operation with Portsdown 4 you only need to connect Pluto via its USB with Portsdown. The link provides data and power (5,02V stby, 5,01V tx). I use the black USB port with Pluto running problemfree during the set up period and later while testing. I did not use or test the 5V supply via the Pluto PWR USB connector.
73, Hubertus
to load the additional line of code (to extend the frequency range) into the Pluto Rev.C/D via ethernet/ssh connection, the OTP is indeed plugged directly to the USB connector next to the blue LED and the 5V is fed via the Pluto PWR USB connector.
The OTP network input is then tied to a network/PC which enables access to Pluto.
For DATV operation with Portsdown 4 you only need to connect Pluto via its USB with Portsdown. The link provides data and power (5,02V stby, 5,01V tx). I use the black USB port with Pluto running problemfree during the set up period and later while testing. I did not use or test the 5V supply via the Pluto PWR USB connector.
73, Hubertus
Re: Portsdown 4 new Pluto vs an old Pluto
Hi Hubertus,
Thanks for the reply.
Brian G6HFS
Thanks for the reply.
Brian G6HFS