Pluto problems - blinking LED1

[Rishtonite]

Apologies if there is a better area of the forum to post this in.

Building a Portsdown4 was going ok until...

Newly purchased Pluto rev C. I thought I had bricked it but I've now got the F5OEO firmware installed and plugged into a USB3 port I can see the drive (E:) from my PC and can bring up the info page with http://192.168.2.1/

Connected to my PC via USB the ready LED is on continuously but LED1 repeatedly blinks twice (like .. .. .. .. ..)
Plugging into the Pi in my Portsdown4 it doesn't find Pluto.
I've spent a lot of time searching but been unable to find a solution.

Thanks
Barry G4IAT

[g0mjw]

What firmware did you install and what patches?

[Rishtonite]

As supplied Pluto firmware was v0.32. I then installed v0.39, then F5OEO v0.31-4-g9ceb-dirty
I'm only planning to use it locally on 23cm so have not extended the frequency range or enabled the 2nd processor.
I wasn't aware of any "patches" being needed.

[g0mjw]

I suspect that might be the problem then. Enable the second CPU. It is working with the PC I assume? The correct info page, not the original AD one.

The guidance is in the Wiki, https://wiki.batc.org.uk/Portsdown_4_Pl ... o_Firmware - do not deviate from the path.

It goes without saying, make sure you are using the latest Portsdown 4 version, fully updated and that you have a functioning USB cable, that you have a decent PI4 power supply etc. Do not apply more than 5v - see the wiki.

I am using later firmware, version 0303 and with a REV-C, that needs a patch. I don't use that with the PD4 The older version you installed should work without one, according to reports, but I don't have practical experience as I do not have a rev c.

[Rishtonite]

Sorry. I'm even more confused now.
1. I don't get a bing-bong when plugging Pluto in to the USB of my PC.
2. Running the .bat file I've reverted to the Pluto v0.39 firmware
3. In DFU mode installed then QO-100/DATV custom firmware, as shown by info.html BUT info.txt shows PlutoSDR Rev.B (Z7010-AD9363)
4. Now trying to extended frequency range, 2nd processor and the ad9364 'fix'
5. I can download SATSAGEN and clicking on identify it finds Pluto, but clicking on 'open' nothing happens.
6. I'm really confused by SSH. I've discovered that if I use the name of my PC, then @192.168.2.1, it asks for a password. I tried 'analog' but was denied.
7. I'm still getting the double blink on the Pluto LED1, which I don't think it should be doing.

Would appreciate any advice

[g0mjw]

For SSH the username is root and the password is analog - I would use putty rather than windows SSH.

Mike

[Rishtonite]

I've now managed to get in using SATSAGEN. root/analog
It shows v0.31-4-g9ceb-dirty and http:// ... tools/pluto
#

fw_printenv attr_name gives attr_name=compatible
fw_printenv attr_val gives attr_val=ad9364
then reboot
Unsure what to do/enter next.

[Rishtonite]

Aparrently the double blink is normal and I can "reverse" it (change from short flashes, 1 sec gap, to longer flashes, shorter gap) using SATSAGEN

Connected to the PC, everyting about the Pluto seemed to be correct, connected to the Pi of the Portsdown4 it could not be found.
While connected to the PC I had changed the device address in the config file, from the 192 range to the 172 range (which all my networked devices are on) and now Portsdown4 now sees the Pluto

Maybe it would be a good idea to add to appropriate wiki page(s) not to change the Pluto address from 192.168.2.1 when connecting to Portsdown4

[g0mjw]

Glad you got it to work - I think the list of things you should not do might be very long. Changing the USB IP address is probably right at the top, along with not connecting the TX directly to the RX, not installing the wrong firmware etc.

Mike

[Rishtonite]

Thanks for all your comments

Portsdown now sees the Pluto and I can TX. Got the stubby antennas on the Pluto, not yet connected the Pluto output to a power amp and external antenna BUT...

Other problems - that may be best asked under a different subject heading...

1. Plugging PicoTuner into Pi it now can't find Pluto (I'm using genuine Pi PSU) Pluto LEDs are 'abnormal'
2. When in TX I can see testcard on screen (if that's selected) but not webcam (or other sources?)

I need to re-read all the documentation as there are probably other menu options I don't yet fully understand, but I'm only planning to use the Portsdown (and PicoTuner) for local 23cm contacts.