Portsdown Buster 202003140 - Recommended Build
Portsdown Buster 202003140 - Recommended Build
Hi
I have just released a new version of the Portsdown Buster software 202003140 (the Pi Day build?). Testing has now reached the stage where I can recommend this as the new build for anyone using a LimeSDR Mini. The main new feature in this version is that there are 10 fixed QO-100 uplink frequencies selectable from the frequency menu.
Thanks to all the beta testers for their comments - I have decided to keep it simple!
More details in the forthcoming CQ-TV.
Dave, G8GKQ
I have just released a new version of the Portsdown Buster software 202003140 (the Pi Day build?). Testing has now reached the stage where I can recommend this as the new build for anyone using a LimeSDR Mini. The main new feature in this version is that there are 10 fixed QO-100 uplink frequencies selectable from the frequency menu.
Thanks to all the beta testers for their comments - I have decided to keep it simple!
More details in the forthcoming CQ-TV.
Dave, G8GKQ
Re: Portsdown Buster 202003140 - Recommended Build
Dave, thanks, I will give it a try.
One question, are those 10 frequencies configurable?
Don’t forget some of us are up-converting from UHF so hard coded 2.4GHz frequencies are of no use.
Colin.
One question, are those 10 frequencies configurable?
Don’t forget some of us are up-converting from UHF so hard coded 2.4GHz frequencies are of no use.
Colin.
Re: Portsdown Buster 202003140 - Recommended Build
Hi Colin
No, not yet. But I'm sure that you can:
Simply edit the 3 lines below https://github.com/BritishAmateurTelevi ... uch.c#L284.
The top line is the actual frequencies, the second and third the button labels. This will work, but menu 1 won't display your uplink frequency unless you also edit https://github.com/BritishAmateurTelevi ... h.c#L16437 and the offset 2 lines below it.
Then run the alias "ugui" from the command line and it will compile, install and run your new version.
I'll look at storing a configurable offset in one of the config files in a future build.
Dave
No, not yet. But I'm sure that you can:
Simply edit the 3 lines below https://github.com/BritishAmateurTelevi ... uch.c#L284.
The top line is the actual frequencies, the second and third the button labels. This will work, but menu 1 won't display your uplink frequency unless you also edit https://github.com/BritishAmateurTelevi ... h.c#L16437 and the offset 2 lines below it.
Then run the alias "ugui" from the command line and it will compile, install and run your new version.
I'll look at storing a configurable offset in one of the config files in a future build.
Dave
Re: Portsdown Buster 202003140 - Recommended Build
Thanks Dave,
Now we are nearly all sending H265 what's the best way to view it? UDP I assume - but I thought the PI could do some H265 decoding- https://forum.kodi.tv/showthread.php?tid=343068
Mike
Now we are nearly all sending H265 what's the best way to view it? UDP I assume - but I thought the PI could do some H265 decoding- https://forum.kodi.tv/showthread.php?tid=343068
Mike
Re: Portsdown Buster 202003140 - Recommended Build
Hi Mike
It would be really useful if you were able to use the info at that link to build a Pi 4 that would decode and display H265 sent to it over UDP (or in due course through a fifo). I could then try and port longmynd on to it so that it at least worked as a receiver.
It's a massive job to port the whole Portsdown on to a Libre-elec based build on a Pi 4. I was going to get Portsdown working on a Pi 4 on Buster first, as Raspberry Pi foundation have promised that H265 display will work on Buster/Pi 4 in the future.
Thanks
Dave
It would be really useful if you were able to use the info at that link to build a Pi 4 that would decode and display H265 sent to it over UDP (or in due course through a fifo). I could then try and port longmynd on to it so that it at least worked as a receiver.
It's a massive job to port the whole Portsdown on to a Libre-elec based build on a Pi 4. I was going to get Portsdown working on a Pi 4 on Buster first, as Raspberry Pi foundation have promised that H265 display will work on Buster/Pi 4 in the future.
Thanks
Dave
Re: Portsdown Buster 202003140 - Recommended Build
Thanks Dave,
I will give it a try later this week.
Colin.
I will give it a try later this week.
Colin.
Re: Portsdown Buster 202003140 - Recommended Build
Hi Dave, thanks! As we discussed in Cardiff last weekend, Is this still using the custom Lime firmware?
Just about to create a card.
73
Just about to create a card.
73
Re: Portsdown Buster 202003140 - Recommended Build
Hi John
Initial testing with the normal firmware seems good. So you can stick with the same as you use for Narrow Band.
Dave
Initial testing with the normal firmware seems good. So you can stick with the same as you use for Narrow Band.
Dave
Re: Portsdown Buster 202003140 - Recommended Build
Ah, OK.
Just got it going with the custom firmware today but it looks easy enough to revert, so I'll try that at some point.
In the meantime, next I'll try out the Video stream to Portsdown from vMix script. I'll let you know how I get on
Great job! MUCH appreciated,,,,,
73
John
Just got it going with the custom firmware today but it looks easy enough to revert, so I'll try that at some point.
In the meantime, next I'll try out the Video stream to Portsdown from vMix script. I'll let you know how I get on
Great job! MUCH appreciated,,,,,
73
John
Re: Portsdown Buster 202003140 - Recommended Build
Rebuilt my Portsdown with Buster today during the QO-100 Net. Unfortunately I didn't get it working until just after the net had finished.
Hopefully next week.
Dave, I recompiled as you suggested to change the preset frequencies. However I didn't change the button text or the display offset code as I found configuring a transverter entry called QO-100 with the necessary offset for my system works fine. Selecting that transverter then displays the correct uplink and downlink frequencies.
Hopefully next week.
Dave, I recompiled as you suggested to change the preset frequencies. However I didn't change the button text or the display offset code as I found configuring a transverter entry called QO-100 with the necessary offset for my system works fine. Selecting that transverter then displays the correct uplink and downlink frequencies.