Upgrading ADALM-Pluto to include 70MHz - HOW -?
Posted: Mon Aug 06, 2018 9:48 am
I've finally got my hands on a Pluto unit and have got it working.
So far I've managed to upgrade it to FW version 0.28.
Installed Express DVB and got it transmitting on 437. Can also select and view a plain carrier (tick box in XPDVB) on similar frequencies via my SDR receiver.
It (Pluto) doesn't transmit a carrier on e.g. 70.400 Mhz so I'm assuming the firmware upgrade does not include the required fixes to open the TRX range up.
I've read the wiki entry herer https://wiki.analog.com/university/tool ... ustomizing and had it run the diagnostic for me (hence version number retrieved).
In terms of upgrading the coverage it then says
"From your favorite serial application, just open a serial connection to the PlutoSDR. The username is root and the password is analog."
Hang on, its USB device?? What is the author on about? Hyperterminal?? Or what?
SO could anyone provide a blow by blow guide on how to get into this particular menu/config file?
Much appreciated.....can't help but think AD should have done a better job of this documentation....
So far I've managed to upgrade it to FW version 0.28.
Installed Express DVB and got it transmitting on 437. Can also select and view a plain carrier (tick box in XPDVB) on similar frequencies via my SDR receiver.
It (Pluto) doesn't transmit a carrier on e.g. 70.400 Mhz so I'm assuming the firmware upgrade does not include the required fixes to open the TRX range up.
I've read the wiki entry herer https://wiki.analog.com/university/tool ... ustomizing and had it run the diagnostic for me (hence version number retrieved).
In terms of upgrading the coverage it then says
"From your favorite serial application, just open a serial connection to the PlutoSDR. The username is root and the password is analog."
Hang on, its USB device?? What is the author on about? Hyperterminal?? Or what?
SO could anyone provide a blow by blow guide on how to get into this particular menu/config file?
Much appreciated.....can't help but think AD should have done a better job of this documentation....