Portsdown 4 - New Update 202008050
Re: Portsdown 4 - New Update 202008050
Hi Gareth
Portsdown 4 needs to be a new build. It is not a migration/update from the Portsdown A27 - so that is why you are having all the problems.
So a card rebuild should sort everything out.
Dave
Portsdown 4 needs to be a new build. It is not a migration/update from the Portsdown A27 - so that is why you are having all the problems.
So a card rebuild should sort everything out.
Dave
-
- Posts: 1380
- Joined: Wed Jan 06, 2016 9:46 am
Re: Portsdown 4 - New Update 202008050
Thanks Dave, I read the relevant wiki and it's busy doing its setup now 
Gareth

Gareth
-
- Posts: 1380
- Joined: Wed Jan 06, 2016 9:46 am
Re: Portsdown 4 - New Update 202008050
Assuming I choose the required protocols for Pluto operation, does this mean I can do DATV on 5.8GHz with my Portsdown 4/Pluto? Currently using DATVExpress to drive a pluto.
Gareth
Gareth
Re: Portsdown 4 - New Update 202008050
Hi Gareth
Yes. Not yet tested, but should work.
Dave
Yes. Not yet tested, but should work.
Dave
-
- Posts: 1380
- Joined: Wed Jan 06, 2016 9:46 am
Re: Portsdown 4 - New Update 202008050
Interesting, a quick play with a pair of Plutos this afternoon, all OK up to and including 13cm.
3.4GHz doesn't like the C920 but transmits a test card, 5.665 lights up the camera but doesn't TX camera or testcard.....or any RF....
TX confirmed as functioning on Langstone SW, listening with SDR#. For DATV I was using the Amsat DVBS GUI, which, when it works, its great......
I did notice that when I stopped transmitting on 3.4, the carrier continues for about 10 more seconds after the screen reverts to the main menu.
Gareth
3.4GHz doesn't like the C920 but transmits a test card, 5.665 lights up the camera but doesn't TX camera or testcard.....or any RF....
TX confirmed as functioning on Langstone SW, listening with SDR#. For DATV I was using the Amsat DVBS GUI, which, when it works, its great......
I did notice that when I stopped transmitting on 3.4, the carrier continues for about 10 more seconds after the screen reverts to the main menu.
Gareth
Re: Portsdown 4 - New Update 202008050
Hi Gareth
The TX over-run after deselecting transmit is normal with the Pluto on Test Card, Contest numbers and (when implemented) Desktop modes. Something to do with ffmpeg that I haven't got to the bottom of yet.
Please confirm that you selected 3.4 and 5.6 GHz by entering the frequency in "direct" mode, not by selecting a band; when correctly entered, the Band/Tvtr should show as 13 cm for both these frequencies. The original concept was that 3.4 and 5.7 GHz would be "transverter" bands, so there is a pre-programmed LO frequency for the bands labelled as 9_cm and 6_cm.
I have certainly seen RF at 5.7 GHz, but need to do some more testing.
Dave
The TX over-run after deselecting transmit is normal with the Pluto on Test Card, Contest numbers and (when implemented) Desktop modes. Something to do with ffmpeg that I haven't got to the bottom of yet.
Please confirm that you selected 3.4 and 5.6 GHz by entering the frequency in "direct" mode, not by selecting a band; when correctly entered, the Band/Tvtr should show as 13 cm for both these frequencies. The original concept was that 3.4 and 5.7 GHz would be "transverter" bands, so there is a pre-programmed LO frequency for the bands labelled as 9_cm and 6_cm.
I have certainly seen RF at 5.7 GHz, but need to do some more testing.
Dave
Re: Portsdown 4 - New Update 202008050
Hello Dave,
here is a short description of my test (at 31 degrees warm).
I've just sent on 13cm with Pluto.
DVBS H264 SR2500 FEC1 / 2.
EasyCap and Testcard work.
The Pluto does not send PI Screen and Contest Numbers.
I don't have PICam and Webbam C920.
In fact, it takes longer to switch on and off with Testcard than with EasyCap.
When I enter 3400 or 5700mhz, Band/Tvtr shows 13_cm.
here is a short description of my test (at 31 degrees warm).
I've just sent on 13cm with Pluto.
DVBS H264 SR2500 FEC1 / 2.
EasyCap and Testcard work.
The Pluto does not send PI Screen and Contest Numbers.
I don't have PICam and Webbam C920.
In fact, it takes longer to switch on and off with Testcard than with EasyCap.
When I enter 3400 or 5700mhz, Band/Tvtr shows 13_cm.
I always have crazy ideas.
Please don't be surprised.
Please don't be surprised.
-
- Posts: 1380
- Joined: Wed Jan 06, 2016 9:46 am
Re: Portsdown 4 - New Update 202008050
Thanks Dave. I was using 'keyboard entry' (desired frequency) which works on 3.4GHz, not on 5.6.
I just tried the transverter buttons - 9cm/3.4 works, 6cm/5.6 does not (assuming I'm looking in the right bit of spectrum of course....).
Not exactly a priority.......could we have the carrier button on Pluto, it would help with sanity checks
Not the weather for logical thinking....
Gareth
I just tried the transverter buttons - 9cm/3.4 works, 6cm/5.6 does not (assuming I'm looking in the right bit of spectrum of course....).
Not exactly a priority.......could we have the carrier button on Pluto, it would help with sanity checks

Not the weather for logical thinking....
Gareth
Re: Portsdown 4 - New Update 202008050
Thomas - my apologies. Contest numbers is only available in the Dev version at the moment (it was done as a quick job for someone to use in our contest at the weekend), and I have only just implemented Pi Screen on my test system. They'll both be in the next full release, and like testcard they will take longer to switchoff.
Gareth - more testing of 5.6 GHz required here, but I can't bring myself to turn on the enormous HP141T shack-heating spectrum analyser at the moment! Carrier mode for Pluto is on the to-do list, but is not straightforward as it is effectively another output device. I'm looking at this http://www.albfer.com/en/2020/08/10/plutotx/ as the most likely candidate approach.
Dave
Gareth - more testing of 5.6 GHz required here, but I can't bring myself to turn on the enormous HP141T shack-heating spectrum analyser at the moment! Carrier mode for Pluto is on the to-do list, but is not straightforward as it is effectively another output device. I'm looking at this http://www.albfer.com/en/2020/08/10/plutotx/ as the most likely candidate approach.
Dave
Re: Portsdown 4 - New Update 202008050
Hi Dave,
it takes 2 minutes and 50 seconds to complete a reboot on my Portsdown 4 running update 202008050 with no devices connected.
Alain, F1CJN has experienced something similar and you replied that it can take up to 90 seconds. I have built a new SD Card but no change.
Anyone else having such a long reboot cycle?
Wolfgang
it takes 2 minutes and 50 seconds to complete a reboot on my Portsdown 4 running update 202008050 with no devices connected.
Alain, F1CJN has experienced something similar and you replied that it can take up to 90 seconds. I have built a new SD Card but no change.
Anyone else having such a long reboot cycle?
Wolfgang