Document Sample
Keyboard_Driver_Help Powered By Docstoc
					Beta Test Drivers – TS750 / TS800 / TS9xx
Please Note: These are pre-release test drivers.
The drivers allow access to the following devices:
I-Button (Dallas) Key
Magnetic Card Reader Module (MCR)
Once the drivers have been installed, the devices will emulate keyboard wedge devices, i.e. when
a magnetic card is swiped or an i-button key is applied, the output will be sent to the system via
the keyboard buffer.
Programmable prefixes and suffixes are allowed; please consult the relevant section later in this

These drivers will only work on the Bleep TS range of touch screen terminals.
They are designed to work on the TS-750, TS-800 or TS-915 models but will also work on the
TS-700 terminal should the required port parameters be changed.

The Operating System needs to be Windows XP, POSReady or Windows 7.
If using XP, a minimum of Service Pack 2 needs to be installed.

These drivers make use of the Microsoft Dot Net Framework which can be downloaded from here
free of charge:

A minimum of version 2.0 is required. These files must be installed prior to installing the drivers.

Due to the beta nature of these drivers, the install procedure is currently manual.

Step 1.

Copy the supplied files into a folder on your computers hard drive. (For ease it is suggested that
you use C:\Drivers)
Run [double click] the dotnetfx.exe Dot Net Framework Installer file and follow the onscreen
instructions if you have not already done so.

Step 2.

The software is supplied in 2 modules, the OPOS Helper Service (Service.exe) and the Control
Panel program. (Control Panel.exe)
It is required to install the OPOS Helper Service first which is achieved as follows;

Click Start | Run
In the Run Dialogue box, type in CMD and press Enter. This will load the command prompt.

From here you need to navigate to the drivers folder (e.g. CD\DRIVERS [Enter])

Once you are in the correct folder you can run the install by typing:

Should you encounter any errors at this point, it would be worth checking that you have Service
Pack 2 or higher installed and that the .NET Framework is installed properly.
Successful installation will not report any errors or messages.

To check that the installation was successful, you may open the Control Panel (Start | Control
Panel) choose Administrative Tools, followed by Services.
In the list of services, you should see the entry OPOS Helper.

{Note: should you be required to update the OPOS Helper at any time (which is the
Service.exe program file) you will need to stop the service first before you can update the
.exe file. This is done by clicking OPOS Helper and clicking Stop the service.
Once the new file has been copied on, you may then Start the service.}

Step 3.

Installing the Control Panel Program.

In the same manner as step 2, you may install the control panel program as follows;

Assuming that you are still in the correct folder in the command prompt, type:


Successful installation will not report any errors or messages.

Once this is done, you may close the command prompt window.

Step 4.

Editing the Control Panel.

Using windows explorer, navigate to the drivers folder and double click the Control Panel.exe

To ensure proper usage, please make sure that the serial port parameters are as follows;

TS-9xx: COM4: 9600,8,None,One
TS-750 / TS-800: COM6,9600,8,None,One
TS-700: COM3,9600,8,None,One

Please ensure that ‘Input goes to Keyboard’ is selected (ticked).

From here you may define your prefix and suffix (if any) for the devices.

The prefix (or START) characters will precede any i-button or mcr read and the suffix (or END)
will be appended to the end of an i-button or mcr read.

In the case of the i-button, if your software supports it, you may enter characters to be sent when
the key is removed.

Allowed Start and End (or Removed) Characters:

[cr] = Enter
[esc] = Escape
[F1]…[F24] = F Function keys
[space] = space key
[[] = literal ‘[‘ character
[@nnn] = virtual key code nnn
Any other characters are literal and will appear as they are typed.

Specifying no Start or End characters will simply send the relevant data without a start or end
Specifying no ‘Removed’ character will disable the ability to detect when the i-button is removed.


It may be that your software has key listeners which react to certain key presses for actions such
as i-button sign-on or mcr swipe.

For example, the function key ‘F1’ may be used to signify that an i-button has been connected, in
which case you would put [f1] into the Start field for the i-button.
This would cause the driver to ‘press’ the F1 key when an i-button key is applied, followed by
sending the i-button data.
As all i-button data is the same length, it is likely that you will not need to specify an End
character; however, if instructed to do so, you may also specify an End character which will then
be sent following the i-button data.

Specifying a Removed character for the i-button will cause the drivers to send this character(s)
when the key is removed, for example, you may specify that the function key F2 is pressed when
an i-button is removed – therefore you would enter [f2] into the Removed field.

The same theory applies to the Magnetic Card Reader (MCR) and can be programmed to specify
Start and End characters for both Track1 and Track 2 data.
For the MCR there is no Removed character as this does not apply.

Testing the Devices

The devices may be tested in virtually any app which allows for keyboard entry.
A good example of this would be Notepad.

Take care however that the app you choose does not have its own functions mapped out which
are the same as your assigned Start and End or Removed characters.
For example, you may have programmed F1 as the Start character for the i-button read; testing
this in Notepad will cause Notepad to assume that you have pressed F1 which will cause the help
menu to appear and in this case, because there is nowhere for the i-button data to go, it will be

To avoid this it is recommended that you either remove all Start and End characters or replace
them with simple text markers if you are testing in an app such as Notepad.

Assuming that your Start and End characters are valid, open Notepad and perform a driver
function to view the data; i.e. Swipe a card or apply an i-button.

You should now see the data from the device.

Particular care should be employed whilst testing the system with a valid monetary card such as
a VISA card for reasons of security.
Should you have any queries about how to use the drivers with your chosen app, you should
consult your application provider for information about how they wish the i-button or MCR data to
be handled.

As this is a beta-test driver, any issues or comments should be addressed to Bleep (UK) PLC on
the following email address:

[End of document]

Shared By: