Stellarium / stellarium

Stellarium is a free GPL software which renders realistic skies in real time with OpenGL. It is available for Linux/Unix, Windows and macOS. With Stellarium, you really see what you can see with your eyes, binoculars or a small telescope.
https://stellarium.org
GNU General Public License v2.0
7.63k stars 818 forks source link

Stellarium doesn't connect to INDIGO Server using LX200 driver #952

Open gaevoc opened 4 years ago

gaevoc commented 4 years ago

-->

Expected Behaviour

I would like to connect Stellarium to my INDIGO Server to which it is connected an Avalon Linear mount via USB

Actual Behaviour

After creating the configuration profile, hitting the Connect button makes the status label change to Connecting but never to Connected

Steps to reproduce

  1. Connect mount to the Mac
  2. Run INDIGO Server and configure it properly. INDIGO Server shows the LX200 driver loaded
  3. Run Stellarium and configure the Telescope Control plugin. Choose INDI/INDIGO, host and port.
  4. Save configuration profile and press Connect
  5. Status label goes to Connecting and stays there forever

    System

    • Stellarium version: Stellarium-0.19.3.17629.dmg
    • Operating system: MacOS 10.15.2
    • Graphics Card: Built in Intel Iris

Logfile

If possible, attach the logfile log.txt from your user data directory. Look into the Guide for its location.

gzotti commented 4 years ago

Duplicate of #825?

gaevoc commented 4 years ago

Hi Georg, Almost yes. The main difference is that I am not working with a remote INDIGO Server but with one installed on the very same machine. I can also add that the connection works if the target mount is the INDIGO Server mount simulator.

Cheers Gaetano

Il giorno 29 gen 2020, alle ore 00:48, Georg Zotti notifications@github.com ha scritto:

 Duplicate of #825?

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or unsubscribe.

alex-w commented 4 years ago

Are you allow connect to localhost in Gatekeeper?

In any way please attach the logs from Stellarium.

gaevoc commented 4 years ago

Hi Alexander, Gatekeeper if off on my machine. Consider also that AstroTelescope works towards the same INDIGO Server.

Gaetano

On 29 Jan 2020, at 08:12, Alexander Wolf notifications@github.com wrote:

Are you allow connect to localhost in Gatekeeper?

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

gaevoc commented 4 years ago

Hi, Maybe it can be useful, log attached.

Gaetano

On 29 Jan 2020, at 08:28, Gaetano gaetano314@gmail.com wrote:

Hi Alexander, Gatekeeper if off on my machine. Consider also that AstroTelescope works towards the same INDIGO Server.

Gaetano

<Screenshot 2020-01-29 at 08.27.46.png>

On 29 Jan 2020, at 08:12, Alexander Wolf <notifications@github.com mailto:notifications@github.com> wrote:

Are you allow connect to localhost in Gatekeeper?

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

2020-01-29T08:32:26 Operating System: Darwin 19.2.0 x86_64 Compiled using Clang 11.0.0 Qt runtime version: 5.9.9 Qt compilation version: 5.9.9 Addressing mode: 64-bit Model Name: MacBook Pro Model Identifier: MacBookPro11,1 Processor Name: Dual-Core Intel Core i5 Processor Speed: 2,4 GHz Number of Processors: 1 Memory: 8 GB Chipset Model: Intel Iris VRAM (Dynamic, Max): 1536 MB /Applications/Stellarium.app/Contents/MacOS/stellarium

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

Writing log file to: "/Users/gvoc/Library/Application Support/Stellarium/log.txt" File search paths: 0 . "/Users/gvoc/Library/Application Support/Stellarium" 1 . "/Applications/Stellarium.app/Contents/Resources" Config file is: "/Users/gvoc/Library/Application Support/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::SwapBehavior(DefaultSwapBehavior), swapInterval 1, profile QSurfaceFormat::OpenGLContextProfile(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::SwapBehavior(DefaultSwapBehavior), swapInterval 0, profile QSurfaceFormat::OpenGLContextProfile(NoProfile)) StelGLWidget constructor StelGraphicsScene constructor initializeGL OpenGL supported version: "2.1 INTEL-14.3.9" Current Format: QSurfaceFormat(version 2.1, options QFlags(DeprecatedFunctions), depthBufferSize 24, redBufferSize 8, greenBufferSize 8, blueBufferSize 8, alphaBufferSize 8, stencilBufferSize 8, samples -1, swapBehavior QSurfaceFormat::SwapBehavior(DoubleBuffer), swapInterval 0, profile QSurfaceFormat::OpenGLContextProfile(NoProfile)) StelMainView::init Driver version string: "2.1 INTEL-14.3.9" GL vendor is "Intel Inc." GL renderer is "Intel Iris OpenGL Engine" GL Shading Language version is "1.20" Detected a high resolution device! Device pixel ratio: 2 Cache directory is: "/Users/gvoc/Library/Caches/stellarium/stellarium" Sky language is "en_US" Planetary features language is "en_US" Application language is "en_US" Couldn't load translations for language "en_US" in section "stellarium-scripts" 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 : "/Applications/Stellarium.app/Contents/Resources/data/ssystem_major.ini" SolarSystem has 83 entries. Loaded 83 Solar System bodies Loading Solar System data (2: minor bodies)... Loading from : "/Users/gvoc/Library/Application Support/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 15590 / 15592 items of planetary surface nomenclature WARNING - The next planets to assign nomenclature items is not found: "Dactyl" Loading star data ... "Loading /Applications/Stellarium.app/Contents/Resources/stars/default/stars_0_0v0_8.cat: 0_0v0_8; 4979" "Loading /Applications/Stellarium.app/Contents/Resources/stars/default/stars_1_0v0_8.cat: 1_0v0_8; 21806" "Loading /Applications/Stellarium.app/Contents/Resources/stars/default/stars_2_0v0_8.cat: 2_0v0_8; 150826" "Loading /Applications/Stellarium.app/Contents/Resources/stars/default/stars_3_1v0_4.cat: 3_1v0_4; 425807" Finished loading star catalogue data, max_geodesic_level: 3 Loading scientific star names from "/Applications/Stellarium.app/Contents/Resources/stars/default/name.fab" Loaded 4507 / 4507 scientific star names Loading variable stars from "/Applications/Stellarium.app/Contents/Resources/stars/default/gcvs_hip_part.dat" Loaded 6862 / 6862 variable stars Loading double stars from "/Applications/Stellarium.app/Contents/Resources/stars/default/wds_hip_part.dat" Loaded 16412 / 16412 double stars Loading cross-identification data from "/Applications/Stellarium.app/Contents/Resources/stars/default/cross-id.dat" Loaded 108338 / 108338 cross-identification data records for stars Loading parallax errors data from "/Applications/Stellarium.app/Contents/Resources/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: "2451514.25001" 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 "/Applications/Stellarium.app/Contents/Resources/skycultures/western/star_names.fab" Loaded 1004 / 1004 common star names Loading DSO name data ... Loaded 1084 / 1097 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 Error in Asterism "TA6" : can't find star with coordinates 2.14697 / 8.55097 ERROR reading asterism lines record at line 88 for culture "western" Loaded 81 / 82 asterism records successfully for culture "western" WARNING - asterism abbreviation "TA6" not found when loading asterism names Loaded 71 / 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 "Exoplanets" [Exoplanets] Version of the format of the catalog: 1 [Exoplanets] loading catalog file: "/Users/gvoc/Library/Application Support/Stellarium/modules/Exoplanets/exoplanets.json" Loaded plugin "MeteorShowers" [MeteorShowersMgr] Loading catalog file: "/Users/gvoc/Library/Application Support/Stellarium/modules/MeteorShowers/showers.json" Loaded plugin "Novae" [Novae] version of the catalog: 1 [Novae] loading catalog file: "/Users/gvoc/Library/Application Support/Stellarium/modules/Novae/novae.json" Loaded plugin "Oculars" Ocular plugin - press Command-O to toggle eyepiece view mode. Press ALT-o for configuration. Oculars::validateIniFile ocular.ini exists at: "/Users/gvoc/Library/Application Support/Stellarium/modules/Oculars/ocular.ini" . Checking version... Oculars::validateIniFile found existing ini file version 3.1 Loaded plugin "Satellites" [Satellites] loading catalog file: "/Users/gvoc/Library/Application Support/Stellarium/modules/Satellites/satellites.json" Loaded plugin "SolarSystemEditor" Using the ssystem_minor.ini file that already exists in the user directory... 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 [TelescopeControl] Loaded successfully 1 telescopes. SlewDialog::loadPointsFromFile(): No pointss loaded. File is missing: "/Users/gvoc/Library/Application Support/Stellarium/modules/TelescopeControl/points.json" [TelescopeControl] port name: "cu.Bluetooth-Incoming-Port" ; vendor identifier: 0 ; product identifier: 0 [TelescopeControl] port name: "tty.Bluetooth-Incoming-Port" ; vendor identifier: 0 ; product identifier: 0 [TelescopeControl] port name: "cu.usbserial-SGWF0453" ; vendor identifier: 1027 ; product identifier: 24597 [TelescopeControl] port name: "tty.usbserial-SGWF0453" ; vendor identifier: 1027 ; product identifier: 24597 [TelescopeControl] port name: "cu.Bluetooth-Incoming-Port" ; vendor identifier: 0 ; product identifier: 0 [TelescopeControl] port name: "tty.Bluetooth-Incoming-Port" ; vendor identifier: 0 ; product identifier: 0 [TelescopeControl] port name: "cu.usbserial-SGWF0453" ; vendor identifier: 1027 ; product identifier: 24597 [TelescopeControl] port name: "tty.usbserial-SGWF0453" ; vendor identifier: 1027 ; product identifier: 24597 [TelescopeControl] port name: "cu.Bluetooth-Incoming-Port" ; vendor identifier: 0 ; product identifier: 0 [TelescopeControl] port name: "tty.Bluetooth-Incoming-Port" ; vendor identifier: 0 ; product identifier: 0 [TelescopeControl] port name: "cu.usbserial-SGWF0453" ; vendor identifier: 1027 ; product identifier: 24597 [TelescopeControl] port name: "tty.usbserial-SGWF0453" ; vendor identifier: 1027 ; product identifier: 24597 [TelescopeControl] port name: "cu.Bluetooth-Incoming-Port" ; vendor identifier: 0 ; product identifier: 0 [TelescopeControl] port name: "tty.Bluetooth-Incoming-Port" ; vendor identifier: 0 ; product identifier: 0 [TelescopeControl] port name: "cu.usbserial-SGWF0453" ; vendor identifier: 1027 ; product identifier: 24597 [TelescopeControl] port name: "tty.usbserial-SGWF0453" ; vendor identifier: 1027 ; product identifier: 24597 [TelescopeControl] port name: "cu.Bluetooth-Incoming-Port" ; vendor identifier: 0 ; product identifier: 0 [TelescopeControl] port name: "tty.Bluetooth-Incoming-Port" ; vendor identifier: 0 ; product identifier: 0 [TelescopeControl] port name: "cu.usbserial-SGWF0453" ; vendor identifier: 1027 ; product identifier: 24597 [TelescopeControl] port name: "tty.usbserial-SGWF0453" ; vendor identifier: 1027 ; product identifier: 24597 INDIConnection::newDevice| New Device... "CCD Imager Simulator" INDIConnection::newProperty| "DRIVER_INFO" INDIConnection::newProperty| "SIMULATION" INDIConnection::newProperty| "CONFIG_PROCESS" INDIConnection::newProperty| "PROFILE" INDIConnection::newProperty| "CONNECTION" INDIConnection::newDevice| New Device... "CCD Imager Simulator (wheel)" INDIConnection::newProperty| "DRIVER_INFO" INDIConnection::newProperty| "CONFIG_PROCESS" INDIConnection::newProperty| "PROFILE" INDIConnection::newProperty| "CONNECTION" INDIConnection::newDevice| New Device... "CCD Imager Simulator (focuser)" INDIConnection::newProperty| "DRIVER_INFO" INDIConnection::newProperty| "CONFIG_PROCESS" INDIConnection::newProperty| "PROFILE" INDIConnection::newProperty| "CONNECTION" INDIConnection::newDevice| New Device... "CCD Guider Simulator" INDIConnection::newProperty| "DRIVER_INFO" INDIConnection::newProperty| "SIMULATION" INDIConnection::newProperty| "CONFIG_PROCESS" INDIConnection::newProperty| "PROFILE" INDIConnection::newProperty| "CONNECTION" INDIConnection::newProperty| "GUIDER_MODE" INDIConnection::newProperty| "GUIDER_IMAGE" INDIConnection::newDevice| New Device... "CCD Guider Simulator (guider)" INDIConnection::newProperty| "DRIVER_INFO" INDIConnection::newProperty| "CONFIG_PROCESS" INDIConnection::newProperty| "PROFILE" INDIConnection::newProperty| "CONNECTION" INDIConnection::newDevice| New Device... "CCD Guider Simulator (AO)" INDIConnection::newProperty| "DRIVER_INFO" INDIConnection::newProperty| "CONFIG_PROCESS" INDIConnection::newProperty| "PROFILE" INDIConnection::newProperty| "CONNECTION" INDIConnection::newDevice| New Device... "DSLR Simulator" INDIConnection::newProperty| "DRIVER_INFO" INDIConnection::newProperty| "SIMULATION" INDIConnection::newProperty| "CONFIG_PROCESS" INDIConnection::newProperty| "PROFILE" INDIConnection::newProperty| "CONNECTION" INDIConnection::newDevice| New Device... "Mount LX200" INDIConnection::newProperty| "X_MOUNT_TYPE" INDIConnection::newProperty| "DRIVER_INFO" INDIConnection::newProperty| "CONFIG_PROCESS" INDIConnection::newProperty| "PROFILE" INDIConnection::newProperty| "DEVICE_PORT" INDIConnection::newProperty| "DEVICE_PORTS" INDIConnection::newProperty| "CONNECTION" INDIConnection::newDevice| New Device... "Mount LX200 (guider)" INDIConnection::newProperty| "DRIVER_INFO" INDIConnection::newProperty| "CONFIG_PROCESS" INDIConnection::newProperty| "PROFILE" INDIConnection::newProperty| "CONNECTION" INDIConnection::newDevice| New Device... "Mount LX200 (focuser)" INDIConnection::newProperty| "DRIVER_INFO" INDIConnection::newProperty| "CONFIG_PROCESS" INDIConnection::newProperty| "PROFILE" INDIConnection::newProperty| "CONNECTION" INDIConnection::newDevice| New Device... "Mount Simulator" INDIConnection::newProperty| "DRIVER_INFO" INDIConnection::newProperty| "SIMULATION" INDIConnection::newProperty| "CONFIG_PROCESS" INDIConnection::newProperty| "PROFILE" INDIConnection::newProperty| "AUTHENTICATION" INDIConnection::newProperty| "CONNECTION" INDIConnection::newDevice| New Device... "Mount Simulator (guider)" INDIConnection::newProperty| "DRIVER_INFO" INDIConnection::newProperty| "CONFIG_PROCESS" INDIConnection::newProperty| "PROFILE" INDIConnection::newProperty| "CONNECTION" INDIConnection::newProperty| "TELESCOPE_TIMED_GUIDE_NS" INDIConnection::newProperty| "TELESCOPE_TIMED_GUIDE_WE" INDIConnection::newProperty| "GUIDER_RATE" connectionType: 6 initString: "New Telescope 1:INDI:J2000:localhost:7624:Mount LX200" Creating telescope "New Telescope 1:INDI:J2000:localhost:7624:Mount LX200" ; name/type/equinox/params: "New Telescope 1" "INDI" J2000 "localhost:7624:Mount LX200" TelescopeClientINDI::TelescopeClientINDI INDIConnection::newDevice| New Device... "Mount LX200" INDIConnection::newProperty| "X_MOUNT_TYPE" INDIConnection::newProperty| "MOUNT_INFO" INDIConnection::newProperty| "GEOGRAPHIC_COORD" INDIConnection::newProperty| "TIME_LST" INDIConnection::newProperty| "TELESCOPE_PARK" INDIConnection::newProperty| "MOUNT_HOME" INDIConnection::newProperty| "TELESCOPE_SLEW_RATE" INDIConnection::newProperty| "TELESCOPE_MOTION_NS" INDIConnection::newProperty| "TELESCOPE_MOTION_WE" INDIConnection::newProperty| "TELESCOPE_TRACK_RATE" INDIConnection::newProperty| "TELESCOPE_TRACK_STATE" INDIConnection::newProperty| "MOUNT_GUIDE_RATE" INDIConnection::newProperty| "ON_COORD_SET" INDIConnection::newProperty| "EQUATORIAL_EOD_COORD" INDIConnection::newProperty| "HORIZONTAL_COORD" INDIConnection::newProperty| "TELESCOPE_ABORT_MOTION" INDIConnection::newProperty| "MOUNT_EPOCH" INDIConnection::newProperty| "ACTIVE_DEVICES" INDIConnection::newProperty| "DRIVER_INFO" INDIConnection::newProperty| "CONFIG_PROCESS" INDIConnection::newProperty| "PROFILE" INDIConnection::newProperty| "DEVICE_PORT" INDIConnection::newProperty| "DEVICE_PORTS" INDIConnection::newProperty| "CONNECTION" INDIConnection::newDevice| New Device... "Mount Simulator" connectionType: 6 initString: "New Telescope 1:INDI:J2000:localhost:7624:Mount LX200" Creating telescope "New Telescope 1:INDI:J2000:localhost:7624:Mount LX200" ; name/type/equinox/params: "New Telescope 1" "INDI" J2000 "localhost:7624:Mount LX200" TelescopeClientINDI::TelescopeClientINDI INDIConnection::newDevice| New Device... "Mount LX200" INDIConnection::newProperty| "X_MOUNT_TYPE" INDIConnection::newProperty| "MOUNT_INFO" INDIConnection::newProperty| "GEOGRAPHIC_COORD" INDIConnection::newProperty| "TIME_LST" INDIConnection::newProperty| "TELESCOPE_PARK" INDIConnection::newProperty| "MOUNT_HOME" INDIConnection::newProperty| "TELESCOPE_SLEW_RATE" INDIConnection::newProperty| "TELESCOPE_MOTION_NS" INDIConnection::newProperty| "TELESCOPE_MOTION_WE" INDIConnection::newProperty| "TELESCOPE_TRACK_RATE" INDIConnection::newProperty| "TELESCOPE_TRACK_STATE" INDIConnection::newProperty| "MOUNT_GUIDE_RATE" INDIConnection::newProperty| "ON_COORD_SET" INDIConnection::newProperty| "EQUATORIAL_EOD_COORD" INDIConnection::newProperty| "HORIZONTAL_COORD" INDIConnection::newProperty| "TELESCOPE_ABORT_MOTION" INDIConnection::newProperty| "MOUNT_EPOCH" INDIConnection::newProperty| "ACTIVE_DEVICES" INDIConnection::newProperty| "DRIVER_INFO" INDIConnection::newProperty| "CONFIG_PROCESS" INDIConnection::newProperty| "PROFILE" INDIConnection::newProperty| "DEVICE_PORT" INDIConnection::newProperty| "DEVICE_PORTS" INDIConnection::newProperty| "CONNECTION" INDIConnection::newDevice| New Device... "Mount Simulator" [TelescopeControl] port name: "cu.Bluetooth-Incoming-Port" ; vendor identifier: 0 ; product identifier: 0 [TelescopeControl] port name: "tty.Bluetooth-Incoming-Port" ; vendor identifier: 0 ; product identifier: 0 [TelescopeControl] port name: "cu.usbserial-SGWF0453" ; vendor identifier: 1027 ; product identifier: 24597 [TelescopeControl] port name: "tty.usbserial-SGWF0453" ; vendor identifier: 1027 ; product identifier: 24597 [TelescopeControl] port name: "cu.Bluetooth-Incoming-Port" ; vendor identifier: 0 ; product identifier: 0 [TelescopeControl] port name: "tty.Bluetooth-Incoming-Port" ; vendor identifier: 0 ; product identifier: 0 [TelescopeControl] port name: "cu.usbserial-SGWF0453" ; vendor identifier: 1027 ; product identifier: 24597 [TelescopeControl] port name: "tty.usbserial-SGWF0453" ; vendor identifier: 1027 ; product identifier: 24597 [TelescopeControl] port name: "cu.Bluetooth-Incoming-Port" ; vendor identifier: 0 ; product identifier: 0 [TelescopeControl] port name: "tty.Bluetooth-Incoming-Port" ; vendor identifier: 0 ; product identifier: 0 [TelescopeControl] port name: "cu.usbserial-SGWF0453" ; vendor identifier: 1027 ; product identifier: 24597 [TelescopeControl] port name: "tty.usbserial-SGWF0453" ; vendor identifier: 1027 ; product identifier: 24597 connectionType: 6 initString: "New Telescope 1:INDI:J2000:localhost:7624:Mount LX200" Creating telescope "New Telescope 1:INDI:J2000:localhost:7624:Mount LX200" ; name/type/equinox/params: "New Telescope 1" "INDI" J2000 "localhost:7624:Mount LX200" TelescopeClientINDI::TelescopeClientINDI INDIConnection::newDevice| New Device... "Mount LX200" INDIConnection::newProperty| "X_MOUNT_TYPE" INDIConnection::newProperty| "MOUNT_INFO" INDIConnection::newProperty| "GEOGRAPHIC_COORD" INDIConnection::newProperty| "TIME_LST" INDIConnection::newProperty| "TELESCOPE_PARK" INDIConnection::newProperty| "MOUNT_HOME" INDIConnection::newProperty| "TELESCOPE_SLEW_RATE" INDIConnection::newProperty| "TELESCOPE_MOTION_NS" INDIConnection::newProperty| "TELESCOPE_MOTION_WE" INDIConnection::newProperty| "TELESCOPE_TRACK_RATE" INDIConnection::newProperty| "TELESCOPE_TRACK_STATE" INDIConnection::newProperty| "MOUNT_GUIDE_RATE" INDIConnection::newProperty| "ON_COORD_SET" INDIConnection::newProperty| "EQUATORIAL_EOD_COORD" INDIConnection::newProperty| "HORIZONTAL_COORD" INDIConnection::newProperty| "TELESCOPE_ABORT_MOTION" INDIConnection::newProperty| "MOUNT_EPOCH" INDIConnection::newProperty| "ACTIVE_DEVICES" INDIConnection::newProperty| "DRIVER_INFO" INDIConnection::newProperty| "CONFIG_PROCESS" INDIConnection::newProperty| "PROFILE" INDIConnection::newProperty| "DEVICE_PORT" INDIConnection::newProperty| "DEVICE_PORTS" INDIConnection::newProperty| "CONNECTION" INDIConnection::newDevice| New Device... "Mount Simulator"

rumengb commented 4 years ago

Hi, It looks to me that you did not configure the driver correctly. You have to specify the device port. Where the punt is connected physically. Mounts are not true USB devices they use usb to serial converters and therefore they are seen as serial devices although they use USB wires... It is the same with many focusers, filter wheels etc... So INDIGO and any other software can not tell what is connected to this converter and unfortunately the user should know... That is why the user should provide this information to the driver. imgpsh_fullsize_anim On this picture you can see where to specify it -> "Serial Port", if there are any serial ports the list below will show it, however I made this screenshot on a Virtual machine and I have no serial ports available, that is why the property is shown in red. Optionally for the LX200 driver you can specify which LX200 dialect the driver should speak as different manufacturers tend to provide a bit different functionality. Please let us know if this worked!

Rumen

gaevoc commented 4 years ago

Hi Rumen, thank you for your kind answer. Please consider that the connection between INDIGO Server and the mount works fine as I am able to use AstroTelescope without any problem. As said, when I try to connect Stellarium to INDIGO Server I get the Connecting issue. Actually, right after pushing the connect button, the status label goes to Connected for about half a second and then changes to Connecting again.

Afterwards, I can close Stellarium, open AstroTelescope again, connect it to the resident INDIGO Server and it move the mount.

I hope there is a way to fix it, I am currently using SkySafari Pro but I really would like to swap it for a better planetarium.

Cheers Gaetano

On Wed, Jan 29, 2020 at 1:02 PM Rumen Bogdanovski notifications@github.com wrote:

Hi, It looks to me that you did not configure the driver correctly. You have to specify the device port. Where the punt is connected physically. Mounts are not true USB devices they use usb to serial converters and therefore they are seen as serial devices although they use USB wires... It is the same with many focusers, filter wheels etc... So INDIGO and any other software can not tell what is connected to this converter and unfortunately the user should know... That is why the user should provide this information to the driver. [image: imgpsh_fullsize_anim] https://user-images.githubusercontent.com/20597893/73354668-ed328b00-429e-11ea-81d0-3a49453fd775.png On this picture you can see where to specify it -> "Serial Port", if there are any serial ports the list below will show it, however I made this screenshot on a Virtual machine and I have no serial ports available, that is why the property is shown in red. Optionally for the LX200 driver you can specify which LX200 dialect the driver should speak as different manufacturers tend to provide a bit different functionality. Please let us know if this worked!

Rumen

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

rumengb commented 4 years ago

Can you give me more detailed information, where is INDIGO server running? Same Mac host? Are you sure you are not using the built in AstroTelescope INDIGO drivers but you are using the INDIGO server ones? Can you start the indigo control panel in parallel with stellarium and see what is the state of "Connection status" while stellarium says "connected".

Can you provide INDIGO server log?

gaevoc commented 4 years ago

Hi Rumen, sure, I can provide all the info you may need.

As I wrote in my first description of the problem, I am running Stellarium and INDIGO Server (IS) on the same machine, Gatekeeper is not active. I am reasonably confident that I am contacting IS and not AT, I also trie without launching AT at all.

Maybe it can be useful to attach these two screenshots that show you the status of IS and Stellarium during a connection attempt.

Thank you G

On Wed, Jan 29, 2020 at 3:58 PM Rumen Bogdanovski notifications@github.com wrote:

Can you give me more detailed information, where is INDIGO server running? Same Mac host? Are you sure you are not using the built in AstroTelescope INDIGO drivers but you are using the INDIGO server ones? Can you start the indigo control panel in parallel with stellarium and see what is the state of "Connection status" while stellarium says "connected".

Can you provide INDIGO server 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/952?email_source=notifications&email_token=ABNHXU3H5XO77MV6NIPVPVLRAGKQXA5CNFSM4KM3WZEKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEKHPH7A#issuecomment-579793916, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABNHXU574ZX2CJYF2LD6TIDRAGKQXANCNFSM4KM3WZEA .

gaevoc commented 4 years ago

Hello, Here I am again. I just made few more tests andI can confirm all I wrote before including that the connection attempt is made towards INDIGO Server, for sure.

I attach here the requested INDIGO Server logs.

Hope this helps G

On 29 Jan 2020, at 17:39, gaetano vocca gaetano314@gmail.com wrote:

Hi Rumen, sure, I can provide all the info you may need.

As I wrote in my first description of the problem, I am running Stellarium and INDIGO Server (IS) on the same machine, Gatekeeper is not active. I am reasonably confident that I am contacting IS and not AT, I also trie without launching AT at all.

Maybe it can be useful to attach these two screenshots that show you the status of IS and Stellarium during a connection attempt.

Thank you G

On Wed, Jan 29, 2020 at 3:58 PM Rumen Bogdanovski <notifications@github.com mailto:notifications@github.com> wrote: Can you give me more detailed information, where is INDIGO server running? Same Mac host? Are you sure you are not using the built in AstroTelescope INDIGO drivers but you are using the INDIGO server ones? Can you start the indigo control panel in parallel with stellarium and see what is the state of "Connection status" while stellarium says "connected".

Can you provide INDIGO server 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/952?email_source=notifications&email_token=ABNHXU3H5XO77MV6NIPVPVLRAGKQXA5CNFSM4KM3WZEKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEKHPH7A#issuecomment-579793916, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABNHXU574ZX2CJYF2LD6TIDRAGKQXANCNFSM4KM3WZEA.

<Screenshot 2020-01-28 at 20.55.10.png><Screenshot 2020-01-28 at 20.55.29.png>

rumengb commented 4 years ago

I can not reproduce the issue :( However I use LX200 simulator but the driver is the same and the Stellarium is the last build. And it works for me... I do not have real lx200 i use arduino simulator but this is not the issue.. Stellarium seems to be working... Are you using the last build?

Screen Shot 2020-01-29 at 21 55 06

gaevoc commented 4 years ago

Hi Rumen, Just a couple of notes:

If there is any other test you want me to perform don’t hesitate to ask, I will do my best

Gaetano

On 29 Jan 2020, at 21:03, Rumen Bogdanovski notifications@github.com wrote:

I can not reproduce the issue :( However I use LX200 simulator but the driver is the same and the Stellarium is the last build. And it works for me... However I do not have real lx200 i use arduino simulator but this is not the issue.. Stellarium seems to be working... Are you using the last build?

https://user-images.githubusercontent.com/20597893/73392608-d1e96f00-42e2-11ea-8caa-01b3ead95575.png — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/Stellarium/stellarium/issues/952?email_source=notifications&email_token=ABNHXU6BSJUNW6F4YLIP4ELRAHOKTA5CNFSM4KM3WZEKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEKIRWEA#issuecomment-579934992, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABNHXU7ACA6JTLPQGJHCBMLRAHOKVANCNFSM4KM3WZEA.

gaevoc commented 4 years ago

Hi again, Please disregard my last point below, I was able to find 0.9.3.17636 but it doesn’t work either

G

On 29 Jan 2020, at 23:10, Gaetano gaetano314@gmail.com wrote:

Hi Rumen, Just a couple of notes:

  • My mount is an Avalon Linear. Avalon uses a dialect of LX200 which is generally compatible with most of the generic LX200 implementations. There are some exceptions that are documented in a dedicated specification.
  • AstroTelescope works fine using the LX200 Classic driver, I never had any issue in the connection phase but I know that Peter (Polakovic) had to make some little changes to provide some of the extensions of the protocol
  • If I use the mount emulator provided by INDIGO Server the connection works
  • I see you are running version 0.19.3.17636 but on this page https://github.com/Stellarium/stellarium-data/releases/tag/beta https://github.com/Stellarium/stellarium-data/releases/tag/beta I can only find the 0.9.3.17629 package

If there is any other test you want me to perform don’t hesitate to ask, I will do my best

Gaetano

On 29 Jan 2020, at 21:03, Rumen Bogdanovski <notifications@github.com mailto:notifications@github.com> wrote:

I can not reproduce the issue :( However I use LX200 simulator but the driver is the same and the Stellarium is the last build. And it works for me... However I do not have real lx200 i use arduino simulator but this is not the issue.. Stellarium seems to be working... Are you using the last build?

https://user-images.githubusercontent.com/20597893/73392608-d1e96f00-42e2-11ea-8caa-01b3ead95575.png — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/Stellarium/stellarium/issues/952?email_source=notifications&email_token=ABNHXU6BSJUNW6F4YLIP4ELRAHOKTA5CNFSM4KM3WZEKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEKIRWEA#issuecomment-579934992, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABNHXU7ACA6JTLPQGJHCBMLRAHOKVANCNFSM4KM3WZEA.

rumengb commented 4 years ago

Hi, I am pretty aware of the Indigo development :) Peter and I started Indigo project several years ago :)

Anyway, it would be nice if you provide us with detailed Indigo server log. To do so start Indigo server, go to "Indigo server -> preferences - > Indigo - > log level" and select "trace" . Then make a single attempt to connect from stellarium. Then save the log from "control-> save log" and send it here.

gaevoc commented 4 years ago

Hi Rumen, I know you are the other half of Indigo astronomy :) , thank you so much for your work!

About the Indigo, Server logs, I sent one yesterday, here is another

Have a nice day Gaetano

On 30 Jan 2020, at 03:56, Rumen Bogdanovski notifications@github.com wrote:

Hi, I am pretty aware of the Indigo development :) Peter and I started Indigo project several years ago :)

Anyway, it would be nice if you provide us with detailed Indigo server log. To do so start Indigo server, go to Indigo server-> preferences - > log level and select trace. Then make a single attempt to connect from stellarium. Then save the log and send it here.

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

alex-w commented 4 years ago

@gaevoc please use web interface for attach the logs, because github remove all attachments through email interface

rumengb commented 4 years ago

I do not see any logs :(

gaevoc commented 4 years ago

Hi, I didn't know that attachments were not propagated via email

Sorry

log_is_1.txt.zip

gaevoc commented 4 years ago

And this si another from a,previous session is.txt.zip

rumengb commented 4 years ago

I looked in the logs and I do not see any issue... The LX200 is connected and recognized and responds to commands. To be honest I have no idea what is wrong! From INDIGO point of view it is connected and operational (see my comments in bold capital):

HERE STELLARIUM REQUESTS CONNECT: 20:16:34.147 INDIGO Bus: property change request 20:16:34.147 'Mount LX200'.'CONNECTION' SWITCH UNDEFINED Idle 2.0 UNDEFINED { 20:16:34.148 'CONNECTED' = On 20:16:34.148 }

HERE INDIGO ANSWERS STELLARIUM THAT IT IS CONNECTED: 20:16:34.148 INDIGO Bus: property update 20:16:34.148 'Mount LX200'.'CONNECTION' SWITCH rw Busy 2.0 OneOfMany { 20:16:34.148 'CONNECTED' = On 20:16:34.149 'DISCONNECTED' = Off 20:16:34.149 } 20:16:34.157 indigo_mount_lx200: Connected to /dev/cu.usbserial-SGWF0453

HERE INDIGO ASKS THE MOUNT WHAT KIND OF MOUNT IS CONNECTED AND THE MOUNT ANSWERS: 20:16:34.275 indigo_mount_lx200[meade_command:179]: Command :GVP# -> Avalon 20:16:34.287 indigo_mount_lx200: Product: Avalon

HERE INDIGO LETS THE CLIENT KNOW THAT WE HAVE AVALON MOUNT (STELLARIUM SHOULD NOT CARE, AND SHOULD IGNORE THIS AS IT PROBABLY DOES): 20:16:34.288 INDIGO Bus: property update 20:16:34.288 'Mount LX200'.'X_MOUNT_TYPE' SWITCH rw Ok 2.0 OneOfMany { 20:16:34.288 'DETECT' = Off 20:16:34.288 'MEADE' = Off 20:16:34.288 'EQMAC' = Off 20:16:34.289 '10MIC' = Off 20:16:34.289 'GEMINI' = Off 20:16:34.289 'AVALON' = On 20:16:34.289 'AP' = Off 20:16:34.289 'ONSTEP' = Off 20:16:34.290 }

HERE IS SOME CHAT BETWEEN DRIVER AND MOUNT (ALL IS GOOD!): 20:16:34.419 indigo_mount_lx200[meade_command:179]: Command :X34# -> m10 20:16:34.547 indigo_mount_lx200[meade_command:179]: Command :X22# -> 35b45 20:16:34.675 indigo_mount_lx200[meade_command:179]: Command :Gt# -> +40t40:00 20:16:34.803 indigo_mount_lx200[meade_command:179]: Command :Gg# -> +014g47:00 20:16:34.931 indigo_mount_lx200[meade_command:179]: Command :GR# -> 00:00:13 20:16:35.059 indigo_mount_lx200[meade_command:179]: Command *:GD# -> +0000:00 20:16:35.187 indigo_mount_lx200[meade_command:179]: Command :X34# -> m10** 20:16:35.204 timer #0 (of 1) used for 0s

I do not see any issues :( And I can not even reproduce the problem :(

Sorry!

Rumen

gaevoc commented 4 years ago

Hi Rumen, indeed this is the evidence, the dialog between INDIGO Server and the mount is all fine and the mount is correctly operational. The problem is between Stellarium and INDIGO Server as Stellarium doesn't report the mount as connected and doesn't allow any slew. You analysis confirms my experience so, to me, the investigation should be performed within Stellarium to understand why it is unable to detect the correct connection status.

Thank you for your support and your kindness Gaetano

alex-w commented 4 years ago

Please show version of INDIGO server and list of loaded drivers.

gaevoc commented 4 years ago

Hi Alexander, currently I have INDIGO Server version 3.12 (505) and the loaded drivers are

G

On Fri, Jan 31, 2020 at 1:17 PM Alexander Wolf notifications@github.com wrote:

Please show version of INDIGO server and list of loaded drivers.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/Stellarium/stellarium/issues/952?email_source=notifications&email_token=ABNHXU7YV2EOTWIQFEST6ILRAQJE7A5CNFSM4KM3WZEKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEKOPFXQ#issuecomment-580711134, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABNHXU62VXSXQWQYD2W7LTTRAQJE7ANCNFSM4KM3WZEA .

alex-w commented 4 years ago

Could you for disable all simulator drivers, restart INDIGO server and try connect again (just for test)?

gaevoc commented 4 years ago

Sure, I can test it this evening, I will let you know.

Thanks for your suggestion

alex-w commented 4 years ago

Just for understanding: I've install INDIGO Server on macOS and tested connection to it from Stellarium (on macOS too) - it works. But note - please check number of port in INDIGO Server settings and in Stellarium - it should be same!

gaevoc commented 4 years ago

Hi Alex, yes, this is as expected. As I wrote in the issue description, there is no problem when connecting Stellarium to the mount simulator in INDIGO Server. The connection doesn't work with the following chain:

Consider that the connection branch between INDIGO Server and the Avalon mount is up and running, but Stellarium is unable to connect to INDIGO Server in this configuration.

alex-w commented 4 years ago

Please enable logging in Telescope Control plugin, try connect to INDIGO server and attach the log here

gaevoc commented 4 years ago

Hi, this is the log I retrieved few days ago, if you want I can take it again log.txt

gaevoc commented 4 years ago

Dear all, big news, removing everything but the Mount LX200 I can get connected!!

I' m even able to manually move the mount using the arrow buttons but slewing still doesn't work. Thank you for your suggestion, common, let's make it work 100% :)

Here is the log with some attempts to slew log.txt

gaevoc commented 4 years ago

Hi, one more update to this issue, due to a bizarre scenario. Now, suppose to:

In some ways AstroTelescope makes Stellarium able to slew, stop AstroTelescope and Stellarium stops working.

I hope this helps

gaevoc commented 4 years ago

Hi all, the missing slew may be due to Stellarium not handling correctly the mount parking status. To recap, after setting up the chain Stellarium - INDIGO Server - Avalon mount, you can connect and move the mount only manually, using the arrow buttons, no go-to an object. In the INDIGO server panel the mount is shown as "unparked". Now, if you park and unpark the mount using the INDIGO server panel, the slew command from Stellarium works again.

Hope this helps a bit in investigation about this integration

gaevoc commented 4 years ago

Hi, Quick update on this topic. The current available beta 0.19.3.17695 of Stellarium improves the overall behavior towards an Avalon mount, it is now possible to connect to the mount and to slew it correctly. I will perform some more tests and report here.

gaevoc commented 4 years ago
Screenshot 2020-03-01 at 18 18 11

Stellarium 0.19.3.17733 shows again the connection problem. The connection phase was fine until 0.19.3.17722 but now the dialog shows the status as Connected and then Connecting again. Tested against INDIGO Server 3.12 (505)

gaevoc commented 4 years ago

Actually the behaviour seems to be a little unstable, now I was able to connect correctly. Out of 10 trials I connected successfully 7 times

alex-w commented 3 years ago

Please check the fresh version (development snapshot) of Stellarium: https://github.com/Stellarium/stellarium-data/releases/tag/weekly-snapshot