×

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

Bi-monthly release with minor bug fixes and improvements

Read More...

SaySafari Problem "Internal Client Not Connected" Error

  • Posts: 60
  • Thank you received: 7

SaySafari Problem "Internal Client Not Connected" Error was created by Ian

Having a problem getting the SkySafari middleware to work when my IndiServer is connected to a real mount. Everything works well when running simulators (local IndiServer and Remote server on RPi). But when I run to real connected hardware I keep getting "Internal client is not connected! Restart driver and try again."

I've changed the "Active Devices" telescope from the default (to EQMod Mount and even tried iEQ45 Pro (the mount I have connected), saving config and restarting everything between tries but I always get this message.

Kstars will slew the mount fine so I know the RPi/Indi Server is talking to the mount ok

Config: Kstars/Ekos on Mac, InidServer on RPi3 under UbuntuMate, SkySafari on Mac & iPhone (same from both)

Full log (with all debugging enabled)
2017-07-10T14:34:45: Internal client is not connected! Restart driver and try again. 
2017-07-10T14:34:45: CMD <> 
2017-07-10T14:34:45: Internal client is not connected! Restart driver and try again. 
2017-07-10T14:34:45: CMD <GD> 
2017-07-10T14:34:45: Internal client is not connected! Restart driver and try again. 
2017-07-10T14:34:45: CMD <RS> 
2017-07-10T14:34:42: Internal client is not connected! Restart driver and try again. 
2017-07-10T14:34:42: CMD <> 
2017-07-10T14:34:42: Internal client is not connected! Restart driver and try again. 
2017-07-10T14:34:42: CMD <GR> 
2017-07-10T14:34:42: Connected to SkySafari. 
2017-07-10T14:34:38: Toggle Logging Level -- Driver Debug 
2017-07-10T14:34:34: Toggle Debug Level -- Driver Debug 
2017-07-10T14:34:28: Debug is enabled. 
2017-07-10T14:34:24: Device configuration applied. 
2017-07-10T14:34:24: Loading device configuration... 
2017-07-10T14:34:24: SkySafari Server is running. Connect the App now to this machine using SkySafari LX200 driver

I'm sure it's my finger trouble. Had a look through the source code and can see it the error and see it means it's not connected but don't understand enough about the design to get much further.

Many thanks
6 years 9 months ago #17764
Attachments:

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

Replied by Jasem Mutlaq on topic SaySafari Problem "Internal Client Not Connected" Error

Put iEQ45 Pro in active devices, save config, disconnect, and then reconnect.
6 years 9 months ago #17768

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

  • Posts: 60
  • Thank you received: 7

Replied by Ian on topic SaySafari Problem "Internal Client Not Connected" Error

I did try iEQ45 Pro when "fishing around" trying everything (as well as just iEQ). I'll try again (wont be until tomorrow).
Fired it all up earlier (to look into other issue) and results posted below
Last edit: 6 years 9 months ago by Ian. Reason: Updated
6 years 9 months ago #17770

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

  • Posts: 60
  • Thank you received: 7

Replied by Ian on topic SaySafari Problem "Internal Client Not Connected" Error

Tried with iEQ45 Pro and not quite the same but still does not seem to work. With iEQ45 IndiServer reports
2017-07-10T16:22:22: Connected to SkySafari. 
2017-07-10T16:21:56: Device configuration applied. 
2017-07-10T16:21:56: Loading device configuration... 
2017-07-10T16:21:56: SkySafari Server is running. Connect the App now to this machine using SkySafari LX200 driver.
And then after a short time SkySafari reports
6 years 9 months ago #17771
Attachments:

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

  • Posts: 60
  • Thank you received: 7

Replied by Ian on topic SaySafari Problem "Internal Client Not Connected" Error

Sorted. Unsure of underlying cause and investigated at same time as another issue so cause/resolution uncertain. Possibly related to SkySafari Active Devices>Telescope setting - so if others have the sae issue make sure the SkySafari Active Devices>Telescope is set to match the telescope driver in use (and restart the driver if you need to change it).
6 years 9 months ago #17877

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

Time to create page: 0.776 seconds