I think I've found the issue; it seems to now work for me. But it it camera type specific. See my
I started with the Astroberry 2.0.3 image. This worked until I did the apt upgrade. The first upgrade broke eqmod, ZWO camera, and QHY camera (missing symbol crashes). Subsequent apt upgrades resolved the issues of missing symbols. But the QHY was still not detected.
So I installed github.com/JerryBlack/buildKstarsNightlyFromGit which builds from git repo’s. So I not installing specific versions.
But, I now know the issue isn’t Astroberry specific. So the thread should either be moved or closed here an restarted elsewhere.
I should have been more clear. With the various distro’s, version numbers can be hard to track. The versions of the various pieces worked with the last official release of Astroberry. Any upgrades do not.
I’ve now just installed the new Raspbian OS, and am building KStars and related components from source. The behavior is the same. The current head version of libqhy & indi_qhy still exhibit this behavior. I can see the camera is on the USB bus, but is not detected. And neither of these components have been updated in the last two weeks.
Tomorrow I’ll dig into the source to see if I can figure out what is happening.
Which packages were updated?
I installed Astroberry on a new Pi4. I created a profile for my rig, and everything connected. So I ran apt update/upgrade, and now the QHY camera no longer connects. The lsusb shows it its connected, but even the qhy_ccd_test doesn't see it. Any ideas?
QHY Test CCD using SingleFrameMode, Version: 1.00
-- InitQHYCCDResource param
QHYCCD|QHYCCD.CPP|InitQHYCCDResourceInside|numdev set to 0
************************** config file path 126.96.36.199 svn: 11361 ************************************
QHYCCD|QHYCCD.CPP|InitQHYCCDResource|Load ini filePath = /home/astroberry/Development/indi-3rdparty/indi-qhy fileName = qhyccd.ini
SDK resources initialized.
No QHYCCD camera found, please check USB or power.
It seems to have stopped now. So my annoyance was a bit premature!
Yes, it helped with the log, so thanks. Unfortunately it only shows that it is crashing.
On my Mac, before Ekos would connect to the mount correctly, I had to set port speed. But that is set in the driver page, and as it is crashing here, I do not have that opportunity. Can I edit this manually before starting?
My Pi is powered via its ow supply. My SSD is in the Pi case, and is powered off of the Pi's USB 3 port (the case is designed to use a USB connector that connects the USB of the SSD to the Pi). Then I have a Powered USB hub for my devices.
The case is the Argon ONE M.2 case.
I'm just getting set up. I'm using KStars and Ekos. This all works on my Mac laptop. I'm now trying to get this working with an Astroberry setup. Everything works there except the mount. Every time I try to connect, the eqmod driver crashes in a loop. All other devices connect.
I'm looking for where I can find information on the crash. If I look in syslog, I just see a generic failure message.
Would someone point me to the correct log file for more information? Or how to troubleshoot the connection from the command line?
It could be a power issue. Check the hub's power supply. If it is one of the cheap ones, it'll be 5 volt. The better ones are 12 volt and 5 amp or so,
As an aside, I just setup a new Pi 4 with SSD, and used a Pi case that held the SSD. Works very well.
That the captcha is used to only to log in, but on every single form post or response, is a gross abuse and ridiculously poor user experience.