5 replies to this topic

[SailDoc]

<p>I'm relatively new to this astrophotography hobby, so please excuse me if this has been covered.&nbsp; &nbsp;I have a ZWO ASI 2600 MM Pro that has had an intermittent problem with saving to the hard drive.&nbsp; &nbsp;This has been a problem whether I have it hooked to my Eagle 5S or my Mele Quieter 4C.&nbsp; &nbsp;NINA says that I am exposing according to plan, and counts the image as complete, but there is not any indication of completed images in the recent images tab, nor or any images written to the external SSD that I have designated as the destination folder.&nbsp; &nbsp;I have read elsewhere that these cameras can be glitchy when hooked to USB 3 ports so I tried USB 2, with similar results.&nbsp; &nbsp;I guess my next step is to try to update the firmware, but I wanted to poll the members to see if anyone else has had similar problems and if so, how did they address it?&nbsp; Color me tired of wasting clear skies.</p>

[sn2006gy]

Make sure you're running latest version of NINA.

 

Beyond swapping out USB cables, I'd make sure that you have good clean power. I use USB 2.0 for the most part because of a history of 3 problems and it's been fine but I have to replace the cables regularly since its remote and all the environmental factors over a period of time seem to degrade them.

[bbasiaga]

1.  Try a new USB3 cable, preferably one that did not come from ZWO

2.  Try it plugged in to a a USB 2 port, with a USB2 cable

3.  In the camera driver in NINA, play with the USB speed setting between 40 and 100 to see if it works. 

 

My 2600MC DUO will not work when connected to a USB3 hub.  Just like you said - NINA thinks everything is fine but the images fail to download.  If I plug it in to the 2.0 ports on the same hub, it works fine.  My hub is a Pegasus Pocket Power Box v2.  I contacted them, and their response was ZWO has an unusual implementation of the USB 3.0 protocol and that this is a known  issue they (ZWO) tried to solve with the speed adjustment in the driver.  It did not work for me using the Pocket power box 3.0 ports, but does work fine when plugged in to the USB3.0 ports on the miniPC directly, or on the ASI Air, or via a USB 2 port on any of the 3 devices.  

 

Brian

[hyiger]

I've had data transfer failures (file save errors) on my ASI2600 that was caused by it to be underpowered. The voltage was sagging to 11VDC and that's when I started getting file save errors. 

Edited by hyiger, 17 June 2024 - 01:40 PM.

[tosjduenfs]

I used to have similar issues with the 2600. I've switched completely to USB 2.0 cables and have not seen the issue since.  

[captainles59]

I am having a problem using a new (used) asi183mm camera in SharpCap and wonder if any of you have heard this or fixed it before?  Similar to above comments.

 

In SharpCap (but not other apps) asi183mm (UNcooled) will not capture or download 16bit frames at high resolution.  But it works fine at 8bit full resolution, and 16bit at lower res like 2000x2000 pixels.  

 

Summary if you are not familiar:  ZWO ASI183MM UNcooled monochrome astronomy camera uses 20.1-megapixel Sony IMX183 sensor with 5496x3672 resolution (39.4 meg files full resolution, 16bit) and 2.4-micron pixel size,  Diagonal: 15.9mm.

 

Observations:  Checked the ZWO drivers and SharpCap version 4.13.13010.0, same on my 2 astro setups, checked 2 cables, same pc, same zwo drivers, works on one rig, not the other.  Problem scope is astro2 (A2).  asi183 (zwo driver) works in 8bit mode but not 16bit at large formats.  16bit seems to work at small formats ie 2000 x 2000 pixels.  Ascom driver worked at 16 bit full format. Cam also worked in asiStudio (asicap) 16bit and in Nina at 16bit full format.  

 

Perhaps related to the download & saving speed, but PC's are almost identical mini pc (MELE Q3). Also, never had any problems with my asi294MCpro with either rig (24 meg files).  

 

Also have strange frame rates.  Mostly ~7fps, but later jumped up to 19fps. Don't know what changed.  I often see cables affecting fps so maby something to be fixed there (but tested 4 now).  19fps is published spec but not sure what conditions.

Thanks,

Les