Portsdown 4 Software Update

[G8GKQ]

Ken

I have just checked on my Portsdown 4, and the older version of C920 works fine with Pluto H264 DVB-S2. It may well be that the newer C920 does not currently work. I'm sure that it can be made to work - it's just that I don't have one to test with.

Also Pi Cam works well for me. Do you have an audio dongle connected? It needs one to work properly with Pluto.

All these modes (DVB-S2, DVB-T and the viewer) use the cameras in a different way , so the fact that they work in one mode does not guarantee operation in another.

Perhaps you could let me know about the audio dongle, and I'll do some guesswork on a fix to make the newer C920 work.

Dave

[G8GKQ]

Ken

The other thing that I would ask you to check is that you are using the correct firmware on the Pluto. Only this year-old version is supported:https://wiki.batc.org.uk/Portsdown_4_Pl ... o_Firmware. More recent verions do not work properly with the Portsdown.

I'll do some more detailed tests to see if I can reproduce your problem later today.

Dave

[g0mjw]

Hi Dave

I think we are going to have to check the Pluto firmware version on each powerup and throw an error as quite a few people don't have the knowledge to understand, and a Pluto they buy now, or a few years from now while attempting to build an older project when everyone else has moved on, like we saw recently, may well come with more recent firmware. Perhaps we need to put the known working firmware on the server.

Evariste is providing exciting new firmware updates on a regular basis and this may break compatibility with Portsdown. If the Portsdown could check which firmware version the Pluto has installed and display a message "Your Pluto Firmware is version XX. Compatibility with this Firmware is untested" at least the user would know what to do. Might also be worth checking the status of the CPUs and Frequency range that is enabled.

Mike

[G8GKQ]

Thanks Mike

I've been thinking about checking the Pluto as well. Is there a fixed field that uniquely identifies the Pluto firmware version?

Dave

[radiogareth]

Personally I have no idea but I do know that Alberto's SATSAGEN software will do something similar AND upgrade the Pluto to full/wideband and both CPUs etc. (if not already done) so it might be possible. He is very helpful....

Gareth

[g0mjw]

Auto update is dangerous as it might mess up peoples setups but the firmware is available

iio_attr -a -C fw_version

by the way the command to extend frequency changed with 0.32

fw_setenv compatible ad9364

Here is what my pluto tells me on starting a session:

Code: Select all

Using username "root".
root@192.168.1.46's password:
Send automatic password
Welcome to:
______ _       _       ______ _   _______
| ___ \ |     | |      |  _  \ | | | ___ \
| |_/ / |_   _| |_ ___ | | | | | | | |_/ /
|  __/| | | | | __/ _ \| | | | | | | ___ \
| |   | | |_| | || (_) | |/ /\ \_/ / |_/ /
\_|   |_|\__,_|\__\___/|___/  \___/\____/

v0.32-dirty
https://wiki.analog.com/university/tools/pluto
# iio_attr -a -C fw_version
Multiple contexts found. Please select one using --uri:
        0: (cf-ad9361-dds-core-lpc, ad9361-phy, cf-ad9361-lpc, xadc, adm1177 on Analog Devices PlutoSDR Rev.B (Z7010/AD9363)) [local:]
        1: 192.168.2.1 (Analog Devices PlutoSDR Rev.B (Z7010-AD9364)), serial=104473222a87000c1a002100588ad5ace8 [ip:pluto.local]
        2: 192.168.1.46 (Analog Devices PlutoSDR Rev.B (Z7010-AD9364)), serial=104473222a87000c1a002100588ad5ace8 [ip:pluto.local]
#

[g4bvk]

Hi Dave,

Many thanks to you all.

I did try again with an USB audio dongle plugged in and you are right, the Pi camera did work okay. Although, I found that plugging in any USB device also seems to work. Then I thought it maybe a power issue, so connected the dongle through a power hub and the Pi camera still worked okay.

The firmware seems to be correct, the Ryde RX is saying that the firmware is the 2101RC, but when I SSH into the Pluto and ran: (iio_attr –a –C fw_ version), it tells me the version is v0.31-4-g9ceb-dirty.

I have already done the update to the AD9364, along enabling the second CPU.

Ken G4BVK

[G8GKQ]

Hi Ken

Pleased that we are making progress. So I think that the only remaining issue is that the new C920 does not work?

I will look at what code modifications might be required to enable that. I'll also try to make the TX tolerant of not having an audio dongle with the Pi Cam

Dave.

[g4bvk]

Hi Dave,

Sorry, I’m still having a problem with my Portsdown 4 build. At present I’m trying to get a PE43703 attenuator working with no success. I have already modified the unit as described in the wiki and connecting the unit as laid out in “Portsdown 4 GPIO Connections” on the wiki.

CLK pin 29, DAT pin 31 and LE pin 10 on the GPIO.

Is that all correct or have I missed something?

Ken G4BVK

[G8GKQ]

Hi Ken

Those are the correct pins. I will try to check that my version works tomorrow.

Dave