Cannot configure telescope with NexRemote external software

Bug #1741322 reported by Scott Loucks
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Stellarium
New
Medium
gzotti

Bug Description

Hello, I recently upgraded to vs 17 from vs 15 and lost telescope connection. I have a Nexstar GPS11 mount and I am connecting to the PC with NexRemote and usb to serial adapter. The Stellarium connection type is external, Nexstar compatible mount with jnow selected and startup button checked. When trying to connect the status reads: "connecting" however it never connects, just hangs there with same status.

Prior to this incident, I was successfully running this same exact setup with vs 15 with no issues. Maybe I have missed something on the configuration process but I cant find my mistake if I have. Stellarium is truly a superb software! I do hope this issue can be resolved.

Thank you -Scott

Revision history for this message
gzotti (georg-zotti) wrote :

v0.17 introduced INDI telescope support. We unfortunately cannot test the necessary changes this move brought in, because we (2-3 active developers) do not have the telescope mounts required. You can try to run your telescope now via INDI. Hopefully the old functionality can also be restored (or checked again what happened).

Revision history for this message
Scott Loucks (hepcat) wrote :

Georg, thank you for your answer. I will try the INDI connection. If this doesn’t work maybe I can try an earlier version of Stellarium.
Can you tell me what becomes of this issue, will the status remain open until hopefully it can be addressed, or do I post another bug report at a later date?
Thank you for your help.
-Scott

Revision history for this message
gzotti (georg-zotti) wrote :

No, this bug report will stay in open state, but it is unclear when we can deal with it. I have a small NexStar compatible mount, so when it really does not work, I am affected myself, bothered and annoyed by this fact and will be possibly motivated enough... But my time budget is limited, so it may be February or June. I spend considerably more time developing this simulation than getting starlight :-( If INDI does not work for you, V0.16.1 should have the same connectivity options as 0.15.

Revision history for this message
gzotti (georg-zotti) wrote :

I assign this bug to myself just to remember, but if anybody else want to solve it, I am not unhappy.

Changed in stellarium:
assignee: nobody → gzotti (georg-zotti)
importance: Undecided → Medium
Revision history for this message
Scott Loucks (hepcat) wrote : Re: [Bug 1741322] Re: Cannot configure telescope with NexRemote external software
Download full text (20.1 KiB)

I am attaching the log here if it helps. The log shows attempted
connection, external local, with NexRemote loaded and running. I did try
INDI connection but that did not work either - not included in log.
Thank you for your support - Scott

2018-01-05T13:52:11
Operating System: Windows 7
Product Name: Windows 7 SP 1 (6.1)
Compiled using MSVC++ 14.0 (Visual Studio 2015)
Qt runtime version: 5.9.3
Qt compilation version: 5.9.3
Addressing mode: 64-bit
Total physical memory: 6063 MB
Available physical memory: 4784 MB
Physical memory in use: 21%
Processor speed: 2992 MHz
Processor name: Intel(R) Core(TM)2 Duo CPU E8400 @ 3.00GHz
Processor speed: 2992 MHz
Processor name: Intel(R) Core(TM)2 Duo CPU E8400 @ 3.00GHz
C:\Program Files\Stellarium\stellarium.exe
 -------------------------------------------------------
[ This is Stellarium 0.17.0 - http://www.stellarium.org ]
[ Copyright (C) 2000-2017 Fabien Chereau et al. ]
 -------------------------------------------------------
Writing log file to:
"C:\\Users\\Scott\\AppData\\Roaming\\Stellarium\\log.txt"
File search paths:
  0 . "C:\\Users\\Scott\\AppData\\Roaming\\Stellarium"
  1 . "."
Config file is:
"C:\\Users\\Scott\\AppData\\Roaming\\Stellarium\\config.ini"
Default surface format: QSurfaceFormat(version 2.0, options
QFlags<QSurfaceFormat::FormatOption>(), depthBufferSize -1, redBufferSize
-1, greenBufferSize -1, blueBufferSize -1, alphaBufferSize -1,
stencilBufferSize -1, samples -1, swapBehavior
QSurfaceFormat::SwapBehavior(DefaultSwapBehavior), swapInterval 1, profile
QSurfaceFormat::OpenGLContextProfile(NoProfile))
Desired surface format: QSurfaceFormat(version 2.1, options
QFlags<QSurfaceFormat::FormatOption>(), depthBufferSize 24, redBufferSize
8, greenBufferSize 8, blueBufferSize 8, alphaBufferSize 8,
stencilBufferSize 8, samples -1, swapBehavior
QSurfaceFormat::SwapBehavior(DefaultSwapBehavior), swapInterval 1, profile
QSurfaceFormat::OpenGLContextProfile(NoProfile))
StelGLWidget constructor
StelGraphicsScene constructor
initializeGL
OpenGL supported version: "4.5.0 NVIDIA 378.78"
Current Format: QSurfaceFormat(version 4.5, options
QFlags<QSurfaceFormat::FormatOption>(DeprecatedFunctions), depthBufferSize
24, redBufferSize 8, greenBufferSize 8, blueBufferSize 8, alphaBufferSize
8, stencilBufferSize 8, samples 0, swapBehavior
QSurfaceFormat::SwapBehavior(DoubleBuffer), swapInterval 1, profile
QSurfaceFormat::OpenGLContextProfile(CompatibilityProfile))
StelMainView::init
Detected: OpenGL "4.5"
Driver version string: "4.5.0 NVIDIA 378.78"
GL vendor is "NVIDIA Corporation"
GL renderer is "GeForce GT 710/PCIe/SSE2"
GL Shading Language version is "4.50 NVIDIA"
GLSL Version Number detected: 4.5
GLSL version is fine, we should not see a graphics problem.
Cache directory is:
"C:\\Users\\Scott\\AppData\\Local\\stellarium\\stellarium\\cache"
Sky language is "en_US"
Couldn't load translations for language "en_US" in section
"stellarium-planetary-features"
Empty translation file for language "en_US" in section
"stellarium-planetary-features"
Planetary features language is "en_US"
Application language is "en_US"
Loading Solar System data (1: planets and moons) ...
Loading fr...

Revision history for this message
Scott Loucks (hepcat) wrote :
Download full text (21.1 KiB)

Sorry about that, text was cut off; complete Log text file now attached.

On Fri, Jan 5, 2018 at 2:14 PM, Hep Cat <email address hidden> wrote:

> I am attaching the log here if it helps. The log shows attempted
> connection, external local, with NexRemote loaded and running. I did try
> INDI connection but that did not work either - not included in log.
> Thank you for your support - Scott
>
> 2018-01-05T13:52:11
> Operating System: Windows 7
> Product Name: Windows 7 SP 1 (6.1)
> Compiled using MSVC++ 14.0 (Visual Studio 2015)
> Qt runtime version: 5.9.3
> Qt compilation version: 5.9.3
> Addressing mode: 64-bit
> Total physical memory: 6063 MB
> Available physical memory: 4784 MB
> Physical memory in use: 21%
> Processor speed: 2992 MHz
> Processor name: Intel(R) Core(TM)2 Duo CPU E8400 @ 3.00GHz
> Processor speed: 2992 MHz
> Processor name: Intel(R) Core(TM)2 Duo CPU E8400 @ 3.00GHz
> C:\Program Files\Stellarium\stellarium.exe
> -------------------------------------------------------
> [ This is Stellarium 0.17.0 - http://www.stellarium.org ]
> [ Copyright (C) 2000-2017 Fabien Chereau et al. ]
> -------------------------------------------------------
> Writing log file to: "C:\\Users\\Scott\\AppData\\
> Roaming\\Stellarium\\log.txt"
> File search paths:
> 0 . "C:\\Users\\Scott\\AppData\\Roaming\\Stellarium"
> 1 . "."
> Config file is: "C:\\Users\\Scott\\AppData\\Roaming\\Stellarium\\config.
> ini"
> Default surface format: QSurfaceFormat(version 2.0, options
> QFlags<QSurfaceFormat::FormatOption>(), depthBufferSize -1, redBufferSize
> -1, greenBufferSize -1, blueBufferSize -1, alphaBufferSize -1,
> stencilBufferSize -1, samples -1, swapBehavior QSurfaceFormat::SwapBehavior(DefaultSwapBehavior),
> swapInterval 1, profile QSurfaceFormat::OpenGLContextProfile(NoProfile))
> Desired surface format: QSurfaceFormat(version 2.1, options
> QFlags<QSurfaceFormat::FormatOption>(), depthBufferSize 24, redBufferSize
> 8, greenBufferSize 8, blueBufferSize 8, alphaBufferSize 8,
> stencilBufferSize 8, samples -1, swapBehavior QSurfaceFormat::SwapBehavior(DefaultSwapBehavior),
> swapInterval 1, profile QSurfaceFormat::OpenGLContextProfile(NoProfile))
> StelGLWidget constructor
> StelGraphicsScene constructor
> initializeGL
> OpenGL supported version: "4.5.0 NVIDIA 378.78"
> Current Format: QSurfaceFormat(version 4.5, options
> QFlags<QSurfaceFormat::FormatOption>(DeprecatedFunctions),
> depthBufferSize 24, redBufferSize 8, greenBufferSize 8, blueBufferSize 8,
> alphaBufferSize 8, stencilBufferSize 8, samples 0, swapBehavior
> QSurfaceFormat::SwapBehavior(DoubleBuffer), swapInterval 1, profile
> QSurfaceFormat::OpenGLContextProfile(CompatibilityProfile))
> StelMainView::init
> Detected: OpenGL "4.5"
> Driver version string: "4.5.0 NVIDIA 378.78"
> GL vendor is "NVIDIA Corporation"
> GL renderer is "GeForce GT 710/PCIe/SSE2"
> GL Shading Language version is "4.50 NVIDIA"
> GLSL Version Number detected: 4.5
> GLSL version is fine, we should not see a graphics problem.
> Cache directory is: "C:\\Users\\Scott\\AppData\\
> Local\\stellarium\\stellarium\\cache"
> Sky language is "en_US"
> Couldn't load translations for languag...

Revision history for this message
Scott Loucks (hepcat) wrote :

As a follow up, I have successfully made a telescope connection via NexRemote. After stepping down versions of Stellarium, vs 17 to 15.1 while trying various connection settings I finally connected with vs 15.1, which I believe was the first version I was using before trying to upgrade to vs 17. In any case, the connection type I finally used was not “indirect” as is suggested for a remote software connection, but rather a “direct” connection. I had to set my mount type (Nexstar) and configure the port setting. I used the current NexRemote virtual port (Com 2) for the port setting.
By the way, this type of connection did not work on any subsequent versions of Stellarium. Neither direct or indirect. My memory is a little rusty but I believe I had made the this same “direct” connection months before and thought it was odd then too but it worked so what did I care. So there you have it! I know I didn't fix anything but maybe this will offer some clues. I can't code but I sure can hack.. ;-)

Hope this helps in some way
-Scott

Revision history for this message
Alexander Wolf (alexwolf) wrote :
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.