Windows Embedded POSReady and POS for .NET Blog : POS for .NET

Interfacing with Biometric Devices from POS applications

posblog — Wed, 23 Sep 2009 19:19:00 GMT

Support for Biometric devices (such as fingerprint readers) was added to the Unified POS specification and incorporated into Microsoft’s POS for .NET in version 1.10. This device category allows applications to interface with such devices and is helpful in capturing and verifying biometric data (such as a finger print). This blog will attempt to describe one possible way to interface with this device using POS for .NET. As always, the developer should first carefully read and understand the Unified POS specification for this device category before attempting to interface with the device (See chapter 5 of Unified POS specification v1.13). Also, before you interface with a physical device, you must install a .NET Service Object for the device (contact the hardware vendor to get the .NET service object). Note that legacy OPOS based service objects are not supported for this device category, one must have a .NET Service Object for this device.

First, an application will want to know what biometric devices are available. This can be done using the PosExplorer class. For example, to get an ArrayList of all Biometric devices, one would do the following:

// Create an instance of an explorer synchronizes events to the main form's thread.

explorer = new PosExplorer(this);

// Create a list of all available biometric devices and bind them to the list box

biometricList = new ArrayList(explorer.GetDevices(DeviceType.Biometrics));

Next, an application may want to register for the DeviceAddedEvent and the DeviceRemovedEvent. Doing so will allow the application to respond to plug-n-play events for the device. Once the application has a device, it will need to do the normal open, claim, and enable as well as subscribe to the required events. This can be done as follows:

// Create an instance of the device, open and claim it.

activeBiometricDevice = (Biometrics)explorer.CreateInstance(selectedDevice);

activeBiometricDevice.Open();

activeBiometricDevice.Claim(1000);

// Enable the device, subscribe to date events, and enable data events

activeBiometricDevice.DeviceEnabled = true;

activeBiometricDevice.DataEvent += new DataEventHandler(activeDevice_DataEvent);

activeBiometricDevice.ErrorEvent += new DeviceErrorEventHandler(activeBiometric_ErrorEvent);

activeBiometricDevice.DataEventEnabled = true;

activeBiometricDevice.StatusUpdateEvent += new StatusUpdateEventHandler(BiometricsStatusUpdateEvent);

The above snippet will open, claim, and enable the device. It will then subscribe to desired events and will enable data events. Once this is done one can use the device as desired. Typically, one will use the beginEnrollCapture() method in order to capture biometric data for a given user. This method customarily results in a series of biometric data captures aggregated together returned in the final form of a BIR (see “beginEnrollCapture” method in the UPOS specification for more detail). Status update events may be provided to instruct the user what actions are required during this process. Status information may include indications such as:

· StatusSensorReady – typically indicates that the device is ready for the user to swipe their finger or provide other biometric data

· StatusSensorComplete – indicates that the biometric data has been captured

· StatusMoveSlower – Indicates that the user needs to move slower

· Etc.

After issuing a beginEnrollCapture method one will wish to save the data in the BiometricsInformationRecord property that is available after a data event. This data is associated with the user providing the biometric input and will be used to identify the person when attempting to verify the user. In order to identify a person, one needs to issue a BeginVerifyCapture command to the device. Again Status update events may be provided as well as a data event (if desired, one can end the operation by issuing an EndCapture command). In response to the data event, the application can then pass a list of BiometricsInformationRecord data to the service object via the IdentifyMatch() method to determine if the biometric data provided by the user matches any contained within the list. This can be done as follows:

List<BiometricsInformationRecord> birs = /* Your list of BIR data */

int[] order =

activeBiometricDevice.IdentifyMatch(50, 0, true,

activeBiometricDevice.BiometricsInformationRecord /* current biometric data to match */,

birs /* list of biometric data to check for match*/ );

Where order[] is a list that identifies all users where the biometric data provided matches within the criteria range specified. Well, that is pretty much all that is needed in order to get biometric data from a user (in the form of a BIR) and then to later verify that the biometric data matches a previously provided BIR.

Setting the BinaryConversions property for Legacy OPOS service objects

posblog — Fri, 18 Sep 2009 18:28:00 GMT

Microsoft’s POS for .NET supports both native .NET service objects and legacy OPOS service objects which are based upon OLE technology. Normally, POS for .NET interfaces with the legacy devices without any issues and this is done without any interaction or knowledge required by the application. However, there are some rare instances where an application may need to know if the service object is based upon OPOS or .NET. For example, in the rare cases where the OPOS service object requires that the BinaryConversion property be set to a value other than the default the application would need to know the type of service object that it is working with.

Because the BinaryConversion property is specific only to OPOS devices within the standard, it is not exposed by .NET service objects. However, one can still access this property when working with legacy OPOS service objects when this is required by the service object. This can be done by casting the service object returned by the POSExplorer to: ILegacyControlObject. Using the cast type, one can then get and set the BinaryConversion property and other OPOS specific properties.

The default value for the BinaryConversion property is None. However some devices, such as the Ingenico Signature Capture (SigCap) device, may require that the value be set to Nibble or Decimal. In such cases, the application would need to cast the device returned by the POSExplorer to ILegacyControlObject and then set the BinaryConversion property to the desired value (such as Nibble).

To learn more about the BinaryConversion property or any other variations of the standard that are specific to OPOS based service object, see page A-24 of Appendix A of the UnifiedPOS standard specification which is freely available at: http://www.nrf-arts.org/UnifiedPOS/default.htm. The help documentation included with the POS for .NET SDK also has some helpful information.

POS for .NET Forum

posblog — Fri, 19 Jun 2009 23:11:00 GMT

Microsoft is proud to announce the availability of the POS for .NET forum. This forum is intended to provide an opportunity for .NET developers to share their knowledge and experiences as they leverage the power of POS for .NET. In order to help foster greater awareness by the .NET developer community of the options for interfacing with POS peripheral devices, this forum has been created under the .NET Developer Forums. Developers and end-users who previously used the Microsoft.public.windows.embedded.pointofservice newsgroup are encouraged to check-out the new forum!

The forum may be accessed via a web browser at: http://social.msdn.microsoft.com/Forums/en-US/posfordotnet/

- Sylvester

Microsoft POS for .NET will be demonstrated in the ARTS Pavilion at NRF

posblog — Tue, 06 Jan 2009 19:48:00 GMT

Microsoft will demonstrate how you can create an optimum checkout experience by mixing and matching devices for convenience and speed using UnifiedPOS based POS for .Net at the ARTS Pavilion at NRF. Come join us at the ARTS Pavilion booth where you can see demonstrations of POS for .NET with the latest devices and device capabilities. We will show how to use POS for .NET to interface with devices such as Biometric reader, secure MSR, RFID. In addition, the demonstration will be performed on POSReady 2009, the newest operating system supported by POS for .NET. Stop by the booth to meet with developers and to learn more about POS for .NET.

- Sylvester

Managment tools may require WMI Namespace to be recreated after SP3 update

posblog — Thu, 11 Dec 2008 02:41:00 GMT

If you use the management tools that are dependent upon WMI (such as posdm.exe), the WMI namespaces may need to be recreated after significant OS updates (such as applying SP3). A temporary fix, can be done by choosing the repair option from the installer; however, the recommended fix, in order to avoid future reoccurrences, is to use mofcomp as described in the attached document.

- Sylvester

Supported Device Categories

posblog — Mon, 01 Dec 2008 21:22:00 GMT

POS for .NET v1.12 support all 36 device categories included in the Unified POS specification as of version 1.12. IHV may develop a native .NET service object for any of the following device categories:

· Belt

· Bill Acceptor

· Bill Dispenser

· Biometrics

· Bump Bar

· Cash Changer

· Cash Drawer*

· CAT

· Check Scanner*

· Coin Acceptor

· Coin Dispenser

· Electronic Journal

· Electronic Value RW

· Fiscal Printer

· Gate

· Hard Totals

· Image Scanner

· Item Dispenser

· Keylock

· Lights

· Line Display*

· MICR

· Motion Sensor

· MSR*

· PIN Pad*

· Point Card RW

· POS Keyboard*

· POS Printer*

· Remote Order Display

· RFID Scanner*

· Scale

· Barcode Scanner*

· Signature Capture

· Smart Card RW

· Tone Indicator

In addition, base classes are provided which greatly simplify the development of .NET service objects for the nine (9) categories marked with the asterisk (*) above.

POS for .NET includes support for legacy OPOS service objects for the following device categories:

· Cash Drawer

· CAT

· Check Scanner

· Coin Dispenser

· Keylock

· Line Display

· MICR

· MSR

· PIN Pad

· POS Keyboard

· POS Power

· POS Printer

· Scale

· Barcode Scanner

· Signature Capture

· Tone Indicator

Finally, the SDK provides device simulators and sample code that can be used during development and testing for the following device categories:

· Cash Drawer

· Check Scanner

· Keylock

· Line Display

· MSR

· PIN Pad

· POS Keyboard

· POS Printer

· Barcode Scanner

- Sylvester

POS for .NET v1.12 Updated with Improved Plug and Play Support

posblog — Wed, 08 Oct 2008 01:32:00 GMT

POS for .NET v1.12 Updated with Improved Plug and Play Support

Among other new features, the POS for .NET v1.12 update provides improved Plug and Play support for service object developers. The previous Plug and Play model only worked with devices that were recognized by the Windows® Plug and Play subsystem. Several device types do not fall in this category, such as some Smart Card, Biometrics, and Bluetooth devices.

In order to provide Plug and Play functionality to these devices, a new means of support was added to POS for .NET 1.12. This support includes exposing two new interfaces to service object developers, IDeviceEnumeration and IDeviceEnumerationPnP.

See thte attached docment for more details.

-- Sylvester

Useful Resources for Developers

posblog — Sat, 20 Sep 2008 02:07:00 GMT

Download page:

http://www.microsoft.com/downloads/details.aspx?FamilyID=eaae202a-0fcc-406a-8fde-35713d7841ca&displaylang=en

Team Blog:

http://blogs.msdn.com/pointofservice/

POS for .NET Forum:

http://social.msdn.microsoft.com/Forums/en-US/posfordotnet/

Usenet Newsgroup:

microsoft.public.windows.embedded.pointofservice

http://www.microsoft.com/communities/newsgroups/list/en-us/default.aspx?dg=microsoft.public.windows.embedded.pointofservice

MSDN Documentation:

http://msdn.microsoft.com/en-us/library/bb848020.aspx

Sample Scanner (TechEd 2008 HOL)

http://blogs.msdn.com/pointofservice/attachment/8590083.ashx

Unified POS specification:

http://www.nrf-arts.org/UnifiedPOS/default.htm

Common Control Objects (OPOS):

http://monroecs.com/oposccos.htm

- Sylvester

Problems with Motorola/Symbol Scanner? Here are a few things to check.

posblog — Mon, 08 Sep 2008 20:05:00 GMT

If you are trying to use a Motorola/Symbol scanner with POS for .NET, and you encounter issues, here are a few things to check:

1. Make sure that the scanner is configured properly. For scanners such as the 2208 or LS1900 series, it should be configured as “IBM HAND-HELD USB”. You can configure the scanner by using the configuration barcodes provided with the scanner. First scan “SET DEFAULTS” followed by “IBM HAND-HELD USB.” In this configuration, the scanner will function as a USB Human Input Device (HID) instead of as emulating a keyboard.

2. If using the scanner with the legacy OPOS service objects provided by Motorola, install the service objects and make sure you select the correct device in your application (such as STI_USBSCANNER). See Step 3.

3. If using the scanner with the legacy OPOS service object provided by Motorola, always install the Common Control Objects afterwards. It turns out that Motorola will install a custom control object over any existing control objects already installed, yet the current version of the Motorola control object (STI OPSO 1.5) which is included in the latest installer for the service object (version 3.24) does not appear to support late binding. Thus, you should always install a control object that does support late binding (such as the CCO) after installing the Motorola service object. Hopefully, this issue will be corrected soon. WARNING: some of the scanners with a manufacture date between April and May of 2008 may have compatibly issues with HID input. If your scanner was manufactured between these dates, there is a firmware update available from Motorola that should correct this issue.

4. If you want to test the scanner with Plug-n-Play in a non-production environment, you may use the example service object included in the SDK by adding the following XML to your control configurations folder:

</ServiceObject>

</PointOfServiceConfig>

Currently, native .NET service objects are not available from the manufacture for this scanner, thus features such as plug-n-play are not supported at this time. While it is possible to configure the scanners to work with the example service object in order to achieve plug-n-play capabilities, this is not recommended in a production environment. Other scanners are available that provide native service objects and Plug-n-Play support.

Installing POS for .NET from Your Installer

posblog — Fri, 20 Jun 2008 21:17:00 GMT

Version 1.12 of the installer for POS for .NET is available for download here: http://www.microsoft.com/downloads/details.aspx?FamilyID=EAAE202A-0FCC-406A-8FDE-35713D7841CA&displaylang=en

The download from this website contains a self-extracting archive. Once the archive is downloaded and extracted, you will find the following content:

Setup.exe - This is the installer setup program for POS for .NET.

1033 - This folder contains language localization files for the setup.exe installer.

Documentation - This folder contains release notes used by the setup.exe installer.

POSFor.NET - This folder contains the POSfor.NET.msi and related files used by the setup.exe installer.

Res – This folder contains resources used by the setup.exe installer.

VCRuntime – This folder contains the installer for the Visual C runtime.

If you would like to install POS for .NET on your local system, simply use the Setup.exe program to perform the installation. When you run the installer, you will be presented with a number of installation options:

Typical – Installs the POS for .NET runtime components and the PosDM command line tool

Complete – Installs POS all components (runtime, PosDM, and SDK)

SDK – This installs the SDK documentation and sample code

The installer can also be used from the command line or to perform silent installs from within your own installer. To see a list of available options, run the setup.exe with the /? option from the command line. The most commonly used options include:

/ADDLOCAL [feature list or “ALL”] – silent install of the specified features

/REMOVE [feature list or “ALL”] – uninstall the specified features

/REPAIR [feature list or “ALL”] – silent repair of an installation.

The “/ADDLOCAL” feature will add the components specified (if they are not already installed) using a silent install. The feature list is a common separated list and may include one or more of the following options:

Runtime – Indicate the POS for .NET runtime

Posdm – Indicates PosDM management tools

SDK – Indicates the SDK

ALL – Specifies all of the above components

For example, to perform a typical installation one could invoke setup from within their own installation program with the following options:

Setup.exe /ADDLOCAL Runtime,Posdm

Other MSI arguments (such as /s for silent install) may also be passed on the command line.

It is recommended that when installing POS for .NET from another installer to use the setup.exe instead of the MSI. This will ensure that all dependent components (such as the C runtime) are present. NOTE: When performing silent install, you should install the required components (Visual C Runtime, .NET Framework 2.0.50727) if they are not already installed.

- Sylvester

POS for .NET at TechEd 2008

posblog — Tue, 10 Jun 2008 18:41:00 GMT

It was great meeting so many of our customers at Tech Ed 2008. We had a session that was intended as an introduction to POS for .NET, a hands-on lab for developers, and a booth that demonstrated a possible integration of WePOS and POS for .NET in “the lane of the future.”

For those who were unable to attend, I’m going to attach a hands-on lab to this blog. The lab is split into components that target software developers and hardware vendors. Setup instructions are included at the end of the lab. In order to complete the .NET service object and Plug-n-Play portions of the lab, one will need a USB barcode scanner.

Share your POS for .NET experience with Microsoft

posblog — Tue, 13 May 2008 18:12:00 GMT

The Windows Embedded Marketing team is interested in your POS for .NET experience. If you are interested in sharing your experiences with using POS for .NET, or would like to be considered for a joint case study, please e-mail wepos@microsoft.com.

Thanks,

- Sylvester

Microsoft Point of Service for .NET v1.12

posblog — Wed, 12 Mar 2008 20:19:00 GMT

Microsoft Point of Service for .NET v1.12 has now been released and is available for immediate download at the Microsoft downloads site.

POS for .NET v1.12 has been updated to be fully compliant with the latest release of the Unified POS specification. New devices that have been added includes:

· Belt

· Electronic Value RW

· Gate

· Item Dispenser

· Lights

· RFID Scanner

In addition the there is now support for encrypted MSR devices as well as some updates to the FiscalPrinter.

- Sylvester

Best practices for finding available devices

posblog — Wed, 27 Feb 2008 20:57:00 GMT

The Unified POS specification, “UnifiedPOS Retail Peripheral Architecture” available at http://www.nrf-arts.org/UnifiedPOS/default.htm, makes a distinction between a Device Name and a Logical Device Name. The device name is expected to be unique among other devices within the same device class. The default value of the Device Name key is the Service Object Name. There are cases, however, where the application or system administrator, may wish to add a level of isolation between the service object and the application. In such cases, one or more logical device names may be created to represent a device. The posdm.exe command line utility provides one way for administrators to assign logical device names.

When writing an code, it is best to avoid any assumptions that all devices will have a logical device name. When attempting to query available devices, it is recommend that one use the logical device name(s) if available; however, if a logical device name is not available, then the code should fall back to the service object name. Finally, if the service object name is not available, the code should fall back to the device description.

Below is an implementation of the GetDeviceDisplayName() method, taken from the sample Test Application included in the SDK, that demonstrates the above logic:

static string GetDeviceDisplayName(DeviceInfo device)
{
    string name = CombineNames( device.LogicalNames );
    if (name.Length == 0)
    {
        name = device.ServiceObjectName;
        if (name.Length == 0)
            name = device.Description;
    }
    return name;
}

- Sylvester

New WEPOS & POS for .NET Training Course

posblog — Fri, 17 Aug 2007 02:52:00 GMT

SJJ Embedded Micro Solutions, one of our Windows Embedded Partners, announced that they have put together a new training course: “Introduction to Windows Embedded for Point of Service / POS for .NET”. Their webpage states that "the course covers the fundamentals and features of WEPOS and POS for .NET." And that there is a specific "focus on POS for .NET 1.11 with support for C# and VB.NET developers."

It is a one day course with dates already scheduled on September 21st and November 2nd. Check out more details here.

If you know of any other courses or trainings covering WEPOS or POS for .NET in your area, please let us know so we can help spread the word!

- Shayna