hi Richard,
glad that SM PRO will solve your problem. Anyway, the resources for INDI development are on this web site under the link 'develop'.
I would recommend to start with Rick's tutorial:
github.com/rickbassham/indi-dev-tutorials
And to contribute to the development community:
indilib.org/developers/add-your-driver.html

But as Jarno already made a draft driver, you could simply 'download' it and compile it, to do that just read the 'Building' paragraph here:
github.com/indilib/indi
Remember to switch from:
git clone github.com/indilib/indi.git
to:
git clone github.com/jpaana/indi.git
as you're cloning Jarno's repo, not the main one.

Ferrante

Read More...

hi Richard,
the command set seems to be quite easy to implement in a INDI driver.
Do you have any programming experience?
Following some good tutorials and with the support from this community, you could give it a try

Ferrante

Read More...

From what I understand the libartesky deals with the communication to and from the flat box device while the driver manages the communication to and from the client applications like kstars/ekos.
So you need the command set to write a custom Indi driver and the compiled (under Linux) libartesky library.
The latter could be also provided as source code and compiled later.

btw I just called Artesky and they told me that an indi version is under way. No idea of the timing though .
Ferrante

Read More...

It seems that all you need is libartesky to compile under Linux.
And from the readme file in the libartesky repo a 1.1 version is supporting Linux; but it's not released yet neither as source code nor as compiled :
github.com/Artesky/artesky-projects-devel

Read More...

Hi Ginge,
Writing a driver for a flat box is quite easy provided that you have the command set for the device.
Does artesky give this kind of information?

Ferrante

Read More...

Ferrante Enriques replied to the topic 'Indi-dome-scripting' in the forum. 5 months ago

good to know that (almost) everything works!

Cheers
Ferrante

Read More...

Ferrante Enriques replied to the topic 'Indi-dome-scripting' in the forum. 5 months ago

hi Gunter,
I guess that in the meantime you figured it out.
Anyway, yes running servers of different ports should do the job.

To start the server you just need the indiserver command, something like:
indiserver -p 7634 -v <add list of drivers and chain them>
systemctl is then needed to start them at boot.

Read More...

Ferrante Enriques replied to the topic 'Indi-dome-scripting' in the forum. 6 months ago

hi Gunter,

did you compile and install the drivers on the local machine (RPI4) too?
I never tried driver forwarding but the list of drivers is build locally.

ferrante

Read More...