"Both Axis No Response" - Orion goto dob

[Walker]

Hello dear members, seeking some help here from your experiences. I have an Orion xx12g that has gone kaput. Been throwing this error Both Axis, No Response. I saw a classified of one with similar error, but unable to get response from the OP of that post.

Have tried replacing the cables, no difference. Also tried using skywatcher usb adaptor, but my laptop fails to recognise it (hadn't used that adaptor before).

Every suggestion is much appreciated. Thanks.

[iborg (Philip)]

Hi Kit (The Ghost Who Walks)

I don't really have an answer for you, but, a suggestion is put a voltmeter on your battery.

Check the voltage with nothing connected, then try to power up. While powering up and trying to move the scope, see if the voltage drops significantly.

Just possibly, your battery will test OK with no load attached, but, if it is failing, it may have too low a voltage while the motors are pulling a current.

This might give the error message you are seeing


You could also try unplugging all the internal cables and re-plugging them. Just might be a loose contact somewhere.



Good luck


Philip

[Drac0 (Mark)]

I hope you are lucky & it's only a voltage issue or poor connection somewhere. Last time I had this on a mount it was the main controller board that was shot & had to be replaced.

Cheers,
Mark

[Startrek (Martin)]

I’ve just got my 7 year old SW 12” Goto Dob up and running after 5 months of ripping my hair out
My scope had multiple issues but the first issue was “ Both Axis no response “
Jumped on Cloudy Nights, Stargazers Lounge etc etc for clues.
This is what I did …,
Upgraded the firmware on my V5 handcontroller ( see attached )
I didn’t upgrade the motor firmware as I couldn’t find the upgrade for a 12” Goto Dob on SW website , so I didn’t do that !!
Replaced the power supply ( Powertech 12V 7.5amp power adapter)
Then I replaced the handcontroller cable
Then I replaced the motor cable ( RJ45 ) from the Alt drive to the Azimuth drive.
Cables and cable connections are a common issue with is warning “Both Axis No Response”
Also check for mould and corrosion on all connections too ( internal and external)
I even pulled my handcontroller apart and cleaned all the tactile points etc..

Finally after all this was done I powered up the scope and at least got it up and running , however the next issue was scope would not change speed in Azimuth when HC changed from default Rate 9 fast to lower speeds say Rate 5 to Rate 2 , it stayed at Rate 9 fast speed even though the handcontroller read the correct rate.
Replaced handcontroller with new
Replaced Az motor board with new
Cleaned all contacts
Checked supply voltages
Still couldn’t find the source of the problem. I even disconnected the encoders which disabled the scope , so plugged them back in again.
Skywatcher ( Graeme ) and Testar ( Adriano ) were very helpful !!
In the end had to buy a new Base unit
Scope is working like a dream now after 5 months but at a cost of $2,300 and endless hours in the garage.
My post regarding my issues is in this section 4 or 5 posts previous to yours.

Maybe try the HC firmware upgrade and replacement of cables plus check connections first and foremost. Before throwing money at it

Good luck

Martin

[justintas (Justin)]

Hi , I had a similar problem with my 12" Goto I followed this thread https://stargazerslounge.com/topic/3...board/page/17/

The first thing I would check is the ALT motherboard to make sure it is not blown as mine was. Remove cover and carefully remove baord noting location of cables. If it is blown get in contact with Testar ( Adriano ) he was very helpful and supplied new boards to me. Fitted them yesterday and scope works perfectly.

Hope that helps
Cheers Justin

[Walker]

Thanks. I hope that's the case. Will take rhe electronics apart and look for any sign.

Originally Posted by Drac0

I hope you are lucky & it's only a voltage issue or poor connection somewhere. Last time I had this on a mount it was the main controller board that was shot & had to be replaced.

Cheers,
Mark

[Walker]

Thanks, Martin. I have rried replacing cables, that didn't do anything. Will try updating the firmware on synscan.

Originally Posted by Startrek

I’ve just got my 7 year old SW 12” Goto Dob up and running after 5 months of ripping my hair out
My scope had multiple issues but the first issue was “ Both Axis no response “
Jumped on Cloudy Nights, Stargazers Lounge etc etc for clues.
This is what I did …,
Upgraded the firmware on my V5 handcontroller ( see attached )
I didn’t upgrade the motor firmware as I couldn’t find the upgrade for a 12” Goto Dob on SW website , so I didn’t do that !!
Replaced the power supply ( Powertech 12V 7.5amp power adapter)
Then I replaced the handcontroller cable
Then I replaced the motor cable ( RJ45 ) from the Alt drive to the Azimuth drive.
Cables and cable connections are a common issue with is warning “Both Axis No Response”
Also check for mould and corrosion on all connections too ( internal and external)
I even pulled my handcontroller apart and cleaned all the tactile points etc..

Finally after all this was done I powered up the scope and at least got it up and running , however the next issue was scope would not change speed in Azimuth when HC changed from default Rate 9 fast to lower speeds say Rate 5 to Rate 2 , it stayed at Rate 9 fast speed even though the handcontroller read the correct rate.
Replaced handcontroller with new
Replaced Az motor board with new
Cleaned all contacts
Checked supply voltages
Still couldn’t find the source of the problem. I even disconnected the encoders which disabled the scope , so plugged them back in again.
Skywatcher ( Graeme ) and Testar ( Adriano ) were very helpful !!
In the end had to buy a new Base unit
Scope is working like a dream now after 5 months but at a cost of $2,300 and endless hours in the garage.
My post regarding my issues is in this section 4 or 5 posts previous to yours.

Maybe try the HC firmware upgrade and replacement of cables plus check connections first and foremost. Before throwing money at it

Good luck

Martin

[Walker]

Thanks, everyone. I did try using my synscan from EQ8, and that gave the same error. Making me think that it could be the board ☹️