Telescope control Plugin connect defect

[Roger Scott]

Unable to connect my telescope using the control plugin.

Basic System Configuation info:
1. Stellarium v0.14.1B
2. Celestron Nexstar 8se connected to PC using Trendnet TU-S9 v2.02 USB to RS232 adapter
3. Windows OS 10
4. Dell XPS 8300, i7 CPU, 3.4 GHz, 8GB RAM

Am unable to register the telescope:
0. Telescope is properly connected and turned on.
1. Select Stellarium directly through serial port
2. Connection delay default of 0.50s
3. Coordinate system J2000 default
4. Device Serial Port selection: Serial Port # shown in list was confirmed in system Device Manager (and confirmed to work with Celestron NexStar Controller Remove SW using same port #)
5. Device Model: Celestron NexStar (compatible) selected
6. Connection Settings: unchanged from default, TCP Port: 10001
7. User Interface Settings empty

Click OK with above preconditions and window doesn't close and configuration not recorded. Change from direct connection through serial port and clicking OK closes window and configuration recorded.

[Alexander Wolf (alexwolf)]

I can't confirm. Please attach full log

[Roger Scott (rmatscott)]

Log file attached.

On Fri, Jan 1, 2016 at 11:44 AM, Alexander Wolf <email address hidden>
wrote:

> I can't confirm. Please attach full log
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1530372
>
> Title:
> Telescope control Plugin connect defect
>
> Status in Stellarium:
> New
> Status in Stellarium 0.14 series:
> New
>
> Bug description:
> Unable to connect my telescope using the control plugin.
>
> Basic System Configuation info:
> 1. Stellarium v0.14.1B
> 2. Celestron Nexstar 8se connected to PC using Trendnet TU-S9 v2.02 USB
> to RS232 adapter
> 3. Windows OS 10
> 4. Dell XPS 8300, i7 CPU, 3.4 GHz, 8GB RAM
>
> Am unable to register the telescope:
> 0. Telescope is properly connected and turned on.
> 1. Select Stellarium directly through serial port
> 2. Connection delay default of 0.50s
> 3. Coordinate system J2000 default
> 4. Device Serial Port selection: Serial Port # shown in list was
> confirmed in system Device Manager (and confirmed to work with Celestron
> NexStar Controller Remove SW using same port #)
> 5. Device Model: Celestron NexStar (compatible) selected
> 6. Connection Settings: unchanged from default, TCP Port: 10001
> 7. User Interface Settings empty
>
> Click OK with above preconditions and window doesn't close and
> configuration not recorded. Change from direct connection through
> serial port and clicking OK closes window and configuration recorded.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/stellarium/+bug/1530372/+subscriptions
>

[Alexander Wolf (alexwolf)]

Please attach log when you try register the telescope.

[Roger Scott (rmatscott)]

That's the log after I tried registering the telescope. Does logging occur
prior to or after clicking OK?
On Jan 1, 2016 2:25 PM, "Alexander Wolf" <email address hidden> wrote:

> Please attach log when you try register the telescope.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1530372
>
> Title:
> Telescope control Plugin connect defect
>
> Status in Stellarium:
> New
> Status in Stellarium 0.14 series:
> New
>
> Bug description:
> Unable to connect my telescope using the control plugin.
>
> Basic System Configuation info:
> 1. Stellarium v0.14.1B
> 2. Celestron Nexstar 8se connected to PC using Trendnet TU-S9 v2.02 USB
> to RS232 adapter
> 3. Windows OS 10
> 4. Dell XPS 8300, i7 CPU, 3.4 GHz, 8GB RAM
>
> Am unable to register the telescope:
> 0. Telescope is properly connected and turned on.
> 1. Select Stellarium directly through serial port
> 2. Connection delay default of 0.50s
> 3. Coordinate system J2000 default
> 4. Device Serial Port selection: Serial Port # shown in list was
> confirmed in system Device Manager (and confirmed to work with Celestron
> NexStar Controller Remove SW using same port #)
> 5. Device Model: Celestron NexStar (compatible) selected
> 6. Connection Settings: unchanged from default, TCP Port: 10001
> 7. User Interface Settings empty
>
> Click OK with above preconditions and window doesn't close and
> configuration not recorded. Change from direct connection through
> serial port and clicking OK closes window and configuration recorded.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/stellarium/+bug/1530372/+subscriptions
>

[clive (stachonc)]

I can confirm that under windows 10 using 14.1b that i have the same problem. Note Scope has no problems creating the 3 std settings but using the ADD in the plug in just hangs on accept but cancel still works. I did have a previous version of Stellarium installed (13.?) . I tried running Stellarium using "run as admin" but still the same result.

[Nick Fedoseev (nick-ut2uz)]

I do not have a NexStar mount, but tried to play with one by Synta. I do not know if protocols are fully compatible, but Synta AZEQ5 mount works with both Synta and NexStar protocols selected in the config dialog.
Stellarium 0.14.0 is here

[Nick Fedoseev (nick-ut2uz)]

0.14.1 beta installed over 0.14.0

Old config works.

But now I can't create any telescope with direct (via COM) connection. Looks like OK button ignores mouse click and keyboard. The other telescope types work as usual.

[Nick Fedoseev (nick-ut2uz)]

The module verifies serial device name to be started with "COM", while actually it starts with "\\.\COM".

So, look for the following line (~#42) in TelescopeControlGlobals.hpp :
 const QString SERIAL_PORT_PREFIX = QString("COM");

Add one more line
 const QString SERIAL_PORT_PREFIX2 = QString("\\\\.\\COM");

In TelescopeConfigurationDialog.cpp :
look for line ~#392
  if(!serialPortName.startsWith(SERIAL_PORT_PREFIX))
   return;//TODO: Add more validation!

Replace this with the following:

  if(!serialPortName.startsWith(SERIAL_PORT_PREFIX) && !serialPortName.startsWith(SERIAL_PORT_PREFIX2))
   return;//TODO: Add more validation!

Recompile.
That's all folks

[Roger Scott (rmatscott)]

Dear Alexander, et al: Excellent, I just verified connection to the scope. Thanks for the quick turnaround. Roger