TallFurryMan wrote:
supernov wrote:
Sorry if this is documented somewhere obvious, but I couldn't find how I can define the park position for the scope.
Last time I hit the park button I had to do an emergency stop since the mount was slewing to some weird position and the scope was almost hitting the pier
So, how do I define the park position?
Read More...
Had a chance to test it out today and it works!
I removed the L and H parameters and the solves works very fast now
thx for the help, very happy with this. Now on to the next step....
Read More...
knro wrote:
Kaczorek wrote:
Kaczorek wrote:
I just tried to Load & Slew to test if the problem is with the indexes or the solver. I loaded a processed JPG and this got solved correctly.
Will run another test when it's clear to see if something is going wrong with the capturing of the frame, even though the FITS viewer shows a decent picture.
Read More...
I just kept the defaults for the command. Will need to look it up tomorrow
The astrometry.cfg was pointing to /usr/share/data, so I changed it to /usr/share/astrometry since the files are put there
Read More...
I'm having trouble with the offline solver.
Here is what I did and know so far;
- Installed the indexes 4203 and up from indilib.org/about/ekos/alignment-module.html
- used sudo dpkg -i astrometry-data-*.deb to install them
- adjusted astrometry.cfg to point to the right folder containing the indexes
- put in the correct settings in Image Info to make sure the resolution is correct
- the FOV in 'Solution Coordinates' states the correct value
- I'm using the default Options.
- I know the coordinates are within 3 degrees of the actual position. (radius is set to 30)
- I keep getting the 'Solve failed' message after the solver runs succesfully through the index fits
- I can solve the image successfully through nova.astrometry.net
Any things I could check? Some more settings somewhere?
Read More...
knro wrote:
Ok, I added them in the Options and can select them in the drop down. However, when I start INDI only a single tab opens up in control panel named 'GPhoto CCD'.
When I go to the Device Manager they are indeed also there. Starting them as Local opens up 2 new tabs with correct naming of my camera label in the INDI Control Panel, however I cannot connect to them. Seems to make sense to me since the camera's are connected to the server, not locally.
However, if I start the devices from Device Manager in Server Mode, nothing happens.
I'm sure I'm overlooking something easy, but cannot figure out what.
So my steps;
- Edit /usr/share/indi/indi_gphoto.xml and add 2 camera's with different device labels, but with the same driver name. Is this correct?
- start the INDI server on my raspberry pi using: indiserver -v -m 100 indi_gphoto_ccd
- open Ekos
- the added labels are listed in the drop downs for CCD and Aux 1. (added this through Ekos->options)
- Start INDI
- The INDI Control Panel starts up with 1 tab named "GPhoto CCD".
- I can Connect to the device and start using 1 of my camera's.
Please advice where I miss something or am going in the wrong direction
Read More...
Many thanks for your assistance. I edited the xml on both the client and the server.
However, I still can't figure out how to get them to appear in the drop downs so I can select them in the Aux boxes. (they are not there)
I DO see my added camera's in the devices list when I go there from tools->devices->device manager
any steps I'm missing/doing wrong?
Read More...