[Guides](https://skyblip.eu/guides.md)

# A fix is earned, and a flight is a speed.

A skyBlip Go needs its own position and time before it can broadcast a position over ADS-L. It checks the GPS receiver’s output, waits for it to settle and uses ground speed to decide whether the aircraft is airborne. That decision changes how often it transmits and whether it allows an update.

## The fix

### A solution is not a fix.

The GPS receiver sends a solution twice a second, whether or not it can see the sky. The Go accepts that solution as a fix only after its own checks. Both sentences carrying the position and date must be present and fresh. The date must not be the 1980 placeholder some receivers send before they know it. The position must be within plausible reach of the previous one. The receiver also reports whether it considers its solution valid, but the Go uses its own verdict.

A Go uses a Quectel L76K receiver. A Bravo uses an Airoha AG3335. Both send their readings in the same NMEA sentence format, which the same parser reads.

### Three words while it waits.

NO FIX alone cannot tell you whether the antenna is under a hangar roof, the receiver has stopped talking or a fix is twenty seconds away. The Go reads the sentences already arriving and shows a word that tells you whether to move it, wait or take it to the bench:

| Word | What the Go sees | What to do |
| --- | --- | --- |
| GPS OFF | no recent sentence from the receiver | take the unit to the bench. Waiting for a clearer sky will not make the receiver talk |
| MOVE OUT | solutions arrive without a usable date | move the unit where the antenna has a clearer view of the sky |
| FINDS FIX | a usable date has been decoded | leave the unit where it is. The receiver has read a satellite’s navigation message but still lacks the geometry for a fix |

FINDS FIX tells you that waiting can help. The date comes from the satellites’ navigation message, so decoding it marks progress beyond receiving no usable signal. The status page adds the time spent at the current stage, up to 9:59. The radar ring and the nearby list show only the word, to avoid redrawing part of the screen every second while the unit has no fix.

![The radar page with no position: the empty ring shows NO FIX and, below it, the receiver's progress towards a position fix](https://skyblip.eu/assets/pages/skyblip-go/no-fix-95ffa948.png)
_No fix yet, but the receiver has decoded a date_

### It transmits once the fix has settled.

A receiver starting cold can produce fixes whose position, altitude and especially ground speed wander for several seconds. Ground speed also triggers the airborne state. Transmitting too soon could broadcast a track the aircraft never flew, at the airborne rate while it is parked.

The Go measures whether the fixes are settling rather than imposing a fixed wait. Each second it predicts the next position from the previous fix, at constant speed and turn rate, then compares the prediction with the new fix. It starts transmitting after three predictions in a row miss by less than 12 m. Twelve metres over one second corresponds to 12 m/s, the takeoff threshold, so the error limit is tied to the flight decision it protects. A 2D solution never counts towards settling because its altitude is not a measurement. If the receiver does not settle, transmission starts after 20 s from the first fix, or 5 s after a brief loss of fix. The wait has a ceiling because withholding every transmission would be worse.

### The fix must land before 450 ms.

The Go cannot use a solution for the current second until the receiver has sent its closing sentence. The first possible transmission is 450 ms after the start of that second. The receiver starts sending about 70 ms into it. At its startup rate of 9600 baud, the 320 bytes of a fix take 333 ms to arrive, leaving only 47 ms of margin. A bench unit using 22 satellites completed its fix at 780 ms. Every transmission scheduled before then was refused.

The Go therefore switches the receiver to 115200 baud, the highest rate documented for its configuration command. The same fix then takes 28 ms to arrive. The command has no acknowledgement, so the Go checks for a correctly received sentence at the new rate. If none arrives, it returns to the old rate.

The satellites page shows a signal bar for each satellite. The sentences carrying those levels also delay the fix, so the Go requests them only while that page is open, with one set every five seconds. The counts on the page still update every second.

The receiver solves twice a second, on the full second and on the half. ADS-L stamps each position to the quarter second, to within 10 ms of the moment the receiver measured it, and sends no position measured more than 500 ms earlier. A solution on the full second therefore serves transmissions only until 490 ms, keeping 10 ms for the burst itself, and the half-second solution serves the rest of the slot. The receiver ignores a request for four solutions a second. At five a second, only the full second falls on a quarter. Our [open questions to EASA](https://skyblip.eu/ads-l/questions.md) ask whether the rule means this.

![The satellites page: one bar per satellite grouped by constellation, against a dotted line at 40 dB-Hz](https://skyblip.eu/assets/pages/skyblip-go/satellites-75da5bce.png)
_Signal levels are requested only while this page is open_

### PPS marks the start of the second.

The receiver provides a pulse per second, or PPS. An interrupt captures its edge without waiting for the next operating-system tick. That edge marks the start of the UTC second from which each [radio window](https://skyblip.eu/timing.md) is measured. Each solution is dated at the edge, not when its last sentence arrives. If the pulses stop, the radio windows continue from the last edge for 60 s, to receive only: the Go transmits nothing without a PPS lock.

Whether the L76K keeps producing pulses without a fix is still unverified. Its documentation describes the pulse but does not say whether losing a fix stops it. The chip supports either behaviour, and the Go does not configure it. A bench test is needed to establish what happens during a loss of fix.

## The flight state

### Airborne or on the ground, from ground speed alone.

The Go decides whether the aircraft is airborne from the ground speed reported with each fix. It uses no altitude, vertical rate or barometer for that decision. Separate thresholds prevent a small change in speed from switching it back and forth:

| State | Condition | Why that number |
| --- | --- | --- |
| Takeoff | 12 m/s or more (23 kt) | a tug hurrying back to the grid does 10 m/s. A glider lifts off on aerotow at about 20 m/s |
| Landing | under 8 m/s for 10 s | a sustained taxi speed lets the Go recognise a landing before the aircraft stops |
| Landing | under 1 m/s | a stop. The threshold is about three times the receiver’s usual stationary speed noise |
| TAXI on the screen | 1.5 m/s or more, on the ground | about a brisk walk. The display returns to GROUND below 1 m/s |
| In between | keep the previous state | the gap prevents repeated changes near a threshold |

The gap between 12 and 1 m/s matters in wind. A circling glider in a 15 m/s wind can go from 5 m/s upwind to 40 m/s downwind on each turn. A single threshold between those speeds would repeatedly declare landings and takeoffs. Requiring 10 s under 8 m/s avoids that during the example turn: in a 20 m/s wind, a glider circling at 22 m/s spends about 3 s of a 25 s turn below the landing threshold.

An earlier rule also declared flight above 2000 m. That left a unit parked at Courchevel, at 2008 m, permanently airborne. Ground speed avoids that altitude trap, but the quality of the fix still matters. Evidence for flight is reduced when the fix is poor, and a speed jump of more than fourfold between consecutive fixes is ignored. Evidence for the ground is never reduced, because reducing a speed must not manufacture a landing. The first fix after switching on decides immediately. Between the thresholds it selects the ground, since switching on while being towed to the grid is the common case.

### What the state changes.

| | On the ground | Airborne |
| --- | --- | --- |
| Positions on the air | every 9 then 11 s | every second |
| Traffic alarm | silent | traffic is assessed for alerts, see [traffic](https://skyblip.eu/traffic.md#ground) |
| Updates, settings from the phone, flight log offload | allowed | new updates, log offload and settings that need a press refused. Settings from a trusted browser remain allowed |
| Flight log | the preceding minute of taxi held in memory | recorded every second, including that preceding minute |
| Flight timer | holds its reading | counts airborne time |

A false takeoff blocks updates on the ground and uses the battery at the airborne transmission rate. A missed takeoff leaves an aircraft broadcasting at the parked rate while flying. Once the Go has declared flight, losing the fix cannot clear the update lock. Only a positive ground state does that, so an antenna losing reception over a ridge cannot unlock an update in flight. A unit with no fix since switching on has an unknown state and allows updates, so it can be worked on indoors at the bench.

The flight timer counts airborne time since switching on, not since the last takeoff. It pauses at a landing and resumes at the next takeoff. A touch and go therefore does not reset the accumulated time, and a false landing loses only the seconds spent in the ground state.

### Wings that need no ground speed.

A paraglider flying at about 10 m/s through the air has only 5 m/s of ground speed into a 5 m/s breeze. It can remain below the takeoff threshold throughout the flight. Hang gliders working a ridge and balloons can present the same problem. For those aircraft types, the Go broadcasts ADS-L’s undefined state instead of on the ground. ADS-L sends that state at the full rate, so the broadcast never labels them as parked. This does not make the ground-speed detector declare flight. Their flight log has a separate rule: it opens when they move and closes after two minutes standing still.

Barometric climb was once used to detect these flights. It was removed because gusts, pressure changes and spikes when the barometer dropped out caused false takeoffs in the hangar queue. Ground speed avoids those false detections, but it can miss flight at low ground speed. The undefined broadcast state and the separate logging rule address those limits without treating barometric climb as proof of flight.

- The Go checks each fix rather than accepting the receiver’s validity flag
- GPS OFF, MOVE OUT and FINDS FIX tell you whether to investigate, move or wait
- Transmission starts after three predictions within 12 m, with a ceiling of 20 s after the first fix
- 115200 baud brings the fix in before the first possible transmission
- The Go declares takeoff at 12 m/s and landing under 1 m/s or after 10 s under 8 m/s
- Losing a fix in flight never counts as a landing

Want to try it now, or get one?

[Try it online](https://skyblip.eu/try.md) the software in your browser

[Get one](https://skyblip.eu/buy.md) a Go from €68, no subscription
