Problems on RPi400

[pa3byv]

I was pleasantly surprised by the announcement of the Linux Transceiver. Thought it would be a welcome addition to my arsenal. Installed it according to the description on an Raspberry Pi 400 with a PiSDR card. It started with the opening screen, but didn't get any further after doing the configuration. Redid it on another SD card with latest Buster installed, same problem, but now I got as far as a spectrum and waterfall with multiple symmetrical peaks, updating once every two seconds. Burned a new SD card with 21-03-04 Buster, again same result. Used two different Pluto's (both rev B), and USB-Dongle. Audio loop worked, although with an annoying hum, RF loop didn't. Also the settings for the frequencies were lost every time at restart of the app. On install I didn't get any errors, only warnings about Jack daemon not installed. At startup also warnings that Jack server didn't startup. But Alsa worked, so probably shouldn't be a problem Any idea what might be wrong?

73 Poll

[dj0abr]

Hello Poll,

I'm not sure what the PI400 is, but what I read it is a PI-4 with a keyboard. So it should be compatible.

if the Screen updates only every 2 seconds, there could be a problem with system performance, usually it updates multiple times per second.

The Jack-warning is normal, I can see it too, but no problem.

• Could you please send me a screenshot of "htop" when the software is running, and
• your config file, which is loacted in the home folder /home/pi and has the name: trx.cfg
• what OS did you install? I know its working fine with Raspi-OS 32 or 64, but does not work with the Ubuntu version offered for the Raspberry (all gets very, very slow).

vy 73 Kurt

[pa3byv]

Dear Kurt,

Thank you for replying, and thank you for writing this software. I know it must have taken a lot of your time and expertise.

Today I tried again, and had the same failures and also (forgot to report earlier) buffer full warnings, as you can see in the accompanying pictures and files.

But, I also tried a Pluto+, which did work! So the problem seems to be with both of my Pluto rev.B’s.

The Pluto’s run different fw, but all with F5OEO fw on it. One Pluto runs Perseverance 2202, one runs 2808 and I believe the Pluto+ is also running on 2808.

So, with the Pluto+ running you can see, that CPU use is actually pretty moderate, below 50% on all cores. With the Pluto-B, that is not running well, the cores run very low, so the software seems not to run its normal speed. Also, that is when you see the strange peaks and the 2-second update interval.

All three Pluto’s work correctly in normal operation. The first Pluto-B, also used in this test, is in daily use on QO-100 in SSB with SDRConsole.

The other Pluto-B and the Pluto+ are in daily use for DATV on the WB-TP, directly from a PC or from the Portsdown 4.

The RPI400 is indeed a RPi4, 4GB, on a larger flatter board to fit in a keyboard. It has one USB-2 less and and the 3.5 mm V/A connector is absent. Otherwise the same thing.

I hope the files and pictures give you enough information, otherwise please feel free to ask for more info. As the picture files are to big I will be sending them in two emails.

73

Poll, PA3BYV

Op 8 jun. 2021, om 18:04 heeft Kurt Moraw @.***> het volgende geschreven:

Hello Poll,

I'm not sure what the PI400 is, but what I read it is a PI-4 with a keyboard. So it should be compatible.

if the Screen updates only every 2 seconds, there could be a problem with system performance, usually it updates multiple times per second.

The Jack-warning is normal, I can see it too, but no problem.

Could you please send me a screenshot of "htop" when the software is running, and your config file, which is loacted in the home folder /home/pi and has the name: trx.cfg what OS did you install? I know its working fine with Raspi-OS 32 or 64 but, but does not work with the Ubuntu version offered for the Raspberry (all get very, very slow). vy 73 Kurt

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/dj0abr/QO100_Transceiver/issues/1#issuecomment-856899514, or unsubscribe https://github.com/notifications/unsubscribe-auth/AUMZBW4I4HE55CEV7KPLKQTTRY5SXANCNFSM46J4EX4Q.

[pa3byv]

Second zip

Op 8 jun. 2021, om 18:04 heeft Kurt Moraw @.***> het volgende geschreven:

Hello Poll,

I'm not sure what the PI400 is, but what I read it is a PI-4 with a keyboard. So it should be compatible.

if the Screen updates only every 2 seconds, there could be a problem with system performance, usually it updates multiple times per second.

The Jack-warning is normal, I can see it too, but no problem.

Could you please send me a screenshot of "htop" when the software is running, and your config file, which is loacted in the home folder /home/pi and has the name: trx.cfg what OS did you install? I know its working fine with Raspi-OS 32 or 64 but, but does not work with the Ubuntu version offered for the Raspberry (all get very, very slow). vy 73 Kurt

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/dj0abr/QO100_Transceiver/issues/1#issuecomment-856899514, or unsubscribe https://github.com/notifications/unsubscribe-auth/AUMZBW4I4HE55CEV7KPLKQTTRY5SXANCNFSM46J4EX4Q.

[pa3byv]

And to answer your last question: 2021-03-04-raspios-buster-armhf.

73 Poll

Op 8 jun. 2021, om 21:17 heeft Poll van der Wouw PA3BYV @.***> het volgende geschreven:

Dear Kurt,

Thank you for replying, and thank you for writing this software. I know it must have taken a lot of your time and expertise.

Today I tried again, and had the same failures and also (forgot to report earlier) buffer full warnings, as you can see in the accompanying pictures and files.

But, I also tried a Pluto+, which did work! So the problem seems to be with both of my Pluto rev.B’s.

The Pluto’s run different fw, but all with F5OEO fw on it. One Pluto runs Perseverance 2202, one runs 2808 and I believe the Pluto+ is also running on 2808.

So, with the Pluto+ running you can see, that CPU use is actually pretty moderate, below 50% on all cores. With the Pluto-B, that is not running well, the cores run very low, so the software seems not to run its normal speed. Also, that is when you see the strange peaks and the 2-second update interval.

All three Pluto’s work correctly in normal operation. The first Pluto-B, also used in this test, is in daily use on QO-100 in SSB with SDRConsole.

The other Pluto-B and the Pluto+ are in daily use for DATV on the WB-TP, directly from a PC or from the Portsdown 4.

The RPI400 is indeed a RPi4, 4GB, on a larger flatter board to fit in a keyboard. It has one USB-2 less and and the 3.5 mm V/A connector is absent. Otherwise the same thing.

I hope the files and pictures give you enough information, otherwise please feel free to ask for more info. As the picture files are to big I will be sending them in two emails.

73

Poll, PA3BYV

> Op 8 jun. 2021, om 18:04 heeft Kurt Moraw ***@***.*** ***@***.***>> het volgende geschreven: > > > Hello Poll, > > I'm not sure what the PI400 is, but what I read it is a PI-4 with a keyboard. So it should be compatible. > > if the Screen updates only every 2 seconds, there could be a problem with system performance, usually it updates multiple times per second. > > The Jack-warning is normal, I can see it too, but no problem. > > Could you please send me a screenshot of "htop" when the software is running, and > your config file, which is loacted in the home folder /home/pi and has the name: trx.cfg > what OS did you install? I know its working fine with Raspi-OS 32 or 64 but, but does not work with the Ubuntu version offered for the Raspberry (all get very, very slow). > vy 73 > Kurt > > — > You are receiving this because you authored the thread. > Reply to this email directly, view it on GitHub , or unsubscribe . >

[dj0abr]

I'm not sure what happens on your system.

So I did it from scratch using your image. I have documented each single step here: https://wiki.amsat-dl.org/doku.php?id=en:plutotrx:raspi

After this procedure I took an image of the running system, the download link is in above description.

I have tested it with an older pluto Rev.B, and a brand new Rev.C and also with the default firmware as well as the F5OEO firmware.

(I did not receive the files which should be included in your emails, please send them again, thank you)

[pa3byv]

Forwarding again with the same .zip file to see if it is a send or a receive problem.

73, Poll

Begin forwarded message:

From: Poll van der Wouw PA3BYV @.> Date: 8 June 2021 at 21:17:35 CEST To: dj0abr/QO100_Transceiver @.> Subject: Re: [dj0abr/QO100_Transceiver] Problems on RPi400 (#1)

Dear Kurt,

Thank you for replying, and thank you for writing this software. I know it must have taken a lot of your time and expertise.

Today I tried again, and had the same failures and also (forgot to report earlier) buffer full warnings, as you can see in the accompanying pictures and files.

But, I also tried a Pluto+, which did work! So the problem seems to be with both of my Pluto rev.B’s.

The Pluto’s run different fw, but all with F5OEO fw on it. One Pluto runs Perseverance 2202, one runs 2808 and I believe the Pluto+ is also running on 2808.

So, with the Pluto+ running you can see, that CPU use is actually pretty moderate, below 50% on all cores. With the Pluto-B, that is not running well, the cores run very low, so the software seems not to run its normal speed. Also, that is when you see the strange peaks and the 2-second update interval.

All three Pluto’s work correctly in normal operation. The first Pluto-B, also used in this test, is in daily use on QO-100 in SSB with SDRConsole.

The other Pluto-B and the Pluto+ are in daily use for DATV on the WB-TP, directly from a PC or from the Portsdown 4.

The RPI400 is indeed a RPi4, 4GB, on a larger flatter board to fit in a keyboard. It has one USB-2 less and and the 3.5 mm V/A connector is absent. Otherwise the same thing.

I hope the files and pictures give you enough information, otherwise please feel free to ask for more info. As the picture files are to big I will be sending them in two emails.

73

Poll, PA3BYV

Op 8 jun. 2021, om 18:04 heeft Kurt Moraw @.***> het volgende geschreven:

Hello Poll,

I'm not sure what the PI400 is, but what I read it is a PI-4 with a keyboard. So it should be compatible.

if the Screen updates only every 2 seconds, there could be a problem with system performance, usually it updates multiple times per second.

The Jack-warning is normal, I can see it too, but no problem.

Could you please send me a screenshot of "htop" when the software is running, and your config file, which is loacted in the home folder /home/pi and has the name: trx.cfg what OS did you install? I know its working fine with Raspi-OS 32 or 64 but, but does not work with the Ubuntu version offered for the Raspberry (all get very, very slow). vy 73 Kurt

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or unsubscribe.

[pa3byv]

Dear Kurt,

I have forwarded the same message including the .zip files with a copy to myself and received the zip file with the message. This is the second zip file. Please let me know if you didn't receive it. If so, I probably need to send it to your other email address.

73 Poll

Begin forwarded message:

From: Poll van der Wouw PA3BYV @.> Date: 8 June 2021 at 21:18:16 CEST To: dj0abr/QO100_Transceiver @.> Subject: Re: [dj0abr/QO100_Transceiver] Problems on RPi400 (#1)

Second zip

Op 8 jun. 2021, om 18:04 heeft Kurt Moraw @.***> het volgende geschreven:

Hello Poll,

I'm not sure what the PI400 is, but what I read it is a PI-4 with a keyboard. So it should be compatible.

if the Screen updates only every 2 seconds, there could be a problem with system performance, usually it updates multiple times per second.

The Jack-warning is normal, I can see it too, but no problem.

Could you please send me a screenshot of "htop" when the software is running, and your config file, which is loacted in the home folder /home/pi and has the name: trx.cfg what OS did you install? I know its working fine with Raspi-OS 32 or 64 but, but does not work with the Ubuntu version offered for the Raspberry (all get very, very slow). vy 73 Kurt

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or unsubscribe.

[pa3byv]

Hi Kurt,

I was able to get one of the Pluto-B’s working: First installed the official AD fw version 0.33, but that didn’t cut it. Then I removed all leftover files and directories from previous DATV patches from /mnt/jffs2/ and now it came to life! So, although I’m not sure what exactly is to blame, it certainly isn’t your software. Seems to be an incompatibility between a previous patch and your software. I will try to reinstall the -for me necessary- 2202 F5OEO firmware and see what happens.

Vy 73, Poll

Op 9 jun. 2021, om 12:54 heeft Kurt Moraw @.***> het volgende geschreven:

I'm not sure what happens on your system.

So I did it from scratch using your image. I have documented each single step here: https://wiki.amsat-dl.org/doku.php?id=en:plutotrx:raspi https://wiki.amsat-dl.org/doku.php?id=en:plutotrx:raspi After this procedure I took an image of the running system, the download link is in above description.

I have tested it with an older pluto Rev.B, and a brand new Rev.C and also with the default firmware as well as the F5OEO firmware.

(I did not receive the files which should be included in your emails, please send them again, thank you)

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/dj0abr/QO100_Transceiver/issues/1#issuecomment-857595345, or unsubscribe https://github.com/notifications/unsubscribe-auth/AUMZBW4LUICTGE4F7NZFQQ3TR5B4XANCNFSM46J4EX4Q.

[dj0abr]

ok thanks Poll, so no more need for the files.

I have the F5OEO firmware installed because I also stream DATV. This works fine with the transceiver software. Which version of the F5OEO firmware du you use?

vy 73 Kurt

[pa3byv]

I have been using multiple versions of the F5OEO software and also versions of patches by F5UII, so all of them could have left something incompatible. On this particular Pluto-B the latest fw was Perseverance 2202.

73 Poll, PA3BYV