Windows Embedded SDKs & Tools - Motorola Solutions LaunchPad ...

Windows Embedded
SDKs & Tools
Prashanth Kadur
Software Architect

Agenda
Introduction to Development Tools
EMDK
DataWedge
Resources

Introduction to Development Tools

Introduction to Development Tools
Family of Products
This presentation will provide a brief introduction to development tools and their
features. Refer to the product help documentation for detailed information.
These products provide developers with the tools necessary for creating applications that
target the enterprise mobility features, such as scanning, printing, Bluetooth, MagStripe,
Sensors, Vehicle Bus and RFID
There are two major development tools:
• EMDK family of products
o EMDK for C supports developing C/C++ applications.
o EMDK for .NET supports developing managed application.
o EMDK for Java supports developing Java applications.
• DataWedge. DataWedge is a utility that allows you to add advanced data capture
capability to any application without writing code.

Introduction to Development Tools
Requirement for EMDK
EMDK for C
Requirements for
developing “C” (native)
applications
• Microsoft’s Visual Studio 2005 or Visual Studio 2008
• Microsoft’s WM 6.5 SDK for WM 6.5 devices such as ES400
• Motorola’s PSDK for CE devices such as MC2100
• EMDK for C v2.5 Update2
EMDK for .NET
• Microsoft’s Visual Studio 2005 or Visual Studio 2008
Requirements for
developing .NET
applications
• Microsoft’s Visual Studio 2005 or Visual Studio 2008
• Microsoft’s WM SDK 6.5 for WM 6.5 devices such as ES400
• No PSDK required for CE devices such as MC2100
• EMDK for .NET v2.6 Update2
EMDK for Java
Requirements for
developing Java
applications
• Eclipse IDE for Java Developers for targeting J9 JVM
• NetBeans IDE v6.0 Mobility or higher for targeting Crème JVM
• J9 or Crème JVM
• Java SDKs (refer to the EMDK for Java website)

Introduction to Development Tools
Requirement for DataWedge
DataWedge
Requirements
for using
DataWedge
• Requires the DataWedge to be running.
• Latest devices come with the DataWedge preinstalled
(but not enabled)
• Download DataWedge from Support.Symbol.Com
for older devices
• No other requirements

Introduction to Development Tools
Why do I need EMDK? Isn’t DataWedge enough?
DataWedge is a powerful tool for capturing data.
For many application, DataWedge is more than enough and there is no need for using
EMDK
However EMDK is very useful if:
You want to access features that are not available in DataWedge. For example
Bluetooth, Fusion (Extended WiFi interface), Image capturing etc.
If you want a complete control of the feature such as scanning in your application
Backward compatibility

Introduction to Development Tools
Why do I need EMDK? Isn’t Microsoft SDK enough?
Microsoft SDK is enough for a number of operations
However, Microsoft SDK may provide little or no access to Motorola value added features
scanners, magstripe reading, Telemetry, RFID etc…
Bluetooth: Microsoft does not have a .NET solution. Motorola .NET solution for BT
provides a simplified and abstracted solution to both Microsoft and Stonestreet stacks.
Image capturing: Customers find Microsoft DirectShow too complicated. Motorola
Imaging APIs are simple yet powerful.

Introduction to Development Tools
Why do I need EMDK? Isn’t Microsoft SDK enough?
Image Capturing: Microsoft does not have .NET solution. Motorola does.
Fusion: Motorola APIs provide extended access to Wi-Fi. Microsoft APIs provide only a
high level access.
Sensors: Motorola APIs provide extended access to Sensor devices such as accelerometer,
Orientation, Compass, Ambient Light, Proximity etc.

EMDK

EMDK
Features (not all devices support all features)
Audio
Audio Extension
Display
Fusion
Image Capture
Keyboard
MSR / DCR
Notification
Printing
Resource Coordinator
RFID/RFID2/RFID3
Scanning (with RS)
Telemetry (VC6096 only)
IO (VC6096 only)
Keylight (VC6096 only)
StoneStreet One Bluetooth
MS Bluetooth
Sensor
Document Capture

EMDK
Sensors on devices to be released very shortly
Multiple of sensors integrated to platform to sense and react to environmental changes.
These sensors include
• Accelerometer
• Magnetometer
• Gyroscope
• Ambient Light Sensor (ALS)
• Near Range Proximity Sensor
Sensor APIs provides an interface to enumerate available
Ability to access sensor data and configure certain parameters of sensors.

EMDK
Document Capture
Document Capture (DocCap) feature provides the ability to capture an image of a
document. In this case, “document” refers to a printed page or label. If the captured
image contains a barcode, the barcode data can also be captured.
The document capture can be performed using one of the following 3 modes:
• Barcode-anchoredanchored - In this mode, a specified part of the label is captured based on
its relative position to the barcode in the label. The document must contain a
barcode.
• Free-form
- In this mode, the document is captured by identifying the border and
contrast between the document and the surface behind it. The document may
optionally contain a barcode.
• Barcode-linked
- In this mode, the document is captured by identifying the border
and contrast between the document and the surface behind it. The document must
contain a barcode.

EMDK
Scan&Pair in EMDK for .NET
Provides simple methods to scan a BT barcode and pair/unpair with that device.
Supports only SPP on the remote device
Simple to use – Only 2 lines of code (see next slide)
First the scanning of the address is performed, the validity of the scanned data is checked
and then an attempt is made to pair with the device using the PIN provided
Uses - Bluetooth printers and PCs

EMDK
Scan&Pair in EMDK for .NET
Using Symbol.Barcode and Symbol.WPAN
Using Symbol.PowerTools
private Reader myScanReader = null;
private ReaderData myScanReaderData = null;
Bluetooth myBT = null;
RemoteDevice myRemoteDevice = null;
private void TestScanAndPair()
{
myBT = new Bluetooth();
myBT.Enable();
myScanReader = new Reader(Device.AvailableDevices[0]);
myScanReaderData = new ReaderData(ReaderDataTypes.Text,
ReaderDataLengths.MaximumLabel);
myScanReader.Actions.Enable();
myScanReader.ReadNotify += new EventHandler(myScanReader_ReadNotify);
myScanReader.Actions.Read(myScanReaderData);
}
void myScanReader_ReadNotify(object sender, EventArgs e)
{
ReaderData rd = this.myReader.GetNextReaderData();
if (rd.Result == Symbol.Results.SUCCESS)
{
// Invoke into main thread and call PairRemoteDevice passing rd.Text
}
}
private void PairRemoteDevice(string BTAddress)
{
myRemoteDevice = new RemoteDevice(string.Empty, rd.Text, string.Empty);
myRemoteDevice.LocalComPort = 5;
myBT.RemoteDevices.Add(myRemoteDevice);
myRemoteDevice.Pair("0000");
}
private void Form1_Closing(object sender, CancelEventArgs e)
{
myReader.Actions.Flush();
myReader.Actions.Disable();
myReader.Dispose();
myBT.Dispose();
}
private void TestScanAndPair()
{
ScanAndPairTool mySP = new ScanAndPairTool();
if (ScanAndPairResults.SUCCESS ==
mySP.ScanAndPair("0000"))
{
// Perform serial communication operations
}
}

EMDK
LocateAndLaunch
Uses GPS
Executes pre-defined set of actions when the device changes geographic location. Some
of the actions:
• enable/disable Bluetooth
• enable/disable WiFi
• enable/disable WAN
• launch a pre-defined application
• log the movements of the device to a file
The app running on the device provides GUI access for using this feature without writing
code
The .NET interface API provides programmatic access to this feature

EMDK
Design Considerations
Understand the different types of keyboards: QWERTY & non-QWERTY keyboards. Some
devices may just not have any keyboard.
Understand the size, shape, screen resolution, screen orientation of the display : QVGA,
VGA.
Touch and non-touch display – If supporting touch and non-touch, design your app to
perform all touch operations (such as buttons, links, pull downs etc) on a non-touch
device.
Support for Microsoft & StoneStreet One Bluetooth stacks. Most of devices have both
stacks. Some devices may support only one stack. Apps written in “C” cannot be ported
to other stack. .NET apps written using EMDK are mostly portable.
For MS stack, use com port from 0 to 9 if not used. For SS1, refer to the following registry
for available com ports:
• HKEY_LOCAL_MACHINE\Software\StonestreetStonestreet One\BTExplorer
BTExplorer\Device
Settings\FactoryCOMPorts

EMDK
Design Considerations
For scanning purposes, your device may have 1D scanner and/or 2D imager or 2D camera.
Cameras are generally not optimized for scan intensive applications.
When scanning, do not enable all available symbologies. Enable only the required
symbologies for performance gain.
Imagers can be used for taking pictures. But for quality pictures, use camera if the device
has one.
Your app may require to scan and then take pictures. In this case, you cannot have both
scanner/imager and camera enabled at the same time. Disable scanner and then enable
camera.

EMDK
Design Considerations
For capturing pictures, you can use Microsoft DirectShow. Many customers have found
DirectShow to be very complicated to write code for. Motorola offers Imager API which is
easy to understand and simple to write code, but yet provides access to numerous
advanced configuration settings of the camera.
Some devices may not have built-in scanners or imagers for scanning. Consider using
external scanners/imagers such as RS309, RS407, RS419 or RS507 (Bluetooth).
The latest devices (both CE and WM) come with Compact Framework (CF) 3.5. Older WM
devices were shipped with CF2.0.
No support for Visual Studio 2010. VS2010 does not support Windows Mobile or CE
development.

EMDK
Design Considerations
Motorola products support several mobile printers from different vendors. Motorola’s
printing API provides a simple and abstracted interface for printing.
If porting application from an older version of CE to the latest Embedded Handheld 7.0,
please note there are a number of APIs either deprecated or obsoleted. use
CeAppCompat to determine the compatibility of your app.
• APIs removed: http://msdn.microsoft.com/en-us/library/aa924080.aspx
• APIs deprecated: http://msdn.microsoft.com/en-us/library/gg154286.aspx
Many of the devices come with GPS. The advanced settings such as enable A-GPS SUPL,
Quality of Position, Enable Access to SUPL Server, Smart Aiding/Reaiding, Estimated
Coarse Location etc under the registry:
• HKLM\Software\Symbol\GPSMux

DataWedge

DataWedge
What is DataWedge?
DataWedge is a utility that allows you to add advanced data capture capability to any
application without writing code.
It runs in the background and handles the interface to barcode scanners, magnetic stripe
readers and communications ports (USB and Serial).
The captured data is converted to keystrokes and sent to the target application as if it was
typed on the keypad.

DataWedge
Automatic data Switching
Allows different behaviors for different target applications
Create a configuration profile for each application
DataWedge monitors foreground application and switches profiles if new application
appears
Example usage: Disable barcode scanning when picture taking application comes to
foreground.
Internet Explorer Pictures and Videos

DataWedge
Buffered Data Collection
Data is queued to allow fast and continuous collection of data with controlled transfer to
slow applications.
0123456789010

DataWedge
Advanced Data Formatting (ADF)
ADF allows the captured data to be automatically modified using a set of rules before
being sent to the target application.
Capture
Modify
Send to Target
0123456789010
A123456789A1A
ADF Rules
• Crunch Spaces
• Replace String
• Send Remaining
• Etc.

DataWedge
API for Enabling and Disabling
Any application can easily control DataWedge.
Allows an application to disable DataWedge input when user input or picture taking is
required.
Prevents inadvertent scans into your application when it is not ready to accept the data.

DataWedge
Remote Configuration
Settings and profiles can be configured remotely over ActiveSync using Internet Explorer
running on a PC.
Allows non-touch and headless devices to be easily configured.

DataWedge
XML Configuration
Settings and profile information are stored in XML files. When configuration is completed
for one device, the XML files can be deployed to other devices using provisioning tools
such as MSP.

Resources

Resources
For access to the tool downloads
Go to the “Developer Kits and software tools” page on Support Central
To create an account and get notification of new releases
Register your email address on Support Central web site
For a datasheet on development tools
Download the EMDT datasheet from the Motorola web site
For a datasheet on configuration tools
Download the EMCT datasheet from the Motorola web site
For more information on the complete toolset
Visit the Enterprise Mobility Development & Configuration Tools page
For information on the EMDK Collateral page
Visit this Compass page for Datasheets, Power Point presentations etc.
Click Here
Click Here
Click Here
Click Here
Click Here
Click Here

THANK YOU