Hi Silver,

It is now possible to connect the QHY filter wheel with a ZWO camera. Previously the QHY filter wheels didn't have an independent driver from the QHY cameras, but Jasem went and put together dedicated drivers for QHY filter wheels so you can operate them with other ccds. Depending on the model of your QHY filterwheel the drivers are:
indi_qhycfw1_wheel
indi_qhycfw2_wheel
indi_qhycfw3_wheel
For example I'm using a QHY 2-S filter wheel and use the indi_qhycfw2_wheel driver. They should all be downloaded when downloading all INDI drivers, so should also be available to you.

Read More...

I wasn't able to make the QHY filter wheel work when hooked up with the ASI camera. I tried running the filter wheel independently and with the QHY CCD driver, but that also didn't work. Are you able to operate your QHY filter wheel without the QHY CCD?

Read More...

I'm using the QHY filter wheel with a ZWO ASI CCD ( indilib.org/devices/ccds/zwo-optics-asi-cameras.html ) and I've connected the filter wheel to that CCD. I accidently said KStars when I meant Ekos, oops. The wheel doesn't work with Ekos.

Read More...

Hi,

I'm trying to connect a PyIndi-client to the QHY CFW. The filter wheel is mentioned here:
indilib.org/devices/ccds/qhy.html
but doesn't indicate that there is a driver for the filter wheel. I thought maybe it was embedded with the QHY CCD driver, but it is not. I also could not find the driver in the QHY repository that the page mentions to download.

So I went looking for an INDI driver for the filter wheel and found this:
indilib.org/develop/indiforjava/i4jdrive...er-wheel-driver.html
Which seems to be what I want, except that it is for Java and though it says it is still compatible with the regular "indiserver indi_qhy_ccd" command to start up the indiserver, it doesn't seem to be connected to INDI properties ( www.indilib.org/develop/developer-manual...dard-properties.html )
I'm thinking this because the driver downloaded with some documentation (attached) on commands to interact with the wheel using bytes and does not mention INDI properties. I also tried the indi_qhy_ccd and java drivers with KStars and KStars was not able to find and connect to the filter wheel. (The java driver also seems like it may not be able to be used with the USB port option on the filter wheel. Which is also an added issue.)

I was hoping to find a driver like the one listed on the INDI site for the QHY CCD for the filter wheel. Does one exist? Is the java one the only INDI driver available for the QHY CFW? If so, am I mistaken that it is not compatible with INDI properties?

Any input on the QHY CFW INDI driver would be helpful, thank you!

Read More...

I figured it out. It was a permissions issue that I solved by running:
sudo chmod 777 /home/user/.cache/pip
and
sudo chmod 777 /home/user/.cache/pip/*
I'm not sure why this was causing the issue, especially since I also tried downloading pyindi-client from pypi.org/project/pyindi-client/#description and was also causing the same issue. Again, probably something really stupid, but I guess atleast it's working now.

Read More...

This might be an easily answerable question, but it's really got me stumped. I'm redownloading pyindi-client following www.indilib.org/develop/indi-python-bindings.html . At
--> pip3 install --user --install-option="--prefix=" pyindi-client

I get an error:
arm-linux-genueabihf-gcc -pthread -DNDEBUG -g -fwrapv -O2 -Wall -Wstrict-prototypes -g -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -I/usr/include -I/usr/include/libindi -I/usr/include/python3.5m -c indiclientpython_wrap.cpp -o build/temp.linux-armv7l-3.5/indiclientpython_wrap.o -std=c++11
cc1plus: warning: command line option '-Wstrict-prototypes' is valid for C/ObjC but not for C++
creating build/lib.linux-armv7l-3.5
arm-linux-gnueabihf-g++ -pthread -shared -Wl,-O1 -Wl,-Bsymbolic-functions -Wl,-Bsymbolic-functions -Wl,-z,relro -Wl,-Bsymbolic-functions -Wl,-s,relro -g -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 build/temp.linux-armv7l-3.5/indiclientpython_wrap.o /usr/lib/libindiclient.a -lz -lcfitsio -lnova -o build/lib.linux-armv7l-3.5/_PyIndi.cpython-35m-arm-linux-gnueabihf.so
/usr/bin/ld: cannot find -lz
collect2: error: ld returned 1 exit status
error: command 'arm-linux-gnueabihf-g++' failed with exit status 1

I'm not sure what's going on, because last time I went through the process it went without a hitch.

Read More...

Aylin replied to the topic 'Using PyIndi client with a simple GUI' in the forum. 6 years ago

I don't understand though how I can edit the code for the GUI that dcd.py creates to make it my own. How would I go about doing that?

Read More...

Aylin replied to the topic 'Using PyIndi client with a simple GUI' in the forum. 6 years ago

Hi Oleg,

This might be a really silly question, but on the gtkindiclient source (DCD-0.13 device control device) you linked to, I can't figure out where to actually download the module gtkindiclient.

Read More...

Aylin replied to the topic 'Using PyIndi client with a simple GUI' in the forum. 6 years ago

I do, but I need a customized client. The other INDI clients have a lot of what I don't need. I'm just looking to make a simple interface.

Read More...

Aylin created a new topic ' Using PyIndi client with a simple GUI' in the forum. 6 years ago

Hi,
I've been having a lot of issues creating a client for multiple devices, a filter wheel and camera. When following the PyIndi client tutorials, I'm not able to change a device property by choice. I'm now trying to control the devices through a simple button GUI to provide an interface to change a set of properties by choice. For example, I have one simple GUI with 2 buttons, one to change the filter wheel to slot 1 and the other to change it to slot 2. Going into this, I thought that it would be as simple as running a basic client in the background and import another client for the filter wheel where I could call the function newProperty through my GUI. This is the code I have for changing the filter slot (bits of it):

#######################################################
class IndiClient(PyIndi.BaseClient):
dwheel = None
def __init__(self):
super(IndiClient, self).__init__()
def newDevice(self, d):
pass #connecting the filter wheel via a basic client
def newProperty(self, p):
if p.getName() == "FILTER_SLOT":
self.nd18()
......
def nd18(self):
slot=self.dwheel.getNumber("FILTER_SLOT")
slot[0].value=1
self.sendNewNumber(slot)

##############################################################3
I imported the IndiClient class from the script to my GUI and am trying to call newProperty, but I hit an issue with the arguments. I don't know how to call the functions ie: newProperty(self, p) because of the "p", property, parameter. I'm not very well versed with Python, so I imagine I'm missing something very obvious, but its doing a dang good job of eluding me. I'm not even sure if just calling the function newProperty or even nd18 would work.

tltr: How do you connect a GUI to a PyIndi client? Can you call one of the PyIndi functions such as newProperty(self, p) and if so, how?

Read More...