You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi Dale,
I am really impressed with the SkySolve, I was planning on developing something myself but seems you have it all covered.
Given I had a Raspberry Pi 4 and a 4.3" touch screen laying around, I've added a screen and a kiosk mode pointing to the WebUI, so you can actually control everything from it.
I am thinking on creating a secondary WebUI, more suited for a small screen / touch, so it makes controlling it a bit easier.
I'll keep you posted on the progress, perhaps you decide to incorporate to your main package when it's done!
One last thing: I have used the latest Raspberry Pi OS (32-bit), not the Legacy one, and everything works perfectly. You might want to try for yourself and update the instructions accordingly.
This is the Repo I created with the instructions I used: https://github.com/fmaranhao/PiSkySolveScreen
Cheers, Fred.
Thank you Fed. I have resisted the idea of adding a screen to control it. Since that just adds weight, cost, complexity, and you usually do not ever need to access the interface if all is working well. It usually only gets used if at all at the start for people to learn about it.
That is why I made the interface a web page so that any device could be it's controller since you need something running Skysafari in the first place that device can also be it's interface if needed.
Ok, I have scrapped that and followed your suggestion (no screen).
I have an Arducam IMX477 camera (not the CameraPi HQ, but same chipset), unfortunately it doesn't work with the Legacy raspistill / PiCamera stack. So I've forked your project and "translated" the camera_pi.py to use the newer Picamera2 stack. It's been working (indoors, can get all the camera stream / change of settings - haven't tried outdoors, perhaps next weekend).
In case you're interest in having it a go and ultimately incorporate to your main code...
Cheers, Fred.
Thanks,
I'm pretty lazy and usually don't change something unless it is broken. Since the real pi cam works well I will stick with it. Glad you found something that works for you.
I just built a unit for a customer and realized I use the interface more than I thought for setup and then to review the images it took. However most of that was done indoors using my laptop browser. Mostly to review the images it took and solved and to play with shutter speed for the light conditions. For instance to set rough infinity focus during daylight hours and then again at night on stars.
However while really observing I don't use the interface at all unless for some reason it does not start up.
Activity
githubdoe commentedon Jun 20, 2023
Thank you Fed. I have resisted the idea of adding a screen to control it. Since that just adds weight, cost, complexity, and you usually do not ever need to access the interface if all is working well. It usually only gets used if at all at the start for people to learn about it.
That is why I made the interface a web page so that any device could be it's controller since you need something running Skysafari in the first place that device can also be it's interface if needed.
fmaranhao commentedon Jun 30, 2023
Ok, I have scrapped that and followed your suggestion (no screen).
I have an Arducam IMX477 camera (not the CameraPi HQ, but same chipset), unfortunately it doesn't work with the Legacy raspistill / PiCamera stack. So I've forked your project and "translated" the camera_pi.py to use the newer Picamera2 stack. It's been working (indoors, can get all the camera stream / change of settings - haven't tried outdoors, perhaps next weekend).
In case you're interest in having it a go and ultimately incorporate to your main code...
Cheers, Fred.
githubdoe commentedon Jun 30, 2023
Thanks,
I'm pretty lazy and usually don't change something unless it is broken. Since the real pi cam works well I will stick with it. Glad you found something that works for you.
I just built a unit for a customer and realized I use the interface more than I thought for setup and then to review the images it took. However most of that was done indoors using my laptop browser. Mostly to review the images it took and solved and to play with shutter speed for the light conditions. For instance to set rough infinity focus during daylight hours and then again at night on stars.
However while really observing I don't use the interface at all unless for some reason it does not start up.