Jump to content

  •  

CNers have asked about a donation box for Cloudy Nights over the years, so here you go. Donation is not required by any means, so please enjoy your stay.

Photo

ZWO 2600MC - APT Error "Can't read the image"

Astrophotography
  • Please log in to reply
125 replies to this topic

#1 oberresford

oberresford

    Lift Off

  • -----
  • topic starter
  • Posts: 17
  • Joined: 14 Dec 2020

Posted 03 April 2021 - 12:09 AM

Hi guys,

 

Just posting this in case anybody is having this same issue with the ZWO 2600MC using APT.  Error attached.

 

 

I constantly kept getting a "Can't read the image" message in APT although it wasn't consistent.  Today I've done a bunch of testing (cables, ports, hubs etc) and in the end the only thing that has worked is using the ASCOM driver instead of using the ZWO native driver, so far(although I wouldn't bet money on it yet) I haven't had an issue.  

 

Please let me know if anyone has found a different solution to this.

 

Cheers

Ollie


  • Hobby Astronomer and kzar like this

#2 kel123

kel123

    Vanguard

  • -----
  • Posts: 2,087
  • Joined: 11 May 2019

Posted 03 April 2021 - 12:17 AM

Are you sure there is no other program accessing or trying to access the camera at the same time, including PHD2? You can as well try it with another computer.
  • oberresford likes this

#3 oberresford

oberresford

    Lift Off

  • -----
  • topic starter
  • Posts: 17
  • Joined: 14 Dec 2020

Posted 03 April 2021 - 12:20 AM

Are you sure there is no other program accessing or trying to access the camera at the same time, including PHD2? You can as well try it with another computer.

I made sure the other camera was not connected but still got the same issue.  Yes true I haven't tried another PC yet.



#4 lmclouth

lmclouth

    Vostok 1

  • *****
  • Posts: 113
  • Joined: 05 Oct 2007
  • Loc: Davison, MI

Posted 03 April 2021 - 11:56 AM

I've been experiencing the same thing with the "Can't read image" errors.  Haven't found a solution yet either.

I have the latest ZWO driver and latest beta APT.

 

Another problem I've had with APT and the ASI2600MC Pro is the Live View (video radio button checked.)  It usually will start but more times than not when you go to leave it will crash APT.  I usually will double-click to see the image 1:1 to help with focusing.  Then when I move the pointer to click "Live View" to close it the program goes gray and never comes back.  I have to close APT and start all over -- very annoying!

I started using a Frame/Focusing plan to do almost the same thing as Live View.

 

But back to the original problem of "Can't read image", it happens at all sections of the program.  For example, Goto++ in Point Craft.  The mount moves to the new location, takes a picture, then fails the plate solve because of "Can't read image".

And as you say, it doesn't happen all the time.  So VERY hard to debug.


Edited by lmclouth, 03 April 2021 - 11:57 AM.


#5 mark77

mark77

    Viking 1

  • *****
  • Posts: 850
  • Joined: 28 Jun 2015
  • Loc: PA

Posted 03 April 2021 - 01:03 PM

Try an older version of drivers.  At least on the ZWO filter wheel, I cannot get the latest drivers to work but the previous drivers work just fine.   Note, this is on Linux so your millage may vary.

 

Mark



#6 oberresford

oberresford

    Lift Off

  • -----
  • topic starter
  • Posts: 17
  • Joined: 14 Dec 2020

Posted 07 April 2021 - 10:50 PM

I've been experiencing the same thing with the "Can't read image" errors. Haven't found a solution yet either.
I have the latest ZWO driver and latest beta APT.

Another problem I've had with APT and the ASI2600MC Pro is the Live View (video radio button checked.) It usually will start but more times than not when you go to leave it will crash APT. I usually will double-click to see the image 1:1 to help with focusing. Then when I move the pointer to click "Live View" to close it the program goes gray and never comes back. I have to close APT and start all over -- very annoying!
I started using a Frame/Focusing plan to do almost the same thing as Live View.

But back to the original problem of "Can't read image", it happens at all sections of the program. For example, Goto++ in Point Craft. The mount moves to the new location, takes a picture, then fails the plate solve because of "Can't read image".
And as you say, it doesn't happen all the time. So VERY hard to debug.


  • Hobby Astronomer likes this

#7 oberresford

oberresford

    Lift Off

  • -----
  • topic starter
  • Posts: 17
  • Joined: 14 Dec 2020

Posted 07 April 2021 - 10:54 PM

I've been experiencing the same thing with the "Can't read image" errors. Haven't found a solution yet either.
I have the latest ZWO driver and latest beta APT.

Another problem I've had with APT and the ASI2600MC Pro is the Live View (video radio button checked.) It usually will start but more times than not when you go to leave it will crash APT. I usually will double-click to see the image 1:1 to help with focusing. Then when I move the pointer to click "Live View" to close it the program goes gray and never comes back. I have to close APT and start all over -- very annoying!
I started using a Frame/Focusing plan to do almost the same thing as Live View.

But back to the original problem of "Can't read image", it happens at all sections of the program. For example, Goto++ in Point Craft. The mount moves to the new location, takes a picture, then fails the plate solve because of "Can't read image".
And as you say, it doesn't happen all the time. So VERY hard to debug.


I've actually thought of trying Nina as I've tried all sorts it seems so be related to having two cameras connected if my guide cam is connected it starts happening.
  • Hobby Astronomer likes this

#8 elgol20

elgol20

    Lift Off

  • -----
  • Posts: 23
  • Joined: 27 Dec 2018

Posted 08 April 2021 - 11:25 AM

try shorter/other USB cables



#9 Professor2112

Professor2112

    Viking 1

  • *****
  • Posts: 967
  • Joined: 23 May 2020
  • Loc: Massachusetts

Posted 08 April 2021 - 04:57 PM

Not sure if this is relevant but I have a 2600mm and when I first plugged it into nina it couldn’t connect the camera. Some thing like camera connection failed try again or something like that. re-downloading the driver seemed to work. Not sure if it’s part of a bigger issue or not so I’m reporting it LOL



#10 Professor2112

Professor2112

    Viking 1

  • *****
  • Posts: 967
  • Joined: 23 May 2020
  • Loc: Massachusetts

Posted 08 April 2021 - 05:03 PM

I've actually thought of trying Nina as I've tried all sorts it seems so be related to having two cameras connected if my guide cam is connected it starts happening.

I would highly recommend nina regardless of whether or not someone is trying to resolve connection issues with a different program.  I used apt for quite a while and got some good images with it, then switched to nina after seeing/hearing so many people praise how great it is. I’ll tell you something, they aren’t exaggerating... it really is incredibly useful. It’s cut my setup down by quite a bit just because of how easy it is to “figure it all out”. I’ve honestly never read the manual except to reference it as far as plate solving, it’s very easy to figure out how to set up an imaging sequence and connect all your equipment just by messing around with all the features.  When I first started imaging using a laptop with my DSLR I thought apt was the coolest thing ever, others will have their own opinions but to me nina takes the prize over apt in every way. 


  • oberresford and licho52 like this

#11 RazvanUnderStars

RazvanUnderStars

    Apollo

  • *****
  • Posts: 1,447
  • Joined: 15 Jul 2014
  • Loc: Toronto, Canada

Posted 08 April 2021 - 07:39 PM

A common cause of "can't read image" errors is not powering the camera from 12V, even if not cooling. If it's only connected via USB, it will take photos and apps can download them if they were with a short exposure, but if the exposure is over a few seconds long, the download will fail with that error. I have the same camera and have seen this many times.

 

The manual states the power is always required but it's easy to forget it since it only fails with long exposures and only when the image is about to be transferred to the computer.


  • JethroXP and licho52 like this

#12 Mert

Mert

    Cosmos

  • *****
  • Posts: 8,466
  • Joined: 31 Aug 2005
  • Loc: Spain, Pamplona

Posted 09 April 2021 - 02:53 AM

It's not a bad idea to try another program just to check if it is related to APT or something else. Very useful for troubleshooting.

#13 lmclouth

lmclouth

    Vostok 1

  • *****
  • Posts: 113
  • Joined: 05 Oct 2007
  • Loc: Davison, MI

Posted 20 April 2021 - 10:23 AM

Any update on this?

 

Last time I was using APT (again the latest beta), I would still get "can't read image" messages but only occasionally.  And still cannot figure out any pattern to it or make it reproducible.

The camera is powered and connected with 12V and the USB3.0 cable.  And I confirmed again that the USB speed is set to the lowest, 40.



#14 kel123

kel123

    Vanguard

  • -----
  • Posts: 2,087
  • Joined: 11 May 2019

Posted 20 April 2021 - 10:55 AM

This happened to me just last night. I had to restart the computer and it corrected itself. I think it has something to do with disrupted connection along the line. Before yesterday, the last time it happened was 3 months ago.

#15 PaulE54

PaulE54

    Vostok 1

  • -----
  • Posts: 112
  • Joined: 17 Nov 2019
  • Loc: NW England

Posted 21 April 2021 - 04:53 PM

Had this happen just now with my ASI294MC Pro and APT latest beta version 3.87.9.2. This version is said to have latest ZWO drivers for more stable behaviour, so connected with ZWO native driver and after 9 x 2 minute exposures got "can't read the image". So disconnected and reconnected via ASCOM driver, so far so good.....

 

Paul 



#16 CrestwoodSky

CrestwoodSky

    Sputnik

  • -----
  • Posts: 35
  • Joined: 28 Mar 2019

Posted 21 April 2021 - 06:44 PM

Just to let you know, it's not just the ASI2600. This problem has been happening with my ASI1600mm Pro sporadically for the last several weeks. Never had the issue before, now it happens every so often. When it does happen, it usually happens just once during an imaging session. I am using the same computer, cables and power supply as I have since I purchased the ASI1600mm Pro two years ago, but the problem only cropped up recently. I checked and all my drivers have been updated to the latest version. I have switched out the older USB cables with new ones and the problem still persists. 

 

When it does happen, I just disconnect and reconnect the camera in APT and that usually solves the problem - though it means I have to restart the cooling, which is a pain. I also find that I have to disconnect and reconnect the filter wheel, otherwise it remains on the same filter even though APT notes the filter as having changed in the file names. If I don't hear the PC say "filter change" I know that the filter wheel isn't really changing the filter. This only happens after I get the "can't read image" warning and disconnect and reconnect the camera.

 

Again, this started just several weeks ago. It happens enough to be irritating, but I can't identify the source of the issue. 



#17 Mr Astro

Mr Astro

    Explorer 1

  • -----
  • Posts: 67
  • Joined: 09 Nov 2016

Posted 22 April 2021 - 02:39 AM

Hello,

 

1- ASI 2600MC pro should be connected to Power supply .. (cooled or not cooled).

2- Flat USB cable is bad in regard of data transfer ..So, get a round good brand USB cable.

These were my solution when I faced the same problem "can not get image from camera" in NINA..

After that,, I did not face any more...

 

Clear sky !  



#18 kel123

kel123

    Vanguard

  • -----
  • Posts: 2,087
  • Joined: 11 May 2019

Posted 22 April 2021 - 08:46 AM

Hello,

1- ASI 2600MC pro should be connected to Power supply .. (cooled or not cooled).
2- Flat USB cable is bad in regard of data transfer ..So, get a round good brand USB cable.
These were my solution when I faced the same problem "can not get image from camera" in NINA..
After that,, I did not face any more...

Clear sky !

.
I have never heard of 2. The cable supplied by ZWO is "flat" . Does it mean that they don't know about this, yet they have been producing these wonderful cameras. That the cable is flat does not mean that the data passing through them is flat. In fact, the wires inside are the same, whether flat or round.
  • AhBok likes this

#19 niccoc1603

niccoc1603

    Messenger

  • -----
  • Posts: 417
  • Joined: 16 Aug 2018
  • Loc: Firenze, Italy

Posted 23 May 2021 - 03:47 PM

I have a similar problem with my ASI2600MM and have narrowed it down to the first exposure after a resolution change.

 

I received my camera in February and started to have the issue, I tried everything (swapping cables, different PC, different software -NINA and ASICap-, different power supply, USB 3 and USB 2 etc..) but it always presentede the download failure.

I then troubleshooted a bit further and found out the errors were always happening on the first exposure after a resolution change (for example a bin2 exposure after bin1)

I contacted ZWO and shared several logs, debug logs, USB logs, they connected remotely to my PC and concluded the camera needed to be sent back for repair

After two months I receive the camera back and...same issue. So I asked my local dealer for a new camera and they sent me a new camera.

New camera...same issue.

 

It only happens randomly on the first exposure after an image resolution change.


Edited by niccoc1603, 23 May 2021 - 03:49 PM.

  • Hobby Astronomer and oberresford like this

#20 Raphaeln

Raphaeln

    Lift Off

  • -----
  • Posts: 7
  • Joined: 22 Mar 2020
  • Loc: Bex (Switzerland)

Posted 10 June 2021 - 01:29 AM

Hi,

 

Did you find a solution to that problem ?

I have the same issue with my ZWO ASI 2600MM. I have received my camera in February, and due to very bad weather I didn't use the camera until now.

My problem is that the program (I use PRISM v10) randomly can't read the image, sometimes at the first image, sometimes after a filter change, or a after resolution change. The timer remains at 0.0s and after few seconds PRISM detect that it can't read the image.

I have try to change cable, hub etc, but without sucess.

 

It seems that we have all different astronomy software with the same issue.

 

Detail of my imaging gear :

- ZWO ASI 2600MM (native driver)

- ZWO ASI 174 mini for guiding (native driver)

- ZWO FW (ascom driver)

 

Thank you and have a nice day.

 

Raphaël



#21 Poochpa

Poochpa

    Vanguard

  • *****
  • Posts: 2,256
  • Joined: 12 Feb 2005
  • Loc: Buffalo Burbs, NY

Posted 12 June 2021 - 04:00 PM

Same issue here to with my ASI2600MC-P. I bought it new last November and did not have these problems until recently.  I'm using APT, but have also tried NINA and ASICap without success.  APT shows "Busy" status and the image fails to download. Happens randomly, sometimes on the first image in the sequence, but also after a number of images have downloaded. However, even the images that appear to download successfully are often corrupted. See sample below. I've tried 3 different power supplies (including 10A PS), 4 different usb cables and two laptops. All with the same result. I've also tried rolling back the ASCOM driver to the previous version, as well as trying the native driver, and a direct usb connection between the camera and laptop.

 

Has anyone made Sam at ZWO aware of this problem? I was all set to initiate the warranty repair process until I found this thread. With so many of us having the same problem, maybe it's a software or firmware problem.

 

Mike

 

Corrupted downloaded image:

L_2021-06-12_14-29-38_15s_G100__19C.jpg



#22 Raphaeln

Raphaeln

    Lift Off

  • -----
  • Posts: 7
  • Joined: 22 Mar 2020
  • Loc: Bex (Switzerland)

Posted 12 June 2021 - 04:39 PM

I sent yesterday a log of the camera when the problem appear. It seems that the problem could come from the driver...

 

You can see here the Camera log :
00000268 15:00:28.179 [19712] [WorkingFunc]: working thread begin!

00000269 15:00:28.179 [19712] [CirBuf::ResetCirBuff]: Rst
00000270 15:00:28.232 [19712] [WorkingFunc]: Sync status:11
00000271 15:00:28.233 [19712] [WorkingFunc]: Begin long exp 20000
00000272 15:00:28.234 [19712] [WorkingFunc]: wait:1000
00000273 15:00:33.284 [19712] [CCameraCool::AutoTemp]: fPreTemp0.88, now_temp0.19, deltaMs 5547, -0.124C/S
00000274 15:00:33.284 [19712] [CCameraCool::AutoTemp]: T0.19 p-2.04 i-0.00 d0.41 cur-1.63
00000275 15:00:38.850 [19712] [CCameraCool::AutoTemp]: fPreTemp0.19, now_temp-0.38, deltaMs 5563, -0.101C/S
00000276 15:00:38.850 [19712] [CCameraCool::AutoTemp]: T-0.38 p-1.93 i-0.00 d0.34 cur-1.59
00000277 15:00:44.417 [19712] [CCameraCool::AutoTemp]: fPreTemp-0.38, now_temp-0.94, deltaMs 5562, -0.101C/S
00000278 15:00:44.417 [19712] [CCameraCool::AutoTemp]: T-0.94 p-1.81 i-0.00 d0.34 cur-1.48
00000279 15:00:49.569 [19712] [WorkingFunc]: wait for xfer error:997 0
00000280 15:00:49.584 [19712] [WorkingFunc]: wait for xfer error:997 1
00000281 15:00:49.600 [19712] [WorkingFunc]: wait for xfer error:997 2
00000282 15:00:49.615 [19712] [WorkingFunc]: wait for xfer error:997 3
00000283 15:00:49.631 [19712] [WorkingFunc]: wait for xfer error:997 4
00000284 15:00:49.646 [19712] [WorkingFunc]: wait for xfer error:997 5
00000285 15:00:49.662 [19712] [WorkingFunc]: wait for xfer error:997 6
00000286 15:00:49.677 [19712] [WorkingFunc]: wait for xfer error:997 7
00000287 15:00:49.693 [19712] [WorkingFunc]: wait for xfer error:997 8
00000288 15:00:49.709 [19712] [WorkingFunc]: wait for xfer error:997 9
00000289 15:00:49.725 [19712] [WorkingFunc]: wait for xfer error:997 10
00000290 15:00:49.740 [19712] [WorkingFunc]: wait for xfer error:997 11
00000291 15:00:49.756 [19712] [WorkingFunc]: wait for xfer error:997 12
00000292 15:00:49.771 [19712] [WorkingFunc]: wait for xfer error:997 13
00000293 15:00:49.787 [19712] [WorkingFunc]: wait for xfer error:997 14
00000294 15:00:49.802 [19712] [WorkingFunc]: wait for xfer error:997 15
00000295 15:00:49.817 [19712] [WorkingFunc]: wait for xfer error:997 16
00000296 15:00:49.833 [19712] [WorkingFunc]: wait for xfer error:997 17
00000297 15:00:49.848 [19712] [WorkingFunc]: wait for xfer error:997 18
00000298 15:00:49.864 [19712] [WorkingFunc]: wait for xfer error:997 19
00000299 15:00:49.880 [19712] [WorkingFunc]: wait for xfer error:997 20
00000300 15:00:49.895 [19712] [WorkingFunc]: wait for xfer error:997 21
00000301 15:00:49.911 [19712] [WorkingFunc]: wait for xfer error:997 22
00000302 15:00:49.926 [19712] [WorkingFunc]: wait for xfer error:997 23
00000303 15:00:49.942 [19712] [WorkingFunc]: wait for xfer error:997 24
00000304 15:00:49.957 [19712] [WorkingFunc]: wait for xfer error:997 25
00000305 15:00:49.973 [19712] [WorkingFunc]: wait for xfer error:997 26
00000306 15:00:49.973 [19712] [CCameraCool::AutoTemp]: fPreTemp-0.94, now_temp-1.44, deltaMs 5563, -0.090C/S
00000307 15:00:49.973 [19712] [CCameraCool::AutoTemp]: T-1.44 p-1.71 i-0.00 d0.30 cur-1.41
00000308 15:00:49.988 [19712] [WorkingFunc]: wait for xfer error:997 27
00000309 15:00:50.003 [19712] [WorkingFunc]: wait for xfer error:997 28
00000310 15:00:50.018 [19712] [WorkingFunc]: wait for xfer error:997 29
00000311 15:00:50.034 [19712] [WorkingFunc]: wait for xfer error:997 30
00000312 15:00:50.049 [19712] [WorkingFunc]: wait for xfer error:997 31
00000313 15:00:50.065 [19712] [WorkingFunc]: wait for xfer error:997 32
00000314 15:00:50.080 [19712] [WorkingFunc]: wait for xfer error:997 33
00000315 15:00:50.095 [19712] [WorkingFunc]: wait for xfer error:997 34
00000316 15:00:50.111 [19712] [WorkingFunc]: wait for xfer error:997 35
00000317 15:00:50.126 [19712] [WorkingFunc]: wait for xfer error:997 36
00000318 15:00:50.141 [19712] [WorkingFunc]: wait for xfer error:997 37
00000319 15:00:50.157 [19712] [WorkingFunc]: wait for xfer error:997 38
00000320 15:00:50.182 [19712] [WorkingFunc]: wait for xfer error:997 39
00000321 15:00:50.189 [19712] [WorkingFunc]: wait for xfer error:997 40
00000322 15:00:50.204 [19712] [WorkingFunc]: wait for xfer error:997 41
00000323 15:00:50.219 [19712] [WorkingFunc]: wait for xfer error:997 42
00000324 15:00:50.234 [19712] [WorkingFunc]: wait for xfer error:997 43
00000325 15:00:50.250 [19712] [WorkingFunc]: wait for xfer error:997 44
00000326 15:00:50.265 [19712] [WorkingFunc]: wait for xfer error:997 45
00000327 15:00:50.281 [19712] [WorkingFunc]: wait for xfer error:997 46
00000328 15:00:50.296 [19712] [WorkingFunc]: wait for xfer error:997 47
00000329 15:00:50.312 [19712] [WorkingFunc]: wait for xfer error:997 48
00000330 15:00:50.328 [19712] [WorkingFunc]: wait for xfer error:997 49
00000331 15:00:50.328 [19712] [WorkingFunc]: Long exp:Get one Frame 20000
00000332 15:00:50.329 [19712] [WorkingFunc]: Buffer status:11
00000333 15:00:50.329 [19712] [WorkingFunc]: Data in cache is invalid, could not reload!
00000334 15:00:50.329 [19712] [WorkingFunc]: get len:0x0 drop:1  frametime:619200us waittime:1ms
00000335 15:00:50.355 [19712] [CCameraFX3::ResetDevice]: ResetDevice
00000336 15:00:50.355 [19712] [WorkingFunc]: after ResetDevice
00000337 15:00:50.355 [19712] [WorkingFunc]: drop frames:1
00000338 15:00:50.358 [19712] [WorkingFunc]: snap Exp: EXP_FAILED:1
00000339 15:00:50.364 [19712] [WorkingFunc]: working thread exit!

 

I will keep you informed when I have some news from ZWO

 

Regards

 

Raphaël


Edited by Raphaeln, 12 June 2021 - 04:40 PM.


#23 Poochpa

Poochpa

    Vanguard

  • *****
  • Posts: 2,256
  • Joined: 12 Feb 2005
  • Loc: Buffalo Burbs, NY

Posted 13 June 2021 - 03:08 PM

I just sent ZWO a description of the problem using their email support contact form. Hopefully, other 2600 owners having the same problem will also contact ZWO and make them aware of the issue.

Mike


  • StevenBellavia likes this

#24 rgsalinger

rgsalinger

    Cosmos

  • *****
  • Moderators
  • Posts: 9,815
  • Joined: 19 Feb 2007
  • Loc: Carlsbad Ca

Posted 13 June 2021 - 03:12 PM

You folks do know that there's a USB bandwidth parameter that you need to adjust until you get an image. If you are using a hub make sure that you test without it to see if it's the underlying issue.

 

My own solution is not to use USB 3 ever. With my ZWO071 the difference in download speed between USB 2 and USB 3 is about 1 second for a full frame. USB is much more forgiving. 

 

Rgrds-Ross


  • charlieb123 and galacticinsomnia like this

#25 Poochpa

Poochpa

    Vanguard

  • *****
  • Posts: 2,256
  • Joined: 12 Feb 2005
  • Loc: Buffalo Burbs, NY

Posted 13 June 2021 - 03:19 PM

Of course, Ross. I typically have the usb traffic set at 40 or 45 for that reason. I've also tried using a USB2 cable instead of USB3 and a direct connection without a hub to the laptop. No luck. I purchased the camera in November 2020 and it worked fine until recently.

Mike




CNers have asked about a donation box for Cloudy Nights over the years, so here you go. Donation is not required by any means, so please enjoy your stay.


Recent Topics





Also tagged with one or more of these keywords: Astrophotography



Cloudy Nights LLC
Cloudy Nights Sponsor: Astronomics