IDBLUE Frequently Asked Questions

If any of these questions don’t seem to apply to your issue, please contact IDBLUE Support and we can walk you through any issues you might be encountering.


Apple iOS (3)

When using the HID version of IDBLUE devices, I don’t have the onscreen keyboard anymore!

This is a known issue with HID profile devices in general. Our IDBLUE HID profile device is recognized as a secondary keyboard and, by default, a smartphone may disable viewing the onscreen keyboard.

iOS:

You can toggle the onscreen keyboard by pressing the power button when connected.

Android:

Once you pair with the IDBLUE HID device:

  • Go to Settings and select “Language and input”.
  • Click on “Default” (Or “Current Keyboard” in Android 5.0+) located just under the “Keyboard and input methods” heading to open the “Choose input method” dialog.
  • Turn the “Hardware physical keyboard” OFF (or on Android 5.0+, it’s referred to “Hardware: Show input method”.

This setting will toggle the onscreen keyboard when you select a text field when paired with our HID profile device. If you have any other questions, please contact IDBLUE Support.

Permalink.

Do I need to do anything before submitting an App to iTunes Store with support for IDBLUE devices?

When working with any MFI accessory, the end user must register their app with the accessory manufacturer first as we need to whitelist your iOS app before you can submit it to the Apple App Store for approval. This is a requirement by Apple and stated in the iOS Developer Program License Agreement (as of  6/10/13).

iOS Accessories:
3.3.27 Your Application may interface, communicate, or otherwise interoperate with or control an
iOS Accessory (as defined above) through Bluetooth or Apple’s 30-pin dock connector only if

  • (i) such iOS Accessory is licensed under Apple’s MFi Licensing Program at the time that You initially submit Your Application,
  • (ii) the MFi Licensee has added Your Application to a list of those approved for interoperability with their iOS Accessory, and
  • (iii) the MFi Licensee has received approval from the Apple MFi Licensing Program for such addition.

You must supply IDBLUE with information regarding your App which we must register with Apple for approval  before your app will be whitelisted.

Requirements:

  • Your application must only start communication between your app and IDBLUE readers on an explicit action in the UI. It cannot auto­start upon connect and it must stop whenever the user stops using your application.
  • com.idblue.r8 is the only external accessory protocol that can be used by 3rd party apps. Make sure this is listed in your Info.plist in the UISupportedExternalAccessoryProtocols array.
  • After we have confirmed whitelisting of your app, you will need to add the following information to the “Review Notes” section of your Apple app submission: MFI PPID 111609-0001

NOTE: Your iOS app does not need to be re-whitelisted every time you release an update. However, we do reserve the right to remove an application from our whitelist if it appears that the app no longer meets requirements.

What are “Whitelisted” apps?

A key aspect of Mobile Application Management (MAM) is Whitelisted apps. Whitelisted apps are applications manufacturers/developers have deemed as safe to use on iPads and iPhones (Apple iOS devices) or Android phones and tablets.

What is the reason for “Whitelisting” apps?

Whitelisted apps are added to ensure that the applications being used are in fact the authorized apps and not malicious or otherwise inappropriate. These apps can be the same for all users or can be unique to each individual device group.

Additional links:

Please contact IDBLUE Support for more information.

Permalink.

How do I initialize the IDBLUE iOS SDK?

NOTE: This is taken from the IDBLUE iOS SDK documentation. Please refer to the SDK documentation for more details.

In this example, we show you how to create your own class, IDBlueApi, that inherits from IDBlueHfApi. You can use this class to communicate with IDBLUE devices.

The IDBlueHfApi takes care of all of the leg work of initializing the SDK. All you need to do is override a few methods and make a few calls into the IDBlueHfApi (and IDBlueCoreApi). You should review IResponseHandler and ISessionHandler if you haven’t already done so.

Create a class named IDBlueApi that inherits from IDBlueHfApi, like so:

// IDBlueApi.h
#import <Foundation/Foundation.h>
#import "IDBlueHfApi.h"
#import "iOSSession.h"

// By sub-classing IDBlueHfApi, IDBlueApi is the only object from the IDBLUE
// iOS SDK you need to instantiate.
@interface IDBlueApi : IDBlueHfApi {
    iOSSession* _iosSession;
}

-(BOOL) openFirstIDBlueDevice;

@end

The corresponding implementation file should look like:

#import "IDBlueApi.h"
@implementation IDBlueApi
-(id) init {
    _iosSession = [[iOSSession alloc] init];
    self = [super initWithSession: _iosSession];
    if (self) {
        // Log the current version of the SDK we are using
        NSLog(@"%@", [self sdkVersion]);
        // add custom initialization here
    }
    return self;
}

-(BOOL) openFirstIDBlueDevice {
    return [_iosSession openFirstIDBlueDevice];
}
@end

Now you’re ready to start using the IDBLUE SDK in your application. When you’re application starts, create an instance of IDBlueApi:

// Initializing the IDBLUE SDK is as simple as creating an instantiate of IDBlueApi
IDBlueApi* sdk = [[IDBlueApi alloc] init];

Before you can communicate with an IDBLUE device in your application, you need to open a session first. Since iPhone only supports one connected accessory at the moment, you can design your application to use the one and only IDBLUE device (if one is present).

To do this, use the openFirstIDBlueDevice method of iOSSession:

if ([sdk openFirstIDBlueDevice]) {
    // onSessionOpened callback method will be called when the session is open
}
else {
    // A session could not be opened. Is IDBLUE paired with the iPhone?
}

To get notifications of session events (such as session opened, session closed, etc.) you have 2 options:

  • Override the session event callback methods in IDBlueApi
  • Create a separate class that implements the protocol ISessionHandler and register it with the IDBlueiOSSdk using addSessionDelegate

Overriding the callback methods in IDBlueApi is the simpler method. To do that, add the following code to IDBlueApi.m:

// SessionHandler callback methods we are overriding
-(void) onSessionOpened: (id) session {
    [super onSessionOpened:session];
    NSLog(@"IDBLUE session opened");
}

-(void) onSessionClosed: (id) session {
    [super onSessionClosed:session];
    NSLog(@"IDBLUE session closed");
}

When using the IDBLUE iOS SDK, sessions should be managed as follows:

  • openFirstIDBlueDevice should be called when you application starts and when it resumes from the background
  • closeSession should be called when you application goes to the background and when it terminates
  • You can use the UIApplicationDelegate protocol to detect when your application resumes from the background, is going to the background and when it terminates.

Now that we have the communication completed, let’s turn our attention to sending commands to IDBLUE and handling responses.

The IDBLUE SDK is designed asynchronously. That is, when you send a command to IDBLUE, the IDBLUE SDK does not wait for a response. Applications are notified of responses via the IResponseHandler protocol. When a response is received from IDBLUE, all registered IResponseHandlers are notified of the response via the appropriate callback method.

Note: the IDBlueCoreApi is itself a ResponseHandler (a class that implements the IResponseHandler protocol). So when you want to listen for events from IDBLUE, it’s as simple as overriding the ResponseHandler methods in your IDBlueApi class.

For example:

You want IDBLUE to scan for an RFID tag, and return back the tag identifier to our application. To do this you would call readTagId. Asynchronously, one of 2 possible callback methods will be invoked: either readTagIdResponse or readTagIdFailed, depending on whether an RFID tag was read successfully or not.

// IDBlueApi.h
-(BOOL) getTagId;

// IDBlueApi.m
// Illustrates how to get IDBLUE to scan an RFID tag and give us back the tag id.
// If IDBLUE finds a tag, the readTagIdResponse callback method will be invoked.
// If no RFID tag was found or an error occurred, the readTagIdFailed callback
// method will be invoked.
-(BOOL) getTagId {
    SendStatus* status = [self readTagId:self];
    if ([status successful]) {
        NSLog(@"get tag id command sent to IDBLUE");
        return TRUE;
    }
    else {
        NSLog(@"failed to send get tag id command to IDBLUE");
        return FALSE;
    }
}

// ResponseHandler callback methods we are overriding
-(void) readTagIdResponse: (IDBlueCommand*) command
                         withResponse: (ReadTagIdResponse*) response {
        [super readTagIdResponse:command withResponse:response];
        RfidTag* tag = [response rfidTag];
        NSString* tagId = [tag toString];
        NSLog(@"Got tag id: %@", tagId);
}

-(void) readTagIdFailed: (IDBlueCommand*) command
                   withResponse: (NackResponse*) response {
        [super readTagIdFailed:command withResponse:response];
        NSLog(@"Get tag id failed");
}

Permalink.

View category→

Bluetooth Questions (4)

How far can my IDBLUE device be from a PC/Pocket PC/mobile device before it loses connection?

Bluetooth has a theoretical range of 15m (48 feet) but in every day scenarios, ideal range is 15 to 20 feet.

Permalink.

How do I pair your device over Bluetooth?

To pair our devices via Bluetooth:

  • Step 1: Turn on your IDBLUE device.
  • Step 2: Go into your System Bluetooth Settings.
    • Windows: Find the Bluetooth icon located in the system tray in the bottom right side of your desktop. Click on the Bluetooth icon and select “Add a Device” from the context menu.
    • Android/iOS: Under System Settings > Bluetooth, ensure Bluetooth is turned on and tap “Search for Devices” if it doesn’t automatically search.
  • Step 4: Place the IDBLUE device in Discovery Mode by pressing and releasing the power (rear) button. The rear LED should flash blue to indicate discovery mode for 2 minutes.
  • Step 5: The device should show up in the Bluetooth menu.
    • Windows: In the Add a Device window, the new device should show up. Highlight the device ID and click Next.
    • Android/iOS: The new device should show up in the Bluetooth menu. Tap the device name to start pairing.
    • Note: The IDBLUE device ID can be found on the back label, and should be of the format IDBLUE-(U)HF-XXXX.
  • Step 6: Enter the pairing code for the device. The default pairing code is ‘0000’ (Four zeros) – enter this pin code and click Next.
    • Note: For iOS, no pairing code is required.

That’s it! You device should now be properly Bluetooth paired – You are done.

  • If you have a Bluetooth SPP version of our RFID devices, it should load the necessary Bluetooth SPP drivers and when completed, it should be detected in any application using our IDBLUE SDK.
  • If you have a Bluetooth HID version of our RFID devices, it should load the necessary Bluetooth HID drivers and when completed, will enter the tag information in any location you can enter keyboard input.

For detailed information, please refer to our Bluetooth Pairing Guide or the IDBLUE User’s Guide on the IDBLUE Documentation page.

Permalink.

Are there any recommended Bluetooth dongles?

IDBLUE devices will work with any Bluetooth dongle that supports the Serial Port Profile (SPP). However, the out-of-the-box applications require a dongle that support one of Toshiba, Broadcomm or Microsoft Bluetooth stacks. Dongles that are known to work with IDBLUE devices are:

  • D-Link DBT-122 (Recommended)
  • D-Link DBT-120
  • IOGear GBU201
  • IOGear GBU301
  • IOGear GBU211
  • IOGear GBU311

Permalink.

View category→

Device Troubleshooting (12)

I just noticed that my Device Status LED has switched from blinking green and blue (or magenta) to blinking yellow and blue (or magenta).

The battery status LED is designed to show the following colors (for scale, approximately 8 hour usage time on a fully charged device):

  • 5 hrs = Green (Over 65% battery level)
  • 2.5 hrs = Yellow (between 35% and 65% battery level)
  • 0.5 hrs = Red (Under 35% battery level)

The Device Status LED is informing you the IDBLUE device battery is low on power and may require charging and has approximately 3 hours of usage time left.

Permalink.

I just noticed that my Device Status LED has switched from blinking yellow and blue (or magenta) to blinking red and blue (or magenta).

The battery status LED is designed to show the following colors (for scale, approximately 8 hour usage time on a fully charged device):

  • 5 hrs = Green (Over 65% battery level)
  • 2.5 hrs = Yellow (between 35% and 65% battery level)
  • 0.5 hrs = Red (Under 35% battery level)

The Device Status LED light is informing you that the IDBLUE device is now very low on power and will shut down shortly. Charge the IDBLUE device via a dedicated USB wall charger as soon as possible.

Permalink.

I plugged in my IDBLUE device for charging over a wall unit, but the Device Status LED does not indicate charging.

The charging circuitry is not receiving power or is defective.

  • Ensure that the wall electrical outlet has power. To confirm, switch to another wall outlet.
  • You may have a defective/non-compliant USB wall charger. To confirm, switch with a compliant USB 2.0+ dedicated wall charger.
  • You may have a defective USB cable. To confirm, switch the USB cable with a known good cable.
  • Try connecting the device to a computer using a USB cable to charge the device from the computer’s USB port.

If all else fails, you may have a device with defective charging circuitry. Please contact IDBLUE support for additional help as the device may be defective and should be returned to be repaired.

Permalink.

View category→

General Questions (2)

What is RFID?

RFID stands for Radio Frequency Identification.  RFID is a wireless tagging system that is the next generation of asset management technology beyond barcodes.  RFID uses RF (radio frequency) to communicate (like a cordless phone) rather than optical lasers as commonly seen in retail barcode applications.  Using RF gives the RFID tags enhanced features such as:

  • Globally unique ID
  • Smaller size
  • Rugged tag packaging and mounting
  • Secure data storage which can be changed “in the field”
  • Faster reading of RFID tags

When a company’s assets are labeled with RFID tags, they realize significant practical benefits over the “line-of-sight” barcode technologies.  Foremost among these are:

  • Automation of many costly manual processes (i.e., inventory and tracking)
  • Near real-time asset tracking providing enhanced asset visibility and management (supply chain and logistics)
  • Enhanced security and accountability
  • Significant reduction of paper work and paper-based tracking
  • Reduced losses from human data entry errors

Permalink.

What is Bluetooth?

Bluetooth®  is a wireless protocol that is used to communicate from one device to another in a small area, usually less than 30 feet. It uses the 2.4 GHz spectrum to provide a one megabit connection between two devices for both a voice channel and a 768 kbps data channel.

Permalink.

View category→

Google Android (1)

When using the HID version of IDBLUE devices, I don’t have the onscreen keyboard anymore!

This is a known issue with HID profile devices in general. Our IDBLUE HID profile device is recognized as a secondary keyboard and, by default, a smartphone may disable viewing the onscreen keyboard.

iOS:

You can toggle the onscreen keyboard by pressing the power button when connected.

Android:

Once you pair with the IDBLUE HID device:

  • Go to Settings and select “Language and input”.
  • Click on “Default” (Or “Current Keyboard” in Android 5.0+) located just under the “Keyboard and input methods” heading to open the “Choose input method” dialog.
  • Turn the “Hardware physical keyboard” OFF (or on Android 5.0+, it’s referred to “Hardware: Show input method”.

This setting will toggle the onscreen keyboard when you select a text field when paired with our HID profile device. If you have any other questions, please contact IDBLUE Support.

Permalink.

View category→

IDBLUE Questions (16)

When using the HID version of IDBLUE devices, I don’t have the onscreen keyboard anymore!

This is a known issue with HID profile devices in general. Our IDBLUE HID profile device is recognized as a secondary keyboard and, by default, a smartphone may disable viewing the onscreen keyboard.

iOS:

You can toggle the onscreen keyboard by pressing the power button when connected.

Android:

Once you pair with the IDBLUE HID device:

  • Go to Settings and select “Language and input”.
  • Click on “Default” (Or “Current Keyboard” in Android 5.0+) located just under the “Keyboard and input methods” heading to open the “Choose input method” dialog.
  • Turn the “Hardware physical keyboard” OFF (or on Android 5.0+, it’s referred to “Hardware: Show input method”.

This setting will toggle the onscreen keyboard when you select a text field when paired with our HID profile device. If you have any other questions, please contact IDBLUE Support.

Permalink.

What are IDBLUE.HF and IDBLUE.UHF?

IDBLUE.HF is the world’s first mobile Bluetooth enabled HF RFID reader while IDBLUE.UHF is our latest product which is our mobile Bluetooth enabled UHF RFID reader.

With a compact pen-shaped design complete with stylus tip, IDBLUE RFID readers are ideal for scenarios requiring human workflow such as MRO, healthcare, tracking and traceability. For more information, visit the IDBLUE RFID Readers page.

Permalink.

What frequency do IDBLUE RFID readers work on?

IDBLUE.HF is a High Frequency (HF) RFID reader able to read HF tags at 13.56 MHz using the ISO15693 protocol. For more information, please see our IDBLUE.HF product page.

IDBLUE.UHF is a Ultra High Frequency (UHF) RFID reader able to read UHF tags at 902MHz to 928MHz (915MHz center frequency) using the EPC Gen 2, ISO 18000-6C protocol. For more information, please see our IDBLUE.UHF product page.

NOTE: The UHF spectrum is regulated independently by country (which is different than the HF spectrum). Please refer to the EPCglobal > Implementation page (under Section UHF Regulations) for more detailed information. To make sure there are no compatibility issues, the UHF tag and reader have to be using compatible frequency ranges.

To determine if IDBLUE.HF or IDBLUE.UHF devices are a best fit for your project depends on the tags you want to use as well as how you want to use our devices. Our Sales Team can provide valuable insight into which one would be a best fit for your project.

For more information, please contact our IDBLUE Sales Team.

Permalink.

View category→

IDBLUE Software (0)

How do I install the IDBLUE Windows USB Driver?

 

The USB driver is required in order to:

  • Allow Windows software built with our Windows .NET SDK to communicate via USB with our devices.
  • Charge the device via USB if it can power on and enumerate properly.

Once this process is completed, Windows will use the same USB driver on any new devices plugged in. The instructions below are for Windows 7 but should the similar for any Windows version you may be using.  The IDBLUE USB driver works the same with our SPP and HID versions of our devices.

NOTE: If the device cannot power on and enumerate, it won’t communicate via USB or charge as efficiently. We recommend using a dedicated USB wall charger for charging our devices (especially if the device is in a critically low battery state and unable to turn on).

Step #1: Download and extract  IDBLUE USB driver

Download and extract our IDBLUE USB driver for Windows on the IDBLUE Drivers and Software page.

 Step #2: Plug the IDBLUE Device into a Windows USB port

When the IDBLUE device is initially plugged into a USB port, Windows should detect the new device and display the “Driver Software Installation” wizard. This will start “Searching Windows Update” process for a driver and fail as the IDBLUE driver is not part of Windows Update.

Installing Device Driver Software

Initial Driver Wizard after plugging in IDBLUE device

If you go under Device Manager, there is a new device “IDBLUE.(U)HF” under [Other Devices].

Device Manager

Device Manager showing unknown driver for IDBLUE device

Step #3: Update IDBLUE Driver from Device Manager

To load Device Manager in Windows, do one of the following:

  • Type “Device Manager” in the Start  Search field and click on the corresponding application
  • Enter “devmgmt.msc” in a command prompt
  • Start Control Center and click Device Manager under the System and Security category.
  • Right-click on My Computer, select Manage and choose Device Manager in the left menu.

Under Device Manager, right-click the IDBLUE device and select the “Update Driver Software…” context menu and manually point Windows to the the driver location of the extracted IDBLUE USB Driver files in Step #1.

IDBLUE Windows USB Driver

Windows Security confirmation when installing IDBLUE Windows USB Driver

When the USB driver is finished installing, the device will enumerate and emit a Low-High tone as well as show up under a new Device Manager [IDBLUE Devices] grouping as “IDBLUE (U)HF RFID Reader”.

IDBLUE Driver successfully installed

IDBLUE Driver successfully installed

Device Manager screenshot with USB driver

Problems Installing the USB Driver

If you don’t get the “Driver Software Installation” wizard, it could mean it was previously detected with no driver or the device isn’t powered on and enumerated. If it was previously detected, follow the procedure above in Step #3.

If you are using the legacy USB driver, the IDBLUE device will show under [Ports (COM & LPT)] category as “IDBLUE HF RFID Reader (COM##)”.

For additional information, you can also download our IDBLUE USB Driver Installation Guide on our Device Documentation page.

If you have any other questions or problems, please contact IDBLUE Support.

Permalink.

View category→

IDBLUE USB Driver (1)

How do I install the IDBLUE Windows USB Driver?

 

The USB driver is required in order to:

  • Allow Windows software built with our Windows .NET SDK to communicate via USB with our devices.
  • Charge the device via USB if it can power on and enumerate properly.

Once this process is completed, Windows will use the same USB driver on any new devices plugged in. The instructions below are for Windows 7 but should the similar for any Windows version you may be using.  The IDBLUE USB driver works the same with our SPP and HID versions of our devices.

NOTE: If the device cannot power on and enumerate, it won’t communicate via USB or charge as efficiently. We recommend using a dedicated USB wall charger for charging our devices (especially if the device is in a critically low battery state and unable to turn on).

Step #1: Download and extract  IDBLUE USB driver

Download and extract our IDBLUE USB driver for Windows on the IDBLUE Drivers and Software page.

 Step #2: Plug the IDBLUE Device into a Windows USB port

When the IDBLUE device is initially plugged into a USB port, Windows should detect the new device and display the “Driver Software Installation” wizard. This will start “Searching Windows Update” process for a driver and fail as the IDBLUE driver is not part of Windows Update.

Installing Device Driver Software

Initial Driver Wizard after plugging in IDBLUE device

If you go under Device Manager, there is a new device “IDBLUE.(U)HF” under [Other Devices].

Device Manager

Device Manager showing unknown driver for IDBLUE device

Step #3: Update IDBLUE Driver from Device Manager

To load Device Manager in Windows, do one of the following:

  • Type “Device Manager” in the Start  Search field and click on the corresponding application
  • Enter “devmgmt.msc” in a command prompt
  • Start Control Center and click Device Manager under the System and Security category.
  • Right-click on My Computer, select Manage and choose Device Manager in the left menu.

Under Device Manager, right-click the IDBLUE device and select the “Update Driver Software…” context menu and manually point Windows to the the driver location of the extracted IDBLUE USB Driver files in Step #1.

IDBLUE Windows USB Driver

Windows Security confirmation when installing IDBLUE Windows USB Driver

When the USB driver is finished installing, the device will enumerate and emit a Low-High tone as well as show up under a new Device Manager [IDBLUE Devices] grouping as “IDBLUE (U)HF RFID Reader”.

IDBLUE Driver successfully installed

IDBLUE Driver successfully installed

Device Manager screenshot with USB driver

Problems Installing the USB Driver

If you don’t get the “Driver Software Installation” wizard, it could mean it was previously detected with no driver or the device isn’t powered on and enumerated. If it was previously detected, follow the procedure above in Step #3.

If you are using the legacy USB driver, the IDBLUE device will show under [Ports (COM & LPT)] category as “IDBLUE HF RFID Reader (COM##)”.

For additional information, you can also download our IDBLUE USB Driver Installation Guide on our Device Documentation page.

If you have any other questions or problems, please contact IDBLUE Support.

Permalink.

View category→

Software and Development (14)

I have established connection to the device and having successful reads. However, the information of my reads is not being communicated back to my host application.

For Developers:

When developing this can happen for a few reasons:

  • The IDBLUE device sends the information back to the host application asynchronously via the established Bluetooth connection. Ensure that the connection is active and that the application is properly processing the asynchronous information from the IDBLUE device. Refer to the IDBLUE Firmware Interface Guide on our IDBLUE Documentation page for more information.
  • The IDBLUE device must be configured in a Connected Mode to retrieve the asynchronous tag information. Refer to the section Connected Operating Mode in our IDBLUE Users Guide on our IDBLUE Documentation page for more information.

For End Users:

This can happen due to improper device configuration settings. Please try power cycling your device and retry. If that doesn’t work, please try a Factory Reset which can be done from our IDBLUE RFID app. This will reset all configurable device properties back to their default settings.

Permalink.

What platforms are supported by IDBLUE.HF and IDBLUE.UHF?

IDBLUE devices are compatible with the following Bluetooth stacks:

  • Microsoft®
  • Broadcomm
  • Toshiba

IDBLUE provides out of the box support for:

  • Microsoft Windows 7, 8®, Microsoft Windows Vista®, Microsoft Windows XP®
  • Microsoft Windows Mobile 2003®, Windows Mobile 5® and Windows Mobile 6®
  • Apple iPad and iPhone

IDBLUE provides development tools for:

  • Microsoft Visual Studio.NET 2005®
  • Microsoft Visual Studio.NET 2008®
  • Apple XCode
  • Google Android

For other platforms, IDBLUE provides all of the necessary interface documentation required for communication with the IDBLUE device.

Permalink.

What software tools are available for IDBLUE devices?

IDBLUE provides multiple software packages as a free download for use with IDBLUE RFID reader:

  • IDBLUE Developer’s Toolkit: A toolkit to be used by developers of RFID applications. The toolkit contains:
    • Drivers and sample applications with source code for Visual Studio.NET® development
    • Developer Documentation including a Developer’s Guide and .NET Reference Guide
    • USB Driver for charging IDBLUE devices from a computer
  • IDBLUE Demonstration Package: A number of demonstration applications to showcase the use of IDBLUE devices. These include:
    • An Asset Management demonstration for Windows Mobile®
    • An RFID Workflow demonstration for Windows Mobile®
  • IDBLUE Serial API Document: For developers using a platform other than Visual Studio .NET. IDBLUE also provides the Serial API Document which provides the required information to communicate directly with an IDBLUE device. It’s available on our IDBLUE Documentation page

The IDBLUE software packages may be downloaded from our Drivers/Software page.

Permalink.

View category→