Welcome, Guest
Username: Password: Remember me
02 Jan 2018
INDI development team is happy to announce the release of INDI Library v1.6.0. This new exciting release builds on the maturity of INDI Library and comes with many new supported devices and fixes for existing drivers.
Read More...

TOPIC: QHYCCD driver: Can not expose more than 5 seconds.

QHYCCD driver: Can not expose more than 5 seconds. 3 weeks 1 day ago #22052

On the PC I am at now the relevant rule is at
/lib/udev/rules.d/85-qhy.rules

I've that file and that line installed.

Your firmware should be (from your log), /usr/local/lib/qhy/firmeare/QHY5II.HEX.
If the firmware is missing you could install it.

That file do exist (only in the non-working PC) since I've installed it from the QHY GitHub repo. See my first post here for further information.

What software distribution are you using on each PC?
Where did you install indi from? Are both PC's up to date?

Working PC: Kubuntu 17.10, 64-bit
The other one: clean installation of Xubuntu 17.04 LTS 32-bit
Both PCs are up-to-date. INDI installed from the official PPA as suggested from the Ubuntu download page in this site.
I tried to get some logs from the QHY, so I ran tail -n LINES /var/log/syslog until I got all the lines regarding the CCD, changing the LINES value. When I arrived to ~20, I don't know if it related, the camera magically booted correctly and the red LED lighted up, so I took a 1s photo - OK - and a 6s one - back to the original error. But this time the LED, instead of returning red, started to blink, even after closing INDI. What does it mean?
~$ tail -n 20 /var/log/syslog
Dec 29 21:55:31 marco-packardBell kernel: [ 2417.567510] perf: interrupt took too long (5095 > 5076), lowering kernel.perf_event_max_sample_rate to 39250
Dec 29 22:01:22 marco-packardBell wpa_supplicant[982]: wlp2s0: WPA: Group rekeying completed with e0:b9:e5:6b:6c:ab [GTK=CCMP]
Dec 29 22:11:22 marco-packardBell wpa_supplicant[982]: wlp2s0: WPA: Group rekeying completed with e0:b9:e5:6b:6c:ab [GTK=CCMP]
Dec 29 22:16:15 marco-packardBell kernel: [ 3661.679352] usb 1-1: USB disconnect, device number 3
Dec 29 22:16:17 marco-packardBell kernel: [ 3663.172259] usb 1-1: new high-speed USB device number 4 using ehci-pci
Dec 29 22:16:17 marco-packardBell kernel: [ 3663.321129] usb 1-1: New USB device found, idVendor=1618, idProduct=0920
Dec 29 22:16:17 marco-packardBell kernel: [ 3663.321147] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Dec 29 22:16:17 marco-packardBell mtp-probe: checking bus 1, device 4: "/sys/devices/pci0000:00/0000:00:1d.7/usb1/1-1"
Dec 29 22:16:17 marco-packardBell mtp-probe: bus: 1, device: 4 was not an MTP device
Dec 29 22:16:17 marco-packardBell kernel: [ 3663.407965] usb 1-1: USB disconnect, device number 4
Dec 29 22:16:17 marco-packardBell systemd-udevd[5587]: Process '/sbin/fxload -t fx2 -I /usr/local/lib/qhy/firmware/QHY5II.HEX -D /dev/bus/usb/001/004' failed with exit code 255.
Dec 29 22:16:19 marco-packardBell kernel: [ 3665.160255] usb 1-1: new high-speed USB device number 5 using ehci-pci
Dec 29 22:16:19 marco-packardBell kernel: [ 3665.309157] usb 1-1: config 1 interface 0 altsetting 0 bulk endpoint 0x81 has invalid maxpacket 64
Dec 29 22:16:19 marco-packardBell kernel: [ 3665.309173] usb 1-1: config 1 interface 0 altsetting 0 bulk endpoint 0x1 has invalid maxpacket 64
Dec 29 22:16:19 marco-packardBell kernel: [ 3665.310223] usb 1-1: New USB device found, idVendor=1618, idProduct=0921
Dec 29 22:16:19 marco-packardBell kernel: [ 3665.310239] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
Dec 29 22:16:19 marco-packardBell kernel: [ 3665.310249] usb 1-1: Product: QHY5-II          
Dec 29 22:16:19 marco-packardBell kernel: [ 3665.310259] usb 1-1: Manufacturer: QHY-CCD  
Dec 29 22:16:19 marco-packardBell mtp-probe: checking bus 1, device 5: "/sys/devices/pci0000:00/0000:00:1d.7/usb1/1-1"
Dec 29 22:16:19 marco-packardBell mtp-probe: bus: 1, device: 5 was not an MTP device
I have never seen a device working in such a strange way...

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

QHYCCD driver: Can not expose more than 5 seconds. 3 weeks 1 day ago #22053

Try a different USB port.

Try a powered USB hub.

I think this is a problem with the QHY liking alot of juice!

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

QHYCCD driver: Can not expose more than 5 seconds. 3 weeks 1 day ago #22054

My QHY will only work on my Raspberry PI when I plug it into a powered USB hub.

Could be a current problem: the 2.0 USB ports on my bigger PC can provide much more current than a 10' mini-PC. What about the blinking LED? Is it turning on and off every second?

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

QHYCCD driver: Can not expose more than 5 seconds. 3 weeks 1 day ago #22055

No idea what the blinking means.

No problem with usb port on my main PC.
On my raspberry Pi there are problems once I start plugging into the USB ports
the QHY5II-M will only work if I plug it into a powered USB hub.

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

QHYCCD driver: Can not expose more than 5 seconds. 3 weeks 1 day ago #22061

I recommend doing another update of the software with apt-get. My latest pull corrected some issues with fxload.

After the update, two things to check. Do a "which fxload" to figure out the path of the fxload being used. Next, look at /lib/udev/rules.d/85-qhy.rules and go to the line that starts with:
ATTRS{idVendor}=="1618", ATTRS{idProduct}=="0920"
What is the path for fxload there?

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

QHYCCD driver: Can not expose more than 5 seconds. 3 weeks 1 day ago #22076

Working PC:
~$ which fxload
/sbin/fxload

~$ cat /lib/udev/rules.d/85-qhy.rules | grep "ATTRS{idVendor}==\"1618\", ATTRS{idProduct}==\"0920\""
ATTRS{idVendor}=="1618", ATTRS{idProduct}=="0920", RUN+="/sbin/fxload -t fx2 -I /lib/firmware/qhy/QHY5II.HEX -D $env{DEVNAME}"

~$ ls /lib/firmware/qhy/QHY5II.HEX
/lib/firmware/qhy/QHY5II.HEX
The other one: exact same output. Probably a simple power problem: whenever, luckily, the camera boots there, if I press the screen power save button (built-in in the keyboard) the camera powers off again. The camera doesn't boot, too, if powering it from the always-on port from my main PC when it's off (current-limiting state).
Kind regards,
SB.

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

Last Edit: by SquareBoot.

QHYCCD driver: Can not expose more than 5 seconds. 3 weeks 1 day ago #22078

Power might be an issue, but it never was for me with RPi2 and 3. The files look good, so the next test would be to manually run the firmware command and check the output. First, do lsusb to find the bus id.
Bus 002 Device 014: ID 1618:0920
In the above example, the bus ID would be 002:014. This will change each time you replug the camera. Having that in hand, run the firmware load command as superuser:
sudo /sbin/fxload -t fx2 -I /lib/firmware/qhy/QHY5II.HEX -D bus:device
For our example, you would put 002:014 after the -D.

Anyhow, this might give you an idea as to whether-or-not the firmware can be loaded on that small computer.

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

QHYCCD driver: Can not expose more than 5 seconds. 3 weeks 1 day ago #22079

~$ lsusb
Bus 002 Device 008: ID 1618:0921
...

~$ sudo /sbin/fxload -t fx2 -I /lib/firmware/qhy/QHY5II.HEX -D 002:008
[sudo] password di marco: 
No such file or directory : 002:008
Not working on both PCs :dry:

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

QHYCCD driver: Can not expose more than 5 seconds. 3 weeks 1 day ago #22080

I apologize for giving you the wrong command.
sudo /sbin/fxload -t fx2 -I /lib/firmware/qhy/QHY5II.HEX -D /dev/bus/usb/bus/device
However, since lsusb shows the ID as 1618:0921, this should mean that the firmware has already been loaded.
Therefore, the problem might indeed be power or that the USB 1 interface isn’t good enough.

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

QHYCCD driver: Can not expose more than 5 seconds. 3 weeks 1 day ago #22082

This time the right command worked.

However, since lsusb shows the ID as 1618:0921, this should mean that the firmware has already been loaded.

Right, for a strange / magical reason I don't know at all, before running lsusb last time the camera booted correctly. However, I'm quite sure that a Xubuntu bug woke up the QHY: when I looked at the system logs a bug report from the power manager was there - no way to find it anymore: it might have reset the root hub, I would like to suppose. Now the CCD works as if the USB provides it all the necessary power...
Kind regards,
SB.

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

QHYCCD driver: Can not expose more than 5 seconds. 3 weeks 1 day ago #22084

Some useful info:

From the QHY5L-II User manual 2016 edition


3.How to avoid the camera hangs

If you camera always hangs. It may be caused by many reasons. You can check the
following things.

3.1 If there is power leak for your mounts and computers? The power leak may
cause the leak current transfer from computer to the camera via the GND . This
may effect the USB transfer and cause the data packet lost and cause it hang.
You need make sure the computer and the mount is well grounded.

3.2 If the USB port's voltage not enough? Some computer's USB port +5V is not
enough. It may cause the camera always hangs. In this condition you can use a
powered USB3.0 HUB to connect camera and get the good +5V power for camera.

3.3 If your cpu load is too high? If CPU load is too high, it will cause many
frame lost and cause the camera hangs. You can increase the USB traffic value
to reduce the FPS and get more stable video transfer.

3.4 If the USB cable connection is good enough? Sometimes the contact issue in
the USB cable to camera or USB cable to computer will cause the signal loss and
cause camera always hangs. Espcially when you move the cables. In this
condition. you can try to add a little silicon oil into the USB socket/plug
.This can increase the contact a lot better.

3.5 Avoid the statics. Sometimes the static electricity on human body will
cause the camera hang. You can touch the computer metal case for first before
touch the camera to let the static elelctricity on your body release.

3.6 Some computer's front USB port is not so good for high speed transfer (The
reason is it connected to mainboard by a cable and which has no good signal
integrity). If you found the camera always hangs on front USB port. You can try
the USB port on backside of the computer (which is connect to chipset directly
on the mainboard).


There is also some info in a chat on SGL
Intersting talk re flashing LED on QHY

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

QHYCCD driver: Can not expose more than 5 seconds. 3 weeks 1 day ago #22087

Thanks! So here we have the solution!
From the forum you linked:

The qhy5l-ii, at least, requires a high bandwidth - usb 2 High Speed port and a good quality cable.

SB.

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

Time to create page: 0.154 seconds

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!


Gallery

Replica

Why INDI

Replica