On 7/16/20 05:38, Geof Lewis wrote: Hi Ned, Sorry, but I have no idea what that means. My images are FITS files generated by a QHY 174 GPS.
I am not competent computer wise to fix it. I normally use SharpCap but its Plate Solve function is jammed up by some interfering code. ANSVR is basically the same as Astrotortilla, uses the same Index files, but places them in a different.
#ALTERNATIVE TO SCOPEBOX WINDOWS PS2#
PS2 works great provided you are very close the the target coordinates, but I sometimes need the blind solve failover. I use PlateSolve2 (PS2) with SGP, with ANSVR as a back up blind solver. I recall that I had issues with FITS files with AT, so I think I ended using jpeg for solving, but I’m not sure about that. I’m also not particularly computer savvy. Hi Ned, Sorry that I couldn’t be more help. I recall that I had issues with FITS files with AT, so I think I ended using jpeg for solving, but I’m not sure about. On 7/16/20 10:01, Geof Lewis wrote: Hi Ned, Sorry that I couldn’t be more help. I do asteroid occultations so I use Astap stand alone because it has a feature that circles the asteroid in a solved image. It comes with PlateSplve3 so I already have its indexes. Get Outlook for iOS From: Ned Smith Sent: Thursday, J4:32:53 PM To: Subject: Re: Connecting ASCOM Camera I use SiTechServo for mount control. I’ve heard that Astap is better than PS2, but I’ve not tried it. Having slewed to the target with CDC, which works fine, I then hit Capture and Solve in Astrotortilla, the camera takes an.
#ALTERNATIVE TO SCOPEBOX WINDOWS SOFTWARE#
All the software versions are no doubt old versions, but it's an old laptop and as I say it all used to work a treat. I use APT, PHD2, CDC (Cartes du Ciel), and Astrotortilla, all on an old vista laptop. Everything was fine bar Astrotortilla, which used to work fine. Hi guys Getting back into astro after about 4 years away and I just set my old kit up and hoped it would work. That's great but does it make sense? what are the 41xx fits files vs the 42xx files? I put them into the data directory and now i get 10 second solves. I noticed today that had solved my image with a 4111.fits vs the 42xx I have in my directory. I'm shooting with a FOV of 3.5 degrees and experiencing very slow solves and total failures. Regards, Geof From: bill rowe Sent: 19 November 2020 16:55 To: Subject: 4111 vs 4211 fits files I'm shooting with a FOV of 3.5 degrees and experiencing very. Hi Bill, I found this on the Sourceforge discussion threads which seems to explain the differences between the indexes. The 4100 set is an alternative index set for wide FOV imaging, not recommended for anything narrower than 3 degrees. As I read that thread the 41xx indexes may be appropriate for my 3.5 degree FOV. I set it up using this : The connection is ASCOM scope and then Celestron. The problem seems to be not communication with the mount. It took a photo and goes trough the process, so it communicate with the camera. I get a "Failed to Solve" message in the end. I installed in win 10 AstroTortilla-0.7.0.0-圆4 and cygwin setup-x86 and cygwin x86_64 but it is the same result. Sent from my iPadĪfter capture and solve i have this message in log, see join files. I’m new to this but can I put on 0 for focal length and get my effective focal length from this? I have a sct 9.25 and depending on spacers the fl changes so I need to know what indexes to get.
if you know your camera sensor pixel size and pixel dimensions. A solved image will display actual field of view dimensions. It would add a few seconds to solution, but noting drastic. You can enter Scale Min and Scale max to cover the entire range of FOVs that you might encounter. John Where are you entering the focal length? The Astrotortilla GUI does not require it.