Hi,
Anyone know if Stellarium will be incorporated into Voyageur?
Stellarium Plans?
1 Like
I heard Leo say he was impressed by it, but I do not believe there is a formal commitment to incorporate it. I like Stellarium much better than CdC.
Kind regards,
Glenn
2 Likes
Is on todo list … sure.
All the best
LO
1 Like
Sweet!!….Thanks :)
We have included planetarium support years ago before the program you mentioned. But actually we have done another choice … creating a virtual fov with framing and mosaic support directly in Voyager with stretched color preview of data in real time. At now is a unique feature in AP panorama. I think you can found it interesting.
Also you have internal RoboClip facilities for all your personal catalog target, another unique feature.
We’ll add Stellarium … but isnt in our priority at now.
All the best
LO
1 Like
There isn’t panorama features.
All the best
LO
I would think you could use Stellarium to decide what targets you should be imaging at any time around your obstacles and then just generate coordinates using the virtual FOV and roboclip to put in a sequence. I have been using CdC but have found the virtual FOV to be much more useful for framing targets than either CdC or Stellarium (Which I used with my previous software) For pointing operations I have found it much better to do a precise goto within Voyager than in the planetarium software.
About the only use I have found for planetarium software with Voyager was to give some visual feedback on where the telescope was aimed in the sky if you were not somewhere where you could look at it directly.
As an aside to Stellarium, they now have ASCOM support for telescope/dome control - no more Stellarium scope 
. Check out the latest build https://stellarium.org/
1 Like
Give the Virtual Field of View feature on the Web Dashboard a try. It’s actually QUITE good at framing (including rotation). I find it better than Stellarium or even Telescopius. You can save your targets WITH their framing in the RoboClip database making it great fun on a cloudy night to save you time under clear nights.
Stellarium doesn’t need Voyager to show where your telescope is currently pointing. In fact, the most recent version has ASCOM built in so you don’t even need StellariumScope anymore.
Voyager is a bit of steep curve if you’re coming from simpler software but once you overcome that and your workflow adapts you’ll find if you plan a lot of targets well ahead of time in RoboClip w/ the FoV tool, you’ll be ready to go on any given night with little daily planning and you’ll waste way less time w/ things going wrong during the night. Voyager handles errors and problems extremely well.
You can use the On the fly section of Voyager. Then find the " Solving Referenced FIT" portion.
That will allow you to solve an arbitrary fit file you already have.
2 Likes
Try to read about OnTheFly on the Wiki:
https://voyager.tourstar.net/index.php?title=OnTheFly
Viewer is external to Voyager… not required to work.
so you dont found inside the actions you talk about.
All the best
LO
1 Like
Also, I strongly suspect you can run Voyager and Stellarium at the same time. There is a very good chance that if you are using the latest version of Stellarium with ASCOM control, that both Stellarium and Voyager can talk to your ASCOM mount at the same time. You can then use Stellarium to slew your mount. You can use Voyager to slew your mount. When either does, it will be reflected in the other.
What you will lack is automatic transfer of PA between the two. You will also lack being able to query Stellarium for object info. If you have internet where you are, that isn’t a loss. You can use Sesame instead.
For the query stuff, if that is essential you could install CDC as well and then connect Voyager to CDC. Then the queries would happen with CDC.
At that point what you lack is the automatic transfer of position angle between Stellarium and Voyager. I don’t actually know if Voyager transfers PA to its Planetarium options because I don’t make use of that. I almost always have my camera set to PA 0.
It is a little clunky but you could solve a fit in on the fly. Goto those coordinates in On-The-Fly. Then in the Web Dashboard, you could press the “Solve Telescope Position and PA” button.
Ultimately, you are going to want to be able to match a camera position with a previous Position Angle.
When that happens, you can do this within Voyager. In on the fly, do a “Plate Solve Actual COORD”. In the status window it will report the PA. Adjust your camera, repeat until happy.
Ohmeye … whats the problem exactly ?
If you want to use Voyager i think you must think at Voyager like a new Program and think that something is really different from before.
If you want to solve a FIT file just do it from onthefly, in monitor log you found the result with resolution an PA.
If you want to move manually the camera (think that is really dangerous in terms of collimation and planarity) just move the camera and do a plate solving operation again from onthefly and before use precise pointing if you need to recenter the target, read the PA and do your adjustments. 1 or 2 ° are ok like precision for flat and other tasks. I hope to help you.
Dashboard is a separated way to do this you found again data on monitor log at bottom of the page.
If you dont feel confortable please ask support, we can arrange a remote session to help you directly.
All the best
LO
This is some interaction between windows manager and OS , probably some standby mode or remote windows management.
One thing you might want to check because it was getting me. I had sleep turned off completely. But it turned out that even though that was true, I did NOT have hibernate turned off. I had to go down into the advanced power management settings to even find it.
We aren’t in beta with the things you mentioned OhmEye … so this is something related to your machine settings. If you want solution at now we cant help, never seen before this behavior. WIll investigate more for sure and wait if other users report about and we have more data to understand.
Thank you so much
LO