Search the Community
Showing results for tags 'error'.
Found 6 results
Anyone out there replaced the Motherboard on an Orion GoTO truss tobe Dobsonian, our Societys 16" started giving error messages stating it could not connect to either axis, we ordered and replaced the Motherboard which promptly "burnt" out, we are seeking a repair (believe this is basically a re-branded Skywatcher) any advise or help greatly appreciated.
A possible solution for the dreaded Bootloader Serial Invalid Pkg 00*0 errors on Celestron HC's, thanks to Carl Randall on the Cloudy Nights forum! Seems to work for all types of mounts (not only AVX)! http://www.cloudynights.com/topic/527834-avx-hand-controller-issue/#entry7058700
Hi all, I captured around 4000 frames in liveview mode while shooting at the Moon, with Camera / 2xBarlow / Telescope. Then cropped them in PIPP and created an AVI file to export after to Registax. The video file, even after cropped and centered, is not very stable (i guess because it was windy?), u can see the Moon is misplaced in a few frames, but nothing really serious, in my guessing. So, when i pass it to Registax 6, i do the normal process that i already did for saturn and for full lunar disc, (Align, choose a decent amount of align points, limit to 95% quality or best frames, etc). Thing is, the final result is something really odd, with the Moon not even entering the final pic. Somewhere along the alignment points process there is a problem that i dont have the knowledge to solve, and you can see the green lines of alignment going way out of the picture for some reason. I only had time to printscreen one shot before coming to work, and looks like this: Some alignment details were, as i remember: default minimum number of pix between alignment points - 30 from edge - 20 chose around 100 alignment points automatically (in some cases, there was one in a black area, but i tried right clicking in order to delete it,but it wouldnt do anything) So, i wonder if i could get any help from you guys! Would be much appreciated. Thanks, Rui
Hi Everyone, Just wanted to post my experiences with the Celestron AVX+Advanced GT and Celestron's Firmware Manager (CFM) - Specifically Boot Loader Errors I've used Celestron's Advanced GT Mount for a few years and only had a Boot Loader error once. The Good people at FLO re-flashed my handset and away I went. Happy camper Before getting in touch with FLO, I tried desperately for days to try and re-flash myself (I've worked as an IT hardware repair technician for years so i'm not an id10T but I am certainly no programmer/software engineer). I used probably every version of CFM available and every version of windows / XP, Vista, 7, 8, 10 (also contacted Celestron and had 2 people sending me links to CFM - they couldn't figure it out!) also I should point out i was using 3 different computers AND 2 completely different cables lol. I never managed to update my handset due to - freezing / crashing / mount not detected and the general instability of CFM. Now on to my AVX. I'm very happy with it overall but i've only had it a few weeks. Tonight it threw a Boot Loader error at me (just as i was about to start collecting data on Andromeda ) - very similar if not exactly the same as my older Advanced GT. ahh....SO it's ok i'm thinking! I just re-flash! Hmmmm lol now my re-flash worked sort of and I now get "Advanced GT" on the screen with an error 17 "No response invalid model" Personally I think CFM is JUNK (I've seen more stability/reliability with windows vista and an 8800GT playing Crysis 1 lol) it has taken me 5 years and 2 mounts to come to that conclusion. What are we to do if we plan a trip and the skies are just right - then (BOOT LOADER ERROR) pops up? Anyone else had any similar experiences or feel frustrated by this? Sure if you can re-flash in 10mins then your good to go but what if that ends your trip and AP session? There is no way i'm alone in this Thanks for reading and please share your experiences! Nuka
I've been guiding using PHD on my EQ5 & Orion Starshoot Autoguider for a while. I recently hooked up a QHY5-ll to do some planetary work om my main scope using SharpCap (successfully). However since then I've gone back to my deep sky work and the AutoGuiding is now failing with an Error - 22 (sometimes when connecting the camera and sometimes when trying to calibrate). Last night, having got past the error 22 on connection (connected the Orion late after starting the App) I then got an "start didn't move enough" error even though the settings hadn't changed from when I successfully guided (as far as I can remember). Also using the same cables to the same Win10 laptop. Not sure if the QHY camera is a red herring or a possible cause. Any pointers would be appreciated.
My Nexstar Evolution handset just decided to give me this message 'boot loader serial invalid pkg 0080'. I assume there's a way to fix it. I got no wires or connections when the scope came so I have no idea how to hook it up to my laptop or which connection to buy.