×
INDI Library v1.8.5 Released (19 Apr 2020)

April 2020 release of INDI Library v1.8.5 introduces new drivers while providing fixes and improvements to existing devices and core framework.

QHY5 not found by Ekos

1 year 1 month ago
crw4096
Expert Boarder
Expert Boarder
Posts: 94
More
Topic Author
QHY5 not found by Ekos #40314
Hi,

I played around with "udevadm monitor" while plugging in the QHY5-II-M. I don't know what to make of it. It does seem to follow Guido's description of what happens when one of these cameras is plugged in, except for the fxload error. I'm including various logs for your scrutiny.

This is the syslog as I plugged in the device:
Jun 18 21:55:27 indi-pi kernel: usb 1-1.3.5.4: new high-speed USB device number 14 using dwc_otg
Jun 18 21:55:27 indi-pi kernel: usb 1-1.3.5.4: New USB device found, idVendor=1618, idProduct=0920, bcdDevice= 0.00
Jun 18 21:55:27 indi-pi kernel: usb 1-1.3.5.4: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Jun 18 21:55:27 indi-pi mtp-probe[890]: checking bus 1, device 14: "/sys/devices/platform/soc/3f980000.usb/usb1/1-1/1-1.3/1-1.3.5/1-1.3.5.4"
Jun 18 21:55:27 indi-pi mtp-probe[890]: bus: 1, device: 14 was not an MTP device
Jun 18 21:55:27 indi-pi systemd-udevd[889]: Process '/sbin/fxload -t fx2 -I /lib/firmware/qhy/QHY5II.HEX -D ' failed with exit code 255.
Jun 18 21:55:27 indi-pi kernel: usb 1-1.3.5.4: USB disconnect, device number 14
Jun 18 21:55:29 indi-pi kernel: usb 1-1.3.5.4: new high-speed USB device number 15 using dwc_otg
Jun 18 21:55:29 indi-pi kernel: usb 1-1.3.5.4: config 1 interface 0 altsetting 0 bulk endpoint 0x81 has invalid maxpacket 64
Jun 18 21:55:29 indi-pi kernel: usb 1-1.3.5.4: config 1 interface 0 altsetting 0 bulk endpoint 0x1 has invalid maxpacket 64
Jun 18 21:55:29 indi-pi kernel: usb 1-1.3.5.4: New USB device found, idVendor=1618, idProduct=0921, bcdDevice= 0.00
Jun 18 21:55:29 indi-pi kernel: usb 1-1.3.5.4: New USB device strings: Mfr=1, Product=2, SerialNumber=0
Jun 18 21:55:29 indi-pi kernel: usb 1-1.3.5.4: Product: QHY5-II          
Jun 18 21:55:29 indi-pi kernel: usb 1-1.3.5.4: Manufacturer: QHY-CCD  
Jun 18 21:55:30 indi-pi mtp-probe[896]: checking bus 1, device 15: "/sys/devices/platform/soc/3f980000.usb/usb1/1-1/1-1.3/1-1.3.5/1-1.3.5.4"
Jun 18 21:55:30 indi-pi mtp-probe[896]: bus: 1, device: 15 was not an MTP device

This is the brief output from udevadm:
udevadm monitor -k -u
monitor will print the received events for:
UDEV - the event which udev sends out after rule processing
KERNEL - the kernel uevent

KERNEL[10242.584954] add      /devices/platform/soc/3f980000.usb/usb1/1-1/1-1.3/1-1.3.5/1-1.3.5.4 (usb)
KERNEL[10242.587013] add      /devices/platform/soc/3f980000.usb/usb1/1-1/1-1.3/1-1.3.5/1-1.3.5.4/1-1.3.5.4:1.0 (usb)
UDEV  [10242.716144] add      /devices/platform/soc/3f980000.usb/usb1/1-1/1-1.3/1-1.3.5/1-1.3.5.4 (usb)
UDEV  [10242.737332] add      /devices/platform/soc/3f980000.usb/usb1/1-1/1-1.3/1-1.3.5/1-1.3.5.4/1-1.3.5.4:1.0 (usb)
KERNEL[10242.902631] remove   /devices/platform/soc/3f980000.usb/usb1/1-1/1-1.3/1-1.3.5/1-1.3.5.4/1-1.3.5.4:1.0 (usb)
KERNEL[10242.903221] remove   /devices/platform/soc/3f980000.usb/usb1/1-1/1-1.3/1-1.3.5/1-1.3.5.4 (usb)
UDEV  [10242.912296] remove   /devices/platform/soc/3f980000.usb/usb1/1-1/1-1.3/1-1.3.5/1-1.3.5.4/1-1.3.5.4:1.0 (usb)
UDEV  [10242.917210] remove   /devices/platform/soc/3f980000.usb/usb1/1-1/1-1.3/1-1.3.5/1-1.3.5.4 (usb)
KERNEL[10244.879284] add      /devices/platform/soc/3f980000.usb/usb1/1-1/1-1.3/1-1.3.5/1-1.3.5.4 (usb)
KERNEL[10244.881772] add      /devices/platform/soc/3f980000.usb/usb1/1-1/1-1.3/1-1.3.5/1-1.3.5.4/1-1.3.5.4:1.0 (usb)
UDEV  [10245.000575] add      /devices/platform/soc/3f980000.usb/usb1/1-1/1-1.3/1-1.3.5/1-1.3.5.4 (usb)
UDEV  [10245.013969] add      /devices/platform/soc/3f980000.usb/usb1/1-1/1-1.3/1-1.3.5/1-1.3.5.4/1-1.3.5.4:1.0 (usb)

I plugged in a second time with more extensive logging (udevadm -k -u -p). That output is in the attached file. From above, it looks like the device attaches, removes, then reattaches. In the attached log, it looks like the first group of ADD events have something to do with the product ID "0920" and the second bunch of ADD events are related to product ID "0921".

Mind you, the camera works in Ekos. I am happy to provide any other info if you think it will help figure out why there's an fxload error in the syslog. Otherwise, I'm calling this "fixed"...

Thanks for all the help,

Charles

Ubuntu 18.04 and Raspbian Jessie; INDI 1.7.4
Mounts: CEM-60 chiefly; iEQ45
Cameras: Atik 383L+, QHY5-II-M
Focuser: Moonlite
Attachments:

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

1 year 1 month ago
AradoSKYindi
Gold Boarder
Gold Boarder
Posts: 302
More
QHY5 not found by Ekos #40319
Hello CRW4096,

The two rule files for QHYCCD are out of sync with the QHY5LII. The driver cannot load because other configuration steps are missing. The -D has this string {env(DEVNAME)}.

This session variable is setup in 85-QHY-Cameras.rules. The 85-QHYCCD.rules has the device parameters. Check the Cameras rule first. Then, check the QHYCCD rule next. Only search in QHY and enable only QHY5II 1618 and 0921 lines. This should help you get this running.

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

1 year 1 month ago
Odiug
Senior Boarder
Senior Boarder
Posts: 45
More
QHY5 not found by Ekos #40326
@CRW4096:
BTW, thanks for the pictures, but I would actually need to get close up shots of all PCBs from both sides, so I can see the traces.

Anybody else who has a QHY5-II and could make detailled PCB pictures? Maybe I should post this as a seperate topic...
I am interested in the differences in wiring between QHY5 and QHY5-II.

Regards
Guido

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

1 year 1 month ago 1 year 1 month ago by crw4096.
crw4096
Expert Boarder
Expert Boarder
Posts: 94
More
Topic Author
QHY5 not found by Ekos #40341

AradoSKYindi wrote: Hello CRW4096,
This session variable is setup in 85-QHY-Cameras.rules. The 85-QHYCCD.rules has the device parameters.


There *is* no "85-QHY-Cameras.rules" file. There is only "/lib/udev/rules.d/85-qhyccd.rules". I have grep'd the entire system:
<code>$ sudo find / \( -name '*QHY*.rules' -o -name '*qhy*.rules' \) -print
/lib/udev/rules.d/85-qhyccd.rules
/home/pi/git/indi/3rdparty/libqhy/85-qhyccd.rules</code>
These are the only rules file for QHY products, and as you can see, one of them is in my copy of the git repo and hence not active. I am attaching this file for your scrutiny.

Charles

(Sorry - looks like I forgot to attach the file. I'll get it later when I'm home)

Ubuntu 18.04 and Raspbian Jessie; INDI 1.7.4
Mounts: CEM-60 chiefly; iEQ45
Cameras: Atik 383L+, QHY5-II-M
Focuser: Moonlite

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

1 year 1 month ago 1 year 1 month ago by AradoSKYindi.
AradoSKYindi
Gold Boarder
Gold Boarder
Posts: 302
More
QHY5 not found by Ekos #40366
Hello CRW4096,

This is how I approached the problem. I look at the RULES files on my systems for QHYCCD. I had two.

I created this one. It had specific actions of setup for the QHY5LII-C. Looked over each 1618:0920 with QHY5II.hex entry. I used this template to configur the device.

85-qhy-camera-rules-local.rules

ACTION!="add", GOTO="qhy_end"
SUBSYSTEM=="usb", ENV{DEVTYPE}=="usb_device", GOTO="qhy_test"
SUBSYSTEM!="usb_device", GOTO="qhy_end"

LABEL="qhy_test"

ATTRS{idVendor}=="1618", ATTRS{idProduct}=="0921", RUN+="/sbin/fxload -t fx2 -I /usr/local/openastro/lib/firmware/qhy/QHY5II.HEX -D $env{DEVNAME}"

ATTRS{idVendor}=="1618", ATTRS{idProduct}=="0941", RUN+="/sbin/fxload -t fx2 -I /usr/local/openastro/lib/firmware/qhy/POLEMASTER.HEX -D $env{DEVNAME}"

LABEL="qhy_end"

# This section is reached after the device has loaded the firmware and reset

ACTION!="add", GOTO="qhy_fw_end"
SUBSYSTEMS=="usb", GOTO="qhy_fw"
GOTO="qhy_fw_end"

LABEL="qhy_fw"

ATTRS{idVendor}=="1618", ATTRS{idProduct}=="0921*", OWNER="root", GROUP="users", MODE="0660", PROGRAM="/bin/sh -c 'i=0;while [ -e QHY5L-$i ]; do i=$(($i+1)); done; echo $i'", SYMLINK+="QHY5L-%c"

LABEL="qhy_fw_end"

This file sets up the USB communications and SYMLINK.

The next file has these additional commands. They could be combined together. I stuck with what I had. Besides, the code had terminations arleady setup. It works.

85-qhyccd.local.rules

#===============================================================================
# 1. Pre-enumerated device IDs:
#===============================================================================

# QHY
ACTION=="add", SUBSYSTEM=="usb", ATTRS{idVendor}=="1618", ATTRS{idProduct}=="0921", RUN+="/sbin/fxload -t fx2 -I /usr/local/lib/qhy/firmware/QHY5II.HEX -D $env{DEVNAME}"

ACTION=="add", SUBSYSTEM=="usb", ATTRS{idVendor}=="1618", ATTRS{idProduct}=="0941", RUN+="/sbin/fxload -t fx2lp -I /usr/local/lib/qhy/firmware/POLEMASTER.HEX -D $env{DEVNAME}"

#===============================================================================
# 2. Post-enumeration device IDs:
#===============================================================================


# QHYCCD
ACTION=="add", SUBSYSTEM=="usb", ATTRS{idVendor}=="1618", ATTRS{idProduct}=="0921", MODE="0666", GROUP="plugdev"
ACTION=="add", SUBSYSTEM=="usb", ATTRS{idVendor}=="1618", ATTRS{idProduct}=="0941", MODE="0666", GROUP="plugdev"

# Stock QHY
SUBSYSTEMS=="usb", ATTRS{idVendor}=="1618", ATTRS{idProduct}=="0921", MODE="0666"
SUBSYSTEMS=="usb", ATTRS{idVendor}=="1618", ATTRS{idProduct}=="0941", MODE="0666"
ATTRS{idVendor}=="1618",ATTRS{idProduct}=="0921", ENV[ID_MM_DEVICE}="1"
ATTRS{idVendor}=="1618",ATTRS{idProduct}=="0921", ENV{MTP_NO_PROBE="1"

LABEL="qhy-rules-end"


I separated out the originals and created new local files. This will prevent the orginals from being overwritten.

Clear skies.

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

1 year 1 month ago 1 year 1 month ago by han.k.
han.k
Gold Boarder
Gold Boarder
Posts: 303
Karma: 6
More
QHY5 not found by Ekos #40903
I have a new setup with Raspbian Buster and want to connect an original QHY5 (2011) to PHD2. The original QHY5 seems not supported by PHD2, but also the INDI driver indi_qhy_ccd doesn't work. With -vvv option the driver reports waiting for the hardware to be connected.

Is it still possible to use the original QHY5 using an older INDI driver?
Any additional driver required?

Han

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

1 year 1 month ago 1 year 1 month ago by han.k.
han.k
Gold Boarder
Gold Boarder
Posts: 303
Karma: 6
More
QHY5 not found by Ekos #40909
I just got the first generation QHY5 working using an old virtual machine running Ubuntu Astronomy 16.04, Indi 1.6.3, indi_qhy_CCD driver v1.8. I will look if I can install the old QHY driver.

Is it not better to keep this old driver in the library as suggested earlier?

Han

Later, downloaded INDI 1.6.2 but what to do with this error? Folder libqhy is in 3rdparty??

pi@raspberrypi:~/indi_old/build/indi-qhy $ cmake -DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_BUILD_TYPE=Debug ../../3rdparty/indi-qhy
-- The CXX compiler identification is GNU 8.3.0
-- The C compiler identification is GNU 8.3.0
-- Check for working CXX compiler: /usr/bin/c++
-- Check for working CXX compiler: /usr/bin/c++ -- works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- Check for working C compiler: /usr/bin/cc
-- Check for working C compiler: /usr/bin/cc -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Detecting C compile features
-- Detecting C compile features - done
-- Found CFITSIO 3.45: /usr/lib/arm-linux-gnueabihf/libcfitsio.so
-- Found INDI: /usr/lib/arm-linux-gnueabihf/libindidriver.so;/usr/lib/arm-linux-gnueabihf/libindiAlignmentDriver.so (found version "1.6.2")
CMake Error at /home/pi/indi_old/cmake_modules/FindQHY.cmake:44 (message):
QHY not found. Please install libqhy www.indilib.org
Call Stack (most recent call first):
CMakeLists.txt:13 (find_package)


-- Configuring incomplete, errors occurred!
See also "/home/pi/indi_old/build/indi-qhy/CMakeFiles/CMakeOutput.log".

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

1 year 1 month ago 1 year 1 month ago by han.k.
han.k
Gold Boarder
Gold Boarder
Posts: 303
Karma: 6
More
QHY5 not found by Ekos #40927
Okay found a solution at :
indilib.org/forum/general/693-qhy-driver...pped-by-default.html

first go to directory libqhy
cmake -DCMAKE_INSTALL_PREFIX=/usr
sudo make install

But still the driver still doesn't detect the original QHY5. Strange is the new INDI not fully overwritten by the old?. It works using an old virtual machine.

Later:
Installed INDI v1.6.2. on a new Raspian Buster installation, same problem. Driver doesn't see the QHY5. "NO QHY camera detected. Power on?"
Installed v.1.6.2 on a virtual machine Lubuntu 18.04, the QHY5 camera is seen. Images can be taken

Why does it work in Ubuntu virtual machine and not on Pi 3 with Raspbian Buster??? Different USB behavior?

The QHY5 is on device 004 and is not recognised:

pi@raspberrypi:/usr/bin $ lsusb
Bus 001 Device 004: ID 1618:0901
Bus 001 Device 006: ID 1c4f:0002 SiGma Micro Keyboard TRACER Gamma Ivory
Bus 001 Device 005: ID 046d:c03d Logitech, Inc. M-BT96a Pilot Optical Mouse
Bus 001 Device 007: ID 0424:7800 Standard Microsystems Corp.
Bus 001 Device 003: ID 0424:2514 Standard Microsystems Corp. USB 2.0 Hub
Bus 001 Device 002: ID 0424:2514 Standard Microsystems Corp. USB 2.0 Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
pi@raspberrypi:/usr/bin $

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

1 year 1 month ago
Odiug
Senior Boarder
Senior Boarder
Posts: 45
More
QHY5 not found by Ekos #40940
You could also try to use indi-ssag. The Starshoot Autoguider is in fact a QHY5.

However this driver works a bit different. For indi-qhy, the firmware for the QHY5 is loaded by the udev kernel mechanism, with the help of fxload and a udev rule which can either be found in /lib/udev/rules.d or /etc/udev/rules.d. In my case it is 85-qhy.rules.

The indi-ssag driver needs to find an uninitialized SSAG or QHY5, because it loads the firmware on its own. For this the loading of the firmware via udev must be prevented. If 85-qhy.rules is found in /lib/udev/rules.d the cleanest way to disable is "ln -s /dev/null /etc/udev/rules.d/85-qhy.rules", because a rule file under /etc/udev/rules.d shadows a rule file with the same name under /lib/udev/rules.d.

What do you want to use the QHY5 for? It's quite outdated and especially the Linux firmware has some (hidden) issues (Indeed for some strange reason, Windows loads a different, slightly simpler and I assume slightly older firmware ).
I probably should write down my findings about the QHY5/SSAG from my experience in building a QHY5 clone and analyzing the firmware, but I didn't find the time yet.

CS
Guido

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

1 year 1 month ago
han.k
Gold Boarder
Gold Boarder
Posts: 303
Karma: 6
More
QHY5 not found by Ekos #40942
Guido,

Thanks for your advice. At this moment I come to the conclusion that the USB detection is causing the problem. i have installed INDI 1.6.2 in both a Raspberry Pi3B and virtual machine running Lubuntu . In the virtual machine it works most of the time. lsusb reports the QHY5 correctly. In Pi3, lsusb doesn't do that for the QHY5 only.

I tried tonight also my classic QHY8 (for guiding), but it seems to suffer from the same problem.

To conclude, I just found and will buy a secondhand QHY5-II. This should solve my problems and I will sell the QHY5 for use in Windows. The QHY5 served me well since 2011 using the ASCOM driver. The large sensor is still great for guiding and in 99.8% of the time a guide star is within range. Modern guide camera have often a smaller sensors and cost a few hunderd euros/dollars.

Maybe the USB of the Pi4 (which will arrive in one or two days) will behave differently, but the QHY5-II will solve any problems and can be read by PHD2 directly.

Han

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

1 year 1 month ago 1 year 1 month ago by han.k.
han.k
Gold Boarder
Gold Boarder
Posts: 303
Karma: 6
More
QHY5 not found by Ekos #40966
Okay , I have now QHY5-II mono. Still the same problem also in the Pi 4 . It is not reported in the USB list :(

pi@raspberrypi:/usr/bin $ lsusb
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 005: ID 1c4f:0002 SiGma Micro Keyboard TRACER Gamma Ivory
Bus 001 Device 015: ID 1618:0920
Bus 001 Device 014: ID 046d:c03d Logitech, Inc. M-BT96a Pilot Optical Mouse
Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub


Bus 001 Device 015: ID 1618:0920 is added as soon I connect the QHY5-II mono
Anyone an idea how to solve this?

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

1 year 1 month ago
wvreeven
Platinum Boarder
Platinum Boarder
Posts: 1576
Karma: 8
More
QHY5 not found by Ekos #40967
Han,

Open a terminal and type

dmesg -w

This will print out all kernel messages since boot time and then will wait for more. Then connect the camera and see what messages you get. They will give you a hint as to why the camera doesn't get recognised.


Wouter

ASI6200 and filter wheel with a SkyWatcher Esprit 80 ED on a SkyWatcher HEQ5-Pro
ASI1600MM-Pro Cooled and filter wheel with an 8" TS Ritchey-Chrétien on a SkyWatcher EQ6-R

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

Time to create page: 0.815 seconds