×

INDI Library v2.0.6 is Released (02 Feb 2024)

Bi-monthly release with minor bug fixes and improvements

Indiwebmanager - Chain servers

  • Posts: 167
  • Thank you received: 54
Hi

what is the proper way to use "custom drivers" box with indiwebmanager ?
I thought i could add other driver on other server, but i can't find how...

Gilles.
5 years 11 months ago #24898

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

driver_name@ip_address is the format
The following user(s) said Thank You: gehelem
5 years 11 months ago #24900

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

  • Posts: 167
  • Thank you received: 54
Yes
I've tried this format, but when i click on start nothing happens (other drivers start, but not the custom one)
5 years 11 months ago #24902

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

It doesn't start them, they need to be started already. It just chains them to the primary server.
5 years 11 months ago #24903

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

  • Posts: 167
  • Thank you received: 54
Well i think i've problems with spaces :
When i add MoonLite@192.168.2.102 it's OK
But ZWO ASI 120MM@192.168.2.102 is KO
"ZWO ASI 120MM"@192.168.2.102 is KO

EDIT :
Same result with 'ZWO CCD ASI120MM'@192.168.2.101 => KO
On command line it's OK :
indiserver -vv -m 100 indi_asi_ccd 'ZWO CCD ASI120MM'@192.168.2.101
Last edit: 5 years 11 months ago by gehelem.
5 years 11 months ago #24907

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

  • Posts: 167
  • Thank you received: 54
It seems to be related to my Tinkerboard config.
I've tried with another setup and it works...
Need to investigate.
5 years 11 months ago #24926

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

  • Posts: 167
  • Thank you received: 54
i went further

Two remote servers : "armodroid" and "armnafabox"
asi120mm connected to armodroid and asi78mm connected to armnafabox.
indiwebmanager is running on both.

First test : armodroid as master armnafabox as slave
Slave = ASI driver started on armnafabox via indiwebmanager
Master = ASI driver started on armodroid plus custom driver on indiwebmanager
"ZWO CCD ASI178MM"@armnafabox

ssh to armodroid, and
sudo systemctl status indiwebmanager.service
This is what i get :
(...)
avril 09 23:01:35 odroid python[4836]: indiserver -p 7624 -m 100 -v -f /tmp/indiFIFO > /dev/null 2>&1 &
avril 09 23:01:35 odroid python[4836]: Driver binary is indi_asi_ccd
avril 09 23:01:35 odroid python[4836]: echo "start indi_asi_ccd -n \"ZWO CCD\""  > /tmp/indiFIFO
avril 09 23:01:35 odroid python[4836]: Driver binary is "ZWO CCD ASI178MM"@armnafabox
avril 09 23:01:35 odroid python[4836]: echo "start \"ZWO CCD ASI178MM\"@armnafabox" > /tmp/indiFIFO
avril 09 23:01:35 odroid python[4836]: 192.168.2.100 - - [09/Apr/2018 23:01:35] "POST /api/server/start/zwo HTTP/1.1" 200 0
avril 09 23:01:35 odroid python[4836]: 192.168.2.100 - - [09/Apr/2018 23:01:35] "GET /api/server/status HTTP/1.1" 200 20
avril 09 23:01:36 odroid python[4836]: 192.168.2.100 - - [09/Apr/2018 23:01:36] "GET /api/server/drivers HTTP/1.1" 20
(...)

=> i can connect and use both ASI cameras

Second test : armnafabox as master armodroid as slave
Slave = ASI driver started on armodroid via indiwebmanager
Master = ASI driver (+Moonlite + EqMod) started on armnafabox plus custom driver on indiwebmanager
"ZWO CCD ASI120MM"@armodroid

ssh to armafabox, and
sudo systemctl status indiwebmanager.service
This is what i get :
(...)
avril 09 23:03:26 tinkerboard indi-web[706]: INFO: indiserver -p 7624 -m 100 -v -f /tmp/indiFIFO > /dev/null 2>&1 &
avril 09 23:03:26 tinkerboard indi-web[706]: INFO: echo "start indi_asi_ccd -c \"/home/nafa/.indi/ZWO CCD_config.xml\" -n \"ZWO CCD\"" > /tmp/indiFIFO
avril 09 23:03:26 tinkerboard indi-web[706]: INFO: echo "start indi_moonlite_focus -c \"/home/nafa/.indi/MoonLite_config.xml\" -n \"MoonLite\"" > /tmp/indiFIFO
avril 09 23:03:26 tinkerboard indi-web[706]: INFO: echo "start indi_eqmod_telescope -c \"/home/nafa/.indi/EQMod Mount_config.xml\" -n \"EQMod Mount\"" > /tmp/indiFIFO
avril 09 23:03:26 tinkerboard indi-web[706]: INFO: echo "start \"ZWO CCD ASI120MM\"@armodroid -c \"/home/nafa/.indi/\"ZWO CCD ASI120MM\"@armodroid_config.xml\"" > /tmp/indiFIFO
avril 09 23:03:26 tinkerboard indi-web[706]: 192.168.2.100 - - [09/Apr/2018 23:03:26] "POST /api/server/start/test HTTP/1.1" 200 0
avril 09 23:03:26 tinkerboard indi-web[706]: 192.168.2.100 - - [09/Apr/2018 23:03:26] "GET /api/server/status HTTP/1.1" 200 21
(...)

==> server is not starting for real, i can't connect to it

Outputs of logs are very different, it looks like the second one is passing xml configuration file

Any ideas ?

Gilles.
5 years 11 months ago #24936

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

  • Posts: 167
  • Thank you received: 54
Can someone try to chain servers with latest version of webmanager ?
Bug seen with fresh vm install
5 years 11 months ago #24960

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

  • Posts: 167
  • Thank you received: 54
Well
I think i know where is the problem.
Older versions of indiwebmanager didn't pass xml config file to fifo when starting a driver :
avril 09 23:01:35 odroid python[4836]: echo "start indi_asi_ccd -n \"ZWO CCD\""  > /tmp/indiFIFO
But recent version do :
avril 09 23:03:26 tinkerboard indi-web[706]: INFO: echo "start indi_asi_ccd -c \"/home/nafa/.indi/ZWO CCD_config.xml\" -n \"ZWO CCD\"" > /tmp/indiFIFO
So, i've tried classical way to use this -c switch :
indiserver -vvv - m 100 indi_simulator_ccd -c /pathtoxmlfile
That's ok
But if "pathtoxmlfile" contains @ character, indiserver fails :
gilles@htpc:~/.indi$ indiserver -vvv -m 100 MoonLite@portabana -c "/home/gilles/.indi/MoonLite@portabana_config.xml"
2018-04-12T08:54:38: startup: indiserver -vvv -m 100 MoonLite@portabana -c /home/gilles/.indi/MoonLite@portabana_config.xml 
2018-04-12T08:54:38: Driver MoonLite@portabana: socket=3
2018-04-12T08:54:38: Driver -c: pid=2258 rfd=4 wfd=7 efd=8
Child process 2258 died
gethostbyname(portabana_config.xml): Success
2018-04-12T08:54:38: good bye
gilles@htpc:~/.indi$ 
(and that's also what's happening with FIFO command used in indiwebmanager)
I've tried again to play with escape character with no success.

One question : what is the purpose to give this xml file to a distant driver ?
it's already got his own on distant machine, no ?
5 years 11 months ago #25008

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

Good catch, there is no need to pass XML for remote drivers. Please open issue on the web manager Github page so I can track this.
The following user(s) said Thank You: gehelem
5 years 11 months ago #25009

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

  • Posts: 167
  • Thank you received: 54
Is this the good place to do it ? :
github.com/knro/indiwebmanager/issues/18
5 years 11 months ago #25010

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

Time to create page: 0.197 seconds