LucMurphy

Sorry Robert I don't remember. And even it were yesterday, I probably coudn't tell what exactly did work. I uninstall/reinstall multiple the gps and virtural port drivers, i reverted back to an earlier version au autoslew, re-install it, try multiple usb port, tried another laptop that had the exact same system image, and other stuff i don't remember, it just started to work again... I hope you found it. Stay healthy Luc

DaveS, You mentionned that you don't have a motored focuser. If this is the case, you might have the same issue that i had while I was "in between" telescopes setup and waiting for the all the gear for a new focuser for the new telescope. By reviewing the sequence log, I figured out that Sequence was most likely expecting a focuser to be connected. After a few trials, I "installed" the ASCOM focuser simulator. ASCOM POTH has 2 focuser simulators, be sure to select the ASCOM one. In the "Current Location" setup tab, check "focuser installed", choose the ASCOM focuser simulator and verify that Sequence recognize the focuser when connecting (the focuser icon on the main page should become yellow-orange). In the "Focuser \ Autofocus during Sequence" tab, check Never and uncheck Begin Sequence with PreFocus Check. When setting your Target file, AutoSelect a focus star. The rest of the settings should be aligned for you telescope\camera. Hope this help. Luc You mentionned that you don't have a motored focuser. If this is the case, you might have the same issue that i had while I was "in between" telescopes setup and waiting for the all the gear for a new focuser. By reviewing the sequence log, I figured out that Sequence was most likely expecting a focuser to be connected. After a few trials, I "installed" the ASCOM focuser simulator. ASCOM POTH has 2 focuser simulators, be sure to select the ASCOM one. In the Current Location setup tab, check "focuser installed", choose the ASCOM focuser simulator and verify that Sequence recognize the focuser when connecting (the focuser icon on the main page should become yellow-orange). In the "Focuser \ Autofocus during Sequence" tab, check Never and uncheck Begin Sequence with PreFocus Check. When setting your Target file, AutoSelect a focus star. The rest of the settings should be the

Very nice!

Hi Mark, Not a trivial question at all actually but stranger than your answer suggests. The comport assigned to the virtual port device in Device Manager is not visible in Autoslew! (for completeness, the virtual port device is needed because the GPS can't talk directly program that communicate trhoug comport like Autoslew). Device manager also sees the GPS sensor (under the sensor grou). I had the same issue as you for connecting directly to the latop, but in my latest trails, both configurations (direct to laptop and usb connector) were tried. Although my usb cable was not heavily shielded. I will try that. Thanks Luc

Good evening fellow ASAer, I recently got a an issue with the GPS USB dongle. Autoslew is no longer "seeing" the GPS. The GPS sensor and Virtual Com port are both visible in Device Manager. To make sure it wasn't a driver issue, I downloaded the latest drivers from u-blox. I run Autoslew 5247 and Window 10. Anyone got a similar issue and have an idea? Luc

Got it! Believe it or not, it was a "cultural" issue. The Win 10 that was installed is the French version (even though I had the Win 7 English version) which handle the decimal point with a coma instead of a period. Visual Basic doesn't like. I change the language pack, and everything works perfectly now, including AS 5222. Thanks to this community for the support. Luc

Hi All, I got Win 10. Did not ask for it but got it anyway eventhough I always refused the autoupdate. In anycase, AS doesn't work. I tried the USB backward update as described in "how to recover the usb control". Nothing. Uninstalled AS 5222 to re-install 5219 and 5218 with going through the USB fix. Nothing. And i mean nothing. I am not even getting the error message "could not connect to controller". AS crashes after a fraction of second. I get the same thing if I connected to the mount or not. Any suggestion? Before reverting back to Win 7 I would like to give Win 10 a try because I read that PixInsight in no longer officially supporfting Win7. Thanks Luc

Yes it is possible. I had to replace the stock FLI Camera power cable because it is fairly rigid in warm temperature but it is getting solid in sub-zero temperature. Even with good cable management, it was dragging the mount. To make sure, you need to do a "time flex" measurement (in Sequence). The default parameter is measuring time flex when the tube points toward the zenith. To perform a better diagnosis, you may have to measure 2 or 3 more positions. The different positions will induce different tension in the cable (or should at least) and therefore should produce a different time flex measurement. Regards Luc

I concur with George. Even if you do not feel any wobble, the mechanical device that moves the mount up or down (being an electrical motor or hydro-mechanical piston) will take time to settle to a final resting position. Even worst, you could have minuscule slippage in the up position. I suggest that you do a flexure measurement with the mount in the most stable position (down) after several hours on being in that position and see what happens. Which brings me to a totally different subject. If I interpret the picture correctly, the imaging train is: Focal reducer OAG Focuser Filter wheel Shutter (the 65mm i believe) Camera Have you made sure that the back focus is 146 mm as per Celestron specs? Celestron has designed their focal reducer to have the same back focus with or without it: so it's 146 mm starting from the reducer flange.

I don't think you have a balancing issue, or at least not a big one. From my experience with a similar albeit scaled down setup (DDM60+C11), if you are getting the red lines reasonably close (let's say From what you wrote, I think the issue is flexure in the imaging train, not mount inbalance. You live in Utah which get freezing temperature at night. Is it possible that you went from 5" flexure to 30" from summer to winter? Don't laugh, that is what happen to me. I made several mod to improve the rigidity of my setup (documented in another email trail) but the biggest contributor was cable management that were getting hard in cold temperature and "pulling" on the tube therefore inducing flexure. In particular, the power cable of the FLI camera was getting rock solid in freezing temperature. I tried 2-3 setup but I ended up replacing the power cable (I know,I know, this invalidate the warranty) that went from the transformer box (which in sitting on the mount base) to the camera with a cold resistant cable that stays flexible down to -50 C. Problem solved. I am getting consistent 10 min unguided subs in any position. 15 min unguided is less successful but still in the 75% range. For my 20 min Ha, I have to guide though. The AP1200 mount will not remove the flexure issue. It will simply hide it by the off-axis-guiding. I hope this help a bit. Luc

I was just thinking about the same. How we going to have a Christmas gift under the tree next week? Luc

I kind of recollect that one DDM85 user had reported 45 min unguided subs with a C14 but i can't find the post in this forum. maybe it was in the old yahoo forum

I second Jay's recommendation to use Sequence hysteris and time flex measure tools. If you already are able to acheive subs of 400 sec undguide, it probably means that the hysteris is pretty much under control. To improve, first you need to measure timeflex before doing anything (that will be your baseline), try changes to your setup (hoping it will improve the ridigity) and measure timeflex again to see if the change had any effect or not. This is the only way because time flexure cannot be cancel with MLTP. In the world we are leaving, more expensive usually means better... but not always. In the old yahoo forum, there is an email exchange between P. Keller and a Tak FSQ-106 owner that couldn't get long un-guided subs (do not remember exactly how long, but it was much shorter than what you would expect for a short fl tube). In the end, they concluded that the Tak focuser was the issue.

Hi, To compare apple with apple, you should also add the length of the tube (moment of inertia) and the equipment weight ratio. OTA: C11 HD; fl = 1800 mm; 067"/pix; in my part of the world, the scope must have dew shield. It doesn't seems much but the shield those increase significantly the moment of inertia. Mount: DDM60 non-pro mounted on a "permanent" tripod (moving to a permanent pier soon) 80 points file Weight ratio = approx. 80% (equipment weight to DDM payload capacity) I get very consistent 10 min sub and about 75% success rate for 15 min sub. I did achieve 20 min, but the results are not consistent enough. I define "success" with a roundness of 0.1 or less as measure by Maxim. But what I found out that had the most influence on my setup was the rigidity of your whole setup. It is harder to compare apple with apple when talking about setup rigidity but here what I did to improve my setup that may help you with your C14. * Added a second dovetail on the top of the tube. Didn't use Celestron dovetail, they are crap. * Remove the ASA female dovetail and screwed scope bottom dovetail directly to the head of the DDM60. * Even though the EdgeHD has two mirror lock, they are not sufficient to prevent mirror sag over 10 min, Therefore, I added 3 "fingers" inside the tube to prevent mirror sag. * The secondary mirror alignment was done in such a way that it is no longer floating ( (always by tightening the screws). * Cable management: repalce the FLI power cable which was becoming rigid as a rock in sub-zero temp and inducing drift; i have one power cable bundle on one side of the tube and one data cable bundle on the other side of the tube. Regards Luc

Hi Jay, How to get MaxPilote to run Sequence and create a new MLPT (if you do)? Thanks Luc