ChristerS Posted January 29, 2016 Report Share Posted January 29, 2016 Hi! Last night I could not connect to my DDM85 using Autoslew, clear sky's of-cause . Everything worked OK except I got the "Could not connect to controller!" error when starting Autoslew. I contacted ASA and got a guide how to fix the problem, they have notices the problem some day ago. Se the attached guide. The guide solved the problem partly, the guide shows how to downgrade to FTDI driver to version 2.8.14, so followed the guide, mount starts up ok. Then I try restart Autoslew still works. Then I power off and on mount the problem appears again! Solution is to reinstall with CDM20814_Setup.exe again (see guide). So it looks like windows reinstalls the newer driver, ver 2.12, when I power off/on but it still shows ver. 2.8.14 in device manager. When I reboot the computer device manager shows the new FDDI ver 2.12. The FTDI is the USB-serial driver Autoslew uses to communicate with the mount. So how do we(ASA) prevent windows from reinstalling driver?? I will google to see what I can find out, let me know if anyone find a solution. I also think this is urgent info for all ASA customer I hope ASA communicate out this information. The final solution is for ASA to add support for the new FTDI 2.12 release. Clear skies! // Christer Link to comment Share on other sites More sharing options...
GeorgeCarey Posted January 29, 2016 Report Share Posted January 29, 2016 I haven't had this error yet, but it is useful information. Thanks Christer. Link to comment Share on other sites More sharing options...
Waldemar Posted January 29, 2016 Report Share Posted January 29, 2016 I get the message that I do not have permission to view that pdf file??? any suggestions? Regards, Waldemar Link to comment Share on other sites More sharing options...
RamaSpaceShip Posted January 29, 2016 Report Share Posted January 29, 2016 Hi Waldemar, I got the exact same message. Any forum administrator to fix this? Bernard Link to comment Share on other sites More sharing options...
ChristerS Posted January 29, 2016 Author Report Share Posted January 29, 2016 Hi, Ok strange, I attach it again and also as zipped. Note is that I'm running on Windows 10, perhaps not a problem with older versions. howto_recover_usb_driver.zip howto_recover_usb_driver.pdf If you are andy with a computer here is a link to one way to fool windows to think the older FTDI driver ASA installs is the newest http://www.rei-labs.net/fixing-the-ftdi-drivers-prevent-auto-updates/ Have not tested yet, perhaps to wait for a solution from ASA BR, //Christer Link to comment Share on other sites More sharing options...
RamaSpaceShip Posted January 29, 2016 Report Share Posted January 29, 2016 Thanks, Christer, I was able to get the pdf file using the new link. Bernard. Link to comment Share on other sites More sharing options...
Waldemar Posted January 29, 2016 Report Share Posted January 29, 2016 Yes, that worked, Thank you Christer BR, Waldemar Link to comment Share on other sites More sharing options...
maxmirot Posted January 30, 2016 Report Share Posted January 30, 2016 Thanks I have the same problem! Link to comment Share on other sites More sharing options...
Corpze Posted January 30, 2016 Report Share Posted January 30, 2016 that´s a close one, i am just installing all software on a new win10 computer, luckily, i saw this thread and got a heads up - Thanks Crister!Is there a way to shut these auto-updates off? It kinda feels like this is not the last time we will se this kind of related errors if win10 starts updating, restarting itself etc./Daniel Link to comment Share on other sites More sharing options...
rharter Posted February 2, 2016 Report Share Posted February 2, 2016 Hi Daniel, in Win 10 Home you can deactivate updates: 1. press "Windows +R" 2. enter "services.msc" 3. look for "Windows update" doubleclick 4. choose "deaktivate" Ralph Link to comment Share on other sites More sharing options...
Corpze Posted September 3, 2016 Report Share Posted September 3, 2016 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 Link to comment Share on other sites More sharing options...
lukepower Posted September 4, 2016 Report Share Posted September 4, 2016 Daniel, try to change the USB cable as a starter. It could be a driver issue, but I would start with the cable. Then check your power supply to the mount. And even, try another USB port on your computer. Link to comment Share on other sites More sharing options...
Corpze Posted September 4, 2016 Report Share Posted September 4, 2016 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) Link to comment Share on other sites More sharing options...
lukepower Posted September 4, 2016 Report Share Posted September 4, 2016 HmmmI would be curious to see if it will work again with Win7... Or if it is a different problem... Link to comment Share on other sites More sharing options...
Corpze Posted September 4, 2016 Report Share Posted September 4, 2016 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 ???? Link to comment Share on other sites More sharing options...
Corpze Posted September 4, 2016 Report Share Posted September 4, 2016 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 ???? Link to comment Share on other sites More sharing options...
Waldemar Posted September 8, 2016 Report Share Posted September 8, 2016 (edited) On my ASUS i7 laptop, running W10. I updated the FTDI driver to the latest version 21216 after deleting the old 208 version... No problems whatsoever! Mac... yes, great machines, but no ASCOM... Running a VM windows on a mac seems a bit weird to me. My ASUS with i7, 16Gb RAM and SSD starts up within 10secs and runs great, I am pleased my old laptop gave up on me so I had to buy a new one and got the best I could affort. I know a laptop like that is a bit overkill, but I use it only for astro and got sick of W7 and 8 problems. Also changed all USB cables and my hub into USB3 cables and a 12V Transcend USB3 hub. I am VERY pleased with these changes!! Makes astro life a lot more pleasing I use 3 different MeanWell power supplies for different applications like: one for the mount only, one for the camera(s) only and another one for the other stuff like dewheaters and focusmotors. Everything is set to ± 12.8 Volts under load. No brown outs or powerdrops to the mount or camera when something else kicks in. I use shielded power cables to prevent any interference or induction. Like I said maybe it is all a bit overkill, but I like to be in a perfect position with my equipment. Too many frustrations crossed my path... enough! You all know that Murphy is the astronomers Patron... Waldemar Edited September 8, 2016 by Waldemar Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now