Opticon OPN2002 User manual

1
CAUTION: This information is subject to change without prior notice.
Copyright 2009, Opticon Sensors Europe BV, all rights reserved.
This manual may not, in whole or in part, be copied, photocopied, reproduced, translated or converted
to any electronic or machine readable form without prior written consent of Opticon Sensors Europe.
THE GENERAL USE AND FUNCTIONING OF THE BAR CODE SCANNER IS DESCRIBED IN THIS
DOCUMENT. ALSO GENERAL SETUP INSTRUCTIONS TO GET STARTED ARE DESCRIBED IN
THIS DOCUMENT. FOR FURTHER INSTRUCTIONS CONSULT OPTICON OR YOUR LOCAL
DEALER.
First release – October 2009
OPN2002 BLUETOOTH DEMO QUICK SETUP GUIDE
(Version RFG35311)
The OPN2002 terminal is supplied with a Bluetooth demo application that
demonstrates its Bluetooth capabilities. Since the OPN2002 terminal does not have
a display to display instructions nor has a keyboard to change the demo application
implements a user interface that consists entirely of using just the 2 keys and
scanning barcodes. This brief setup guide describes the features as well as
instructions to be able to use this demo application.
More product details, additional support or configuration options to your own
preferences (by Universal menu book) will be updated at www.opticon.com
Information about how to install and use a Bluetooth stack on your remote device,
like a PC or mobile device, please check the manual of your Bluetooth device.
Capabilities of the Bluetooth demo application (RFG35311)
The following features are currently supported:
Connecting to a remote device (as master) and transmit its data using a
Bluetooth virtual COM port (VCP)
Making the OPN2002 connectable (as slave) and discoverable to allow a
remote device to connect with the OPN2002 and allow the transmission of its
data using a Bluetooth virtual COM port (VCP)
Making the OPN2002 connectable (as slave) and discoverable as HID
(keyboard) device to allow the remote device to connect with the OPN2002 and
transmit its barcode data as Bluetooth keyboard device.
Reconnecting to a paired remote device (as master) to quickly re-establish a
lost Bluetooth HID connecting without having to re-enter a PIN code.
(Limited) OSE menu book support to configure all barcode decoders, pre- and
suffixes, change Bluetooth configurations and switch between HID or VCP as
Bluetooth interface.
Possibility to configure a remote Bluetooth address and PIN code using
barcodes
Smart use of the trigger and clear key to connect, disconnect, make
discoverable / connectable and reconnect.
Storing of configurations in non-volatile memory to allow all settings to be
restored after a reset.
Easy software upgrading by USB (VCP) or the CRD-2000 multi cradle (RS232)
using Appload.

2
Configuring the Bluetooth demo application
Minimum required OS version
This demo application requires the following minimal OS version: RBGV0204. If this
application was already installed on arrival the minimal (or a newer) OS version
should already be installed.
If you want to check the currently installed OS and application version it is possible
to transmit both versions by USB-VCP by reading the 'Z1' menu label (See
Universal menu book chapter 7). It's also possible to use Appload (Utilities > Show
software version) to check the OS version.
Software updates
In the future more features and bug fixes are likely to be implemented into the OS of
the OPN2002 and this application. To find out if there are software updates
available, please check our web site. All available software and documentation for
the OPN2002 can be found under:
'Service and support' > 'Software' / 'Manuals' > 'OPN2002' at www.opticon.com.
Supported defaults
The following default settings are supported.
(The labels below can be read without reading any SET/END labels)
Bluetooth VCP *
(default)
Bluetooth HID *
* If you only have a OSE Universal menu book available which doesn't list 'C02' or
'C05' as supported defaults, it's possible to use RS232 ('U2') or Bluetooth ('SO')
instead of 'C05' and USB-HID ('SU') instead of 'C02'.

3
Connecting your OPN2002 as Bluetooth keyboard (HID)
The first step of connecting your OPN2002 as Bluetooth keyboard to a remote
device is to make sure the Bluetooth HID default is configured (see 'Supported
defaults').
When using Bluetooth HID, the remote device always has to make the first
connection attempt. Therefor it is not necessary to configure the remote Bluetooth
address, but you will have to make your OPN2002 discoverable and connectable to
allow the remote device to find, pair and connect to your OPN2002.
To make your OPN2002 discoverable and connectable (for 2 minutes) keep the
small clear key pressed for 5 seconds till the blue LED starts blinking. When this is
done, let your remote device discover all Bluetooth devices in range to find your
OPN2002.
Print screen of an OPN2002 that has been discovered on a remote PC.
After you've discovered your OPN2002 you can try to let your remote device
connect with your OPN2002.
Depending on your Operating system you will either be asked to enter any PIN code
on your remote device or you will be shown a random PIN code. Either way you will
be requested to enter that same PIN code on your OPN2002.
If you are allowed to enter any PIN code, then it is easiest to choose the last 4 digits
of the Bluetooth address of your OPN2002 as PIN code since that is the default PIN
code of your OPN2002. To skip having to enter a PIN code on your OPN2002 read
the 'Fixed PIN code' label below to configure this. To change this configuration back
to default again (= entering the PIN code manually) you can read the other label.
Use fixed PIN code Enter PIN code manual
(using numeric direct input labels)

4
If you want to use a different PIN code or you are only allowed to enter a random
PIN code on your OPN2002, then you will have to enter this PIN code using direct
input labels. These labels can be found in the universal menu book (or below). After
entering the PIN code read the END label to send the PIN code to the remote
device.
When executed correctly your OPN2002 should now be connected as keyboard and
you should be allowed to scan and transmit barcodes as keyboard data. If the
remote device does establish the pair, but doesn't automatically connect, you might
have to manually connect afterwards by pressing the trigger key for 5 seconds.
To manually end a connection you can press the small clear key for 5 seconds to
disconnect your OPN2002.
If you've lost your connection, then the OPN2002 will try to reconnect automatically
once after about 1 minute, but if that fails you can reconnect manually by pressing
the trigger key for 5 seconds. The trigger key allows you to reconnect without having
to enter the PIN code again as long as the remote device doesn't lose the pairing
information and the OPN2002 wasn't reset to default or the remote Bluetooth
address was changed.
If the pair was ever lost or you want to connect to another remote device you will
have use the clear key again to make your OPN2002 connectable and allow the
remote device to connect and pair with your terminal.

5
Connecting your OPN2002 as a Virtual COM port (VCP)
First step of connecting your OPN2002 as Bluetooth keyboard to a remote device is
to make sure that Bluetooth VCP default is configured (see 'Supported defaults').
When using Bluetooth VCP, the remote device can either connect to your OPN2002
(slave mode) or your OPN2002 can connect to remote device (as master).
Note: Currently it is recommended to disable authentication / encryption on your
remote device to avoid any troubles with having to enter a PIN-code on your
OPN2002.
Configuring a remote Bluetooth address
If you want the OPN2002 to connect to a remote device (as master) it will be
necessary to configure the Bluetooth address of the remote device first.
Usually the address is displayed on the product label as a hexadecimal code
(example: 00-11-F6-03-39-69). Otherwise consult the documentation of the device
how to retrieve the device address code. To configure this Bluetooth address in the
OPN2002 you'll have to create a barcode label containing this hexadecimal code as
described below.
Opticon provides a simple on-line application on for this purpose:
http://opticonfigure.opticon.com/bluetooth.asp
Type in the digits of the hexadecimal code in numbers and capital characters
without dashes, dots and spaces (example: 0011F6033969).
Submit the code into a barcode and print the screen to have it available for
scanning.
After you've created the barcode, you should scan the barcode to configure the
Bluetooth address and save it in non-volatile memory. (The OPN2002 will
automatically to try to establish a Bluetooth connection when reading this label).

6
Connect as master
When you want your OPN2002 to connect with a remote device you can either read
the created Bluetooth address labels or you can choose to press the trigger key for
5 seconds (until the blue LED starts blinking).
Even though authentication is not recommended when using VCP it is possible that
you are requested to enter a PIN code on your PC. By default the PIN code of the
OPN2002 equals the last 4 digits of the Bluetooth address.
When executed correctly your OPN2002 should now be connected as Virtual COM
port on your remote device and you should be allowed to scan and transmit
barcodes as serial data.
If you've lost your connection, then the OPN2002 will try to reconnect for about 1
minute, but if that fails you can also reconnect manually by pressing the trigger key
for 5 seconds.
To manually end your connection you can press the small clear key for 5 seconds to
disconnect your OPN2002.
Connect in slave mode
When you want the remote device to connect with your OPN2002, then it is not
necessary to configure the remote Bluetooth address, but you will have to make
your OPN2002 discoverable and connectable to allow the remote device to find and
connect to your OPN2002.
To make your OPN2002 discoverable and connectable for 60 seconds keep the
small clear key pressed for 5 seconds till the blue LED starts blinking. After that you
should let your remote device discover all Bluetooth devices in range to find your
OPN2002.
After you've successfully discovered your OPN2002 you can try to let your remote
device connect with your OPN2002.
If successful, the OPN2002 should now be connected as Virtual COM port on your
remoted device and you should be allowed to scan and transmit barcodes as serial
data.
If you've lost your connection, then the OPN2002 will become connectable again for
about 60 seconds, but if that fails you can reconnect manually by pressing the small
clear key again for 5 seconds.
To manually end your connection you should press the small clear key for 5
seconds to disconnect your OPN2002.

7
Limited Universal menu book support
In contrary to other Opticon programmable terminals, the OPN2002 also supports
the reading of various configuration options that can be found in the Universal menu
book. This makes it possible to customize this application without having to actually
change the source code of this software.
The OPN2002 support (most of the) menu options listed in the following chapters:
1. Defaults (See chapter 'Supported defaults' at the start of this set-up guide)
2.3. Bluetooth options (See 'Supported Bluetooth features' below)
3.1 Enabling/disabling readable codes
3.2 Setting of fixed, minimum and maximum lengths
3.3 Code specific options (almost all options are supported except some 2D
decoder options)
4.1 Case conversion
4.2 Set prefixes
4.3 Set suffixes
5.1 Add-on wait modes
5.1.1 Multiple read reset time
5.1.2 Quite zone options (margins)
5.4 Redundancy
5.5 Positive and negative barcodes
7.1 Diagnostics
Supported Bluetooth features
In the Opticon Universal menu book there are additional Bluetooth features listed for
Opticon barcode readers with Bluetooth support. Some of these features are also
available on this demo application.
The following of these listed features are supported:
Chapter 2.3.1: Bluetooth connection labels
+-CONN-+ (Manually connect label)
+-DISC-+ (Manually disconnect label)
+-DSCO-+ (Make discoverable / connectable)
Chapter 2.3.3: Configurable Trigger-to-connect time (default = 5 seconds)
Chapter 2.3.4: Configurable Trigger-to-disconnect time (default = 5 seconds)
Chapter 2.3.6: Auto reconnect options (default = 1 minute)
Version history
RFG35310 First release October 10
th
, 2009
RFG35311 Added features and bug fixes October 20
th
, 2009
Please check our web site at www.opticon.com to see if there are updates
available for the Operating System, this application and this manual.