Firstly, it fixes a bug (introduced in the last release) that broke the MPEG-2 transmit capability.
Secondly, it changes the way that the Pluto is addressed in the transmit script. This should allow the Pluto to be connected through a LAN (for DVB-S and DVB-S2, not DVB-T), rather than by USB. My preference is that you connect the Pluto by USB, but this change may allow other configurations to work.
Thanks to Clive G3JGA and Michel HB9DUG for helping with this release.
Please report any new bugs here.
I just tried transmitting via a Pluto the other day (while using the last version of software) after connecting the Pluto via the LAN. To my surprise the system worked perfectly! I have had the odd problem doing this in the past. It was the fact that I had just connected the Pluto to my network without altering the IP address or anything. The reason this may have worked so well may be that I have a secondary address range setup on my LAN for 192.168.2.(0 - 255) .
So I was going to say well done but now I will try the update.........
PS As I had two Portsdowns and one with the Pluto still via USB, I was wondering if this would cause any problems as both Plutos are the same address but the USB Pluto was not seen by the network. (Not that I thought it would be)
So I have updated to the latest software 202102150 from 202101310 and the Pluto does not work! I tried the other Portsdown 4 which still has the older software and it worked fine. The TX mode was S2QPSK 437MHz 333K SR H264 FEC 1/2 in both cases.
PS. The second Portsdown was also connected only by 5GHz WiFi so even more surprised it worked!
To access 2 connected Plutos reliably from one Portsdown, you will need to give them separate IP Addresses and then tell the Portsdown (with the latest software update) which IP address/Pluto you want it to use.
The only fully supported configuration is a Pluto connected by USB. I can't test other configurations (network-connected Plutos) as everyone's network/router is different. I made a change in the latest software update which increases the chance of network-connected Plutos working; I can do no more.
Your previously-working solution relies on your router telling your Portsdown what IP address the device known as "pluto.local" is using. Not all routers do this reliably, and that means that the Portsdown cannot access the Pluto. Hence I have changed the Portsdown to refer to the Pluto's IP address; this should provide a more robust solution once set up properly.
Here are a few clues:
First thing is to give you Pluto a LAN network address.
Use Advanced IP Scanner to find your LAN network addresses including your Router which is also (usually) the gateway address.
Pick a free address for your Pluto
Using the above information plug your Pluto into your computer (mine is a Windows 10 )
The Pluto is seen as a new drive and should be seen in the 'This PC' menu and also open a window showing contents: Now open the file config (probably by double clicking on it) If you need to use a program to open it then choose Notepad.
You can now edit or fill the line shown in 2 below
Enter the address you have chosen for your Pluto, the netmask is probably already correct and the gateway address is probably your router's address.
These must be addresses in the address range of your router and have the first three groups matching your system. In my case 192.168.123.xxx
While editing this you can change the Pluto's name if you need, for example if it is your second Pluto change it to pluto-2 (see 1 )
Note that I have changed the frequency correction in position 3 as my Pluto was slightly off frequency.
Once you have edited these you can save the file back to the Pluto and then 'eject' the Pluto from the computer by right clicking on the Pluto in the file explorer's left hand plane and choose Eject.
Now plug the Pluto into a USB to Network adapter and connect to your network as Described in the WiKi
Put the Pluto address into the Portsdown (menu 3 - Pluto Config)
It should now work if you choose the correct settings ( works best at lower SR)
- Pluto config txt.png (59.64 KiB) Viewed 471 times
Langstone is affected by these changes I have made!
The renaming of the Pluto (in position 1 above) stops the Langstone working. Keep any Langstone pluto as pluto not pluto-2 etc.
The IP address of the Pluto when connected to the Portsdown by USB is the address under Network and the IP address of the Pluto when on the Network via a USB to LAN adapter is under USB so don't get confused!!!
It probably is best to load Langstone on your Portsdown using the Pluto plugged into the USB of the Portsdown before trying the USB Network configuration.
However I find that Langstone works over the LAN network once you sort out these addresses (use the USB network address when setting up Langstone to use over the network.
It would seem you could put the Pluto at the aerial for reception.
Langstone will work over a network but it may give variable results. It depends how much other traffic is on the network.