On my Mac (Mac mini 2018, Mojave), the QHY driver crashes as soon as it is loaded. This is on version 3.5.7-Beta.
On other Macs, that have 3.5.5 and 3.5.7 beta installed, QHY driver works fine. I cannot find a 3.5.5 image anywhere.
The link on the official download page only shows a beta version. (it says 3.5.6 beta, but installs 3.5.7 beta).
Does anyone have an idea what could be wrong here and how this could be fixed? On Mac we don't have to worry about SDK's, right?
So the 3.5.7 beta is really supposed to be 3.5.6 (hopefully stable) as I mentioned in the other thread. They changed the version number to "3.5.7 beta" before I got finished getting the Mac build done.
But it sounds like your issue here is not related to the Mac build specifically, but is related to QHY in general. No, you don't have to install the SDK on your computer. Jasem does that and uses it to build the dynamic library that I used to build the Mac INDI drivers. The drivers are all inside the KStars app bundle. If there is an issue with it, hopefully it can be addressed and when it gets fixed, then I can rebuild the Mac version for you.
Thank you for clarifying the version-issue. Yes, I remember reading in another thread that something had gone wrong with the numbering. So I should assume I have the proper 3.5.6 installed then. Agreed, it seems then an issue with QHY in general, further proven with the same issue on the Ubuntu computer on (the real) 3.5.7beta. That's the nightly build I had to install to test a new mount driver.
@Jasem, would you have an idea what could cause this QHY issue under the latest version(s)?
On Ubuntu I could solve the issue with the following commands (had made a note on this based on a tip from someone else some time ago):
`sudo apt-get remove indi-full indi-qhy libqhy`
`sudo apt-get install indi-full indi-qhy libqhy`
I guess this installs back the QHY libraries from the nightly build to the currently released version of KStars?
@Jasem, does this give a clue on what could go wrong in 3.5.7 beta?
@Rob, are there similar commands on the Mac I could try to fix this? Or should I just altogether delete this version of KStars and do a fresh install of 3.5.5 instead? Is there a link still somewhere to 3.5.5?
The strange thing is that on a Mac running Monterey where both 3.5.5 and 3.5.7beta are installed, the camera can be connected well.
it isn’t really that something went wrong with the numbering so much as the timing of the build. It took me a few days to sort out some build issues I was having. The 3.5.7 beta was basically identical to the 3.5.6 version when I built it on Mac so it is basically the same as the Linux 3.5.6 one, but 3.5.7 is changing more and more by the day so it is possible that it is different now on Linux.
The drivers are inside the app bundle on Mac. And you can have different versions of KStars on the same Mac if you like. The 3.5.5 version is still available as well. You can’t run a command to build new INDI drivers on your Mac because you would need the whole development environment to be set up first and that’s complex. I can build a new dmg if there was a significant fix. If there was an issue with qhy And it has since been fixed, I can rebuild it.
Thanks for clarifying, Rob. You say 3.5.5 is still available. Could you share a link where I could find that version? Most places link to edu.kde.org/kstars/, where I can only see the 3.5.6/7beta. Would like to try and see if I can get the camera to work on this Mac on 3.5.5
Good question. I am not sure if Jasem put links to them anywhere. But it is still on the server in the same spot it has been. I think if you just try the current link location and edit it, that should work
Found it!. Thank you. Installed 3.5.5, but it would not start. Deleted the data files from Application Support/Kstars. Then it did work, so I have now a working 3.5.5 next to 3.5.7beta. However... the indi_qhy_ccd driver still crashes. So it looks like somewhere along the line I'm doing something wrong. But where....? Would love to hear any ideas from anyone.
Oh right, I bet that all those changes there were made recently to the DSO libraries made the current data directory not compatible with an older version. Or maybe some other change. But yes you did the right thing. You can of course backup the old data directory if there is something important there before deleting it. Yeah if that wasn't the issue then I am not sure why your QHY is crashing. Maybe try asking Jasem, he builds libqhy.
Jasem said that the camera works on his system with no issues with the latest version. I just tried it on mine, but of course I have no QHY camera so I won't know much.
So a couple of ways you can get information about the issue would be to either:
1. In the Ekos Logging options click "verbose", then select INDI and the CCD options and see what prints out when you try to connect the camera
2. Use the "Device Manager in the KStars Menu to Select the QHY driver and then try to connect the camera.
Either one of those methods might get some relevant information about why it crashes on your system (either Linux or Mac or Both).
If this doesn't give enough good information I have another idea of a way you could test it.
Thanks Rob. Got a little bit further. The Verbose logging in Ekos did not say anything other than that the driver crashed. But the Device Manager gave some clues. It said that libusb-1.0.0.dylib was not loaded, because libqhyccd.21.dylib requires version 4.0.0 and the version installed is libusb-1.0.0.dylib. See attached the log-file.
Based on that, I tried the following:
Updating libusb-1.0.0 with 'brew install libusb': no success (probably because the in-app embedded version is used anyway?)
Copied a libusb-1.0.0 from another Mac that has a working version: no success
Fresh install from KStars 3.5.5.img (again): no success
Would this give you any clues of what is wrong, and how to solve it?
Is this on the 3.5.5 version or the most recent version?
Yes this is very useful information and tells me precisely why it crashed. Yes it will be looking inside the app for the file not in homebrew since it is a fully packaged up app. If it is the most recent version then I can certainly look into what happened and fix it. If it is 3.5.5, then Please try the newer version and see if it also has the same linking issue.