I’d like to be able to switch to the Sky X and see the scope crosshairs when pointing, tracking and slewing. Would the best way to do this to use the Sky X as mount instead of straight to ASCOM in Voyager? Or just connect the Sky X in parallel to the ASCOM driver?
Wayne
I use TheSkyX and either way works, as long as your ASCOM mount handles multiple clients reliably.
I’ve been letting TheSkyX connect to the ASCOM driver and then Voyager connects to TheSkyX and it’s worked flawlessly with a Paramount MyT and an iOptron CEM60.
Leo may have another perspective, as he uses an AP mount like you do.
Cheers,
Rowland
Thanks! Seems using TSX as the mount would be simpler. Now just gotta dive into the TSX profile settings.
Yes. I use TSX as the camera too. Let me know if you have any questions. I don’t think there was much to change in the TSX profile. More for the camera than the mount, mostly getting the image scale correct so TSX plate solve works. And yes, I’m using TSX for plate solving too - works really well 
Rowland
Rowland, I asked this in the Bisque forum but you might know also. Do you have more than 1 equipment profile? When Voyager calls TSX, how does TSX determine which profile is operative?
I asked Bisque also if there was a way for a calling program like Voyager to specify a profile or even select from a list of profiles when setting up the Voyager profile? I know you can do this with PHD2 profiles, as SGP lets you choose a PHD2 profile when setting up that program. That would be neat.
Thanks, Wayne
Hi Wayne, changing PHD2 sequence from Voyager is a feature requested and in the TO-DO list.
Changin profile in TSX from Voyager i dont check yet if is possible … i need to look in the DCOM interface of TSX to find a method to realize this. I add now to my todo list
LO
Thanks Leo. I do think that would be an excellent addition. I will let you know what I hear back from Bisque.
Voyager was born to be strong … i’m not relaxed with this options to change profile, ok for PHD2 but TSX ! If something go wrong a lot of thing can be affected with strange result … this is a features to add with some deep test.
Leo has answered from the API perspective.
TSX always uses the most recently loaded profile when it starts up, so when Voyager calls it, that’s what TSX will use. If you have changed hardware since the last time you ran TSX, you should run TSX, load the correct profile, and then start Voyager.
I have separate computers for each of my imaging systems - the MyT and the CEM60. So I rarely touch profiles on either Voyager or TSX. Once or twice a year I might switch OTA’s and that’s when I would load a new profile in both Voyager and TSX to match the new OTA / camera, etc.
Cheers,
Rowland
I’m used to strange results in my imaging! 
. I’ll live within the current capabilities until you have a chance to take a look at it. No more questions today I promise.
You are welcome Wayne, please consider my difficult to express myself in another language … sometime i’m not sure to write what i think … 
You do a lot better than I would in another language! 
Leo, according to Software Bisque there’s no programmatic way to query/change profiles in TSX. So one less feature to look at!
Thanks, Wayne
Sorry to hear … personally I have one minipc for each of my setup
Hi
Where there’s a will… may be no programmatic way but I had a dig on the SB forum and it looks like someone has already done something similar: http://www.bisque.com/sc/forums/p/35718/190831.aspx#190831 You will need a valid subscription to see this however if you can’t get to it then I’ll post a synopsis here. You’ll need to start TheSkyX via dragscript run program is what I’m thinking.
Kind Regards
Robert