Oo dear.
Just testing out new system. Server client mode.
Server: tinkerboard2, Arbmian Jammy arm64 (ubuntu 22).
Client: Linux mint 21.2. kstars 3.6.8 everywhere.
3100 ? S 2:15 indiserver -p 7624 -m 100 -v -f /tmp/indiFIFO
3102 ? Sl 1:24 indi_altair_ccd
3104 ? S 0:01 indi_myfocuserpro2_focus
3361 ? S 0:00 indi_ieq_telescope

Altair 26C, iOptron Az Mount pro (alt az mount) with wifi connection, myfocuserpro2.
I requested a sequence for 200x 10s exposure and was working fine. Interestingly kstars crashed after taking 200th frame.
No messages on server. Maybe kernel error/ power issue.
Anyone else have similar problem or is it just my cabling ?
Nick

: org.kde.kstars.indi: Altair AA26CTEC : "[DEBUG] Exposure complete "
org.kde.kstars.indi: Altair AA26CTEC : "[DEBUG] Uploading file. Ext: fits, Size: 51891840, sendImage? Yes, saveImage? No "
Dispatch command error(-1): INDI: Could not find property CCD_EXPOSURE in Altair AA26CTEC
<setNumberVector device="Altair AA26CTEC" name="CCD_EXPOSURE" state="Ok" timeout="60" timestamp="2024-01-27T17:18:01">
<oneNumber name="CCD_EXPOSURE_VALUE">
0
org.kde.kstars.indi: Altair AA26CTEC : "[DEBUG] BLOB transfer took 0.00331277 seconds "
</oneNumber>
</setNumberVector>
kstars: ./libs/indidevice/basedevice.cpp:902: const string& INDI::BaseDevice::messageQueue(size_t) const: Assertion `index < d->messageLog.size()' failed.
Aborted (core dumped)

Ok I increased the supply voltage from 12V to 12,6V and it seems more stable. I was also getting download timeouts on frames before.
Just ran a 200 frame sequence and it worked fine this time.
All the kit (including arm board) should work fine up to 15V.
Hope that's it . Nothing worse than going to bed only to find your system crashed out on frame 2 !
N