Welcome, Guest
Username: Password: Remember me
20 Aug 2017
INDI development team is happy to announce the release of INDI Library v1.5.0. This new exciting release builds on the maturity of INDI Library and comes with many new supported devices and fixes for existing drivers.
Read More...
  • Page:
  • 1

TOPIC: ASI 120MC failes to expose

ASI 120MC failes to expose 7 months 2 weeks ago #15992

  • emk
  • emk's Avatar Topic Author
  • Offline
  • Fresh Boarder
  • Fresh Boarder
  • Posts: 15
  • Thank you received: 1
Hey,
I'm having problems with my ASI 120MC. It connects just fine and the client is receiving everything fine. But when I try to make an exposure, doesn't matter how long, it fails to get the image from the camera. It also seems to have problems setting the CONTROL parameter like Gain and so on.

My INDI version is 1.3.1+r2850~201702231016~ubuntu16.04.1. The version of the asi driver is 0.5+r2850~201702221347~ubuntu16.04.1. The cam itself is about 3 years old, it worked already sometime last year in autumn.

And here goes the log-file. In sec 42 I started an 1 seconds exposure, it obviously failed and later on, in seconds 112 I tried to change BandWidth and later Gain, it both failed.
The error code 16 sttands for ''ASI_ERROR_GENERAL_ERROR//general error, eg: value is out of valid range'', but I've no idea how the values could have been out of range since i set them via the Kstars slide interface and that does not allow to set values out of range...
INFO	15.008676 sec	: Session log file /home/gamepod/.indi/logs/2017-04-06/indi_asi_ccd/indi_asi_ccd_07:37:10.log
DEBUG	24.472871 sec	: Toggle Logging Level -- Driver Debug
DEBUG	32.377863 sec	: Attempting to open ZWO CCD ASI120MC...
INFO	32.837732 sec	: Setting intital bandwidth to AUTO on connection.
INFO	32.839314 sec	: CCD is online. Retrieving basic data.
DEBUG	32.840057 sec	: Control #0: name (Gain), Descp (Gain), Min (0), Max (100), Default Value (50), IsAutoSupported (True), isWritale (True) 
DEBUG	32.840127 sec	: Adding above control as writable control number 1
DEBUG	32.840151 sec	: Adding above control as auto control number 1
DEBUG	32.840173 sec	: Control #1: name (Exposure), Descp (Exposure Time(us)), Min (64), Max (2000000000), Default Value (33000), IsAutoSupported (True), isWritale (True) 
DEBUG	32.840212 sec	: Control #2: name (Gamma), Descp (Gamma), Min (1), Max (100), Default Value (50), IsAutoSupported (False), isWritale (True) 
DEBUG	32.840233 sec	: Adding above control as writable control number 2
DEBUG	32.840266 sec	: Control #3: name (WB_R), Descp (White balance: Red), Min (1), Max (100), Default Value (52), IsAutoSupported (True), isWritale (True) 
DEBUG	32.840285 sec	: Adding above control as writable control number 3
DEBUG	32.840303 sec	: Adding above control as auto control number 2
DEBUG	32.840324 sec	: Control #4: name (WB_B), Descp (White balance: Blue), Min (1), Max (100), Default Value (95), IsAutoSupported (True), isWritale (True) 
DEBUG	32.840340 sec	: Adding above control as writable control number 4
DEBUG	32.840358 sec	: Adding above control as auto control number 3
DEBUG	32.840378 sec	: Control #5: name (Brightness), Descp (Brightness), Min (0), Max (20), Default Value (0), IsAutoSupported (False), isWritale (True) 
DEBUG	32.840394 sec	: Adding above control as writable control number 5
DEBUG	32.840414 sec	: Control #6: name (BandWidth), Descp (USB bandwidth percentage), Min (40), Max (100), Default Value (50), IsAutoSupported (True), isWritale (True) 
DEBUG	32.840430 sec	: createControls->set USB 40
DEBUG	32.841846 sec	: Adding above control as writable control number 6
DEBUG	32.841877 sec	: Adding above control as auto control number 4
DEBUG	32.841899 sec	: Control #7: name (Flip), Descp (Flip: 0->None 1->Horiz 2->Vert 3->Both), Min (0), Max (3), Default Value (0), IsAutoSupported (False), isWritale (True) 
DEBUG	32.841917 sec	: Adding above control as writable control number 7
DEBUG	32.841937 sec	: Control #8: name (AutoExpMaxGain), Descp (Auto exposure maximum gain value), Min (0), Max (100), Default Value (50), IsAutoSupported (False), isWritale (True) 
DEBUG	32.841956 sec	: Adding above control as writable control number 8
DEBUG	32.841981 sec	: Control #9: name (AutoExpMaxExp), Descp (Auto exposure maximum exposure value(unit second)), Min (1), Max (60), Default Value (30), IsAutoSupported (False), isWritale (True) 
DEBUG	32.842000 sec	: Adding above control as writable control number 9
DEBUG	32.842022 sec	: Control #10: name (AutoExpMaxBrightness), Descp (Auto exposure maximum brightness value), Min (50), Max (160), Default Value (100), IsAutoSupported (False), isWritale (True) 
DEBUG	32.842039 sec	: Adding above control as writable control number 10
DEBUG	32.842064 sec	: Control #11: name (HighSpeedMode), Descp (Is high speed mode:0->No 1->Yes), Min (0), Max (1), Default Value (0), IsAutoSupported (False), isWritale (True) 
DEBUG	32.842083 sec	: Adding above control as writable control number 11
DEBUG	32.842103 sec	: Control #12: name (Mono bin), Descp (bin R G G B to one pixel for color camera, color will loss), Min (0), Max (1), Default Value (0), IsAutoSupported (False), isWritale (True) 
DEBUG	32.842121 sec	: Adding above control as writable control number 12
DEBUG	32.842141 sec	: Control #13: name (Temperature), Descp (Sensor temperature(degrees Celsius)), Min (-500), Max (1000), Default Value (20), IsAutoSupported (False), isWritale (False) 
DEBUG	32.842160 sec	: CCD ID: 0 Width: 1280 Height: 960 Binning: 1x1 Image Type: 0
DEBUG	32.842179 sec	: Supported Video Format: ASI_IMG_RAW8
DEBUG	32.842220 sec	: Supported Video Format: ASI_IMG_RGB24
DEBUG	32.842240 sec	: Supported Video Format: ASI_IMG_Y8
DEBUG	32.842260 sec	: Supported Video Format: ASI_IMG_RAW16
INFO	32.843264 sec	: The CCD Temperature is 23.000000
DEBUG	32.843313 sec	: setupParams ASISetROIFormat (1280x960,  bin 1, type 0)
DEBUG	41.248927 sec	: StartExposure->setexp : 1.000s
DEBUG	42.455676 sec	: ASIGetExpStatus failed (0). Restarting exposure...
DEBUG	42.555910 sec	: StartExposure->setexp : 1.000s
DEBUG	43.830414 sec	: ASIGetExpStatus failed (0). Restarting exposure...
DEBUG	43.930609 sec	: StartExposure->setexp : 1.000s
ERROR	45.257410 sec	: Exposure failed after 3 attempts.
DEBUG	84.000917 sec	: ISNewNumber->set ctrl 0: 70.00
DEBUG	112.985600 sec	: ISNewNumber->set ctrl 6: 52.00
ERROR	112.985666 sec	: ASISetControlValue (BandWidth=52) error (16)
DEBUG	118.390615 sec	: ISNewSwitch->SetControlValue 0 70.00
DEBUG	118.394616 sec	: ISNewSwitch->SetControlValue 3 52.00
DEBUG	118.396215 sec	: ISNewSwitch->SetControlValue 4 95.00
DEBUG	118.397847 sec	: ISNewSwitch->SetControlValue 6 40.00
ERROR	118.397887 sec	: ASISetControlValue (BandWidth=40) error (16)
DEBUG	124.971306 sec	: StartExposure->setexp : 1.000s
DEBUG	126.294383 sec	: ASIGetExpStatus failed (0). Restarting exposure...
DEBUG	126.394552 sec	: StartExposure->setexp : 1.000s
DEBUG	127.723626 sec	: ASIGetExpStatus failed (0). Restarting exposure...
DEBUG	127.823817 sec	: StartExposure->setexp : 1.000s
ERROR	128.825398 sec	: Exposure failed after 3 attempts.
INFO	132.411172 sec	: CCD is offline.

Anybody any ideas? Thanks in advance!

Erik

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

ASI 120MC failes to expose 7 months 2 weeks ago #16001

Please flash your camera as indicated in the CCD FAQ
The following user(s) said Thank You: emk

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

Jasem Mutlaq
Support INDI & Ekos; Get StellarMate Astrophotography Gadget.
How to Submit Logs when you have problems?

ASI 120MC failes to expose 7 months 2 weeks ago #16020

  • maudy
  • maudy's Avatar
  • Away
  • Platinum Boarder
  • Platinum Boarder
  • Posts: 323
  • Karma: 2
  • Thank you received: 23
In case it helps, this has happened me as I use an ASI1600 and ASI224 for guiding. With ZWO in the CCD and Guider INDI setup in Ekos, the frames loop and do not download. To fix it, I leave ZWO in CCD only.

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

ASI 120MC failes to expose 1 month 2 weeks ago #20093

I have a similar problem.
My setup is:
Odroid XU4 Ubuntu Mate 4.9.52-66 (armv7l)
Indi 1.5.0 from repository
ASI 1600MM-Cool attached at USB3 port
-> ASI 120MC attached at ASI 1600 hub
-> ASI EFW attached at ASI 1600 hub

The filter wheel is working well but camera exposures don't work. I'm getting [ERROR] Exposure failed after 3 attempts. I tried other USB ports - same problem. The 1600MM-Cool was working with Odroid XU4 Ubuntu Mate and Kernel 3.10 but the 120MC had the same exposure error. I also tried the compatible firmware for 120MC - no change.
The setup works fine on my Laptop with Linux Mint and Kernel 4.10.0-35-generic so I think it's an ARM problem?
Attachments:

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

ASI 120MC failes to expose 1 month 1 week ago #20105

  • emk
  • emk's Avatar Topic Author
  • Offline
  • Fresh Boarder
  • Fresh Boarder
  • Posts: 15
  • Thank you received: 1
is your indi driver version compatible with your asi firmware?

right now i've outdated firmware on my asi120, which doesnt work with new indi driver versions, but works fine with my pi, which has still an older indi driver installed.

viel glueck

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

Last Edit: by emk.

ASI 120MC failes to expose 1 month 1 week ago #20106

Modern Linux kernels don't support high bandwidth on USB2 anymore. For more details and how to patch your kernel, please see

zwoug.org/viewtopic.php?f=17&t=7132&sid=...1b71e3e7e5c4&start=0
The following user(s) said Thank You: fehlfarbe

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

ASI 120MC failes to expose 1 month 1 week ago #20112

  • kecsap
  • kecsap's Avatar
  • Offline
  • Senior Boarder
  • Senior Boarder
  • Posts: 47
  • Karma: 1
  • Thank you received: 23
I have a Chinese clone (Datyson T7) of the Chinese ZWO ASI120MC camera. (It sounds funny, is not it? :D )
I did an investigation about these cameras because it did not work out of the box with my Raspberry Pi. I came into these conclusions:
- All QHY and ZWO _low-end_ cameras use the same cheap, crappy USB chip inside.
- QHY did a Windows-only implementation over the crappy HW. It barely works on Linux.
- ZWO did a better HW design+SW implementation, but it is still not fully compatible with Linux.

ZWO (e.g. ASI120) issues:
- The original firmware used 1024-byte USB packets what is not compatible with new Linux kernels. It violates the USB standard to reach higher fps.
- ZWO released later "compatible" firmwares with 512-byte USB packets, but it is not as fast as the original firmware and it will work in less places.

My understanding that if you want to use the low-end ZWO cameras in Linux, you have two options:
1. To be the best chance to run with your Linux box, use the original "non-compatible" firmware and patch/recompile the kernel with the following patch: zwoug.org/viewtopic.php?f=17&t=7132#p13486
2. If you don't care about the performance or you don't know how to compile kernel then flash the "compatible" firmware for your camera and pray.

In my case, I use "compatible" firmware for my ASI120MC clone. It works well with my Raspberry Pi, it is enough for me, but the exposure fails with my Linux laptop.
The following user(s) said Thank You: knro, fehlfarbe

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

Last Edit: by kecsap.

ASI 120MC failes to expose 1 month 1 week ago #20116

Thanks for your input!

I'll try to patch my kernel. But this is only about USB 2.0 cameras.
It should'nt affect the ASI 1600 with USB3 that shows the same error!?

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

Last Edit: by fehlfarbe.

ASI 120MC failes to expose 1 month 1 week ago #20119

I patched the kernel and uploaded the "not compatible" firmware to the cam but the error is the same. Then I plugged the AS120MC to USB2 port and it's working. The 1600 is also working on USB2 so I think there is something wrong with ODROIDs USB3 drivers.

Edit:

Summary for ODROID XU4
ASI 1600 connected to USB2 - works
ASI 120MC connected to USB2 - works
ASI 120MC connected to ASI 1600 connected to USB2 - works
ASI 1600 connected to USB3 - works (if I remove the 20cm extension cord of my "astro-box", so maybe it's an USB3 power problem?)

ASI 120MC connected to USB3 - doesn't work
ASI 120MC connected to ASI 1600 connected to USB3 - doesn't work

I will use "ASI 120MC connected to ASI 1600 connected to USB2" for the moment. I want to take deepsky images with the 1600 and guide with the 120 so download speed isn't that important. Thanks for your hints :)

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

Last Edit: by fehlfarbe.
  • Page:
  • 1
Time to create page: 0.168 seconds

Login



3rd Party

Choose from the numerous 3rd party INDI drivers to suit your needs!

Got Problem?

Check out the FAQ, the forum, and the bug tracking system to resolve any issues you might have!
You can also subscribe to INDI newsletter and development mailing lists to get the latest updates on INDI!


Gallery

Replica

Why INDI

Replica