Last night I started getting repeated errors when starting autoslew. It says
“Axis 1:
Could not connect to controller !
Please check connections and power !
There was a problem during init of the mount
Please check power and connections, continuing in Sim Mode”
This is the same error I would get if I didn’t have the mount connected to the laptop at all.
I am using Autoslew version 5.2.1.9, but I was previously using 5.1.1.6 and got the same error. I am running Windows 10, and I only use this laptop for operating the mount (i.e. I haven’t been installing other software etc).
The power appears to be fine (the light comes on and I’ve measured the 12V supply) and the USB connection also appears to be okay (it appears on Windows Device Manager with the usual FTDI driver). I've tried isolating the problem by removing the only other USB connection (my FLI camera) and the problem persists.
I’ve tried changing sockets, changing 12V supplies (I’ve checked the voltage with my voltmeter), rolled back the last update of Windows 10 and re-installed ASCOM 6 and Autoslew (including drivers) a number of times. I've manually changed COM ports on the Autoslew initiation files to agree with Device Manager too. Nothing appears to be working.
Has anybody come across this error? It looks like one I've solved before just by re-starting the laptop- i.e. in the past it seemed to be software related, and at a guess the USB drivers were getting themselves tied into knots.
As a final check I removed the back panel of the DDM60 and I could see a red light coming on when I plugged in the USB, and it turned green when I turned on the power. Assuming this is the designed behaviour (seems logical to me), I am still thinking it must be a software issue somehow.
Question
asgr
Hi,
Last night I started getting repeated errors when starting autoslew. It says
“Axis 1:
Could not connect to controller !
Please check connections and power !
There was a problem during init of the mount
Please check power and connections, continuing in Sim Mode”
This is the same error I would get if I didn’t have the mount connected to the laptop at all.
I am using Autoslew version 5.2.1.9, but I was previously using 5.1.1.6 and got the same error. I am running Windows 10, and I only use this laptop for operating the mount (i.e. I haven’t been installing other software etc).
The power appears to be fine (the light comes on and I’ve measured the 12V supply) and the USB connection also appears to be okay (it appears on Windows Device Manager with the usual FTDI driver). I've tried isolating the problem by removing the only other USB connection (my FLI camera) and the problem persists.
I’ve tried changing sockets, changing 12V supplies (I’ve checked the voltage with my voltmeter), rolled back the last update of Windows 10 and re-installed ASCOM 6 and Autoslew (including drivers) a number of times. I've manually changed COM ports on the Autoslew initiation files to agree with Device Manager too. Nothing appears to be working.
Has anybody come across this error? It looks like one I've solved before just by re-starting the laptop- i.e. in the past it seemed to be software related, and at a guess the USB drivers were getting themselves tied into knots.
As a final check I removed the back panel of the DDM60 and I could see a red light coming on when I plugged in the USB, and it turned green when I turned on the power. Assuming this is the designed behaviour (seems logical to me), I am still thinking it must be a software issue somehow.
Any help is much appreciated,
Aaron
Link to comment
Share on other sites
2 answers to this question
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