qhyccd-lzr / QHYCCD_Linux_New

This repository contains a new (2017+) QHYCCD's Ubuntu Linux 64 and ARM V8 (Raspberry PI3, Odroid XU4) deliveries.
8 stars 3 forks source link

Problems with QHY128C #4

Open quams opened 6 years ago

quams commented 6 years ago

Hoi!

I have a problem running the SingleFrameMode test application on Linux with a QHY 128C camera. It detects the camera but hangs when downloading the captured frame:

SingleFrameMode, Version: 1.00
2018-02-06 13:24:03.231 LOG_ALARM -----------------  log4z thread started!   ----------------------------
2018-02-06 13:24:03.232 LOG_ALARM logger id=0 key=Main name=SingleFrameMode path=/tmp/ level=1 display=1
SDK resources initialized.
Number of QHYCCD cameras found: 1
Application connected to the following camera from the list: Index: 1,  cameraID = QHY128C-f922d2428bc892e8c
Open QHYCCD success.
SetQHYCCDStreamMode set to: 0, success.
2018-02-06 13:24:03.284 LOG_FATAL qhy5iii128base.cpp (qhy5iii128base.cpp):184
InitQHYCCD success.
GetQHYCCDOverScanArea:
Overscan Area startX x startY : 0 x 0
Overscan Area sizeX  x sizeY  : 0 x 0
GetQHYCCDEffectiveArea:
Effective Area startX x startY: 0 x 0
Effective Area sizeX  x sizeY : 0 x 0
GetQHYCCDChipInfo:
Effective Area startX x startY: 0 x 0
Chip  size width x height     : 36.150 x 24.380 [mm]
Pixel size width x height     : 5.970 x 5.970 [um]
Image size width x height     : 6056 x 4084
This is a color camera.
SetQHYCCDParam CONTROL_USBTRAFFIC set to: 10, success.
SetQHYCCDParam CONTROL_GAIN set to: 10, success
SetQHYCCDParam CONTROL_OFFSET set to: 140, success.
SetQHYCCDParam CONTROL_EXPOSURE set to: 20000, success.
SetQHYCCDResolution roiStartX x roiStartY: 0 x 0
SetQHYCCDResolution roiSizeX  x roiSizeY : 6056 x 4084
SetQHYCCDBinMode set to: binX: 1, binY: 1, success.
SetQHYCCDParam CONTROL_TRANSFERBIT set to: 10, success.
ExpQHYCCDSingleFrame(pCamHandle) - start...
ExpQHYCCDSingleFrame(pCamHandle) - end...
ExpQHYCCDSingleFrame success.
Will try to allocate: 74198112 [uchar] for image data.
Allocated memory for frame: 74198112 [uchar].

After some tests and a bit of poking around if located the problem within this block:

// get single frame
retVal = GetQHYCCDSingleFrame(pCamHandle, &roiSizeX, &roiSizeY, &bpp, &channels, pImgData);
if (QHYCCD_SUCCESS == retVal) {
        printf("GetQHYCCDSingleFrame: %d x %d, bpp: %d, channels: %d, success.\n", roiSizeX, roiSizeY, bpp, channels);
        //process image here
} else {
        printf("GetQHYCCDSingleFrame failure, error: %d\n", retVal);
}

It seems as if the system never returns from GetQHYCCDSingleFrame. I tried it on ArmV8 and on a Ubuntu 16.04 on intel 64Bit.

Any ideas what went wrong?

blue skies Jan

qhyccd-lzr commented 6 years ago

I will check that, jan ---------- Původní e-mail ---------- Od: Jan Albiez notifications@github.com Komu: qhyccd-lzr/QHYCCD_Linux_New QHYCCD_Linux_New@noreply.github.com Datum: 6. 2. 2018 14:34:35 Předmět: [qhyccd-lzr/QHYCCD_Linux_New] Problems with QHY128C (#4) " Hoi!

I have a problem running the SingleFrameMode test application on Linux with a QHY 128C camera. It detects the camera but hangs when downloading the captured frame:

SingleFrameMode, Version: 1.00 2018-02-06 13:24:03.231 LOG_ALARM ----------------- log4z thread started! ---------------------------- 2018-02-06 13:24:03.232 LOG_ALARM logger id=0 key=Main name=SingleFrameMode path=/tmp/ level=1 display=1 SDK resources initialized. Number of QHYCCD cameras found: 1 Application connected to the following camera from the list: Index: 1, cameraID = QHY128C-f922d2428bc892e8c Open QHYCCD success. SetQHYCCDStreamMode set to: 0, success. 2018-02-06 13:24:03.284 LOG_FATAL qhy5iii128base.cpp (qhy5iii128base.cpp):184 InitQHYCCD success. GetQHYCCDOverScanArea: Overscan Area startX x startY : 0 x 0 Overscan Area sizeX x sizeY : 0 x 0 GetQHYCCDEffectiveArea: Effective Area startX x startY: 0 x 0 Effective Area sizeX x sizeY : 0 x 0 GetQHYCCDChipInfo: Effective Area startX x startY: 0 x 0 Chip size width x height : 36.150 x 24.380 [mm] Pixel size width x height : 5.970 x 5.970 [um] Image size width x height : 6056 x 4084 This is a color camera. SetQHYCCDParam CONTROL_USBTRAFFIC set to: 10, success. SetQHYCCDParam CONTROL_GAIN set to: 10, success SetQHYCCDParam CONTROL_OFFSET set to: 140, success. SetQHYCCDParam CONTROL_EXPOSURE set to: 20000, success. SetQHYCCDResolution roiStartX x roiStartY: 0 x 0 SetQHYCCDResolution roiSizeX x roiSizeY : 6056 x 4084 SetQHYCCDBinMode set to: binX: 1, binY: 1, success. SetQHYCCDParam CONTROL_TRANSFERBIT set to: 10, success. ExpQHYCCDSingleFrame(pCamHandle) - start... ExpQHYCCDSingleFrame(pCamHandle) - end... ExpQHYCCDSingleFrame success. Will try to allocate: 74198112 [uchar] for image data. Allocated memory for frame: 74198112 [uchar].

After some tests and a bit of poking around if located the problem within this block:

// get single frame retVal = GetQHYCCDSingleFrame(pCamHandle, &roiSizeX, &roiSizeY, &bpp, &channels, pImgData); if (QHYCCD_SUCCESS == retVal) { printf("GetQHYCCDSingleFrame: %d x %d, bpp: %d, channels: %d, success.\n", roiSizeX, roiSizeY, bpp, channels); //process image here } else { printf("GetQHYCCDSingleFrame failure, error: %d\n", retVal); }

It seems as if the system never returns from GetQHYCCDSingleFrame. I tried it on ArmV8 and on a Ubuntu 16.04 on intel 64Bit.

Any ideas what went wrong?

blue skies Jan

— 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/4), or mute the thread (https://github.com/notifications/unsubscribe-auth/AE-NVBqFcqD5DYCbJTXpQvzOT6Kmsswfks5tSFTlgaJpZM4R7DnH) .

"

qhyccd-lzr commented 6 years ago

I have asked colleagues in China to check that, because I have no such a camera in my stock. He promised to check it tomorrow. Jan

jbvoelker commented 6 years ago

I have the same problem with a QHY5II-M on Ubuntu 16.04 64 Bit. It occurs only if i set CONTROL_EXPOSURE to > 1000000 µs.

ExpQHYCCDSingleFrame() returns QHYCCD_READ_DIRECTLY almost immediately, independent of the exposure time. After that, GetQHYCCDExposureRemaining() returns 100, GetQHYCCDMemLength() returns the expected buffer size. The following call to GetQHYCCDSingleFrame() never returns.

Setting the log level to trace shows the following output: 2018-02-11 02:17:16.014 LOG_DEBUG BeginSingleExposure (qhy5iibase.cpp):307 2018-02-11 02:17:16.014 LOG_DEBUG ReSetParams2cam (qhy5iibase.cpp):128 2018-02-11 02:17:16.073 LOG_TRACE GetSingleFrame begin (qhy5iibase.cpp):374 2018-02-11 02:17:16.073 LOG_TRACE GetSingleFrame ret=-1 chipoutputsizex chipoutputsizey cambits / 8=1310720 (qhy5iibase.cpp):401

The two last lines repeat until I kill the application.

qhyccd-lzr commented 6 years ago

Hi, this looks strange. I am now testing QHY5II-L  with: Ubuntu16.04.3 LTS,  MATE Desktop 1.12.1, kernel 4.12.0-26-generic

I run TheSkyX and I do not see such problems. I can set exposure times over 1 second, currently 2.5 or 3.5 seconds and system takes images in loop without problems.

In any case, I will check the source code including our testapp,but difficult to say, where the problem is. I will keep you informed.

Thanks, Jan  

---------- Původní e-mail ---------- Od: Jannis_V notifications@github.com Komu: qhyccd-lzr/QHYCCD_Linux_New QHYCCD_Linux_New@noreply.github.com Datum: 11. 2. 2018 1:57:57 Předmět: Re: [qhyccd-lzr/QHYCCD_Linux_New] Problems with QHY128C (#4) " I have the same problem with a QHY5II-M on Ubuntu 16.04 64 Bit. It occurs only if i set CONTROL_EXPOSURE to > 1000000 µs.

ExpQHYCCDSingleFrame() returns QHYCCD_READ_DIRECTLY almost immediately, independent of the exposure time. After that, GetQHYCCDExposureRemaining() returns 100, GetQHYCCDMemLength() returns the expected buffer size. The following call to GetQHYCCDSingleFrame() never returns.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub (https://github.com/qhyccd-lzr/QHYCCD_Linux_New/issues/4#issuecomment-364709529) , or mute the thread (https://github.com/notifications/unsubscribe-auth/AE-NVKaJu9CHxT0uQSJM3hqSn2gl3E_Gks5tTjsSgaJpZM4R7DnH) .

"

jbvoelker commented 6 years ago

Hi Jan,

the problem only occurs with the libs from this repository.

I have just linked my application against libqhy_64.a from https://github.com/qhyccd-lzr/QHYCCD_Linux and it works great for exposures of up to 6 seconds. For longer exposures, the console gets spammed with _2018-02-11 13:04:37.973 LOG_FATAL LIBUSB_TRANSFER_TIMEDOUT (cmosdll.cpp):64 but I get valid images.

Regards, Jannis

qhyccd-lzr commented 6 years ago

so, if I understand you well, your app doesn't work if linked with a new library, but works well if linked with an older one, right ? ---------- Původní e-mail ---------- Od: Jannis_V notifications@github.com Komu: qhyccd-lzr/QHYCCD_Linux_New QHYCCD_Linux_New@noreply.github.com Datum: 11. 2. 2018 13:12:23 Předmět: Re: [qhyccd-lzr/QHYCCD_Linux_New] Problems with QHY128C (#4) " Hi Jan,

the problem only occurs with the libs from this repository.

I have just linked my application against libqhy_64.a from https://github. com/qhyccd-lzr/QHYCCD_Linux(https://github.com/qhyccd-lzr/QHYCCD_Linux) and it works great for exposures of up to 6 seconds. For longer exposures, the console gets spammed with 2018-02-11 13:04:37.973 LOG_FATAL LIBUSB_TRANSFER_TIMED_OUT (cmosdll.cpp):64 but I get valid images.

Regards, Jannis

— You are receiving this because you commented. Reply to this email directly, view it on GitHub (https://github.com/qhyccd-lzr/QHYCCD_Linux_New/issues/4#issuecomment-364746880) , or mute the thread (https://github.com/notifications/unsubscribe-auth/AE-NVCaeXgkl9LOZlu04zOMtLMJmdawLks5tTtkigaJpZM4R7DnH) .

"

jbvoelker commented 6 years ago

Yes, that's correct.

jakobs commented 6 years ago

Any updates on this issue?

qhyccd-lzr commented 6 years ago

Jokobs, sorry for my very late answer, I just received qhyccd 128 camera, so I will try to fix it this week. I will keep you informed. Jan

qhyccd-lzr commented 6 years ago

Jakobs, sorry for my misprints...

jakobs commented 6 years ago

Any luck with this? Could you replicate the problem?

qhyccd-lzr commented 6 years ago

I am working hard on rewriting sdk to support multiple cameras. This is priority I got from company. Hope to finish it during this week, then can look on those bugs. I am very sorry with this delay. Jan

---------- Původní e-mail ---------- Od: Jakob Schwendner notifications@github.com Komu: qhyccd-lzr/QHYCCD_Linux_New QHYCCD_Linux_New@noreply.github.com Datum: 21. 3. 2018 9:44:34 Předmět: Re: [qhyccd-lzr/QHYCCD_Linux_New] Problems with QHY128C (#4) " Any luck with this? Could you replicate the problem?

— You are receiving this because you commented. Reply to this email directly, view it on GitHub (https://github.com/qhyccd-lzr/QHYCCD_Linux_New/issues/4#issuecomment-374866806) , or mute the thread (https://github.com/notifications/unsubscribe-auth/AE-NVNJx73idS_CY8eXlVcDQCBaaasBlks5tghLmgaJpZM4R7DnH) .

"

AnWeNet commented 6 years ago

I am having the same issue with QHY183 mono, running on Ubuntu Mate.

Here is an output from syslog:

Jun 18 00:46:27 anwenet-desktop kernel: [ 48.985485] usb 1-1.3: new high-speed USB device number 4 using ehci-pci Jun 18 00:46:27 anwenet-desktop kernel: [ 49.095104] usb 1-1.3: New USB device found, idVendor=1618, idProduct=c183 Jun 18 00:46:27 anwenet-desktop kernel: [ 49.095111] usb 1-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3 Jun 18 00:46:27 anwenet-desktop kernel: [ 49.095115] usb 1-1.3: Product: WestBridge Jun 18 00:46:27 anwenet-desktop kernel: [ 49.095119] usb 1-1.3: Manufacturer: Cypress Jun 18 00:46:27 anwenet-desktop kernel: [ 49.095122] usb 1-1.3: SerialNumber: 0000000004BE Jun 18 00:46:27 anwenet-desktop mtp-probe: checking bus 1, device 4: "/sys/devices/pci0000:00/0000:00:1d.0/usb1/1-1/1-1.3" Jun 18 00:46:27 anwenet-desktop mtp-probe: bus: 1, device: 4 was not an MTP device Jun 18 00:46:27 anwenet-desktop systemd-udevd[2879]: Process '/sbin/fxload -t fx3 -I /usr/local/lib/qhy/firmware/QHY183.img -D /dev/bus/usb/001/004' failed with exit code 185. Jun 18 00:46:27 anwenet-desktop kernel: [ 49.167167] usb 1-1.3: usbfs: USBDEVFS_CONTROL failed cmd fxload rqt 64 rq 160 len 4096 ret -71 Jun 18 00:46:27 anwenet-desktop systemd-udevd[2879]: Process '/sbin/fxload -t fx3 -I /usr/local/lib/qhy/firmware/QHY183.img -D ' failed with exit code 255. Jun 18 00:46:27 anwenet-desktop upowerd[1780]: unhandled action 'bind' on /sys/devices/pci0000:00/0000:00:1d.0/usb1/1-1/1-1.3 Jun 18 00:46:28 anwenet-desktop kernel: [ 49.272939] usb 1-1.3: USB disconnect, device number 4 Jun 18 00:46:28 anwenet-desktop upowerd[1780]: unhandled action 'unbind' on /sys/devices/pci0000:00/0000:00:1d.0/usb1/1-1/1-1.3 Jun 18 00:46:28 anwenet-desktop kernel: [ 49.497321] usb 1-1.3: new high-speed USB device number 5 using ehci-pci Jun 18 00:46:28 anwenet-desktop kernel: [ 49.612991] usb 1-1.3: New USB device found, idVendor=1618, idProduct=c184 Jun 18 00:46:28 anwenet-desktop kernel: [ 49.612998] usb 1-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=0 Jun 18 00:46:28 anwenet-desktop kernel: [ 49.613002] usb 1-1.3: Product: Q183-Cool Jun 18 00:46:28 anwenet-desktop kernel: [ 49.613005] usb 1-1.3: Manufacturer: QHYCCD Jun 18 00:46:28 anwenet-desktop mtp-probe: checking bus 1, device 5: "/sys/devices/pci0000:00/0000:00:1d.0/usb1/1-1/1-1.3" Jun 18 00:46:28 anwenet-desktop mtp-probe: bus: 1, device: 5 was not an MTP device Jun 18 00:46:28 anwenet-desktop upowerd[1780]: unhandled action 'bind' on /sys/devices/pci0000:00/0000:00:1d.0/usb1/1-1/1-1.3

Here is output from ./SingleFrameMode SingleFrameMode, Version: 1.10 Press any key to start test application...

SDK resources initialized.

Idx: 1, OpenQHYCCD QHY183M-227bea45a63f9f4d6 success. SetQHYCCDStreamMode set to: 0, success. InitQHYCCD success. GetQHYCCDOverScanArea: Overscan Area startX x startY : 0 x 0 Overscan Area sizeX x sizeY : 0 x 0 GetQHYCCDEffectiveArea: Effective Area startX x startY: 0 x 0 Effective Area sizeX x sizeY : 0 x 0 GetQHYCCDChipInfo: Effective Area startX x startY: 0 x 0 Chip size width x height : 13.306 x 8.842 [mm] Pixel size width x height : 2.400 x 2.400 [um] Image size width x height : 5544 x 3684 This is a mono camera. SetQHYCCDParam CONTROL_USBTRAFFIC set to: 10, success. SetQHYCCDParam CONTROL_GAIN set to: 10, success SetQHYCCDParam CONTROL_OFFSET set to: 140, success. SetQHYCCDParam CONTROL_EXPOSURE [us] set to: 20000, success. SetQHYCCDResolution roiStartX x roiStartY : 0 x 0, success. SetQHYCCDResolution roiSizeX x roiSizeY : 5544 x 3684, success. SetQHYCCDBinMode set to: binX: 1, binY: 1, success. SetQHYCCDParam CONTROL_TRANSFERBIT set to: 10, success. ExpQHYCCDSingleFrame(pCamHandle) - start... ExpQHYCCDSingleFrame(pCamHandle) - end... ExpQHYCCDSingleFrame success. Will try to allocate 61272288 [uchar] data array for image. SetQHYCCDParam CONTROL_EXPOSURE set to: 20000 [us], success. Allocated data array of 61272288 [uchar].

Let me know if you need any more information. I would like to think I tried everything.

qhyccd-lzr commented 6 years ago

we are about releasing a new sdk driver, please wait, the driver is under tests.

This should work with longer exposure times with QHY18c cameras.

Jan

---------- Původní e-mail ---------- Od: AnWeNet notifications@github.com Komu: qhyccd-lzr/QHYCCD_Linux_New QHYCCD_Linux_New@noreply.github.com Datum: 18. 6. 2018 6:58:09 Předmět: Re: [qhyccd-lzr/QHYCCD_Linux_New] Problems with QHY128C (#4) " I am having the same issue with QHY183 mono, running on Ubuntu Mate.

Here is an output from syslog:

Jun 18 00:46:27 anwenet-desktop kernel: [ 48.985485] usb 1-1.3: new high- speed USB device number 4 using ehci-pci Jun 18 00:46:27 anwenet-desktop kernel: [ 49.095104] usb 1-1.3: New USB device found, idVendor=1618, idProduct=c183 Jun 18 00:46:27 anwenet-desktop kernel: [ 49.095111] usb 1-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3 Jun 18 00:46:27 anwenet-desktop kernel: [ 49.095115] usb 1-1.3: Product: WestBridge Jun 18 00:46:27 anwenet-desktop kernel: [ 49.095119] usb 1-1.3: Manufacturer: Cypress Jun 18 00:46:27 anwenet-desktop kernel: [ 49.095122] usb 1-1.3: SerialNumber: 0000000004BE Jun 18 00:46:27 anwenet-desktop mtp-probe: checking bus 1, device 4: "/sys/ devices/pci0000:00/0000:00:1d.0/usb1/1-1/1-1.3" Jun 18 00:46:27 anwenet-desktop mtp-probe: bus: 1, device: 4 was not an MTP device Jun 18 00:46:27 anwenet-desktop systemd-udevd[2879]: Process '/sbin/fxload - t fx3 -I /usr/local/lib/qhy/firmware/QHY183.img -D /dev/bus/usb/001/004' failed with exit code 185. Jun 18 00:46:27 anwenet-desktop kernel: [ 49.167167] usb 1-1.3: usbfs: USBDEVFS_CONTROL failed cmd fxload rqt 64 rq 160 len 4096 ret -71 Jun 18 00:46:27 anwenet-desktop systemd-udevd[2879]: Process '/sbin/fxload - t fx3 -I /usr/local/lib/qhy/firmware/QHY183.img -D ' failed with exit code 255. Jun 18 00:46:27 anwenet-desktop upowerd[1780]: unhandled action 'bind' on / sys/devices/pci0000:00/0000:00:1d.0/usb1/1-1/1-1.3 Jun 18 00:46:28 anwenet-desktop kernel: [ 49.272939] usb 1-1.3: USB disconnect, device number 4 Jun 18 00:46:28 anwenet-desktop upowerd[1780]: unhandled action 'unbind' on /sys/devices/pci0000:00/0000:00:1d.0/usb1/1-1/1-1.3 Jun 18 00:46:28 anwenet-desktop kernel: [ 49.497321] usb 1-1.3: new high- speed USB device number 5 using ehci-pci Jun 18 00:46:28 anwenet-desktop kernel: [ 49.612991] usb 1-1.3: New USB device found, idVendor=1618, idProduct=c184 Jun 18 00:46:28 anwenet-desktop kernel: [ 49.612998] usb 1-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=0 Jun 18 00:46:28 anwenet-desktop kernel: [ 49.613002] usb 1-1.3: Product: Q 183-Cool Jun 18 00:46:28 anwenet-desktop kernel: [ 49.613005] usb 1-1.3: Manufacturer: QHYCCD Jun 18 00:46:28 anwenet-desktop mtp-probe: checking bus 1, device 5: "/sys/ devices/pci0000:00/0000:00:1d.0/usb1/1-1/1-1.3" Jun 18 00:46:28 anwenet-desktop mtp-probe: bus: 1, device: 5 was not an MTP device Jun 18 00:46:28 anwenet-desktop upowerd[1780]: unhandled action 'bind' on / sys/devices/pci0000:00/0000:00:1d.0/usb1/1-1/1-1.3

Here is output from ./SingleFrameMode SingleFrameMode, Version: 1.10 Press any key to start test application...

SDK resources initialized.

Idx: 1, OpenQHYCCD QHY183M-227bea45a63f9f4d6 success. SetQHYCCDStreamMode set to: 0, success. InitQHYCCD success. GetQHYCCDOverScanArea: Overscan Area startX x startY : 0 x 0 Overscan Area sizeX x sizeY : 0 x 0 GetQHYCCDEffectiveArea: Effective Area startX x startY: 0 x 0 Effective Area sizeX x sizeY : 0 x 0 GetQHYCCDChipInfo: Effective Area startX x startY: 0 x 0 Chip size width x height : 13.306 x 8.842 [mm] Pixel size width x height : 2.400 x 2.400 [um] Image size width x height : 5544 x 3684 This is a mono camera. SetQHYCCDParam CONTROL_USBTRAFFIC set to: 10, success. SetQHYCCDParam CONTROL_GAIN set to: 10, success SetQHYCCDParam CONTROL_OFFSET set to: 140, success. SetQHYCCDParam CONTROL_EXPOSURE [us] set to: 20000, success. SetQHYCCDResolution roiStartX x roiStartY : 0 x 0, success. SetQHYCCDResolution roiSizeX x roiSizeY : 5544 x 3684, success. SetQHYCCDBinMode set to: binX: 1, binY: 1, success. SetQHYCCDParam CONTROL_TRANSFERBIT set to: 10, success. ExpQHYCCDSingleFrame(pCamHandle) - start... ExpQHYCCDSingleFrame(pCamHandle) - end... ExpQHYCCDSingleFrame success. Will try to allocate 61272288 [uchar] data array for image. SetQHYCCDParam CONTROL_EXPOSURE set to: 20000 [us], success. Allocated data array of 61272288 [uchar].

Let me know if you need any more information. I would like to think I tried everything.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub (https://github.com/qhyccd-lzr/QHYCCD_Linux_New/issues/4#issuecomment-397942118) , or mute the thread (https://github.com/notifications/unsubscribe-auth/AE-NVJRcU7fIfne4Jb5jYY6lIxE8N7ttks5t9zNbgaJpZM4R7DnH) . "

jakobs commented 5 years ago

Any update on this issue?

qhyccd-lzr commented 5 years ago

Jakob, all drivers and other stuff are developed directly in QHYCCD company in China, you can download their drivers from: https://www.qhyccd.com/index.php?m=content&c=index&a=lists&catid=127

Contact person of those drivers is : Davis Miao, Email: myq@qhyccd.com Regards, Jan