Go Back   IceInSpace > Equipment > Equipment Discussions
Register FAQ Calendar Today's Posts Search

Reply
 
Thread Tools Rating: Thread Rating: 13 votes, 5.00 average.
  #21  
Old 14-12-2014, 10:49 PM
killswitch's Avatar
killswitch (Edison)
Registered User

killswitch is offline
 
Join Date: Feb 2013
Location: Western Sydney, NSW
Posts: 537
Updated the handset to v3.36. I noticed the setup asks for the elevation now. Cant wait to test it out.

Voltage and temp reading is still quite off. The voltage patch lowers the voltage, i need it to read higher.
Reply With Quote
  #22  
Old 18-01-2015, 10:42 PM
cyberblitz's Avatar
cyberblitz
Registered User

cyberblitz is offline
 
Join Date: Aug 2014
Location: Birsbane
Posts: 68
Newb Question on elevation?

What on earth do I put in for elevation on the new fw for Synscan? I have know Idea what this is for.
Reply With Quote
  #23  
Old 23-01-2015, 11:04 AM
Robert9's Avatar
Robert9 (Robert)
Registered User

Robert9 is offline
 
Join Date: Dec 2008
Location: Mt. Waverley, VIC, Australia
Posts: 741
Quote:
Originally Posted by cyberblitz View Post
What on earth do I put in for elevation on the new fw for Synscan? I have know Idea what this is for.
This will be your height above sea-level. The higher you are the more you will see around the horizon. Unless you're not in Brisbane, don't need to worry about it. Put in a nominal if figure if needed, say 25m; that will keep the software happy.
Robert
Reply With Quote
  #24  
Old 23-01-2015, 02:02 PM
SkyWatcherMike (Mike)
SkyWatcher Meade Support

SkyWatcherMike is offline
 
Join Date: Oct 2014
Location: Sydney
Posts: 20
Hi guys,

It would be good if anyone would be able to document the changes in behaviour after 3.27.
I would like to raise these issues with Sky-Watchers engineers and see if we can resolve them.

Regards,
Mike - Sky-Watcher Australia.
Reply With Quote
  #25  
Old 23-01-2015, 03:42 PM
AndrewJ
Watch me post!

AndrewJ is offline
 
Join Date: Mar 2006
Location: Melbourne
Posts: 1,905
Gday Mike

Dunno if it helps, but i was playing with 3.27 and getting really odd behaviour at times when it was applying backlash via the Hbx. ( which may explain why other people also had odd behaviour at times )

I loaded 3.36 and "so far" the lash appears to apply properly but can still take some time. What is Odd ( to me ) tho is it appears they have also changed the commands associated with doing "gotos", and that may have something to do with it???
I am still playing with that tho, as no one i have contacted to date even knows about the new commands, but my mount responds to them.

Andrew Johansen Melbourne Australia
( Using an EQ6Pro )
Reply With Quote
  #26  
Old 23-01-2015, 10:10 PM
rustigsmed's Avatar
rustigsmed (Russell)
Registered User

rustigsmed is offline
 
Join Date: Mar 2012
Location: Mornington Peninsula, Australia
Posts: 3,998
Giving 3.36 a proper go tonight... Have been trying to polar align for 45 mins and not even close to having it sorted, frustrating on a clear night. I would be done in 15 mins tops on 3.35... Not liking this aspect of it as we speak ... When in polar align mode it swings really far away from the star and it does the adjustments in a different order.
Reply With Quote
  #27  
Old 24-01-2015, 01:59 AM
Eden's Avatar
Eden (Brett)
Registered Rambler

Eden is offline
 
Join Date: Jan 2014
Location: Melbourne, Australia
Posts: 399
Hi Russell,

What mount are you using? I've been running 3.36 since November and haven't had any hassles with it on my AZEQ6GT so far.

They did change the polar alignment process slightly a couple of versions back, so that the altitude and azimuth adjustments are broken into separate steps. I preferred it the way it was originally, however Skywatcher are claiming that this method is more accurate.

If the polar alignment tool slews a long way from the star, it's a good indication that your starting point with respect to the pole wasn't ideal to begin with. I recommend adjusting the altitude and azimuth of the mount onto the first star when you do a 2 or 3 star alignment, this will give you a reasonably accurate starting point and should prevent the polar alignment tool from having to make as large a correction on either axis.
Reply With Quote
  #28  
Old 24-01-2015, 11:23 AM
Camelopardalis's Avatar
Camelopardalis (Dunk)
Drifting from the pole

Camelopardalis is offline
 
Join Date: Feb 2013
Location: Brisbane
Posts: 5,479
My experiences with 3.36 aren't very positive either, I just couldn't eliminate the drift after several hours of trying with my NEQ6. I rolled it back to 3.35 and last weekend I was getting 3+ minute subs relatively easily again (it takes me longer than 15 minutes though), just like the last half a dozen times at the same site.
Reply With Quote
  #29  
Old 24-01-2015, 11:28 AM
rustigsmed's Avatar
rustigsmed (Russell)
Registered User

rustigsmed is offline
 
Join Date: Mar 2012
Location: Mornington Peninsula, Australia
Posts: 3,998
Quote:
Originally Posted by Eden View Post
Hi Russell,

What mount are you using? I've been running 3.36 since November and haven't had any hassles with it on my AZEQ6GT so far.

They did change the polar alignment process slightly a couple of versions back, so that the altitude and azimuth adjustments are broken into separate steps. I preferred it the way it was originally, however Skywatcher are claiming that this method is more accurate.

If the polar alignment tool slews a long way from the star, it's a good indication that your starting point with respect to the pole wasn't ideal to begin with. I recommend adjusting the altitude and azimuth of the mount onto the first star when you do a 2 or 3 star alignment, this will give you a reasonably accurate starting point and should prevent the polar alignment tool from having to make as large a correction on either axis.
Hi Eden,
This is with an eq8, yes it does indicate that however in 3.35 it didn't matter how far out you are within a few iterations you were ready to roll - user friendly is the name of the game. As when you were asked to adjust the altitude the mount would only move the altitude, then again for azimuth, not both at once which meant that no matter how far off you would end up going through the cross hairs more or less. 3.36 appears to be wanting to save a step that wasn't really a problem in the first place - I don't like that. I will probably go back to 3.35 and wait for a new update as the cone error feature that was introduced sounds promising.
Reply With Quote
Reply

Bookmarks


Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump


All times are GMT +10. The time is now 11:09 PM.

Powered by vBulletin Version 3.8.7 | Copyright ©2000 - 2025, Jelsoft Enterprises Ltd.
Advertisement
Bintel
Advertisement
Astrophotography Prize
Advertisement