The wind died down a bit, so I gave the update a shot.
After a bit of a struggle to get the mount to load (USB issues again) I finally got everything connected. The mount's slave, rotator and shutter settings were all zero again. I re-entered them, and saved them to eprom. I tested the dome to slave to various parts of the sky, and it all worked. The shutter didn't disconnect, and the dome rotated appropriately.
When I moved the mount to home (000 az.) the dome slewed to 000, then onto 090, and back to 360. Once it git back to 360, it stopped appropriately. Some reason that "000" sends it 090. Not sure why, since the mount was at 000, it's park ing position is 000, and the dome's home/park position is 264. Nothing is set to 090. But it sopped after that one iteration, so I'm not too bothered by it.
I then turned everything off and tried again, This time I turned on the debug logging.
INDI again failed to connect my mount. I tried rebooted three times, turned off the mount and back on, and it failed to connect.
It is supposed to connecting at USB0 - but it won't. And when I try to SCAN for ports in EKOS - it only shows USB0 as an option.
So I was not able to test the slaving again.
Also - while the slaving and dome rotator motor settings were still saved in the EPROM and loaded up, the SHUTTER settings reset back to ZERO.
I tried saving them several times, and INDI said all was written to EPROM, but when I rebooted and checked, the shutter settings were back to zero.
I didn't have this issue with the ASCOM driver, so its not the shutter firmware.
So he attached debug should show the CEM120 not connecting, and the shutter saving to EPROM several times - but which was either never saved, or the settings are reset back to zero upon loading.
I downloaded the latest Nightly, but I can't unlock my dome to test it right now as the winds are gusting to 40 MPH (64kph)
This doesn't prevent the Esatto focuser from working, but the error pops up when I start INDI:
[2021-01-24T14:12:17.212 MST INFO ][ org.kde.kstars.indi] - Esatto : "[ERROR] Failed to find property: FnRUN_ACC "
[2021-01-24T14:12:17.213 MST INFO ][ org.kde.kstars.indi] - Esatto : "[WARNING] Failed to inquire parameters. Check logs. "
See the log.
Thanks Kengs! Keep updating this thread, and I will be happy to test any changes to the dome driver you make, with regards to Nexdome 4.0.
As I mentioned above - the dome driver is the only issue that is keeping me from using KStars/EKOS now. It's a show stopper for me.
I've only used INDI with KStars/EKOS since I started digital astrophotography several years ago. I first want to thank Jasem and others who have put so much work into KStars/Ekos and INDI drivers, and helped me save many problems. But now that I am running a remote observatory, I have found that I need to see what else is out there. I have a Nexdome observatory and they upgraded their firmware and solved a major issue with the slaving going out of sync after an hour or so. But there is no INDI driver for the new firmware and so I have not been able to use the observatory since. So this is a good time to try other software, Windows ASCOM software that I have never used before.
I bought my very first ever Windows PC for this endeavor (I have only used Macs and Linux since 1996). This first foray into Windows has not been fun. But I am making headway. I did waste three hours today before I learned that you need Windows drivers for my cameras and other gear. My Macs never needed such things. The second thing that I learned is that ASCOM is messy. So many tools and apps just to connect one dome. I ended up trying NINA to see if it works with all my gear and the dome.
Today I have finally got everything connected, and will test it out on the next clear night. But I have been reading about NINA and its polar alignment routine is not nearly as nice as EKOS's. And I am forced to use an external guider like PHD2 and that will be a real test. I tried PHD2 last year and it would not play well with my CEM120 EC2 mount. I never could get it to work, as it fights with the encoders. But EKOS's multistar worked like a charm. If I can't get PHD2 to work, then my experiment with NINA and ASCOM will be over.
And then there's the lack of a planetarium. I will have to find an external one that works. But I will miss the seamless connection between KStars and EKOS.
But the biggest thing I learned today is that I can't run all my gear at home while controlling all that equipment remotely out in the observatory via INDI. VNC is sluggish.
If anyone ever gets time to write the new INDI driver for Nexdome 4.0, please let me know! I can't wait to come back.
The reason I was hoping to use the new firmware is they solved the issue of the rotator getting out of sync after an hour or so of use. I can confirm that 4.0 did solve that. I had it track for three hours and the dome stayed on target the whole time even through a meridian flip. But the other issues are just too much to contend with now, so yeah I would stick with 3.3.
The new Firmware 4.0 may have a bug, or the INDI driver needs some updates. Something is broke.
I am using KStars 3.5 and Nexdome Firmware 4.0. Here's what problems I have been over the last two days:
- The dome still has a problem when I send my mount to the HOME position (zero az.). As soon as the dome slews to zero, it then waits a few seconds and then goes off and slews to 270. After a few more seconds it goes back to zero and this repeats until I either turn off SLAVING or I move the mount to any other location.
- The shutter keeps crashing after a few minutes of use. I have to cycle the shutter power off and back on, and then use the manual button to close it.
- The Nexdome driver can't seem to hold any settings I type in and even I write them two the EPROM. This includes the rotator acceleration and velocity speeds, and the slave configuration measurements. I fill them in, and choose to save them to EPROM. It appears to work. But then after I log off and back in, the settings are back to zero!
NONE of the above issues happened with the previous version of the Nexdome firmware (3.3). They are all new after upgrading to 4.0
Is there anyone who can update the INDI driver to use the new 4.0 Nexdome firmware that mis now available on GitHub?
I just got the latest nightly and discovered that the polar alignment adjustment screen has a new feature. Instead of drawing one line vector from the alignment star back to the target icon, it now includes separate colored vector lines for azimuth and altitude. This, along with the PA error broken down into two separate written measurements (Alt and Az) makes moving the mount correctly much more accurate! I love it!! Thanks!!
I continue to have major problems with INDI starting up, and I want to remove INDI Web Manager to reduce one possible source.
I only use my INDI control system via VNC so I don't need the web manager. How do I remove it completely from my system?
Can anyone offer suggestions as to what driver is corrupting my EKOS Profile file?
For the second time in a month my EKOS profile file has been corrupted. Like before, I was trying to start INDI and KStars crashed. When I restarted KStars all my profiles were gone, and I was unable to add new ones. I had to delete the profile file (userdb.sqlite) and then all was well. Until tonight. Again, I was having trouble starting INDI. The USB drivers were nit connecting, and then KStars crashed. Upon relaunching KStars the profiles where again empty. This time I saved the corrupted profile file (see attached). I had to change the suffix to TXT but it's the correct .SQLITE file. If anyone sees anything suspicious in it, please let me know. I think one of my devices is corrupting it.
AAC Cloudwatcher NG
After some work, I got my Esatto focuser to work on the C11 Edge, with the auto guider, filter wheel and ASI1600MM - all within the required 146mm back focus.
But now I am struggling to get EKOS to autofocus. I am imaging through a C11 Edge at 2800mm focal length f/10. The HFR bounces around too much to allow EKOS to find a good focus. I tried 1 second exposures, 2 second, 5 and even 10. I tried averaging the HFR values 2 and 3 times. Regardless, I would see HFR values like 310, 345, 320, 300, 360 etc…. This made determining the exact best focus impossible.
I never had this issue with my small 349mm f.4.9 WOStar71. The HFR values were consistent between exposures. AutoFocus was a breeze and reliable.
I don't know what the best settings to help stabilize HFR values at this high focal length. I tried many different combinations, from using gradient, centroid, and SEP to changing the tolerance settings. Nothing seemed to fix the issue that my star HFR values jump around too much between equal exposures.
Any ideas I can try?
Jasem, I just tested the new update on the CEM120 using the indi_ioptronv3_telescope driver.
It now physically moved the mount to the custom PARK position, but like you said earlier it still thinks it's slewing, so I have to press ABORT.
But even then, it keeps TRACKING. So I have to PARK the mount, then ABORT then STOP tracking manually.