Hi all,

I have been trying to test out some moderately complex scenario with the telescope simulator recently. It appeared that the telescope simulator only accepts EQUATORIAL_EOD_COORD (JNow) as a number for both RA and DEC and for both sending and receiving.
I tried sending/receiving EQUATORIAL_COORD (J2000) number on telescope simulator device without success.

I found out about this behaviour in this thread: indilib.org/forum/general/4989-telescope...-and-astrometry.html
This can be sort of a problem, especially when interacting with astrometry, because astrometry.net returns everything in J2000 equinox it seems, so there is a discrepancy between coordinates sent to the mount, and actual coordinates written in the fits header, written by the camera simulator.

I understand that this is the default behaviour because it eases the telescope red pointer representation in Kstars, but it would be very nice to have a switch to change the JNOW/J2000, as it is possible to do with the losmandy gemini2 apparently: www.losmandy.com/losmandygoto/gemini_manual_l4.pdf
I did not check wether this is implemented in the gemini2 indi driver, but I will try to test that soon.

Thank you for your help

Read More...

I did not tested this feature extensively to understand how indi telescope simulator is handling the pulse guide duration, but it feels like there is an inconsistency between RA travel and DEC travel for a similar guiding pulse sent by phd2.
The original problem was stated there:
indilib.org/forum/general/4988-phd2-tele...expected-amount.html

Can someone confirm that this is indeed a bug of the telescope simulator ?

Thank you in advance for your help.

Read More...

News: I got a very accurate answer on openphdguiding forums:
groups.google.com/forum/?fromgroups=#!to...-guiding/VKyA3-yEUQo

Might be a good candidate for the wishlist channel.

Read More...

Ok I think there is something I do not understand here, and that is very simple to reproduce:
Launch simulator using ekos with telescope + ccd camera and got to the following coordinates: RA: 2:13:19, DEC: 66:39:36 in hh:mm:ss / dd:mm:ss format

Then in ekos, go to the target icon and click on acquire and solve.
Save the resulting image to fit, and use the set of astrometry parameter provided by ekos, and launch the solve_field command on your own with the same set of parameter.
When I do that, I see different results from the one reported by ekos gui ???

How is it possible ?

Read More...

AstroNerd wrote: I am a bit confused what you are trying to do here....
When using sims, you can still set the telescope home position on Polaris, then slew to an object on the sky map, take an image and solve, and if the mount is not quite in the centre you can adjust then take an image and sync that position, the INdI driver does not really come into the equation...there is no need to do anything with that... or maybe I am not getting what you are trying to do at all.....sorry...

Dear all,

I recently tried to run a simulation of an observing session, and found myself in trouble while trying to validate pointing on my own.
I appeared that the coordinates returned for the image by astrometry.net are different from the one I set to the telescope simulator, by a rather large amount. Maybe I am using the wrong solving parameter ?

I included some examples in the attachement.

The telescope simulator is set to RA: 2:13:19, DEC: 66:39:36

solve-field --guess-scale --cpulimit 15 --no-verify --no-plots --no-fits2fits --crpix-center --match none --corr none --wcs none --downsample 4 --overwrite --skip-solved --ra 33.33 --dec 66.66 --radius 1 [...].fits

Reading input file 1 of 1: "[...].fits"...
Extracting sources...
Downsampling by 4...
simplexy: found 64 sources.
Solving...
Reading file ".axy"...
Only searching for solutions within 1 degrees of RA,Dec (33.33,66.66)
Field 1 did not solve (index index-4208.fits, field objects 1-10).
Field 1 did not solve (index index-4207-00.fits, field objects 1-10).
Field 1 did not solve (index index-4206-00.fits, field objects 1-10).
Field 1 did not solve (index index-4205-00.fits, field objects 1-10).
log-odds ratio 165.597 (8.28061e+71), 35 match, 0 conflict, 23 distractors, 84 index.
RA,Dec = (32.947,66.5702), pixel scale 1.19135 arcsec/pix.
Hit/miss: Hit/miss: +++++-+-++++++++-++++-+-+++-++--+-+-+-+-+-+-+--++----+---+(best)--++++
Field 1: solved with index index-4204-03.fits.
Field 1 solved: writing to file .solved to indicate this.
Field: .fits
Field center: (RA,Dec) = (32.947331, 66.570193) deg.
Field center: (RA H:M:S, Dec D:M:S) = (02:11:47.359, +66:34:12.693).
Field size: 25.4321 x 20.348 arcminutes
Field rotation angle: up is 90.0147 degrees E of N
Creating new FITS file

--crpix-x <pix>: set the WCS reference point to the given position
--crpix-y <pix>: set the WCS reference point to the given position

indiserver --version
2019-04-09T06:07:23: startup: indiserver --version
Usage: indiserver [options] driver [driver ...]
Purpose: server for local and remote INDI drivers
INDI Library: 1.7.5
Code v1.7.4-391-g8f25e25. Protocol 1.7.

Dear all,

I am trying to simulate a guiding session with openPHD2 and the indi telescope simulator.
However, it looks like I am experiencing problem while running the calibration step, see included images:


Is it normal to experience such problems ?

Thank you in advance for your help

Read More...

Did you find any solution for connecting to canon 6D through wifi ?

Read More...