The RPi should be able to handle your setup well. The MacMini likely gives you a better overall user experience, at the cost of a more costly and bulkier setup that requires mains power. For a long time my go-to solution was a Fitlet 2 mini computer, which is a great compromise between the two and which I like more than the RPi solution. But recently I went your suggested route and bought a 2018 MacMini, which is now my go-to system, with the Fitlet 2 as backup for anything more portable. So far I’ve used it down to -5 degrees Celsius and the heat produced by the computer was sufficient to keep it all warm enough to be working fine. I’m using
for it, which gives a nice bit of protection and I’m telling myself it keeps it a bit warmer. The 2020 M1 Mac mini is so energy efficient that it does not produce any heat at all, so would probably get colder over night. But since it is different electronics altogether, not sure if that means it can handle the cold better or worse.
If you connect from another Mac, you can simply use ‘Share screen’ from the finder, and if you connect from iPad/iPhone, you can use the free VNC viewer from RealVNC to connect. Mac’s come with an embedded VNC server installed.
Great news! QHY Camera connects flawlessly! Thank you so much for your continued support Rob, to help finding the root cause of this issue and make the fixes. Much appreciated. Also nice to see the proper version number, to prevent confusion in the future when there might actually be a 3.5.7beta release.
That sounds promising! It would be great if this would appear to be the issue as the fix seems simple.
No rush Rob, we've come a long end, so a few more days is not a problem at all.
Progress made! Since it seemed like it was a version-issue, I have tried to install other older versions. Your information that older version were still available by simple changing the url was very helpful with this. These were the results:
3.5.1: QHY worked
3.5.4: QHY worked
3.5.5: QHY crashed
3.5.7b: QHY crashed
Both cases that had the crashes were showing the identical messages of a version issue with libusb-1.0.0.dylib in the device manager.
So the good news, we're closing in on the issue and I now have a fully working KStars, albeit it being 3.5.4.
Would this give you some clues of what could go wrong with 3.5.5/3.5.7b, either in general, or the DMG image? And most importantly: how to correct 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?
Many thanks, Willem Jan.
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.
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
Sounds good. If there is anything I can help with, please let me know. As you say, it's a group effort.
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.
Thank you Rob, and it would indeed be a great help if we collect the various combinations that work (and don't work) in the documentation. The outcomes will probably be different for the different devices, so perhaps the most logical place would be to add it to the individual drivers INDI-page.
It seems like there are several variables that are relevant:
- the USB to Serial bridge controller chip in the device (focuser, USB>Serial cable, etc)
- the version of the virtual com-port driver (the brand is determined by the chip)
- the macOS version
As far as chips and drivers go, the three main brands that keep coming up are: Prolific, FTDI and Silabs
As far as macOS version is concerned this may be limited to: before Big Sur vs Big Sur and later.
The drivers use system extensions. Before Big Sur these were Kernel extensions, using little system files with the extension .kext. In Catalina so called driver extensions were introduced, making use of DriverKit. Kernel extensions require terminal commands to install and normally you won't see them. Driver extensions install as an app and remain visible as an app in the Applications folder. Catalina introduced Driver extensions. From Big Sur onwards, this was mandatory.
so perhaps we can add an extra line with each INDI driver for which we have the information.
For the Sesto Senso 2 and Esatto focusers this could look like:
For this INDI driver to work properly on a Mac, a separate USB-Serial driver needs to be installed. The legacy Silabs driver version 4.* can be found here . Installation requires macOS 10.14 (Catalina) or lower. So far, it has not been possible to establish a proper connection using either driver version 6.* or macOS 11 (Big Sur) and higher.
For the Microtouch focuser (based on another thread on this topic), it could look like:
For this INDI driver to work properly on a Mac, a separate USB-Serial driver needs to be installed. The latest Silabs driver can be found here . This driver has shown to work on macOS 12 (Monterey) and is likely to work on 10.14 (Catalina) and 11 (Big Sur). For older macOS version, the legacy Silabs driver may be required, which can be found here .
Even so, it would be good to know from people who have no problems with focusers and their Macs, for which it could look like:
For this INDI driver to work properly on a Mac, no separate USB-Serial drivers need to be installed. The required drivers are embedded in the macOS. This has been tested on macOS versions .....
Finally it looks like most issues occur with focusers and USB-Serial cables, but perhaps there are other devices as well? USB-serial cables probably have an infinite amount of manufacturers. But they probably all use one of the three chips. Perhaps we could create a general sentence on USB-serial cables, and point people to the three drivers mentioned. We could add that sentence to the devices that have a traditional serial (DB-9?) interface.
Just a few thoughts, Rob. Happy to help further where I can. I've got a Monterey and Mojave setup that I can use. But only have the Primalucelab focusers as hardware that I can test.
Having the same issue now on my Ubuntu computer. Also on 3.5.7 Beta. QHY driver crashes as soon as it is loaded.
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?