I have the ASI462MC. I have not tried it on Astroberry. I have it working in Windows 10. But at first I could not get it to work in Firecapture 2.6 in Windows 10. It turns new Firecapture 2.7 beta has the latest ZWO drivers integrated into the program. It works fine with the 462. An alternate solution listed in another forum is to replace the driver or SDK in the Firecapture 2.6 folder with the newest one from ZWO. Can’t remember the details.
I don’t know if this new 2.7 version is available for the pi. I don’t know if the pi version has the drivers integrated into the program where you could swap in the latest INDI version. But it is something you might want to look into.
Last edit: 1 year 8 months ago by Tim Roske. Reason: Clarification
Got this camera a couple of days ago and have no end of issues trying to get it to play nice on a raspberry pi 3b
In ocapture I see `(ZWASI2)` in the camera menu when it's connected, however on clicking it gives the error "Unable to connect camera"
In firecapture I click "ZWO" and get "The selected camera could not be started"
I've managed to get images from it in phd2 (although obviously that's no use for capturing planetary footage).
I've managed to get images from it in kstars.
However, here's the biggest issue I have. If I try to stream video from the camera in kstars, I can do so successfully at about 0.25s per frame.
Soon after I lower the exposure time below about 0.2s (and therefore ~5fps framerate) the raspberry pi hardlocks
VNC disconnects, the clock stops ticking, any watch commands in terminals start segfaulting, ssh stops responding. I get a bunch of kernel "oops" messages from running processes.
This consistently happens within a few seconds of starting the video stream.
I've read some topics around pi zeros having issues with video streaming that suggest it can be fixed by setting over_voltage=4. However, I've set it as high as 6 and seen no effect. I've also tried underclocking the cpu.
I wonder if maybe the camera is drawing far too much power. The manual for the ASI462MC says that the maximum power usage is 13.9W (!!!). Which is close to 3A at 5V. I find this incredibly hard to believe as even cooled cameras do not use this much with the cooler running. Plus USB2 spec only provides ~500mA and even USB3 only provides ~900mA.
Any ideas what could be going on here? I've attached some backtraces from `/var/log/kern.log`.
Is there any way I can roll back the libASICamera2.so to see if this is a new issue with the SDK?
I don't have any other ZWO cameras but I've tested video streaming with a logitech c920 using the indi_webcam driver and that seems to work fine (albeit with nearly maxed cpu).
Works with oacapture. I set autobandwidth for usb. Also output as set and select a location for output.
Frames per second bit disappointing, maybe because I am running a sata drive on the other usb3 port.
Recently I’ve been working with Torsten to give support to Firecapture on Raspeberry. Please, could you download and try the 2.7 beta 2?. I’ve made it works with the QHY5III462C that’s uses the same sensor.