Scanner Wedge for Windows
Microvision has updated Scanner Wedge for Windows to version 1.1.
The biggest change in V1.1 is that support for international
versions of Windows was added. With previous versions of Scanner
Wedge, bar code data was sometimes altered based on the keyboard
settings of the Windows operating system. Scanner Wedge 1.1 for
Windows resolves this issue and supports many international settings.
Contact support for the various keyboards and languages supported.
Another change in V1.1 is improved interaction with Bluetooth
stacks from Broadcom.
Scanner Wedge for BlackBerry and Microvision SDK for BlackBerry
You can now use your Flic Cordless Scanner with the BlackBerry
Pearl 8100. Microvision has updated Scanner Wedge for BlackBerry
to version 1.1 and our SDK for BlackBerry to version 39. These
updates support the new RIM 4.2 OS update on the BlackBerry Pearl
8100, 8800, 8700, and 7130. Scanner Wedge 1.1 for BlackBerry and SDK
for BlackBerry remain backwards compatible with the RIM 4.1 OS.
Partner Spotlight - SerialMagic API from Serialio.com
There are many ways to interface application software to Flic
Scanners. To simply add bar code scanning input to an existing application a software wedge works well. Other applications that require additional control over the scanner or bar code data flow benefit from the SDK. There is
an “in between” solution - the SerialMagic Pro API.
Available for Windows, Windows Mobile, Palm, and BlackBerry, the
SerialMagic Pro API provides the easiest path to integrate the
Flic Scanner into your application while maintaining control over
your data.
While the methods vary by platform, the general concept of the
SerialMagic Pro API is to provide two features.
First, SerialMagic
provides the user interface and setup for connecting to the Flic
Scanner. This minimizes the time and effort required of developers
to provide the scanner interface in their application. Second,
SerialMagic provides a programmatic interface for passing the data
from SerialMagic to the application. Think of this as an event
that is generated by SerialMagic that the application can capture
and act upon.
The benefits of the SerialMagic Pro API are:
• Provides user interface
and connection management for the Flic Laser Bar Code Scanner
• Bypasses shortcomings of keyboard
input:
- Keystroke injection permissions
on BlackBerry
- Data going to wrong application
- Data being entered in wrong
field
- Application has complete
control over data formatting
• Provides fastest path to application integration
The next generation of Flic Scanner USB connectivity is here.
So what’s new?
Two Configurations
This new Flic Scanner USB Cable is available in two forms, a five foot
straight version and a coiled version for portable applications.
Both cables connect the scanner directly to the computer
- the USB adapter cable is no longer needed.
Two Unique Operating Modes
Both coiled and straight USB cables can operate in ‘Keyboard
mode’ and ‘VCOM mode’.
VCOM mode is no different from the current USB cable – it
still allows Windows applications to assign a virtual COM port
to the scanner.
Keyboard mode turns the cable into a simple hardware
wedge. No wedge connectivity software is required to scan bar
codes into an application. By emulating a USB HID-compliant device,
the scanner becomes plug’n’play. Keyboard mode
is supported for both Windows and Mac platforms.
Easy installation
Although the VCOM mode requires a driver, it can now be installed
before or after the cable is plugged in.
Keyboard mode installation is nearly instantaneous on Windows
computers as it uses standard HID drivers. Mac users simply plug
in the cable, scan a bar code when input is required, and configuration
is complete.
More affordable
The new USB cables retail for $24.95 MSRP – about half the
price of the previous USB cables.
RoHS Compliant
To comply with European requirements and recently enacted legislation
in the United States, both USB cables are RoHS complaint.
What are symbology identifiers
and how can
I make use of these in an application?
Symbology Identifiers
are codes that identify the specific bar code symbology scanned.
This identifier can also include additional details about
the symbology such as if supplemental information was included,
if the check digit was stripped, etc. You can configure the Flic
Scanner to return the Symbology Identifier with
each scanned bar code. There are many ways your application can
use the Symbology Identifier including:
Your
application can reject bar codes symbologies not supported by your
application. For example, if your application uses Code-39 bar
codes then you can alert the user if a UPC bar code is scanned.
This method gives you the flexibility to check the bar codes on
the host computer. As an alternative you can disable unwanted bar
code symbologies in
the Flic Scanner itself. As an application
designer you have the flexibility to perform the symbology checking
on the scanner (through configuration) or on the host (through
software).
Certain
bar code symbologies are normally used
for specific types of data. For example, RSS is used in the health
care industry and retail products typically use UPC. The carton
(or “case”) that holds the retail product normally
uses ITF (also called “Interleaved 2 of 5” or “I
2 of 5”). If the application detects the ITF bar code then
it can process the data for the case differently than for the individual
retail item.
The Flic Scanner supports
two types of Symbology Identifiers, namely, AIM
Codes and NCR Codes. AIM codes seem to be used more
frequently. AIM Symbol Identifiers use this format:
]cm
where:
]
Symbology
indicator ($5D hex)
c
AIM
Code (Symbology identification):
A = Code 39,
C = Code 128,
e = RSS
E = EAN/UPC
I = ITF (I 2 of 5)
m
AIM
code modifier
The AIM code modifier varies depending on the
bar code symbology. For example, the modifiers for Code 39 are:
0 = No check character or Full ASCII
1 = Reader performed mod 43 check
2 = Check character was stripped
3 = Check performed and stripped check char
The NCR symbology identifiers
are:
A = UPC-A
E = UPC-E
F = EAN-13
FF = EAN-8
A = Code 39
B = ITF (Interleaved 2 of 5)
F = Code 128, UUC/EAN-128
R = RSS
You can enable the symbology identifiers
using SDK function calls, sending an S (SET) command (if writing
an interface from scratch), or by scanning a control bar code.
Customer Success Story – Thompson
Grading Improves Productivity withMobile
Time and Job Tracking Solution from Actsoft.
Using a BlackBerry handheld on the Nextel network, Actsoft’s
Comet Tracker software and a Flic Cordless Scanner, Thompson Grading
synchronized the home office with field-based job and time tracking.
With this solution they gained the following benefits:
» Reduced Overtime—Thompson Grading realized monthly
savings, contributing to company health and profitability.
» Increased Productivity—Crew leaders now redirect
hours previously used to deliver documentation to job better on-site
job management.
» Improved administration—Sharing documents keeps
track of the details that affect
job costing and customer billing.
Why did they choose the Flic Scanner?
» It was Simple: One-button operation captures bar code data and
pushes it to BlackBerry application via Bluetooth connection.
» It was Affordable: Low acquisition cost, no training required,
and common AAA batteries makes for low Total Cost of Ownership
(TCO).