×

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

Bi-monthly release with minor bug fixes and improvements

INDI Web Manager

  • Posts: 29
  • Thank you received: 2

Replied by Clément on topic INDI Web Manager

Yes it works, on both my Nikon D90 and D5300 :)
7 years 10 months ago #8471

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

Replied by Jasem Mutlaq on topic INDI Web Manager

INDI Web Manager updated with new feature: Auto Start.

You can select a profile as "Auto Start" and whenever you start the service or reboot the device (And systemd unit service was installed) then it will startup the INDI server for that profile.
7 years 10 months ago #8499

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

  • Posts: 69
  • Thank you received: 12

Replied by anat on topic INDI Web Manager

indiwebmanager cannot start indi_mi_ccd_usb. Please see the log,
10.0.0.4 - - [31/May/2016 23:46:04] "POST /api/profiles/Simulators/ HTTP/1.1" 200 0
{u'label': u'Imager Agent'}
{u'label': u'MI CCD (USB)'}
10.0.0.4 - - [31/May/2016 23:46:09] "POST /api/profiles/Simulators/ HTTP/1.1" 200 0
indiserver -p 7624 -m 100 -v -f /tmp/indiFIFO > /dev/null 2>&1 &
Driver binary is indi_imager_agent
echo "start indi_imager_agent -n "Imager Agent""  > /tmp/indiFIFO
Driver binary is indi_mi_ccd_usb
echo "start indi_mi_ccd_usb -n "MI CCD (USB)""  > /tmp/indiFIFO
/bin/sh: 1: Syntax error: "(" unexpected
10.0.0.4 - - [31/May/2016 23:46:16] "POST /api/server/start/Simulators HTTP/1.1" 200 0
10.0.0.4 - - [31/May/2016 23:46:16] "GET /api/server/status HTTP/1.1" 200 20
10.0.0.4 - - [31/May/2016 23:46:16] "GET /api/server/drivers HTTP/1.1" 200 33
7 years 9 months ago #8579

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

Replied by Jasem Mutlaq on topic INDI Web Manager

Please git pull and test again
7 years 9 months ago #8581

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

  • Posts: 69
  • Thank you received: 12

Replied by anat on topic INDI Web Manager

It works now. Thanks.
7 years 9 months ago #8583

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

  • Posts: 29
  • Thank you received: 2

Replied by Clément on topic INDI Web Manager

Hi,

Here is a followup about my issues with Nikon+GPhoto+Web manager. The web manager is a version checked out less than a week ago.
In my Raspberry Pi 3 + Raspbian Jessie, with the latest INDI package, + libgphoto2.5.4. When I start the GPhoto driver from the web manager, the driver is very limited, and I don't have any liveview. Whereas while starting INDI in command line, the liveview works with my Nikon cameras. See the screenshots I have posted in a previous message.
Sorry if it is posted in the wrong topic, but my GPhoto issues are related to the web manager, so I think it is relevant.

Here are some logs:
  • Starting INDI from the web manager:
2016-06-03T06:57:37: startup: indiserver -p 7624 -v -f /tmp/indiFIFO
2016-06-03T06:57:37: listening to port 7624 on fd 4
FIFO: start indi_gphoto_ccd -n Nikon DSLR
FIFO: Starting driver indi_gphoto_ccd
2016-06-03T06:57:37: Driver indi_gphoto_ccd: pid=4974 rfd=6 wfd=10 efd=11
2016-06-03T06:57:37: Driver indi_gphoto_ccd: snooping on Telescope Simulator.EQUATORIAL_EOD_COORD
2016-06-03T06:57:37: Driver indi_gphoto_ccd: snooping on Telescope Simulator.TELESCOPE_INFO
2016-06-03T06:57:37: Driver indi_gphoto_ccd: snooping on CCD Simulator.FILTER_SLOT
2016-06-03T06:57:37: Driver indi_gphoto_ccd: snooping on CCD Simulator.FILTER_NAME
2016-06-03T06:58:01: Client 7: new arrival from 192.168.2.42:49645 - welcome!
2016-06-03T06:58:08: Driver indi_gphoto_ccd: stderr EOF
2016-06-03T06:58:08: Driver indi_gphoto_ccd: restart #1
2016-06-03T06:58:08: Driver indi_gphoto_ccd: pid=5140 rfd=6 wfd=11 efd=12
2016-06-03T06:58:08: Driver indi_gphoto_ccd: snooping on Telescope Simulator.EQUATORIAL_EOD_COORD
2016-06-03T06:58:08: Driver indi_gphoto_ccd: snooping on Telescope Simulator.TELESCOPE_INFO
2016-06-03T06:58:08: Driver indi_gphoto_ccd: snooping on CCD Simulator.FILTER_SLOT
2016-06-03T06:58:08: Driver indi_gphoto_ccd: snooping on CCD Simulator.FILTER_NAME

And it is the same when in the drop-down list I select "GPhoto CCD" instead of "Nikon DSLR".
I noticed that as soon as I connect to the GPhoto device in Ekos, there is a "stderr EOF" and the driver restarts. Which does not happen when starting from the command line:

  • From the command line:
  • 2016-06-03T06:59:03: startup: indiserver -v indi_gphoto_ccd
    2016-06-03T06:59:03: Driver indi_gphoto_ccd: pid=5403 rfd=3 wfd=6 efd=7
    2016-06-03T06:59:03: listening to port 7624 on fd 4
    2016-06-03T06:59:03: Driver indi_gphoto_ccd: snooping on Telescope Simulator.EQUATORIAL_EOD_COORD
    2016-06-03T06:59:03: Driver indi_gphoto_ccd: snooping on Telescope Simulator.TELESCOPE_INFO
    2016-06-03T06:59:03: Driver indi_gphoto_ccd: snooping on CCD Simulator.FILTER_SLOT
    2016-06-03T06:59:03: Driver indi_gphoto_ccd: snooping on CCD Simulator.FILTER_NAME
    2016-06-03T06:59:15: Client 0: new arrival from 192.168.2.42:49648 - welcome!


    In both cases, the GPhoto tab in Ekos shows the version "GPHoto v1.5, interface 10."

    I also noticed that when started from the command line, the GPhoto driver manages the configuration files correctly. When I connect to the device in Ekos, I see this log in Ekos:
    2016-06-03T06:59:18: Device configuration applied. 
    2016-06-03T06:59:18: Loading device configuration... 
    2016-06-03T06:59:18: Please update the camera pixel size in the Image Info section. The camera resolution will be updated after the first exposure is complete. 
    2016-06-03T06:59:18: GPhoto CCD is online.

    And I can save, load, or load the default XML config file for the driver.
    However, when started from the web manager, the config files seem not to be found. For example when I try to load the default config file:
    2016-06-03T07:31:25: Error loading default configuraiton. Unable to read user config file. Error loading file (null)/.indi/GPhoto CCD_config.xml.default: No such file or directory
    There is an issue with the path here, right?

    How come there is such a difference of version between both cases? Are there 2 different version of the GPhoto driver somewhere on my machine, and the web manager loads a different one from the command line?

    PS: Here is a log with double verbose option, when starting INDI from the web manager:
    2016-06-03T07:30:41: startup: indiserver -p 7624 -vv -f /tmp/indiFIFO
    2016-06-03T07:30:41: listening to port 7624 on fd 4
    FIFO: start indi_gphoto_ccd -n GPhoto CCD
    FIFO: Starting driver indi_gphoto_ccd
    2016-06-03T07:30:41: Driver indi_gphoto_ccd: pid=14626 rfd=6 wfd=10 efd=11
    2016-06-03T07:30:41: Driver indi_gphoto_ccd: sending <getProperties version='1.7'/>
     
    2016-06-03T07:30:41: Driver indi_gphoto_ccd: read <getProperties device='Telescope Simulator' name='EQUATORIAL_EOD_COORD'>
    2016-06-03T07:30:41: Driver indi_gphoto_ccd: snooping on Telescope Simulator.EQUATORIAL_EOD_COORD
    2016-06-03T07:30:41: Driver indi_gphoto_ccd: read <getProperties device='Telescope Simulator' name='TELESCOPE_INFO'>
    2016-06-03T07:30:41: Driver indi_gphoto_ccd: snooping on Telescope Simulator.TELESCOPE_INFO
    2016-06-03T07:30:41: Driver indi_gphoto_ccd: read <getProperties device='CCD Simulator' name='FILTER_SLOT'>
    2016-06-03T07:30:41: Driver indi_gphoto_ccd: snooping on CCD Simulator.FILTER_SLOT
    2016-06-03T07:30:41: Driver indi_gphoto_ccd: read <getProperties device='CCD Simulator' name='FILTER_NAME'>
    2016-06-03T07:30:41: Driver indi_gphoto_ccd: snooping on CCD Simulator.FILTER_NAME
    2016-06-03T07:30:41: Driver indi_gphoto_ccd: read <defSwitchVector device='GPhoto CCD' name='CONNECTION'>
    2016-06-03T07:30:41: Driver indi_gphoto_ccd: read <defTextVector device='GPhoto CCD' name='DRIVER_INFO'>
    2016-06-03T07:30:41: Driver indi_gphoto_ccd: read <defSwitchVector device='GPhoto CCD' name='CONFIG_PROCESS'>
    2016-06-03T07:30:41: Driver indi_gphoto_ccd: read <defTextVector device='GPhoto CCD' name='ACTIVE_DEVICES'>
    2016-06-03T07:30:41: Driver indi_gphoto_ccd: read <defTextVector device='GPhoto CCD' name='DEVICE_PORT'>
    2016-06-03T07:30:43: Client 7: new arrival from 192.168.2.42:49814 - welcome!
    2016-06-03T07:30:43: Client 7: read <getProperties device='' name=''>
    2016-06-03T07:30:43: Driver indi_gphoto_ccd: queuing responsible for <getProperties device='' name=''>
    2016-06-03T07:30:43: Driver indi_gphoto_ccd: sending <getProperties version="1.7"/>
     
    2016-06-03T07:30:43: Driver indi_gphoto_ccd: read <defSwitchVector device='GPhoto CCD' name='CONNECTION'>
    2016-06-03T07:30:43: Client 7: queuing <defSwitchVector device='GPhoto CCD' name='CONNECTION'>
    2016-06-03T07:30:43: Client 7: sending <defSwitchVector device="GPhoto CCD" name="CONNECT
    2016-06-03T07:30:43: Driver indi_gphoto_ccd: read <defTextVector device='GPhoto CCD' name='DRIVER_INFO'>
    2016-06-03T07:30:43: Client 7: queuing <defTextVector device='GPhoto CCD' name='DRIVER_INFO'>
    2016-06-03T07:30:43: Client 7: sending <defTextVector device="GPhoto CCD" name="DRIVER_IN
    2016-06-03T07:30:43: Driver indi_gphoto_ccd: read <defSwitchVector device='GPhoto CCD' name='CONFIG_PROCESS'>
    2016-06-03T07:30:43: Client 7: queuing <defSwitchVector device='GPhoto CCD' name='CONFIG_PROCESS'>
    2016-06-03T07:30:43: Client 7: sending <defSwitchVector device="GPhoto CCD" name="CONFIG_
    2016-06-03T07:30:43: Driver indi_gphoto_ccd: read <defTextVector device='GPhoto CCD' name='ACTIVE_DEVICES'>
    2016-06-03T07:30:43: Client 7: queuing <defTextVector device='GPhoto CCD' name='ACTIVE_DEVICES'>
    2016-06-03T07:30:43: Client 7: sending <defTextVector device="GPhoto CCD" name="ACTIVE_DE
    2016-06-03T07:30:43: Driver indi_gphoto_ccd: read <defTextVector device='GPhoto CCD' name='DEVICE_PORT'>
    2016-06-03T07:30:43: Client 7: queuing <defTextVector device='GPhoto CCD' name='DEVICE_PORT'>
    2016-06-03T07:30:43: Client 7: sending <defTextVector device="GPhoto CCD" name="DEVICE_PO
    2016-06-03T07:30:43: Driver indi_gphoto_ccd: read <defSwitchVector device='GPhoto CCD' name='DEBUG'>
    2016-06-03T07:30:43: Client 7: queuing <defSwitchVector device='GPhoto CCD' name='DEBUG'>
    2016-06-03T07:30:43: Client 7: sending <defSwitchVector device="GPhoto CCD" name="DEBUG"
    2016-06-03T07:30:43: Client 7: read <enableBLOB device='GPhoto CCD' name=''>
    2016-06-03T07:30:43: Driver indi_gphoto_ccd: queuing responsible for <enableBLOB device='GPhoto CCD' name=''>
    2016-06-03T07:30:43: Driver indi_gphoto_ccd: sending <enableBLOB device="GPhoto CCD">
    Also
    </enableBLOB
    2016-06-03T07:30:43: Driver indi_gphoto_ccd: read <defSwitchVector device='GPhoto CCD' name='SIMULATION'>
    2016-06-03T07:30:43: Client 7: queuing <defSwitchVector device='GPhoto CCD' name='SIMULATION'>
    2016-06-03T07:30:43: Client 7: sending <defSwitchVector device="GPhoto CCD" name="SIMULAT
    2016-06-03T07:30:43: Driver indi_gphoto_ccd: read <defTextVector device='GPhoto CCD' name='ACTIVE_DEVICES'>
    2016-06-03T07:30:43: Client 7: queuing <defTextVector device='GPhoto CCD' name='ACTIVE_DEVICES'>
    2016-06-03T07:30:43: Client 7: sending <defTextVector device="GPhoto CCD" name="ACTIVE_DE
    2016-06-03T07:30:43: Driver indi_gphoto_ccd: read <defTextVector device='GPhoto CCD' name='DEVICE_PORT'>
    2016-06-03T07:30:43: Client 7: queuing <defTextVector device='GPhoto CCD' name='DEVICE_PORT'>
    2016-06-03T07:30:43: Client 7: sending <defTextVector device="GPhoto CCD" name="DEVICE_PO
    2016-06-03T07:30:44: Client 7: read <newSwitchVector device='GPhoto CCD' name='CONNECTION'>
    2016-06-03T07:30:44: Driver indi_gphoto_ccd: queuing responsible for <newSwitchVector device='GPhoto CCD' name='CONNECTION'>
    2016-06-03T07:30:44: Driver indi_gphoto_ccd: sending <newSwitchVector device="GPhoto CCD" name="CONNECT
    2016-06-03T07:30:44: Driver indi_gphoto_ccd: read <message device='GPhoto CCD' name=''>
    2016-06-03T07:30:44: Client 7: queuing <message device='GPhoto CCD' name=''>
    2016-06-03T07:30:44: Client 7: sending <message device="GPhoto CCD" timestamp="2016-06-03
    2016-06-03T07:30:44: Driver indi_gphoto_ccd: read <setSwitchVector device='GPhoto CCD' name='CONNECTION'>
    2016-06-03T07:30:44: Client 7: queuing <setSwitchVector device='GPhoto CCD' name='CONNECTION'>
    2016-06-03T07:30:44: Client 7: sending <setSwitchVector device="GPhoto CCD" name="CONNECT
    2016-06-03T07:30:44: Driver indi_gphoto_ccd: read <defNumberVector device='GPhoto CCD' name='CCD_EXPOSURE'>
    2016-06-03T07:30:44: Client 7: queuing <defNumberVector device='GPhoto CCD' name='CCD_EXPOSURE'>
    2016-06-03T07:30:44: Client 7: sending <defNumberVector device="GPhoto CCD" name="CCD_EXP
    2016-06-03T07:30:44: Driver indi_gphoto_ccd: read <defNumberVector device='GPhoto CCD' name='CCD_FRAME'>
    2016-06-03T07:30:44: Client 7: queuing <defNumberVector device='GPhoto CCD' name='CCD_FRAME'>
    2016-06-03T07:30:44: Client 7: sending <defNumberVector device="GPhoto CCD" name="CCD_FRA
    2016-06-03T07:30:44: Driver indi_gphoto_ccd: read <defNumberVector device='GPhoto CCD' name='CCD_INFO'>
    2016-06-03T07:30:44: Client 7: queuing <defNumberVector device='GPhoto CCD' name='CCD_INFO'>
    2016-06-03T07:30:44: Client 7: sending <defNumberVector device="GPhoto CCD" name="CCD_INF
    2016-06-03T07:30:44: Driver indi_gphoto_ccd: read <defSwitchVector device='GPhoto CCD' name='CCD_COMPRESSION'>
    2016-06-03T07:30:44: Client 7: queuing <defSwitchVector device='GPhoto CCD' name='CCD_COMPRESSION'>
    2016-06-03T07:30:44: Client 7: sending <defSwitchVector device="GPhoto CCD" name="CCD_COM
    2016-06-03T07:30:44: Driver indi_gphoto_ccd: read <defBLOBVector device='GPhoto CCD' name='CCD1'>
    2016-06-03T07:30:44: Client 7: queuing <defBLOBVector device='GPhoto CCD' name='CCD1'>
    2016-06-03T07:30:44: Client 7: sending <defBLOBVector device="GPhoto CCD" name="CCD1" lab
    2016-06-03T07:30:44: Driver indi_gphoto_ccd: read <defSwitchVector device='GPhoto CCD' name='CCD_FRAME_TYPE'>
    2016-06-03T07:30:44: Client 7: queuing <defSwitchVector device='GPhoto CCD' name='CCD_FRAME_TYPE'>
    2016-06-03T07:30:44: Client 7: sending <defSwitchVector device="GPhoto CCD" name="CCD_FRA
    2016-06-03T07:30:44: Driver indi_gphoto_ccd: read <defSwitchVector device='GPhoto CCD' name='CCD_FRAME_RESET'>
    2016-06-03T07:30:44: Client 7: queuing <defSwitchVector device='GPhoto CCD' name='CCD_FRAME_RESET'>
    2016-06-03T07:30:44: Client 7: sending <defSwitchVector device="GPhoto CCD" name="CCD_FRA
    2016-06-03T07:30:44: Client 7: read <newSwitchVector device='GPhoto CCD' name='CONFIG_PROCESS'>
    2016-06-03T07:30:44: Driver indi_gphoto_ccd: queuing responsible for <newSwitchVector device='GPhoto CCD' name='CONFIG_PROCESS'>
    2016-06-03T07:30:44: Driver indi_gphoto_ccd: sending <newSwitchVector device="GPhoto CCD" name="CONFIG_
    2016-06-03T07:30:44: Driver indi_gphoto_ccd: read <defTextVector device='GPhoto CCD' name='CCD_CFA'>
    2016-06-03T07:30:44: Client 7: queuing <defTextVector device='GPhoto CCD' name='CCD_CFA'>
    2016-06-03T07:30:44: Client 7: sending <defTextVector device="GPhoto CCD" name="CCD_CFA"
    2016-06-03T07:30:44: Driver indi_gphoto_ccd: read <defSwitchVector device='GPhoto CCD' name='CCD_RAPID_GUIDE'>
    2016-06-03T07:30:44: Client 7: queuing <defSwitchVector device='GPhoto CCD' name='CCD_RAPID_GUIDE'>
    2016-06-03T07:30:44: Client 7: sending <defSwitchVector device="GPhoto CCD" name="CCD_RAP
    2016-06-03T07:30:44: Driver indi_gphoto_ccd: read <defSwitchVector device='GPhoto CCD' name='WCS_CONTROL'>
    2016-06-03T07:30:44: Client 7: queuing <defSwitchVector device='GPhoto CCD' name='WCS_CONTROL'>
    2016-06-03T07:30:44: Client 7: sending <defSwitchVector device="GPhoto CCD" name="WCS_CON
    2016-06-03T07:30:44: Driver indi_gphoto_ccd: read <defSwitchVector device='GPhoto CCD' name='UPLOAD_MODE'>
    2016-06-03T07:30:44: Client 7: queuing <defSwitchVector device='GPhoto CCD' name='UPLOAD_MODE'>
    2016-06-03T07:30:44: Client 7: sending <defSwitchVector device="GPhoto CCD" name="UPLOAD_
    2016-06-03T07:30:44: Driver indi_gphoto_ccd: stderr EOF
    2016-06-03T07:30:44: Driver indi_gphoto_ccd: restart #1
    2016-06-03T07:30:44: Driver indi_gphoto_ccd: pid=14632 rfd=6 wfd=11 efd=12
    2016-06-03T07:30:44: Driver indi_gphoto_ccd: sending <getProperties version='1.7'/>
     
    2016-06-03T07:30:44: Driver indi_gphoto_ccd: read <getProperties device='Telescope Simulator' name='EQUATORIAL_EOD_COORD'>
    2016-06-03T07:30:44: Driver indi_gphoto_ccd: snooping on Telescope Simulator.EQUATORIAL_EOD_COORD
    2016-06-03T07:30:44: Driver indi_gphoto_ccd: read <getProperties device='Telescope Simulator' name='TELESCOPE_INFO'>
    2016-06-03T07:30:44: Driver indi_gphoto_ccd: snooping on Telescope Simulator.TELESCOPE_INFO
    2016-06-03T07:30:44: Driver indi_gphoto_ccd: read <getProperties device='CCD Simulator' name='FILTER_SLOT'>
    2016-06-03T07:30:44: Driver indi_gphoto_ccd: snooping on CCD Simulator.FILTER_SLOT
    2016-06-03T07:30:44: Driver indi_gphoto_ccd: read <getProperties device='CCD Simulator' name='FILTER_NAME'>
    2016-06-03T07:30:44: Driver indi_gphoto_ccd: snooping on CCD Simulator.FILTER_NAME
    2016-06-03T07:30:44: Driver indi_gphoto_ccd: read <defSwitchVector device='GPhoto CCD' name='CONNECTION'>
    2016-06-03T07:30:44: Client 7: queuing <defSwitchVector device='GPhoto CCD' name='CONNECTION'>
    2016-06-03T07:30:44: Client 7: sending <defSwitchVector device="GPhoto CCD" name="CONNECT
    2016-06-03T07:30:44: Driver indi_gphoto_ccd: read <defTextVector device='GPhoto CCD' name='DRIVER_INFO'>
    2016-06-03T07:30:44: Client 7: queuing <defTextVector device='GPhoto CCD' name='DRIVER_INFO'>
    2016-06-03T07:30:44: Client 7: sending <defTextVector device="GPhoto CCD" name="DRIVER_IN
    2016-06-03T07:30:44: Driver indi_gphoto_ccd: read <defSwitchVector device='GPhoto CCD' name='CONFIG_PROCESS'>
    2016-06-03T07:30:44: Client 7: queuing <defSwitchVector device='GPhoto CCD' name='CONFIG_PROCESS'>
    2016-06-03T07:30:44: Client 7: sending <defSwitchVector device="GPhoto CCD" name="CONFIG_
    2016-06-03T07:30:44: Driver indi_gphoto_ccd: read <defTextVector device='GPhoto CCD' name='ACTIVE_DEVICES'>
    2016-06-03T07:30:44: Client 7: queuing <defTextVector device='GPhoto CCD' name='ACTIVE_DEVICES'>
    2016-06-03T07:30:44: Client 7: sending <defTextVector device="GPhoto CCD" name="ACTIVE_DE
    2016-06-03T07:30:44: Driver indi_gphoto_ccd: read <defTextVector device='GPhoto CCD' name='DEVICE_PORT'>
    2016-06-03T07:30:44: Client 7: queuing <defTextVector device='GPhoto CCD' name='DEVICE_PORT'>
    2016-06-03T07:30:44: Client 7: sending <defTextVector device="GPhoto CCD" name="DEVICE_PO
    2016-06-03T07:30:44: Client 7: read <enableBLOB device='GPhoto CCD' name='CCD1'>
    2016-06-03T07:30:44: Driver indi_gphoto_ccd: queuing responsible for <enableBLOB device='GPhoto CCD' name='CCD1'>
    2016-06-03T07:30:44: Driver indi_gphoto_ccd: sending <enableBLOB device="GPhoto CCD" name="CCD1">
    Also
     
    2016-06-03T07:31:25: Client 7: read <newSwitchVector device='GPhoto CCD' name='CONFIG_PROCESS'>
    2016-06-03T07:31:25: Driver indi_gphoto_ccd: queuing responsible for <newSwitchVector device='GPhoto CCD' name='CONFIG_PROCESS'>
    2016-06-03T07:31:25: Driver indi_gphoto_ccd: sending <newSwitchVector device="GPhoto CCD" name="CONFIG_
    2016-06-03T07:31:25: Driver indi_gphoto_ccd: read <message device='GPhoto CCD' name=''>
    2016-06-03T07:31:25: Client 7: queuing <message device='GPhoto CCD' name=''>
    2016-06-03T07:31:25: Client 7: sending <message device="GPhoto CCD" timestamp="2016-06-03
    2016-06-03T07:31:25: Driver indi_gphoto_ccd: read <setSwitchVector device='GPhoto CCD' name='CONFIG_PROCESS'>
    2016-06-03T07:31:25: Client 7: queuing <setSwitchVector device='GPhoto CCD' name='CONFIG_PROCESS'>
    2016-06-03T07:31:25: Client 7: sending <setSwitchVector device="GPhoto CCD" name="CONFIG_
    2016-06-03T07:31:29: Client 7: read <newSwitchVector device='GPhoto CCD' name='CONFIG_PROCESS'>
    2016-06-03T07:31:29: Driver indi_gphoto_ccd: queuing responsible for <newSwitchVector device='GPhoto CCD' name='CONFIG_PROCESS'>
    2016-06-03T07:31:29: Driver indi_gphoto_ccd: sending <newSwitchVector device="GPhoto CCD" name="CONFIG_
    2016-06-03T07:31:29: Driver indi_gphoto_ccd: read <message device='GPhoto CCD' name=''>
    2016-06-03T07:31:29: Client 7: queuing <message device='GPhoto CCD' name=''>
    2016-06-03T07:31:29: Client 7: sending <message device="GPhoto CCD" timestamp="2016-06-03
    2016-06-03T07:31:29: Driver indi_gphoto_ccd: read <setSwitchVector device='GPhoto CCD' name='CONFIG_PROCESS'>
    2016-06-03T07:31:29: Client 7: queuing <setSwitchVector device='GPhoto CCD' name='CONFIG_PROCESS'>
    2016-06-03T07:31:29: Client 7: sending <setSwitchVector device="GPhoto CCD" name="CONFIG_
    2016-06-03T07:32:00: Client 7: read <newSwitchVector device='GPhoto CCD' name='CONNECTION'>
    2016-06-03T07:32:00: Driver indi_gphoto_ccd: queuing responsible for <newSwitchVector device='GPhoto CCD' name='CONNECTION'>
    2016-06-03T07:32:00: Driver indi_gphoto_ccd: sending <newSwitchVector device="GPhoto CCD" name="CONNECT
    2016-06-03T07:32:00: Driver indi_gphoto_ccd: read <setSwitchVector device='GPhoto CCD' name='CONNECTION'>
    2016-06-03T07:32:00: Client 7: queuing <setSwitchVector device='GPhoto CCD' name='CONNECTION'>
    2016-06-03T07:32:00: Client 7: sending <setSwitchVector device="GPhoto CCD" name="CONNECT
    7 years 9 months ago #8611

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

    Replied by Jasem Mutlaq on topic INDI Web Manager

    What is the content of your indiwebmanager.service file?

    EDIT: I just tried my 600D with the INDI Web Manager and it all worked OK.
    Last edit: 7 years 9 months ago by Jasem Mutlaq.
    7 years 9 months ago #8612

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

    • Posts: 29
    • Thank you received: 2

    Replied by Clément on topic INDI Web Manager

    Here is the Systemd service file:
    [Unit]
    Description=INDI Web Manager
    After=multi-user.target
     
    [Service]
    Type=idle
    ExecStart=/usr/bin/python /home/pi/indiwebmanager/servermanager/drivermanager.py
     
    [Install]
    WantedBy=multi-user.target

    I will try to get a Canon DSLR next week to check if the issue is related to Nikon DSLRs. I tested with both D90 and D5300, so it is probably the case.
    7 years 9 months ago #8614

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

    Replied by Jasem Mutlaq on topic INDI Web Manager

    That's your problem. Please clone INDI Web Manager again and use the supplied indiwebmanager.service file.
    7 years 9 months ago #8617

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

    • Posts: 29
    • Thank you received: 2

    Replied by Clément on topic INDI Web Manager

    I have tested with the last version, it works fine now. Thanks a lot!
    7 years 9 months ago #8671

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

    • Posts: 29
    • Thank you received: 2

    Replied by Clément on topic INDI Web Manager

    I have another question: is it possible with the web manager to choose which XML skeleton to use? I use Indiduino and I am interested in doing that. I could modify the startINDIServer function in the servermanager.py file to declare the environment variable I need, but is there something nicer?
    7 years 9 months ago #8672

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

    • Posts: 72
    • Thank you received: 21

    Replied by Philippe on topic INDI Web Manager

    Yesterday (on the 16th of July) I've started to work with indiwebmanager and met few issues.
    I've install it on RPI3 running Raspian Jessie.
    I've removed my old Projet folder, and follow instruction to compile indi from git to get up to date indiserver and drivers, native and 3rdparty ones.
    make, sudo make install without problem.
    With gpsd 3rdparty, erro library not found. It has been solved with sudo apt-get install libgps-dev.
    Then few test with indi and simulator dirvers. OK
    Now git clone webindiserver, and troubles started.
    - Some simulator's driver wasn't with the <driverList> </driverList> (Don't remeber which one. I've corrected these and the drivermanager.py manually started well expect listen on port 8624 instead 8080!
    Easy to correct like this is at end of the file, just swap the # comment between the two last lines.
    - Then I followed the instructions to start the server on RPI boot. next error occured. lunch of the script failed. It was due to no IP adress present in time (I use DHCP). To correct that I've added these two lines in the indiwebmanager.service, below [service] section:
    [Service]
    ...
    Restart=always
    RestartSec=5

    - then last but not least, other error with the autostart.py scipt. It use also the port 8624 on line 7. Changed to 8080 and now everything works fine.

    Hope could help someone in the future!

    PS Isaw that in EKOS the default prot for Indi Web Manager is set to 8624, that means probably easyier to correct the instruction on the github to access via "http://localhost:8624"

    Regards, Philippe
    Philippe Besson
    Skywatcher HEQ5, Televue 101-IS, Takahashi FS-60CB
    Focus Boss II with OptecInc TCF-S focuser and Starlight Instruments HSM20 handy stepper motor
    Guiding camera ZWO ASI120MM
    Filterwheel OptecInc IFW
    Camera not set yet
    Switzerland
    Last edit: 7 years 8 months ago by Philippe. Reason: Found a new information through Ekos
    7 years 8 months ago #9337

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

    Time to create page: 1.097 seconds