Skip to content

Latest commit

 

History

History
124 lines (86 loc) · 5.29 KB

File metadata and controls

124 lines (86 loc) · 5.29 KB

Migration Guide: 1.x → 2.0 → 2.1

This guide covers what changed between version 1.x and 2.0 and what you need to do when upgrading.

Quick Summary

Area Change Action Required
Folder structure RADIO/ renamed to src/ in the repository None — the release ZIP still extracts to the correct SD card paths
Tile folders Native EthosMaps path is now the primary format Only if you had custom (non-Yaapu) tile folders in a non-standard layout
Settings Settings key may be reset between major versions Re-configure widget settings after update
MSP stack Complete rewrite with native V1/V2 support None — transparent improvement
Minimum ETHOS 1.6 required Update your radio firmware if below 1.6

Tile Folder Changes

What Changed

Version 2.0 expects native EthosMaps tiles under:

bitmaps/ethosmaps/maps/<PROVIDER>/<MapType>/<z>/...

with strict naming:

  • Provider: GOOGLE, ESRI, OSM (uppercase)
  • Map type: Satellite, Hybrid, Street, Map, Terrain (title case)

What Is NOT Affected

  • Yaapu tiles in bitmaps/yaapu/maps/ continue to work as before (auto-detected fallback for Google)
  • Tiles downloaded with the High Resolution Map Generator using output target b14ckyy ETHOS Mapping Widget are already in the correct format

Who Needs to Migrate

Only users who had tiles in a custom non-standard layout that was neither Yaapu nor the native EthosMaps format (1.0-beta). If you downloaded tiles with the recommended downloader tool, no changes are needed.

Migration Steps (if needed)

  1. Create provider folders under bitmaps/ethosmaps/maps/:
    GOOGLE/
    ESRI/
    OSM/
    
  2. Move each map type into the correct provider/type subfolder (exact case)
  3. Ensure the coordinate layout matches the provider:
    • Google / OSM: {z}/{x}/{y}.ext
    • ESRI: {z}/{y}/{x}.ext
  4. Restart the radio and verify in widget settings that the provider and map type are detected

Settings Reset

Widget settings are stored under a versioned key. When upgrading from 1.x to 2.0, settings will be reset to defaults. You'll need to re-configure:

  • Map provider and type
  • Zoom levels (min / default / max)
  • Top bar telemetry sensors
  • Units (metric / imperial)
  • Feature toggles (trail, waypoints, etc.)

Settings are preserved between minor releases (e.g. 2.0 → 2.1).

MSP Stack

The MSP waypoint download system was newly implemented in 2.0:

  • Native MSP V1/V2 protocol support
  • Dual transport: SmartPort and CRSF/ELRS with automatic fallback
  • Auto-retry on connection loss (5-second intervals)
  • INAV FC detection with version validation

New Features in 2.0

Features added since 1.0 that are available after upgrading:

  • CRSF/ELRS transport for MSP waypoint download
  • Active waypoint tracking with nav-mode coloring
  • BMP tile support
  • Touch panning with observation marker (fullscreen)
  • Multiple vehicle symbol styles (Arrow, Airplane, Multirotor)
  • Edge arrows when UAV or home is off-screen
  • Default position setting for map initialization

For details on all features, see the Overview.


2.0 → 2.1 Changes

Quick Summary

Area Change Action Required
Settings Fully preserved on upgrade None — all settings carry over
New file: compute.lua New library in lib/ None — included in release ZIP
State file: state.dat Zoom level, observation marker, default position now stored separately None — created automatically
Telemetry-lost indicator UAV and GPS overlay turn red when signal lost >5s None — automatic
Vehicle symbols Shadows reworked with semi-transparent fills None — visual improvement

No Settings Reset Required

Unlike the 1.x → 2.0 upgrade, version 2.1 preserves all existing settings. The internal storage schema has not changed, so no reconfiguration is needed after updating.

New Runtime State File

Version 2.1 stores volatile runtime state (zoom level, observation marker position, default map center) in a separate file at scripts/ethosmaps/state.dat on the SD card. This file is created automatically and survives radio restarts. It replaces the previous approach of storing these values in ETHOS widget storage, which had buffer size limitations.

New Features in 2.1

  • Telemetry loss detection — UAV symbol and GPS coordinates turn red when no position update is received for 5 seconds
  • Improved vehicle shadows — Arrow and Airplane symbols now have semi-transparent filled shadow backdrops
  • Smoother map panning — tiles and overlays (UAV, Home, observation marker) scroll together without jitter
  • Performance overhaul — heavy computation moved from rendering to a background scheduler, resulting in stable frame rates even with 60+ waypoints
  • Smarter MSP connection — error retries skip redundant FC re-identification when the flight controller is already known

Updating

  1. Download the latest release ZIP from GitHub Releases
  2. Extract to the SD card root — existing files are overwritten
  3. Reboot the radio
  4. Re-configure widget settings

See Installation Guide for full instructions.