×

INDI Library v2.0.6 is Released (02 Feb 2024)

Bi-monthly release with minor bug fixes and improvements

ZWO ASI462MC [ERROR] Error connecting to the CCD (16) [Fixed with New ASI SDK]

  • Posts: 14
  • Thank you received: 0
As per title, ZWO ASI462MC won't work (previous mount problem resolved by using EQ DIRECT cable) :-(

Camera connects and works fine with FireCapture on the same system - Ubuntu 20.04

Output of lsusb shows this as the device;
<code>Bus 002 Device 010: ID 03c3:462b </code>
Note the name is empty - is that normal?

When I connect with KSTARS I only ever get [ERROR] Error connecting to the CCD (16)

Driver shows as indi_asi_ccd version 7 interface 6

KSTARS 3.4.3 Build: 2020-07-20T13:52:15Z

Any help appreciated.

Roger
Last edit: 3 years 7 months ago by Roger Moffatt.
3 years 7 months ago #57806

Please Log in or Create an account to join the conversation.

  • Posts: 388
  • Thank you received: 17
I just had the same issue with a brand new ZWO ASI533MC Pro. The first try I got the same error (16). I ran lsusb and I also only got the camera number xx533. I then restarted Kstars/Ekos with debugging and logging turned on (I figured I would need to use this to find out where the problem was) and then the camera initialized and worked fine!!

So maybe try again .

ron
3 years 7 months ago #57807

Please Log in or Create an account to join the conversation.

  • Posts: 14
  • Thank you received: 0
Interesting, didn't know I had to restart for the debug option to work? Saw your earlier post and initially didn't seem to make a difference, however now, after enabling debug and restarting, I now get this log;
2020-08-06T02:23:09: startup: /usr/bin/indiserver -v -p 7624 -m 300 -r 0 -f /tmp/indififo2c41788d 
2020-08-06T02:23:09: listening to port 7624 on fd 3
FIFO: start indi_asi_ccd
FIFO: Starting driver indi_asi_ccd
2020-08-06T02:23:09: Driver indi_asi_ccd: pid=112493 rfd=4 wfd=7 efd=8
2020-08-06T02:23:09: Client 5: new arrival from 127.0.0.1:53448 - welcome!
2020-08-06T02:23:09: Driver indi_asi_ccd: snooping on Telescope Simulator.EQUATORIAL_EOD_COORD
2020-08-06T02:23:09: Driver indi_asi_ccd: snooping on Telescope Simulator.TELESCOPE_INFO
2020-08-06T02:23:09: Driver indi_asi_ccd: snooping on Telescope Simulator.GEOGRAPHIC_COORD
2020-08-06T02:23:09: Driver indi_asi_ccd: snooping on Telescope Simulator.TELESCOPE_PIER_SIDE
2020-08-06T02:23:09: Driver indi_asi_ccd: snooping on Rotator Simulator.ABS_ROTATOR_ANGLE
2020-08-06T02:23:09: Driver indi_asi_ccd: snooping on Focuser Simulator.ABS_FOCUS_POSITION
2020-08-06T02:23:09: Driver indi_asi_ccd: snooping on CCD Simulator.FILTER_SLOT
2020-08-06T02:23:09: Driver indi_asi_ccd: snooping on CCD Simulator.FILTER_NAME
2020-08-06T02:23:09: Driver indi_asi_ccd: snooping on SQM.SKY_QUALITY
2020-08-06T02:23:09: Driver indi_asi_ccd: *** buffer overflow detected ***: terminated
2020-08-06T02:23:09: Driver indi_asi_ccd: stderr EOF
Child process 112493 died
2020-08-06T02:23:09: Driver indi_asi_ccd: Terminated after #0 restarts.
FIFO: stop indi_asi_ccd
dp->name: indi_asi_ccd - tDriver: indi_asi_ccd
FIFO: start indi_asi_ccd
FIFO: Starting driver indi_asi_ccd
2020-08-06T02:23:20: Driver indi_asi_ccd: pid=112923 rfd=4 wfd=8 efd=9
2020-08-06T02:23:20: Driver indi_asi_ccd: snooping on Telescope Simulator.EQUATORIAL_EOD_COORD
2020-08-06T02:23:20: Driver indi_asi_ccd: snooping on Telescope Simulator.TELESCOPE_INFO
2020-08-06T02:23:20: Driver indi_asi_ccd: snooping on Telescope Simulator.GEOGRAPHIC_COORD
2020-08-06T02:23:20: Driver indi_asi_ccd: snooping on Telescope Simulator.TELESCOPE_PIER_SIDE
2020-08-06T02:23:20: Driver indi_asi_ccd: snooping on Rotator Simulator.ABS_ROTATOR_ANGLE
2020-08-06T02:23:20: Driver indi_asi_ccd: snooping on Focuser Simulator.ABS_FOCUS_POSITION
2020-08-06T02:23:20: Driver indi_asi_ccd: snooping on CCD Simulator.FILTER_SLOT
2020-08-06T02:23:20: Driver indi_asi_ccd: snooping on CCD Simulator.FILTER_NAME
2020-08-06T02:23:20: Driver indi_asi_ccd: snooping on SQM.SKY_QUALITY
2020-08-06T02:23:20: Driver indi_asi_ccd: *** buffer overflow detected ***: terminated
2020-08-06T02:23:21: Driver indi_asi_ccd: stderr EOF
2020-08-06T02:23:21: Driver indi_asi_ccd: Terminated after #0 restarts.
Child process 112923 died
FIFO: stop indi_asi_ccd
dp->name: indi_asi_ccd - tDriver: indi_asi_ccd
FIFO: start indi_asi_ccd
FIFO: Starting driver indi_asi_ccd
2020-08-06T02:23:25: Driver indi_asi_ccd: pid=112938 rfd=4 wfd=8 efd=9
2020-08-06T02:23:25: Driver indi_asi_ccd: snooping on Telescope Simulator.EQUATORIAL_EOD_COORD
2020-08-06T02:23:25: Driver indi_asi_ccd: snooping on Telescope Simulator.TELESCOPE_INFO
2020-08-06T02:23:25: Driver indi_asi_ccd: snooping on Telescope Simulator.GEOGRAPHIC_COORD
2020-08-06T02:23:25: Driver indi_asi_ccd: snooping on Telescope Simulator.TELESCOPE_PIER_SIDE
2020-08-06T02:23:25: Driver indi_asi_ccd: snooping on Rotator Simulator.ABS_ROTATOR_ANGLE
2020-08-06T02:23:25: Driver indi_asi_ccd: snooping on Focuser Simulator.ABS_FOCUS_POSITION
2020-08-06T02:23:25: Driver indi_asi_ccd: snooping on CCD Simulator.FILTER_SLOT
2020-08-06T02:23:25: Driver indi_asi_ccd: snooping on CCD Simulator.FILTER_NAME
2020-08-06T02:23:25: Driver indi_asi_ccd: snooping on SQM.SKY_QUALITY
2020-08-06T02:23:25: Driver indi_asi_ccd: *** buffer overflow detected ***: terminated
2020-08-06T02:23:25: Driver indi_asi_ccd: stderr EOF
Child process 112938 died
2020-08-06T02:23:25: Driver indi_asi_ccd: Terminated after #0 restarts.

So basically trapped in a buffer overflow loop.

Clues?

Roger
3 years 7 months ago #57808

Please Log in or Create an account to join the conversation.

  • Posts: 388
  • Thank you received: 17
No clue. My Process was to shut down kstars/ekos, try another USB3.0 port for the camera, ran LSUSB, got same response; tried LSUSB without camera, saw that the xx533 was missing. Went back to original USB 3.0 slot and restarted Kstars/Ekos this time it worked?

sorry no more help than that.
Ron
3 years 7 months ago #57809

Please Log in or Create an account to join the conversation.

The driver is crashing, I will re-trigger the build on 20.04
3 years 7 months ago #57816

Please Log in or Create an account to join the conversation.

  • Posts: 388
  • Thank you received: 17
Is this a camera specific problem or should all ASI cameras update the Indi driver after the build?

thanks,
Ron
3 years 7 months ago #57820

Please Log in or Create an account to join the conversation.

  • Posts: 14
  • Thank you received: 0
OK I've tried the nightly build and am testing on Build: 2020-08-06T10:33:03Z

Behaviour is;

1) Unplug camera, run the ZWO service, get an error message about no ASI camera found as expected
2) Plug in camera, stop the ZWO service and run again, the INDI control panel pops open as expected
3) Camera is named randomly, this time it is ZWO CCD >V
4) Click Connect - get [ERROR] Error connecting to the CCD (16)

So no crashes on the nightly build, but still isn't working. This is one of the most recent ZWO cameras.
3 years 7 months ago #57833

Please Log in or Create an account to join the conversation.

  • Posts: 1957
  • Thank you received: 420
Have you tried ASIStudio on the same Linux system? Dies it work with that?
3 years 7 months ago #57834

Please Log in or Create an account to join the conversation.

  • Posts: 14
  • Thank you received: 0
It works fine with Firecapture on the same system, I don't use ASIStudio. Camera also works fine on my other windows based computers with Firecapture.

But I'll download it and give it a go and report back ...
Last edit: 3 years 7 months ago by Roger Moffatt.
3 years 7 months ago #57836

Please Log in or Create an account to join the conversation.

  • Posts: 14
  • Thank you received: 0
OK, installed ASIStudio, camera works as expected. Re-tried INDI since the installation process added some rules - no change from my previous report. Does not work :-(
3 years 7 months ago #57838

Please Log in or Create an account to join the conversation.

btw, what's the ZWO Service ?
3 years 7 months ago #57871

Please Log in or Create an account to join the conversation.

  • Posts: 14
  • Thank you received: 0
Sorry, maybe my terminology is incorrect - I mean doing this;

KSTARS Tools -> Devices -> Device Manager, select ZWO CCD in the CCD section, click "Run Service" to run "the ZWO service"
3 years 7 months ago #57874

Please Log in or Create an account to join the conversation.

Time to create page: 0.576 seconds