Closed andimik closed 4 years ago
Tomorrow I'll have a look. did not look for a long time to it
Op ma 9 dec. 2019 om 21:00 schreef andimik notifications@github.com:
Dear Jan, I've lots of PCs and Laptops running with your great tools. But on my Raspberrry Pi 3B (not +) I've discovered that the eti-cmdline-rtl does not work properly (no matter if I define a manual gain). eti-cmdline-rawfiles works, indeed.
At the start the fibquality is 100 but after a few seconds it gets less and will end at 0. At the same time the CPU load is not much (see screenshot).
[image: image] https://user-images.githubusercontent.com/24510556/70465657-b66f9e00-1ac1-11ea-94ac-42fe64fe0a61.png
On the same RPI3 qtdab works without any problems, even with Protection level 4A (used in Slovenia).
[image: image] https://user-images.githubusercontent.com/24510556/70466290-1286f200-1ac3-11ea-8784-991254973abe.png [image: image] https://user-images.githubusercontent.com/24510556/70466467-7a3d3d00-1ac3-11ea-9e36-176988bd1b4e.png
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/JvanKatwijk/eti-stuff/issues/43?email_source=notifications&email_token=ACCPHQA5V3K73WJFFND4M4TQX2PWNA5CNFSM4JYQ4T72YY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4H7HCFJQ, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACCPHQGEO6XLXPITPEPGC7DQX2PWNANCNFSM4JYQ4T7Q .
-- Jan van Katwijk
Additionally, I have to mention that the exported eti file is full of errors.
I also tried to pipe rtl_sdr into eti-cmdline-rawfile but this also went wrong.
Seems there is a buffer overflow soon.
Thanks for the new commit.
It's really a bit better on my RPI3, now the counter on left bottom is faster and the eti-file contains all service IDs (but is still not errorfree). Screenshots taken with XPADxpert, see https://basicmaster.de/ which can analyse eti files.
Before:
After:
In the next days I will get a RPI4 and will test it again.
I optimized some parts, but the "major breakthrough" failed, due to problems with the compiler chain. In the past, two, may be three, years ago, the C++ compiler on the RPI system supported inlining and using of neon instructions, but the current compiler chain fails to do so. The use of the neon instruction would make a difference of probably around 10 %
Op di 10 dec. 2019 om 23:14 schreef andimik notifications@github.com:
Thanks for the new commit.
It's really a bit better on my RPI3, now the counter on left botton is faster and the eti-file contains all service IDs (but is still not errorfree). Screenshots taken with XPADxpert, see https://basicmaster.de/
Before:
[image: image] https://user-images.githubusercontent.com/24510556/70573216-c494eb80-1ba1-11ea-8d59-7e36c4ada636.png
After:
[image: image] https://user-images.githubusercontent.com/24510556/70573330-09b91d80-1ba2-11ea-93f1-32720a394c26.png
In the next days I will get a RPI4 and will test it again.
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/JvanKatwijk/eti-stuff/issues/43?email_source=notifications&email_token=ACCPHQFQPNTBGWWSN4WLRULQYAIDTA5CNFSM4JYQ4T72YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEGRESBA#issuecomment-564283652, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACCPHQGFRYEVMLUM2TQKJPTQYAIDTANCNFSM4JYQ4T7Q .
-- Jan van Katwijk
Yesterday I got my raspberry 4 and have success with an Airspy. It is error-free now.
So it is really a matter of processing although the CPU load is not even 100%!
BTW: I still have to solve a driver issue with RTL Sticks (they don't work on my Raspberry Pi 4 due to incompatible USB driver).
BTW: Despite of all dependencies mentioned in the Qt-DAB
Readme, I also had to install librtlsdr-dev
on Raspbian.
I will also try your latest commit on the RPI 3B.
Thanks again anyway for the optimization.
Hi Andreas
The librtlsdr on Ubuntu requires blacklisting the device, I am surprised that the default one on Raspbian is OK
Anyway, the optimizations done were actually long overdue, so it was good to be triggered to have them done
Op vr 13 dec. 2019 om 08:56 schreef andimik notifications@github.com:
Yesterday I got my raspberry 4 and have success with an Airspy. It is error-free now.
So it is really a matter of processing although the CPU load is not even 100%!
BTW: I still have to solve a driver issue with RTL Sticks (they don't work on my Raspberry Pi 4 due to incompatible USB driver).
BTW: Despite of all dependencies mentioned in the Qt-DAB Readme, I also had to install librtlsdr-dev on Raspbian.
I will also try your latest commit on the RPI 3B.
Thanks again anyway for the optimization.
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/JvanKatwijk/eti-stuff/issues/43?email_source=notifications&email_token=ACCPHQHEC4VM2OL4Y5W5CILQYM54PA5CNFSM4JYQ4T72YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEGZGUIY#issuecomment-565340707, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACCPHQDTTFU5MX4KZSN2OE3QYM54PANCNFSM4JYQ4T7Q .
-- Jan van Katwijk
I close it due to lack of compute power on a Raspberry.
Dear Jan, I've lots of PCs and Laptops running with your great tools. But on my Raspberrry Pi 3B (not +) I've discovered that the eti-cmdline-rtlsdr does not work properly (no matter if I define a manual gain). eti-cmdline-rawfiles works, indeed.
At the start the fibquality is 100 but after a few seconds it gets less and will end at 0. At the same time the CPU load is not much (see screenshot).
On the same RPI3 qtdab works without any problems, even with Protection level 4A (used in Slovenia).