Thanks for the feedback on Stellarmate.
That works, thanks and is a useful workaround. So what is the Toggle Fits Viewer Icon used for?
I am on 3.5.8 as well. The workaround for me is to disable the FITS viewer then I don't get the crashing when imaging.
I should say I didn't experience any crashing when I took lots of bias frames with FITS viewer on during the day, only experience frequent crashing when imaging at night whilst attempting observations. When I took the bias frames I had everything connected up just didn't turn the mount or dome on.
It seems crashing only happens with the observing sequence of focusing, aligning, guiding then imaging.
Running Kstars in the debugger and see lots of theses messages:
Dispatch command error(-1): INDI: Could not find property CCD_TEMPERATURE in ZWO CCD ASI120MM Mini
<setNumberVector device="ZWO CCD ASI120MM Mini" name="CCD_TEMPERATURE" state="Idle" timeout="60" timestamp="2022-04-08T11:23:03">
Strange but looking at the Indi Tab for the guide camera or selecting it in the imaging TAB , the temperature is being displayed.
On the Kstars toolbar there is an Indi section that shows a galaxy icon to run (toggle) the FITS viewer. On my system this icon is greyed out. I would like to use it to run the Fits viewer to examine images stored on the SD card. The fits viewer opens when imaging but like to use it when not imaging.
I have tried the Kstars setting but can't find one that enables the viewer. Does anybody know how to get this to work please?
Hi Jasem. Just checked and I had 6:3.5.8 already installed. Did an update and the only item needing updating was skychart. When you say Re-download do I uninstall (apt-get remove) and then re-install? If so will my settings be preserved?
I have to manually stop the sequence queue and select run again to start each entry in the queue for bias frames. Light frame sequences work without interaction.
I have been taking a lot of bias frames to study what offset I should use at a particular gain. This involves adding several entries in the sequence queue. Each entry has a count of 5 at different offset. Typically 6 or 7 entries in the queue. I start the queue and see the whirly gig wait cursor display but nothing happens. I then have to hit the stop button and the start button again. The first item in the queue runs and the 5 images are taken, displaying in the fits viewer. The whirly gig wait cursor appears again and I have to hit stop and start again and manually step through the entries in the sequence.
This behaviour is not seen with Light frames. The sequence queue runs without interaction.
I have a 8 gb Pi 4 with a 32 gb SD card. Just taken 15 darks and watched the CPU and memory usage. When downloading images and updating the fits viewer the CPU peaks around 70% and memory usage peaks at about 1.2 gb or around 2.2gb including cache memory. The mount and dome were not being used so need to look again when next observing. No crash to report which is encouraging.
Yes this topic describes the same problem I have had for the last 2 months. It was raised over a year ago I see and I wonder if the fix is being worked on? I went out tonight after installing latest updates today and it only crashed on the first run. I then managed one or two runs of over 20 frames without crashing and fits viewer on. It would be nice to know if this is being worked on or even if it's thought to be fixed. I can try turning fits viewer off but its essential to check images as they are captured.
Hi Malcolm thanks for reminder. Just did an update. As you say, quite a number of changes recently so will see if this helps. There is another post in the forum that suggests turning off sound for kstars notifications. This has removed the last warning entries in the log when I get a crash. I do wonder however if the warning was due to kstars crashing and not the cause of the crash.
I updated when I re-installed Astroberry about 2 weeks ago. Astroberry is still at v 2.0.4 which is the version I have. You say updated recently? To be clear, do you mean sudo apt update etc?
I am about to give up with Astroberry as kstars crashes when imaging. I would like to move to Stellar Mate but want to see Astroberry working first. It's a shame as I think it has great potential and advanced in terms of networking and architecture.
I have re-installed Astroberry, changed SD card, changed cables, power supplies and USB cables but still see the same issue. It crashes when imaging with the ZWO ASI 2600MM camera but at various times and isn't predictable. It is most likely to crash when taking the second image. With verbose logging selected for all devices in use, the last entries in the log are warnings:
[2022-04-01T23:26:59.603 BST WARN ][ default] - QObject::startTimer: Timers can only be used with threads started with QThread
[2022-04-01T23:26:59.616 BST WARN ][ default] - QtDBus: cannot relay signals from parent Phonon::AbstractAudioOutput(0x45f3ee8 "") unless they are emitted in the object's thread QThread(0x1269270 ""). Current thread is QThread(0x5c73d58 "").
[2022-04-01T23:26:59.618 BST WARN ][ default] - QtDBus: cannot relay signals from parent QObject(0x45f3ee8 "") unless they are emitted in the object's thread QThread(0x1269270 ""). Current thread is QThread(0x5c73d58 "").
[2022-04-01T23:26:59.627 BST WARN ][ default] - QObject::~QObject: Timers cannot be stopped from another thread
From what I have read, these errors relate to the GUI interface.
Do Zoom meetings happen where user problems can be shared? Is there a central resource of known bugs?
Where do I go from here? Help/advice would be appreciated?
I have finally solved the issue I had where imaging would fail to capture. It took me sometime to figure out what was wrong.
My profile was set to internal guiding but I was using PHD2 without using the EKOS guider.
I hope this is the correct process: Start PHD2 first. Then start Kstars and run EKOS with my profile set to external guider, PHD2. After a short while the EKOS guider connects to PHD2. Align and focus then start guider either from EKOS or from PHD2. Finally run my imaging sequence.
Can I upgrade indi to latest version 1.9.4 or do I have to wait for the next release of astroberry? apt list --upgradeable doesn't indicate an update is available.
Clear skies tonight having spent the last few days re-configuring usb connections and hubs. Unfortunately no better, Kstars crashed on taking the second image! I had logging to file on as requested in verbose and attached is the kstars log file and the sys log