Horizon Creator bug report

Issue #1198 closed
Jordi Solaz created an issue

Hello

Thank you for the nice NINA project. I appreciate it very much.

it’s my first time here contributing in reporting a bug, and It is related to the Horizon Creator plugin.

I use a quite old Meade LXD75 autostar goto mount using the “Meade Classic and Autostar I” connection driver. Time ago I already wanted to create my obstructed horizon using this plugging, but I got very strange negative altitude horizon readings, so I decided to scrap the result.

This time I decided to make it another try with version 1.1.1.0 of Horizon Creator and make a recording of my steps, so the developers can see.

So the procedure I make was quite straightforward. In daylight I set up my mount and synchronized with the sky. Next I pointed it to Deneb as a starting known point (see screenshot1). Here the cross in the graphics is wrong, the azimuth of Deneb should be about 72 deg East, and the cross point at near 270 deg. Altitude is also about 10 degrees lower than expected 69deg.

Then I use Scope Control commands to send the mount at Alt=0 and Azi=185. The mount drives there, while the cross in the graphics makes a weird movement travel around the celestial sphere. (screenshot2)

Next I add my first point to the table, which is numerically wrong according to the telescope pointing. After that I press the up arrow icon on the Horizon Creator, expecting to increase altitude by 5 deg. and then the the mount makes a nearly endless long travel to elsewhere (screenshot3). I add the next point to the table and make a completely senseless point 2 deg below the horizon, while the mount point high up in the sky.

My impression is that maybe the conversion of RA,Dec coordinates to ALT/AZI is wrong or something similar.

I’m adding the log file with trace comments for if you like to take a look.

Thank you for taking your time to feedback me.

Jordi Solaz

Comments (6)

  1. Stefan B repo owner

    Hi, in the logs i can see that the latitude/longitude was imported. Are these correct after import? Also does the problem persist after restarting the application - maybe the plugin did not react on the update of the location.

  2. Jordi Solaz reporter

    Yes they are imported from the telescope, but they are the same as in NINA. They are correct. I also tested the other way, taking them also from NINA directly.

    Thanks for looking at it!!

  3. Log in to comment