Awesome work guys
So you are right. For some reason last night it was guiding with no issue. I left everything setup. Got up early this morning to capture C/2020 F8 Swan. And that issue reappeared. Everything ok for about 90 seconds and then RA went off on its merry way again.
As suggested by Kross I checked to see if all corrections were ticked on and they were. I played with the aggressiveness as suggested by krno with no luck.
So not too loose another session I just set the automatic guide star rest of RMS exceeded 3 just to capture the comet.
Now I I don't know what to do.
Again I tried phd2 with the default settings with no issues.
Hi all so similar issues to before. So I uninstalled and reinstalled everything.
It's now guiding with no issues. Looks like something was half baked in my last apt upgrade.
Thanks for all your help.
Hi All, thanks for your responses. The weather hasn't been the best here, so i haven't had a chance to check your suggestions.
Leave it with me, hopefully over the weekend i can do some tests and report back.
Hi all so after the issues with RPi4 guiding (and wifi eqmod connection) I uninstalled everything and did a fresh install. I tested eqmod wifi and it now connects. I have not had a chance to test the guider due to weather, but i have a funny feeling it will now work.
Correct me if I'm wrong (I'm no Linux expert), but to update my Rpi4 (and tinker board), all i do:
sudo apt update && sudo apt upgrade
Is this the correct way to keep my system up to date with the stable INDI releases?
Im using the default ekos logarithm, Smart. I have also tried SEP as well with the same results. I have also tried the other 3 with no luck.
Hi krno and Herrhausen, thanks for your fast responses.
I using eqmod pulse guiding method, not ST4. I have not used ST4 cable from guide camera to mount for a long time.
The graphs were taken one after the other. I first ran phd2 (using its default settings), guidered for a while until everything was stable. I then disconnected phd2 and reinstated the internal guider and did the same. I did not move the mount, it was still pointing at the same target and the time from disconnection of phd2 and re-connection to internal guiding was only 20 or seconds. I have now plotted the pulse below the error correction and Herrhausen is correct; the mount is not receiving the RA connection pulses for some reason. See attachment.
How can one use phd2 and internal guider logging at the same time? As you suggest this will be the best way to log what is going on?
Hi all just to add to the guiding issue, i have not had much luck with the internal guider on my RPi4 over the last few nights ever since the last update (3.4.2). See attached logs.
When i use phd2, i have no issues. See attached log from phd2.
Initially i though the problem was with my mount, so i adjusted my mount to eliminate backlash. Polar alignment was within within 12" of the south celestial pole. The weather was fine (no wind), no cable snags, everything was balanced and mount clutches tight.
But the internal guider just did not want to cooperate. I also tested with my Asus tinker board which was last updated on 2/1/2020 and the internal guider works perfectly.
So something has changed in the internal guider.
Hi all, jut wondering if anyone is having any issues with EQmod connection with the skywatcher wifi adapter.
So 2 days ago everything was working fine.
So i did a apt update and upgrade yesterday (stupid me) and there were no indi updates, just a heap of Raspbian OS updates on the RPi4.
After the update, skywatcher wifi dongle refuses to connect.
EQmod cable connects and works fine. Wifi dongle with the skywatcher app on android phone connects and works fine.
So it must be something has happened with the last RPi4 update.
Anyone seeing the same issue?
PS here is an image from 3 nights ago using 135 samy on a qhy163c
Hi jmh, i have been debugging it today after issues last night. So a summary; the tinker board is stable no issues so no more updates for it. I use it when im doing a serious imaging run as it works perfectly. The rpi4 is a build in progress.
So i had not updated the rpi4 since the end of February 2020 as it was working ok. After the issues last night (mainly with guiding) i decide to do a full update and then the qhy issue started. The qhy and the zwo asi224 (guider) are both connected via USB3.
This morning i tried again with no luck. So i connected the qhy to the USB2 port instead of the USB3 port and presto, it worked. When i connected back to the USB3 port, the thing works.. All power connections we the same as last night after the upgrade. I then ran everything (mount via wifi, guider, imaging camera with cooling etc and everything is working under both USB2 and USB3. Really weird, i cant explain it.
I have read elsewhere on the forum issues with using USB3 and 2.4G wifi (which is how i remote to the rpi4). I switched to 5G wifi with no issues, except my mount connects via wifi and the shywatcher wifi dongles do not support 5G wifi, so i have to stick with 2.4G or go back to USB eqdirect.
Anyways, ill give it another go tonight. Maybe it is just scared of the dark
Hi all any news from QHY regarding a fix to their SDK.
Im using a QHY163 and then thing wont capture at all. On capture, it goes into an endless download loop.
The cooler oscillates significantly from the set point and the camera will not disconnect.
Attached is the log file,