> For the complete documentation index, see [llms.txt](https://docs.wingbits.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.wingbits.com/wingview/user-guide.md). # User Guide Everything the device does, and how to reach it. Setting one up for the first time is in [SETUP.md](broken://pages/2c3dcaf0495a22dc2330dc19eda34c9d0b192831). ## The controls A knob you can turn, four buttons around the rim at the compass points, and the screen itself. Everything is reachable from those, and everything is also reachable from a web page if you would rather not touch the device. {% hint style="info" %} **One difference between the two boards.** The Elecrow's knob also presses; the Waveshare's does not - its knob is flat to the body and there is nothing to push. Everything in this guide works on both. Where the Elecrow's press is a shortcut, it is called out as one. {% endhint %} ### The knob **Turn** does one of two things depending on which mode you are in. In zoom mode it steps through the range rings. In scan mode it moves through the aircraft on screen, one at a time, going clockwise by bearing. **Hold W** switches between those two modes. A message appears briefly in the middle of the screen telling you which one you are now in, then fades. *On the Elecrow you can press the knob instead, which does the same thing.* Turning clockwise zooms in. If you are used to a map application where scrolling up zooms out, this will feel backwards for about a minute. ### The four buttons **N** opens the settings menu. Holding it opens the status screen instead. Pressing N again closes whichever is open. **S** cycles the view: map, radar, ATC. See below. **W** hides and shows the two information blocks over the map. A brief message says `INFO OFF` or `INFO ON`. If you have an aircraft selected the blocks stay visible regardless, because a selected aircraft with no readout is pointless. Deselect it and they will go. **Holding W** switches the knob between zoom and scan, as above. **E** is not assigned yet. Pressing it says `TBD`. **Holding E** puts the device to sleep straight away, without waiting out the idle timeout. A brief message says `SLEEPING`. The screen goes dark - or shows a clock, if you have asked for one and the device knows the time - and it stops polling until you touch it again. Use it when you are finished looking and would rather not spend the day's API allowance on a screen nobody is watching. It is a hold rather than a press because the rim is buttons and the middle is aircraft: a finger aimed at a plane near the right-hand edge lands on E, and a short press there would blank a screen you were reading. ### Touch The screen is a touchscreen, and **touch does everything the knob press does** - which is how the board without a knob press works at all. | where you are | tap | | ------------------- | ----------------------------------------------------------------------------------------------------------------------------- | | the map | an aircraft selects it and switches to scan mode; empty map clears the selection | | the settings menu | anywhere in the panel acts on the highlighted row, the same as pressing the knob would. Turn the knob to choose the row first | | the status screen | anywhere closes it | | a confirmation card | **touch and hold**, see [the erase page](#the-erase-page) | Tapping in a menu deliberately acts on whichever row is already highlighted rather than on the row under your finger. The rows are close together on a small screen and a fingertip covers most of two of them, so aiming at nothing cannot miss. Whether tapping empty map also leaves scan mode depends on how you got there. If you tapped an aircraft to enter scan mode, tapping away is plainly "never mind" and returns you to zoom. If you chose scan mode deliberately - by holding W, or by pressing the knob on an Elecrow - it stays, because a tap that missed a small moving target is the common case and should not undo a deliberate choice. ## The three views **Map** is the default. A dark street map under altitude-colored aircraft silhouettes. On a very busy screen those silhouettes become plain dots. See [when the aircraft turn into dots](#when-the-aircraft-turn-into-dots). **Radar** is a phosphor green display with a sweeping line and a data block beside each contact. It looks like a radar screen because that is the point. **ATC** is closer to what a controller sees: white squares rather than aircraft shapes, short history trails behind each one, and leader lines to the data blocks. The view is remembered across restarts, as is the range, so the device comes back the way you left it. Brightness, units, trails, the sleep timeout and whether the information blocks are showing are remembered too. ## Ranges Seven rings: 3, 6, 10, 15, 25, 50 and 100 nautical miles. The number shown is the radius, so the outer edge of the circle is exactly that far away. Two things change with the range. The map disc underneath swaps for one drawn at that scale, and the device asks the API for a matching radius. Wider views also poll less often, because an aircraft crossing a 100 NM display takes fifteen minutes and there is nothing to be gained from asking every two seconds. Aircraft on the ground are only drawn at 25 NM and below. Further out they are clutter, and at a busy airport there can be a lot of them. ### When the aircraft turn into dots Above roughly 110 aircraft on screen the display switches every contact to a plain dot, and it switches back once the count falls below about 85. The two numbers differ on purpose, so that traffic hovering around the threshold does not flicker between the two styles every few seconds. This is not a fault and nothing has been dropped. Every aircraft is still there, and the one you have selected keeps its shape so you can still see what it is. Trails get shorter rather than disappearing, because movement is the point of a wide view. The reason is legibility rather than speed. At that density the little directional shapes overlap into a mess, and a dot has no direction of its own, so a curving trail behind it reads as an aircraft turning instead of a bent arrow. Zoom in one stop and the shapes come back. ## Settings Press N. Turn to move, press to change. The rows are ordered by how often you would touch them. **Location** switches between the places you have set up. Press to move to the next one. Switching re-centers the map, swaps the discs, and clears the trails, because a trail that spans two locations shows an aircraft apparently flying between them. **Trails** turns the short history behind each aircraft on and off. **Demo** cycles how demo mode behaves: automatic (the default), always on, or off. Automatic means it appears only when there is no live feed. **Sleep after** is the screen timeout: 15, 30 or 60 minutes. The screen goes dark - or shows a clock, see the next row - and polling stops, so a sleeping device costs nothing. Touch anything to wake it. Holding **E** sleeps it immediately, without waiting the timeout out. The scope comes back empty for a second or two rather than showing what was there before, because nothing was watched while it slept and positions from then would be a picture of the past. **When asleep** chooses what the panel does once it sleeps: go dark, or show a clock. The clock needs the time, which the device learns from your network and from the browser the first time you open one of its pages, so this row reads `clock (no time yet)` on a device that has never managed either - and such a device goes dark rather than showing a face with nothing on it. While the clock is showing, **turning the knob changes its brightness** and nothing else, with the level shown for a couple of seconds as you turn. That level is remembered separately from the brightness the scope uses, because a clock across a dark room and a scope you are reading up close are not the same screen. It also means the knob no longer wakes the device: touch the screen for that. The clock reads the hour the way your browser does, 12 or 24 hour, unless you have said otherwise on the settings page. **Brightness** is the only row with a sub-mode. Press to start adjusting, turn to change, press again to finish. It never goes fully dark, because a black screen reads as a dead one. **Units** switches between nautical miles and kilometers for everything displayed. It does not change the ranges themselves, only how they are labeled, and kilometer values are rounded to the nearest half so the top of the screen is not full of decimals. **Wi-Fi setup** brings back the device's own network so you can reach its web pages. Useful if your wifi password changed, or if the setup window closed before you got to it. **New passphrase** replaces the page passphrase. Use it if somebody has seen the old one, for example if you showed the status screen on a video call. The new one appears briefly on screen and afterwards lives on the status screen. **Close** closes the menu. ## Status screen Hold N. This is the first place to look when something seems wrong. | row | meaning | | ------------- | ------------------------------------------------------------------------------------------------------------------- | | `feed (rate)` | `acquiring`, `ok`, `throttled`, `api down`, `no internet`, or `no auth`, with how often it is asking in parentheses | | `view` | map, radar or atc, and the current ring | | `contacts` | how many aircraft the device is holding | | `station` | the current location's name | | `plan` | your API plan and the requests a minute it allows | | `quota` | requests used this month against the allowance | | `build` | firmware version | | `address` | where the device's web pages are on your network | | `page pass` | the passphrase for that page | | `free` | free internal memory, which is the scarce kind | The rate in parentheses beside `feed` is worth knowing about, because it is sometimes slower than you expect and that is deliberate. Every plan allows a certain number of requests a minute, and at the closest ranges the device would ask more often than the plan permits if nothing stopped it. So it asks as often as it is allowed to and no more. If the number looks high for the range you are on, that is what you are seeing. `acquiring` means the device has not finished a request yet, which is normal for the first few seconds after a restart. It is deliberately not `ok`: nothing has been asked, so nothing can be reported. There is no coordinate on this screen. That is on purpose, so the device can be photographed or filmed without giving away where it is. If you need to check the exact position it is measuring from, the locations page links each one to a map of where it sits. `api down` and `no internet` are the same failure to the device and a completely different one to you. It tells them apart by checking whether two well-known addresses answer, the same trick your phone uses to spot a hotel wifi login page, and only after the feed has already failed. The small arc around the N button is the same information at a glance. Nothing means healthy. A quarter, a half or a full ring means increasing trouble, and the size changes as well as the color so it is readable without relying on color vision. ## Demo mode When the device has no live feed it shows recorded Los Angeles traffic instead of an empty screen. Three things make that obvious: an amber palette instead of the normal colors, a DEMO MODE banner, and a map of Los Angeles, which is unmistakably not where you are (unless that is actually where you are, in which case, sorry). It is automatic. As soon as a real response arrives it hands over. You can force it on or off from the settings menu, which is useful for showing the device to somebody. ## When the map is missing Bare rings and aircraft, with no imagery behind them. Nothing appears on screen to explain it: everything else draws as usual and the map is simply absent. Usually the location has no maps built yet, and the locations page says which of your locations have them. A build that did not finish counts as none rather than as a partial one, so if you stopped one part way, start it again. The other cause shows itself differently: the map is there at wide ranges and **disappears as you zoom in**. That means the device is using a set built for a nearby point rather than the one you are centered on. Maps are drawn for one coordinate, with the outer edge of the disc at the outer ring, so a set from somewhere else puts every road wrong relative to every aircraft, which looks fine and is not. The device refuses it rather than showing that. The tolerance is three percent of the range on screen, so it tightens as you zoom in: about 5.5 km at 100 NM, but only 170 m at 3 NM. A map built a kilometer from where you are centered will hold at 100 and 50 NM and vanish below that. Two ways to get there: two of your own locations close enough that each matches the other's maps, or being near Los Angeles, where the demo maps that ship with the device are centered. Building maps for the location you are actually using fixes both. ## The device web UI Reachable at the device's address on your network, or on its own network during setup. The address and passphrase are both on the status screen. There are nine pages: | link | what it is for | | ----------- | -------------------------------------------------------------------- | | `home` | status: the feed, your plan, quota, address, uptime and build | | `traffic` | the aircraft nearest you right now, and which are about to be closer | | `settings` | the same settings the device's own menu holds | | `locations` | adding, switching and removing locations, and building their maps | | `network` | wi-fi and the Wingbits API key | | `firmware` | the version it is running, updates, and the beta channel | | `log` | what the device has been saying, ready to send to support | | `remote` | the knob and the four buttons, as web buttons | | `erase` | wiping the device, always last in the row | Every page carries the same row of links at the top so you can move between them without typing an address. `erase` is last deliberately, with a gap before it, so there is nothing after it to mis-tap towards. On a phone the row wraps onto two lines, which is expected. Whichever page you are on is shown in that row without being a link, so it also tells you where you are. There is a restart button at the bottom of `home`. Almost nothing needs it: wi-fi, locations and the API key all take effect immediately. ### The home page Where the device says how it is doing: whether the feed is working, which API plan the key belongs to and how much of its allowance is left, the address to reach it at, how long it has been running, and the firmware build. It also reports contacts as two numbers, **seen** and **drawn**, and they are usually different. The scope draws only what fits inside the range ring, and aircraft on the ground are not drawn above 25 NM - at a busy airport that is dozens of them. So 243 seen and 183 drawn is a working device at 100 NM, not a fault. Before the device is set up, this page is a checklist instead - the steps you still have to complete, in order, with the forms for each. It stops being a checklist once they are done, so a working device shows status rather than an empty list of ticks. ### The traffic page What is near you right now, as a page rather than a screen: the reason the device exists is to answer "what was that overhead", and you are not always in the room with it. **Coming your way** is the top section - aircraft whose projected path brings them within a distance you choose, nearest in time first. The distance is a menu, up to 10 NM. Ten miles is not close, and the section is not pretending it is: at 400 knots that setting is about ninety seconds of warning, which is enough time to walk outside. Two icons say what you are likely to notice when it gets there: | icon | means | | ---- | ------------------------------- | | 👁️ | probably visible in a clear sky | | 👂 | probably audible where you are | Both are estimates from the aircraft's type, its altitude, how far above you that leaves it, and how far off it will pass, capped so that nothing distant is ever marked either way. They say *probably*, and the tooltips say so too. **Nearest now** is a table of what the device is currently holding, closest first, with altitude, whether it is climbing or descending, speed and how far off it is. Aircraft on the ground are hidden unless you tick **Include aircraft on the ground**, which is remembered in your browser - at a big airport they would otherwise fill the table. Distances follow the units setting, so if the device is in kilometers the page is too. **The location is named at the top**, so you know which of your locations the page is talking about, with the next refresh counting down beside it. **Everything here is extrapolation**, which the page says at the bottom in its own words: one position, one speed and one direction carried forward in a straight line from whenever the last poll happened. An aircraft that turns or levels off makes it wrong immediately and the page cannot know until the next poll. #### While the device is asleep The page still works, and this is the part worth understanding. A sleeping device is not polling, so to answer the page at all it has to start again - and that spends your API allowance on a screen nobody is looking at. So it is bounded, and the page tells you when it is happening: * It polls **every 30 seconds** at a fixed 40 NM while a page is watching, rather than at the device's usual rate. * It stops on its own about **90 seconds** after the last time the page asked for anything, so closing the tab or walking away ends it. * It is capped at **90 minutes of watching a day**, and the page says how much is left. * A banner explains all of this while it is going on. You can collapse it, and your browser remembers that you did. When the budget runs out, or the watching window closes, the figures stay on screen but are marked as old rather than being silently refreshed. **Keep watching** starts it again if there is budget left. While the device is awake, none of that applies: the page is served from the polls the device is already making, at whatever range it is showing, and costs nothing extra. ### The settings page The same settings the device's own list holds, with room to show them: the clock's 12 or 24 hour reading, what the panel does when asleep, the sleep timeout, units, trails, demo, and both brightness levels. Change what you like and press **Save**. It is the same setting either way - the device keeps one copy, so turning the knob changes what this page shows, and saving here changes what the device does, immediately. The clock brightness is worth knowing about here in particular: on the device that level can only be reached by turning the knob while the panel is asleep in front of you. Wi-Fi, the API key, locations and erasing anything are on their own pages. ### The network page Wi-Fi and the Wingbits API key. Neither is ever shown back to you. The key field names the stored key by its **first eight characters** of thirty-five, so you can tell which one this device is using if you look after several; the rest is never shown, and eight characters cannot be used for anything. If a key is being rejected the page says so, rather than leaving you to work out why nothing is arriving. Both forms show "already set, leave blank to keep", so changing one does not mean retyping the other. ### The locations page Adding, switching and removing locations, and building the maps for each - they are one page because a location without maps is half a job. Removing a location asks first, and names it. Worth reading rather than clicking through: the maps built for it go too, and rebuilding those takes a few minutes in a browser where retyping the location takes seconds. You cannot remove the last location. To move a device somewhere else, add the new place first and then remove the old one. The map has to be centered on something. The heading shows how many you have and the limit, as `Locations 3 of 8`. At eight the form is still there but greyed out, saying so, rather than disappearing and leaving you looking for it. Each location links to a map rather than printing its coordinate, so a screenshot of the page does not give away where your places are. ### Building maps Each location has a **build map** button, which says **rebuild map** once it has them. Building takes a couple of minutes per location and needs the browser you are using to have internet access - the device cannot draw maps itself, so your phone or laptop does the work and sends the result over. Keep the page open until it finishes. The device shows a progress count and is unavailable until it is done. If it fails, the device returns to normal and the page says why. ### The remote `/remote` on the same address gives you the knob and the four buttons as web buttons. It was built for filming: pointing a camera at the device is much easier when your hand is not in the frame. These are the device's real controls, and the settings menu is one of the things they reach, so it is not a page to leave open. A press from here counts as using the device, the same as touching it, so the remote wakes a sleeping screen and stops one going to sleep while you are driving it. ### The log page Everything the device has been saying, oldest first, in a box you can select. It opens with a short header naming the device, when the log was captured in **both local time and UTC**, the build, the address, and how long the device has been up. The two clocks are there because a problem usually involves more than one report: local time is the one you remember, UTC is the one that lines up with everybody else's. Times only appear once the device knows what time it is, which it learns from your network and from the first browser to open one of its pages. Before that the header says so. Two buttons: **Copy all** and **Download**, which saves it as a text file. Both are disabled until the whole log has arrived. A truncated log sent to support is worse than none, because nobody can tell it was cut short. There is also a **Show additional details (for support)** checkbox. It reveals rows that are always being recorded but are hidden by default because they repeat: what is left of the API allowance, and the update checks a sleeping device makes on its own. Nothing is switched on by ticking it, and the device behaves identically either way. **If you are sending a log to support, tick it first** - those rows are usually the ones that answer the question. It is scrubbed before it is shown: the wifi network name, the API key, the page passphrase and anything coordinate-shaped are replaced with ``. The page exists to be sent to a stranger, so it is written as though it already had been. ### The firmware page Shows the version the device is running, and a **Check for update** button. If a different build is waiting it installs immediately and restarts into it, and the page reports progress while that happens, showing the phase and a percentage, so you do not have to watch the device. The device shows its own card while it writes. The picture jumps about during the first ten seconds or so, while it clears space; that is expected on this display and not a fault. After that it settles and the progress bar is readable. **Keep the power on** until it restarts. If a new build will not start, the device puts the previous one back by itself. That needs nothing from you. **Channel: stable or beta.** The page shows which one you are on. Stable is the default and is what you want unless you have a reason not to. Beta installs builds that arrive earlier and are less tested; switching to it opens a short list of the real risks first, and switching back is one press. A switch takes effect at the next check rather than immediately, and going back to stable may put you on an *older* build than the beta you were running, which is the point of going back. ### The erase page Three options, least destructive first, each naming exactly what it keeps: | option | erases | keeps | | -------------------------- | ------------------------------- | ----------------------------------------------- | | **Forget Wi-Fi** | the network and password | the API key, the passphrase, locations and maps | | **Wipe Wi-Fi and API key** | those, plus the page passphrase | locations and maps | | **Factory reset** | everything | nothing | Each asks you to type a different word in capitals, so a habit formed on the smallest cannot answer the largest. Then the device shows a confirmation card and waits for you to answer it **on the device itself**. **To confirm, touch the screen anywhere and hold for about two and a half seconds.** A red ring sweeps round the outside edge of the display as you hold; when it closes, the erase begins. Let go early and nothing happens. *On the Elecrow you can press the knob instead, which confirms immediately.* **While it erases, the screen says ERASING and stops responding.** That is normal. A factory reset takes a minute or two, because it clears the whole map storage rather than a few settings; the other two are over in a moment. The device restarts itself when it finishes. **Do not unplug it** - power lost partway through leaves the storage half-erased. Nothing is erased from the web page alone, which is what stops a stray tap or a page left open on somebody else's phone from doing it. A quick tap is not a confirmation - only the hold is - so brushing the screen cancels rather than erases. If the screen is asleep it wakes up for the confirmation. Turning the knob, tapping, or simply waiting cancels, and nothing is lost. **Forget Wi-Fi** is the one to reach for least often. Changing networks does not need it: the wifi form takes new details directly and shows "already set, leave blank to keep". **Wipe Wi-Fi and API key** is the one for handing a device to somebody else. It arrives with the maps for its location already built, and the new owner joins their wifi and enters their own key. ## Sleep and power The screen sleeps after the timeout in settings, which is **15 minutes** unless you change it, with 30 and 60 as the other choices. Polling stops with it, so a sleeping device makes no API requests. **Hold E to sleep it now** rather than waiting the timeout out. A sleeping device either goes dark - looking exactly like one that is switched off - or shows a clock, depending on the **When asleep** setting. Touch it and it comes straight back either way. **While the clock is showing, the knob belongs to the clock**: turning it changes the clock's brightness and nothing else, so waking the device means touching the screen. On a dark device the knob wakes it as before. The one exception to "no API requests" is the traffic page: a browser watching it can ask a sleeping device to start polling again, within a daily budget, and the page says so while it is happening. That is covered under [the traffic page](#the-traffic-page). While it is awake but untouched for five minutes, polling slows from a few seconds to thirty. The screen stays exactly as it is and aircraft keep moving, because the display carries on projecting their positions between updates. Touch anything and it speeds back up immediately. This is what keeps a device left running on a desk from spending your monthly API allowance on an empty room. The display says so, in one of two ways. If the information blocks are showing they fade to about 60 percent. If you have them turned off, a block appears at the top reading `ECO` and `updates every 30 s`, so a plane that has not moved in a while is explained without you having to reach over and find out. Either way it clears the moment you touch anything. **That first touch only wakes it.** There is nowhere on the glass that does nothing - the rim is the four buttons and the middle is the aircraft - so the tap that means "I am back" would otherwise also select something, change the view, or open the settings panel, leaving you to undo it before you could start. The same holds for waking a clock, where the risk is sharper: the tap that woke it could otherwise land on E. The first press after a long pause is used up on waking, exactly as the title screen at boot uses up the press that dismisses it. Press again for whatever you actually wanted. ## How the device gets the time The device has no clock of its own and no battery to keep one running, so it starts every boot knowing nothing about the time and learns it twice over. **The time itself comes from the network.** It asks your router first - most hand out a time server along with the address they give the device - and falls back to `pool.ntp.org` if yours does not. That is the same mechanism your computer and phone use. **The time zone comes from your browser**, the first time you open one of the device's pages. There is no third source for it: the alternatives are asking you to type something like `EST5EDT,M3.2.0/2,M11.1.0/2`, or shipping a database of the world's cities to a device with no room for one. The machine already rendering the page knows the answer. **What it sends is a rule, not a place.** The device receives something of the form `EST5EDT,M3.2.0/2,M11.1.0/2`, which says that clocks here run five hours behind UTC, four in summer, and change on the second Sunday in March and the first in November. Millions of people share that exact string. It says nothing about where you are beyond which of about forty timekeeping conventions your part of the world uses, and **it never leaves your network** - the page is served by the device, on your wi-fi, and the answer goes straight back to it. **It corrects itself.** Every page load recomputes the rule and sends it only if it disagrees with what the device is holding, so a device that moves - sold on, taken to another house, carried to another country - is right again the first time somebody opens its page there. A clock that is an hour out is a fault rather than a preference, so this one is not left to be noticed and fixed by hand. Whether the clock reads 12 or 24 hour is asked the same way but **only once**, because that one *is* a preference: a household with a 24-hour laptop and a 12-hour phone would otherwise flip the clock back and forth depending on who looked at it last. Set it on the settings page and it stays set. Until the device has been told, times show as UTC and say so, and the idle clock stays dark rather than showing a face with nothing on it. ## Firmware updates Updating happens over wi-fi. There is nothing to install and no cable involved. **On its own, while it sleeps.** Half an hour after the screen goes dark the device looks for a new build, and then again every one to three hours. If it finds one it installs it and goes back to sleep. Nothing lights up and nothing is interrupted, which is why sleep is the moment it does this - the screen is already off, so the write and the restart cost you nothing to watch. The exact timing varies from one check to the next. **Or when you ask.** The firmware page has a **Check for update** button, described above. Press it and the device fetches whatever is waiting, compares it with what it is running, and installs it if they differ. While the screen is awake this is the only time it looks. **How you know it happened.** A ring around the **S** on the scope, in one of two colors. **Cyan means it updated.** Nothing to do. It clears itself after about half a minute. If the update happened while the screen was asleep, the half minute starts when you wake it, so waking the device does not cost you the message. **Orange means it gave up on an update.** A build failed to run three times, so the device has stopped trying to install it and put the working version back. Nothing is broken and nothing is lost, but it will not try that build again on its own. Press **Check for update** on the firmware page, which installs it regardless, or send the log to support. Unlike the cyan one, this ring waits until you touch the screen to dismiss it, because it is telling you about something that will not resolve by itself. **Which version you are on** is on the status screen, by long-pressing N. That is the first thing anyone helping you will ask for. **If the new firmware will not start**, the device notices and puts the previous version back by itself. You may see it restart twice. Nothing is lost, and that needs nothing from you. Your locations, maps, wi-fi and API key are untouched by any of this. Updates never clear settings. If an update ever fails while the device is otherwise working, [RECOVERY.md](broken://pages/eac483f9ac709cd462b74aa05e47368c73e6411c) covers it. The answer is almost always to restart it. ## When something is wrong [**Troubleshooting**](broken://pages/fef3fdd03700af60243a7f6a941805efaaa5c212) covers the common symptoms: a dark screen, demo traffic that will not clear, a missing map, a page you cannot reach, an erase that appears to do nothing. Updates that fail have their own page, [**Recovery**](broken://pages/eac483f9ac709cd462b74aa05e47368c73e6411c), because the answer there is one restart and worth saying on its own. ## Known rough edges * Frames take around half a second, so the radar sweep steps rather than glides, and a very quick tap is occasionally missed. * Altitude is shown by color alone, which does not work for everyone. * A short press of E does nothing yet; holding it sleeps the device. ## Privacy and security Two questions come up often enough to have their own page: **what can be shown to other people**, and **what the device talks to on your network**. Both are answered in [Privacy and security](broken://pages/64bc27d00dd25ff71974772982e7e47d2600fe3c), including how to verify the second for yourself rather than taking anybody's word for it. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.wingbits.com/wingview/user-guide.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.