×

INDI Library v1.9.6 Released (21 May 2022)

Bi-monthly INDI Library released with new drivers and bug fixes.

Omegon Pro / Touptek drivers

Well, I can't replicate exactly that but I have serial devices connected to StellarMate and still no issues. Try to swap ports, or check power supply. (now running 35 mins with 5 devices connected to StellarMate and still no timeouts)
Jasem Mutlaq
Support INDI & Ekos; Get StellarMate Astrophotography Gadget.
How to Submit Logs when you have problems?
Add your observatory info
11 months 3 weeks ago #73103

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

  • Posts: 12
  • Thank you received: 3
I tried all of that over the course of a couple of months. Different USB-cables, different powered hubs, non-powered hubs, exactly the same behaviour running kstars natively on my macbook pro and on Linux Ubuntu virtual machine on my HP-laptop. But everytime I get the same results. So I'm pretty out of options by now. The only thing left to do I if there's no solution for this is to get a new guide camera maybe. Any suggestions on what is a good reliable option?
11 months 3 weeks ago #73106

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

  • Posts: 165
  • Thank you received: 15

Reading that, I would bet that something is going on with the mount or the mount driver.

Something odd, but my troubleshooting steps would be :

1. Run PHD2 and connect only the cam, not the mount. Do you still have time outs?

2. I would create a fresh SD card with Astroberry or with AstroPi3 script, and run try again with the mount connected. Do you still have time outs?


Sent from my iPad using Tapatalk
11 months 3 weeks ago #73205

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

  • Posts: 2
  • Thank you received: 3
I've had a very similar issue recently. I was able to debug it and prepare a fix. It has been merged to master today. Can you confirm that it fixes things for you, too?
The following user(s) said Thank You: Hartmut
1 month 3 weeks ago #82767

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

  • Posts: 12
  • Thank you received: 3
It's been a long while since I used my Stellarmate but I will defenitely give it a go once the new INDI-lib version comes out and I'll let you know how it went.
The following user(s) said Thank You: Wiktor Latanowicz, Hartmut
1 month 2 weeks ago #82788

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

  • Posts: 29
  • Thank you received: 3
May I ask a question related to this problem?

I'm using a veTEC533c with Astroberry & Stellarmate via RPi4 USB3 port.
Additionally I'm using a ZWO ASI120MC-S connected via USB-3 cable to the veTEC USB-2.0 HUB.
The veTEC is powered by external 12V.

This works great and as expected using the internal Guider, not PHD2.
Now I want to exchange the ASI120MC-S by a veTEC GUIDE 2000M (has an USB2.0 Port).

Could the above stated problem also occure if using the "Internal Guider" or is is only related to the usage of PHD2?

Cheers
Hardy
1 month 2 weeks ago #82813

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

  • Posts: 2
  • Thank you received: 3
The bug that I fixed was in the driver. Session management software doesn't matter until it connects to the indi server. And it didn't matter if the camera was used for guiding or main expositions.

Long story short: the driver didn't wait long enough (sometimes didn't wait at all) for the camera to finish the exposition.
The following user(s) said Thank You: Hartmut, max
1 month 2 weeks ago #82817

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

  • Posts: 12
  • Thank you received: 3
I too have the Omegon Guide 2000M and the problem is the same in PHD2 as in the internal guider. I have the same problem on my MacBook Pro with the Omegon camera. Only under Windows and the ASCOM driver does the guide camera performs reliably.
The following user(s) said Thank You: Hartmut
1 month 2 weeks ago #82818

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

  • Posts: 165
  • Thank you received: 15
It is really interesting cause I’ve never seen this issue, at least with internal guider.

I have my Omegon 533 connected directly with a USB 3.0 cable to my mini pc. The Omegon 1200b M connected to 533’s usb hub. I have selected Omegon Pro as driver in CCD and Guider tab into Indi.

Here is the setup astrob.in/rdxygc/0/

The only difference between our guide cameras are the MPixels and bit depth. Is it possible the extra “weight” of your files to cause that? Have you tried setting the camera to 8bit?
1 month 2 weeks ago #82824

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

  • Posts: 29
  • Thank you received: 3
I'm a little bit afraid if the problem will occure or not...

Would be great if the final solution will be part of INDI 1.9.6. Unfortunately for Astroberry this packet will be updated 2-3 weeks after Stellarmate.
So I will wait before buying the camera. and hopefully we will see the solution in the release-note..
1 month 2 weeks ago #82837

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

  • Posts: 12
  • Thank you received: 3
Yes, I have tried the camera in 8 and 16 bit mode and even with binning 2 and 3 the issue occurs. As well in in Stellarmate internal guiding as in PHD2
1 month 2 weeks ago #82840

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

In StellarMate you can try the latest changes either by switching to Beta channel or running the following commands in the terminal:
update_indi_core
update_indi_drivers
Jasem Mutlaq
Support INDI & Ekos; Get StellarMate Astrophotography Gadget.
How to Submit Logs when you have problems?
Add your observatory info
The following user(s) said Thank You: Hartmut
Last edit: 1 month 2 weeks ago by Jasem Mutlaq.
1 month 2 weeks ago #82845

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

Time to create page: 0.711 seconds