1) It is strongly recommended to use only the latest available SW. If not the latest, the SW compatibility between modem, beacon, and Dashboard SW is not guaranteed.
To update the SW on your devices:
Download the SW (see the links below: "Latest stable SW to download") on your hard drive
Connect beacon or modem via USB to your computer. Make sure that only one device (either modem or beacon) is connected via USB, while programming!
Run the Dashboard => Advanced view => Firmware => Choose the file => Program
After programming, which takes a few seconds, press the HW reset button on modem/beacon
Double-check in the Dashboard that the modem/beacons contains now the expected version of the SW
2) Some new SW versions bring very substantial changes to the internal protocols and become incompatible with previous SW version. Thus, always keep the same SW versions on all beacons. Also use only compatible versions of the modem and the Dashboard SW, since they come in a package (beacon SW + modem SW + Dashboard SW) and all shall support the same protocols.
3) Double-check that the beacon's address is the same after SW updating. Major changes in SW versions may lead to the device's address to be overwritten. If happened, use the Dashboard to assign the required address to the beacon again.
stm32_vcp.zip - required to connect beacons/modems to the Dashboard via USB. It needs to be installed only once on your Windows PC.
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.
Here is the Python code for Linux-based devices integration via virtual UART via USB
Library is easy to use. Also, here is detailed description and example
Code is fairly universal; Tested on:
Mac (OS X 10.10)
CRC calculation is done in "pythonic way", i.e. library crcmod is used
There are handlers of different exceptions, for example, non-standard states of COM/USB
The Python library provides quick and easy ability for integration of ultrasound navigation system 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 web page).
The best place to start, if you have questions, is to check FAQ and ask questions there, if you haven't found the answer. Usually, we reply the same day or faster.
We do currently provide extensive support to our customers via email too. Don't hesitate to ask questions. Just drop us an email on: email@example.com
Before starting working with the system, please, check the operating manual. It will guide you through all aspects of working with the system, setting it up and tuning for the best performance.
Check that power switch is in the right position: switch 1 must be OFF and switch 2 must be ON. When the board is charged and switch is on, the LED on the board is blinking every a few seconds
See demo video for more details. Note, that the video is taken for the previous HW version. The newer HW version, for example, has a different combination for DIP switch settings (power supply switch). But the main starting in steps are the same
Make sure that the map of beacons is frozen in the Dashboard before starting using the mobile beacon
Also make sure that the mobile beacon is in "hedgehog" mode - mobile beacon mode - not in the stationary beacon mode
Check that correct SW versions are installed on the beacons, routers, hedgehog, dashboards. It is recommended to download the latest version from Download SW
One can check the SW version of any device by connecting it to the dashboard via USB. If already connected via radio interface, the SW version is also visible, if the device is awake
Charging is done automatically when device is connected to USB. It takes 1-2h to fully charge the battery
Notice a tiny side-looking reset button on the boards. Use it, if you are stuck
Beacons go asleep automatically, if not visible via radio interface to modem/router for more than 1 min. They can be woken up