Corpze

We should really add these commands under the wiki-site, for those who want to script etc. /Daniel

I was thinking the exact same thing Nigel, i would really like to see your menu or a similar one - it make more sense. /Daniel

I backed down to win7, i was up and running within an hour, everything worked at once... /Daniel

Have you looked at the video of me running a autopoint and calculating the pointingfile? I do not wan't to add something that might contain eny errors... It worked for me that time but you never know with autoslew (especially on win10) Wen't back to win7 and everything was operating flawlessly within an hour. Personally, as a newbe - the hardest thing for me to get the mount up and running was; - How crucial the balance and tuning is. Best result did I get when i did a; Rough balance Autotune Manual tune Balance And to finish it off with a final servo tune. - The second most important thing was to me in which order you have to set up autoslew the first time Power on Start Autoslew Motors on Homefind etc... - The third most horrific experience was setting up the parameters for autofocus - but I think there was a quite good PDF on that subject. We could also add what kind of USB-cables, extensions and USB-hubs we are using, i change brand three times before finding a 5m USb 2.0 Cable from Deltaco that worked for me; This one (For both the COM and the HUB) https://www.deltaco.se/produkter/deltaco/kablar-adaptrar/usb/usb2-a-ha-a-ha/USB2-10 (Swedish) - but you have the right part nr. There is possibly tons of things i can think of, and i will be contributing from a total newbe perspective - which I think this wiki will be awesome for. /Daniel

Hi, just registred for this awesome initiative. I have recorded some videos and put on youtube, just as a reminder to myself but also for other to watch - anyone who wan't can use this with my permission. This is how The balance routine works - https://youtu.be/SuIuHkcxjJw Here is a conplete recording of a autopoint,- hopefully without errors? - https://youtu.be/1mrjV1gOUk0 And here is a recording of me running a sequence i have already setup - https://youtu.be/wOgA41y-RpM /Daniel

Yep, up and running in an hour. It might have been me running a Dell Optiplex 960 which doesn't have support for win10, but it worked last weekend??? I realize why i switched to Mac ????

Yep, up and running in an hour. It might have been me running a Dell Optiplex 960 which doesn't have support for win10, but it worked last weekend??? I realize why i switched to Mac ????

Tried all of the above, no change what so ever... I am rollig back to win7 now :/ I had to many strange errors. I had just the mount and the keyboard plugged in to my computer, flushed the com-ports, uninstalled all the drivers, reinstalled, new ftdi, the old ftdi, nothing seems to work. i only hope there is no harm with the mount :/ The powersupply is putting out 13.5v (have a lcd voltmeter added to my power distrubution box)

Ok... this is getting mroe and more worse - now i can't even connect to my mount - i am running win 10 and is getting constantly error 43 - USB device is not recognized by windows... I have tried to reinstall the older ftdi driver located under C:\programx86\Autoslew with no success... No wonder autoslew/the mount have been behaving strange (if this is the problem) anyone seen this behaviour before? /Daniel

Hi, i don't know if i have gotten this dreadful error but i constantly get Error 43 - The USB device isn't recognized by windows10 ​No matter how i try, i constantly getting this error and can't connect to my DDM85. ​I have tried the above guide with no luck... any pointers? /Daniel

The problem is that i haven't been able to do a sucessful synch with SEQ either. The one point i am thinking of might have screwed things up for me is that i Did not restarted autoslew after i set new home position - is this crucial? if the mount doesn't know where it is pointing (even though i have made a manual synch in AS) it isn't that strange that SEQ pinpoint can't solve any images :/ I will check the settings again. Daniel

I set up mine gamepad a while ago but i think i had the same problem, i thought it wasn't moving, but it was, very very slowly. so i had to push a second button on the gamepad to activate a faster slew rate. Some controllers also have a toggle switch to switch between analog mode or digital mode... could be worth checking that to. /Daniel

Hi Mark. The original fl is 700mm f7, which i have mounted a .79 reducer to... so 553mm gives me 1,69 as/px... not 1,64. it was late last night (eyes rolling) No i did not synch sequence (i presume you mean vai the synch-button in the left menu? - i only synched AS with aql aplha and set the new home pos... /Daniel

Hi, i just can't get my head around why on earth i can't make a three-star PA autopoint in seq. I managed to do a 3-star PA a few weekends ago and made the first rough PA (well within 10arc minutes) so the physical mount setup should be ok. the pinpoint Went fine that time. ​the last weekend i tried again with no luck. Now i am wondering if my settings in seq. is off? i ahve a meade 102mm APO with a 0,79 reducer which takes me to a 1.44 as/px with my Atik 460. ​i have lowered the maximum magnitude to 11. ​i did get one succesful solve througout the night thoug. ​initially i do this; ​Power on start AS motors on reset config ​homefind near meridian Aquila Alpha in this case, center and new home pos. heading over to Seq and... well, no luck there. ​What the heck am i doing wrong? Got this error during my "test solve" /Daniel Ps... I might (fingers crossed) have manage to pinpointed out what i have been missing out. I read the manual for AS (again) and have missed to save and closed down autoslew after i set the new home position. Is this crucial? I will also double check my pixelscale - my second calculation ended up with 1,643 as/px

Thanks for your input - so you don't do a synch on a star after you have cleared the old config? maybe thats what's causing my troubles? other than that, i am using the AS version 5.2.2.3. So here is your routine: "First night: Motor on Homefind Clear old config 3-star polar alignment using SEQ - I do a synch on a near meridian star and i new home position before heading over to sequence. Solve frames" - All my solves failed, maybe because of my synch? /Daniel

Si6pack: I have done a homefind, but maybe i have to do another after i have reset the configuration? Motor on Homefind Synch a star near the meridian New home position New home find? Autopoint or manual three star? Christer; I di not use GPS but will check the settings so AS hasn't added a GPS for me / Daniel

I can try to set the "wrong" pier side to see if that solves it... The first star was 0.0 degree dec and 0.3 degree RA off and the second star that much. The strange thing is that last weekend i did a autopoint and that time, it manage to pinpoint the images, not this time :-/ As you see on the image, the reported coordinates from CdC and the coordinates from the mount isn't that faar away, so i presume it isn't any fault between my planetarium and the mount. Seems to be an translation error just like the pierside is wrong, hence the huge errors? The pierside is how ever the right side as reported from autoslew (pierside east) and m counterweight was indeed pointing east.

Ok, did some new test today with zero progress. I reset autoslew and started off from scrath. Choosed a 40 degree dec near the meridian with the right pierside. Synched and set a new home position. Then i tried a synch in sequence but pinpoint couldnt solve that one. I then tried to make a three star pointing model in autoslew, with huge errors, 140degree in dec and 70 min in RA... But i was only 1,3 degree off compared to CdC and the values in autoslew. I have no idea whats going on :-/ I rebooted my pc several times, restarted AS with reseting the configuration each time... Internet time synch and the right observer coordinates is right as well :/

Will check that, just updated to 5.2.2.3 as well. How ever, the autopoint didn't get those huge error values... I did a PA after those values and when the weather allows mw to do a bigger autopoint model i will double check the PA error values again. /Daniel

Hi, just wanna share my latest experience in this jungle of making the right settings in the right order. I was going to make a new PA for the upcoming season here in Sweden. Loaded the old pointing file, slewed to a 40deg Dec star near the meridian, cleared the old config, synched the star with CdC and set the new home pos. Started a new pointingfile, three stars, same Dec, same pierside. Calculated the file and got a neat error of 340 degrees RA and 70 degree Dec. Started over again but checked my location, time, date, old configs... Even in CdC... Everything looked ok. Made the same procedure and with same result (just like Einsteins quote - only a fool expects different results from the same procedure. Well well. Next time, started a new instance of autoslew, cleared config, new CdC instance, synched a star and new home position. But this time, autopoint did a 3 star,msame pier side for me. Calculated the file and got 7x12 degree off... What dis i do wrong? It would make me understand Autoslew if i know what made it go so terrible off. /Daniel

Well, it is a while ago i made my model (end of January) and it worked well quite a few weeks, but as of last night, the tracking was not good. (No error in tracking, just not good) I guess I have to do a model every other month or so. - But why? I should mension that the ice in the ground "might" have altered the concrete/pier... even though it is almost a ton of concrete in the ground it might have moved due to what we here in Sweden call tjällossning So, is this beaviour the same with other mounts? or is it just ASA that looses tracking performance over time? /Daniel

I run 5.2.1.0 on Windows 10, haven't had a single problem. Both windows and Autoslew was a complete fresh install.

Thanks for the tip Mark, i am how ever determined to learn PixInsight and of that reason, i try to get as close to the final result as possible without PS. But then and now, i use Photoshop as well. /Daniel

Hi Christer, i will try a linear fit before combining the RGB, i am after all shooting through the city glow, and the moon was 40-60% during the nights, so it isn't any strange that the blue are a bit off the edge

Thanks for your input Lukas, will probably give it another shot to fine-tune the color levels. I forgot to mension I also use the Teleskoo-service 2" flattener/corrector, giving 550mm fl. Taken from within Arvika, a 4000 residents city. /Daniel