Stellarium 19.3.1 and latest Beta fail to Launch when using Telescope Control Plugin

[wetzelmd]

Stellarium V 19.3.1 and the latest Beta build 17542 fail to launch under the following conditions:

The Telescope Control Plugin is set to start when Stellarium is launched and The Telescope ASCOM driver is not running.

Stellarium will begin the startup process, but then disappear when the Telescope Control is starting.

If the ASCOM driver is present, everything works normally.

I believe there is also an issue in shutting down if the ASCOM driver is shut down before quitting Stellarium.

Windows 10 Pro Celestron CPWI and its ASCOM driver for scope mount control.

Mark W

[gzotti]

@gionkunz can you please have a look into this?

[gionkunz]

Hi @gzotti , I will have a look at this at the weekends at the latest.

[dts350z]

For Stellarium 19.3 Windows 64bit.

I've been using the native ASCOM support, vs. StellariumScope, to control my telescope since the release of 19.3, for astrophotography.

It works fine, however about 50% of the time when I get up in the morning Stellarium is no longer running. All the other Astro programs are OK and the mount(telescope) is still connected to them and working.

What would be the approach to troubleshoot this?

Sorry if this should be a separate issue. I was given this link.

Thanks

[gionkunz]

Hi @gzotti , I will have a look at this at the weekends at the latest.

Now is obviously a couple of weekends later... It has been very hectic around me and I need to spend all my time with my business at the moment. I hope I can pick this up soon.

@dts350z Do you have any stellarium logs for such an incident? I was running it with ASCOM and EQMod over many nights and Stellarium was never exiting. At least I never noticed, but sometimes I also shut it down, because Stellarium is a real battery drainer :-)

[dts350z]

I will look. Is logging in Stellarium something I need to enable?

hmm... C:\Users\Glenn\AppData\Roaming\Stellarium looks like it only keeps the last instance log?

[wetzelmd]

When I launch Stellarium without the Celestron CPWI application running (and its ASCOM driver), Stellarium gets to the Load Telescope plugin, pauses, then vanishes. Attached is the log.

The config.ini file has these settings for the Telescope Control:

[TelescopeControl] flag_enable_telescope_logs = false flag_telescope_circles = true flag_telescope_labels = true flag_telescope_reticles = true flag_use_server_executables = false

Mark W.

On Sun, Mar 8, 2020 at 12:46 PM dts350z notifications@github.com wrote:

I will look. Is logging in Stellarium something I need to enable?

hmm... C:\Users\Glenn\AppData\Roaming\Stellarium looks like it only keeps the last instance log?

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/Stellarium/stellarium/issues/928?email_source=notifications&email_token=ANLATCPV3EW2VSBPRCT4CO3RGP73BA5CNFSM4KFPEYM2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEOE7OAQ#issuecomment-596244226, or unsubscribe https://github.com/notifications/unsubscribe-auth/ANLATCLYIW4ZX3FXTVDCUYTRGP73BANCNFSM4KFPEYMQ .

2020-03-08T17:13:50 Operating System: Windows 10 (10.0) Compiled using MSVC++ 15.9 (Visual Studio 2017) Qt runtime version: 5.12.6 Qt compilation version: 5.12.6 Addressing mode: 64-bit Total physical memory: 8088 MB Available physical memory: 4031 MB Physical memory in use: 50% Processor speed: 2304 MHz Processor name: Intel(R) Core(TM) i3-6100U CPU @ 2.30GHz Processor speed: 2304 MHz Processor name: Intel(R) Core(TM) i3-6100U CPU @ 2.30GHz Processor speed: 2304 MHz Processor name: Intel(R) Core(TM) i3-6100U CPU @ 2.30GHz Processor speed: 2304 MHz Processor name: Intel(R) Core(TM) i3-6100U CPU @ 2.30GHz C:\Program Files\Stellarium\stellarium.exe

[ This is Stellarium 0.19.3.17733 [HEAD] - https://stellarium.org/ ] [ Copyright (C) 2000-2020 Fabien Chereau et al. ]

Writing log file to: "C:\Users\mdwet\AppData\Roaming\Stellarium\log.txt" File search paths: 0 . "C:\Users\mdwet\AppData\Roaming\Stellarium" 1 . "." Config file is: "C:\Users\mdwet\AppData\Roaming\Stellarium\config.ini" Default surface format: QSurfaceFormat(version 2.0, options QFlags(), depthBufferSize -1, redBufferSize -1, greenBufferSize -1, blueBufferSize -1, alphaBufferSize -1, stencilBufferSize -1, samples -1, swapBehavior QSurfaceFormat::DefaultSwapBehavior, swapInterval 1, colorSpace QSurfaceFormat::DefaultColorSpace, profile QSurfaceFormat::NoProfile) Desired surface format: QSurfaceFormat(version 2.1, options QFlags(), depthBufferSize 24, redBufferSize 8, greenBufferSize 8, blueBufferSize 8, alphaBufferSize 8, stencilBufferSize 8, samples -1, swapBehavior QSurfaceFormat::DefaultSwapBehavior, swapInterval 1, colorSpace QSurfaceFormat::DefaultColorSpace, profile QSurfaceFormat::NoProfile) StelGLWidget constructor StelGraphicsScene constructor initializeGL OpenGL supported version: "4.5.0 - Build 25.20.100.6472" Current Format: QSurfaceFormat(version 4.5, options QFlags(DeprecatedFunctions), depthBufferSize 24, redBufferSize 8, greenBufferSize 8, blueBufferSize 8, alphaBufferSize 8, stencilBufferSize 8, samples 0, swapBehavior QSurfaceFormat::DoubleBuffer, swapInterval 1, colorSpace QSurfaceFormat::DefaultColorSpace, profile QSurfaceFormat::CompatibilityProfile) StelMainView::init Detected: OpenGL "4.5" Driver version string: "4.5.0 - Build 25.20.100.6472" GL vendor is "Intel" GL renderer is "Intel(R) HD Graphics 520" GL Shading Language version is "4.50 - Build 25.20.100.6472" GLSL Version Number detected: 4.5 GLSL version is fine, we should not see a graphics problem. Cache directory is: "C:\Users\mdwet\AppData\Local\stellarium\stellarium\cache" StelLocation::createFromLine(): TimeZone name for "Casitas de Gila NM" not found. Translating "system_default" to "system_default" StelLocation::createFromLine(): TimeZone name for "El Rito NM" not found. Translating "system_default" to "system_default" StelLocation::createFromLine(): TimeZone name for "Oregon Star Party Ochoco NF OR" not found. Translating "system_default" to "system_default" StelLocation::createFromLine(): TimeZone name for "el Rito New Mexico" not found. Translating "system_default" to "system_default" Sky language is "en_US" Planetary features language is "en_US" Application language is "en_US" Empty translation file for language "en_US" in section "stellarium-scripts" Scripts language is "en_US" Loading Solar System data (1: planets and moons) ... Loading from : "./data/ssystem_major.ini" SolarSystem has 83 entries. Loaded 83 Solar System bodies Loading Solar System data (2: minor bodies)... Loading from : "C:\Users\mdwet\AppData\Roaming\Stellarium/data/ssystem_minor.ini" SolarSystem has 188 entries. Loaded 105 Solar System bodies File ssystem_minor.ini is loaded successfully... Loading nomenclature for Solar system bodies ... Loaded 15630 / 15632 items of planetary surface nomenclature WARNING - The next planets to assign nomenclature items is not found: "Dactyl" Loading star data ... "Loading .\stars\default\stars_0_0v0_8.cat: 0_0v0_8; 4979" "Loading .\stars\default\stars_1_0v0_8.cat: 1_0v0_8; 21806" "Loading .\stars\default\stars_2_0v0_8.cat: 2_0v0_8; 150826" "Loading .\stars\default\stars_3_1v0_4.cat: 3_1v0_4; 425807" "Loading C:\Users\mdwet\AppData\Roaming\Stellarium\stars\default\stars_4_1v0_2.cat: 4_1v0_4; 1692779" "Loading C:\Users\mdwet\AppData\Roaming\Stellarium\stars\default\stars_5_2v0_1.cat: 5_2v0_1; 7083058" "Loading C:\Users\mdwet\AppData\Roaming\Stellarium\stars\default\stars_6_2v0_1.cat: 6_2v0_1; 24670782" "Loading C:\Users\mdwet\AppData\Roaming\Stellarium\stars\default\stars_7_2v0_1.cat: 7_2v0_1; 50733321" "Loading C:\Users\mdwet\AppData\Roaming\Stellarium\stars\default\stars_8_2v0_1.cat: 8_2v0_1; 92304337" Finished loading star catalogue data, max_geodesic_level: 8 Loading scientific star names from ".\stars\default\name.fab" Loaded 4507 / 4507 scientific star names Loading variable stars from ".\stars\default\gcvs_hip_part.dat" Loaded 6862 / 6862 variable stars Loading double stars from ".\stars\default\wds_hip_part.dat" Loaded 16412 / 16412 double stars Loading cross-identification data from ".\stars\default\cross-id.dat" Loaded 108338 / 108338 cross-identification data records for stars Loading parallax errors data from ".\stars\default\hip_plx_err.dat" Loaded 117703 / 117703 parallax error data records for stars navigation/preset_sky_time is a double - treating as jday: "2458660.41944" Loading DSO data ... [...] "Stellarium DSO Catalog, version 3.8 (standard edition)" Loaded 94394 DSO records Loading DSO outline data ... Loaded 72 DSO outline records successfully LandscapeMgr: initialized Cache for 100 MB. Loading star names from ".\skycultures\western\star_names.fab" Loaded 1004 / 1004 common star names Loading DSO name data ... Loaded 1085 / 1098 DSO name records successfully WARNING - No position data for 13 objects: "PGC 2907, PGC 23521, PGC 28759, PGC 29167, PGC 34658, PGC 42102, PGC 54559, PGC 59117, PGC 73957, PGC 95597, PGC 100170, PGC 100170, PGC 119230" Loaded 88 / 88 constellation records successfully for culture "western" Loaded 85 / 85 constellation art records successfully for culture "western" Loaded 88 / 88 constellation names Loading constellation boundary data ... Loaded 782 constellation boundary segments Loaded 82 / 82 asterism records successfully for culture "western" Loaded 72 / 72 asterism names stel.OpenGLArray: Disabling VAO usage because of Intel driver bugs stel.OpenGLArray: Vertex Array Objects are not supported on your hardware (this is not an error) Initializing basic GL shaders... Creating GUI ... Loaded plugin "AngleMeasure" Loaded plugin "CompassMarks" Loaded plugin "EquationOfTime" Loaded plugin "Exoplanets" [Exoplanets] Version of the format of the catalog: 1 [Exoplanets] loading catalog file: "C:\Users\mdwet\AppData\Roaming\Stellarium\modules\Exoplanets\exoplanets.json" Loaded plugin "MeteorShowers" [MeteorShowersMgr] Loading catalog file: "C:\Users\mdwet\AppData\Roaming\Stellarium\modules\MeteorShowers\showers.json" Loaded plugin "Novae" [Novae] version of the catalog: 1 [Novae] loading catalog file: "C:\Users\mdwet\AppData\Roaming\Stellarium\modules\Novae\novae.json" Loaded plugin "Oculars" Oculars::validateAndLoadIniFile() ocular.ini exists at: "C:\Users\mdwet\AppData\Roaming\Stellarium\modules\Oculars\ocular.ini" . Checking version... Oculars::validateAndLoadIniFile() found existing ini file version 3.1 Loaded plugin "Quasars" [Quasars] Version of the format of the catalog: 1 [Quasars] Loading catalog file: "C:\Users\mdwet\AppData\Roaming\Stellarium\modules\Quasars\quasars.json" Loaded plugin "Satellites" [Satellites] loading catalog file: "C:\Users\mdwet\AppData\Roaming\Stellarium\modules\Satellites\satellites.json" Satellite has invalid orbit: "NOSS 2 (A)" "10502" Satellite has invalid orbit: "BATSU-CS1 (IRAZU)" "43468" Loaded plugin "SolarSystemEditor" Using the ssystem_minor.ini file that already exists in the user directory... Loaded plugin "Supernovae" [Supernovae] version of the catalog: 1 [Supernovae] loading catalog file: "C:\Users\mdwet\AppData\Roaming\Stellarium\modules\Supernovae\supernovae.json" Loaded plugin "TelescopeControl" [TelescopeControl] Only embedded telescope servers are available. [TelescopeControl] Adding device model: "Meade AutoStar compatible" "Any telescope or telescope mount compatible with Meade's AutoStar controller." "TelescopeServerLx200" 500000 [TelescopeControl] Adding device model: "Meade LX200 (compatible)" "Any telescope or telescope mount compatible with Meade LX200." "TelescopeServerLx200" 500000 [TelescopeControl] Adding device model: "Meade ETX70 (#494 Autostar, #506 CCS)" "Meade's ETX70 with the #494 Autostar controller and the #506 Connector Cable Set." "TelescopeServerLx200" 1500000 [TelescopeControl] Adding device model: "Losmandy G-11" "Losmandy's G-11 telescope mount." "TelescopeServerLx200" 500000 [TelescopeControl] Adding device model: "Wildcard Innovations Argo Navis (Meade mode)" "Wildcard Innovations' Argo Navis DTC in Meade LX200 emulation mode." "TelescopeServerLx200" 500000 [TelescopeControl] Adding device model: "Celestron NexStar (compatible)" "Any telescope or telescope mount compatible with Celestron NexStar." "TelescopeServerNexStar" 500000 [TelescopeControl] Adding device model: "Sky-Watcher SynScan (version 3 or later)" "Any Sky-Watcher mount that uses version 3 or later of the SynScan hand controller." "TelescopeServerNexStar" 500000 [TelescopeControl] Adding device model: "Sky-Watcher SynScan AZ GOTO" "The Sky-Watcher SynScan AZ GOTO mount used in a number of telescope models." "TelescopeServerNexStar" 500000 connectionType: 7 initString: "C9.25:ASCOM:JNow:ASCOM.CPWI.Telescope:true" Creating telescope "C9.25:ASCOM:JNow:ASCOM.CPWI.Telescope:true" ; name/type/equinox/params: "C9.25" "ASCOM" JNow "ASCOM.CPWI.Telescope:true" TelescopeClientASCOM::TelescopeClientASCOM with telescope name "C9.25" and ascomDeviceId "ASCOM.CPWI.Telescope"

[alex-w]

@wetzelmd, are you enabled auto-connect to the mount in the plugin?

[wetzelmd]

Yes, automatic connection is enabled so that an imaging session is easy to start up.

Mark

Sent from my iPhone

On Mar 9, 2020, at 1:39 AM, Alexander Wolf notifications@github.com wrote:

 @wetzelmd, are you enabled auto-connect to the mount in the plugin?

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or unsubscribe.

[dts350z]

Here is a log from a stellarium crash when using the telescope plugin.

log_crash.txt

[dts350z]

And another one.

log_crash2.txt

[dts350z]

Do you want more logs? I have a total of 5 now.

[wetzelmd]

The problem with the Telescope Control plugin that causes Stellarium 0.20.1.xxxxx to crash when the telescope's ASCOM driver is not running persists (latest beta). The plugin times out and causes Stellarium to exit. I need Stellarium to launch with and without the telescope driver present while loading the plugin at startup, especially when using Stellarium to plan an imaging session without my gear connected. Otherwise I have to edit the config.ini file and change the plugin flag.

Windows 10 Pro, latest version, most recent updates. Celestron CPWI ASCOM driver (latest version - release candidate)

If the CPWI ASCOM driver is running and CPWI is connected to the mount, Stellarium and the Telescope Control plugin work exceptionally well.

Mark W

The log:

14:43:20.562 INFO: Connecting process : stellarium 14:43:20.564 INFO: Initializing Telescope driver for C:\Program Files\Stellarium\stellarium.exe 14:43:20.569 INFO: Get DriverVersion 14:43:20.569 INFO: Submitting Synchronus request: /CPWI/version 14:43:22.623 INFO: could not communicate with CPWI, request =/CPWI/version 14:43:22.627 INFO: ERROR: ASCOM.DriverAccessCOMException (0x00000000): could not communicate with CPWI, request =/CPWI/version ---> System.Net.WebException: The operation has timed out at System.Net.HttpWebRequest.GetResponse() at PWLib.Net.WebUtils.HttpGetString(String url, Int32 timeoutMsec) at ASCOM.CPWI.AscomTelescopeThread.Request(String urlPath) at ASCOM.CPWI.AscomTelescopeThread.Request(String urlPath) at ASCOM.CPWI.AscomTelescopeThread.SubmitRequest(String request) at ASCOM.CPWI.Telescope.SubmitRequest(String request) at ASCOM.CPWI.Telescope.b__25_0() at ASCOM.CPWI.Telescope.LogCall[T](String logPrefix, Func`1 func)

[wetzelmd]

Fix in latest beta seems to work.

Thanks!

Mark W

[luzpaz]

Is this ticket still relevant ?

[gzotti]

If the "dirty fix" (disable autoconnect feature for ASCOM telescopes) is OK for all, we could close it. @alex-w , @wetzelmd, @gionkunz ?

[alex-w]

Nope. I've added this "dirty fix" some time ago and many users was angry - so, it was revert...

[gzotti]

Is it possible to surround the connection attempt with something like

try
{
   connect();
}
catch (ConnectionError &e) 
{ 
   handle_connection_error_gracefully();
}

?

[wetzelmd]

I have not tested so it probably is no longer relevant.MarkSent from my iPadOn Sep 28, 2023, at 12:50 AM, luzpaz @.***> wrote: Is this ticket still relevant ?

—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: @.***>

[gzotti]

We should come to a conclusion. Four years ago someone answered it works.