I've been using mine for months without problems, expect funnily enough, when using TheSkyX where it would crash during runs of 10+ bias frames (I suspect the internal DDR was getting overrun as the camera struggled to get images down the USB cable fast enough).
Happy to help provide a TV session if logs/testing required.
GSO Ritchey Chretien 12" Truss | SkyWatcher ED72
ZWO ASI 2600MC Pro, 1600MM Pro, ASI290MM and ASI224MC all-sky | ZEO EFW | ZWO OAG
Moonlite V2.5 CSL | DeepSkyDad AF3
EQ8-R | Paramount ME & MX
Nexdome | SQM LE | AAG CloudWatcher and Solo | Ultimate Power Box V2 | Spike-a-Flat
I have a 4gig RAM version of the Pi4. Many use the 4gig versions now and a number of users are also using the 8gig editions now. It seems a waste to have these extra resources available for use while concurrently having new camera's coming out now with bigger sensors and not be able to take full advantage of the hardware. During this issue, I had like ~1.8-2gig or something free in memory. In essence I had *no* discernible memory exhaustion issue. Is this new patch going to let users use the full memory that is available in their Pi's for these modules processing these large subs?
For me, I can shoot darks/flats/bias all day with the 2600mc, it's imaging that is causing the problem.
I think I mentioned this before, but I am using the Stellarmate OS too, so I've done zero messing around with compiling stuff that could lead to this issue. I've got a 2nd imaging rig with another pi on it and its doing this on that Pi4 as well, with the same stellarmate OS but off a different SDcard.
On memory, I have the 4gig Pi and during the crashing it was only using ~2gig of RAM......we've had nothing but clouds here for ~2mths now so I haven't had the chance to image anything anyway, but its a bummer I can't use my brand new 2600MC for imaging. Its interesting you are using the 6200 with no issues as its a bigger sensor (and therefore bigger subs) with no problems, yet the 2600MC doesn't work.
I just tested it on my system:
- Pi 4 4GB
- Stellarmate most recent stable
- Zwo MC2600
I slewed to an arbitrary point of the "sky", started autoguiding and set up an imaging run of 10 subs @120 secs. Seems to run stable and without any problems. The pictures are all dark, as my scope is inside. All overcast for weeks here, unfortunately. This is why I set up the guidesimulator. Don´t know whether actual autoguiding would make a difference here. Please let me know if I should test something else, as I probably can come close to the problematic setup.
P.S: btw: I have fitsviewer with debayer enabled. Every exposure taken is coming up in the fits viewer.
With the nightly builds I see an odd behavior with the FITS viewer. When I loop the main imaging camera (in my case an ASI6200MM) then the first image is displayed correctly but consecutive images get displayed at a lower and lower resolution and I actually need to close the FITS viewer. I use this looping for manually focusing with a Bahtinov mask so it is quite essential to me that this works well. I noticed tonight that this also happens in the focus tab. Could this be related to the memory optimization fix?
Wouter van Reeven
ASI6200MM and 7 slot 2" filter wheel with a SkyWatcher Esprit 80 ED on a SkyWatcher HEQ5-Pro
ASI1600MM-Pro Cooled and 5 slot 1.25" filter wheel with an 8" TS Ritchey-Chrétien on a SkyWatcher EQ6-R