Every burst has its second, its channel and its millisecond.
A skyBlip Go schedules each radio burst in three steps. Its serial number sets the seconds. Whether the second is even or odd sets the channel. A draw repeated every second sets the millisecond within that channel’s window.
The second, cut into three windows.
GPS marks the start of each UTC second. The Go has one radio, so it listens in three windows, each on a different channel. The radio guide explains what it receives in each. Here, the question is when it transmits. All times below are measured from the start of the second.
| Window | Channel | Full listening window | The Go’s own bursts start |
|---|---|---|---|
| Uplink | 869.525 MHz | 210 to 440 ms | never: the ground station transmits here and the Go only listens |
| Window 1 | 868.2 MHz, channel A | 450 to 820 ms | positions and Status from 450 to 810 ms |
| Window 2 | 868.4 MHz, channel B | 830 to 1200 ms | positions and Status from 830 to 990 ms, callsign from 1000 to 1190 ms |
Window 2 extends 200 ms into the next second to receive FLARM-generation devices still transmitting there. ADS-L’s direct slot, reserved for transmissions between aircraft, ends at 1000 ms. Positions must finish by then. A burst spends 4.64 ms on air. The latest permitted start leaves room for its booked air time and a 5 ms allowance before its window closes. Bench measurements found a worst case of 5.5 ms from the transmit command to the end of the burst, within that allowance.
Each change between windows takes 10 ms: 2 ms still listening on the old channel for a late burst, 5 ms to retune, then 3 ms listening on the new channel before its window opens. Those 3 ms also leave room to check the channel before a burst scheduled for the window’s first instant.
The parity of the second picks the channel.
A position uses channel A in an even UTC second and channel B in an odd one, both on the ground and in flight. A Status message reports what the Go can receive. It uses the channel opposite to the one a position would use in that second. The callsign always uses channel B, at the end of window 2.
ADS-L requires consecutive positions to change channel, and consecutive Status messages to do the same. The even-or-odd rule makes the position channel predictable from the time alone. A receiver listening on only one channel can still receive every other scheduled position. At takeoff or landing, two positions in a row can use the same channel, but only once at the change between ground and flight. This happens at nearly one change in two: 45 % of the takeoff and landing phases covered by the tests.
A 20 s cycle that starts from the serial.
Each Go follows a 20 s cycle. Its start, called c here, is an even second: twice the last decimal digit of its serial number, or c = 2 × (serial mod 10). skyblip.eu assigns that number at activation. For the example unit skyBlip Go 00012A, the hexadecimal serial is 298 in decimal. Its last digit is 8, so its cycle starts at second 16.
| Last digit of the serial | The cycle starts at |
|---|---|
| 0 | :00, :20 and :40 |
| 1 | :02, :22 and :42 |
| 2 | :04, :24 and :44 |
| 3 | :06, :26 and :46 |
| 4 | :08, :28 and :48 |
| 5 | :10, :30 and :50 |
| 6 | :12, :32 and :52 |
| 7 | :14, :34 and :54 |
| 8 | :16, :36 and :56 |
| 9 | :18, :38 and :58 |
skyblip.eu assigns serials in order from 1, spreading consecutive units evenly over the ten cycle starts. Each unit schedules its bursts at the same offsets from its own start:
| Second | On the ground | In flight | Channel |
|---|---|---|---|
| c | position | position | A |
| c + 2 | Status | position and Status | Status on B, position on A |
| c + 4 | callsign | position and callsign | position on A, callsign on B with its start in the first 190 ms of c + 5 |
| c + 9 | position | position | B |
| c + 11 | Status | position and Status | Status on A, position on B |
| c + 14 | callsign | position and callsign | position on A, callsign on B with its start in the first 190 ms of c + 15 |
| any other | nothing scheduled | position | A in an even second, B in an odd one |
On the ground, skyBlip Go 00012A schedules positions at :05, :16, :25, :36, :45 and :56 in each minute, Status messages at :07, :18, :27, :38, :47 and :58, and its callsign at the start of :01, :11, :21, :31, :41 and :51. In flight, it schedules a position every second. The Status and callsign schedule stays the same through takeoff and landing.
An exhaustive search chose these offsets to meet four rules:
- Ground positions are 9 then 11 s apart. A gap of 10 s would put consecutive positions on the same channel. The average remains one every 10 s, skyBlip’s reading of the ADS-L ground rate
- Positions and Status messages each alternate channels. Each channel carries a Status every 20 s. The callsign goes every 10 s
- The callsign is scheduled in an even second, when the position uses A and leaves B free for it
- The schedule keeps bursts from the same unit on the same frequency at least 100 ms apart, with no more than one in each window
The schedule also spreads ground positions and Status messages evenly. Across the ten cycle starts, each channel’s window in each second carries one scheduled burst of either type from a unit on the ground. A Status on A always falls in an odd second. A Status on B always falls in an even second. That leaves even-second A windows and odd-second B windows for ground positions. Positions alternating between those windows must be an odd number of seconds apart. That is why ground positions stay 9 then 11 s apart rather than exactly 10 s. Positions 10 s apart on alternating channels would put two ground bursts in a quarter of the windows and none in another quarter. At a busy airfield, those crowded windows would have more collisions.
The schedule always uses the unit’s own address, even when its messages carry an aircraft’s ICAO address. Setting or clearing that address in flight changes neither the timing nor the channel of a burst.
The millisecond is drawn again every second.
Within its window, a position’s start time comes from a hash: a calculation that mixes the unit’s address with the UTC second and spreads the result across the available milliseconds. Status and callsign messages use further rounds of the same calculation, giving each its own draw. Units sharing a scheduled second need not share a start time. If their bursts overlap, the next second gives them new draws.
For a 5 ms burst spread over the 550 ms direct slot, start times within 5 ms of each other give a rough collision estimate of 1.8 % per neighbour in range. Drawing again reduces the risk of the same pair colliding repeatedly. With a fixed instant per unit, two unlucky aircraft could overlap every second for the whole flight.
A position also needs a fix measured less than 500 ms before it leaves. The receiver solves on the full and on the half second, so a position drawn between 490 ms and the arrival of the half-second solution, about 590 ms, has no fix it may carry. It waits for that solution. If its instant has passed by then, the Go draws a new one over the rest of the window, from the address and the second, so units with the same receiver do not all transmit the moment the solution lands. Only 868.2 MHz is affected, because 868.4 MHz opens at 830 ms. About a quarter of the positions on 868.2 MHz move into 590 to 810 ms, and the collision estimate on that channel rises from about 2.8 % to about 3.9 % per neighbour. A position is lost only if the half-second solution arrives after 810 ms, the window’s last instant. Our open questions to EASA ask whether ADS-L means to impose this.
It listens before transmitting.
ADS-L requires listen-before-talk under the polite spectrum access rules of ETSI EN 300 220-1. Before the scheduled instant, the Go measures the burst’s channel for 200 µs. It averages nine readings as power, with the measurement ending no more than 2 ms before transmission. Below the threshold, it transmits. At or above it, the Go waits a random 15 to 250 ms in steps of 5 ms, one booked burst duration, then listens again. That is the ADS-L 4 SRD-860 C.2 backoff range, limited to waits that end at or before the burst’s latest permitted start in its window. If no wait of at least 15 ms fits, the burst is missed. The wait counts from the burst’s scheduled instant, and the address and that instant determine the draw.
The threshold comes from the standard’s rule for a 200 kHz channel, adjusted for antenna gain. At the radio chip, the channel counts as busy from −78 dBm. The antenna gain and feed loss used in this calculation come from the datasheet and an allowance, not from measurements on a unit.
A deferred burst stays in its window and on its channel. A deferred position is encoded again for its new instant using the newest fix. If the channel stays busy until the window closes, the burst is missed. On the ground, once 3 s have passed since its first busy assessment, the Go may force a transmission without listening, as ADS-L permits. It then stays silent for 2 s after the burst ends. It never forces a transmission in flight, where that silence would cost two positions.
| EN 300 220-1 parameter | Declared | The standard allows |
|---|---|---|
| Minimum channel measurement | 200 µs | at least 160 µs |
| Maximum gap between measurement and transmission | 2 ms | at most 5 ms |
| Method used to randomise a deferral | a hash of the address and the burst’s scheduled instant | |
| Deferral step | 5 ms, one booked burst duration | at least the measurement duration |
| Minimum and maximum deferral | 15 and 250 ms | |
| Maximum transmission duration | 5 ms | at most 1 s |
| Minimum silence on the same frequency | 100 ms | at least 100 ms |
Listening cannot prevent every collision. It can detect only a burst already on air, and it measures the channel at the Go’s antenna, not at the receiver. Another aircraft may hear two overlapping bursts even when neither transmitter hears the other. The check also favours nearby, stronger signals over distant ones. The timing design therefore relies on a fresh draw every second and the 1 % duty-cycle limit, rather than on listening alone.
A burst that missed tries again 2 s later.
A burst can miss its scheduled second because the fix is too old, the channel stays busy or the hour’s air-time budget is exhausted. It gets another opportunity 2 s later, in a second of the same parity and therefore on the same channel. If that channel’s window already carries one of the unit’s bursts, the retry waits for the next free second of the same parity. It gets opportunities every 2 s until it succeeds or the next message of its type is due. At that point, the Go gives up on the old one and counts the miss. On the ground, a position missed at c can be retried at c + 2, c + 4, c + 6 and c + 8. In flight, positions are not retried: the new position 2 s later already uses the same channel.
The callsign goes in the tail.
ADS-L Issue 2 has no callsign field. The Go sends its callsign in OGN-Tracker’s record format, with a start between 1000 and 1190 ms on 868.4 MHz. This is the end of window 2, outside the direct slot reserved for ADS-L messages and where ADS-L transmits nothing today. The callsign question explains that choice, and what changes once Issue 3 defines a field.
OGN-Tracker drops a callsign if it has no target with that address, so the position needs to arrive first. With the normal schedule in flight, that position is at most a second old. On the ground, the callsign follows a position by 4 or 5 s, well inside the time a receiver keeps a ground target between its reports.
1 % of any hour, enforced.
The Go declares a limit of 1 % of any hour on air for its use of the 868 MHz band. It keeps sixty one-minute counters and checks the budget before every burst. A position every second plus a Status and a callsign every 10 s uses 6 ms per second: 0.6 % of the time in flight, or 0.15 % on the ground. The normal schedule cannot exhaust the budget. If a fault does exhaust it, the Go blocks transmission rather than keep occupying the band.
GPS sets the clock, and the clock gates the radio.
The GPS receiver’s pulse per second, PPS, marks the edge from which the radio deadlines are calculated. The Go transmits only with a settled fix, valid UTC time, a PPS lock and an assigned serial number. If the pulses stop, it keeps the windows running for 60 s to receive, but transmits nothing.
The GPS receiver reports the UTC second in a data sentence that arrives hundreds of milliseconds after the pulse. Until then, that report still names the previous second. Dating a received burst from it could put the burst in the wrong second. Two Go units exposed the problem on the bench: a burst read 42:52.954 on the sender and 42:53.956 on the receiver. Received bursts are now dated from the UTC second opened by the latest pulse.
The firmware’s service loop runs every 10 ms, too slowly to open each radio window on time itself. Early bench captures showed window 2 opening 3 to 6 ms late at the median, and up to 120 ms late at worst. The firmware now gives the radio its next window as soon as the current one starts, with an absolute deadline calculated from the pulse. The radio can then switch without waiting for another pass through the loop.
- The serial’s last digit sets the start of the 20 s cycle
- An even second puts the position on 868.2 MHz, an odd one on 868.4 MHz
- On the ground, the Go schedules two positions, two Status messages and two callsigns every 20 s
- In flight, it schedules a position every second without moving the Status or callsign schedule
- It draws the instant within the window again every second
- It checks the channel before normal transmissions and gives missed bursts another opportunity 2 s later, except for positions in flight
Want to try it now, or get one?