- Professional Navigation SDK
- Installation and Activation
- Installation of 2D Navigation
Installation of 2D Navigation
You can install the navigation from the set of 3 resources, typically sent by email:
- navigation+sdk package as download link
- map package as download link
- license file as file attachment
Our supported Windows platform are WindowsCE, Windows Mobile, WindowsXP and Windows 8, and the installation procedure is the same for all of them.
Download the navigation+sdk package zip with our Contact form. Make sure WindowsCE as Operating system is selected in the contact form.
You will receive the download link to your email in few seconds.
Installation of Navigation
Prepare installation image
Out of the downloaded packages you need to construct the following folder structure setup (image).
Drive\ Res\ Maps\
We recommend to construct it locally on your computer. And finally as such copy it on your target device.
The installation image needs to be constructed through merging the contents of the two packages and a license file.
The navigation+sdk package with its subfolder Navigation/Sygic2D fills the Drive and Res folders. You also need to place .apk in the root.
The content of the map package needs to be copied inside the Maps folder, which should be cleaned up before if e.g. populated with demo maps. As the last step the license file (mlm file) needs to be copied inside the Maps folder. Finally the image should look as follows (the example with Europe map).
Drive\ Res\ Maps\ alb\ and\ aus\ bel\ ... Europe.mlm license.txt
Installation on device
Installation of navigation is about to copy the image to an appropriate place on sdcard or internal memory. Typically the image is copied to the device's root folder as follows (example with sdcard):
sdcard\ Drive\ Res\ Maps\
Alternatively it can be placed inside a wrapping folder and moved into an arbitrary location, example Sygic2D:
sdcard\ Sygic2D\ Drive\ Res\ Maps\
But please note that positioning of the Sygic software in the device's file system is subject to device's configuration capabilities as well as your requirements for application invocation.
Invoking the navigation on device
The navigation invocation is about to start Drive.exe application, which is on one of the following paths depending on your platform:
The invocation of the application can be done in several ways:
- clicking on Drive.exe file in OS shell or through File Manager
- filling the Drive.exe full path in a device configuration. Then typically power off an on the device for auto start. Alternatively there is often a special GUI button to trigger the application
- by means of a call from another program
Activating the navigation
In the use for testing purposes you can Activate with a trial code.
If you purchased licenses for commercial usage the navigation needs to be activated according to an agreed mechanism.
The following activation scenarios are supported:
Note: In case you downloaded a demo package the activation is not needed
as the package contains demo maps inside requiring no activation.
Installation of SDK library
The installation of SDK library means storing it locally on your computer to be available for compilation.
Next, the SDK library also contains the communication drivers, which needs to be copied on device for run-time operations.
Use for compilation
Compilation with C#
For successful compilation you need to include the file SDK/Lib/.NET/ApplicationAPI.NET.dll into a project using Add Reference. The compilation tool normally makes sure the dll file is placed next to the resulting application exe file as it is needed for runtime.
Compilation with C++
For successful compilation you need to include the file SDK/Lib/CPP/Platform/Application.lib using Add Reference.
where Platform corresponds to your actual platform (OS), e.g. WindowsCE for ARM, or WindowsXP for Win32.
You also need to include the header files from SDK/Include/Compiler, where Compiler is the compiler you use.
We support two compilers: Visual Studio 2005 or 2008 (folder name VS2005), and Embedded Visual 4.0 (folder name eVC4).
Alternatively you only need to include the header and cpp files from SDK/Include/Compiler into your project.
In such case you do not need to link ApplicationApi.lib for compilation.
Use for runtime
Depending on your platform/OS you need to copy the appropriate communication drivers next to the application exe.
The drivers are ApplicationApi.dll and sdkdriver.dll and you need to select them from the folders SDK/Drivers/Platform, where Platform corresponds to your actual platform (OS), e.g. WindowsCE for ARM, or WindowsXP for Win32.
In addition to it, for .NET applications you also need to have ApplicationAPI.NET.dll from SDK/Lib/.NET next to the application exe.
Attention: When moving to a new version of the SDK library, please make sure you remove any old versions of dlls from device. It might be you copied the dlls into Windows system folders, and this takes precedence over positioning it next to the application exe.