Radxa RockPi S V13 512MB + PoE HAT

[ckambiselis]

Radxa RockPi S V13 512MB + PoE HAT with manufactures Debian Bookworm CLI B40 image

Thanks to @adicon's post about installing

# apt install git build-essential python3-pip python3-setuptools python3-dev
# apt install i2c-tools libgpiod-dev python3-libgpiod

$ python3 -m pip config set global.break-system-packages true
$ pip3 install adafruit-blinka gpiozero

before Allsky, I was able to get it running.

Capture, module image overlay, LAN and WLAN dashboard seem to work, Configure Wifi shows networks found but entering the password doesn't seem to connect to the network even though the checkmark appears next to the network, the System menu loads empty in the middle. Will wait until tomorrow to check timelapse, keogram and startrail automatic creation and general stability.

[adicon]

I'm sorry, I use Ethernet (PoE) with DHCP. May I check in my installation if network setting works.

Did you install Radxa Linux official distro or what?

[ckambiselis]

I'm also using Ethernet PoE, just tried different things. Yes I used the official image found on Raxdas webpage, a few months ago I had tried Armbian but had problems while installing and running, not sure if it was because of Armbian or the older Allsky version though.

[adicon]

Ehm! I forgot Radxa Zero 3E has no WiFi.
However, in config menus, there are no errors.

[ckambiselis]

Timelapse creation failed in some way, there is a mp4 file but it is only a few bytes in size and no playback, keogram worked, startrail worked, got a ZWO error message for 5 consecutive fails, but that happened after at least 300 photos, probably something with the daytime pictures since pictures stopped at around 6:30 in the morning, didn't change capture settings compared to the NanoPi I was testing, will set them to something better and test again, also enabled debugging since I forgot to, new update tomorrow.

[ckambiselis]

It's a Rockchip RK3308 based SBC. Not sure in what way you mean being a Raspberry Pi, most of these Chinese companies use the Pi in the name to say that they can be used in a similar way to a Raspberry Pi.

[ckambiselis]

Also, both my posts are not requests to fix anything, they are mostly informative for those looking at using something else than a Raspberry Pi, because of price and size, and maybe someone might think of some easy way to get AllSky to work with other SBCs too.

[ckambiselis]

rockpi s allsky.log

[EricClaeys]

@ckambiselis,
your log file is 25000 lines and I'm not sure what you are hoping I'll do with it.

A few things I noticed:

At 04:13:53 Allsky successfully recovered from:

*** capture_ZWO: ERROR: Maximum number of consecutive errors of 5 reached; capture program exited.

I'll have to think about not showing that error in the WebUI when Allsky recovers from it.
You can ignore that error.

---

Every time Allsky restarts you're getting:

sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper
sudo: a password is required

This indicates "sudo" is failing but I can't determine if it's actually causing any problems.

---

Every image gives an error like this:

*** WARNING: Time to take exposure (72.5 sec) differs from requested exposure time (60.0 sec) by 12.2 sec, threshold=12.0 sec

This could be a camera problem, a USB problem, or an oddity with your device.

---

It appears you are telling Allsky to upload your startrails but you haven't specified where it should go, e.g., local Website, remote Website, or remote Server. You'll need to fix it in the WebUI.

endOfNight.sh: ===== Startrails complete
...
 *** generateForDay.sh ERROR: '--upload' specified but nowhere to upload!

---

Something is killing Allsky shortly after timelapse creation starts. This is most likely because the resolution of your camera (3096x2080) high and timelapse creating is taking too much CPU time, so the operating system is killing it. The best way to fix that is to shrink the timelapse via the Timelapse `Width` and `Height` settings. Try 1/2 resolution: 1548 x 1040.

2025-01-17T06:17:38.842987+00:00 rock-pi-s allsky[46096]: endOfNight.sh: ===== Generating Timelapse for 20250116
...
2025-01-17T06:18:20.659729+00:00 rock-pi-s allsky[39694]: capture_ZWO: Got SIGTERM to exit.

[ckambiselis]

The reason of the 25000 lines is because I noticed it had stopped saving pictures at around 6:15 in the morning, both times I tested and had to enable debugging before going to sleep, sorry about that.

About the sudo fail, the debian image came preconfigured with this "rock" user and I use it's password for sudo commands, so I'm not sure why it would fail either, the only thing I noticed giving an error for sudo (on the other device at least) is the throttle status in the System menu.

The exposure time error, if a hardware error, is probably the SBCs USB port, it only has USB 2.0, since the exact same camera and cable was used on the other SBC I'm testing and that one is not giving that error. Also noticed that it started happening right after the "capture_ZWO: ERROR..." and AllSky restarting, maybe the SoC overheating, not sure what's its temp since the System menu is blank, I'll throw it outside and check again.

Forgot to disable startrail uploading, my mistake, since all uploads should have been disabled.

Timelapse failing I suspected it was a problem with the SoC not being powerfull enough, it only has a Cortex-A35 at 1Ghz and the 512MB RAM being too little. But I would have expected the capture to continue anyway, since daytime capture and save is enabled, I got the log file in the afternoon when I came from work, and the Web UI did open without needing to restart the SBC or anything like that.