INDI uses the native Linux and macOS drivers from ZWO, which are designed to support all ZWO cameras, filter wheels and the focuser. If any problems connecting to ZWO hardware are seen then it most certainly is due to those drivers. I believe a few months ago there were driver issues which ZWO fortunately solved quickly.
The USB2 issues I mentioned above are not ZWO driver or INDI software issues but firmware issues in the camera. That firmware doesn't implement the USB2 standard correctly which causes issues using them on all modern operating systems since all of them enforce the correct use of the USB2 protocol now..ZWO have published a patch for those cameras which never worked for me though I did read several success stories online.
Not sure if this answers your question.
Clear skies, Wouter
It is well known that the ASI120MM/MC (USB2) cameras don't work well with modern operating systems. You need to use ASI120MM/MC-S (USB) cameras, which work well.
brew edit kstars
worked like a charm.
I use homebrew for almost all software on macOS and therefore for KStars as well. The only time I do not use it is when the package is not available via homebrew, which doesn't happen often. It usually works very well for me and now I know how to solve checksum issues as well if they ever happen again.
I am trying to install KStars 3.6.2 on macOS via homebrew and get a checksum mismatch. Can someone fix that please?
$> brew update && brew upgrade --greedy && brew cleanup; mamba update --all -y Already up-to-date. ==> Upgrading 1 outdated package: kstars 3.6.1 -> 3.6.2 ==> Upgrading kstars ==> Downloading https://www.indilib.org/jdownloads/kstars/kstars-3.6.2.dmg ######################################################################## 100.0% ==> Purging files for version 3.6.2 of Cask kstars Error: kstars: SHA256 mismatch Expected: d179cbfb95617932146fad180fcaff920c5fed9416a0a0ac8a8782c748758ba2 Actual: 70c52ac585bd43c5967cb072150c3638110421acab72e5826c8fb63a9dca5ffc File: /Users/wouter/Library/Caches/Homebrew/downloads/c02208c5f813a8bce6c22884ddbdbba7e0db622ca48d1e43509073047ff15fa8--kstars-3.6.2.dmg To retry an incomplete download, remove the file above.
The info on how to get INDI for Raspbian is outdated. Simply use
wget -O - https://www.astroberry.io/repo/key | sudo apt-key add - sudo su -c "echo 'deb https://www.astroberry.io/repo/ bullseye main' > /etc/apt/sources.list.d/astroberry.list" sudo apt update sudo apt install indi-full kstars-bleeding
$ kstars org.kde.kstars: Failed to create local astrometry directory Call to writableLocation without an application-based location. org.kde.kstars: Welcome to KStars 3.6.0 Stable org.kde.kstars: Build: 2022-08-27T18:31:54Z org.kde.kstars: OS: "debian" org.kde.kstars: API: "arm64-little_endian-lp64" org.kde.kstars: Arch: "arm64" org.kde.kstars: Kernel Type: "linux" org.kde.kstars: Kernel Version: "5.15.61-v8+" org.kde.kstars: Qt Version: 5.15.2 qt.qpa.xcb: QXcbConnection: XCB error: 148 (Unknown), sequence: 192, resource id: 0, major code: 140 (Unknown), minor code: 20 org.kde.kstars: User DB does not exist. New User DB will be created. org.kde.kstars: Rebuilding User Database org.kde.kstars: Processing "unnamedstars.dat" , HTMesh Level 3 org.kde.kstars: Sky Mesh Size: 512 org.kde.kstars: Loaded DSO catalog file: "unnamedstars.dat" org.kde.kstars: "Star HD20,794 not found." org.kde.kstars: "Star HD98,230 not found." org.kde.kstars: Loaded DSO catalogs. org.kde.kstars: Loading asteroids terminate called after throwing an instance of 'std::runtime_error' what(): Could not open file. Aborted
The focal length of a lens or telescope is independent of the size of the sensor of the camera used. So 200 mm remains 200 mm regardless of if you use a 1 x 1 mm sensor or a 100 x 100 mm sensor. Ekos can indeed compute the new FOV but you need to clear the DSLR info in the imaging tab before you start imaging. There is a trashcan icon that you need to click and then Ekos will ask you for the new info.
There is no proper ADU value for 8 bit since you should not take 8 bit images silly.png For 16 bit many people suggest to have the peak in the middle (which would be around 32000 ADU) but I advice to go much higher (around 55000 or more as long as you don't get saturated pixels) to make the best use of the full dynamic range of the sensor.
Adding to that, why don't you shoot at 16 bit RAW? That is the preferred format for the ASI533MC camera.
What camera do you use? Is it a DSLR or an Astro CMOS camera? If the latter, what offset are you using and are you sure that the offset for the lights and darks is the same?