Jump to content

Stargazers Lounge Uses Cookies

Like most websites, SGL uses cookies in order to deliver a secure, personalised service, to provide social media functions and to analyse our traffic. Continued use of SGL indicates your acceptance of our cookie policy.

sgl_imaging_challenge_celestial_motion.thumb.jpg.a9e9349c45f96ed7928eb32f1baf76ed.jpg

dragorom7

Need help ASCOM for Stellarium Telescope Control

Recommended Posts

Hello, i am new to this forum, i made my account here because i need help.

So few weeks ago i ordered a USB to Serial cable to be able to Control my Telescope with my computer using stellarium.

It arrived today.

So i made my Star Alignment, then i plugged the cable to my Telescope and Computer, i installed the Cable driver and ASCOM Platform + ASCOM Celestron Driver.

I started DriverConnect.exe and put the Celestron Driver i downloaded, and did the properties informations ( had to tick on "Advanced Setup" and "Show All COM Ports" ) and i put "COM8" on "COM Port", then i pressed "OK" and then "Connect"

Result:

Create              Creating device
Connected           Connecting to device
Error               System.Exception: Connect to COM1 failed, no Celestron scope detected
   to System.Dynamic.ComRuntimeHelpers.CheckThrowException(Int32 hresult, ExcepInfo& excepInfo, UInt32 argErr, String message)
   to CallSite.Target(Closure , CallSite , ComObject , Boolean )
   to ASCOM.DriverConnect.ConnectForm.btnConnect_Click(Object sender, EventArgs e) in C:\ASCOM Build\Export\ASCOM.DriverConnect\ConnectForm.cs:line 268scr2.PNG.b62ba9e1f780acf4a6ac6c00b0d56293.PNG
Dispose             Disposing of device
ReleaseComObject    Releasing COM instance
ReleaseComObject    Completed release. Count: 0
GC Collect          Starting garbage collection
GC Collect          Completed garbage collection

 

"Connect to COM1 failed, no Celestron scope detected"

scr1.PNG.d8c889391ed21b7cd153c826f96724e6.PNG

In Stellarium i set-up everything, the plug-in and restarted the app, then added my telescope  and i says it's "connected" but i can't find my telescope.

 

Telescope:
Celestron NexStar 127SLT

The Cable i bought:

https://www.amazon.com/Telescope-CP2102-Adapter-Control-Console/dp/B077G37VL1/

PC Specs:

Windows 10 Pro, GTX 970, 8GB Ram(DDR4), i7 6700 3.4Ghz

 

Looking forward for your help, thanks in advance,

dragorom7.

Share this post


Link to post
Share on other sites

Hello and welcome to SGL.

Thoughts
1. You selected com 8 for the usb-serial  adapter but com 1 is shown in the Celestron setup window. EQ N is also selected as track mode, this should be alt az for the SLT.
2. The Meade cable might not work with a Celestron mount.
3. If the Celestron SLT mount works like the Skywatcher AZ -GOTO then you need to connect the mount to the computer via the handset using the correct cable, not directly.
4. The ASCOM platform and ASCOM mount drivers aren't required to control the mount through Stellarium, Stellarium has its own mount drivers.
5, If you control the mount through ASCOM you also need Stellariumscope  to communicate between Stellarium and ASCOM.

Share this post


Link to post
Share on other sites

1. Sorry i just changed my COM8 to COM1 on windows device manager, this is my bad. Also i changed EQ N to ALT-AZ.

2. I was able to plug the cable on my telescope bottom of hand controler and it fits perfectly, but though it can be the issue if it's the wrong cable, but if it is, which cable do you recommend me?

3. I connected it to the hand controller bottom port where it's written "NXS"

4. It didn't work with it's own drivers so i did some search and got told i must have ASCOM

5. I have Stellariumscope installed, and it does the same error as ASCOM: " Connect to COM1 failed, no Celestron scope detected" in an box

 

Thank you for your help and answers, you are very helpful, i hope i will be able to fix it.

 

 

Share this post


Link to post
Share on other sites
16 minutes ago, Cornelius Varley said:

Hello and welcome to SGL.

Thoughts
1. You selected com 8 for the usb-serial  adapter but com 1 is shown in the Celestron setup window. EQ N is also selected as track mode, this should be alt az for the SLT.
2. The Meade cable might not work with a Celestron mount.
3. If the Celestron SLT mount works like the Skywatcher AZ -GOTO then you need to connect the mount to the computer via the handset using the correct cable, not directly.
4. The ASCOM platform and ASCOM mount drivers aren't required to control the mount through Stellarium, Stellarium has its own mount drivers.
5, If you control the mount through ASCOM you also need Stellariumscope  to communicate between Stellarium and ASCOM.

 

Share this post


Link to post
Share on other sites
1 hour ago, Cornelius Varley said:

Hello and welcome to SGL.

Thoughts
1. You selected com 8 for the usb-serial  adapter but com 1 is shown in the Celestron setup window. EQ N is also selected as track mode, this should be alt az for the SLT.
2. The Meade cable might not work with a Celestron mount.
3. If the Celestron SLT mount works like the Skywatcher AZ -GOTO then you need to connect the mount to the computer via the handset using the correct cable, not directly.
4. The ASCOM platform and ASCOM mount drivers aren't required to control the mount through Stellarium, Stellarium has its own mount drivers.
5, If you control the mount through ASCOM you also need Stellariumscope  to communicate between Stellarium and ASCOM.

I think i bought the wrong cable, it says on amazon that it's RJ-10 and the real celestron one is RJ-11

Share this post


Link to post
Share on other sites

Stellarium direct ASCOM support testers wanted: https://github.com/Stellarium/stellarium/issues/406 and https://github.com/Stellarium/stellarium/pull/761

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By Asghar
      Hi all,
       
      I'm pretty new to astronomy and need help deciding if I should buy the following telescope or not, mainly if there is anything visibly missing by looking at the photos?
       
      Thanks in advance!



    • By Viktorious
      Time for yet another cry for help when it comes to choosing diagonal. I have read the many similar threads and gathered some knowledge (too many to start linking). I have come some way in my process and now that it is coming to final decisions I would like to hear from the experts. Not many of threads I have read end with the OP returning to deliver some review/verdict of his/her final decision. While I wait for response on some thread where I asked about the result, the eagerness in me forces me to write my own thread. Perhaps some of the people asking these questions before can now answer in my thread as experts!

      I have the Nexstar Evolution 9.25 and am currently using the stock diagonal. My eyepieces are the Baader 8-24 mm zoom and the stock 40 mm Plössl. I would also like to upgrade EPs and there I'm looking at something better in 24 mm range, as well some nice low power for more FOV. I'm following threads about EPs and SCTs with great interest for this (on CN). Can say that I'm currently leaning towards the 1.25" 24 mm ES 68° and 2" 36 mm Hyperion aspheric (if going 2" route).

      I'm thinking 2 alternatives (including a budget alternative for one of them). I'm looking at Baader mainly for ClickLock (and expect good optics):
      Baader T2 Zeiss prism with a 1.25" ClickLock EP (T2 part #08) -OR- the 2" prism with 2" ClickLock (splurging that is). The budget alternative would be to get the non-Zeiss T2 prism instead for the 1.25". Worth noting that I would like to get the Celestron f/6.3 Reducer/Corrector. This would be for future purposes of delving into EAA but of course I would use it visually as well (especially if choosing the T2 route). The reasoning for my alternatives:
      Go for the 2" Zeiss prism to theoretically get the best of the best in visual terms. I would make better use of the 46 mm baffle tube opening. Theoretically possible to combine with the R/C thanks to relative short light path (although not necessarily needed with 2" EPs). Downside of going to 2" accessories would be the cost, EPs, filters etc., on top of diagonal. Would not be able to spend all these costs at once. Cheaper route with T2 prism (especially the non-Zeiss), not only diagonal but also the other accessories. Cost of the R/C would be comparable to e.g. the 36 mm aspheric and give similar power and FOV with the 24 mm ES, i.e. the 24 mm would act as both. Extra plus is the ClickLock clamp for 1.25" with built in fine focusing not involving the mirror. Downside of knowing that not all light coming out of baffle tube is used. To get the wide FOV (24 mm + R/C) I'm adding glass to the optical train (theoretically not a good thing). I'm leaning towards the T2 as it would be a cheaper diagonal and for EPs I would only need the 24 mm and then the reducer instead of a 30-40 mm, so saving the expense of one EP. Then I would already have the reducer for continuing into EAA. The questions I hope the experts here can help with:
      The old reducer vs 2" diagonal question. With R/C and the 24 mm I can get roughly the same mag and FOV as e.g. the 36 mm Hyperion (technically 38 mm vs 36 mm and 68° vs 72°). Also reading good things about the ES 68° and with R/C the EP should behave the same. Am I missing something here? The logics say that the I would lose some contrast with the R/C (not using full opening + adding elements), correct? Possibly flatter fields though (not important now, hopefully the EP threads might tell soon enough). The Zeiss vs non-Zeiss T2? Big differences? I have read a few posts on this so most to get some updated views here (have read that Baader has changed some things over the years). Using the R/C (f/6.3) with these prisms. I know f/7 is mentioned as "the limit" but also remember BillP's test where he was happy down to f/6 with the prisms (in 2014 at least). Perhaps most important: have I missed some other obvious alternative here? Maybe I have forgotten some question here but perhaps for the best as I assume those who have gotten this far are tired of reading now. Thanks for getting here though!

      Thanks,
      Viktor
    • By ssuummoonnaa
      Hi, I have recently bought the celestron AM 130 EQ. when setting up , I wrongly assembled the counter weight first rather than adjusting the lattitude knob both at the front and rear side. That made the counter weight pull towards the floor and now the lattitude adjustment knob is jammed, I cant move it counter clockwise. The pin at lattitude is showing 0 degree. What to do. Please help. 

    • By alexwolf
      The second bugfix release for series 0.19.
      Thank you very much to community for bug reports, feature requests and contributions!
      Full list of changes between versions 0.19.1 and 0.19.2:
      - Added support DMS and DD formats for parallactic angle feature
      - Added altitude limitation filter for AstroCalc/Graphs[AltVsTime/ME] tools
      - Added visual improvements for AstroCalc/Graphs tool
      - Added new time intervals for AstroCalc/Ephemeris tool
      - Added computation of ephemeris for all naked-eye visible planets into AstroCalc/Ephemeris tool
      - Added GUI for select the color of ephemeris markers into AstroCalc/Ephemeris tool
      - Added 2 new scripts (Saturnian and uranian analemmas)
      - Added 'k Pup' designation to star HIP 37229 (GH: #706)
      - Added information about progress of loading on splash screen (GH: #719)
      - Added a new skylore for Stellarium: Anutan
      - Added support catalog "Southern Stars embedded in nebulosity" (Van den Bergh and Herbst, 1975 - VdBH)
      - Added support "Catalogue and distances of optically visible H II regions" (Dickel+, 1969 - DWB)
      - Added distances for few LDN objects
      - Added support removing shortcuts through config.ini file (GH: #724)
      - Added extraInfoString to StelObject: Allows extra info injected by plugins or scripts.
      - Added display of Apex/Antapex points (GH: #737)
      - Added "observers" for all planets with moons (GH: #736)
      - Added IAU constellation abbreviation to object info
      - Added 3 new actions
      - Added settings for Script Console (GH: #741)
      - Added Vanuatu (Netwar) skyculture (GH: #762)
      - Added few asterisms (GH: #753, #768)
      - Added new one time step into AstroCalc/Ephemeris tool (GH: #758)
      - Added few new DSO textures (GH: #756, #780)
      - Added support Vec3d into scripting engine
      - Added a Messier Marathon script (GH: #771)
      - Added support for short weekday display modes in bottom toolbar
      - Added GUI option to toggle permanent orbit drawing
      - Added hyperbolic comet C/2019 Q4 (Borisov) [2I/Borisov] into default ssystem_minor.ini file
      - Added a scripting function for refraction (GH: #778)
      - Fixed coloring text issue when formatting output is on
      - Fixed saving properties for external software/remote computer in Telescope Control plugin (GH: #702)
      - Fixed behaviour of selected ephemeris marker when sorting not for date (AstroCalc/Ephemeris tool)
      - Fixed sorting date and time columns for AstroCalc/Ephemeris and AstroCalc/Phenomena tools
      - Fixed crash on destruction of static QWidget (GH: #720)
      - Fixed small difference of values issue for different time zones for Date and Time column in AstroCalc/Ephemeris tool (GH: #717)
      - Fixed stupid conversion bug in hmsToRad function (GH: #716)
      - Fixed an asymmetry w.r.t. to the ecliptic latitudes (Moon age)
      - Fixed Search Tool/Lists behaviour for VdBH catalog
      - Fixed distances for few DSO (GH: #708)
      - Fixed Gregorian date issue for AstroCalc (GH: #711)
      - Fixed support GPS on macOS (GH: #712)
      - Fixed coefficient for the duration of mean tropical year
      - Fixed issue for images in description for landscapes: set search directory (GH: #735)
      - Fixed tooltip behaviour for Date and Time dialog
      - Fixed star name to its source spelling (GH: #729)
      - Fixed compiling with GPSD 3.19 [API 8.0] (GH: #733)
      - Fixed encoding script files in Script Console (GH: #742)
      - Fixed drawing names of asterisms
      - Fixed aFOV display in Oculars plugin
      - Fixed visual issue in Script Console (white background) with Qt 5.13
      - Fixed links for scripting docs (SUG)
      - Fixed screen flashing during solar eclipse (GH: #747)
      - Fixed core.resetOutput(); method behaviour (GH: #750)
      - Fixed AltGr behaviour for some languages on Windows
      - Fixed clipping issue for LabelMgr.labelObject (GH: #776)
      - Fixed weekday computation
      - Fixed rendering planets orbits (GH: #773)
      - Fixed error in shape of asterism Red-Necked Emu (GH: #769)
      - Fixed proper removing of default secondary shortcut (GH: #764)
      - Fixed cross-id error in DSO catalog
      - Updated appdata.xml file
      - Updated outdated code for names of days and months
      - Updated Observability plugin
      - Updated list of proper names of stars (IAU approved list)
      - Updated Moon age calculation: let's use geocentric coordinates only for compute of the Moon age
      - Updated AstroCalc/PC tool: simplification and colorification for graphs
      - Updated AstroCalc/Phenomena tool: small speed-up
      - Updated the default color space: StelToneReproducer now use sRGB as target RGB color space (GH: #718)
      - Updated GUI for Satellites plugin
      - Updated common names for DSO
      - Updated common names for stars
      - Updated packaging for macOS: Let's use macdeployqt for creating a MacOS bundles
      - Updated nomenclature support: Let's use compressed nomenclature data to reduce an installation package
      - Updated translations
      - Updated planetary nomenclature
      - Updated Sardinian skyculture
      - Updated file handling in Script Console
      - Updated HDPI features: enabled scaling fonts on High DPI monitors (GH: #546)
      - Updated default shortcuts: changed default shortcut for copying selected object information (Ctrl+C -> Ctrl+Shift+C) to allow use Ctrl+C shortcut for text edit fields for whole planetarium (GH: #748)
      - Updated getInfoMap method [scripting engine]: enhanced the getInfoMap method for the Sun (get eclipse data; GH: #747)
      - Updated Chinese (Simplified) and Russian translations for Windows installer (GH: #755, #779)
      - Updated Bookmarks tool
      - Updated default exoplanets and pulsars catalogs
      - Updated behaviour on Windows: disable HiDPI scaling in manifest (GH: #763)
      - Updated Oculars plugin: improve RA/Dec output for CCD frame
      - Code refactoring: type checking/casting clarifications
      - Removed FOV plugin (the feature was moved into core of planetarium)
      Homepage + links to downloading binary packages: https://stellarium.org
    • By CrystalFox
      Hello guys,
      I recently got into astronomy so I bought my first telescope. I've read through several articles and the recommendation for a beginner's telescope (value/price) was Celestron Astromaster 130EQ-MD. I bought this from someone who was not really using it and it is in a very good condition. Prior to actually purchasing this, I've watched countless videos on how the telescope works, what needs to be done - latitude, RA/DEC alignment, polar alignment, etc..
      After reading through all available manuals and videos, I finally brought it home from the seller (they've had it for around 5 years but it wasn't used much). After setting up the tripod, mounting the telescope and familiarising myself with all the different knobs, I pointed the mount/telescope towards north. The first thing I had to do was setting up the latitude. Since I am based in London, the latitude is around 52 degrees. Afterwards, I had to align the declination axis so the telescope can be balanced. As I understand it, you should be able to move it to any position on the axis and it should stay in that position. If the front or rear was heavier, I would either pushing or pulling the telescope after unlocking the brackets holding it together. This is where the issues began, I could balance the telescope so it doesn't move while in the horizontal position, however, when pointing it towards north, it would exclusively lean towards one direction - to the left. If the telescope was pointing to north, north-east or east, it would pull towards the west all the time. It is probably easier to show it in the video. I've spent three days trying to balance the telescope by using different methods and it just would not work. 
      I've also tried balancing the RA axis first. This could be somehow done, but the declination axis would still pull the telescope to the left.
      It is extremely frustrating as I don't know what could be causing this. Balancing the telescope should be relatively easy from what I have heard - either push it or pull it depending on where the weight is. However, I have been really struggling to get it set-up.
      I would be thankful for any suggestions and please feel free to ask any questions so I can help with finding out what is wrong.
       
      Thank you.
      VID_20190918_202940.mp4


×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.