Hi,
The current season for us in Chennai, a coastal metropolis in southern India is marked by transparent and substantially clear skies with occasional fast moving low clouds. I use PHD2 for guiding. When a cloud rolls by, PHD2 tries to reacquire the guide star for 60 seconds and continues guiding. Unfortunately when a large cloud rolls by, PHD2 aborts after the 60 second timeout. At this point, EKOS also stops the sequence as PHD2 has stopped guiding. I shoot overnight, after going to sleep and am unable to manually restart after the abort. For example, last night while shooting Thor's helmet a large cloud rolled in around 12:30AM and the sequence was aborted. I still had about 3 hours worth of data that could have been captured.
Is it possible to automate the process for retrying running the sequence along with instructing PHD2 to reacquire a guide star and guide?
Regards,
Arun
Read More...
The Pi4 with 4GB will easily handle the fully autonomous operations. I use the same configuration. Give it a try!
Regards,
Arun
Read More...
I run the Kstars, EKOS and PHD2 in the Pi. I use my laptop only to connect over VNC to manage the session. Practically my laptop is just like a remote monitor.
In your setup, every guide camera frame has to be sent over the network to your laptop. Then a guide decision has to be made in your laptop and sent back over the network. I would assume that this might create a lag or put pressure on your network. Also, why rely on two compute devices when one can do the job. Unless of course you are running indi on a very low powered rpi. I personally would like to reduce the number of points of failure for a productive session.
Regards,
Arun
Read More...
Hi,
I have a setup where all my equipment is on the rooftop and I control it from my study through a combination of wired and wireless LAN. The whole setup is controlled through a Astroberry+rpi and it works brilliantly.
I use a wifi switch to turn on power to all my equipment in the roof in one go. The problem is that the wifi router in my roof takes about 15 seconds to make the wifi network available. The Astroberry/rpi does not wait for this network. Since no configured network is present, it switches to the hotspot mode and makes it impossible to access it from my study, 3 floors below. To solve this problem, I manually switch on the rpi a few seconds after the wifi router is tuned on.
Is there a software based solution for this? Can we delay the switch to hotspot and continue to wait for the wifi network to be available? I do not want to disable hotspot completely as I think is incredibly useful to troubleshoot or when I use it in a external dark site. The other solution I am thinking about is a delayed on electrical switch for the rpi. Hopefully there will be a software solution for this.
Regards,
Arun
Read More...
I have the same issue. kstars crashes when I connect to EQMOD. This is after the upgrade to 3.5.6.
Kernel message:<code>[ 103.349143] Alignment trap: not handling instruction ed917b06 at [<00431e4c>]
[ 103.349152] 8<--- cut here ---
[ 103.349165] Unhandled fault: alignment exception (0x221) at 0xb6e7a6ed
[ 103.349176] pgd = 326a05e4
[ 103.349185] [b6e7a6ed] *pgd=06121003, *pmd=7cd45003</code>
Read More...