Jasem Mutlaq thanked Jason Westervelt in topic Canon+Pi3 connecting issue 6 hours 31 minutes ago
Jason Westervelt replied to the topic 'Canon+Pi3 connecting issue' in the forum. 14 hours 59 minutes ago

Well, there isn't a "3rd party" driver for the canon, so to speak. From my understanding, canon_ccd is supported by the base INDI package. I always add in indi_gphoto_ccd when starting INDI and my Canon connects right up. I am using a 20D though. The only other thing that I can think of is 1) make sure the camera is not in PTP communications mode and 2) try using the [M]anual mode if you aren't already doing so.

Also, starting indiserver with -v or -vv may show more details, specifically which parameters are failing.


Jason Westervelt replied to the topic 'Canon+Pi3 connecting issue' in the forum. 17 hours 29 minutes ago

I think I had issues until I compiled the indi_gphoto_ccd 3rd party driver. Maybe try other USB ports on the Pi?


Jason Westervelt replied to the topic 'INDI/Linux driver for the QHY Polemaster, developers needed.' in the forum. 19 hours 27 minutes ago

I managed to use the Polemaster as a guider in EKOS last night with my rPi GPIO ST4 implementation. I did run into an issue while attempting to use it for imaging. It appears to have problems when exposure times exceed 45sec or so, where images returned were just black and contained no data. It could have been a software issue on my end, I'll test again this evening with a pristine installation of INDI.


Jason Westervelt replied to the topic 'RaspberryPI - GPIO to ST4 Guiding Driver' in the forum. 2 days ago

I get that about needing level shifters and optoisolators, etc. The software still needs to be there.

Do you have a listing of the capabilities of your AstroHat? Will it be able to send guiding via ST4, focusing, DSLR shutter control, etc?


Jason Westervelt replied to the topic 'RaspberryPI - GPIO to ST4 Guiding Driver' in the forum. 2 days ago

I managed to cobble something together using reverse-engineering/repurposing the existing ardust4 and corresponding indi driver. I'll post it to my github once i clean it up a bit, however folks using a RaspberryPi instead of a Pine64 will need to modify the pinout.h file, and if running on 32bit distro, may need to make two small changes to the source. I need to wait until nightfall to test with my gear.

This whole exercise does highlight a large opportunity for INDI development. There really should be a unified RaspberryPi GPIO driver where individual pins can be assigned to things such as focuser control, ST4 guiding, DSLR bulb trigger, flat/cover servo actuation, and so on.


Jason Westervelt replied to the topic 'RaspberryPI - GPIO to ST4 Guiding Driver' in the forum. 3 days ago

Please excuse the extreme thread necromancy...

Is there a raspberry pi GPIO driver for ST4 guiding? I have built an interface using a 4-channel optoisolator and cables, I just need to connect it to a controller, preferably direct to the Pi's GPIO but alternatively through an Arduino. Did anyone ever manage to write up a C++ driver for this? If not, is there an example showing an arduino used as a USB->ST4 interface with INDI?


Jason Westervelt replied to the topic 'WebManager' in the forum. 3 days ago

check if there is a stale process...

$ ps aux | grep indi

You might need to kill the stale process or reboot.


Looks like a slightly older article. KStars/EKOS will run in windows natively now. Not really a need for two Pi systems.

I'd say, skip the two pi setup, save battery while out in the field. Just run INDI on the Pi3 along with hostapd for the access point, grab KStars for your laptop, connect it's wifi to the Pi, and configure KStars to connect to the Pi3.


I don't use wifi between my EKOS laptop and the pi running Indi, but no reason that you shouldn't be able to. Normally I connect my laptop to my mobile phone's wifi and then use an ethernet cable to the pi and share my wifi internet connection to the ethernet via windows 10.

If you are mobile and want internet from the pi, for online plate solving for instance, you could probably connect your pi and your laptop to your phone's hotspot and then find out the IP of the pi and connect to it.

Otherwise, you could set up the pi as an access point, as you stated, and then connect via your laptop. The advantage with that method is that you'll know the IP of the Pi and it won't change. Having the Pi connect to an access point, on the other hand, will usually result in it getting a dynamic IP and that could complicate matters slightly.

There is a guide here which covers using dnsmasq and hostapd to turn the Pi 3 into an access point. It is pretty straight forward but it does take a little bit of time to configure. Keep in mind that disabling DHCP on wlan0 and running the hostapd service will prevent your Pi from connecting to other wifi access points as a client. If you need to get network access to it after things are up and running, you'll have to either connect to the Pi's access point, or use the ethernet cable and attach the pi to an existing network.


You should be able to connect bluetooth as an RFCOMM device, which is basically another serial port to the linux system... usually showing up as

or the like.

The raspberrypi 3 would probably be a better fit here since it has WiFi and Bluetooth on board.

Anyway, try following this guide .

Once that is done, you SHOULD be able to specify /dev/rfcomm0 or whatever as the comm port and it should connect right up.


I attempted to enable compression and got about the same framerate from the camera... it turns out that the CPU was limiting.

I compiled on my pine64 and connected via GigE. Framerate was about doubled, however it appears that compression is single threaded.

I left the indi server up for 2 hours why grabbing frames continuously, and I did not experience issues.


Thanks Jasem!

I tested the new build and initially had issues:
- needed GCC 5.x for qhy driver
- my polemaster was not receiving the firmware blob upload and thus was not being recognized by indilib

My polemaster is showing up as Bus 001 Device 006: ID 1618:0940
After loading firmware, it shows up as 1618:0941. I had to modify 85-qhy.rules to include 1618:0940. Disconnecting and reattaching the PoleMaster after making this change resulted in the firmware getting loaded and the device being recognized by indilib.

I found that I was getting about 1FPS while framing. I guess this is to be expected since I am using an Intel Edison which is a dual-core Intel @500MHz, plus I am connecting via WiFi.

I did notice a message about SQM while starting the server which I didn't notice prior to loading the QHY module. Is there perhaps plans to use the PoleMaster as a SQ Meter, because that would be a cool use for the device.


I have a polemaster and can offer assistance with coding, but I'm not so sure about the NDA.

The Polemaster really is just a QHY5L-IIm. In fact, it works with the older QHY5LII ASCOM drivers just fine. Polemaster support was explicitly removed from the imaging driver, so I do not expect that we will get much cooperation from the maker on this. I guess what I'm trying to say is that there already is a INDI support for this should the support for the Polemaster be re-enabled in the binary blobs.


Jason Westervelt replied to the topic 'QHY5 camera and Raspberry Pi' in the forum. 7 days ago

For what it is worth, I have gotten INDI running well on both the Pine64 2GB model, as well as on an intel Edison. Granted I haven't done any video transfer, just transferring images from my DSLR and controlling the mount, but it appears to be sufficient. Neither of those boards share USB with networking though, and could potentially be viable alternatives to the Pi.



3rd Party

Choose from the numerous 3rd party INDI drivers to suit your needs!

Got Problem?

Check out the FAQ, the forum, and the bug tracking system to resolve any issues you might have!
You can also subscribe to INDI newsletter and development mailing lists to get the latest updates on INDI!