You can also download source codes of the Demo application, where you can find examples on how to integrate Navigine SDK. They are available at GitHub.
Please note that you can find full documentation about integrating Navigine SDK here.
You need internet connection on the target device to work with the application.
Sign in the Demo Application. Apply e-mail and password that you used in the CMS website.
Choose a location to work with and tap it to activate for measurement and navigation. The active location is checked.
Using the Add Beacon mode
Once the map archive is loaded, you can run the Add beacon mode - simply tap the Add Beacon button in the main menu.
In the mode “Add beacons” you can measure a radiomap (signals in your environment) of your target location and manipulate beacons (add/delete). To activate the measurement tools, choose one type of the object that you need to measure: beacon or polyline measurement.
Select the sublocation you want to record logs on. Use the drop-down menu on the top.
Click on “measure log along polyline” button in the top left corner.
Specify a polyline (a route that you will take while recording log).
A polyline is presented by a set of points that you will have to specify in this menu. Note, that starting point will be created at the position of cursor upon clicking on bottom right button. Other points are specified by moving cursor to proper place and clicking **“Add point”**. After last point is specified, you click **“Finish”**. If you made some mistakes and want to cancel this line, simply click on bottom right button again.
Go to start point of specified polyline. At that point you click **“Start Measuring”** and start walking along route and at the same time. For log recording procedure we assume a constant velocity motion, so please don’t make stops during log recording and try to keep approximately same speed during walking.
Each time you pass another checkpoint (vertex), you click **“Checkpoint”** in the application, so that application can bind your current position to current time label. All passed points and sections will be marked with green color.
Warning: avoid misclick. If you press checkpoint at the wrong time - delete the log and record again. To guarantee that all checkpoints were pressed correct, try to avoid points overlapping - select simple long routes with equally distributed points.
Figure above shows recording log along the polyline, green line is the previous trajectory, blue polyline is the route to pass, blue points are future checkpoints
After last checkpoint you will be shown the name of resulting log file and you can click **“Finish”**.
To share the log-file: go to “Profile” tab → “Machine Wheel” (top right corner) → “Log management” → Tap on file name → share.
Use this mode to control data and check application working capacity
For Beacon navigation, check the “BEACONS” section for “entries/sec” number. For configured location with installed beacons, “entries/sec” number should be above 3.0
If the number in brackets (number of total visible devices) is less than the number of total beacon installed → some beacons are not detected/visible/not working.
For WiFi scanning, the WiFi must be turned on and new signal entries should be visible
Configure the Navigine Demo Application settings using the Settings button in the application's main screen. You can also use the Settings menu to enable some debug features like saving logs, changing power modes, and so on.
The following options are available:
Background navigation mode Toggle switch - enable collecting coordinates while the application is minimized
Power saving modes (available with Background navigation mode ON):
NORM radio button - enables normal mode when the device modules (e.g. Wi-Fi, Bluetooth) scan for available signals continuously. Battery usage is high, while the navigation is more accurate compared to ECO modes.
ECO-1 radio button - enables economic mode, when only Bluetooth and sensor modules (accelerometer) are used for navigation. In this mode the applications scans the available modules periodically, while Wi-Fi and GPS modules are not scanned at all. Navigation accuracy in ECO-1 mode might be worse than in NORM mode, while battery usage is 4-5 times less.
ECO-2 radio button - enables super economic mode, when only Bluetooth module is used for navigation, and delays between scanning are even bigger than in ECO-1 mode. In ECO-2 mode, navigation accuracy might be worse than in NORM and ECO-1 modes, while battery consumption is 10-15 less than in NORM mode.
Save navigation log - if on, a log file with all sensors' measurements will be created after the next Navigation mode use. You can send this log file accompanied by the true traversed path to the Navigine support to resolve any possible issues with indoor positioning accuracy. Default path to the file is: /android/data/com.navigine.navigine/<location_name>
Save navigation track - if on, a log file with all measured coordinates (path) will be created after the next Navigation mode use. Default path to the file is: /android/data/com.navigine.navigine/<location_name>
Send statistics to the server - if on, the application will send positioning results to the Navigine server. In this case you can view positions of the device in real time in the Analytics tab of the Navigine CMS. You can view the history of device's movement in the Heatmap mode of the Analytics tab.
Send crashes to the server - if on, the application will send the errors to the Navigine server.
Debug mode enabled - if on, the Debug mode appears in the Main menu.
Navigation file enabled - view path from the log file created via Save navigation log feature.