My ZWO ASI120MM is actually the mini version with USB2 only. I've seen a few issues posted on various forums related to the ZWO ASI120MM-S . I wonder if you are seeing the same problems with your 120MC-S?
Hi Tom. No I've not noticed any issues with skipping frames with the 120MM. I have it set as 8 bit though. I had to do that in Windoze days too.
I updated my Astroberry from 2.02 to 2.03 upgrading Kstars at the same time and ran into the problem with my ASI cameras (and ASI EFW) not showing up when I launch KStars/EKOS from the PI4 or from the INDI WebManager
My hardware version is:
Hardware : BCM2835
Revision : c03111
Serial : 100000004632cd93
Model : Raspberry Pi 4 Model B Rev 1.1
lsusb would no longer show anything from the command line - zip
usb-devices was the same. However sudo lsusb or sudo usb-devices did work.
Anyway I did run sudo rpi-update e1050e94821a70b2e4c72b318d6c6c968552e9a2 and reboot. ASI devices now recognised again and everything shows up ok in lsusb
astroberry@astroberry:~ $ lsusb
Bus 002 Device 005: ID 03c3:183e
Bus 002 Device 004: ID 045b:0210 Hitachi, Ltd
Bus 002 Device 003: ID 045b:0210 Hitachi, Ltd
Bus 002 Device 002: ID 05e3:0616 Genesys Logic, Inc. hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 004: ID 0403:6001 Future Technology Devices International, Ltd FT232 Serial (UART) IC
Bus 001 Device 010: ID 03c3:120c
Bus 001 Device 009: ID 03c3:1f01
Bus 001 Device 008: ID 04b4:6572 Cypress Semiconductor Corp.
Bus 001 Device 007: ID 0403:6001 Future Technology Devices International, Ltd FT232 Serial (UART) IC
Bus 001 Device 006: ID 045b:0209 Hitachi, Ltd
Bus 001 Device 005: ID 045b:0209 Hitachi, Ltd
Bus 001 Device 003: ID 05e3:0610 Genesys Logic, Inc. 4-port hub
Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
For reference I am running the following hardware
ZWO ASI 183MM, ASI120MM, ASI 5 position filter wheel (the latter 2 connected to the integral hub on the 183) and Lakeside focuser connected to a powered USB3 hub on the mount. This runs down an active USB3 cable to the PI4 straight into the USB3 socket.
The EQMOD cable runs direct from the HEQ5Pro to the PI4 USB2 socket. So two USB cables running to the PI and a relatively simple setup.
I am controlling the PI4 via 1G Ethernet connection so no wireless involved. I also have a bug with Windows KStars which I've already reported to Jasem.
I have found that the Lakeside Driver crashes if you specify an initial step size greater than 999
I am using a Pi4 with all the latest updates to today 01/02/2020 and my ZWO ASI120MM works ok.
However my ZWO ASI183MC-PRO, although recognised, when I try to connect to it using oacapture or CCDciel crashes both applications.
I'm not sure where the crash logs are as /var/logs/messages does not contain any log of the crash. Happy to submit logs if you can tell me where they are.