Hi
It does sound good and i do want to try it out.
Is the astrometry.net index a paid product or open source?
Is there a windows version? Didn't see the link for the index files on the site
Yeah, standalone. I dont think astrotortilla currently does web lookup.
Im only using the first 1 Gb worth of index files, down to 11 arcminutes, the whole index for all sky down to 2 arcminutes is about 26Gb I think. I might even be able to get away with less, but 1Gb is nothing in the scheme of things
Plate solved a 15 second shot of M20 in under 40 seconds for the first time! Big Whoop!
Also its not too shabby that the raw pointing of the Atlux with a SS2K-PC driving things from under the Sky6 PE and Tpoint. I'd say the the target was only a handful of arc seconds off given the image scale is 20 * 30 arc minutes!
Now I have to learn how to tune AT's parameters are faster! Possibly remove sky catalogues whose imaging scale I won't use. I have now moved the Sky Catalogue (25GB to a SSD), will be keen to see how this speeds thing up!
Software linkage was a tad tricky:
1. The Sky6 points to Vixen SS2K driver using a 70 star Tpoint Model
2. MaxPoint point to "A Sky6 controlled telescope" under ASCOM
3. AstroTortilla (64 bit) points to Maxpoint
Had to do it that way as the Sky's driver hub 32bit model isn't compatible with AT's 64 bit model.
Now have to see what happens when AT updates the SS2K's sync model. I note that the pointing ability of AT seems to be only within 1 arc minute by default - will be keen to see if its practical to go down as low as say 10 arc seconds!
Glad to hear you have success. I've tried AT a couple of times and never had any luck to get it work correctly - it just spends forever trying to plate solve. Any tips?
PinPoint LE (included with MaximDL) works brilliantly for me, provided the reference coordinates are reasonably close. I liked MaxPoint's ability to build a pointing model for the whole sky, but I think it's designed for higher end mounts than the typical EQ6 - every target lands on chip, but it's about ~ 10 arc min out for me.
EQMOD's N-point model, however, works well for me - provided there's a nearby triangle, most of my targets land within arc secs (or 1-2 arc mins) of centre. Having a script that can automatically slew / plate solve / sync (ala MaxPoint's automap feature) using just AT and EQMOD would be great.
I've been using this for a day now, key points I've gained through reading are:
1. Have a shot that includes 30 - 100 stars, do this by maybe taking a 5 - 15 second shot and setting the Sigma parameter to around 70
2. Calculate your imaging scale and set your units accordingly and provide upper and lower bounds; for me that is arcsecperix as unit with a 0.2 - 0.8 range (mine is just under 0.44 arc sec / pixel)
3. I use the parameters other have suggested -H and -L and -r -c 0.02 - seem to work okay
4. I searched originally 180 degrees of sky - will try 30 degree, given my pointing that is still vast versus my current pointing.
5. Try asking on the Cloudy Nights forum for more info; the AT developers seem to hang out a bit there!
Thanks Matthew - I'll give it a go if the weather holds up the next few nights. The index downloads are pretty slow (~ 300 kb/s on a 2 Mb/s connection) - I might try asking AARNET if they'll mirror them for us locally since there would be a good academic justification for them too.
Funny one tonight - I tried both x86 and x64 bit versions tonight at the scope. The 64 bit version connects to the Sky6 Telescope via MaxPoint, as this is the only 64 bit driver in the list that will work with 32 bit drivers. The 32 bit version connects direct to The SKy 6 controlled telescope driver.
With correct imaging I got plenty of plate solves - generally about 2 arc minutes off in DEC, however I had the check boxes Sync and re-point ticked and nothing! It said centering but I could detect no movement. I checked the SS2K-PC handcontroller and it still had the three original stars sync-ed - not the new one that had just been plate solved.
Is this most likely a bug in the sync and goto command?
Later I also opened a previous night's image of M20 and issued a solve and goto - it slew the scope considerably and got fair close but not perfect - about 10 arc minutes off I'd guess.
Anyone know what is likely happening or who to ask?
So reading the Astro Tortilla forums - https://sourceforge.net/p/astrotorti...read/b5546e48/ - this may be an issue introduced in the last version of code. One other person has reported Centering working in v0.51 but broken in v0.52 - may try the earlier version when the clouds clear!
BTW
Tried M83 - a 600 second shot on x86 version v0.51 on a dual core Conroe2 2.3GHz machine, Windows 7 sp1 machine with 8GB RAM and a SSD - found 100 objects - took 26 seconds to solve - yah!
It may have been an issue with a switch setting for the ASCOM driver for the SKY - I had sync disabled to protect the Tpoint model - reckon this could have resulted in the behaviour I experienced - will test it later tonight!
So still more errors on the re-centering. I ensure the ASCOM driver was selected for the Sky6 and syncs were enabled, regardless of the Tpoint model, and that the Sky6 didn't ask for syncs to be confirmed.
Solved for M4 - which was a few arc seconds off in RA and an arc minute or two in DEC off, but the sync and re-slew failed. Checking the log it refused the sync because the reported RA DEC had a 44.23" pointing error - wonder what went wrong?
More investigation, I am beginning to suspect that the default driver that The Sky6 uses to connect to the Skysensor2000-PC isn't the latest version (2.0.6) that definitely supports Syncs. The Yahoo ASCOM group and SS2K group both confirm that AT does support sync's to the SS2K with the native driver directly connected, but not through POTH.
Maybe SS2K driver doesn't allow 3rd party software to issue a sync to it?
I can report that Astro Tortilla connecting directly to the latest Vixen SkySensor2000-PC driver worked correctly; plate solve, re-sync and slew worked like a charm.
So for my needs I its something within the Sky6 that is disregarding the Sync; have posted a query to the Bisque forums - hope I get an answer!
Clouds rolled in before I could try a sync through the Sky6 using both versions of Vixen driver models (original and latest via Telescope API) with debug on.
Tom Bisque got back to me that the Sky6 doesn't restrict or limit sync's - but suggested its not a great idea to pollute your Tpoint pointing model!
Bisque pointed me back at the AT guys to ask them if the error is on their side and suggested I try a simple VB script to confirm the Sky6 does allow (correctly formated syncs).
Will have a go with APT to see if it can issue a Sync to The Sky6 and even confirm that the Sky6 can issue a sync from within itself!
Matthew, any tips for how to configure AT? I had another go after tweaking the settings as you suggest - still no luck plate solving (timeout after 5 mins) even though I gave it the exact coordinates from PinPoint
A bit frustrating really - PinPoint just works for me out of the box, and plate solves everything in about 1-2 seconds max on my 2005 era Core Duo imaging laptop.
Glad to hear you have success. I've tried AT a couple of times and never had any luck to get it work correctly - it just spends forever trying to plate solve. Any tips?
PinPoint LE (included with MaximDL) works brilliantly for me, provided the reference coordinates are reasonably close. I liked MaxPoint's ability to build a pointing model for the whole sky, but I think it's designed for higher end mounts than the typical EQ6 - every target lands on chip, but it's about ~ 10 arc min out for me.
EQMOD's N-point model, however, works well for me - provided there's a nearby triangle, most of my targets land within arc secs (or 1-2 arc mins) of centre. Having a script that can automatically slew / plate solve / sync (ala MaxPoint's automap feature) using just AT and EQMOD would be great.
How are you with VB.NET Dave? I've got some code for this in my drift alignment program if of any interest. Ironically I wrote this to do a Maxpoint type "brute force" maths versus mechanical weakness approach for my HEQ5Pro, but ended up understanding how to align my mount better and use EQMOD pier-side syncs such that a few sync points and plate solving are all I need. From memory set it up to map about 20 point each side of the pier. From memory the trickiest bit was using astrometry routines to issue alt/az slew commands (which EQMOD doesn't natively recognise- have to convert to RA/DEC before slew).
Heck, that was a lot of waffle. Ignore if I missed the mark.....
