HELP - ASI1600 - RPI3 - ASIGetExpStatus failed (0)

maudy

Hello:

How can the ASIGetExpStatus failed be resolved on RPI3 using Ekos and INDI server?

It was suggested to update to the 120mm-c compatible version using the windows tool. Please help resolve this.

I have been using Ekos successfully with a Canon T6i on my RPI3. It does not matter if the indiserver is running remote on RPI3 - 127.0.0.1 - or local to Ekos.

Running local though, the ASI1600 hub does not find the ASI EFW. Running indiserver remote on RPI3 the ASI EFW is found.

Using a new ASI1600MM-C v3 I am unable to get a single frame, whether it is a preview or scheduled.

Debug is turned on the ASI1600 and an excerpt is of the log follows.

Excerpt:

INFO 5.202128 sec : Session log file /home/pi/.indi/logs/2017-01-21/indi_asi_ccd/indi_asi_ccd_22:$

INFO 5.202262 sec : Upload settings set to client only.

DEBUG 5.202442 sec : Requested CCD Frame is ( 0, 0) (4656 x 3520)

DEBUG 5.202492 sec : UpdateCCDFrame ASISetROIFormat (4656x3520, bin 1, type 0)

DEBUG 5.255528 sec : Setting frame buffer size to 16389120 bytes.

DEBUG 5.255730 sec : UpdateCCDFrame ASISetROIFormat (4656x3520, bin 1, type 0)

DEBUG 5.246331 sec : Setting frame buffer size to 16389120 bytes.

DEBUG 5.246526 sec : UpdateCCDFrame ASISetROIFormat (4656x3520, bin 1, type 0)

DEBUG 5.299397 sec : Setting frame buffer size to 16389120 bytes.

DEBUG 5.299629 sec : UpdateCCDFrame ASISetROIFormat (4656x3520, bin 1, type 2)

DEBUG 5.290327 sec : Setting frame buffer size to 16389120 bytes.

DEBUG 5.290556 sec : UpdateCCDFrame ASISetROIFormat (4656x3520, bin 1, type 2)

DEBUG 5.390950 sec : Setting frame buffer size to 32778240 bytes.

WARNING 5.391542 sec : 16 bit bayer format GRBG it not supported by the SER recorder.

DEBUG 5.391898 sec : Configuration successfully loaded.

DEBUG 5.384632 sec : Setting frame buffer size to 32778240 bytes.

WARNING 5.384728 sec : 16 bit bayer format GRBG it not supported by the SER recorder.

DEBUG 5.384918 sec : Configuration successfully loaded.

WARNING 6.432385 sec : World Coordinate System is enabled. CCD rotation must be set either manually or $

WARNING 6.455092 sec : World Coordinate System is enabled. CCD rotation must be set either manually or $

DEBUG 41.941423 sec : StartExposure->setexp : 10.000s

DEBUG 41.920465 sec : StartExposure->setexp : 10.000s

INFO 41.948078 sec : Taking a 10 seconds frame...

INFO 42.101601 sec : Taking a 10 seconds frame...

DEBUG 52.371764 sec : ASIGetExpStatus failed (0). Restarting exposure...

DEBUG 52.472024 sec : StartExposure->setexp : 10.000s

INFO 52.472308 sec : Taking a 10 seconds frame...

DEBUG 52.685237 sec : ASIGetExpStatus failed (0). Restarting exposure...

DEBUG 52.785550 sec : StartExposure->setexp : 10.000s

INFO 52.785859 sec : Taking a 10 seconds frame...

DEBUG 62.765265 sec : ASIGetExpStatus failed (0). Restarting exposure...

DEBUG 62.865561 sec : StartExposure->setexp : 10.000s

INFO 62.865829 sec : Taking a 10 seconds frame...

DEBUG 66.170600 sec : ASIGetExpStatus failed (0). Restarting exposure...

DEBUG 66.270935 sec : StartExposure->setexp : 10.000s

INFO 66.271203 sec : Taking a 10 seconds frame...

ERROR 73.122929 sec : Exposure failed after 3 attempts.

yang

Hi, do you select "ZWO CCD" both as camera and guider in profile?

maudy

yang wrote:
Hi, do you select "ZWO CCD" both as camera and guider in profile?

Yes.

Ideally my ASI1600mm-c is the CCD, and my ASI224mc-c is the guider.

In this case though the ASI1600 was the only connection plus a USB stick on the RPI3 to attempt debugging.

Sent from my iPhone using Tapatalk

yang

the INDI of old version did have this issue, but it works normally if only select ASI CCD as camera.

It seems tht this problem is fixed in the latest version's INDI, please run git pull to update the code.

maudy

Sorry, we encountered an error while displaying this content. If you're a user, please try again later. If you're an administrator, take a look in your Flarum log files for more information.

yang

you need to check the permission of ASI224, you can run INDI server with super user permission,

and see if ASI224 can be opened.

maudy

yang wrote:
you need to check the permission of ASI224, you can run INDI server with super user permission,

and see if ASI224 can be opened.

Thank you so much for the quick reply.

You were correct, making the indiserver startup as root instead of pi solved the problem.

I did a test run and the update from Jan 23rd to the INDI PPA resolved the ASI1600 issue too.

I think it is all set now.

Sincerely,

Stephen

maudy

yang wrote:
you need to check the permission of ASI224, you can run INDI server with super user permission,

and see if ASI224 can be opened.

One more question, does it make sense that ZWO CCD is only set as CCDs in Ekos INDI settings and not also set as Guider as well?

Current tests indicate that I should only use CCD and then within Ekos pick the camera to use for guiding.

Regards,

Stephen

yang

good news! BTW, does the 99-asi.rules or asi.rules is located in /lib/udev/rules.d or /etc/udev/rules.d,

only in the case it is located in /etc/udev/rules.d, you can open ASI224 without root.

I'm not familiar with the usage of INDI, you'd better ask it in INDI forum.

maudy

yang wrote:
good news! BTW, does the 99-asi.rules or asi.rules is located in /lib/udev/rules.d or /etc/udev/rules.d,

only in the case it is located in /etc/udev/rules.d, you can open ASI224 without root.

I'm not familiar with the usage of INDI, you'd better ask it in INDI forum.

I must have done something thing wrong.

99-asi.rules is in then/lib directory.

Moved to /etc and rebooted and still have issues.

Keeping in /lib and making ensure root is used things seem to be working.

Also, only using CCD and not putting ZWO CCD in guider section for indi always things to work.

Thank you for helping to get this working again.

Sent from my iPhone using Tapatalk