×

INDI Library v2.0.7 is Released (01 Apr 2024)

Bi-monthly release with minor bug fixes and improvements

Read More...

Driver OnStep (LX200 like) for INDI

  • Posts: 144
  • Thank you received: 7

Replied by Ettore on topic Driver OnStep (LX200 like) for INDI

Hello, why in wifi have this error:

2023-01-29T19:44:55: [WARNING] Communication error on Barometer (:GX9B#), this update aborted, will try again...
2023-01-29T19:42:55: [WARNING] Communication error on backlash (:%BD#/:%BR#), this update aborted, will try again...
2023-01-29T19:35:21: [WARNING] Communication error on backlash (:%BD#/:%BR#), this update aborted, will try again...
2023-01-29T19:31:21: [INFO] Setting Max Slew Rate to 6 (24x)
2023-01-29T19:31:16: [WARNING] Communication error on Humidity (:GX9C#), this update aborted, will try again...
2023-01-29T19:30:29: [INFO] Slewing to RA: 11:33:40 - DEC: 79:44:43
2023-01-29T19:29:57: [INFO] Setting Max Slew Rate to 7 (48x)

Regards.
Ettore.
1 year 2 months ago #90000

Please Log in or Create an account to join the conversation.

  • Posts: 144
  • Thank you received: 7

Replied by Ettore on topic Driver OnStep (LX200 like) for INDI

Nothing response.
1 year 2 months ago #90051

Please Log in or Create an account to join the conversation.

  • Posts: 144
  • Thank you received: 7

Replied by Ettore on topic Driver OnStep (LX200 like) for INDI

Hello, why in wifi have this error:

2023-01-29T19:44:55: [WARNING] Communication error on Barometer (:GX9B#), this update aborted, will try again...
2023-01-29T19:42:55: [WARNING] Communication error on backlash (:%BD#/:%BR#), this update aborted, will try again...
2023-01-29T19:35:21: [WARNING] Communication error on backlash (:%BD#/:%BR#), this update aborted, will try again...
2023-01-29T19:31:21: [INFO] Setting Max Slew Rate to 6 (24x)
2023-01-29T19:31:16: [WARNING] Communication error on Humidity (:GX9C#), this update aborted, will try again...
2023-01-29T19:30:29: [INFO] Slewing to RA: 11:33:40 - DEC: 79:44:43
2023-01-29T19:29:57: [INFO] Setting Max Slew Rate to 7 (48x)

Regards.
Ettore.
1 year 2 months ago #90117

Please Log in or Create an account to join the conversation.

  • Posts: 29
  • Thank you received: 3

Replied by lanco on topic Driver OnStep (LX200 like) for INDI

Any Tips for station mode wifi connect crash？

On my computer，onstep INDI wifi connection is 100% got crash.
1 year 2 months ago #90287

Please Log in or Create an account to join the conversation.

  • Posts: 452
  • Thank you received: 71

Replied by Alain Zwingelstein on topic Driver OnStep (LX200 like) for INDI

WiFi concerns:

I cannot reproduce loss of connection nor crash.
my configuration is:
================= OS version
PRETTY_NAME="Debian GNU/Linux 11 (bullseye)"
NAME="Debian GNU/Linux"
VERSION_ID="11"
VERSION="11 (bullseye)"
VERSION_CODENAME=bullseye
ID=debian
HOME_URL="https://www.debian.org/"
SUPPORT_URL="https://www.debian.org/support"
BUG_REPORT_URL="https://bugs.debian.org/"
================= indiserver 
2023-02-07T20:48:23: startup: indiserver -v
Usage: indiserver [options] driver [driver ...]
Purpose: server for local and remote INDI drivers
INDI Library: 2.0.1
Code v1.9.6-411-gb4f3497ce. Protocol 1.7.
================= kstars version
kstars 3.6.4 Beta 
========= tests done with ======== OnStep 4.24s and OnStepX 10.11i

may be you could use Khalid's wonderfull Python tool to test communication github.com/kbahey/onstep-python

Also could you please define which versions you use
OS version
cat /etc/os-release
Indi version
indiserver -v &>> infos
kstars version
kstars -v >>
it would help

another option would be to test is with indi_lx200_TeenAstro driver the problem is the same
The following user(s) said Thank You: lanco
1 year 2 months ago #90292

Please Log in or Create an account to join the conversation.

  • Posts: 161
  • Thank you received: 39

Replied by james_lan on topic Driver OnStep (LX200 like) for INDI

It's generally lost connection or a communication error. So it skips the rest of the update on error. You'd need to have verbose logs on and find where that is to see what's going on. Could be parsing a reply (maybe a change in OnStep) or something else.
The following user(s) said Thank You: lanco
1 year 2 months ago #90370

Please Log in or Create an account to join the conversation.

  • Posts: 144
  • Thank you received: 7

Replied by Ettore on topic Driver OnStep (LX200 like) for INDI

Repete may last message. in WIF onstep have may error:
2023-02-11T20:08:31: [WARNING] Communication error on Align Status Update, this update aborted, will try again...
2023-02-11T20:08:31: [WARNING] Fail Align Command
2023-02-11T20:08:31: [INFO] Getting Alignment Status: response Error, response = >
2023-02-11T20:08:22: [WARNING] Communication error on backlash (:%BD#/:%BR#), this update aborted, will try again...
2023-02-11T20:05:07: [INFO] Polar Align Error Status response Error, response = >
2023-02-11T20:03:37: [WARNING] Communication error on Dewpoint (:GX9E#), this update aborted, will try again...
2023-02-11T19:55:54: [WARNING] Communication error on Preferred Pier Side (:GX96#), this update aborted, will try again...
2023-02-11T19:53:30: [WARNING] Communication error on Degrees past Meridian West (:GXEA#), this update aborted, will try again...
2023-02-11T19:53:21: [WARNING] This update aborted, will try again...
2023-02-11T19:53:21: [INFO] RA/DEC could not be read, possible solution if using (wireless) ethernet: Use port 9998
2023-02-11T19:53:15: [WARNING] Communication error on Humidity (:GX9C#), this update aborted, will try again...
2023-02-11T19:51:50: [WARNING] Communication error on Degrees past Meridian East (:GXE9#), this update aborted, will try again...
2023-02-11T19:50:55: [WARNING] Communication error on Preferred Pier Side (:GX96#), this update aborted, will try again...
2023-02-11T19:49:15: [WARNING] Communication error on backlash (:%BD#/:%BR#), this update aborted, will try again...
2023-02-11T19:47:32: [WARNING] Communication error on Degrees past Meridian West (:GXEA#), this update aborted, will try again...
2023-02-11T19:46:06: [INFO] Polar Align Error Status response Error, response = >
2023-02-11T19:25:42: [WARNING] Communication error on Humidity (:GX9C#), this update aborted, will try again...
2023-02-11T19:23:12: [WARNING] This update aborted, will try again...
2023-02-11T19:23:12: [INFO] RA/DEC could not be read, possible solution if using (wireless) ethernet: Use port 9998
2023-02-11T19:23:01: [WARNING] This update aborted, will try again...
2023-02-11T19:23:01: [INFO] RA/DEC could not be read, possible solution if using (wireless) ethernet: Use port 9998
2023-02-11T19:11:21: [INFO] OnStep: Synchronization successful.
2023-02-11T19:06:02: [WARNING] Communication error on backlash (:%BD#/:%BR#), this update aborted, will try again...
2023-02-11T19:02:28: [WARNING] Communication error on backlash (:%BD#/:%BR#), this update aborted, will try again...
2023-02-11T18:58:55: [ERROR] Check system & Align if doing align to see if it went through!
2023-02-11T18:58:55: [ERROR] Unexpected return on sync call!
2023-02-11T18:58:54: [WARNING] Communication error on Preferred Pier Side (:GX96#), this update aborted, will try again...
2023-02-11T18:58:26: [INFO] Slewing to RA: 2:35:07 - DEC: 61:32:50
2023-02-11T18:58:26: [INFO] OnStep: Synchronization successful.
2023-02-11T18:58:00: [INFO] Slewing to RA: 2:35:07 - DEC: 61:32:50
2023-02-11T18:57:59: [INFO] OnStep: Synchronization successful.
2023-02-11T18:57:33: [INFO] Slewing to RA: 2:35:07 - DEC: 61:32:50
2023-02-11T18:57:33: [INFO] OnStep: Synchronization successful.
2023-02-11T18:57:11: [INFO] Slewing to RA: 2:35:07 - DEC: 61:32:50
2023-02-11T18:57:10: [INFO] OnStep: Synchronization successful.
2023-02-11T18:56:44: [INFO] Slewing to RA: 2:35:07 - DEC: 61:32:50
2023-02-11T18:56:44: [INFO] OnStep: Synchronization successful.
2023-02-11T18:56:18: [INFO] Slewing to RA: 2:35:07 - DEC: 61:32:50
2023-02-11T18:56:18: [INFO] OnStep: Synchronization successful.
2023-02-11T18:55:48: [INFO] Slewing to RA: 2:35:07 - DEC: 61:32:50
2023-02-11T18:55:47: [INFO] OnStep: Synchronization successful.
2023-02-11T18:55:11: [INFO] Slewing to RA: 2:35:07 - DEC: 61:32:50
2023-02-11T18:55:11: [INFO] OnStep: Synchronization successful.
2023-02-11T18:53:40: [INFO] Slewing to RA: 2:35:07 - DEC: 61:32:50
2023-02-11T18:52:56: [INFO] Observer location updated: Latitude 46:10:58.0 (46.18) Longitude 13:32:59.0 (13.55)
2023-02-11T18:52:56: [INFO] Site location updated to Lat 46:10:58.00 - Long 13:32:59.00
2023-02-11T18:52:56: [INFO] Time updated, updating planetary data...
2023-02-11T18:52:56: [INFO] Device configuration applied.
2023-02-11T18:52:56: [INFO] Pulse guiding is enabled.
2023-02-11T18:52:56: [INFO] Custom tracking rates set. Tracking mode must be set to Custom for these rates to take effect.
2023-02-11T18:52:56: [INFO] Setting Max Slew Rate to 5 (8x)
2023-02-11T18:52:56: [INFO] Observer location updated: Latitude 46:10:58.0 (46.18) Longitude 13:32:59.0 (13.55)
2023-02-11T18:52:56: [INFO] Site location updated to Lat 46:10:58.00 - Long 13:32:59.00
2023-02-11T18:52:56: [INFO] Dome Policy set to: Dome ignored. Mount can park or unpark regardless of dome parking state.
2023-02-11T18:52:56: [INFO] Loading device configuration...
2023-02-11T18:52:51: [INFO] Initialization Complete
2023-02-11T18:52:51: [INFO] Mount is unparked.
2023-02-11T18:52:51: [INFO] No Rotator found.
2023-02-11T18:52:51: [INFO] No Focusers found
2023-02-11T18:52:51: [INFO] Focuser 2 NOT found
2023-02-11T18:52:51: [INFO] Focuser 1 NOT found
2023-02-11T18:52:51: [INFO] Network based connection, detection timeouts set to 2 seconds
2023-02-11T18:52:51: [INFO] =============== Parkdata loaded
2023-02-11T18:52:51: [INFO] Mount is unparked.
2023-02-11T18:52:51: [INFO] V4 OnStep detected, setting some defaults
2023-02-11T18:52:50: [INFO] Mount has Latitude 46:10:58.0 (46.1828) Longitude 13:32:59.0 (13.5497) (Longitude sign in carthography format)
2023-02-11T18:52:50: [INFO] Telescope detected having Pier Side, adding that capability (many messages duplicated)
2023-02-11T18:52:50: [INFO] Initialization Complete
2023-02-11T18:52:50: [INFO] Mount is unparked.
2023-02-11T18:52:50: [INFO] No Rotator found.
2023-02-11T18:52:50: [INFO] No Focusers found
2023-02-11T18:52:50: [INFO] Focuser 2 NOT found
2023-02-11T18:52:50: [INFO] Focuser 1 NOT found
2023-02-11T18:52:50: [INFO] Network based connection, detection timeouts set to 2 seconds
2023-02-11T18:52:50: [INFO] =============== Parkdata loaded
2023-02-11T18:52:50: [INFO] Mount is unparked.
2023-02-11T18:52:50: [INFO] V4 OnStep detected, setting some defaults
2023-02-11T18:52:48: [INFO] Mount has Latitude 46:10:58.0 (46.1828) Longitude 13:32:59.0 (13.5497) (Longitude sign in carthography format)
2023-02-11T18:52:48: [INFO] Telescope detected having PEC, setting that capability
2023-02-11T18:52:48: [INFO] Initialization Complete
2023-02-11T18:52:48: [INFO] Mount is unparked.
2023-02-11T18:52:48: [INFO] Outputs not detected, disabling further checks
2023-02-11T18:52:46: [INFO] No Rotator found.
2023-02-11T18:52:46: [INFO] No Focusers found
2023-02-11T18:52:46: [INFO] Focuser 2 NOT found
2023-02-11T18:52:46: [INFO] Focuser 1 NOT found
2023-02-11T18:52:45: [INFO] Network based connection, detection timeouts set to 2 seconds
2023-02-11T18:52:45: [INFO] =============== Parkdata loaded
2023-02-11T18:52:45: [INFO] Mount is unparked.
2023-02-11T18:52:45: [INFO] V4 OnStep detected, setting some defaults
2023-02-11T18:52:45: [INFO] Mount has Latitude 46:10:0.0 (46.1667) Longitude 13:32:0.0 (13.5333) (Longitude sign in carthography format)
2023-02-11T18:52:45: [INFO] LX200 OnStep is online.
2023-02-11T18:52:44: [INFO] Connecting to 192.168.1.110@9998 ...
1 year 2 months ago #90434
Attachments:

Please Log in or Create an account to join the conversation.

  • Posts: 452
  • Thank you received: 71

Replied by Alain Zwingelstein on topic Driver OnStep (LX200 like) for INDI

What version of OnStep do you use?
OnStepX ( Version 10.) and OnStep (Version 4.24.s ) do not behave exactly the same.

Strange you have a good communication all along initailisation and then loose apparently communication.
What has changed between last working set-up?
OnStep Update?
Raspbian Update?
Indi Update (seems not since it shows upo version 1.17)

Again doing some tests with Khalid's Python secript would help a lot to exclude WiFi as a source of problem since I canno reproduce the error here with eitehr OnStep and OnStep X with all other beeing nightly builds.
1 year 2 months ago #90449

Please Log in or Create an account to join the conversation.

  • Posts: 144
  • Thank you received: 7

Replied by Ettore on topic Driver OnStep (LX200 like) for INDI

Thank for response.
I use onstep version 4.24 s.
I've always had this problem and I've opened 3 requests with no response.
I use latest indi and raspbian 64bit bullseye.
If use usb nothing problems.
Regards.
Ettore
1 year 2 months ago #90451

Please Log in or Create an account to join the conversation.

  • Posts: 452
  • Thank you received: 71

Replied by Alain Zwingelstein on topic Driver OnStep (LX200 like) for INDI

Ettore,

here my logs with OnStep 4.2.m and WiFi
 

As you can see I have no timeouts and so.
I definitively woul go for testing with github.com/kbahey/onstep-python
1 year 2 months ago #90458

Please Log in or Create an account to join the conversation.

  • Posts: 452
  • Thank you received: 71

Replied by Alain Zwingelstein on topic Driver OnStep (LX200 like) for INDI 

INFO	0.014132 sec	: Session log file /home/alain/.indi/logs/2023-02-12/indi_lx200_OnStep/indi_lx200_OnStep_10:39:52.log
DEBUG	104.752574 sec	: Connecting to 192.168.0.40@9998 ...
DEBUG	104.783056 sec	: Connection to 192.168.0.40@9998 is successful, attempting handshake...
DEBUG	104.783186 sec	: Testing telescope connection using ACK...
DEBUG	104.786724 sec	: Testing successful!
INFO	104.786907 sec	: LX200 OnStep is online.
DEBUG	104.788146 sec	: Configuration successfully saved.
DEBUG	104.789793 sec	: Configuration successfully saved for CONNECTION_TYPE.
DEBUG	104.792538 sec	: Configuration successfully saved for DEVICE_LAN_SEARCH.
DEBUG	104.794130 sec	: Configuration successfully saved for CONNECTION_MODE.
SCOPE	104.795390 sec	: CMD <:GR#>
SCOPE	104.800470 sec	: RES <21:57:06>
SCOPE	104.800549 sec	: Equatorial coordinate format is high precision.
SCOPE	104.800566 sec	: <ACK>
SCOPE	104.800579 sec	: CMD <0X6>
SCOPE	104.803740 sec	: RES <P>
SCOPE	104.803844 sec	: <getTimeFormat>
SCOPE	104.803859 sec	: CMD <:Gc#>
SCOPE	104.807840 sec	: RES <24>
SCOPE	104.807901 sec	: <getSiteName>
SCOPE	104.807919 sec	: CMD <:GM#>
SCOPE	104.814861 sec	: RES <Schoenau>
DEBUG	104.814929 sec	: Site Name <Schoenau>
SCOPE	104.814960 sec	: <getTrackFreq>
SCOPE	104.814972 sec	: CMD <:GT#>
SCOPE	104.820025 sec	: RES <0.00000#>
SCOPE	104.820106 sec	: VAL [0]
SCOPE	104.820153 sec	: <getSiteLatitudeAlt>
SCOPE	104.820177 sec	: CMD <:Gt#>
SCOPE	104.824835 sec	: RES <+48*13>
SCOPE	104.824898 sec	: VAL [48,13,0.0]
SCOPE	104.824937 sec	: <getSiteLongitudeAlt>
SCOPE	104.824953 sec	: CMD <:Gg#>
SCOPE	104.830054 sec	: RES <-007*38>
SCOPE	104.830122 sec	: VAL in CartographicLongitude format [7,38,0.0]
INFO	104.830160 sec	: Mount has Latitude 48:13:0.0 (48.2167) Longitude 07:38:0.0 (7.63333) (Longitude sign in carthography format)
DEBUG	104.831117 sec	: Configuration successfully saved for GEOGRAPHIC_COORD.
SCOPE	104.831179 sec	: CMD <:GG#>
SCOPE	104.835108 sec	: RES <-01>
SCOPE	104.835182 sec	: VAL [-1]
SCOPE	104.835216 sec	: CMD <:GL#>
SCOPE	104.840657 sec	: RES <21:57:20>
SCOPE	104.840707 sec	: VAL [21.9556]
SCOPE	104.840735 sec	: <getCalendarDate>
SCOPE	104.840750 sec	: CMD <:GC#>
SCOPE	104.845993 sec	: RES <12/28/22>
DEBUG	104.846048 sec	: Mount controller UTC Time: 2022-12-28T20:57:20
DEBUG	104.846065 sec	: Mount controller UTC Offset: 1.00
SCOPE	104.846092 sec	: CMD <:GVD#>
SCOPE	104.852224 sec	: RES <Nov 22 2021>
SCOPE	104.852254 sec	: CMD <:GVT#>
SCOPE	104.857517 sec	: RES <10:57:08>
SCOPE	104.857542 sec	: CMD <:GVN#>
SCOPE	104.862933 sec	: RES <4.24m>
SCOPE	104.863004 sec	: CMD <:GVP#>
SCOPE	104.867946 sec	: RES <On-Step>
INFO	104.868013 sec	: V4 OnStep detected, setting some defaults
DEBUG	104.868462 sec	: OnStep SyncParkStatus called
INFO	104.868489 sec	: Mount is unparked.
DEBUG	104.868519 sec	: InitPark Axis1 15.42 Axis2 58.89
INFO	104.868546 sec	: =============== Parkdata loaded
INFO	104.868953 sec	: Network based connection, detection timeouts set to 2 seconds
SCOPE	104.869383 sec	: CMD <:FA#>
SCOPE	104.873955 sec	: RES <1>
INFO	104.874010 sec	: Focuser 1 found
SCOPE	104.874103 sec	: CMD <:fA#>
SCOPE	104.878905 sec	: RES <0>
INFO	104.878953 sec	: Focuser 2 NOT found
INFO	104.878970 sec	: At least one focuser found, showing interface
DEBUG	104.879199 sec	: Focusers checked Variables:
DEBUG	104.879220 sec	: OSFocuser1: 1, OSFocuser2: 0, OSNumFocusers: 1
SCOPE	104.879237 sec	: CMD <:GX98#>
SCOPE	104.884208 sec	: RES <N>
INFO	104.884254 sec	: No Rotator found.
SCOPE	104.884736 sec	: CMD <:GXY0#>
SCOPE	104.890981 sec	: RES <11111110>
SCOPE	104.891030 sec	: CMD <:GXY1#>
SCOPE	104.897237 sec	: RES <FAN 0,1>
SCOPE	104.897285 sec	: CMD <:GXY2#>
SCOPE	104.905601 sec	: RES <FAN 1,2>
SCOPE	104.905659 sec	: CMD <:GXY3#>
SCOPE	104.911744 sec	: RES <FAN 2,2>
SCOPE	104.911800 sec	: CMD <:GXY4#>
SCOPE	104.918409 sec	: RES <Chauf 0,3>
SCOPE	104.918463 sec	: CMD <:GXY5#>
SCOPE	104.925035 sec	: RES <Chauf 1,3>
SCOPE	104.925088 sec	: CMD <:GXY6#>
SCOPE	104.931418 sec	: RES <Chauf 2,3>
SCOPE	104.931490 sec	: CMD <:GXY7#>
SCOPE	104.937999 sec	: RES <Chauf 3,3>
DEBUG	104.938538 sec	: OnStep SyncParkStatus called
INFO	104.938601 sec	: Mount is unparked.
DEBUG	104.938633 sec	: InitPark Axis1 15.42 Axis2 58.89
DEBUG	104.938667 sec	: Setting Default Park Axis1 to 0.00
DEBUG	104.938685 sec	: Setting Default Park Axis2 to 48.22
INFO	104.939747 sec	: Initialization Complete
DEBUG	104.939888 sec	: New JD is 2459987.95
SCOPE	104.939916 sec	: CMD <:SG-01:00#>
SCOPE	104.945055 sec	: CMD <:SG-01:00#> successful.
SCOPE	104.945107 sec	: CMD <:SL11:41:36#>
SCOPE	104.951118 sec	: CMD <:SL11:41:36#> successful.
SCOPE	104.951165 sec	: CMD <:SC02/12/23#>
SCOPE	104.957747 sec	: RES <1>
INFO	104.957817 sec	: Time updated, updating planetary data...
SCOPE	104.957894 sec	: CMD <:Sg352:21:9.00#>
SCOPE	104.964441 sec	: CMD <:Sg352:21:9.00#> successful.
SCOPE	104.964521 sec	: CMD <:St+48:13:29.00#>
SCOPE	104.970958 sec	: CMD <:St+48:13:29.00#> successful.
INFO	104.971034 sec	: Site location updated to Lat  48:13:29.00 - Long    7:38:51.00
DEBUG	104.971997 sec	: Configuration successfully saved for GEOGRAPHIC_COORD.
INFO	104.972070 sec	: Observer location updated: Latitude 48:13:29.0 (48.22) Longitude  7:38:51.0 (7.65)
SCOPE	105.796322 sec	: CMD <:GU#>
SCOPE	105.889915 sec	: RES <nNpHz/Eo260>
SCOPE	105.889997 sec	: CMD <:GR#>
SCOPE	105.895050 sec	: RES <14:41:06>
SCOPE	105.895156 sec	: VAL [14.685]
SCOPE	105.895171 sec	: CMD <:GD#>
SCOPE	105.900528 sec	: RES <+90*00:00>
SCOPE	105.900606 sec	: VAL [90]
INFO	105.900642 sec	: Telescope detected having PEC, setting that capability
DEBUG	105.900652 sec	: capabilities = 73f
SCOPE	105.901264 sec	: CMD <:GR#>
SCOPE	105.905815 sec	: RES <14:41:06>
SCOPE	105.905924 sec	: Equatorial coordinate format is high precision.
SCOPE	105.905976 sec	: <ACK>
SCOPE	105.906022 sec	: CMD <0X6>
SCOPE	105.908916 sec	: RES <P>
SCOPE	105.909056 sec	: <getSiteName>
SCOPE	105.909103 sec	: CMD <:GM#>
SCOPE	105.914376 sec	: RES <Schoenau>
DEBUG	105.914459 sec	: Site Name <Schoenau>
SCOPE	105.914499 sec	: <getTrackFreq>
SCOPE	105.914518 sec	: CMD <:GT#>
SCOPE	105.919655 sec	: RES <0.00000#>
SCOPE	105.919777 sec	: VAL [0]
SCOPE	105.919851 sec	: <getSiteLatitudeAlt>
SCOPE	105.919888 sec	: CMD <:GtH#>
SCOPE	105.926218 sec	: RES <+48*13:29.000>
SCOPE	105.926304 sec	: VAL [48,13,29.0]
SCOPE	105.926338 sec	: <getSiteLongitudeAlt>
SCOPE	105.926357 sec	: CMD <:GgH#>
SCOPE	105.933002 sec	: RES <-007*38:51.000>
SCOPE	105.933076 sec	: VAL in CartographicLongitude format [7,38,51.0]
INFO	105.933108 sec	: Mount has Latitude 48:13:29.0 (48.2247) Longitude 07:38:51.0 (7.6475) (Longitude sign in carthography format)
DEBUG	105.933905 sec	: Configuration successfully saved for GEOGRAPHIC_COORD.
1 year 2 months ago #90459

Please Log in or Create an account to join the conversation.

  • Posts: 452
  • Thank you received: 71

Replied by Alain Zwingelstein on topic Driver OnStep (LX200 like) for INDI

My configuration is:
OnStep 4.24m
kstars 3.6.4 Beta
2023-02-12T11:00:18: startup: indiserver -v
Usage: indiserver [options] driver [driver ...]
Purpose: server for local and remote INDI drivers
INDI Library: 2.0.1
Code v1.9.6-411-gb4f3497ce. Protocol 1.7.

and log file in ~/.indi/logs/2023-02-12/indi_lx200_OnStep/indi_lx200_OnStep_10\:39\:52.log

I will make some tests with Python scripts and let you know
1 year 2 months ago #90460

Please Log in or Create an account to join the conversation.

Time to create page: 0.815 seconds