Adrien Barrajon replied to the topic '[solved] QHY163M driver' in the forum. 4 weeks ago

Well it works! I've used the GitHub link you've provided and it's all good now. I still have a problem with the FW which thinks it has 9 slots instead of 5, and I'm not sure why I can't get bin 4x4, but that's for another thread. Thanks for your help.

Read More...

Adrien Barrajon replied to the topic 'QHY163M driver' in the forum. 4 weeks ago

I'm running Kstars/Ekos on a laptop (Dell XPS 13" 9360) with Arch Linux. I'm using the latest version, with all applied updates. The camera is brand new, and would probably be plugged directly in USB-3, the other equipments (mount & autoguider) plugged into a USB hub.

I don't know if power is being drawn. How can I check?

I assume the cables are good because the camera is brand new. I can't really try with other cables because the USB-3 is a weird socket on the camera side. Something I had never seen before. But I know for sure the power works (fan spins when camera is powered, and the FW does one full rotation), and I'm pretty sure the USB connection works too because I see the camera appearing with lsusb (although no vendor/product).

I'll give a try to that package, thanks for the link.

Read More...

Adrien Barrajon replied to the topic 'QHY163M driver' in the forum. 1 month ago

Oh well, I'll give it a try.
Does it work well on Ubuntu? Maybe I could make a USB stick install for this...

Read More...

Adrien Barrajon replied to the topic 'QHY163M driver' in the forum. 1 month ago

So... no one managed to get that camera to work with INDI on another distro that Ubuntu?

Read More...

Adrien Barrajon created a new topic ' QHY163M driver' in the forum. 1 month ago

Hello,

I have a QHY163m that I can't get to work with INDI. I saw drivers on the QHY website but it's a .deb archive and I'm running Arch. No source code. I tried installing what I could from the .deb archive, but all I got to work is an ugly proprietary GUI that can't connect to my camera, no INDI compatibility (QHY asks me to connect a device). The INDI QHY driver can't connect to the camera and then crashes (log attached).

lsusb gives an empty line:

Bus 001 Device 012: ID 1618:c163

And no correspondence with this ID in 85-qhy.rules (but correct vendor ID).

I also have a FW attached (QHYCFW2-M), but I'm focusing on the camera first. Then I'll worry about the FW. Any ideas on how I could make it work? Can I simply hook it up to an existing QHY driver by editing udev rules? Or is the solution actually in that package I can't install?

Thanks!

Read More...

85-qhy.rules file attached (renamed in .txt to allow upload).

So this is the file I am now using. It originally came with the libindi_3rdparty 1.6.2 (latest version), and I added these lines:

Lines 28 - 37:

#Van Ooijen Technische Informatica
ATTRS{idVendor}=="16c0", ATTRS{idProduct}=="081a", RUN+="/sbin/fxload -t fx2 -I /lib/firmware/qhy/QHY5.HEX -D $env{DEVNAME} -s /lib/firmware/qhy/QHY5LOADER.HEX"
ATTRS{idVendor}=="16c0", ATTRS{idProduct}=="0818", RUN+="/sbin/fxload -t fx2 -I /lib/firmware/qhy/QHY5.HEX -D $env{DEVNAME} -s /lib/firmware/qhy/QHY5LOADER.HEX"
ATTRS{idVendor}=="16c0", ATTRS{idProduct}=="2972", RUN+="/sbin/fxload -t fx2 -I /lib/firmware/qhy/QHY8.HEX -D $env{DEVNAME}"
ATTRS{idVendor}=="16c0", ATTRS{idProduct}=="2970", RUN+="/sbin/fxload -t fx2 -I /lib/firmware/qhy/QHY2PRO.HEX -D $env{DEVNAME}"
ATTRS{idVendor}=="16c0", ATTRS{idProduct}=="296c", RUN+="/sbin/fxload -t fx2 -I /lib/firmware/qhy/QHY5.HEX -D $env{DEVNAME}"

# Orion SSAG
ATTRS{idVendor}=="1856", ATTRS{idProduct}=="0011", RUN+="/sbin/fxload -t fx2 -I /lib/firmware/qhy/QHY5.HEX -D $env{DEVNAME} -s /lib/firmware/qhy/QHY5LOADER.HEX"
ATTRS{idVendor}=="1856", ATTRS{idProduct}=="0113", RUN+="/sbin/fxload -t fx2 -I /lib/firmware/qhy/QHY5.HEX -D $env{DEVNAME} -s /lib/firmware/qhy/QHY5LOADER.HEX"

Lines 82-86:
SUBSYSTEMS=="usb", ATTRS{idVendor}=="1856", MODE="0666"
SUBSYSTEMS=="usb", ATTRS{idVendor}=="1781", ATTRS{idProduct}=="0c7c", MODE="0666"
SUBSYSTEMS=="usb", ATTRS{idVendor}=="04b4", ATTRS{idProduct}=="8613", MODE="0666"
SUBSYSTEMS=="usb", ATTRS{idVendor}=="0547", ATTRS{idProduct}=="1002", MODE="0666"


Read More...

I found the source of the problem. The /lib/udev/rules.d/85-qhy.rules was missing the lines for the vendor 1856 / product 0011. I just copy/pasted them from the 85-qhy.rules I had on my other machine. Works fine now. Not sure why those lines weren't present. I guess I'll have to reinput them manually next time there's an update.

Anyway, solved.

Read More...

Hi all,

I can't seem to connect to my Orion Starshoot Autoguider from my new laptop. My device seems to be completely unrecognized by my system.

When I plug the camera to my computer (USB2), I should have a red LED on it, but it does not turn on. I have a "test" profile on Ekos, using only indi_qhy_ccd driver, and as soon as I start INDI (even before I try to connect), I get a message box saying "No QHY camera detected. Power on?".

The Ekos output looks like this:

2018-02-05T00:35:45 Unable to establish:
+ QHY CCD
Please ensure the device is connected and powered on.
2018-02-05T00:35:40 INDI services started on port 7624. Please connect devices.
2018-02-05T00:35:40 Starting INDI services...
2018-02-05T00:35:40 INDI services stopped.
2018-02-05T00:31:21 Unable to establish:
+ QHY CCD
Please ensure the device is connected and powered on.
2018-02-05T00:31:17 INDI services started on port 7624. Please connect devices.
2018-02-05T00:31:17 Starting INDI services...
2018-02-05T00:31:15 INDI services stopped.
2018-02-05T00:30:59 Unable to establish:
+ QHY CCD
Please ensure the device is connected and powered on.
2018-02-05T00:30:54 INDI services started on port 7624. Please connect devices.
2018-02-05T00:30:54 Starting INDI services...

Interestingly, the output of the 'lsusb' command is:
tan@bobby ~$ lsusb
Bus 002 Device 002: ID 0424:5742 Standard Microsystems Corp. 
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 007: ID 0c45:670c Microdia 
Bus 001 Device 005: ID 04f3:20d0 Elan Microelectronics Corp. 
Bus 001 Device 003: ID 0cf3:e300 Qualcomm Atheros Communications 
Bus 001 Device 008: ID 1856:0011  
Bus 001 Device 006: ID 138a:0091 Validity Sensors, Inc. VFS7552 Touch Fingerprint Sensor
Bus 001 Device 004: ID 04f3:0235 Elan Microelectronics Corp. 
Bus 001 Device 002: ID 0424:2742 Standard Microsystems Corp. 
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

Notice the empty line for Device 008? That's the autoguider, which by the way works fine on other computers.

My INDI log directory (~/.indi/logs) does not exist. My laptop (Dell XPS 13 9360) is running Arch Linux with KDE Plasma, Kstars and Ekos.

Any ideas?

Read More...

Adrien Barrajon created a new topic ' libindi_3rdparty package for Arch Linux?' in the forum. 4 months ago

Hi everyone,

I've been trying to build the libindi_3rdparty source on Arch Linux, and make exits with an error because of a missing log4z.h file in the indi-qhy folder. I could download that file from another location and the build worked.

However this is not a clean install, I'd rather have a package. There is a package in the Arch User Repository but it's outdated (1.2). I tried creating a package from the source with the added log4z.h but it can't install (says that /lib already exists, duh!) (also I should say that I don't know much about creating Arch packages).

Anyway, does anyone know if I can find a nice PKGBUILD to cleanely install libindi_3rdparty on my Arch system?

Many thanks

Read More...

Adrien Barrajon replied to the topic 'Ekos solver only solving the first image?' in the forum. 6 months ago

Oh and something I forgot to mention as well. In the Capture tab under Ekos, I have weird numbers in the Frame section. W is 5616, which it should be, but H is -1524852282, where it should say 3744. I double checked in the INDI settings and I have the right values so I'm not sure what the problem is.

Read More...

Adrien Barrajon replied to the topic 'Ekos solver only solving the first image?' in the forum. 6 months ago

Usually I capture images in native format (.cr2). In that case, my files are 5616 x 3744 pixels, which correspond to the maximul resolution of my camera.

However, I also captures a couple of .fits files, and just realised that some of my fits files have slightly different resolution (4365 x 2910). I'm unsure why. I'm testing now INDI with just gPhoto driver, captured two images, one fit and one raw, and both of them have the same resolution, 5616 x 3744.

On the INDI gPhoto control panel - Image Settings tab, I have the correct Width and Height, while Top and Left are both 0. On the Image Info files, same Width and Height, Pixel X, Y and size is 8.20um, bits per pixel is 8 (I tried to set it to 14, which is the correct number, but it doesn't want to change). Note that on the Image Info tab, I sometimes find a different value for Width and Height: 5634 x 3753, which is above my camera's max resolution.

Also, when I open one of my .cr2 files in PixInsight, it tells me this:

Thumb size: 5616 x 3744
Full size: 5792 x 3804
Image size: 5634 x 3753
Output size: 5634 x 3753
Note that apart from Thumb size, all those values are above my camera's max resolution.

I'm trying again at the observatory tonight, so I'm gonna keep a close look at my files resolutions.

Read More...

Adrien Barrajon replied to the topic 'Ekos solver only solving the first image?' in the forum. 6 months ago

That's odd, I always 'apt update & apt upgrade' before observing nights. On the Help menu of Kstars, it says I'm using version 2.8.7, Build: 2017-11-09T12:28:19Z, which I thought was the last one!

My camera pixel shift is 8.20 um. I did install 4200 index files through the astrometry Debian packages available on Synaptic.

Read More...

Adrien Barrajon created a new topic ' Ekos solver only solving the first image?' in the forum. 6 months ago

Hi all,

I'm having problems with the Astrometry.net solver in Ekos, while trying both online and offline methods. It usually works perfectly fine on the first image I try in a session, and in less than 5s, but then nothing. On any following image, the solver (both online and offline) will work endlessly without finding a solution. I even tried solving twice in a row the same field ("capture & solve" with the sync option, and "capture & solve" immediately again without moving the telescope) and it didn't work. However, if I disconnect my devices, stop INDI, close Kstars, and restart everything, my first image will solve again in less than 5 seconds.

I attached the log I have for that night but couldn't find anything relevant in it. The options passed by Ekos to the solver are "-O --no-plots --no-verify --resort --no-fits2fits --downsample 2 -L 19.3223 -H 26.6952 -u aw -3 119.209 -4 -90 -5 30". I'm using gPhoto driver (for a Canon EOS 5d Mk II) and Celestron NexStar driver (for a CGE Pro mount). The telescope has a long focal length (3950mm) so my FOV is pretty small.

When the first image is solved, the solver tells me to update the FL to around 5600mm, which I did even if it sounds weird (far from the announced FL, not sure why), but it didn't help. I also checked that the solver options update when the telescope is moved, which they do fine.

So I'm a bit out of options now. Does anyone have an idea of what I could try to troubleshoot this?

Thanks

Read More...

Adrien Barrajon replied to the topic 'Support for Apogee Alta U47?' in the forum. 9 months ago

So I tried again today after upgrading INDI and Apogee driver and I'm getting the same issue. Here is the log update:

INFO	0.063757 sec	: Session log file /home/tan/.indi/logs/2017-09-01/indi_apogee_ccd/indi_apogee_ccd_12:54:37.log
INFO	1.246531 sec	: Attempting to find Apogee CCD...
ERROR	1.519568 sec	: Error opening camera: libapogee:/build/libapogee3-upZIm_/libapogee3-3.0.3234+r3367~201708311716~ubuntu16.04.1/libapogee/linux/GenOneLinuxUSB.cpp(476):UsbRequestIn failed with error -9.  RequestCode = c2 : Index = 0 : Value = 2:1
INFO	23.154595 sec	: Attempting to find Apogee CCD...
ERROR	23.166990 sec	: Error getting USB address: libapogee:/build/libapogee3-upZIm_/libapogee3-3.0.3234+r3367~201708311716~ubuntu16.04.1/libapogee/linux/GenOneLinuxUSB.cpp(72):failed to claim usb interface:0
INFO	24.750435 sec	: Attempting to find Apogee CCD...
ERROR	24.759876 sec	: Error getting USB address: libapogee:/build/libapogee3-upZIm_/libapogee3-3.0.3234+r3367~201708311716~ubuntu16.04.1/libapogee/linux/GenOneLinuxUSB.cpp(72):failed to claim usb interface:0
INFO	25.738597 sec	: Attempting to find Apogee CCD...
ERROR	25.749745 sec	: Error getting USB address: libapogee:/build/libapogee3-upZIm_/libapogee3-3.0.3234+r3367~201708311716~ubuntu16.04.1/libapogee/linux/GenOneLinuxUSB.cpp(72):failed to claim usb interface:0


Read More...

Adrien Barrajon replied to the topic 'Support for Apogee Alta U47?' in the forum. 9 months ago

I'm using downloads/old-versions/apogee-driver-3.7.0-linux-x86.tgz.

Read More...

Adrien Barrajon replied to the topic 'Support for Apogee Alta U47?' in the forum. 9 months ago

I edited the file and it didn't seem to solve the problem. I'm getting the same errors, which are:

2017-08-31T07:58:45: Error getting USB address: libapogee:/build/libapogee3-lQrGz5/libapogee3-3.0.3234+r3357~201708291059~ubuntu16.04.1/libapogee/GenOneLinuxUSB.cpp(72):failed to claim usb interface:0 
2017-08-31T07:58:45: Attempting to find Apogee CCD... 
2017-08-31T07:58:40: Error opening camera: libapogee:/build/libapogee3-lQrGz5/libapogee3-3.0.3234+r3357~201708291059~ubuntu16.04.1/libapogee/GenOneLinuxUSB.cpp(476):UsbRequestIn failed with error -9.  RequestCode = c2 : Index = 0 : Value = 2:1 
2017-08-31T07:58:40: Attempting to find Apogee CCD... 


Read More...

Login



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!