noah4x4

Up until now I had merely dabbled using a Nexstar Burst Colour. I had secured a few hazy images of Jupiter & Saturn, but they were always disappointing. This is my very first ever effort with an unmodified Nikon D5200 DSLR in a Celestron Evolution 8". It was a single 8 second exposure at ISO 1600. The only subsequent processing has been conversion to JPEG and significant cropping. Now awaiting delivery of my wedge so my tracking will be better and to permit longer exposures and the stacking of multiple images. But for a very first attempt it blew my socks off with surprise. I am very familiar with the Orion Nebula, but to capture some colour was unexpected.

Much if the illustration content of "Turn Right at Orion" can be found on line. http://www.cambridge.org/features/turnleft/

Works fine for me. But SkyPortal can be a bit fussy. So try SkySafari for Android. Same software producer, but much better than the free SkyPortal. The budget 'plus' version is excellent. No need to spend ££££'s on the 'pro' version that adds many more objects but you do need a big scope to benefit.

I assume you are referring to the Evolution's widely publicised (original) WiFi woes? My understanding is that gen2 versions have an improved more powerful antenna. However, a few retailers are still getting rid of their old stocks of gen1. You are likely to have a gen1 if the supplied Nexstar + HC has an older RS232 port. Later versions tend to have a mini USB output. But if you do have a gen1, don't despair. I spent six months struggling to keep my Android tablet connected to mine. I followed all the guidance, like "forget" your home network. I still couldn't stay connected for long. I concluded that my urban "Wi-Fi clutter" was too great. So I gave up, switched to HC and simply used SkyPortal/SkySafari OFF-LINE. It was a good move in one respect as the best way to learn about your scope is by using the HC. However, I then discovered that buried deep in my tablet amongst the packaged rubbish loaded by my Telecoms supplier was a 'Battery saving' APP that turned off other APPS after n minutes of IN-activity. This was disconnecting SkyPortal/SkySafari after about five minutes of looking through an EP. Of course, I stayed connected for longer if I did something else (like an adjusting slew or sought information etc). Since I deleted that APP, I have lost connection only once! I have spoken to both Celestron and Simulation Curriculum about this and neither had considered this possibility. But are about to include this guidance within future packaging. There are dozens of these nuisance APPS, none are native to IOS or Android 'Lollipop'. They tend to be buried pretty deep, so can be hard to find and disable. This isn't to say that "WiFi clutter" isn't a problem, simply that in a good many cases this isn't the problem. As I said my Evo now works perfectly with my Android tablet and despite cursing Celestron for six months the issues were not of their making.

Starsense merely addresses initial alignment. Your subsequent GoTo's are limited by your mount and it's settings. What has become apparent to me since my earlier post is that (my) SkyPortal or SkySafari are set to a generic "Celestron WiFi" telescope. This obviously means any warnings about slew limits are set conservatively for the lowest common denominator of all compatible scopes in the Celestron range. So although object XYZ might be amongst "tonight's best" it might be outside the slew limits of some scopes, but not for all. I can imagine the current position of M31 might exceed your unique user defined (or default) slew limits. But using HC directional controls, (easier than with tablet) you would be wise to learn what those limits are for various EP's and devices. Example; what I have also discovered since my earlier post is that my Evolution mount has a neat scooped out channel (that can hold spare EPs) in the top of the mount base, which allows enough clearance for me to go right to the Zenith even with a large Televue Delos 8mm EP. But I could not do that with my more limited Nexstar SE4. So do push the envelope, Just take care if you ignore such warnings. But what you describe is routine good accuracy, but inaccuracy when near to the zenith. I have read about this in other forums, but have never suffered myself. I attribute this to having added ten additional alignment points ( via Starsense) in ten different constellations that appear to chase each other most evenings/seasons. I gather this is a bit like SYNC function which improves accuracy around a particular alignment star. The joy here is you can add ten, and Starsense remembers all. One close to the Zenith will assist. One other thought, in my light polluted urban location I often struggle to make out anything other than a bit of circular hazy glare from the Andromeda Galaxy's central core. Also don't underestimate it's size. If using too powerful magnification it could be that you can't see it's elongated shape because all is outside your FOV in EVERY direction. It took me ages to discover the joys of using 32mm and 40mm EP'S. I will never forget telling Starsense/GoTo to find the Orion Nebula; then wondering where it was, before discovering that was simply because in my scope I could fill it's aperture with just the four central stars of the Trapesium. I had to drop from 200x to around 64x to fit it all in and even then it's two extending arms were outside the FOV.

Hi Ian, agree with all you say, and I am so glad it is now working for you via Android/WiFi. But for now, I think I will probably continue to depend on the StarSense HC (which has proved 100% reliable for me) and use SkyPortal for Android (WiFi) as merely an off-line guide (with audio etc.) to the skies. But can we touch base again in here in perhaps a month and compare notes when you have enjoyed a sustained period of trouble free WiFi/Android control of your Evolution? I think that we can be of great assistance to the community of Evo' owners, albeit testing Starsense control for the Evo' from opposite sides. This topic has filled many forum threads since 2014. I am not suggesting that the 'access point' approach to fixing WiFi connectivity issues isn't a perfect solution in many circumstances, but I have encountered some unexplained wild slews when under Android/WiFi control even when the 'location' etc. is prior set correctly in both the HC and Android and I simply don't know why. I fear this issue could be beyond Starsense failing to pick up 'location' from the tablet. Here I stress to other interested readers, Starsense via the HC on my Evo or SE 4 is just awesome. I have heard its good when hard wired to the HC. It's when under WiFi/ Sky Portal that makes me a little nervous. The lack of tactile feedback obviously isn't helpful on a tablet and I am a bit fearful that if the WiFi did fail, then I might lose control. I also have a CCTV system that uses 'access point' connectivity to my home network that I can then monitor remotely on any Internet connected device, but that too quite regularly 'drops out' on my Android but strangely, never on my Windows laptop. Here I warn any prospective burglars that it is still recording to disc and that is beaming shots to a central station. But what if I had the same loss of control with my OTA? Let me expand on that... Sky Portal (off-line) once told me; having correctly set its time/date & location in my Android device; that the Andromeda Galaxy was one of 'Tonight's Best'. My HC time/date/ location was set correctly too. But when I tried to GoTo using the HC it rightly warned me "will exceed slew limits". I am hence nervous about attempting this equivalent GoTo when under solely Android control. How can an object be in both "Tonight's Best" and yet "beyond slew limits'? Frankly, there is probably zero concern about any of the above, and one hopes the Android (like the HC) would similarly warn about exceeding slew limitation too. But the fact that it won't reliably determine 'location'' from the Android even when its GPS is live doesn't inspire me with confidence. Indeed I wonder how reliable Sky Portal is as regards any objects very close to the artificial horizon, which is depicted on my Android screen as a mountainous background (errr....what mountains in Essex!!!!)? Maybe I am being over cautious, but I don't want to risk watching a monster 1lb Televue EP smash into my mount and damage my OTA. In summary, enjoy Android WiFi control, but I suggest you don't stray too far from the telescope on/off button until 100% confident. It would hence be good to get your feedback that all is well after a few more sessions. But it does seem odd that Celestron are not placing far more emphasis on 'access point' connectivity as a primary solution. There is no mention under "WiiFi tips and only trivial mention in the Evo manual. Be cautious using tablet/WiFi. But the Evo + Starsense using the HC is simply awesome.

Isn't it a tragedy that the Celestron manuals are so awful! I will try your Evolution Wi-Fi solution Ian, but my BT Home hub is so rubbish I won't hold my breath! Whatever the 'settings' in my Android, it does seems to ignore 'location' on any second use. It only asks for that on first use, and I assume the HC setting then takes precedence. Like most people with this technology, I started ONLY with Android control for my Evo', but I obviously got it wrong first up, so the HC/scope remained in 'California', But given there is no further prompt on subsequent use to check/change 'location' via Android (or HC) I suffered wild slews like you. Puzzling, because the Android was always correctly set to North Essex by Long/Lat. So one naturally assumes it's a more sinister issue. Retailers must hate this! To be frank, I didn't work it out until I took my 'grab & go' NextStar SE4 to the Lake District where I couldn't use WiFi/Android as it doesn't have this Evo' feature. As this was the first time I had moved a scope with StarSense far enough for 'location' to be an issue, it forced me to grab the Starsense manual to find out how to change this (via HC). Stood in freezing temperatures doesn't inspire one to read all to page 26 and find the 'menu tree' , but I did. Prior to this I had also been puzzled by a dozen other irrelevant Evo' issues (like flaky WiFi, or 'lock ups' caused by doing the alignment via Android then accidently touching a HC button). You perhaps need to get away from such confusing WiFi bewilderment to work this out. I would advise all (new) Evo' owners to make their initial 'settings' via HC. Then until they have it spot on, and understand the criticality of time/date & location & calibration; don't attempt to use a tablet. Fortunately, I was in the Lake District the weekend DST changed, else I might not have so quickly worked out why all my GOTO objects were 15 degrees west! Now it all works - fantastic. I pop my Evo' tripod on three marks on my patio; check location (via menu). Press Auto Align, enter date/time; then head off to put the kettle on. Then I wow my pals when I click solarsystem/jupiter and it's smack in the middle of my Televue 8mm Delos. On reflection, my Android/Sky Portal and WiFi has become redundant other than as a star chart. I think it's more fun that way too, and the risk of stepping on my expensive Android is eliminated. Stargazing shouldn't need three hands, and accurately swiping a tablet slew button with a finger having one eye down an EP is as difficult as a circus trick can get. I reckon Evo' WiFi is unnecessary, as I use SkyPortal offline. BTW, I now fasten the HC cradle to the upright grab handle rather than tripod leg. No cord wrap from HC or battery = Evo' bliss. Hence the confidence to leave it and make tea.

Maybe I have just confirmed what you already know! But that should assist as the doubt and frustration is agony. But I forgot something... Sorry, What I didn't say was you might need to reset location via your tablet. But note that it doesn't seem to pick it up from the normal SkyPortal 'settings' except on FIRST use,. But that glitch is exactly the same via the HC which seeks only time/date on any subsequent use (do before 'align' or 'connect and align'). With the HC, you hence need to go via 'menu' to reset location as you otherwise don't get a second chance during 'align'.. I have not checked this as I gave up with WiFi (local interference too great) but I suspect you may have to do so on-line on Sky Portal via a route other than via 'settings'. I am confident this problem is about location and it not taking that data from the tablet whilst ignoring the HC.. I too am in North Essex, so happy to compare notes. You might even need to do a factory reset if you want to persevere with WiFi to get back to a first use scenario. BTW, I have heard these problems don't occur with the stand alone WiFi accessory which is shielded from interference differently. This confirms a comment above.

Been there too with my Evo 8 and its Starsense. Frustrating to resolve such issues between too few clear nights. But fortunately I also have an SE4 with Starsense, so I have eventually worked it out (I think); and I now get 100% accuracy with both telescopes. Your problems probably relate to one (or all) of time/date; location; and calibration. On first use with the hand controller (HC), you get opportunity to set these. Frankly, I can't remember if it's the same on first use with Wi-Fi/Android/I-Pad, but on ANY second attempt StarSense will remember camera calibration and location. That's fine if you have set those correctly. I am not embarrassed to say I forgot to take off the StarSense camera lens cap on first attempt! It then doesn't ask you again for these settings (other than time/date). Mine hence remained set to a California default. Ooops! No wonder my OTA looked in the wrong direction. Here, the manual is useless. You possibly now need to set location via ''menu' before your next 'auto align' and once again do 'calibrate' and 'align' again. Do so using the handset. Take account of daylight saving time, else all your GOTOS will be 15 degrees west of FOV (e.g. one hour). If you instead attempt to use the Wi-Fi, and SkyPortal, your initial options are only 'align' or 'connect and align'. So If the HC still holds the wrong location and calibration data it doesn't over write it. Your tablet GPS might also disagree with the HC data. Always enter longitude and latitude, as there are not enough (UK) 'city' options in StarSense for perfection (unless you live in London or Glasgow). Also check your tablet and HC is correctly set to current time and current location. I came back from Vietnam and nearly crocked my scope as it looked beyond the equator. To add to the complications, if you don't tell your tablet to 'forget' your home Wi-Fi network, you will probably suffer conflicts and drop outs. If your locality is very Wi-Fi cluttered, other networks might interfere. Failed or flakey Wi-Fi might also leave you with incorrect or incomplete stored data. So I suggest you use ONLY the handset to set location and get calibration resolved, even if you do intend to use ONLY Wi-Fi on third use. Once set, then don't try to use both HC and Tablet in the same session. The temptation to do so exists when you discover it is hard to manage slew controls on a tablet due to having no tactile finger feedback. Yes, the HC slew buttons will work, but touch any other button and your Evo' will lock up and slew wildly due to the conflict between controllers. You really must use only one or other controller. To be frank, I eventually gave up with SkyPortal and Wi-Fi. I now use that OFF-LINE simply to guide me. I now use only the StarSense HC for control, always checking location (via menu) before 'align'. I can still read and hear all the SkyPortal APP information. But it's just as easy to navigate using only the HC. The other features of the Evo are so good, who actualy needs it's W-Fi (e.g. manual clutches, built in battery etc). Lastly, when setting time/date and location, remember 'back' means accept the stored data and go forward (illogical!). 'Enter' means go back and change settings. The manual must have been translated from Chinese. But it's fantastic to do a Sky Tour (via HC) and have every GOTOS smack in the middle of your EP when ALL your settings are correct. Of course, there could be a fault, but that's less likely. Hope this helps.