Skip to content

Telescope Remote Control gets stuck on first object #1392

Open
@dabenpb

Description

@dabenpb

Expected Behaviour

When sending a RA/DEC coordination from a TCP client Stellarium shall indicate telescope LOS reticle on the the coordinates.

Actual Behaviour

One set of coordinates can be sent and the behavior is correct (the first). After that, the second coordinate will be received by Stellarium, the LOS will hop to the new coord (#2) and then hop back to the original (#1). This repeats indefinitely. It appears that if the stream and server are closed and re-connected, the behavior is as expected. But, I should not have to close the TCP client.

Steps to reproduce

Connect to local, external telescope on localhost:10001. Send client data via TCP.

System

  • Stellarium version: 0.20.3
  • Operating system: Windows 10x64
  • Graphics Card: NVIDIA RTX4000
  • Screen type (if applicable): HO 4k

Logfile

No real info in log file besides connection.

TelescopeTCP( "BabyYoda" )::prepareCommunication: Attempting to connect to host "127.0.0.1" at port 10001
TelescopeTCP( "BabyYoda" ): turning off Nagle algorithm.
TelescopeTCP( "BabyYoda" )::prepareCommunication: Connection established

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething likely wrong in the codehw: telescopeSpecific issues for various mounts of telescopessubsystem: pluginsThe issue is related to plugins of planetarium...

    Type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions