Synscan error

[Marc8667]

I have a 200p on an EQ5 which I've upgraded with the EQ5 upgrade kit. I had no problems fitting it and I went out and tried it that night. I did a rough polar alignment and inputted my coordinates and date and time correctly. After I had done a 2 star alignment and it said alignment successful it came up with the message RA offset by 45 degrees. I ignored this and went to find M42 and M81/82 without any problems.

Has this ever happen to anyone else?

[malc-c]

When you first turned the unit on how did you have the scope set up. It assumes the parking position is with the tube pointing along the polar axis, ie with the weight bar vertical when viewed from the front with the tube pointing North / south. Turn on the synscan and perform a two star alignment and see if it reports the same error

[Marc8667]

Hi Malc.c.

Thanks for the reply. When I first turned it on it was in the home position as you described. I parked the scope just to make sure that it knows the home position and it was spot on. I've done a one star, two star and three star alignment and I still get the same message.

It finds objects with no problems and is very accurate, even with a rough polar alignment it still puts objects near enough in the centre of the eyepiece. I was considering re flashing the software to see if that cures the problem.

All in all it works fine even when the message comes up, I was wondering if anyone else had come across it.

Thanks for your help.

Marc.

[malc-c]

A quick google came up with this...

http://stargazerslounge.com/beginners-help-advice/106451-ra-offset-45-a.html

Does seem to be a parking / reffernce issue -

[MikeWilson]

Check that you have the EQ firmware on the SynScan hand controller. Did you reflash it accidentally with AZ firmware?

It sounds to me like your hand controller is running the AZ firmware. Check the firmware version on the hand controller and let us know what it says

[Marc8667]

I've checked the firmware and it's EQ version 3.27. I have re-flashed it and it's seems to have sorted the problem out. It worked perfectly when I tried it out Monday night.

Thanks for all the help.

Marc.