Thank you Jasem, if I can help with testing just let me know
Yesterday night we finally had a clear night but I could not capture any photos. After updating to KStars 3.4.1 I unfortunately did not test if my equipment work properly before going out, big mistake.
Immediately after starting INDI the indi_qhy_ccd driver crashed.
Neither the main camera (QHY376C) not the guide camera (QHY 5L-II) could be connected. The log file which I attach shows the message "INDI driver "indi_qhy_ccd" crashed!", log level was set to verbose.
There is also a message "Driver indi_qhy_ccd: dyld: Library not loaded: @rpath/libqhyccd.6.dylib"" which could point to a problem, but I could not resolve this.
Is there something missing in my installation?
Thank you for your help
I'm using Stars/Ekos/INDI 3.3.9 on an MacBook Pro 16" with Catalina installed. I run everything connected locally to the MacBook. Having started to use Stars/Ekos/INDi since last November I don't consider myself as an expert yet but all I can say, this is a masterpiece of a software. I had some crashes with plate solving and polar alignment but after a lot of trial and error with the settings and Phyton issues it runs perfectly. With version 3.3.4 the hassle with Phyton on the Mac should be solved but I didn't try it yet.
There are some issues with modal windows (a disables window can sometimes cover the active enabled window but it is not possible to access the active window) and then I have to kill KStars.
Summarized: having all devices controlled with one integrated software that supports the workflow of astro-photography so well: I consider this as a masterpiece and I'm quite tolerant for minor issues. Also the support by the developers and the folks in this forum is great.
Reading about these strange behaviors that you have with your camera I would also recommend you to try another USB cable.
See a topic that I opened after struggling with strange and not reproducible problems with my camera ( Thread ).
I could get rid of the problem with a new USB cable. I don't want to do marketing for the brand of this USB cables but they are outstanding, already when you plug the cable you can feel that they are much more solid and my camera now works reliable and without problems.
Just for the case that someone else has the same problem as I reported, I found the solution.
The camera showed different and not reproducible behaviours. Sometimes it didn't connect to INDI, sometimes the downloaded frames were pure white, sometimes the frames were not downloading at all.
I bought high quality USB cables from tether tools and now all the problems are gone. It seems like my problems were all because of the USB cables that were included with the camera.
have a nice day
I'm still trying to connect the FocusLynx to INDI.
Reading the thread "Serial timeout with Moonlite Focuser" Thread gave me hopes as in this thread a solution was published to successfully connect a FTDI USB/Serial focuser. Its not the same focuser as the FocusLynx but I tired to do the same as published there (installing the older version of the FTDI driver).
Unfortunately no success, still the "TTY timeout" message.
I can confirm that the driver is successfully loaded in macOS, the system report of the extensions confirmed this. The USB/Serial port is visible and available and INDI can also see the port, but cannot establish a connection.
Maybe this helps a bit in isolating the problem.
Except for the "pester them" (a human does it's best when he is motivated and not when he is pestered) I agree with you.
The problem we are facing is most probably a problem of the Mac itself and therefore the possibilities for support from this forum is limited.
I'd like to ask another question here.
The FocusLynx can also be connected with an ethernet connection. I tried this but cannot make a successful connection. Can anybody quickly explain me what the "ethernet connection mode" in Indi's Focusser tab means? I start Ekos with the "local mode". Does this not mean that all devices it manages are connected locally and directly to my Mac? But Indi expects an IP and a port for a ethernet connection which seems to me like being a remote connection. I entered my Mac's IP address and Indi's port but the connection didn't succeed. I'm using a normal ethernet cable without a router and hook FocusLynx to the Mac directly.
Shouldn't it be possible to connect FocusLynx with ethernet to a local mode Ekos/Indi service?
A good day to everybody
I'm having the very same problem as you reported.
Have you found the solution for your problem, I'd be glad if you could post it here, if you solved it.
I have the following devices connected to my MacBook Pro (with macOS Catalina):
- Astro-Physics Mount connected to INDI (USB-Serial)
- Focuslynx connected to INDI (USB-Serial)
- QHY367C connected to INDI (USB)
- QHY5-IIL connected to INDO (USB)
All devices are connected to two USB hubs which are connected to the Mac's Team Thunderbolt 3 connectors.
Starting Ekos is fine but then connecting the devices is always a bit of a lottery. The mount mostly is connected immediately, the focuser doesn't connect since a few days (but this is not the problem of this topic), the QHY5II-L connects mostly without problems, but the QHY367C makes problems. I usually have to disconnect the devices, restart Ekos and connect again. In 1 out of 10 tries, the QHY367C is connecting successfully.
I did not find a pattern to connected the QHY367C correctly. I assume it is a matter of where the camera is connected (on which USB Hub, with which other devices on the same hub), but as said, I didn't find a pattern yet.
The last two nights I have run into a new problem. Besides the usual connection problems, I cannot download anymore frames from the QHY367C. I took a 1s frame, the remaining exposure time field counted down to zero, the spinner next to the remaining exposure time doesn't stop spinning and the frame is not downloading. The FITS viewer never opens.
In the attached log file you see the log entries for the QHY367C. Theres is a message "Exposure timeout. Restarting exposure..." which points to the problem but I have no idea what creates the problem and how to solve it.
I noticed that as soon as I unplug the USB cable from the QHY376C, the FITS viewer opens immediately and the frame is displayed.
Does someone else has a similar problem and found a solution for it?
Jasem, I found out what was wrong - or better I found who made the mistake.
I made a mistake that shouldn't occur for someone who is doing astro photography since 20 years, but I did. I started the guiding calibration with the scope still on Polaris...
Now it works smoothly and correct.
Thank you very much for your support and sorry for my mistake.
I will try this tonight, also to connect with the experimental driver.
Do you tend more towards a problem with the mount itself than to a problem with software?
No, I try try this, but I will do it tonight.
What I did is moving the mound with the direction buttons in the manual guide module in PHD2. These buttons send a pulse command and the mount actually moves. The implementation of the lx200AP driver limits the pulse length to 999ms but I could see the coordinates change when I clicked to any of the direction buttons. The move was very small but I could see (and hear) that the mount moves.
Are these buttons in PHD doing the same as the direction buttons in INDI's guide tab?
I tried it once or twice to connect with the experimental, but I remember that I was not able to connect my mount (but I don't remember the log messages anymore).
As far as I know, I should not use the experimental driver with my mount with the CP3 controller. Is this wrong? My controller is more than 10 years old...