I have had crash issues on mac side as well with the zwo cameras, especially during focusing, when there are a lot of image downloads happening

you may try reducing the usb bandwidth on the zwo cameras to 50 or less

and you should probably be plugging your equipment into a powered usb hub and then that hub to the stellar mate

I am using a bandwidth of 40 for my ZWO cameras.
I'm not using a hub. That might be something to consider.
So far I have not been able to see any pattern in when crashes occurs. I have now switched on some logging. Hope that can shed some light on the issue.

/Odd

Here is a log. The last thing that happened was that the exposure completed and the file was download.

The steps I carried out were:
Starting Kstars
Enable logs for Ekos, since I didn't know what to look for I only chose a few. (Capture, Guide and Mount I think).
Align: Goto and plate solve
Start Guiding
Autofocus
Define capturing sequence
Start Capturing
Leave PC at its task with a minimum number of applications running, not touching anything

Then, after a while I had a crash.

/Odd

THanks, looks like it's crashing while loading the FITS. Will try to reproduce this and try to find out the issue ASAP.

Another crash.
This time I had the following logging for Ekos: INDI, Capture, Scheduler, Guide, Mount.
Same workflow as for the previos session.
Everything worked fine for quite a long time of narrowband imaging.
Then I defined a sequence for LRGB imaging, and re-focused.
Started the new jobs in the CCD tab. Immidiately after downloading the first image, Kstars crashed.

/Odd

Sorry for the intrusion... I have a very similar situation - was going to report but decided to do some more testing.
Anyway, my last two sessions I had these crashes. The session before it didn't crash (it was actually my first session with Windows KStars client and Stellarmate server).
(Simple setup - Nikon DSLR, AZ-GTI mount, Stellarmate, Windows 7 64 Kstars 2.9.8 August'18 buid)

-- start everything up
-- able to take pictures in Capture module
-- several Capture/Solve
-- try to take a picture in Capture module. The image gets taken, empty preview window appears - crash!
-- between successful and unsuccessful sessions I installed ansvr server.

Couldn't reproduce with simulators - needs a real camera, I guess.
Today it's going to be clear - will try.
BTW, Windows reports that problem module is ucrtbase.dll

When I use internal Stellarmate client - no crash.

Thanks!
Max

Figured mine out... User error or maybe a bug.
For some reason the Format option in Capture module changed from Native to FITS.
Weird thing is that even with FITS option selected the Capture module works in the beginning but after a few goto's causes a crash.

Oh.. tried to install a newer build of Kstars but wouldn't install saying that Kstars folder is occupied by some other processes, offers to terminate them but doesn't succeed. Reboot doesn't help.
Thanks!
[/quote]

Several users are reporting the exact issue with the Windows version. That is, it crashes when loading FITS, so I'll mark this as confirmed and it is now the priority bug to resolve. If you JUST use the capture module, can you still replicate the crash?

I believe, if I stay in the capture module, it won't crash. Only happens after several (maybe single - didn't try) capture/solve/slew.

Another thing which happened several times - I set ISO to 12800 to have shorter exposures for capture/solve and when I am back from Align to Capture module it's reverted back to default 800. Didn't get the pattern here. Not sure how to reproduce.

I was away over the weekend, but brought my ZWO camera, my laptop and a tracker. So only the camera was connected. I only used the capture window, but still had a couple of crashes. However, I didn't switch on logging.

/Odd

Hey guys,
fairly new to KStars 3.0.0 on Mac, and Jasem has already been more than helpful.
But last night I decided I wanted to image IC2118 (Witch head nebula).
Equipment-wise, I'm only using the camera and filter modules. The camera is an Atik 383L+,the filter wheel is an SX-USB with 5 50mm unmounted-filter slots.
Guiding is done with PHD2 (ZWO ASI178MM on the guidescope) stand-alone, as I don't trust myself enough yet to use it via Ekos.
I've used the focus module (no electric focuser, just a human one) to accurately focus the CCD and then got on the job.
After aligning the mount (EQ8 whose RS232-RJ45 cable I've misplaced and am not able to find anymore...) with the camera attached by taking 4x4 binned previews with the camera module and then slowly working my way up the resolution to more accurately align the mount, I fired up PHD2 and calibrated the guiding process.
When everything was set and the CCD was at its correct temperature, I tried inputing the sequence as single L-R-G-B frames, to be repeated until dawn.
First thing I noticed: when deciding where to put the captures and the .esq file, the reaction time of the "finder" window was 12-15 seconds between the click and the result.
That puzzled me as rather strange (did not have this issue in 2.9. and annoying, but just a minor hurdle to be overcome in order to get good images.
After painstakingly programming the sequence, I started it, and that's where things get interesting: KStars just crashed. And crashed. And crashed. Again and again. At various steps of the sequence set-up process, with no apparent pattern to be recognised.
Until it did not crash anymore and seemed to work perfectly.
Only to trick me into leaving the telescope for a few minutes. When I came back KStars had taken an L frame and then crashed.
Stubborn like a goat, I tried again for something like 20 times, always unable to even get the sequence loaded.
Then again it took one L frame, just to crash once more.
Fed up, I dedicated myself to other things.
Then it dawned on me I could try comet 46P.
I worked my way through another series of random crashes, but then managed to have the CCD start taking exposures.
Left the laptop working. Came back after about one hour, to find out KStars/Ekos had crashed after about 25 minutes of capture time.
Tonight I tried to start KStars (no Ekos) once more to look for some targets for the future. It crashed without mercy.
Attached you'll find:
- Ekos logs from yesterday and tonight (zip file)
- Mac OS logs of the crashes (rtf files)
Can someone help in solving this issue?
With 2.9.8 I had other problems, but at least it was kinda stable. 3.0.0 solved some of the problems I had in 2.9.8, but has become manageable like a wild tiger...

Sorry for the long post, but I wanted to make the whole adventure clear to all

Cheers

Antonio Soffici

After the release of 3.0.0 it has been cloudy where I live, so I have not been able to carry out real world tests.
I have however updated my darks library with several hours of exposures (only camera and filterwheel connected).
No issues seen so far.

I look forward to some clear nights for real imaging though, but weather forecast is still bad

/Odd