×

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
It seems like the last update has made this issue worse. Last night I had 2 disconnects. I updated INDI before starting tonight and I'm up over 10 now.

The issue does seem to be when the image is captured. It finishes the exposure but the image never writes when a crash happens.
6 years 1 month ago #23372

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

I just took 30x10s images from QHY 168C on StellarMate (RPI3) from my PC and it went without a hitch. Only problem I saw is that if you disconnect, you cannot reconnect. I will try to investigate this issue in the QHY SDK.
6 years 1 month ago #23388

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

I just took 30x10s images from QHY 168C on StellarMate (RPI3) from my PC and it went without a hitch. Only problem I saw is that if you disconnect, you cannot reconnect. I will try to investigate this issue in the QHY SDK.
6 years 1 month ago #23389

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

When my 163M drops from the RPi3, you have to unplug and replug the usb cable and relaunch Indi in order for Indi to see it again. I was having this problem fairly regularly with the Focus module, possibly because my manual focusing takes a while.

I wonder if a watchdog could be put in place? Something that could watch for a lost connection and then reinitialize?

Still, the 168 is a larger sensor, so it would be throwing more data over the bus. @knro, are you connected wirelessly to the RPi?

Regarding the Rock64, there is a thread here about that. So far, I have not encountered a disconnect. However, the available Linux distributions are not up to RPi standards. I’m working through a routing issue with having WiFi and eth0 at the same time. Also, full images transfer slower across the usb3 than RPi’s usb2, 10s vs 7s, but I’ll take that over instability. Another variable, since the Rock64 only has 3usb, I am using a powered hub. I hadn’t tried a powered hub on my RPi.
6 years 1 month ago #23392

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

I'll try to provide more clarity. Here I have the QHY163M setup to focus on an artificial star in my office.

It goes for a while, but then stops capturing. You can see that 35 frames have passed since starting at 10:10:43, but it is now after 10:13. I then click Stop to halt the focus module, and I go to the Imaging module. I try a 1s preview image.

You can see that while the capture began at 10:13:38, it is now 10:15 and no image has been received. Checking to see if the camera is still connected...

... shows that the 163 (properly identified as c164) is still present according to lsusb. I then tell Ekos to disconnect, stop Indi, and restart Indi.

Unfortunately, Indi no longer finds the camera.

This is how the problem manifests for me. I don't know if it is similar or different for rankinstudio.
6 years 1 month ago #23396
Attachments:

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

  • Posts: 112
  • Thank you received: 6
colgs3b,

If you read through the previous pages, you'll see an insane amount of different test and configurations I've tried. Nothing has solved the issue. When mine fails, just rebooting the RP3 gets it back up again. Can you post the link to the Rock64 thread? I'm desperate to get this working and running out of patience. And yes, the way yours is failing with the RP3 sounds like the exact same issue I'm having. The only way I found some sort of stability was to not use autofocus at all. It fails every time when I use it. From there, I have it hard wired to my router, using a USB2 cable directly into the RP3, and all other equipment is on a 3a powered USB hub. I was getting through a good part of the night without a crash that way, 1 to 2 crashes a night. After the last update, I gave up last night after 10 crashes.

Definitely going to give the Rock64 a try.

Cheers
6 years 1 month ago #23398

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

Here is the Rock64 thread:
indilib.org/forum/embedded-indi/2762-ind...ct.html?limitstart=0
A few people are trying Odroid-xu4 SBCs too.
The following user(s) said Thank You: David Rankin
6 years 1 month ago #23402

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

  • Posts: 112
  • Thank you received: 6
colgs3b

One thing you might try is writing your images to the Rock64 and using FTP to get them. I found that is way faster than the INDI transfer, at least for the 163M. Downloads are 1-2 seconds.
6 years 1 month ago #23403

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

Yes, I leave the images on my Pi and then copy them over.

Bad news. After about 10 successful test runs with the Rock64, this evening it too failed while framing. Previously I had no issues for many minutes. Tonight, the 163M disconnected from Indi in 25s. So, the USB3 bus might not be as big of an issue as I thought.

knro, please let me know how I can help figure this out. I've played with the QHY SDK in the past, and I got a basic PNG imager built.
6 years 1 month ago #23416

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

  • Posts: 112
  • Thank you received: 6
Thats disheartening. I ordered a Rock64 yesterday. Maybe it'll work more reliably anyway...
6 years 1 month ago #23417

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

  • Posts: 112
  • Thank you received: 6
Messing with the Rock64 (4gb).
It definitely didn't like the usb wifi dongle plugged in to it while indi was running. Moved it to powered USB hub.
Updated everything, running latest Kstars ect.

Seems to have been an improvement, not sure if that was reflected as a change in the drivers / software or the better performance of the Rock64.

I still have the cam ran USB2 directly to the Rock64. Saving images to the Rock64 instead of trying to transfer them via indi / Kstars.

I was able to get 80 x 40sec subs in a row without issue. Haven't tried autofocus yet.
Last edit: 6 years 2 weeks ago by David Rankin.
6 years 2 weeks ago #24034

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

  • Posts: 112
  • Thank you received: 6
Just to further this up. I ran a few sequences last night using the Rock64 without issue. I was able to run live view ect. I still opted to save images directly to the rock and ftp them over, and did focusing manually using the controls available in the focusing window. Typically using any of the live view features would crash it. Also ran over a wifi dongle, no hard wire.

I was able to use ekos scheduler running plate solves between many different locations in a short time without issue. No disconnects at all. I'm guessing the Rock64 is more suited to run the QHY163M.
The following user(s) said Thank You: Jasem Mutlaq
Last edit: 6 years 2 weeks ago by David Rankin.
6 years 2 weeks ago #24111

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

Time to create page: 0.331 seconds