0.00
#...
·
 |
|---|
|
I have a new mount (10micron) which I am using to also learn NINA (I also have a MyT which is tied to TSX, but want to spread my software wings, so to speak). I have a problem though, in that NINA does not properly record the RA and DEC values for a target in the FITS header file. They always show up as perfect zeros (e.g. 0h 0' 0"). This causes problems with plate solving with ASTAP as well; I know I should be able to blind solve but want to address the problem instead of relying on a kludgey approach. I am very new to NINA, so have no idea where to look for a setting to change. I have searched in the 10micron ASCOM driver and under just about any tab in NINA for a clue about this. Does anyone know what might cause this, giving me thoughts about what I can do to change it? TIA, and CS! Kenward |
4.37
#...
·
|
|---|
|
What version of Nina are you using? Release, Beta, nightly? What ascom version? Are you using the option to center and solve in Nina in your imaging sessions? |
1.20
#...
·
|
|---|
| And the NINA discord is a great source as the developers hang out on their discord. |
0.00
#...
·
|
|---|
| What planetarium software? |
5.77
#...
·
|
|---|
|
Hi Kenward, I don't have a 10u mount, but here are a few ideas :- 1. How does NINA connect to the mount ? Are you using ASCOM or a direct connection ? Does the ASCOM driver have settings to enable syncing these parameters ? Does the direct driver have something similar ? 2. To synch your plate-solving ... In NINA/Options/Equipment/Telescope - make sure you have 'Automatic Sync' se to ON. I hope that helps  Gary |
|
0.00
#...
·
|
|---|
|
Hi all, I am using the latest stable version of NINA, and have it set with server on so it communicates with other programs like Cartes du Ciel or Stellarium, and ASCOM is up to date. The driver for the mount is 10micron's own, at the latest version. I generally follow the process they recommend regarding syncs--that being no syncing from NINA (or anything else) to the mount after model building. That prevents accidental tampering with the model itself. Of the several nights I have had been learning these new ways, at least one of those included my using the star atlas to find my target, add it to the sequencer, and then build a sequence of images to run. I was not looking for this problem, but certainly would have expected that the coordinates would have been set by that series of steps. As stated before, I am at the beginning of this learning curve, so there may have been something I was unaware of in this sequence that was needed. ??? Next time out (starting tomorrow) I carefully watch my steps and see what happens. It strikes me as quite possible that there is something that is supposed to be done which I'm leaving out. Kenward |
