This is the FAQ page

Support Resources

I will set priority on responding from my Github and my Discord Channel:

Public Discord Channel for up to date info https://discord.gg/B3zDCAMP4V

Facebook Group: Smart Telescope Underworld https://www.facebook.com/groups/373417055173095/

YouTube Channel https://www.youtube.com/channel/UCASdbiZUKFGf6VR4H_mijxA

Github https://github.com/smart-underworld

Using Seestar_alp and the Seestar App together

When the Seestar is powered up Seestar_alp should always be the first thing that connects to it. This ensures that Seestar_alp is treated as the Master device and can send commands to the S50. After initialization you can also connect with the normal Seestar App from mobile phone/tablet e.g. to view live images.

If you connect in the wrong order i.e. App first then Seestar_alp will probably fail to send commands because it will be in Guest mode on the S50. If the App has connected then it may stay running in the background on the mobile device and need to to forced stop from App settings.

Note: this behaviour by the ZWO firmware is a developing change and may be different when the Mosaic Beta firmware is released.

Raspberry Pi supported Operating Systems

On a Raspberry Pi you need to install a 64-bit OS - either Bookworm Lite version or with the Desktop GUI. 32-bit OS is not supported.

Generally it is a good idea to keep the OS up to date with patches. On the Desktop version this can be done using this icon when updates are available

To update the Raspberry Pi OS from the command line use:

sudo apt update
sudo apt upgrade

How to force an update on Raspberry Pi

On a Pi seestar_alp is usally updated simply by running the update.sh script in the raspberry_pi folder. However, sometimes on major updates the script itself needs to be updated before you run it (e.g. you may receive errors during the update). In this case use the following commands

cd ~/seestar_alp
git pull
./raspberry_pi/update.sh --force

How to control where the Seestar points on startup

when the Seestar startup sequence is run from the commands window there are two settings in the configuration which control where the S50 will point before it starts its alignment routine. These are set in the SSC configuration see SSC configuration

Scope_aim_lat & Scope_aim_lon
These are NOT related to your geographical position, instead they determine where the Seestar arm will be pointed after the startup sequence command is issued.
For an Alt/Az mounted Seestar scope_aim_lat will be the altitude above the horizon and scope_aim_lon will be how many degrees (couter-clockwise) it will rotate relative to the starting position.
For an EQ mounted Seestar the coordinates refer to the Celestial Equator

Note: scope_aim_lon of 180 will face the scope to the reverse of where it is set when turned on.
scope_aim_lat of -90 is the arm closed position scope_aim_lat of 0 is the horizon which is the plane of the bottom of the seestar.
Maximum scope_aim_lat is +80 as the scope cannot point straight up in Alt/Az mode.  

Using seestar_alp with new S50 Firmware v3.31 and later

The v3.31 firmware (which added the Mosaic/Framing feature) also introduces the concept of Controller and Guest access to the S50.

Unlike earlier firmware there can only be a single device sending commands to the S50. However, multiple Guest devices can see the image as the Seestar does an enhancement stack.

If you are using seestar_alp to control the Seestar then you must NOT use the Seestar App before seestar_alp has become the controlling device after you boot the Seestar.

For detailed information refer to the Guest Mode wiki