×

INDI Library v2.0.6 is Released (02 Feb 2024)

Bi-monthly release with minor bug fixes and improvements

QHY163M disconnect INDI

  • Posts: 112
  • Thank you received: 6
Thanks Dan. Hoping to help someone out that may want to try this cam out in INDI. I really love the camera, very high quality build.

Knro:
github.com/qhyccd-lzr/QHYCCD_Linux_New

I'll give it a shot and see if it works.

Cheers
Last edit: 6 years 3 months ago by David Rankin.
6 years 3 months ago #21682

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

Do not use anything directly from QHY. Just use the INDI QHY driver and it includes the latest supported SDK.
6 years 3 months ago #21683

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

  • Posts: 112
  • Thank you received: 6
Okay, what command would I use to update just that INDI driver? Do I just overwrite a file?
6 years 3 months ago #21684

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

I presume you're using the PPA? just run the software update and install the updates.
6 years 3 months ago #21685

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

  • Posts: 112
  • Thank you received: 6
Nope, I just followed their instructions and ran the sudo ./linux_install_qhyccd_sdk_driver.sh. they provided.

Sorry, I'm still a bit new to the whole linux thing. ;)
6 years 3 months ago #21688

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

How did you install KStars & INDI in the first place? using what method? on what OS?
6 years 3 months ago #21690

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

  • Posts: 112
  • Thank you received: 6
Client is a Raspberry PI3 running Ubuntu Mate
Kstars is on a PC running Windows 10
I installed INDI using terminal apt-get commands
6 years 3 months ago #21691

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

yeah the same command to update:
sudo apt-get update && sudo apt-get -y dist-upgrade
6 years 3 months ago #21692

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

  • Posts: 112
  • Thank you received: 6
Okay, that must be my confusion here. I can run that command and it will go out and get the new QHY driver automatically?

I'm guessing by this line that the answer is yes:
Setting up indi-qhy (1.7+r3651~201712161157~ubuntu16.04.1) ...
Last edit: 6 years 3 months ago by David Rankin.
6 years 3 months ago #21693

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

  • Posts: 112
  • Thank you received: 6
Okay, few things I'm noticing right off the bat.
1. The camera connected way faster
2. The cooler was not reporting often before, and sometimes at all. I would set the temperature and it wouldn't update the values in the driver until an image was shot. Now it is updating live temperature value and power%

Test 1: I'm going to run will be over Wifi using the USB2 cable at USB Traffic 0.
Test 2: will be over Wifi using USB3 and USB Traffic of 40.

Update on test 1: This looks very promising. I was able to run a continuous exposure for 5 minutes, stop that, cool the camera, shoot a 40 image sequence, then go back and run a continuous exposure. This sequence of events would always crash it before.

I think a major part of the issue here is what I suspected before. The shoddy wifi performance of the RP3. This is well documented online. It was running great then my kids turned on their xbox. I did a firmware update, and also disabled the power management on it. No changes. Here are the ping times between the PR3 and my router - ridiculously slow and even dropping packets:

64 bytes from 192.168.1.1: icmp_seq=11 ttl=64 time=118 ms
64 bytes from 192.168.1.1: icmp_seq=12 ttl=64 time=1373 ms
64 bytes from 192.168.1.1: icmp_seq=13 ttl=64 time=365 ms
64 bytes from 192.168.1.1: icmp_seq=14 ttl=64 time=146 ms
64 bytes from 192.168.1.1: icmp_seq=15 ttl=64 time=25.3 ms
64 bytes from 192.168.1.1: icmp_seq=16 ttl=64 time=616 ms
64 bytes from 192.168.1.1: icmp_seq=17 ttl=64 time=236 ms
64 bytes from 192.168.1.1: icmp_seq=18 ttl=64 time=96.3 ms
64 bytes from 192.168.1.1: icmp_seq=19 ttl=64 time=446 ms
64 bytes from 192.168.1.1: icmp_seq=20 ttl=64 time=1677 ms
64 bytes from 192.168.1.1: icmp_seq=21 ttl=64 time=606 ms
64 bytes from 192.168.1.1: icmp_seq=22 ttl=64 time=510 ms
64 bytes from 192.168.1.1: icmp_seq=23 ttl=64 time=1041 ms
64 bytes from 192.168.1.1: icmp_seq=24 ttl=64 time=19.4 ms
64 bytes from 192.168.1.1: icmp_seq=25 ttl=64 time=21.7 ms
64 bytes from 192.168.1.1: icmp_seq=26 ttl=64 time=46.3 ms
64 bytes from 192.168.1.1: icmp_seq=27 ttl=64 time=172 ms
64 bytes from 192.168.1.1: icmp_seq=28 ttl=64 time=498 ms
64 bytes from 192.168.1.1: icmp_seq=29 ttl=64 time=8.34 ms

No question the new driver seems a lot more stable, but it will be hard to learn anything running tests over Wifi with the connection so bad. I'll be buying a higher quality USB wifi dongle for it to see if that helps.

Update:

So I had a cable matters wifi dongle sitting around. I plugged it into the RP3 and it was supported by default. I used it to connect to my network with other devices (xbox, computer, ect) also streaming data. The connection to the RP3 was much more solid using the USB dongle, consistent 4ms ping times to my router. I guess that is a lesson learned as well.

Test 2 using the USB dongle - USB Traffic set to 40, USB3
Similar results as test 1, solid performance.

Thanks to QHY for updating the drivers. Here are the lessons learned:

1. Use recent driver.
2. Use high quality USB hardware.
3. Don't use the RP3 internal Wifi - get a dongle or run ethernet.

Seems this setup is good to go.
Last edit: 6 years 3 months ago by David Rankin.
6 years 3 months ago #21694

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

  • Posts: 112
  • Thank you received: 6
Well, I spoke too soon. Had another disconnect tonight. It always seems to happen while trying to focus running "continuous exposure", it says it captured image but nothing ever shows up and the camera completely stops responding.

I have to assume at this point that it is definitely how the data is being sent over Wifi as it worked perfectly over an ethernet connection. Going to just have to run a permanent ethernet cable out to the scope.

Update:

Well, two more disconnects / freezes. Seems to be no improvement running over Wifi at all. The only time I've gotten the camera to function reliably with INDI is over ethernet.

Cheers,
Last edit: 6 years 3 months ago by David Rankin.
6 years 3 months ago #21719

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

  • Posts: 51
  • Thank you received: 12

Replied by Jeff Wilson on topic QHY163M disconnect INDI

Hmmm... I ran this, and I now cannot connect to my QHY5III-185C. dmesg is showing that a Cypress chip is now being found instead of Titan, suggesting that fxload isn't being correctly called. Do you know what has changed?
lsusb gives:
Bus 001 Device 008: ID 1618:0185
Manually trying to run the command in 85-qhy.rules:
$ sudo /usr/bin/fxload-libusb -t fx3 -I /lib/firmware/qhy/QHY5III185.img -D /dev/bus/usb/001/008
/usr/bin/fxload-libusb: invalid option -- 'D'
Instead, I need to run:
sudo /usr/bin/fxload-libusb -t fx3 -I /lib/firmware/qhy/QHY5III185.img -p 001,008
And now the Titan interface shows up.

So, fxload-libusb doesn't seem to like the way QHY has setup their udev rules file. More accurately, fxload-libusb isn't respecting the same arguments as fxload.

SDK 1.07 was apparently released today too.
The following user(s) said Thank You: Jasem Mutlaq
6 years 3 months ago #21750

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

Time to create page: 0.299 seconds