January 30, 2008
What's New?
Welcome to the January edition of the FlicWatch Developer Newsletter, the last edition of this newsletter by the name "Flicwatch!" It is now up to you to help us name the newsletter, you could win $100! Read this month’s Flic Fact to learn more about the ROV Scanner’s power specifications when using regular alkaline batteries versus rechargeable batteries. Check out the Flic Tip to learn how to deploy a software application to mobile devices.
To support application development for the ROV Scanner, we’ve developed new SDKs for Windows®, Windows Mobile® and BlackBerry®. Read the "You Ask, We Answer" to learn more about what's new with the SDKs.
Check out the second edition of Trend Spotting, to understand how an Open Handset world will affect application development.
Regards,
The Bar Code Scanner Team at Microvision
Events
CTIA Wireless
April 1-3, 2008
Las Vegas, Nevada
http://www.ctiawireless.com
Come visit us at booth #4411
Would you like to meet with us? Let us know!
GSMA World Congress
February 11-14, 2008
Barcelona, Spain
http://mobileworldcongress.com
Would you like to meet with us? Let us know!
Groundhog Day
February 2nd, 2008
http://www.punxsutawneyphil.com/
Our prediction? He'll be too busy with his ROV Scanner to even notice his shadow.
Observant readers of the FlicWatch Developer Newsletter have by now realized that Microvision has released the ROV Scanner. This event has us, and now you, rethinking the newsletter name.
As with the naming of the original newsletter we’d love your brain share. To spur your thinking we are offering you Fortune and Fame. Fortune is all relative but we’re willing to part with an AMEX gift card valued at $100 USD in exchange for the winning newsletter name. If that weren’t sufficient by itself we’re also willing to provide Fame – yes the person who submits the winning name will be highlighted in a future newsletter. We will also note honorable mentions in an upcoming newsletter.
What are you waiting for? This is your chance to see yourself in lights.
Multiple submissions are A-OK.
Click here to submit a new name for the Developer Newsletter!
Flic Fact: ROV Feature - Rechargeable Battery Support
The ROV Scanner is powered by three AAA batteries; Alkaline (non-rechargeable) and rechargeable batteries are both supported. Typical AAA alkaline batteries are rated around 1000mAH of stored energy. Once the energy has been expended, the batteries must be replaced. Rechargeable batteries, however, are more varied in their energy capacity:
NiMH – 800-900 mAH
LiIon – 400-500 mAH
NiCad – 300-400 mAH
Also, keep in mind rechargeable batteries suffer from self-discharge over time (some refer to this as "leak"). When deciding among the common rechargeable battery technologies, Microvision recommends that ROV Scanner users select NiMH batteries because they have the highest energy capacity, the lowest self-discharge rate, and highest number of useful recharges (attaining >50% of energy capacity).
Typical Battery Life*
ROV Scanner
Alkaline (1000mAH) AAA 12,000 scans / 6 months
NiMH (900mAH) AAA 10,000 scans / 5 months
ROV Scanner with Bluetooth**
Alkaline (1000mAH) AAA 7,000 scans / 3.5 months
NiMH (900mAH) AAA 6,000 scans / 3 months
*As tested 100 scans/day, 5 days a week
**As tested 100 scans/day, 5 scans per Bluetooth connect/timeout (20 reconnects per day), 5 days a week
Results may vary when using different types of rechargeable batteries as they may contain less energy capacity and suffer from higher rates of self-discharge.
Flic Tip: Deploying Software
to Mobile Devices
Microvision has developed multiple Scanner Software offerings for the ROV Scanner. However, deploying software to mobile devices can be burdensome and time consuming, leading to high support costs and long deployment time. To help IT managers with the decision process, here are three options for software deployment.
Desktop Executable: This file can be downloaded or emailed to a user’s desktop computer. From there, the user will sync their mobile device via a utility provided by the device manufacturer (e.g. Microsoft ActiveSync for Windows Mobile devices) and run the executable.
Manual OTA (“Over the Air”): The raw install file is hosted on a website that the user must access through the mobile device’s web browser (note: data service plan is required). Once clicked, the link will download and automatically install the software onto the device.
Push OTA: Push OTA is enabled through mobile device management software solutions. These software solutions allow administrators to wirelessly “push” software application files directly to a user’s device, regardless of location, without requiring user interaction. These solutions typically also offer device management tools as well.
Choosing the Method of Distribution
Desktop Executable |
Manual OTA* |
Push |
|
Ideal Geographic Distribution of Devices |
Near |
Near- Far |
Near-Far |
Ideal Deployment Size |
1-10 |
1-20 |
20+ |
Complexity for User |
High |
Medium |
Low |
Time to Deploy (software) |
Long |
Medium |
Short |
Time to Deploy (solution) |
Medium |
Short |
Medium/Long |
Cost (solution) |
Low** |
Low** |
Medium/High |
Software Upgrade Difficulty/Time |
High |
Medium |
Low |
*Requires mobile data service plan.
**Though direct cost is Low, method is prone to high support costs.
Available Microvision Scanner Software
|
Microvision |
3rd Party |
|
Desktop Executable |
Manual OTA |
Push |
|
Scanner Wedge for Windows Mobile |
|||
Scanner Wedge for BlackBerry |
N/A |
BlackBerry Enterprise Server (.JAD/.COD files available on request) |
|
SerialMagic Pro for Windows Mobile, BlackBerry, Symbian and Palm |
N/A |
N/A |
|
Microvision is currently exploring its OTA software distribution for other mobile software products.
What method of deployment do you or your customers typically use? Tell us!
Question: What's the difference between the old Flic SDKs and the new ROV Scanner SDKs?
The ROV Scanner includes new functionality not available in the Flic Scanner. In order to take advantage of this added functionality, Microvision developed a new set of SDKs. These SDKs support Windows, Windows Mobile, BlackBerry; other platforms are planned for the future. The ROV Scanner SDK uses a different programming interface in order to take full advantage of the added functionality of the ROV Scanner.
Added Controls
The Flic Scanner SDK used a DLL with a C interface. Functionality for the .NET programming languages was provided using “wrapper” files that created the proper interface for that language. The Microvision SDK for the ROV Scanner includes a DLL with a basic C interface but it also includes an ActiveX control and an Interop Component. The ActiveX control provides an extremely simple interface that works well with most simple data capture applications. The Interop Component allows you to use a scanner Namespace and Class in your .NET applications. You create a scanner object and interact with the scanner using the methods and properties contained in the scanner object. For C/C++ development you can use the C interface that is native to the SDK DLL.
Powered by Events
The Flic Scanner SDK required the application to use timers to check the state of the scanner. The application had to poll the scanner to check for data and status. The Microvision SDK for the ROV Scanner uses event notifications to alert the application when noteworthy events occur. Your application receives event notifications when it receives data, when it receives a banner, when a command response is received, when attempting to connect via Bluetooth, when the scanner goes out of Bluetooth range, and when the scanner reconnects to the host. Your application only needs to respond to the events that you need to service. Most applications only handle the BarCodeDataReceived event but you have the flexibility to handle the other events if you so choose.
Simplified Configuration
The Flic Scanner SDK included a large number of scanner configuration functions. The Microvision SDK for the ROV Scanner uses only three functions to configure the scanner, set scanner properties, and read scanner properties. These functions use the XSP (eXtensible Scanner Protocol) commands and properties to interact with the scanner. When new functions and properties are added you can access these new features using the existing SDK functions/methods. That is, the SDK can remain unchanged even when new properties and commands are added.
Summary
The Microvision SDK for the ROV Scanner takes full advantage of the additional features built into the ROV Scanner. You can now respond to event notifications rather than rely on polling the scanner. The SDK package includes the SDK files, XSP Programming Guide, and a number of sample applications in various programming languages.
>> Visit the Microvision Developer Site
Trend Spotting: Application Development in an Open Handset world
The “Open Handset Alliance” (OHA), sponsored by Google, is a group of more than 30 companies who have come together to accelerate innovation in mobile devices and offer consumers a richer, less expensive, and better mobile experience. Validating the need for an “open” world; HTC, Motorola, Samsung, Qualcomm, Texas Instruments, Sprint and T-Mobile and others have all joined the OHA. In a related move, Verizon Wireless announced it would allow any compatible devices or software to run on its wireless network later this year.
Ultimately, the goal of a grand alliance between handset manufacturers, carriers, high tech companies and others is an “open” mobile environment. The driver behind this is “Android”, a truly “open” offering that includes an open-source OS, middleware and key mobile applications. Android will enable true cross-hardware and cross-carrier application development. These applications will be compatible with all devices running Android, regardless of ROM versions, network carriers, etc. So for independent developers, life becomes less complicated. A win for developers is a win for users.
Historically, proprietary operating systems, carrier-customized device ROMs and other prohibitive functions have severely hindered mobile application development. For example, key features such as Bluetooth are deactivated or altered for specific ROMs, even when this was a key selling point of the handset. These sort of changes cause significant differences among devices and end up making application development and deployment incredibly time consuming, difficult and costly.
Android and the OHA will greatly benefit application developers and end users, alike. It’s the long-awaited solution to the highly fragmented world of mobile devices and applications.
To learn more about the Open Handset Alliance, click here.
To learn more about Android and the early Android SDK, click here.
Flic Beat: ROV Scanner Spotting
This ROV Scanner was recently spotted preparing for a trek through the Himalayas. Rumor has it the Sherpas need to inventory their yaks.
For your own look at the ROV Scanner, come visit us at CTIA Wireless in April.
Submit your own ROV Scanner Spotting!
Developer FAQ
Case Studies
Three ways to put the ROV Scanner to work for you right now.
Check out the Compatibility Matrix and Platform Resources
Report device compatibility issues or successes.
Developer Support - Need Help?
Buy a ROV Scanner online
Flic® is a registered trademark and ROV ™ is a trademark of Microvision, Inc. BlackBerry® is a registered trademark of Research in Motion, Ltd. Windows®, Windows Mobile® and ActiveX® are registered trademarks of Microsoft, Inc. Symbian® is a registered trademark of Symbian Software Limited. Palm® is a registered trademark of Palm, Inc. Bluetooth® is a registered trademark of Bluetooth SIG, Inc.
Click
FlicWatch Developer Newsletter.
