qhyccd-lzr
commented
4 years ago Drivers are developed directly at QHYCCD company now. Users should use those official drivers, driver in that github does not support all cams and is very, very obsolete.
Inside their distributions, there are also test applications. I have never tested qhyccd on Gentoo distro, just Ubuntu, so difficult to say if this may have influence. Otherwise,
from you listing below it looks, your camera was properly detected and even firmware was uploaded to it. Normally, without firmware download, the VID: PID is 1618:0178,
after firmware upload and device reset, it is seen as VID:PID 1618:0179 which is your case.
---------- Původní e-mail ---------- Od: zenmetsu notifications@github.com Komu: qhyccd-lzr/QHYCCD_Linux_New QHYCCD_Linux_New@noreply.github.com Datum: 2. 3. 2020 2:07:25 Předmět: [qhyccd-lzr/QHYCCD_Linux_New] Camera not found (#14) " I'll close this if it is invalid, however I am having trouble verifying that the driver is working as intended. I looked at the installation script, and nothing appears to be terribly specific to any particular distribution. I am attempting to get this running on Gentoo, however the application I am trying to use (Firecapture) seems to crash when I select the QHY driver, and most reports indicate that this tends to happen if the camera is not detected or attached.
I can't find an entry under /dev that corresponds to the camera. I have / dev/video devices from my laptop's two built-in cameras, but I'm just not seeing where the QHY device is being created in the /dev tree. I have a QHY5 III178mono if it matters.
This is the output found in my logs when the camera is attached:
Mar 1 17:56:36 mercury kernel: usb 3-2.1: new high-speed USB device number 3 using xhci_hcd Mar 1 17:56:36 mercury kernel: usb 3-2.1: New USB device found, idVendor=1618, idProduct=0178, bcdDevice= 1.00 Mar 1 17:56:36 mercury kernel: usb 3-2.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 Mar 1 17:56:36 mercury kernel: usb 3-2.1: Product: WestBridge Mar 1 17:56:36 mercury kernel: usb 3-2.1: Manufacturer: Cypress Mar 1 17:56:36 mercury kernel: usb 3-2.1: SerialNumber: 0000000004BE Mar 1 17:56:36 mercury kernel: usb 4-2.1: new SuperSpeed Gen 1 USB device number 4 using xhci_hcd Mar 1 17: 56:36 mercury kernel: usb 4-2.1: LPM exit latency is zeroed, disabling LPM. Mar 1 17:56:36 mercury kernel: usb 4-2.1: New USB device found, idVendor= 1618, idProduct=0179, bcdDevice= 0.00 Mar 1 17:56:36 mercury kernel: usb 4- 2.1: New USB device strings: Mfr=1, Product=2, SerialNumber=0 Mar 1 17:56:36 mercury kernel: usb 4-2.1: Product: Titan178U Mar 1 17:56:36 mercury kernel: usb 4-2.1: Manufacturer: QHYCCD
Let me know what other diagnostic info is needed, and which kernel options are dependencies that I might be overlooking. I'm trying to figure out if this is an issue with the SDK or the application that I am using.
Thanks.
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub (https://github.com/qhyccd-lzr/QHYCCD_Linux_New/issues/14?email_source=notifications&email_token=ABHY2VDD7RGEMKABRNRM27LRFMBEDA5CNFSM4K7KJP72YY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4IRRKRAQ) , or unsubscribe (https://github.com/notifications/unsubscribe-auth/ABHY2VAE3FV4Y75EESHVALDRFMBEDANCNFSM4K7KJP7Q) . "
zenmetsu
I'll close this if it is invalid, however I am having trouble verifying that the driver is working as intended. I looked at the installation script, and nothing appears to be terribly specific to any particular distribution. I am attempting to get this running on Gentoo, however the application I am trying to use (Firecapture) seems to crash when I select the QHY driver, and most reports indicate that this tends to happen if the camera is not detected or attached.
I can't find an entry under /dev that corresponds to the camera. I have /dev/video devices from my laptop's two built-in cameras, but I'm just not seeing where the QHY device is being created in the /dev tree. I have a QHY5III178mono if it matters.
This is the output found in my logs when the camera is attached:
Let me know what other diagnostic info is needed, and which kernel options are dependencies that I might be overlooking. I'm trying to figure out if this is an issue with the SDK or the application that I am using.
Thanks.