×

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

Bi-monthly release with minor bug fixes and improvements

Cannot connect to remote indiserver device from PH

  • Posts: 269
  • Thank you received: 53
I'm not sure if this is an INDI problem or PHD2 problem but I'm guessing it is INDI or more likely something I'm doing or not doing in regards to INDI
Hoping someone can point me in the right direction.

I have INDI installed on a Raspberry Pi 2 running Ubuntu Mate 15.10. IP Address 192.168.0.15
Raspberry Pi is powered from a powered USB hub
A DBK21AU04 camera is connected to the powered USB hub
RPi: Indi library 1.2.0 Protocol 1.7
I also have INDI and PHD2 installed on my 64bit desktop running Ubuntu 15.10
Desktop: Indi library 1.2.0 Protocol 1.7

I am chaining to the camera on the RPi from indiserver on the desktop.
Running PHD2 on the RPi I can connect successfully to the camera.
But if I try to connect to the camera from PHD2 running on the desktop it cannot connect.
In fact, available camera is not displayed in PHD2 setup
I thought indiserver on the desktop would provide same info to PHD2 as if the camera were connected locally and would show up in the Driver dropdown list.
If there is an easy way to test the chained connection I'm keen to know. I tried using EKOS but it always set up its own indiserver.

Details are as follows:
On the RPi I start indiserver with:
indiserver -vv indi_v4l2_ccd &

Then on desktop I start indiserver with:
indiserver -vv indi_v4l2_ccd@192.168.0.15 &

I run PHD2 on the desktop. I click the Connect button and select as Camera "Indi Camera"
I then click the Camera Setup button:
- Indiserver is shown as connected
- Driver has no drop down options. So I type in V4L2 CCD (this is the option that appears on the RPi)
- CCD says Main Imager
I then click OK

desktop indiserver log says:
ken@ken-ubuntu:~$ 2016-02-02T10:27:41: Client 0: new arrival from 127.0.0.1:40270 - welcome!
2016-02-02T10:27:41: Client 0: read <getProperties device='' name=''>
2016-02-02T10:27:41: Driver indi_v4l2_ccd@192.168.0.15: queuing responsible for
2016-02-02T10:27:41: Driver indi_v4l2_ccd@192.168.0.15: sending

2016-02-02T10:27:50: Client 0: read EOF
2016-02-02T10:27:50: Client 0: shut down complete - bye!

I then click Connect in PHD2
indiserver log says:
ken@ken-ubuntu:~$ 2016-02-02T10:29:51: Client 0: new arrival from 127.0.0.1:40272 - welcome!
2016-02-02T10:29:51: Client 0: read <enableBLOB device='V4L2 CCD' name='CCD1'>
2016-02-02T10:29:51: Client 0: read <getProperties device='V4L2 CCD' name=''>
2016-02-02T10:29:57: Client 0: read EOF
2016-02-02T10:29:57: Client 0: shut down complete - bye!

PHD reports that it cannot connect to V4L2 CCD

Next I try Camera Setup with Driver: indi_v4l2_ccd
I then click OK

indiserver log says:
ken@ken-ubuntu:~$ 2016-02-02T10:31:41: Client 0: new arrival from 127.0.0.1:40276 - welcome!
2016-02-02T10:31:41: Client 0: read <getProperties device='' name=''>
2016-02-02T10:31:41: Driver indi_v4l2_ccd@192.168.0.15: queuing responsible for
2016-02-02T10:31:41: Driver indi_v4l2_ccd@192.168.0.15: sending

2016-02-02T10:31:55: Client 0: read EOF
2016-02-02T10:31:55: Client 0: shut down complete - bye!

I then click Connect
indiserver log says:
ken@ken-ubuntu:~$ 2016-02-02T10:33:38: Client 0: new arrival from 127.0.0.1:40278 - welcome!
2016-02-02T10:33:38: Client 0: read <enableBLOB device='indi_v4l2_ccd' name='CCD1'>
2016-02-02T10:33:38: Driver indi_v4l2_ccd@192.168.0.15: queuing responsible for
2016-02-02T10:33:38: Driver indi_v4l2_ccd@192.168.0.15: sending
Al
2016-02-02T10:33:38: Client 0: read <getProperties device='indi_v4l2_ccd' name=''>
2016-02-02T10:33:38: Driver indi_v4l2_ccd@192.168.0.15: queuing responsible for
2016-02-02T10:33:38: Driver indi_v4l2_ccd@192.168.0.15: sending

2016-02-02T10:37:44: Client 0: read EOF
2016-02-02T10:37:44: Client 0: shut down complete - bye!

I then click Connect
indiserver log says:
ken@ken-ubuntu:~$ 2016-02-02T10:38:28: Client 0: new arrival from 127.0.0.1:40284 - welcome!
2016-02-02T10:38:28: Client 0: read <enableBLOB device='indi_v4l2_ccd@192.168.0.15' name='CCD1'>
2016-02-02T10:38:28: Client 0: read <getProperties device='indi_v4l2_ccd@192.168.0.15' name=''>
2016-02-02T10:38:34: Client 0: read EOF
2016-02-02T10:38:34: Client 0: shut down complete - bye!

PHD reports that it cannot connect to indi_v4l2_ccd@192.168.0.15
8 years 1 month ago #6835

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

1. Why are you chaining? Chaining is only necessary if you have multiple devices spread across multiple PCs.
2. You need to specify the device name, not it executable:
indiserver -v "V4L2 CCD"@192.168.0.15
3. Ekos already has a guide module. To use Ekos, set it to "remote" and select the V4L2 driver from the dropdown list. In the setup page, click "Options" and go to the Ekos tab, and set the IP address of the RPI and its port (7624)
8 years 1 month ago #6836

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

  • Posts: 193
  • Thank you received: 46

Chaining should well to reduce network load. I have an allsky camera currently on the far side of a wireless bridge, and often run with multiple clients processing the data. If they all connect to the remote indi server, then 3 copies of the fits have to cross the bridge. If I chain from a local indi server, then one copy of an image crosses the bridge, and the local server feeds it out to the three local clients. At least that's my understanding of what should happen.
8 years 1 month ago #6840

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


Yes, this is another case where chaining can be useful.
8 years 1 month ago #6846

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

  • Posts: 269
  • Thank you received: 53
I've been looking at Kstars/Ekos and I'm very impressed!
What I was trying to do is emulate what Ekos does for guiding and run PHD2 on one machine with the camera on the RPi. Mainly as I'm familiar with PHD2. I can run PHD2 on the RPi but it seems sluggish so I wanted to see if it was better to offload it to another machine. Plus it's an opportunity to come to grips with chaining e..g. if I want to have the imaging cam on a separate RPi.
I'll use the startup line you've given me and see how it goes - thanks for the tip!
8 years 1 month ago #6847

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

Time to create page: 0.392 seconds