I have an Altair AA 183MM Pro, that I bought specifically to use with indi. Unfortunately, I haven't been able to use it properly, as I often need to reboot something (either the driver or the indiserver or the ekos indi client crash or become unusable).
Anyway, let start with a bug I can easily reproduce.
Whenever I launch indiserver with indi_altair_ccd driver alone:
indserver -vvv indi_altair_ccd
I get a very weird behaviour after I have launched an acquisition, on the client side, I basically end-up with a completely blank client (and of course never manage to get the nice image pop-up as it works with the asi driver for zwo ccd):
Here are some logs from the driver logs:INFO 37.003239 sec : Session log file /home/user/.indi/logs/2021-12-30/indi_altair_ccd/indi_altair_ccd_22:24:21.log
INFO 38.421031 sec : Session log file /home/user/.indi/logs/2021-12-30/indi_altair_ccd/indi_altair_ccd_22:24:21.log
DEBUG 44.505031 sec : Attempting to open Altair AA183MPRO with ID tp-2-19-5840-3466 using SDK version: 49.18914.20210510
DEBUG 45.058517 sec : Hardware ROI supported.
DEBUG 45.058677 sec : ST4 guiding enabled.
DEBUG 45.087033 sec : Using default recorder (SER)
DEBUG 45.087191 sec : Using default encoder (RAW)
DEBUG 45.087719 sec : maxSpeed: 3 preview: 4 still: 4 maxFanSpeed 2
DEBUG 45.087794 sec : Exposure Time Range (us): Min 264 Max 1000000000 Default 10000
DEBUG 45.087856 sec : Binning 1 rc: 0
INFO 45.087905 sec : Altair AA183MPRO is online. Retrieving basic data.
DEBUG 45.092268 sec : Max bit depth: 12
DEBUG 45.092361 sec : Mono camera detected.
DEBUG 45.092387 sec : OPTION_RAW 1. rc: Operation successful
DEBUG 45.159527 sec : OPTION_BITDEPTH 1. rc: Operation successful
DEBUG 45.159685 sec : Bits Per Pixel: 16 Video Mode: Mono 16-bit
DEBUG 45.159746 sec : Resolution #1: 5440 x 3648
DEBUG 45.159800 sec : Resolution #2: 4096 x 2160
DEBUG 45.159851 sec : Resolution #3: 2736 x 1824
DEBUG 45.159902 sec : Resolution #4: 1824 x 1216
DEBUG 45.159951 sec : Fan is On
DEBUG 45.160661 sec : Camera snap support: True
DEBUG 45.160720 sec : Trigger mode: 0
DEBUG 45.160767 sec : Setting trigger mode to software...
DEBUG 45.161677 sec : Dual Conversion Gain 0 rc: -2147467263
DEBUG 45.161770 sec : Exposure Auto Gain Control. Min: 100 Max: 5000 Default: 100
DEBUG 45.161826 sec : Contrast Control: 0
DEBUG 45.161874 sec : Hue Control: 0
DEBUG 45.162086 sec : Saturation Control: 0
DEBUG 45.162144 sec : Brightness Control: 0
DEBUG 45.162194 sec : Gamma Control: 100
DEBUG 45.162241 sec : Speed Control: 3
DEBUG 45.168516 sec : Frame Rate Limit 0 rc: 0
DEBUG 45.168635 sec : Allocating Frame Buffer...
DEBUG 45.169014 sec : Pixel format 0 is supported by SER recorder.
DEBUG 45.169079 sec : Pixel format 0 is supported by RAW encoder.
DEBUG 45.375244 sec : Event 0X01
DEBUG 45.385609 sec : Event 0X01
DEBUG 45.432281 sec : Event 0X01
DEBUG 45.436362 sec : Event 0X01
DEBUG 45.440320 sec : Event 0X01
DEBUG 45.443120 sec : Starting event callback in push mode.
DEBUG 49.779226 sec : Starting exposure: 5000000 us @ 1824 x 1216
DEBUG 51.727946 sec : Event 0X01
INFO 51.728119 sec : Taking a 5 seconds frame...
WARNING 51.728178 sec : Failed to snap exposure. Error: Unexpected failure. Switching to regular exposure...
DEBUG 56.816728 sec : New download estimate 89 msand from the driver verbose output:
I tried changing the auto-exposure (enabled by default ?) in the controls tab.
I also played with the resolution option, but I got weird behaviour ranging from, getting an image after a very long time, to driver disconnection + getting the client interface reseted for the camera.
Nothing more than the previous logs are shown in those cases unfortunately... It is really a shame that the driver is that bad with regard to the consistent behaviour I have with ZWO ASi cameras.
Client is on a x86 laptop and server/driver on a 4GB SBC ~30% more powerful than a rasbperrypi4 (rock64pro from pine64). I tried with 8bit and lowest resolution but didn't get better results unfortunately. But the outcome seems more or less random, I will try to reduce the potential source of errors in my next attempt, IE, much better network, changing usb cable, etc...