MORELLI replied to the topic 'QHY Driver: Testing required' in the forum. 1 week ago

It seems that 3.4.0 version of Kstars olves well this issue.

Read More...

MORELLI replied to the topic 'QHY Driver: Testing required' in the forum. 1 week ago

Hello,

I have the same problem with my QHY 183C. Into the Control Panel it is not possible to setup a temperature to focus. Into the Capture tab, the temperature reached is that of the control panel. But I can't change it.

Read More...

MORELLI replied to the topic 'Camera not detected on TinkerBoard' in the forum. 2 weeks ago

No way. On the TB, Kstars is 3.4.0 version. I use a powered usb3 hub.

Read More...

MORELLI created a new topic ' Camera not detected on TinkerBoard' in the forum. 2 weeks ago

Hello,

I use à Tinkerboard in order to manage my device by remote on my laptop. The connection between the laptop and the TB is OK. I create a profil on TB Kstars with Telescope Simulator and QHY CCD.
The QHY 224C (and QHY 183C) are not detected. The message is "No QHY camera detected. Power on?". I use an USB3 hub powered.

A solution ?

Read More...

MORELLI created a new topic ' After QHY183C issue solved, issue now with Canon 1000D' in the forum. 2 weeks ago

Hello,

I used recently, before the issue wtih my QHY183C, a Canon 1000D. I try to test it today and It doesn't work. I cannot take a capture with these messages into the control panel:

020-02-08T09:36:57: [ERROR] Exposure failed to save image... Unspecified error
2020-02-08T09:36:57: [WARNING] Could not wait for event.
2020-02-08T09:36:57: [WARNING] Could not wait for event.
2020-02-08T09:36:57: [WARNING] Could not wait for event.
2020-02-08T09:36:57: [WARNING] Could not wait for event.
2020-02-08T09:36:57: [WARNING] Could not wait for event.
2020-02-08T09:36:57: [WARNING] Could not wait for event.
2020-02-08T09:36:57: [WARNING] Could not wait for event.
2020-02-08T09:36:57: [WARNING] Could not wait for event.
2020-02-08T09:36:57: [WARNING] Could not wait for event.
2020-02-08T09:36:57: [WARNING] Could not wait for event.
2020-02-08T09:36:56: [INFO] Starting 0.5 seconds exposure.
2020-02-08T09:36:56: [ERROR] Exposure failed to save image... Unspecified error
2020-02-08T09:36:56: [WARNING] Could not wait for event.
2020-02-08T09:36:56: [WARNING] Could not wait for event.
2020-02-08T09:36:56: [WARNING] Could not wait for event.
2020-02-08T09:36:56: [WARNING] Could not wait for event.
2020-02-08T09:36:56: [WARNING] Could not wait for event.
2020-02-08T09:36:56: [WARNING] Could not wait for event.
2020-02-08T09:36:56: [WARNING] Could not wait for event.
2020-02-08T09:36:56: [WARNING] Could not wait for event.
2020-02-08T09:36:56: [WARNING] Could not wait for event.
2020-02-08T09:36:52: [INFO] Starting 0.5 seconds exposure.

I have re installed the driver indi-gphoto and libgphoto2 is installed.

File Attachment:

File Name: log_10-33-38.txt
File Size: 132 KB


Read More...

MORELLI replied to the topic 'Indi and QHY 183C' in the forum. 3 weeks ago

ALELUIA ! It runs ! I installed the SDK as you say. Thank you very very very much. I can keep my computer with its real 10-hour battery life !

Robert MORELLI
France

Read More...

MORELLI replied to the topic 'Indi and QHY 183C' in the forum. 3 weeks ago

Thank you for your message. I try as su, but no way. At the connection I have a windows with the message "Indi driver crashed , Continue - No".
I had installed the last skf from QHY website. Now the driver crashed every time. I try to come back to the previous one.

Read More...

MORELLI replied to the topic 'Indi and QHY 183C' in the forum. 3 weeks ago

Hi Jasem,

thank for your help. Could you be more specific about your answer please ? What should I do ?

Read More...

MORELLI replied to the topic 'Indi and QHY 183C' in the forum. 3 weeks ago

One day later. I install an Indigo server. With Kstars, no change, same issue. But the camera runs perfectly with the Indigo Control Panel ????????

I am feeling a little bit alone. Help Jasem !

Read More...

MORELLI replied to the topic 'Indi and QHY 183C' in the forum. 3 weeks ago

Finaly, the issue is caused by the power of the USB port not enought on this laptop and others. I try the camera with the laptop newer than mine and the result was the same.
So I bought this afternoon an usb3 hub powered 2A, and the camera becames a c184 type.
It runs well with Firecapture. With Kstars I have the connection. I can modify the parameter panel. But it fails to capture an image. Not enought power ? I'll send next the log. I am not at home.
I am more relax than the last days :)

Read More...

MORELLI replied to the topic 'Indi and QHY 183C' in the forum. 3 weeks ago

I'm continuing my investigations. I installed a Win10 on my laptop, broadcast driver wdm, ascom driver and system driver.
EZCAP seems to runs.
Firecapture recognises the camera but do anything.
Sharpcap runs with the ascom driver, slowly.

It seems to be an OS problem of Ubuntu. I don't know how to do.

Read More...

MORELLI replied to the topic 'Indi and QHY 183C' in the forum. 4 weeks ago

No, it's not working. The camera is recognized but always with error:

robert@robert-PORTEGE:~lsusb -s 003:003 -v

Bus 003 Device 003: ID 1618:c183 Cypress WestBridge
Couldn't open device, some information will be missing
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 0
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 64
idVendor 0x1618
idProduct 0xc183
bcdDevice 1.00
iManufacturer 1
iProduct 2
iSerial 3
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 0x0012
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0x80
(Bus Powered)
MaxPower 200mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 0
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 0
bInterfaceProtocol 0
iInterface 0 lsusb -s 003:003 -v

Bus 003 Device 003: ID 1618:c183 Cypress WestBridge
Couldn't open device, some information will be missing
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 0
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 64
idVendor 0x1618
idProduct 0xc183
bcdDevice 1.00
iManufacturer 1
iProduct 2
iSerial 3
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 0x0012
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0x80
(Bus Powered)
MaxPower 200mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 0
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 0
bInterfaceProtocol 0
iInterface 0
robert@robert-PORTEGE:~$
robert@robert-PORTEGE:~$

Read More...

MORELLI replied to the topic 'Indi and QHY 183C' in the forum. 4 weeks ago

I think I find a solution either the solution. I launch a live Ubuntu 19.10. The camera is well recognized into a terminal. I am installing this version . And I'm keeping my fingers crossed.

Read More...

MORELLI replied to the topic 'Indi and QHY 183C' in the forum. 4 weeks ago

I think it is a problem with the laptop. It recognizes badly the camera, instead the 224C is correctly recognized.

robert@robert-PORTEGE:~$ lsusb -s 003:002 -v (ligne spécifique de la caméra)

Bus 003 Device 002: ID 1618:c183
Couldn't open device, some information will be missing
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 64
idVendor 0x1618
idProduct 0xc183
bcdDevice 1.00
iManufacturer 1
iProduct 2
iSerial 3
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 18
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0x80
(Bus Powered)
MaxPower 200mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 0
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 0
bInterfaceProtocol 0
iInterface 0
robert@robert-PORTEGE:~$

Read More...

MORELLI replied to the topic 'Indi and QHY 183C' in the forum. 4 weeks ago

I run Ubuntu-Mate 18.04.03 LTS, on the laptop and the desktop.

File Attachment:

File Name: log_13-29-35.txt
File Size: 31 KB

I check the Portege has 2 USB 3.0.

The command lsusb gives:

robert@robert-PORTEGE:~$ lsusb
Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 003: ID 04f2:b369 Chicony Electronics Co., Ltd
Bus 001 Device 004: ID 8087:07da Intel Corp.
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 002: ID 1618:c183
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
robert@robert-PORTEGE:~$

Read More...