Portsdown Buster 202003140 - Recommended Build

[ve3jgl]

I've downloaded the new buster-portsdown and installed it on buster 20200205 my problem is the waveshare has a blanked screen no button screen but the toutch part works.
here is the dump when connected on ssh :

(rasbian buster-portsdown set up 25 march 2020 shows a blank screen on waveshare 3.5")
(tx pressure button works but blank screen)

/home/pi/rpidatv/scripts/menu.sh: line 3188: fbcp: command not found
Webcam device name is none
Video capture device name is /dev/video0

VIDIOC_S_STD: failed: Inappropriate ioctl for device
Input device name: "ADS7846 Touchscreen"
Supported events:
Event type 0 (Sync)
Event type 1 (Key)
Event code 330 (Touch)
Event type 3 (Absolute)
Event code 0 (X)
Value 758
Min 0
Max 4095
Event code 1 (Y)
Value 3334
Min 0
Max 4095
Event code 24 (Pressure)
Value 0
Min 0
Max 255
X Scale Factor = 5.687500
Y Scale Factor = 7.109375
Starting with CalfactorX = 1.000000
Starting with CalfactorY = 1.000000
Starting with CalShiftX = 0.000000
Starting with CalShiftY = 0.000000
Read in the presets from the Config file
Mode Output in ReadModeInput() is IQ
In ReadBand, CurrentFreq = 437.000000, CurrentBand = 2 and band desig = d3
Mode Output in ReadModeInput() is IQ
Entering Start_Highlights_Menu1
Value=0 EasyCap Input
Value=on Caption State
Value=auto Audio Selection
Value=NONE Attenuator Selection
Value=1000 SR
Value=7 Fec
Value=d3 Band
Entering Update Window
Update Window

(rasbian stretch-portsdown 201912100 shows button screen on waveshare 3.5")

Webcam device name is none
Video capture device name is /dev/video0

VIDIOC_S_STD: failed: Inappropriate ioctl for device
Input device name: "ADS7846 Touchscreen"
Supported events:
Event type 0 (Sync)
Event type 1 (Key)
Event code 330 (Touch)
Event type 3 (Absolute)
Event code 0 (X)
Value 1049
Min 0
Max 4095
Event code 1 (Y)
Value 3403
Min 0
Max 4095
Event code 24 (Pressure)
Value 0
Min 0
Max 255
X Scale Factor = 5.687500
Y Scale Factor = 7.109375
Starting with CalfactorX = 1.037800
Starting with CalfactorY = 1.091900
Starting with CalShiftX = -13.100000
Starting with CalShiftY = -9.600000
Read in the presets from the Config file
Mode Output in ReadModeInput() is IQ
In ReadBand, CurrentFreq = 1255.000000, CurrentBand = 3 and band desig = d4
Mode Output in ReadModeInput() is IQ
Entering Start_Highlights_Menu1
Value=0 EasyCap Input
Value=on Caption State
Value=video Audio Selection
Value=NONE Attenuator Selection
Value=2000 SR
Value=2 Fec
Value=d4 Band
Entering Update Window
Update Window

ve3jgl luc

[G8GKQ]

Hi Luc

Looks like there was a problem downloading fbcp during your build. Two options: either wipe the card and build again, or run the following lines to try to get fbcp installed:

Code: Select all

cd /home/pi/
wget https://github.com/tasanakorn/rpi-fbcp/archive/master.zip
unzip master.zip
mv rpi-fbcp-master rpi-fbcp
rm master.zip

cd rpi-fbcp/
mkdir build
cd build/
cmake ..
make
sudo install fbcp /usr/local/bin/fbcp
cd /home/pi/

I've built new cards both yesterday and today without problems, so I think it must have been a temporary problem.

Let me know how you get on.

Dave

[ve3jgl]

thank's Dave your instructions were perfect, it worked on the firts try.
Luc ve3jgl

[BG0AUB]

There are, the firmware file. Testing 30 versions of the same signs.
I always think about the unknown problems in the process of building, （Including my problem encountered in portsdown2019 h264 doesn't work)is likely to be caused by network.
Can you provide a building to complete the SD card image file to test the reason?

44.jpg (191.61 KiB) Viewed 4099 times

[PA3GUO]

SW upgrade worked fine.
Thanks Dave

[G8GKQ]

Hi BG0AUB

You have some files in your home directory that suggest you have not followed the installation instructions properly.

What is the file install.sh.1 ? That should not be there. And the file install ?

Have you looked at the terminal during the build? Are there any errors coming up?

I cannot post an image file as I change the software too often for that. Last time I did it, it took me 4 hours, and I do not have the time to spare. I build at least one new card each day and very rarely have any problems. If you are really stuck, you could buy an SD Card from the BATC Shop.

Dave, G8GKQ

[PA3GUO]

Hi Dave

Due to the Portsdown I really got excited about DATV.
Thanks a lot, I really like all the options and features.
Buster works indeed more stable, great!

Is there somewhere an overview of which modes (4:3, 16:9, 720, 1080) work in combination with which inputs (cam, testcard, tcanimation) and which codec? Right now it is just trial and error what I do

Having fun here, both via QO100 as well as direct on 144 and 440 MHz.
Henk

[G8GKQ]

Hi Henk

Because of the way that the project has grown, there is no overview like you suggest. I agree that there should be, and it would be great to find a technical author to maintain some documentation! I do my best on the Wiki, but do not have time to do it as well as I would like.

To answer your specific question, currently it is only the MPEG-2 encoding that allows higher resolutions. The one exception is when using a C920 camera in raw H264 mode with a filter-modulator board (not a LimeSDR) at certain SRs and FECs, it can generate 1080p H264.

Pleased that you are finding the Buster build to be an improvement.

Dave, G8GKQ

[g0mjw]

My new minimal portable Portsdown.

Porta-Portsdown.jpg (677.18 KiB) Viewed 3740 times

RPI3
Pijuice
Waveshare Screen


To do anything useful things need to be attached, e.g. A webcam and a LimeSDR, or a network cable.

[radiogareth]

I can see this concept taking off. New case to include a Picamera, Hardwire a Lime mini inside but leaving access to SMA's, add external DC power (powerbank being commonplace - option). Good to go I've already got a RPI/Screen/Camera/DC converter/RTL Dongle which I use for 'sanity checking'.....and to do a proper job is on my to-do list.....)
Gareth