Page 1 of 2
Portsdown Software Update 201912100
Posted: Fri Dec 20, 2019 9:25 am
by G8GKQ
I have just released a minor software update for the Portsdown System. It only includes 2 new features:
- Auto-setting of the exact LNB LO offset (but only within 1 MHz of 9750 MHz) in the LongMynd RX by measuring the QO-100 beacon received frequency. Available on the RX Config menu
- Re-labelling and context-sensitive greying-out of some of the video source buttons
As part of the preparation for the forthcoming migration from Stretch to Buster, it also includes 2 bug-fixes:
- Cures a file handle leak that could result in crashes
- More constrained (safer) string handling
If you don't need any of the features above, there is no pressing need to apply the update.
Note that this update is only intended for the normal user running Portsdown on the Stretch operating system. If you are playing around with Buster, please don't apply this update - it will give unexpected results.
As always, please post bug reports here.
Happy Christmas!
Dave, G8GKQ
New install not working correctly.
Posted: Tue Dec 24, 2019 8:56 pm
by G4EWJ
I can go in and out of menus, but if I try to change a parameter, say the FEC, the BATC Portsdown screen comes up and stays there.
I've made a new SD card with Stretch Lite 2019-04-08 and run the commands:
wget
https://raw.githubusercontent.com/davec ... install.sh
chmod +x install.sh
./install.sh -d
RPi 3B with Waveshare 3.5A screen and official 5.1v psu, nothing else connected. I've previously had this combination working successfully with Portsdown.
Brian

- 20191224_203715.jpg (797.77 KiB) Viewed 3947 times
Re: New install not working correctly.
Posted: Wed Dec 25, 2019 10:29 am
by G8GKQ
Hi Brian
That’s a bit worrying. I’ll try to reproduce it later and get back to you. Any particular reason that you are using the dev release, not the production release?
Dave
Re: Portsdown Software Update 201912100
Posted: Wed Dec 25, 2019 11:53 am
by G4EWJ
Sorry, it was the production version, as confirmed by looking at the command history. I must have selected the wrong section when I copied and pasted it into the message above.
Brian
Re: Portsdown Software Update 201912100
Posted: Wed Dec 25, 2019 1:37 pm
by G8GKQ
Hi Brian
OK. I've tried to reproduce this, but it all worked for me. What make/size of SD Card are you using?
Next step would be to go to the command prompt, type"gui" (the alias to start the touchscreen), and watch the terninal to see what the last messages are before it crashes out of the GUI (which would leave you with the Portsdown Logo). Paste them here and I'll do some more thinking.
Thanks
Dave
Re: Portsdown Software Update 201912100
Posted: Wed Dec 25, 2019 2:08 pm
by G4EWJ
Sandisk 8GB 10 HC I
When I press the button for FEC 3/4, the terminal screen clears and goes back to the command prompt. I just managed to capture it before it cleared.
I can type gui again to restart it.
Thanks.
Brian

- Image 2019-12-25, 14-01-37.png (47.05 KiB) Viewed 3855 times
Re: Portsdown Software Update 201912100
Posted: Wed Dec 25, 2019 5:59 pm
by G8GKQ
Hi Brian
Looks like a problem writing to the config file. Please try:
Code: Select all
ls -l ~/rpidatv/scripts/portsdown*
and
and post the results here.
Thanks
Dave
Re: Portsdown Software Update 201912100
Posted: Wed Dec 25, 2019 10:08 pm
by G4EWJ
The files have only root write permissions. I think I must have done a sudo su as an automatic reaction after logging in.
I've started again from scratch and I can change settings now. I'll try it on tranmit tomorrow. Apologies and thanks for your help.
Brian
Re: New build with Lime - H264 not working.
Posted: Mon Jan 06, 2020 8:58 am
by mm0mgb
Reading this chain and I have the same issue, tried second rpi and lime usb with same result, tried fresh sd card with download from sites as per the build instructions. Help where do I go now. I had a working system but the sd card on that fried, now all symptoms as above chain despite new hardware and software????
Stuck
Andrew
Re: New build with Lime - H264 not working.
Posted: Mon Jan 06, 2020 10:57 am
by G8GKQ
Andrew
You probably have a different issue from the posts above, as the software has changed a lot since then. It may well be that I have changed something that has affected Lime USB support. I am unable to test this as I do not own a Lime USB.
Can you try it with a Lime Mini or other output device? Or give me more details of the exact configuration and problem?
Dave, G8GKQ