Skip to content

19. Using MobileConnect for IOS and Android

Gord Tulloch edited this page Nov 15, 2026 · 4 revisions

19. Using MobileConnect for iOS and Android

Status: in design and early development. MobileConnect has two halves: the MobileConnect plugin (the server side, on the observatory computer) and the apps. The plugin is a draft that is not yet published, and the apps have not yet run with real equipment: the iOS app runs against test code with simulated devices, and the Android and Meta Quest editions have not started. This article describes what MobileConnect is designed to do, so you know what to expect; check the project's status before relying on it.

MobileConnect lets you watch and operate a running Galileo observatory from a tablet (the primary target) or a phone — connect equipment, find and centre targets, focus, guide, run and edit sessions, and respond to safety events — without going back to the computer. For a browser instead of an app, see 18. Using WebConnect.

The apps operate an observatory; they never configure one. The observatory should already be set up and running before you pick up the tablet.

Contents


What the apps do

The areas are in the menu in this order. Every control has built-in help on the desktop; the apps are for operating, so the screens are laid out for use at the telescope, with the most-used controls first and big enough to hit in the dark.

Area From the app
Overview The activity timeline and alerts for the working Pier, then the Pier list, node health and the session. When the Master has more than one Observatory, Piers are named Observatory - Pier. Connect All Devices connects everything the working Pier has configured
Sky Planetarium view with the telescope's position and field of view, target search, go-to, framing and mosaics
Focus Autofocus first; then manual focus, with large Hold in and Hold out buttons at the top that move the focuser only while held
Polar Alignment The polar error as numbers: total, north-south (altitude) and east-west (azimuth) deviation with what to turn; start and stop; a small latest frame at the bottom
Targets The targets you saved on the desktop (Planning > Targets), each with its picture: slew to one, slew and centre on it, or remove it (removing needs control)
Mount Control A full-screen pad of eight arrows (including diagonals) and a Stop, with a speed slider (the Mount page's nine speeds). Each arrow moves the mount only while it is held
Imaging Capture, live preview with stretch, histogram, star statistics
Solve Capture & Solve, Load & Slew and Stop; the bullseye with the deviation in dRA, dDec and total; exposure; which of the Pier's cameras to use; the latest frame last
Guiding Start and stop guiding, dither
Sessions Run, pause and stop sessions; author and edit sessions and the multi-night schedule
Safety See every safety input; acknowledge an event; one-touch stop and park
Equipment Connect devices; mount, the meridian flip (state, and flip now or defer it), camera, filter wheel, rotator, dome
Settings The app's own settings and theme

The Library (recent sessions and frames as previews, history and charts) is also available.

State is pushed to the app as it changes, rather than polled.

What they do not do

The apps never configure: equipment profiles, Observatories, Piers, site location, safety limits, Options and plugin settings stay on the Galileo desktop (or reach other computers through 17. Using NodeConnect). Setting a value for a single run — an exposure time, a focus step, a target — is operation, and is available.

Imaging never depends on the app. Closing it, or losing the connection, does not stop the night; the only exception is a manual motion you are holding down, which stops when you let go or the connection drops.

There is no cloud account and no internet relay: the app talks to your observatory over your own network (or a VPN you already run). Because of that, alerts reach you while the app is connected; background push notifications are not part of the first version.

Installing and pairing

  1. On the observatory computer (the Master), install mobileconnect from Options > Plugins once it is published, and make sure Connect Link is enabled.
  2. Install the Galileo MobileConnect app on the tablet or phone (App Store for iOS/iPadOS; Google Play for Android).
  3. In the app, find your Master and request to pair. A short confirmation code appears on both devices; compare them.
  4. On the Master, open Options > MobileConnect and approve the request.

After updating Galileo, update the plugin too. The Master loads the copy of MobileConnect you installed from Options > Plugins, not the newest one on disk, so a new feature in the apps (for example the pictures on the Targets screen) shows nothing until the plugin is reinstalled from its zip there and Galileo is restarted. If a screen says This Master doesn't offer this yet, the Master is running an older plugin or an older Galileo. Some newer controls (diagonal moves and the speed slider on Mount Control, the camera choice on Solve, Connect All Devices) also need a current Galileo on the Master; restart it after updating.

From then on the app signs in with its own token. Approved apps are listed on the Master's options page, where each can be given a role or revoked immediately. An app that has not been approved is refused.

Roles and the control lease

An approved app is a Viewer (sees everything, changes nothing) or an Operator. Only one controller can drive a Pier at a time, through a control lease shared with the desktop and any browser, so a tablet and the desktop cannot give a mount conflicting commands; any number of viewers can watch. Destructive operations ask for confirmation, and everything done from an app is recorded in an audit log on the Master.

Several computers

The app pairs with one computer — the Master — and operates every paired computer's Piers through it, exactly as the browser does. A single-computer observatory is simply a Master with nothing else attached. Operating another computer's Pier needs that computer to have allowed it when it paired with the Master; see 17. Using NodeConnect.

Images and data use

Images reach the app as ready-made, stretched, scaled previews rendered on the observatory computer, not as FITS files, so a night's use over a weak link stays modest. Downloading a full FITS frame is an explicit action.

Outreach: sharing the live image

At a club or public event, the owner can open an outreach event on the Master. Visitors scan a QR code with their own phone or tablet, join the event's Wi-Fi network and see the live image of the Pier you chose to share, as each frame is made, switching between the Piers you offered. They do not register, pair, or see or touch anything else. The event is closed by default, ends on a timer and is confined to its own network. The same event can also serve visitors in a browser; see 18. Using WebConnect. How to set up and open an event is described under Setting up an outreach event.

Meta Quest

A Meta Quest 2/3 edition is planned, intended to be equal to the tablet in function, with an immersive planetarium and image viewer. It has not started, and serving it needs the Master to be PC- or Mac-class hardware: a Raspberry Pi-class Master serves tablets, phones and browsers, and tells a headset that VR streaming is unavailable.

Safety

The app is a second front end to the same services the desktop uses, with the same safety checks. It can acknowledge a safety event and request a retry that Galileo's own safety service judges, but it cannot disable the safety monitor, clear an unsafe state or override a mount limit. A one-touch stop and park is always available.

Limitations

  • Not finished: see the status note at the top.
  • No configuration, no offline operation (the app controls a node it can reach; it does not hold a plan to run later), and no FITS processing on the device.
  • It is not a remote-desktop view of the Galileo application.
  • Every plugin control has built-in help (press F1 or the ? button on the desktop).

Clone this wiki locally