I think that answers my question, I need to set " the handset to flip about 10 degrees past meridian". I was used to the mainly dumb HEQ5_Pro where everything is set via EKOS and I couldn't find a setting for it.
On a related note, do you power off the mount using the mounts' push button or do you cut the power another way. I have been careful to power off the mount directly so far, but it would suit me just to remotely cut the power after parking..
Just set up my new CEM120 all seems fine, can track, park, goto, platesolve and goto etc. But when pointing south and tracking across the Meridian the mount stops tracking at 180 deg and goes idle. If I do a GOTO say to 190 deg target, it does a nice Meridian flip. (pretty scarry with 35 kilos of gear.) I want the ability to track to around 190 degrees before flipping or stopping. From the Ioptron manual I can use the handset :
Maybe a useful update:. After reading this thread I just got my new CEM120 and set the Home position and a custom parking position at aprox 90 degrees using the hand controller. Then I set up EKOS with same parking position and it all works fine. I can Park and unpark from Ekos and it shows the correct status in mount control. Mount connection via ethernet. I do however have a different problem at the Meridian that I will start a new topic for.
There are various flavours of Indi Ekos on Raspberry Pi. The easiest thing to do is get a new SD card and keep the Asair one. The just install the free Astroberry image. www.indilib.org/raspberry-pi/astroberry-server.html
Very straightforward and you get a great range of device drivers. I haven't used ASair, but not sure of added benefit of using Asair branded version.
Comet 7p/pons-winnecke is also in the wrong position, out by around 30 deg. Did same as previous poster. Located in Stellarium, cross checked with SkySafari. Checked my location time settings OK by locating a known star. Also updated comet settings in Indi. Still wrong. Max D
After a bit more work I got past that part and it now seems to work.
A few other questions: I am using this to close my roll off shed using a garage door opener. Mechanically it all looks good.
I will probably not use the scheduler to open the roof. Too much can go wrong with dire consequences, for example trying to open with the roof latches locked.
The OBS is in my back garden so my main use, particularly in the summer, will be to set the scheduler going and get indi to image and shutdown while I sleep.
THe main disaster I can foresee is the roof shutting without the scope being parked. Park scope is a tick box on the scheduler which I could forget. Is there a way in the my roof park script to check the scope is indeed parked?
I will probably try and also implement a physical check using a laser trigger and a last resort "collision" switch on the roof. But it would be good to be able to check the indi status.
The other possible disaster is rain. I have a rain gauge, what do you think is the best approach to connect this to trigger shutdown?
Thanks, this looks really promising. I have read the threads you suggested. I have copied the full set of scripts to /usr/share/indi/scripts/ ran sudo chmod +x *.*To test I left all the scripts at their default "Empty" values except park, where I added the lines:
print "Shutting Roof ..."
Just to see if it runs.
I then created a simple Indi Ekos profile with the dome scripting gateway. When I ran it, the control panel shows the full set of scripts but the gateway would not connect with the error "2021-04-15T09:28:37: [WARNING] Failed to connect "
I looked at your script for connect.py which contains a USB connect routine, but I assume I can leave it empty, or does it need something to connect to?
I switched on the log files, but the directory is empty.
Getting there, grateful for the help.
Still having a problem with this.
Same issue as below script runs when I issue it at the command prompt python maxclose.py made the script executable
Made executable, but doesn't run in scheduler.
Does the script need to be in a particular directory?
All I am trying to do is briefly close then open a relay to trigger the closure of my roof. Is there a better way?
I agree, any camera from a mainstream manufacturer like ZWO or QHY should just work. I have never had a problem with my ZWO ASI294MC, or my QHY guide camera, but the choice depends on what sort of imaging you want to do. I won't open up the can of worms that is OSC vs Monochrome, but if you do get something like ASI1284 I would recommend the Optolong L_Enhance filter for nebula and other Ha rich targets and the L_pro for RGB targets like galaxies, clusters etc. Unless you have very dark skies. I also upgraded from an EOS 1100D a few years ago and the improvement is huge.
Each time the solver stopped working for me it was because I changed kit, scope, FR or sensor and forgot to tell it. Worth checking that the FOV it thinks it has corresponds to your actual FOV. I maybe the only fool who has forgot to do this, but its worth checking.
I just install Indi Ekos on a new install of ubuntu20.04.1 but there are no icons and no way to start it.
Install completed with no errors and when I tried to install it again I got :
" indi-full is already the newest version (1.8.6~202008211453~ubuntu20.04.1).
I have installed before on Ubuntu on other machines and various other packages like VNC & Firecapture installed OK this time.
Hi, I had the same problem with my EQ5_pro when changing scopes. When I re-started EKOS it thought the mount was still in the Parked position. The key is to unpark the mount in EKOS, switch it off, then manually move the mount to the home position. Then switch on the mount and re-start EKOS and it shows the correct position. I then GOTO a star in the region I will be imaging and plate-solve to get the alignment precise.