1) Study Operating Manual

The Operating Manual is your most detailed source of information.

Get a basic understanding of the system architectures.

Study the high-level presentation of Marvelmind RTLS.

2) Study Placement Manual

Learn how to place stationary and mobile beacons properly and meet the essential requirement – the line of sight between the stationary and mobile beacons – with the least amount of equipment.

3) Study other sources of help

There are many other helpful documents and guides, including those made by our users.

We also have a developed YouTube channel for those who prefer watching to reading.

Study in detail and avoid typical mistakes.

4) Install required drivers

Download and install the required STM32 driver.

Optionally, install the DfuSe programmer.

5) Install the latest SW pack

Download and install the latest SW pack. All beacons, modems and the Dashboard must have the software only from the same SW pack.

Remember to press the Default button to default the settings.

6) Integrate with your devices

After achieving perfect tracking in the Dashboard, start integration with your external devices (robots, drones, etc.)

Step 1: Check Operating Manual

The Operating Manual is your primary source of detailed information about the Marvelmind Indoor “GPS” system. Download, study it, and follow the recommendations before deploying any Marvelmind system. If anything is unclear, check the Help page.

Step 2: Check Placement Manual

Another essential manual to start with is the Placement Manual, which explains where and how to place stationary, mobile beacons and the modem for different scenarios: robots, drones, vehicles, people, etc.

Step 3: Check other sources of help

Marvelmind List:

  • Marvelmind Robotics List – a list of companies operating in the fields relevant to autonomous robotics and precise indoor positioning

Manuals and Application Notes:


Placement of beacons, submaps, and maps:

Selection guides:
  • Beacons comparison – a table summarizing key differences between different types of beacons
  • Selection Guide – a slide set aiming at helping you in creating the configuration of Indoor “GPS” suitable for your particular task and requirements

Network planning and implementation:

White papers and training:


    Use cases:

    How to:

    Other helpful photos, PDFs, 3D models, CAD files, STLs, STEPs, and archives:

    Step 4: Install drivers

    Download STM32 driver

    Download and install STM32 driver on your computer once

    The driver is required on your computer for the processors used in beacons and modems to be visible in Windows.
    Linux already has it. Thus, you don't have to install it.

    Download DfuSe programmer

    Download and install the DfuSe programmer on your computer once

    The DfuSe programmer is required if you decide to upload the SW via DFU.

    DFU SW is the lowest lever SW and can be uploaded even to an empty processor. But use it with caution because there is no HW vs. SW control, i.e., you can upload any SW to any HW, and in case mistakes are made, the wrong SW can in some cases, damage the hardware.

    A detailed summary of working with DFU is given in the DFU update troubleshooting manual.
    If doesn’t help:
    • Try different Windows vs. DfuSe combinations
    • Try different USB ports.
    • Try different computers
    • Try clean DfySe installations
    Short links:

    Installing DfuSe can be an issue in some Windows configurations. See comments from one of the customers:

    “I discovered a solution in an online forum. Unzipping the driver file and running the executable isn’t enough to get the device to register in DFSuE mode. I had to dig deeper into that folder and install a separate windows 10 driver. There was no record of this information in any set of MarvelMind directions. I am including the link to the forum for your company’s further use in expanding any explanations or instructions. “


    Step 5: Install the latest SW and API

    Download SW/API pack

    Download the latest SW pack

    This is the latest software (SW) pack required for any Marvelmind hardware (HW). It contains the SW for all Marvelmind beacons and modems except for the Super-Modem. The pack also includes the API.

    For the Super-Modems SD card, use a separate SW file.

    API is included in the same SW pack as the main SW. Just download and use it.

    Protocols are described in the Marvelmind protocols and interfaces document.

    Watch the unpacking and setting up video for Starter Set Super-MP as an example to have your experience with the Marvelmind system smooth.

    SW updates:

    Some releases ago, we introduced a system of constant updates. Thus, we don’t wait for major or minor updates. We update the pack as soon as there is an update in the following manner:

    • We make a new feature => increase the SW version number => upload the new SW
    • We identify a bug => fix the bug => increase the SW version number => upload the new SW

    Thus, the best and latest SW is always available on the site without delay. The SW release changes below are just the latest changes. Not between the SW versions, not version-to-version, but just the latest changes introduced to the SW pack in the constantly evolving SW pack.

    Always update the SW from the same SW pack upon getting the equipment. Update the SW to all beacons, modem, and the Dashboard. Always from the same SW pack only. And remember to press the Default button to have the default settings for each piece of equipment.

    SW release v7.701 (28.Nov.2023):

    • It is a minor bug-fixing release

    Bug fixes:

    • USA radio profile in Linux returned a garbage. Fixed

    SW release v7.700 (05.Sep.2023):

    • It is a major new SW release that brings many new SW features, improvements, and bug fixes
    New features:
    • Multi-Modem Architecture is commercially available and is being implemented on one of our customers (450x450m T-shaped warehouse with 120+ simultaneously running forklifts. Multi-Modem Architecture allows virtually unlimited coverage and capacity at the same time: thousands of mobile beacons (hedges) and hundreds of thousands of square meters of area
    • New, improved, and more advanced version of IMU post-processing architecture without needing a Radio Head Remote (RHR). In the new version, the mobile beacon works with the main modem on one radio frequency and offloads the fast IMU data to the IMU modem (RHU) on another radio frequency, thus eliminating the need for the RHR
    • The modem can now search and find over the radio the lost beacons over multiple potential radio channels and radio profiles. For example, you changed some radio settings to a beacon and applied the changes, but you lost or forgot those changes. Now, it is easier to find the beacon over the radio. You can always find and change the settings back to default over the USB, of course, but often, the beacons are not physically easily accessible
    • The Dashboard can also wake up beacons on the current radio profiles and those from 2-3 years back. As well the automatic waking up of these beacons when the system is turned on for the first time
    • A new and simple variant for geofencing zones – just a radius around a mobile beacon. Regular geofencing zones assume drawing a real zone with a shape and coordinates of the corners – similar to serving zones
    • Calibration submaps are now supported in 3D also (SW feature MMSW0015). Choosing which of the distances is used for the calibration is possible as well. Previously, it was supported in 2D only with a single distance
    • In the embedded oscilloscope, it is possible to choose how many location updates are skipped between the measurements. It helps to debug complex IA or MF NIA cases where multiple ultrasound frequencies with high distance ratio between beacons can affect each other (“overflows”)
    • Handover type 3 is now supported in NIA. Type 3 is when the measured coordinate is weighted in the service zone based on the coordinate from Service Zone 1 and Service Zone 2. Handover type 3 is the most smooth type of the handovers
    • API can now work via UART as well – not only via USB
    • Now, there is an option to set which frequencies in the IA the hedge will be listening to: all available (up to 8 frequencies) or only those that belong to the serving submaps (for example, 2 or 3 frequencies). It increases the update rate because less filtering is required, but it can decrease the stability of the system and increase the hard handover time
    • Detailed and deep settings of the ultrasound distance trigger can be configured in a config file
    • It is possible to use the Oscilloscope in the constant mode as an ultrasound microphone – not triggered by the time resets. New tick in the Oscilloscope window – the bottom part of the window
    • GPGGA packet of NMEA now has the option to send the hedge address along with the coordinates instead of the “differential reference station ID”. Without this, a basic NMEA protocol cannot distinguish coordinates streamed from different mobile beacons
    • A new feature allows to warn when the stationary Super-Beacons are not placed on the wall with the USB facing down. The feature allows to identify which direction the transducers TX1-TX5 are facing, thus helping significantly with deploying the maps when required to use non-default settings with only some of the transducers enabled
    Boxie robot:
    • A new separate command for a 90-degree turn
    • Improved GUI with a large number of waypoints
    • Significantly improved the PID performance for even more stable driving
    • Fixed the Pause command


    • Improved algorithm and quality of the IMU post-processing tracking
    • By default, the height of 2D submaps is not 10 meters as it used to be, but it is equal to the height of the stationary beacons (if they are above the floor as assumed in the default settings), and the floor is assumed to be 0 meters. Also, not the thickness of the layer is set, but the bottom level’s height and the top level’s height
    • Improved the Realtime Player (RTP). Its settings moved to the right menu. A new option for RTP-2 – when more data is available, it fixes errors done with the RTP-1 – when not enough data was available to choose between different location candidates correctly
    • Separate SW for Industrial-RX. Previously, Industrial-RX and Industrial Super-Beacon shared the SW, and it could lead to confusion
    Bug fixes:
    • Fixed the log of raw distance data from the modem (some data was missing) and the log of coordinates (some data was duplicated)
    • The angle in the Paired Beacons configuration with Ultrasound+IMU angular sensor fusion is fixed. Previously, there could be issues when the angle is close to 90 degrees, or the hedge is turned upside down
    • New licensed optional feature MMSW0016 for UDP streaming from the Dashboard and the Super-Modem. The license is per modem. So, for example, if you have the Modem v5.1, you get the license, and the Dashboard will do the UDP stream of location data to your fixed IP address anywhere in the world. If you have the Super-Modem, you don’t need the Dashboard. The Super-Modem will do it with the help of the embedded computer

    • MMSW0005 is now called the “Advanced SW pack”. Earlier, it was called “SW v7.1xx pack”, but it changed the name because it is also valid for new releases – not only for v7.1xx. To identify beacons or modems with the pack enabled, there is an L at the end of the version, for example, v7.700 vs. v7.700L. If the license is available to all network elements, then the Dashboard’s version changes to v7.700L as well. Otherwise, it remains v7.700, thus indicating that some licenses may be missing
    Download SW for Super-Modem

    Download Super-Modem SW

    Required for Super-Modem only - the latest stable SD-card image and HEX file for Super-Modem. It is separate from the main SW pack because of its large size - the SD card image (1Gb)

    Download Robot v100 SW

    Download SW for Robot v100

    The latest SW pack for Robot v100 (1.8Gb)

    Download SW for robot Marvelmind Boxie

    Download SW for robot Boxie

    The latest SW pack for robot Boxie. It consists of two parts

    1. Marvelmind Boxie SW – unzip files and save them to a USB stick. Enter the USB stick into the Boxie’s rear USB ports and press the reset button on Boxie. The Boxie SW will be updated automatically. The archive contains Odo board SW, modem SW, Dashboard, and SW for internal mobile beacons (“hedges”) – separate versions for left and right. Left – from the robot’s point of view. For the first time, Marvelmind Boxie SD card SW update is required
    2. Marvelmind Boxie SD card SW – use only when the SD card update is needed. The update process requires a screwdriver and opening of the top plastic cover around the display
    3. Marvelmind Boxie API

    For more information, check and follow the Marvelmind Boxie Operating Manual.

    The most basic requirements

    • Always use SW from the same pack only: Dashboard SW + Modem SW + Beacon SW
    • Don’t mix SW from different SW packages. If not from the same SW pack, the SW compatibility between the Modem, the Beacons, and the Dashboard SW is not guaranteed
    • Always press the Default button in the Dashboard, when uploading the SW
    • Start with default settings only => remember to press the Default button in the Dashboard, after updating the SW

    SW releases archive

    Earlier important changes in the naming of SW versions and licenses:

    • Advanced SW feature pack brought by MMSW0005 are now marked with L at the end of the release name. For example, v7.200 – only base SW features are enabled – by default. Purchasing the MMSW0005 license activates the pack of advanced SW features, and the SW version name changes to v7.200L
    • Naming example IA vs. NIA: v7.200 and v7.200L – SW for NIA and MF NIA, v7.200i and v7.200Li – SW for IA
    • If some beacons/modems don’t have the MMSW0005 license, their addresses are listed in the upper part of the Dashboard – information window
    Earlier important changes in files in the Marvelmind SW pack:
    • The SW files for beacons/modems that don’t require an update with the new release won’t be replaced with the new files in the new SW pack. However, the Dashboard will assign the new version number to them based on the newly introduced SW version compatibility table. Thus, the files physically remain the same, but if they are compatible with the latest SW pack, the Dashboard will automatically substitute their older SW version number with the latest SW version number
    • It is done to detect and avoid the most common mistake by the users – an attempt to run incompatible SW versions of beacons, modem, or Dashboard obtained from different SW packs, i.e., not updating the beacons/modems to the latest SW version from the same SW pack upon getting the equipment from Marvelmind Robotics
    • It is a major new SW release that brings many new SW features, improvements, and bug fixes
    New features:
    • Sending user payload from your central system (computer) via the modem via the mobile beacon to your mobile device (robot, drone, etc.) with each location update. Also, sending the user payload from your mobile device (robot, drone, etc.) via the mobile beacon via the modem to your central system (computer)
    • “Location update rate boost”: the feature increases the location update rate by 25-100% by freeing time slots that are generally allocated to advanced telemetry, data transfers, commands. Enabled by the optional SW license MMSW0012
    • “Virtual pen” – an optional SW feature that allows using a mobile beacon as a virtual pen and drawing/not drawing/wiping in real-time on the virtual screen, for example, a projector. The functionality can be used for presentations, exhibitions, and shows. Enabled by the optional SW license MMSW0013. The future development of the feature will allow using the mobile beacon as a computer mouse
    • Now, the default settings, for example, radio profiles, are not stored in the firmware but in separate files that can be edited. This offers great flexibility to meet the certification requirements of different countries and the requirements of specific projects. It is possible to edit the files manually and set your own default settings for nearly any important parameter, for example, radio or ultrasound settings
    • Control of the Super-Modem via API over UDP over WiFi instead of USB. Enabled by the optional SW license MMSW0014
    • Snap to grid feature when drag and drop stationary beacons on the map
    • Set beacon to (0,0,0) feature – choose by the right mouse click on the beacon – in the beacon’s context menu and the map’s context menu 
    • Specially dedicated buttons to Mirror Submap and Mirror Service Zone
    • Option not to stream out location data in the streaming if the data quality is below a set threshold. Also, an option not to show location update dots in the Dashboard, if the quality of the location measurement is below another threshold
    • Sending a submap to sleep by double-clicking on the submap’s button – the same way as sending a beacon to sleep
    • A new feature that returns the distance from beacon to beacon based on the API request. It is designed for cases when distances are measured – not coordinates. Enabled by the optional SW license MMSW0011: API for manual distance measurement
    • Using RS485 instead of radio for data exchange and telemetry between Super-Modem and stationary Industrial Super-Beacons. Enabled by the optional SW license MMSW0010: RS485 instead of radio
    • Possibility to turn off streaming of coordinates if only raw distances are required
    • A new mode of depicting the track: when the quality of tracking is lower, the dots become larger but less condensed, and the track – fuzzier
    • A new filter to improve the quality of tracking in IA based on “hysteresis of quality” 
    • New hardware variant supported: Mini-TX-2 with a special 6-pin connector for easy UART interface, for example, towards PixHawk, Arduino
    • The SW pack includes the SW for Marvelmind UWB
    • Special calibration methods and manual adjustments for particularly accurate absolute distance measurements


    • Faster modem firmware update
    • When a beacon is manually kicked out from the map and then later re-introduced, the system first attempts to place it in the previous coordinates, if possible
    • Improved coloration and segmentation of buttons on the left side of the Dashboard map
    • The Dashboard warns when the Dashboard version doesn’t match the API version. Particularly important for Linux
    • New mode of operation of the Oscilloscope that allows better debugging complex cases with potential ultrasound reflections. Particularly important for debugging map with high update rates – >8Hz
    • Improved distance measurement trigger
    Bug fixes:
    • M2 mode: aligning two neighboring submaps for handover. Previously: a) one of the “oranges” couldn’t be dragged and dropped, b) when a submap was dragged and dropped, the “oranges” could be mixed up
    • Oscilloscope: a) new oscilloscope graph is not shown unless all data on the bottom of the oscilloscope was received and shown correctly; b) when switching between beacons, all data is now erased to make sure that the correct data from the correct beacon is shown
    • UART/USB streaming and in the log: the coordinates in the location updates were shifted (delayed) by 1 location update – an incorrect timestamp
    • Angle in the NMEA GPHDT string: the angle was not according to the format of the NMEA string
    • Waking up of a beacon when attached to the USB: previously, fast (<10 sec) connecting and disconnecting to the USB could be missed, and the beacon would remain in the sleep mode
    • Dropping mature Beacons v4.9 and Modem v4.9: previously, they could sporadically lose radio every 20…200 minutes
    • Changes: protocol has been updated. Check and use the revised protocol, if you already have integration with your devices
    Download v7.306
    • New feature: IMU+Ultrasound post-processing sensor fusion for location is introduced. Read more
    • New feature: Support for a new SW feature: MMSW0007: Submap islands
    • New feature: Support for a new SW feature: MMSW0008: All hedgehogs’ location update in every cycle
    • New feature: the timestamp between all devices is now fully synchronized and linked to the time of the modem. If the modem is connected to the Dashboard, the modem’s time is synchronized with the time of the computer that runs the Dashboard. The new streaming format is not backward compatible. But there is a tick that can return the compatibility, but it will lose the new feature: Dashboard => Interface => “Stream real-time timestamps”
    • New feature: it is possible to set a static address of the Super-Modem now
    • Linux x86 is also supported in Ubuntu 20.04 now
    • Bug fix: Precise Z rotation of the vertical submap affected the position and the horizontal submap as well
    • Bug fix: Default settings also erased ultrasound frequency settings. They must have remained untouched
    • Bug fix: Overlapping 3D submaps
    • Bug fix: Paired beacons were losing the fixed distance between the pair
    • Bug fix: Axes in the Dashboard
    • Changes: protocol has been updated. Check and use the revised protocol, if you already have integration with your devices
    Changes in the naming of SW versions and licenses:
    • Optional SW features brought by MMSW0005 are now marked with L at the end of the release name. For example, v7.200 – only base SW features are enabled – by default. Purchasing the MMSW0005 license activates optional features and the SW version changes to v7.200L
    • Naming example IA vs. NIA: v7.200 and v7.200L – SW for NIA and MF NIA, v7.200i and v7.200Li – SW for IA
    • If some beacons/modems don’t have the MMSW0005 license, their addresses are listed in the upper part of the Dashboard – information window
    Changes in files in the Marvelmind SW pack:
    • The SW files for beacons/modems that don’t require an update with the new release won’t be replaced with the new files in the new SW pack. However, the Dashboard will assign the new version number to them based on the newly introduced SW version compatibility table. Thus, the files physically remain the same, but if they are compatible with the latest SW pack, the Dashboard will automatically substitute their older SW version number with the latest SW version number
    • It is done to detect and avoid the most common mistake by the users – an attempt to run incompatible SW versions of beacons, modem, or Dashboard obtained from different SW packs, i.e., not updating the beacons/modems to the latest SW version from the same SW pack upon getting the equipment from Marvelmind Robotics

    Minor SW release v7.080 (14.Jun.2022):

    • New feature: Support of 8 ultrasound frequencies in MF NIA – particularly important for multiple drones and other systems with multiple
      mobile beacons, when IA is not feasible, for example, because of excessive noise near the mobile beacons
    • New feature: Geofencing zone violation. Instead of reading the stream of location data in the protocol, it is now possible to have just a pin from the 4X4 pins be automatically switched to “0” or “1” every time reset when the geofencing zone rules are violated. Thus, it simplifies the interfacing. This is an option SW feature under license: MMSW0006
    • New feature: It is now possible to have 3D geofencing zones. XY – based on the shape of the zone. Z – heights range – a layer thickness
    • New feature: An option for highly-resilient industrial applications – an automatic self-reset of beacons in case of the absence of the modem’s radio signal, when the radio from the modem is supposed to be available, but the beacon doesn’t get it for some reason. It shall help the beacons to re-assign themselves to the radio traffic from the modem
    • New feature: Support of new hardware: Industrial Super-Beacons-3 (Industrial-RX-3, Industrial-TX-3)
    • Improved: New default radio profile 100kbps instead of the former 38kbps and 153kbps. 100kbps allows us to have a common radio profile for the most extensive variety or radio chips and different batches of beacons/modems we supply, thus simplifying the settings in complex maps consisting of multiple hardware variants. Supported by all devices except for Beacons HW v4.9-433MHz and Modem HW v4.9-433MHz
    • Improved: PPS (timing) signal from Super-Beacons in NIA
    • Improved:  M1/M2 mode (“oranges”) – to easy building handover zones and to matching localization from neighboring submaps
    • Improved: internal control of maps in IA based on multiple parameters – not only based on the number of beacons and submaps as before
    • Improved: Optimized DSP filters in IA. The update rate is enhanced by 10-20% as compared with the previous SW release
    • Improved: Greatly improved timings in IA and NIA. Stricter control over timings in complex maps
    • Improved: In NIA, the mobile beacons that are not tracked are disappearing from the map, like it was earlier already implemented in IA, i.e., in order not to give false information about the current location, when location is not determined anymore
    • Improved: Beacons and Modems with default settings are displayed with the “-d” suffix now – to highlight the importance of default settings for beginners and simplify debugging when wrong settings are used in the system. Applied to all beacons except for mature Beacons HW v4.9
    • Improved: If the location of a mobile beacon is not determined, there still will be a stream of data, but the fields will carry a “not measured” mark with each time reset
    • Improved: Measurements of battery voltages in beacons
    • Improved: Temperature settings now affect on calculations in IA as well. Previously – only in NIA
    • Improved: Dashboard interface improvements, particularly, related to working robots: path settings, manual control, robot selection, etc.
    • Improved: The paired beacons in NIA are shown in the Dashboard based on IMU – not based on ultrasound. It gives for more stable angle of direction
    • Bug fix: Fixed handovers in NIA. With larger number of submaps there could be handover issues
    • Improved: Beacons and Modems with default settings are displayed with “-d” suffix now – to highlight important of default settings for the beginners and to simplify debugging, when wrong settings are used in the system. Applied to all beacons except for mature Beacons HW v4.9
    • Bug fix: Fixed issues with submaps in NIA with Beacons HW v4.9 and Modem v5.1
    • Bug fix: Fixed issues with the embedded Oscilloscope with Beacons HW v4.9 in IA
    – The main change in the release is an introduction of support of 8 ultrasound frequencies: 19kHz, 22kHz, 25kHz, 28kHz, 31kHz, 34kHz, 37kHz, 45kHz. Previously, the system could have up to 5 ultrasound frequencies: 19kHz, 25kHz, 31kHz, 37kHz, 45kHz
    – Introduction of new frequencies greatly simplifies deployment and greatly improves the performance of complex indoor positioning systems with complex maps of stationary beacons, where ultrasound frequency reuse could quickly become a major headache for network planning. The lack of available ultrasonic frequencies in neighboring submaps would lead to a need for TDMA between the timeslots of the submaps. In its turn, the need for TDMA would lead to the location update rate reduction
    – Additional frequencies also help with avoidance of potential interference with other ultrasound devices in your robot, for example, with sonars. Usually, they work on 40kHz, i.e. no problems, but there could be some variants. Thus, more frequencies – more freedom and more options
    – Super-Beacons with frequencies are fully available too
    – Super-MP set came previously with 5 frequencies and no variation. Now, the set will come with 5 frequencies out of 8 frequencies available. If you want a particular set of frequencies for your Super-MP, let us know during the order
    – 8 frequencies are fully supported in IA and NIA. MF NIA has a limited support now: only 5 frequencies of 8 available, but new frequencies from the list of 8 frequencies are already supported. Support of all 8 frequencies in MF NIA will come in the coming releases
    Changes and improvements:
    – Several minor improvements and bug fixes
    – Introduces support for the very latest hardware batch Super-Beacons-3, Mini-RX-3 and Modem v5.1-3
    – Backward radio connectivity compatibility has been tested on 38kbps only. Thus, for the time being, it is a default radio profile. Remember to press the Default button in the Dashboard after updating the SW on beacons and modem
    – Other radio profiles shall work, but not thoroughly tested yet. If you experience any difficulties, just fall back to the default 38kbps for now
    – Always remember to press the Default button in the Dashboard’s bottom-right corner to upload default settings. Without pressing the Default button, the modem, most likely, won’t see beacons over radio
    Changes and improvements:
    – Minor improvements in submap/map building routine:
    – Deleted beacons are not attempting to return to a submap
    – Chosen in the Dashboard submap automatically rebuilds itself with a higher priority than other – not selected – submaps. It makes the submap building faster
    – Fixed issues with heights of beacons in overlapping submaps
    – User payload now is supported in NIA for Modem v5.1 also. Previously supported only for IA
    – Modem v5.1 now automatically self-reboots after some time of not being connected with a Dashboard
    – New and special mode of splitted microphones for Badge
    – IMU data via Modem v5.1 fixed
    – Fixed robot path transmission via UART from a mobile beacon on the robot
    – New advanced feature for tracking relying on “relatives” – neighboring beacons not belonging to a serving submap. Improves tracking in complex and noisy industrial environment
      • New features:

        • New hardware (HW) for Super-Beacons is supported. We have two types of Super-Beacons: Super-Beacon (produced until Dec.2020) and Super-Beacon-2 (starting from Jan.2021).
          • Super-Beacon-2 has MIC/TELEC certification for Japan. Super-Beacon didn’t have it and won’t have it. From the SW point of view and the main functionality point of view the Super-Beacons are equal. There are additional improvements with optional external microphones and some differences in 4×4 pinout. See more in the Operating Manual
          • Both types of Super-Beacon HW are tested and supported now and in the foreseeable future
        • Similarly to Super-Beacons, new hardware (HW) for Super-Modems is supported. We have two types of Super-Modems: Super-Modem (produced until Nov.2020) and Super-Modem-2 (starting from Dec.2020).
          • The Super-Modem SW is the same for both versions and the HW is detected automatically. You can see the type of your HW in the Dashboard, when the modem is USB connected
          • Both types of Super-Modem HW are supported now and in the foreseeable future. Only the latest Super-Modem-2 HW has been thoroughly tested in this release. The older HW will be tested in the coming weeks. The probability that is already well supported is very high
        • Supported option CAN interface for Industrial Super-Beacon, Industrial-RX and Industrial-TX. CAN interface with other interfaces are described in detail
        •  Dashboard:
          • Possibility to assign own icons instead of hedgehog’s default icon
          • Enhanced and enriched interface of Robot v100
          • Possibility to draw a floorplan directly in the Dashboard
      • Improvements:

        • Dashboard
          • Realtime Player in NIA mode with low location update rate improved
      • Known issues (to be confirmed soon in this release):

        • Verification tests of the SW release with Super-Modem HW are still to be done
      • New major SW release: Marvelmind SW pack v6.240
      • Please, notice that Super-Modem SW is still being prepared. Thus, if your system is using Super-Modem, use the previous SW pack
      • New features:

        • New Modem v5.1 is supported
        • MF NIA is supported and fully commercially available. MF NIA is particularly great for multiple drones and multiple noisy mobile objects when location update per mobile beacons is important. MF NIA allows to have up to 5 times higher update rate than NIA in the configurations with 5 or more mobile objects. See more:
        • MMSW0002: Heading packet GPHDT for NMEA0183 introduced
        • MMSW0003: UBX (u-blox) protocol for PX4
          • Great feature for fully autonomous flight with PixHawk & PX4
          • Supports the Paired Beacons instead of u-blox thus resolving one of the most critical issue for the indoor flight – direction, when compass doesn’t work
          • Check out the Drones page
        • It is not necessarily now to make a filter selection for Super-Beacons, Mini-RXs, and Industrial-RX/Industrial Super-Beacons. The system is handling this information automatically
        • A new parameter in IA: “Max. hedges readout per cycle”. Update rate per mobile beacon/hedgehog doesn’t directly depend on the number of mobile beacons, because they calculate their location independently from the modem and at the same time. However, if you want to track all those hedges in the Dashboard and there are many hedges at once, the radio bandwidth may be become a bottleneck. Thus, this parameter helps to define the optimal number of hedges that share their location with the modem at once. For example, if you have 60 mobile beacons, you can choose all 60 to be sending their location to the modem with each location update. Even though, they could have 8-10Hz location update per mobile beacon, 60 messages per location update create high radio traffic load and lead to the reduction of the update rate to every beacon. Thus, the real location update rate may reduce to 1-3Hz instead of 8-10Hz – depending on the chosen radio profile. However, if you choose, 10 hedges to be updated at once, then you will still have your 8-10Hz per beacon, but on the modem side, you will see your hedge with 8Hz/60*10 location update, i.e. 1/6 of the real location update on the hedges’ side.
        • Stereo microphone support enabled. External stereo microphones are very useful and very powerful when it is needed to provide the highest performance for larger maps consisting of many submaps (warehouses, for example), or the stationary beacons are close to the horizon and the embedded microphone in Super-Beacon or Mini-RX don’t perform too well anymore. Stereo microphones are used, for example, in Marvelmind Autonomous Delivery Robot v100
        • In the paired beacon configuration, it is now possible to send data between the hedges via UART or via radio and to choose it from the Dashboard
        • Option to never sleep. Before, the beacons would automatically sleep after 1 min, when the connection with the modem lost
        • There is a new flag in IA indicating incorrect positioning detected by the system. Previously – in NIA only
        • New and richer coloring of beacons and buttons in the Dashboard in different modes (sleep, no radio, no ultrasound, etc.)
        • Several new modes in the Dashboard for beacons: with coordinates, without coordinates, small dots
        • New button: Freeze zones. It blocks changes in all kinds of zones (service zones, no-driving zones, etc.) and in the robot path. It is done it prevent accidental changes of the zones after they are created. Use Save map button to create backups for the maps and service zones. Use Save path button to store paths
      • Improvements:

        • In NIA, when the service is selected, there is no anymore an automatic submap size limitation. Previously, it was calculated based on a fixed formula and the size of the submap depended on the distance between stationary beacons. For shorter distances between the beacons, the submap could have been smaller than wanted. Now, there is no such a dependency and the size of the submap is defined by the Limitation of Distance, if a service zone is not defined, or the service zone for the submap, if it is defined. By default – the service zone. But, again, if the service zone is defined. If it is defined, it possible still possible to manually switch to higher limitation of distance and, for example, for 10-m submap, the limitation of distance will be 30m. It will lead to slower update rate, because the system will wait longer for an ultrasound to arrive. But in same cases, it may be interesting and required by the user. So, such an option exist
        • In IA, there is an internal check now that the map and the timing of “hedgehogs” and “owls” are loaded to hedges correctly
        • New warnings and messages in the Dashboard for the end users:
          • When the user tries to activate more than 4 stationary beacons per submap – only up to 4 stationary beacon per submap is supported. For more – build more submaps
          • When the user tries to introduce in a submap in IA stationary beacons with the same ultrasonic frequencies. It is not allowed, because IA submaps must have beacons with different ultrasonic frequencies
          • When only one hedge per cycle is selected in the Paired Beacons configuration – at least, two are required
        • In radio profile, FEC is not disabled for 38kbps and 153kbps. The radio becomes incompatible with the previous SW versions, but we ask to update the SW for all beacons and modem to the latest from the same SW pack anyway. So, the change is unnoticed to a regular user, but brings higher update rate due to shorter radio pulses
        • Updated 500kbps profile to achieve compatibility between Modem v4.9 and Modem v5.1
        • Improved ultrasonic trigger (distance measurement) for Super-Beacons, Mini-RXs, Industrial-RXs, Industrial Super-Beacons
        • Dashboard now shows a message when there is no lock between gyroscope angle and the ultrasonic angle in the Paired Beacons configuration. Used, for example, in the following cases: and
        • Improved tracking in IA in 2D
        • Log-files of the Dashboard now have extension .CSV instead of previous .log
        • Several robots driving simultaneously are supported in the Dashboard now
        • Default height of the service zone is 10m
      • Bug fixes:

        • When one of the hedges were lost over radio in NIA, another were lost too – fixed
        • RX485 if power save mode with Industrial Super-Beacons didn’t work properly – fixed
        • IMU fusion of angle with power saved enabled didn’t work properly – fixed
        • Simultaneous positioning in two submaps (M2 button in the Dashboard or “oranges”) for defining handover zones in didn’t work well in IA – fixed
      • Known issues (to be fixed in the next releases):

        • The button in the Dashboard defining the axis and the starting beacon – – works well only, when the submap is frozen. If it is not, the behavior of the submap/map can be unstable
      • New features:

        • Support of up to 120m range in NIA. Works with special horn antenna with external microphone with Super-Beacon and Mini-RX
        • Modem can find too closely placed beacons now. Previously, both devices would be overloaded by RSSI
        • Support of geofencing zones in IA (previously, only in NIA)
        • Inverse and non-inverse geofencing zones (allowing and forbidding zones)
        • “IMU via modem” from beacons are available via radio in the Dashboard now with each location update. Previously – only via USB directly from modem to streaming, but not to the Dashboard
        • Dashboard streams out via UDP the received “IMU via modem” data
        • “IMU via modem” is supported in IA as well
        • All hedges stream our location data of all other hedges in IA now. It was previously supported in NIA only. In both architectures it is possible to turn the functionality off and increase the update rate by saving on the streaming time
        • Now IA supports new types of streaming packets via UART and USB: a) raw distances; b) raw IMU data; c) telemetry data (RSSI, battery voltage; d) quality of positioning. This have been supported in NIA only before. In IA and NIA these packets can be turned on from the Dashboard. By default only streaming of location data is enable
        • New types of devices added: robots and workers. And new layers of buttons in the Dashboard added to each of the new types
        • Player is now split into two parts: a) Player window, b) Statistics/Analytics window. Statistics/Analytics windows are customer specific and customized by request
        • Dashboard warns users that switched the Dashboard into streaming-only mode when they try to change settings in the beacons, because they can’t in this mode
      • New API features:

        • Function of read/write of configuration memory of the modem (settings and the map)
        • Function of angle received from the Paired Beacons feature
        • Function of manual entry of coordinates of stationary beacons
        • Function of read/write air temperature (as a parameter for speed of sound calculation)
      • Improvements:

        • When user starts entering distances in the table of distances manually, the automatic building up of submaps freezes to stop interfering with manual entries
        • LEDs of all beacon blink identically. Previously, for the same mode, different beacons could blink differently
        • Optimized power saving in Super-Beacons, Mini-RX and Industrial-RX and Industrial-RX beacons
        • Default size of submap and IA and NIA is the same now – 30m. Previously, 30m in NIA and 20m in IA
        • More settings are stored in the file of settings created by Save Map button
        • Quality of tracking of Mini-TX with Super-Beacons, Mini-RX and Industrial beacons
        • Dashboard automatically saves maps with any changes of settings and enters the link to the map into the log so that the Player could play log properly and use the right map accordingly
      • Bug fixes:

        • Corrected loading map into the hedges when button Load Map pressed in IA
        • Now the distance in the submap matches the distance in in the embedded oscilloscope in IA
        • Correct height entry of stationary beacons in overlapping submaps. Previously, when one of the heights enters, some other heights could alter
      • Known issues (to be fixed in the next releases):

        • Direction in the Paired Beacons configuration may not work properly with location update rates 1Hz or lower

    Step 6: Integrate with your devices

    Download Marvelmind Interface Protocols

    Download PDF with all Marvelmind interfaces and protocols

    All external Marvelmind protocols and interfaces are described in a detailed PDF. The location data can be received from the mobile beacon, the modem, or both simultaneously, allowing tracking, remote control, or using the location directly on the spot by autonomous robots or drones.

    Before you start integrating anything, see and follow our recommendations:

    – 8 basic steps from unpacking to autonomous drive/flight
    Typical mistakes with Precise Indoor “GPS”

    In short:

    • Always do step by step from the most straightforward 2D configuration with two stationary beacons and only one mobile beacon and everything in NIA, even if your final design is far more complex, something completely different and in another architecture
    • You will be there, but reach that stage small single step at a time
    • Don’t try to build the final configuration right away before confirming that the more straightforward design already gives you the perfect tracking
    • This is the fastest and most guaranteed way to achieve perfect tracking for any possible configuration
    Example 1 – building a system for an autonomous flight with more than one drone:
    • Reach basic NIA tracking in 2D – not even on a drone – 2 stationary beacons, one mobile beacon, one modem
    • Reach basic NIA tracking in 3D – not yet on a drone – add two more stationary beacons – nothing else
    • Reach the same on a drone, but the drone is not yet flying – only remotely controlled – but the mobile beacon is powered from a drone – – the drone may interfere in one way or another – has to be checked: radio/telemetry, motors, power supply drops/noise, etc.
    • Try to revolve propellers, but not to the full power. Monitor tracking. Use embedded into the Dashboard oscilloscope to see the
      signal and the trigger, if needed – checking that noise from propellers doesn’t affect the tracking
    • Try to fly remotely, control the drone, and track. You must see something like this: – if you have it, then you are ready to move to try an autonomous flight
    • Get the 3D lock-in Mission Planned or ArduPilot
    • Try to fly autonomously with one beacon and not yet with the paired beacons
    • Try the Paired Beacons with directions. Return a bit and repeat the same steps with the Paired Beacons as you have done for a single beacon and achieve the perfect tracking and direction on a static and remotely controlled drone before trying the autonomous flight
    • Fly autonomously with the Paired Beacons
    • Repeat the same for each drone separately. Other drones are off completely – kick them out from the network and switch off
    • And only at this stage try to fly more than one drone autonomously

    Virtual UART over USB

    This is the easiest way to connect Marvelmind devices (beacons and modem) since no soldering is required:

    Supported devices:


    It can be connected via the available pins. See Marvelmind Interfaces document

    Supported devices:


    Supported devices:


    Supported only optionally and on request

    Supported devices on request:


    • UDP protocol description
    • UDP SW example
      • Here is the C-written UDP example
      • Supported operating systems:
        • Microsoft Windows
        • GNU/Linux
      • Supported streaming as well as a master-slave mode

    It is possible to get the UDP stream from:

    Python library for beacon

    The Python library provides the quick and easy ability to integrate ultrasound navigation systems with various Linux-based devices. Among them are Raspberry Pi and other single-board PCs. This code is free to use in your applications (please include a reference link to this webpage).
    • Here is the Python code for Linux-based devices integration via virtual UART via USB
    • The library is easy to use. Also, here is a detailed description and example

    The code is pretty universal. It is tested on:

    • Ubuntu 16.04
    • Raspbian Jessie
    • Mac (OS X 10.10)
    • Python 2.7 & Python 3+

    There are handlers of different exceptions, for example, non-standard states of COM/USB.

    C library for beacon

    Here is the C code + guiding document.

    Supported operating systems:

    • Microsoft Windows
    • GNU/Linux (including Raspberry Pi)
    • Mac OS X

    Additionally, here is a link to the GitHub repository.

    Android/Java library for beacon

    • Here is the Java code and simple Android application
    • A simple Android app for testing (old by now. Performance not guaranteed)
    • Tested on:
      • Samsung S7 (API 25)
      • Huawei P6 (API 22)
    Marvelmind Android sample code and Java sample code

    PixHawk, PX4, ArduPilot, NMEA0183, and uBlox supported

    ROS2 and ROS supported




    Marvelmind ROS package v1.0.11 compatibility and main changes:

    • Supports receiving telemetry, quality, and waypoints data
    • hedge_rcv_bin allows specifying serial port baud rate in the command line

    Supported ROS versions:

      • Noetic for Ubuntu 20.04
      • Melodic for Ubuntu 18.04
    Additional hints:

    Sending path to your robot/copter

    • Here is an explanation of sending path data via mobile beacon to your robot/copter and sample code.
    • Check a corresponding chapter in the protocol description. The request of writing the movement path
    • Relevant forum discussion

    The Dashboard software log description

    Contact us via with any questions

    Updated on 07.Dec.2019

    • New SW: Marvelmind SW pack v6.190
      • New feature: support of jitter for IA for larger maps consisting of multiple submaps
      • New feature: ultrasonic gain plateau is enabled by default to equalize ultrasonic signal strength difference with different distances between mobile and stationary beacons
      • New feature: support of NMEA0183 streaming in Mini-RX, Super-Beacon, Industrial Super-Beacon, Industrial-RX and Industrial-TX
      • New feature: support of Paired Beacons feature in IA with fast angle from IMU that is unlinked from the location data from ultrasonic. For example, you have the Paired Beacons and rotate your robot clockwise by 90 degrees. You will get the angle with 12-15ms delay from the USB or UART. Location data will be still updated with regular 4-16Hz update rates or so
      • New feature: Advanced power saving:
        • Power saving is on by default for all types of beacons, except for Beacons HW v4.9
        • It is possible to turn on and to turn off power saving feature individually per beacon (previously – per modem)
        • Overall more economical sleep between location updates and in general in the sleep mode
      • New feature: It is possible to set the gain of ultrasonic reception directly in the embedded oscilloscope – very convenient for the tests, when using the oscilloscope
      • New feature: it is possible to switch between several streaming modes in the mobile beacon: none, USB only, USB+UART, USB+UART/Bluetooth. The feature allows to achieve the highest update rate, because time savings on streaming. In order to enjoy the savings all mobile beacons must have the least possible streaming mode. If one mobile beacon has full streaming enabled, it is equivalent that all mobile beacons have it and there will be no time saving
      • Improvement: update rate in IA increased – excessive safety times have been reduced inside the timing slots
      • Update: SW for Super-Beacons is a part of the main SW pack now
      • Bug fixed: Mini-RX, Super-Beacons and Industrial Super-Beacons don’t wake up now, when are connected to USB charger, but not to a USB host (computer). You must update using DFU in order to fix the bug

    Known issues and not yet supported features and functionalities, but earlier promised (to some customers) and work in progress:

    • Tracking in IA 3D is supported, but without 3+1 redundancy. Thus, direct line of sight/hearing is required for all stationary beacons
    • Reading and writing parameters of modem and map by reading/writing raw damps of memory via API – work in progress and will come later
    • Entering air temperature via API – work in progress and will come later
    • Streaming of the angle of the Paired Beacons via API is not supported. Streaming from the mobile beacon directly to your robot/drone is supported and has been supported for a long time
    • Streaming of IMU data via UDP is not supported yet – IMU via modem mode
    • Some minor settings are still not saved in Save Map feature. Ongoing revision


    Updated on 4.Nov.2019


    Updated on 08.Oct.2019

    • Correction update before main SW release: Marvelmind SW pack V6.160/6.166/6.170
      • Bug fix: streaming via virtual UART over USB didn’t properly work in Mini-RX and Industrial-RX in IA configuratio



    Updated on 01.Oct.2019

    • Correction update: Marvelmind SW pack v6.166
      • Correction: proper detection of Mini-RXs, Industrial Beacons and Industrial Super-Beacons in Linux
      • Improvement: drastically improved power consumption in IA mode for Mini-RX, Industrial Beacons, and Super-Beacons
      • New feature: support for IA in Industrial Super-Beacons
      • Changes: default ultrasound settings for Industrial Beacons and Industrial Super-Beacons are now 25kHz (metal sensors’ frequency) instead of previous default ultrasonic 31kHz (default for 16mm plastic sensors)


    Updated on 25.Aug.2019

    • Major update and several new features: Marvelmind SW pack v6.160
      • New: Support of new HW – Industrial Super-Beacons
      • New: Paired beacons in IA and dual-head in IA. Demo:
      • New: Support of TDMA Mode 1 and Mode 2 in IA
      • New: Support of RSSI for automatic selection of submaps in IA maps with multiple submaps
      • New: Embedded Realtime Player for streaming location data in IA hedge
      • New: Both mobile beacons (“hedgehog” or hedgehog or hedge) and modem have a flag showing that the mobile beacon left geo-fencing zone
      • New: Possibility to set the COM part number for the modem for the Dashboard manually. And, as a result, a possibility to support more than 1 Dashboard and more than 1 modem per computer. Also, supported in API now
      • New: Support of 4 beacons per submap in IA (previously – up to 3 beacons)
      • New: Support in API of possibility of controlling axis vs. beacons relative position
      • New: Support of summing up of up to 3 microphones as a single microphone – used in Marvelmind Badge and Marvelmind Jacket – for more guaranteed tracking in challenging environment with obstructions
      • Updated: Radio profile 868MHz
      • Bug fix: minor USB connectivity issues with Mini-RX
      • Bug fix: corrected measurement with microphone n2 and Realtime Player enabled


    Updated on 21.May.2019

    • Major update and several new features: Marvelmind SW pack v6.130
      • Support of submaps in Inverse Architecture (IA):
      • Support of vertical submaps in IA – useful for tracking in long aisles in warehouses, where XZ coordinates (along with the aisle and height) are important and Y coordinate (across) of the aisle is less so
      • Support of TDMA in IA – allows nearly perfect tracking in challenging conditions with obstructions in IA
      • Support for the Paired Beacons SW feature in IA. Now both IA and NIA allows Location+Direction functionality shown here:
      • Support for streaming of location data via virtual UART from the mobile beacon in IA
      • Support for Load Map with sleeping beacons to add new beacons for building larger maps
      • Support for streaming out center of Paired Beacons as opposed to locations of each of the beacons – option in the Dashboard
      • Service Zones for submaps are handled now by context menu (right click on the dot) instead of in a separate window
      • Mobile beacons (“hedges”) can be named now, for example, the name of the robot or the person – not only addresses as before
      • Support of advanced history in IA. Possibility to have duplicated ultrasound frequency combinations in submaps
      •  Improvements and bug fixes:
        • Temperature measurement by beacons with low temperatures and power voltage measurements
        • Stability of beacons with addresses >128
        • Height settings of stationary beacons in IA (“owls”)
        • Table of distances in IA with >2 stationary beacons
        • Load Map of vertical and intersecting submaps
        • Prevention of other beacons going to sleep on timeout during long SW update of a beacon over radio on slow radio profile
        • Smoother and more polished Realtime Player in the Dashboard




    Updated on 22.Mar.2019

    • Major new and long-awaited Inverse Architecture (IA) introduced: Marvelmind SW pack v6.08
      • It is not a fully mature release yet – for those who can’t wait 🙂 New minor updates shall come pretty soon. If you see bugs, please, report to
      • If you have Mini-RX HW with earlier SW release that shows “Bootloader”, when connected to the Dashboard, do DFU programming right away:
        • Open the housing
        • Switch DIP switches similar to the instructions in the Operating Manual for HW v4.9
        • Uupdate the SW via DFU to the latest. After that, normal HEX programming via Dashboard will be possible
      • If your Mini-RX is discharged due to long shelf storage:
        • Switch both DIP switches off
        • Charge the beacon normally via USB for 2h
        • Upload the latest SW (DFU or HEX – depending on your original SW)
        • The beacon will have longer standby time now
      • Only one submap up to 30x30m supported. Support for multiple submaps shall come in a couple of months
      • Multiple mobile beacons without update rate reduction per mobile beacon unlike in NIA. Update rate is still slightly going down due to radio, but it has a lesser impact than in NIA
      • If two stationary beacons (“owls”) are used – 2D (XY) mode is chosen automatically. If 3 stationary beacons – 3D (XYZ) mode
      • See more on the Architectures comparison
    • Beacon naming change:
      • DSP beacon => Mini-RX
      • Mini-beacon => Mini-TX
      • Beacon RX IP67 => Industrial-RX
      • Beacon TX IP67 => Industrial-TX
    • Improved Industrial-TX: power saving; IMU data is streamed out to modem along with ultrasonic location updates
    • Improved power saving and battery protection for Beacon HW v4.9, Mini-TX and Mini-RX
    • New feature: hedgehog streams out its address in the raw IMU stream
    • Marvelmind SW package now contains not only pure SW, but also protocols and manuals. Note, that the manuals maybe updated independently from the SW. Thus, check the latest manuals on Downloads page


    Updated on 07.Mar.2019

    • We are happy to publish a long-awaited Marvelmind API! 🙂
      • API library included
      • Windows and Linux supported
      • Intel/AMD and ARM processors supported
      • API Manual included
      • C-example included



    Updated on 21.Feb.2019


    Updated on 13.Dec.2018

    What is new:

    • Support for DSP beacon and Mini-beacon added
    • IMU fusion of angle of Paired Beacons added
    • Change: IMU is switched off by default to save power
    • New power saving features – battery lifetime improved
    • Other improvements: faster connectivity to the Dashboard over USB; improved blinking of beacons with lost radio connectivity; etc.
    • Bug fix: manual entry of coordinates into the table of distance
    • Bug fix: angle – result of the Paired Beacons SW feature started working incorrectly in SW v6.01 – fixed now



    Updated on 26.Nov.2018

    What is new:

    • Major new feature – support for 255 beacons and 255 submaps per modem
      • Now it is possible to build truly large maps including up to 255 beacons (stationary+mobile combined) and up to 255 submaps
      • Notice that for larger maps, consisting of many submaps, most probably, you will have larger distances between modem and beacons. It is particularly important to place modem in the middle of the network of beacons to provide good radio coverage to all beacons in the map
    • New feature: user must setup handover zones between submaps to guarantee handover quality for complex maps with multi-floor and similar
    • New feature: default wireless connection is setting is now 153kbps (used to be 38kbps). Radio profile 153kbps provides radio coverage range nearly as much as 38kbps and update rate nearly as high 500kbps, i.e. it is a middle of 38kbps and 500kbps, combining the best of both
    • Correction: USB streaming in power save mode improved
    • Correction: Zero IMU button in the Dashboard is improved, while button Reset IMU is removed completely
    • Correction: ultrasound TX is not reset to 31kHz when Default button is pressed. Now, several types of ultrasonic frequencies supported, so 31kHz is not anymore a default ultrasonic frequency for all beacons
    • Improved: both energy saving and tracking quality with Power Saving mode enabled
    • Improved: only beacons with selected tick in the Dashboard lower menu will be accepted to the network – not any addresses. This improves predictability of the network, when there many beacons that may not belong to the network. Their attempts to join the network will be blocked
    • Improved: now, submaps support up to 4 beacons only. More than that – build another submap. Up to 255 beacons and up to 255 submaps are supported per beacon
    • Bug fix: improved map building with active hedgehog
    • Bug fix: duplicated address might work incorrectly in some cases


    Updated on 01.Oct.2018

    • For HW v4.9 and v4.5: Dashboard SW v5.77 + Beacon SW v5.96 + Modem SW 5.96
    • It is an upgrade release with one major new feature and several corrections, improvements and bug fixes
    • Notice that SW support for HW v4.5 is about to be discontinued. So, it is recommended to get HW v4.9 or newer. HW v4.5 and HW v4.9 can work together in the same network
      • In the SW pack, only DFU SW for HW v4.5. And HEX and DFU for HW v4.9

    What is new:

    • Major new feature – Real-time Player
      • Produces high-quality and very smooth track in real time (similar to the original Player, but in real-time – not from the CSV file) even in challenging conditions with an original poor raw track by doing real-time post-processing (filtering and interpolation) of several latest location measurements
      • Especially good for tracking of slow moving objects, like, people or producing location data for slow-moving autonomous robots. Less suitable for providing real-time location data for fast drones, because of inherent higher latency due to internal post-processing
      • Option to trade-off between latency vs. smoothness
    • Updated protocol and interfaces:
    • Bug fix: more stable path sending to a robot
    • Bug fix: corrected direction indicator in the Paired Beacon SW feature
    • Bug fix: improved map building with active hedgehog



    Updated on 27.Aug.2018

    • For HW v4.9 only: Dashboard SW v5.72 + Beacon SW v5.93 + Modem SW 5.93
    • It is a major release with several new major features
    • Linux version of the Dashboard and Dashboard API will follow in the next minor release
    • Important notice for 500kbps:
      • Build the map in the 38kbps radio profile first
      • Modem will measure and store beacons’ frequency offsets
      • Only after that switch the system to 500kbps radio profile

    What is new:

    • Multi-floor support:
    • Support of 3D (XYZ), 2D (XY), 1D (X) in a single map
    • Vertical submaps. Especially useful for precise Z support:
    • Support of submaps with Z-only data
    • Support of streaming of IMU data with each location update
    • Possibility to create 3D (XYZ) path, for example, for autonomous drones/copters
    • Support of direct manual entering of stationary beacons’ coordinates
    • Q – quality of positioning from modem and mobile beacon
    • Support of speed in NMEA stream based on IMU data
    • Streaming of telemetry from mobile beacon
    • Improved embedded Player of locations CSV file
    • Improved filtering of distances and location
    • Improved handovers between submaps
    • Reworked and improved ultrasonic trigger
    • Warning, when a second instance of Dashboard is started
    • Improved Load Map function
    • Bug fix: locking beacons to axes
    • Bug fix: locking beacons to substrate
    • Other bug fixes and improvements



    Updated on 14.Mar.2018

    What is new:

    • Update rate is measured with 1 digit after point, i.e. 8.2Hz instead of 8Hz
    • Timestamp in coordinates packet in streaming corresponds to the moment of emission of ultrasonic
    • Additionally, time from the moment of ultrasonic pulse emission to the current moment (packet time) is provided
    • Modem is streaming now angle from the Paired Beacons (previously, didn’t stream it)
    • Bug fix: IMU packets with ultrasonic packets from hedge via UART
    • Bug fix: compass works now properly
    • 6 symbol CPU ID introduced



    Updated on 11.Mar.2018

    What is new:

    • 1D mode supported now: So, it is possible now to have configuration consisting of 1 modem + 1 mobile beacon + 1 stationary beacons to have constant tracking of the distance from the stationary beacon to mobile beacon and vise versa. It is also possible to have distance tracking from several stationary beacons simultaneously. Each of them shell be a Submap. Multiple mobile beacons are supported too. Below is a screen capture of an exampled 1D system deployed with 1 stationary beacon (1 submap) and 2 mobile beacons (20 and 23):

    • Improved support of IP67 beacons
    • Switching between radio profiles is faster and more robust now
    • Possible to choose radio power in dBm
    • Fixed bug in robot path sending
    • Fixed bug in Write All command in the Dashboard
    • Fixed bugs in testing routing
    • General improvements and bug fixes


    Updated on 25.Jan.2018

    What is new:

    • New major feature for beta testing: IMU + ultrasonic sensor fusion. With update rate based purely on ultrasonic as low as 4Hz, you can get effective update rate of 100Hz from mobile beacon equipped with IMU thanks to the new sensor fusion feature. Expected update rate in future SW releases – 200Hz on the same HW
    • Tracks below:
      • 4Hz ultrasonic-only track => location update latency ~250ms
      • 4Hz ultrasonic + 100Hz IMU => location update latency ~10ms
      • 100Hz IMU-only track => location update latency ~10ms
      • Each square is 5x5cm
    • Notice, that IMU raw data protocol has changed. Also, notice that 100Hz location update is available only from the mobile beacon – not from the modem
    • Here is a Python code to extract 100Hz fast location update from mobile beacons via UART and virtual UART over USB
    • Code is in beta testing. So, your feedback is highly appreciated
    • General improvements and bug fixes




    Updated on 04.Jan.2018

    What is new:

    • New feature: CSV log file player. You can read tracks of mobile beacons recorded by the Dashboard into the CSV file and play it back directly in the Dashboard. You can choose exact time from the log, length of the track and even get some basic analytics, like: maximum speed, average speed, etc.
    • Improved radio profiles (38kbps, 153kbps, 500kbps) with better sensitivity. Tested line of sight distance on 500kbps with full-size quarter-wave antennas was >400m. Expected distance with 38kbps is even larger
    • Improved stability of waking up from sleep
    • Improved power saving mode
    • True update rate for paired beacons is shown now. Previously, it was shown for each beacon separately, i.e. 1/2 of the true update rate
    • Improved internal system clock synchronization
    • Dashboard now creates a new CSV log file every time, when the system starts/wakes up and every time, when a map is frozen
    • General improvements and bug fixes


    Updated on 15.Nov.2017

    What is new:

    • New: Now the SW for beacons and modem supports 2 main bands (915MHz and 433MHz) and 2 additional bands (868 MHz and 315 MHz) in a single file, i.e. you don’t have to select a separate file per frequency from the SW pack. Though, you still have to choose between SW for modem vs. SW for beacon and you have choose your HW (beacon v4.9 (5 sensors) vs. beacon v4.5 (4 sensors)). Note, that 315MHz additional band is recommended to be used with 433MHz HW boards and 868MHz – with 915MHz HW boards, because they are closer in frequencies. Remember, that the HW is not tuned for the additional bands and radio range can be severely reduced, as compared to the range in the regular main bands the boards are actually designed for. However, still, you may use additional band now, if you wish to do so, for example, to minimize interference with your onboard telemetry or because your country’s regulations don’t allow either 433MHz or 915MHz systems
    • New: Raw distance data streaming supported now
    • New: beacons streams out location data and clearly marks now whether it is its location or another beacon
    • New: flag introduced “Accept new/woken devices”. It is possible now to forbid the modem to automatically take into the map accidentally woken up beacons. Previously, if the beacon woke up for any reason, it would stay active, because it would respond to the modem’s signal and thus the beacon’s battery could be depleted for no purpose
    • New: a watchdog timer introduced in beacons to improve stability. As a drawback, the deep sleep mode that was previously recommended for shelving the product with absolute minimal current consumption is not supported anymore. For shelving, it is recommended to put both DIP switches in OFF position
    • New: mobile beacon protocols are updated (raw distance data added; flag of source of location data). Check them out
    • Improvement: more robust building of bigger maps made of frozen submaps
    • Bug fix: distances in the table of distance could be changing in some settings even, if the map was frozen
    • Bug fix: corrected loading of saved maps with submaps from a file
    • Bug fix: mirroring of a full frozen map consisting of submaps works now properly
    • Bug fix: uploading firmware over radio to a beacon in the frozen map
    • General bug fixes


    Updated on 29.Oct.2017

    What is new:

    • Improved: Power saving features are significantly improved. Note, that power saving is off by default and shall be enabled in modem settings: “Power save functions”
    • General bug fixes


    Updated on 28.Sep.2017

    What is new:

    • New feature: Two mobile beacons (‘hedgehogs”) can be paired and work together as a single beacon without update rate reduction. Moreover, each beacon streams out in this mode not only its own location, but direction where the pair is facing. This feature hugely simplifies autonomous driving and flight. Here is updated protocol with the changes
    • New feature: Save Map/Load Map feature and buttons are active now. You can build a very complex map with submaps and save all settings for the map, submaps, and all beacons including their ultrasonic gain, triggers, etc.
    • New feature: streaming user payload from mobile beacon to modem. See the table with speed vs. payload
    • New Arduino sample file: sending user payload from mobile beacon to modem
    • Improved: Until beacons are really awake, they are not shown as alive in the Dashboard anymore. Previously, they could be shown as green and alive before disappearing on timeout after a minute or so and that could confuse
    • General bug fixes

    Updated on 13.Aug.2017

    What is new:

      • New feature: path sending to copters
      • New feature: now each hedgehog streams out coordinates of all other hedgehogs – not only its own coordinates, i.e. now all robots/copters may know location of all other robots/copters
      • New feature: support of extended memory for Modem_256 (modem supporting up to 256 beacons. Current modem HW v4.9 supports up to 30 beacons)
      • New feature: extended update rate options to 0.1Hz and 0.2Hz
      • Improved service zones with 8 points
      • Improved sleep modes
    • Bug fix in modem: modem, sometimes, was not recognized by PC after PC reboot
    • Bug fix in sabmaps: after one of the beacons in submap of 3 beacons lost, system remained in 3D mode with insufficient number of beacons. Now it turns to 2D mode automatically
    • Bug fix of submaps with 2 beacons: they might lose tracking of hedge after modem reboot
    • Bug fix in embedded oscilloscope for distances between beacons >30m
    • Bug fix: occasionally, beacons sent previous location measurement, when no ultrasonic signal received. Now send a flag, that no signal received
    • Bug fix: improved operations with IMU

    Updated on 05.Jun.2017

    • For HW v4.9 and v4.5 SW pack: Dashboard SW v5.31 + Beacon SW v5.63 + Modem SW 5.63

    What is new:

    • Please, make sure that you are using right SW version for your HW – v4.5 vs. v4.9
    • Improved radio synchronization in challenging conditions
    • Increased channel spacing for 915MHz band
    • Improved oscilloscope scaling
    • Significantly improved trigger mode
    • Quality of ultrasonic signal assessment enchanced
    • Repetitive waking up of sleeping beacons
    • Timed out beacons are not removed from the map now, but marked as unused
    • As a customized feature, it is possible to have now 2 additional external buttons connected to 4×4 pins. They perform now 2 actions: (1) manual log of coordinates, (2) remote clearing the map of traces. Customized functionality may be assigned to those 2 external buttons
    • Improved waking up command
    • Improved performance for complex maps with multiple submaps
    • Multiple and various bug-fixing and error corrections

    Updated on 27.Mar.2017

    • For HW v4.9 and v4.5 SW pack: Dashboard SW v5.16 + Beacon SW v5.51 + Modem SW 5.51
    • Since SW changes are pretty big with this release, please, use DFU for SW uploading. Future SW upgrades can be done with HEX, as usually.

    What is new:

    • Please, make sure that you are using right SW version for your HW – v4.5 vs. v4.9
    • Full support of HW v4.9 – both 433MHz and 915MHz boards
    • Major change in ultrasonic signal triggering mode and AGC – completely new technique is employed now. It shall bring better results in noisy environment as well as when the ultrasonic signal is either too strong or too weak
    • Improved scanning of radio frequencies for better searching of beacons
    • Increased precision of geo-referencing from ~11cm to ~1.1cm
    • Added a new mode of raw data streaming from the modem’s UART – real-time raw distances and RSSI data
    • Usual bug-fixing and error corrections

    Updated on 16.Feb.2017

    • For HW v4.5 (5 sensors) SW pack: Dashboard SW v5.06 + Beacon SW v5.41 + Modem SW 5.46
    • For HW v4.5 (5 sensors) Dashboard: Dashboard SW v5.06 – installation file with drivers. It is suitable the most for the very first installation of the Dashboard

    What is new:

    • It is possible now to build a fully functional map/submap for 3D navigation using only 3 stationary beacons. Before, one would need at least 4 stationary beacons per map/submap for 3D navigation or 2 stationary beacons for 2D navigation
    • It is possible now to enter values in the table of distance between stationary beacons manually. Before it was fully automatic only
    • It is possible now to remove restriction on the minimal distance between stationary beacons or stationary beacons and mobile beacons. Before it was 0.35m at minimum. Now, it can be set to 0mm. As before, the distance between beacons is not limited anyhow. So, mobile beacons can as close to each other as one wishes
    • Enriched features of embedded oscilloscope designed for making possible a deeper analysis of implications of higher location update rate settings on the system performance
    • C and Python and UDP sample codes support now mm-output format, i.e. fully compatible with the main SW pack. To switch back to cm-resolution format
    • Usual bug-fixing and error corrections

    Updated on 12.Jan.2017

    • For HW v4.5 (5 sensors) SW pack: Dashboard SW v5.01 + Beacon SW v5.40 + Modem SW 5.40

    What is new:

    • Fixed bug that affected on proper writing of settings into the beacon in some circumstances
    • Faster beacon wake up time
    • Ultrasonic gain self-calibration introduced in beacons: Dashboard > View
    • Optimized displaying of beacon’s parameters, while beacon wakes up
    • Notice that C and Python and UDP sample codes are written for cm-output – not mm-output, i.e. not directly compatible. You can turn on compatibility mode to switch back to cm-resolution format

    Updated on 20.Dec.2016

    • For HW v4.5 (5 sensors) SW pack: Dashboard SW v4.94 + Beacon SW v5.37 + Modem SW 5.37

    What is new:

    • Fixed bug with SPI of mobile beacon
    • Significantly improved resolution of embedded oscilloscope
    • Now the Dashboard has an install file
    • Distances and coordinates are given now in millimeters
    • Notice that C and Python and UDP sample codes are written for cm-output – not mm-output, i.e. not directly compatible. You can turn on compatibility mode to switch back to cm-resolution format

    Updated on 11.Dec.2016

    • For HW v4.5 (5 sensors) SW pack: Dashboard SW v4.92 + Beacon SW v5.35 + Modem SW 5.35

    What is new:

    • Distances and coordinates are given now in millimeters
    • Key protocols are updated. Please, see them inside the SW package archive
    • Notice that C and Python and UDP sample codes are written for cm-output – not mm-output, i.e. not directly compatible. You can turn on compatibility mode to switch back to cm-resolution format

    Updated on 08.Dec.2016

    • For HW v4.5 (5 sensors) SW pack: Dashboard SW v4.91 + Beacon SW v5.34 + Modem SW 5.34

    What is new:

    • Some beacon addresses bug fix
    • Modem streaming bug fix

    Updated on 26.Nov.2016

    • For HW v4.5 (5 sensors) SW pack: Dashboard SW v4.89 + Beacon SW v5.33 + Modem SW 5.33

    What is new:

    • Interface with modem is done now in exactly the same format as with the beacon (UART/virtual UART, SPI)
    • NMEA support fixed: mm vs. cm output
    • Other various bug fixes

    Updated on 10.Nov.2016

    • For HW v4.5 (5 sensors) SW pack: Dashboard SW v4.88 + Beacon SW v5.32 + Modem SW 5.32

    What is new:

    • Tested support of at least 30 beacons per modem (29 stationary beacons + 1 mobile beacon or 26 mobile beacons + 4 stationary beacons or anything in the middle)
    • Various bug fixes, particularly, in submaps

    Updated on 29.Oct.2016

    • For HW v4.5 (5 sensors) SW pack: Dashboard SW v4.87 + Beacon SW v5.28a + Modem SW 5.31_6cb9597

    What is new:

    • UDP location streaming from modem is supported now. Previously, location data had to be requested each time – point by point
    • Bug fix in multimaps

    Updated on 25.Oct.2016

    • For HW v4.5 (5 sensors) SW pack: Dashboard SW v4.85 + Beacon SW v5.28a + Modem SW 5.28_1564fd4

    What is new:

    • Minor update

    Updated on 13.Oct.2016

    • For HW v4.5 (5 sensors) SW pack: Dashboard SW v4.85 + Beacon SW v5.28 + modem SW sw5_28_1564fd4

    Important! The SW introduced rather major changes, so some settings are affected too. After programming do the following:

    • While a beacon/modem is USB connected, press “Default” button (botton-right corner) to upload default settings to the beacon
    • Check radio profile settings on the beacon and on the modem. Choose the same. Otherwise, the modem won’t see beacons over the radio interface

    What is new:

    • Some bug fixes and improvements

    Updated on 12.Sep.2016

    • For HW v4.5 (5 sensors) SW pack: Dashboard SW v4.74 + Beacon SW v5.20a + modem SW sw5_20_745fac6 + DFU files

    Important! The SW introduced rather major changes, so some settings are affected too. After programming do the following:

    • While a beacon/modem is USB connected, press “Default” button (botton-right corner) to upload default settings to the beacon
    • Check radio profile settings on the beacon and on the modem. Choose the same. Otherwise, the modem won’t see beacons over the radio interface

    What is new:

    • A bug in oscilloscope timing was fixed
    • Modifified protocol. Now timestamp is milliseconds instead of alpha-cycles => our Python and C examples are not yet corrected accordingly
    • Addresses in devices will be now preserved even with major SW changes
    • It is now possible to disable additional location filtering in hedgehog by turning it off in the Dashboard. It is especially useful for small update rates of 0.5-2Hz
    • Improved timing with sending location data at update rates of 16Hz and below
    • Other minor bug fixes and improvements

    Updated on 01.Sep.2016

    • For HW v4.5 (5 sensors) SW pack: Dashboard SW v4.73 + Beacon SW v5.19 + modem SW v5.19_f6c5d90

    What is new:

    • Major new feature: NMEA support
      • Here is the NMEA protocol implementation description
    • Advanced energy saving features
      • Tested running time by beacon with 16Hz update rate and fully-charged embedded 1000mAh battery is up to 72h
      • Expected/calculated running time by beacon with 1Hz update is nearly 16 times longer => 48 days
      • External 10,000mAh power bank & 1Hz update rate on beacon shall give >1y running time from the same battery
    • Accellerated embedded oscilloscope
    • Optimized map creation for complex multi-beacon multi-submap maps with scanning ultrasonic sensor pairs feature
    • Other bug fixes and improvements

    Updated on 23.July.2016

    • For HW v4.5 (5 sensors) SW pack: Dashboard SW v4.70b + Beacon SW v5.15 + modem SW v5.15_4279848
    • For HW v4.3 (4 sensors) SW pack: Dashboard SW v4.72 + Beacon SW v5.17 + modem SW v5.17

    Important! The SW introduced rather major changes, so some settings are affected too. After programming do the following:

    • Connect each beacon via USB cable and assign addresses from the Dashboard again (2, 3, 4, etc.), since the SW resets addresses to all beacons to 1
    • While a beacon is USB connected, press “Default” button (botton-right corner) to upload default settings to the beacon
    • Check radio profile settings on the beacon and on the modem. Choose the same. Otherwise, the modem won’t see beacons over the radio interface

    What is new:

    • Major new feature: Submaps
      • You can create several independent submaps, for example, for separate rooms with 2-6 beacons in each submap or even a few submaps in one big hall and merge them into a single solid map
    • Major new feature: Dashboard => Substrate
      • You can upload your real floor layout in .png or .tiff or .jpg or .bmp format on the map with beacons and put beacons in the right position on the layout
    • Other multiple bug fixes and improvements
    • If updating from SW v4.62 and fresher, just follow basic SW routing update: Run the Dashboard => Advanced view => Firmware => Choose the file => Program

    Updated on 17.May.2016

    What is new:

    • Bug fix: when powered by external power supply, the beacons didn’t wake up
    • Bug fix: data on heights of beacons were lost at some point of time
    • Other smaller bug fixes and improvements
    • If updating from SW v4.62 and fresher, just follow basic SW routing update: Run the Dashboard => Advanced view => Firmware => Choose the file => Program

    Updated on 10.Mar.2016

    What is new:

    The key new features:

    • Support for Indoor “GPS” mini – system with two stationary beacons
    • Support of Z-coordinate in UDP protocol with the Dashboard
    • Various pther improvements and bug fixings

    Updated on 02.Feb.2016

    What is new:

    • For HW v4.5+ only! (beacons with 5 ultrasonic sensors)

    Several major improvements:

    • Support for external flash memory for additional capacity in modem
    • Support for the 5th ultrasonic sensor providing even wider coverage in ultrasonic
    • Multiple other new features

    Updated on 17.Nov.2015

    What is new:

    • Various bug fixing
    • Further usability improvements

    Updated on 02.Oct.2015

    What is new:

    • Advanced power saving modes
    • Various bug fixing
    • General usability improvements

    Important! Some earlier HW versions do not support all power saving modes. Use “Analog power in sleep” enabled first. It will increase power consumption by 5-8mA in active mode. If you happen to have a newer HW version, disable analog power in sleep. If system continues working normally – use it. It saves battery. Default mode – “disabled”, i.e. if your HW does not support it, the system won’t work stable. Updated on 20.Aug.2015 Important! Please, use addresses for beacons in the range of 2..63. There were reports that addresses 64..99 don’t always work well with SW v3.73. This bug has been fixed in the later versions.