• Cameras

  • 2600mm failing to download exposure

Brand new 2600mm while running a capture sequence after 30 perfect exposures, images initially corrupt or 60% and now get a failed image using either the ZWO software or NINA.
Camera working perfectly otherwise, cooling, etc.

Same here, I get these random download fails from time to time.

Stopped after 2 hours of imaging. Nothing touched or changed. Now will not download come what may. $2400 camera. I'm very irritated. Would have hoped for a zwo suggestion. Can't even report an issue as the 2600mm does not list as a camera option on their support page.

    1.Did you try it with different cables, ports, and computers?
    2.Please try in ASIStudio
    3.After these steps, if issue persists, please refer to attached PDF to catch SDK log.

    zwo-catch-sdk-log-manul.pdf
    1MB

    Ok I can consistently replicate this problem also in ASIStudio.
    The problem is likely to happen in the following two scenarios:

    1) the first ever exposure after connecting the camera
    2) the first exposure after a change in the image dimension properties ( bin or resolution)

    check these videos:
    https://drive.google.com/file/d/1KsgVhM7Iw5cuvlpXOeQ71Q70xhh_kmC0/view?usp=sharing
    https://drive.google.com/file/d/1hH9Bmb43aPQS-0TRwyyf8RFgnbu43F8c/view?usp=sharing

    SDK and wireshark logs are saved here:
    https://drive.google.com/drive/folders/1RBRBG-472bTJ-lB1OBXZLX-g8fbtdjyk?usp=sharing

      Hello
      we want to do a remote check
      would youplease leave your email ,We will contact you via email

      10 months later
      7 months later

      @tech@zwo
      After working perfectly for a few months, my ASI2600MM Pro just started having the same problem.
      I've tried different software, with different cables, different USB ports on different PCs, but the issue still remains.
      In my experience the problem presents itself when the cooling power rises above about 15-20%.
      If I keep the cooling off, the camera works perfectly (I've captured and downloaded hundreds of frames), but after a few minutes after setting cooling on, I get total download failures and at times USB freezes.

      I've acquired SDK and USB Wireshark logs.
      https://drive.google.com/drive/folders/1IMrfqYpp5WrdJan_yLi67vmmwE93-Tfg?usp=sharing

      My local dealer here in Italy is at a loss and was unable to suggest a solution other than returning the camera.

      Should I open a ticket with support?

        Alsand Did you try different 12V 3-5A power supplies?
        It may cause by power issue.
        If you have tried, you need to contact your dealer for repair.

          @Tech@ZWO#58202
          Yes, I did try with different power supplies with plenty of current available, both mains and battery, and it does not appear to be a power issue.

          I'll contact my dealer.

          I have two ASI6200M's that do this as well. They work flawlessly until I turn the cooler on. They are in remote locations, so returning them is not really an option. If someone finds the solution to this, I would really appreciate it.

            zimmer777 You can try different 12V power supplies first, it may casue by power issue.

              Yes, we've tried several different 12V supplies and measured their output as well. The cameras will work for a little while with the cooler on but then stop responding to the SDK calls after a few minutes or sometimes up to an hour. I think how fast that happens depends on how much power the cooler is drawing, but I have not been able to prove that. With the cooler turned off via the SDK, they both work. This behavior is very repeatable.

                4 days later

                Unfortunately, they are both in remote locations and returning them is not practical. So as I said in my earlier post, if someone finds a solution to this that doesn't invlove returning them, I would really appreciate it.

                2 years later

                same issues BUT only using NINA. if taking images with ASI AIR there is not a single, dopped frame.
                So it might not be the hardware - could it be the driver?