Radek,
This is really strange.
Initially, I installed Astroberry 2 on RPI3.
aoCapture didn't work giving me "Segmentation fault" error.
Today, I installed Astroberry 2.0.3 on RPI4 - same error!
Yesterday, I installed oaCapture on RPI4 with Stellarmate - same error!!
Strange..
-- Max S
ZWO AM5. RST-135. AZ-GTI. HEQ5. iOptron SkyTracker.
TPO RC6. FRA400. Rokinon 135 and other lenses.
ZWO ASI2600MC. D5500 modified with UVIR clip-in filter.
ZWO ASI120MM Mini x 2. ZWO 30F4 guider. Orion 50mm guider.
ZWO EAF x 3.
Have you tried to run it from fresh image (v2.0.3)? I use it myself for planetary imaging without any issues. If it crashes, it might be unsupported hardware issue and you can consider reporting it to oaCapture developer.
Radek,
Yes. You were right...
It's hardware.
oaCapture works with ZWO camera and focuser attached but as soon as I plug-in the mount it wouldn't start again (silently crashes on start).
Mount: AZ-GTi. EQMod with EQDir USB cable.
FTDI chip in the cable is to blame? It was conflicting with ZWO cameras not long ago until a fix was issued.
EDIT: it's for sure the FTDI chip. If I just plug-in the cable/FTDI alone (no mount attached) - oaCapture refuses to start..
Tried with AB 2.0.3 on RPI3 and RPI4.
-- Max S
ZWO AM5. RST-135. AZ-GTI. HEQ5. iOptron SkyTracker.
TPO RC6. FRA400. Rokinon 135 and other lenses.
ZWO ASI2600MC. D5500 modified with UVIR clip-in filter.
ZWO ASI120MM Mini x 2. ZWO 30F4 guider. Orion 50mm guider.
ZWO EAF x 3.
The workaround is to have the cable disconnected, launch oaCapture and then connect the cable.
The problem cable was made out of this: www.amazon.com/gp/product/B014GZTCC6
The other cable which came with my used HEQ5 doesn't have this issue.
-- Max S
ZWO AM5. RST-135. AZ-GTI. HEQ5. iOptron SkyTracker.
TPO RC6. FRA400. Rokinon 135 and other lenses.
ZWO ASI2600MC. D5500 modified with UVIR clip-in filter.
ZWO ASI120MM Mini x 2. ZWO 30F4 guider. Orion 50mm guider.
ZWO EAF x 3.