×
INDI Library v1.8.6 Released (21 Aug 2020)

August 2020 release of INDI Library v1.8.6 introduces new drivers while providing fixes and improvements to existing devices and core framework.

What is the point of Device manager in Kstars

9 months 2 weeks ago
rlancaste
Supernova Explorer
Supernova Explorer
Posts: 2269
Karma: 22
More
What is the point of Device manager in Kstars #46529
indidrivers.xml is certainly not obsolete. It is a very important file. This file is how KStars can list drivers for remote INDI Servers in the INDI profile and connect to them, even though your current computer doesn't have those drivers installed. If KStars does not have that file, then the drivers listed under "remote" would only include the drivers which are actually installed on the computer you are currently using. For an example, let's say you have a raspberry Pi and it has an SBIG driver on it. You are accessing it from your laptop that doesn't have 3rd party drivers installed. So that means that it can't see the xml file for SBIG since it isn't on the computer. So when you select "Remote" in the INDI profile, you can't select an SBIG camera in the profile to start it up, since it isn't in the list.

There are some drivers that can't be installed on some systems and not on others because the don't compile or work on that system. This file makes it possible to use those drivers remotely.

The file should not prevent other XML files from being loaded, so if you have custom drivers or 3rd party drivers that aren't from the 3rd party Repo. But it should make it possible to load drivers that aren't on your system so you can run them remotely.
The following user(s) said Thank You Kaczorek, pug916

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

9 months 2 weeks ago
Ihoujin
Platinum Boarder
Platinum Boarder
Posts: 913
Karma: 3
More
What is the point of Device manager in Kstars #46569
Thank you Rob. I found that information worth investigating for myself. As I have not done much with the remote features to date. Now, I found I can indeed connect to a remote profile running drivers that are not installed locally. However the local server has a bad habit of overwriting the remote profile's driver list if it is started locally, and not from within the remote web manager that is fully aware of the available remote drivers.
In other words, I find I must have the INDI server start via the Web Manager and connect to the already running server from the local machine, otherwise only locally available drivers are started, and the profile itself is overwritten without the remote drivers.

Is this typical behaviour? This doesn't seem to be optimized to me. I shouldn't have to redo the profile whenever I accidentally attempt to connect to a remote server with more available drivers that was not already started in advance.

INDI/KStars on Raspberry Pi 4, 4gb
Raspbian Buster with AstroPi3 script configuration
Skywatcher HEQ5 Pro Mount
Canon 600D Camera
Orion SSAG/ASI120mm @280mm Guide Scope
PHD2
Adafruit Motor Hat shield
Adafruit GPS Module
Generic Bluetooth Joystick.
Startech 7 port powered USB Hub.

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

9 months 2 weeks ago
rlancaste
Supernova Explorer
Supernova Explorer
Posts: 2269
Karma: 22
More
What is the point of Device manager in Kstars #46575
Ok, there is probably room for improvement. This was Jasem's solution to the problem 2 years ago when I told him about the issue with remote drivers not showing up because they had no xml file on the local system. There may be better ways to fix it or it could probably be improved upon. I can let him know there is an issue with overwriting drivers.

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

9 months 2 weeks ago
Ihoujin
Platinum Boarder
Platinum Boarder
Posts: 913
Karma: 3
More
What is the point of Device manager in Kstars #46577
Sounds good. Perhaps when a remote profile is selected in EKOS, the start button should command the server to start, rather than start the local version of the profile.
Which is another oddity IMHO, why is it necessary to populate drivers locally for a remotely configured profile at all? I found I can leave everything blank, other than the 'mandatory' CCD driver. The remote server just ignores it and connect the remote drivers that are started in advance. Surely a matching a profile name is sufficient to select what profile to start on the web manager server.
Local EKOS with it's limited driver list could probably do away with any local configuration power over the web manager's profiles. There by only supporting configuring from within the web manager with all available drivers and eliminate any confusion.

INDI/KStars on Raspberry Pi 4, 4gb
Raspbian Buster with AstroPi3 script configuration
Skywatcher HEQ5 Pro Mount
Canon 600D Camera
Orion SSAG/ASI120mm @280mm Guide Scope
PHD2
Adafruit Motor Hat shield
Adafruit GPS Module
Generic Bluetooth Joystick.
Startech 7 port powered USB Hub.

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

9 months 2 weeks ago
rlancaste
Supernova Explorer
Supernova Explorer
Posts: 2269
Karma: 22
More
What is the point of Device manager in Kstars #46583
So you are correct if you are connecting to an already running INDI server on the remote device. If you connect to that running INDI Server, KStars will get the information about the running drivers not whatever ones you select in the profile on the local machine.

But, if you connect using Ekos and tell it to use the INDI Web Manager, you can configure everything from within Ekos. You can set up your profile exactly the way you want to on your local machine, and then when you tell it to start, the Web Manager on the remote machine will update your profile on that remote machine to reflect the profile you selected. If the profile doesn't exist on the remote machine, it will be created. Then the selected and updated profile on the remote machine will be used to start the INDI server.

So it is very important actually. And it is a much simpler way to work with the web Manager.

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

9 months 2 weeks ago
Ihoujin
Platinum Boarder
Platinum Boarder
Posts: 913
Karma: 3
More
What is the point of Device manager in Kstars #46584
Ok. But the problem is not all the drivers are necessarily available on the local system when creating a remote profile.
For the record I was experimenting with KStars on Windows.

INDI/KStars on Raspberry Pi 4, 4gb
Raspbian Buster with AstroPi3 script configuration
Skywatcher HEQ5 Pro Mount
Canon 600D Camera
Orion SSAG/ASI120mm @280mm Guide Scope
PHD2
Adafruit Motor Hat shield
Adafruit GPS Module
Generic Bluetooth Joystick.
Startech 7 port powered USB Hub.

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

9 months 1 week ago
knro
Administrator
Administrator
Posts: 8370
Karma: 51
What is the point of Device manager in Kstars #46654
Currently KStars does not load profiles from a remote Web Manager server. Implementing this shouldn't be too difficult, but it just needs time.

Right now, if you create a remote profile and no local version is available, this is where the drivers in indidrivers.xml are used. This was proposed by Robert a couple of years ago and appears to be working well for most people. If it is not there, you can simply put the device label as well.

Device manager is no longer used, but is kept for testing purposes for when you need to connect to INDI without Ekos.

Jasem Mutlaq
Support INDI & Ekos; Get StellarMate Astrophotography Gadget.
How to Submit Logs when you have problems?
Add your observatory info

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

9 months 1 week ago
Ihoujin
Platinum Boarder
Platinum Boarder
Posts: 913
Karma: 3
More
What is the point of Device manager in Kstars #46844
I just tried out a couple things and have found a reasonable work around for creating a profile with a non-local INDI driver that does not require the remote server to be run in advance.
It turns out manually filling in the name of the driver will do the trick, even if the local machine is not able to list it.

Incidentally I also attempted to describe a remote driver with driver1@remotehost:port first, but it was not effective.

INDI/KStars on Raspberry Pi 4, 4gb
Raspbian Buster with AstroPi3 script configuration
Skywatcher HEQ5 Pro Mount
Canon 600D Camera
Orion SSAG/ASI120mm @280mm Guide Scope
PHD2
Adafruit Motor Hat shield
Adafruit GPS Module
Generic Bluetooth Joystick.
Startech 7 port powered USB Hub.

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

9 months 1 week ago
knro
Administrator
Administrator
Posts: 8370
Karma: 51
What is the point of Device manager in Kstars #46852
Was driver1@remotehost:port running already?

Jasem Mutlaq
Support INDI & Ekos; Get StellarMate Astrophotography Gadget.
How to Submit Logs when you have problems?
Add your observatory info

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

9 months 1 week ago 8 months 3 weeks ago by escriban. Reason: New insights
escriban
Senior Boarder
Senior Boarder
Posts: 54
Karma: 1
More
What is the point of Device manager in Kstars #46878
Hi Jasem

This is an interesting discussion and gives some insights into the coding of KStars and INDI.

BUT: I still don't understand, why the device manager keeps listing a wrong version number! (KStars and INDIlib on localhost!)
I tried to debug KStars and could trace down the calls in "drivermanager.cpp".

The "debug-version" of KStars (Debugging in QT Creator) reads the correct version from "indidrivers.xml". But the very same binary (produced by QT Creator debugger) started by hand does always return the driver version I got debugging in QT Creator, in spite of a handmade change in "indidrivers.xml". This change will be reflected, ONLY if I start a new debugger in QT Creator. From this time on - starting kstars directly from command line - brings always the version number read before in QT Creator.

New information (25.12.19) for Jasem and Kaczorek:

I found a notice from Kaczorek ( www.indilib.org/forum/ekos/2137-device-n...le-editor.html#16059 ), that states exactly what i'm referring to! The contribution dates two years ago and apparently nothing has changed!
This strange behaviour is not crucial, but bothersome. Especially when you want to check against a correct driver version. Unfortunately Kaczorek didn't follow the case, so we are none the wiser. There is definitively some caching of "indidrivers.xml", but by now I cannot spot where. I hope, we can track down it!

Sincerely
Antonio

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

9 months 6 days ago
Ihoujin
Platinum Boarder
Platinum Boarder
Posts: 913
Karma: 3
More
What is the point of Device manager in Kstars #46890
Driver1@remotehost:port was not running
I told it to run with attention to spaces and case sensitivity:
Adafruit Motor HAT@HostIP:hostport
On the remote host, where that custom driver resides, the web manager app stated the server and listed it by the given name as running along with the other standard drivers. But the local host did not bring it up in the indi control panel.

Now I recognize this is already well off topic, I think I should I create a new thread.

INDI/KStars on Raspberry Pi 4, 4gb
Raspbian Buster with AstroPi3 script configuration
Skywatcher HEQ5 Pro Mount
Canon 600D Camera
Orion SSAG/ASI120mm @280mm Guide Scope
PHD2
Adafruit Motor Hat shield
Adafruit GPS Module
Generic Bluetooth Joystick.
Startech 7 port powered USB Hub.

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

8 months 3 weeks ago
escriban
Senior Boarder
Senior Boarder
Posts: 54
Karma: 1
More
What is the point of Device manager in Kstars #47273
Hi all

Perhaps there are other persons interested in this case of the "Device manager". I was able to trace down the strange behaviour of this manager when listing the version numbers!
See here: www.indilib.org/forum/ekos/2137-device-n...le-editor.html#47272

Greetings
Antonio

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

Time to create page: 0.598 seconds