×

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

Bi-monthly release with minor bug fixes and improvements

ASI120MM ASIGetExpStatus failed

  • Posts: 82
  • Thank you received: 9
INDI Library: 1.2.0
Code $Rev$. Protocol 1.7.
Daily packages from download pages for Raspberry Pi, latest packages from Jasem's PPA for Desktop

kstars-bleeding 5:16.04+r5982.2611~ubuntu16.04.1 amd64 from Jasem's PPA

Kernel: 4.4.0-36-generic #55-Ubuntu SMP Thu Aug 11 18:01:55 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux

I just got a new ASI120MM to replace my QHY5 because of the issues I had with it recently. Unfortunately, the ASI doesn't work with INDI. It is recognizes by Ubuntu and can connect to Ekos on amd64. When starting an exposure however, it gets stuck in an exposure loop:

2016-09-01T14:04:30: StartExposure->setexp : 1.000s
2016-09-01T14:04:30: ASIGetExpStatus failed (0). Restarting exposure...
2016-09-01T14:04:29: StartExposure->setexp : 1.000s
2016-09-01T14:04:29: ASIGetExpStatus failed (0). Restarting exposure...
2016-09-01T14:04:28: StartExposure->setexp : 1.000s
2016-09-01T14:04:28: ASIGetExpStatus failed (0). Restarting exposure...
2016-09-01T14:04:27: StartExposure->setexp : 1.000s
2016-09-01T14:04:27: ASIGetExpStatus failed (0). Restarting exposure...
2016-09-01T14:04:26: StartExposure->setexp : 1.000s
2016-09-01T14:04:26: Setting frame buffer size to 307200 bytes.
2016-09-01T14:04:26: UpdateCCDFrame ASISetROIFormat (640x480, bin 2, type 0)
2016-09-01T14:04:20: StartExposure->setexp : 1.000s
2016-09-01T14:04:20: ASIGetExpStatus failed (0). Restarting exposure...
2016-09-01T14:04:19: StartExposure->setexp : 1.000s
2016-09-01T14:04:18: ASIGetExpStatus failed (0). Restarting exposure...
2016-09-01T14:04:17: StartExposure->setexp : 1.000s
2016-09-01T14:04:17: ASIGetExpStatus failed (0). Restarting exposure...
2016-09-01T14:04:16: StartExposure->setexp : 1.000s
2016-09-01T14:04:16: ASIGetExpStatus failed (0). Restarting exposure...
2016-09-01T14:04:15: StartExposure->setexp : 1.000s
2016-09-01T14:04:07: Toggle Logging Level -- Driver Debug
2016-09-01T14:04:07: Toggle Debug Level -- Driver Debug
2016-09-01T14:04:05: Debug is enabled.
2016-09-01T14:04:02: Device configuration applied.
2016-09-01T14:04:02: Upload settings set to client only.
2016-09-01T14:04:02: Loading device configuration...
2016-09-01T14:04:02: The CCD Temperature is 23.700000
2016-09-01T14:04:02: CCD is online. Retrieving basic data.

On a Raspberry Pi, it doesn't even work with indiserver:

2016-09-01T15:04:47: startup: indiserver -vv indi_asi_ccd
2016-09-01T15:04:47: Driver indi_asi_ccd: pid=888 rfd=3 wfd=6 efd=7
2016-09-01T15:04:47: listening to port 7624 on fd 4
2016-09-01T15:04:47: Driver indi_asi_ccd: sending <getProperties version='1.7'/>

2016-09-01T15:04:47: Driver indi_asi_ccd: stderr EOF
2016-09-01T15:04:47: Driver indi_asi_ccd: restart #1
2016-09-01T15:04:47: Driver indi_asi_ccd: pid=889 rfd=0 wfd=6 efd=7
2016-09-01T15:04:47: Driver indi_asi_ccd: sending <getProperties version='1.7'/>

2016-09-01T15:04:47: Driver indi_asi_ccd: stderr EOF
2016-09-01T15:04:47: Driver indi_asi_ccd: restart #2
2016-09-01T15:04:47: Driver indi_asi_ccd: pid=890 rfd=0 wfd=6 efd=7
2016-09-01T15:04:47: Driver indi_asi_ccd: sending <getProperties version='1.7'/>

2016-09-01T15:04:47: Driver indi_asi_ccd: stderr EOF
2016-09-01T15:04:47: Driver indi_asi_ccd: restart #3
2016-09-01T15:04:47: Driver indi_asi_ccd: pid=891 rfd=0 wfd=6 efd=7
2016-09-01T15:04:47: Driver indi_asi_ccd: sending <getProperties version='1.7'/>

2016-09-01T15:04:47: Driver indi_asi_ccd: stderr EOF
2016-09-01T15:04:47: Driver indi_asi_ccd: restart #4
2016-09-01T15:04:47: Driver indi_asi_ccd: pid=892 rfd=0 wfd=6 efd=7
2016-09-01T15:04:47: Driver indi_asi_ccd: sending <getProperties version='1.7'/>

2016-09-01T15:04:47: Driver indi_asi_ccd: stderr EOF
2016-09-01T15:04:47: Driver indi_asi_ccd: restart #5
2016-09-01T15:04:47: Driver indi_asi_ccd: pid=893 rfd=0 wfd=6 efd=7
2016-09-01T15:04:47: Driver indi_asi_ccd: sending <getProperties version='1.7'/>

2016-09-01T15:04:47: Driver indi_asi_ccd: stderr EOF
2016-09-01T15:04:47: Driver indi_asi_ccd: restart #6
2016-09-01T15:04:47: Driver indi_asi_ccd: pid=894 rfd=0 wfd=6 efd=7
2016-09-01T15:04:47: Driver indi_asi_ccd: sending <getProperties version='1.7'/>

2016-09-01T15:04:47: Driver indi_asi_ccd: stderr EOF
2016-09-01T15:04:47: Driver indi_asi_ccd: restart #7
2016-09-01T15:04:47: Driver indi_asi_ccd: pid=895 rfd=0 wfd=6 efd=7
2016-09-01T15:04:47: Driver indi_asi_ccd: sending <getProperties version='1.7'/>

2016-09-01T15:04:47: Driver indi_asi_ccd: stderr EOF
2016-09-01T15:04:47: Driver indi_asi_ccd: restart #8
2016-09-01T15:04:47: Driver indi_asi_ccd: pid=896 rfd=0 wfd=6 efd=7
2016-09-01T15:04:47: Driver indi_asi_ccd: sending <getProperties version='1.7'/>

2016-09-01T15:04:47: Driver indi_asi_ccd: stderr EOF
2016-09-01T15:04:47: Driver indi_asi_ccd: restart #9
2016-09-01T15:04:47: Driver indi_asi_ccd: pid=897 rfd=0 wfd=6 efd=7
2016-09-01T15:04:47: Driver indi_asi_ccd: sending <getProperties version='1.7'/>

2016-09-01T15:04:47: Driver indi_asi_ccd: stderr EOF
2016-09-01T15:04:47: Driver indi_asi_ccd: restart #10
2016-09-01T15:04:47: Driver indi_asi_ccd: pid=898 rfd=0 wfd=6 efd=7
2016-09-01T15:04:47: Driver indi_asi_ccd: sending <getProperties version='1.7'/>

2016-09-01T15:04:47: Driver indi_asi_ccd: stderr EOF
2016-09-01T15:04:47: Driver indi_asi_ccd: Terminated after #10 restarts.
2016-09-01T15:04:47: good bye

Could this be a hardware issue or does it have to do with the driver/Ekos? indi-asi version is 0.5 on the Pi and 0.5+r2609~201608311818~ubuntu16.04.1
on the desktop.
Sorry for "spamming" the forum with such issues but I really have no luck with INDI lately :D
7 years 6 months ago #9920

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

  • Posts: 171
  • Thank you received: 41
Raspi 1? If yes: I know that issue, reason is: package was built on Raspi 2 or 3, so ARMv7 binary library has been chosen. A rebuilt at Raspi 1 should fix it.
The following user(s) said Thank You: Adam
7 years 6 months ago #9925

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

  • Posts: 82
  • Thank you received: 9
Thanks for your answer :) It is a Pi Zero, so armv6 indeed. Do I have to remove the old driver before installing the new one after the build?
On the other hand, as it is not working with the amd64 driver either, I don't have much hope to also fix the first mentioned issue.
I just read on the ZWO webpage, that their USB3.0 cameras are recommended for Mac and Linux. I don't know about other countries, but here in Germany, they sell two different versions: the USB2.0 version (ASI120MM) and the USB3.0 version (ASI120MM-S). On the devices page here, it says that the drivers have been tested with the ASI120MM, which would be the unrecommended USB2.0 version, is that true? If not, it would maybe be better to change the description there to prevent people from running into issues :cheer:
7 years 6 months ago #9932

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

  • Posts: 712
  • Thank you received: 174
Adam, it is actually hardware issue, some ASI USB 2.0 cameras don't work with some older Mac USB host controllers. There is no difference in the driver/SDK, it is libusb based code. Peter
7 years 6 months ago #9933

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

  • Posts: 82
  • Thank you received: 9
Ok, I see. But how about Linux?
Actually, the first mentioned issue seems to be fixed with today's version of the asi driver which seems to respect SDK changes. The camera works fine now locally with Ekos on amd64. But I am stil interested in whether this is just luck and the USB2.0 cameras by ZWO are rather incompatible with Linux in general.
I have never build INDI or drivers from source before, do I have to remove the old drivers and INDI on the Pi first?
Anyway, thanks for all your help! I am really amazed by the support here and how nice people are :cheer:
Last edit: 7 years 6 months ago by Adam.
7 years 6 months ago #9935

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

  • Posts: 171
  • Thank you received: 41
I'm using 120MM and 120MC USB 2 versions with Fedora 24, no issues for quite some time. Nowadays it also works fine with Raspi one.
7 years 6 months ago #9936

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

  • Posts: 82
  • Thank you received: 9
Ok, thanks a lot! I will try it with the Pi again then. Is it enough to compile the driver or do I also have to recompile libindi? Because my other camera works fine with the packaged libindi.
7 years 6 months ago #9937

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

  • Posts: 712
  • Thank you received: 174
It is enough to recompile the driver, I just hope that ASI SDK is compiled for ARM6 and not ARM7. Peter
The following user(s) said Thank You: Adam
7 years 6 months ago #9938

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

  • Posts: 82
  • Thank you received: 9
Thanks! It works now! There is even a version for armv5 in the repo :)
Sometimes, at lower exposure times and higher frame rates, the server seems to freeze however and streaming often doesn't work when connected remotely, but that's something I can live with :)
7 years 6 months ago #9939

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

  • Posts: 82
  • Thank you received: 9
Just a little update concerning the "ASIGetExpStatus failed" error and the resulting exposure loop: It turned out that not the recent driver update fixed the problem, but flashing the "compatible" version of the ASI120MM firmware using their Windows only firmware update tool. Just in case someone has a similar issue ;)
The following user(s) said Thank You: nMAC
7 years 6 months ago #9961

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

  • Posts: 456
  • Thank you received: 76

Could you explain this a bit more please? Do you mean flash the FW on the camera?


Update: Tried it but still have the problem...

UPDATE2: Like you said, I flashed the camera again with the ASI120MM-compatible.iic firmware this time and now its working!!! Not sure why this suddenly happened today. I've been using this camera for about 1 year. I never touched the firmware

Thanks,
Derek
Last edit: 7 years 5 months ago by Derek.
7 years 5 months ago #10980

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

Time to create page: 1.063 seconds