No warranty of any kind is made in regard to this material,
including, but not limited to, implied warranties of merchantability
or fitness for a particular purpose. Although every ef fort is made to
assure accuracy and completeness, we can not be held liable for
any errors contained herein nor incidental or consequential
damages in connection with furnishing, performance or use of this
material.
We shall be under no liability in respect of any defect arising from
fair wear and tear, willful damage, negligence, abnormal working
conditions, failure to follow the instructions and warnings, or
misuse or alteration or repair of the products without written
approval.
No part of this document may be reproduced, transmitted, stored
in a retrieval system, transcribed, or translated into any language
or computer language in any form or by any means electronic,
mechanical, magnetic, optical, chemical, manual or otherwise,
without express written consent and authorization.
We reserve the right to make changes in product design without
reservation and without notification. The material in this guide is
for information only and is subject to change without notice.
All trademarks mentioned herein, registered or otherwise, are the
properties of their various respective owners.
ii
Table of Content
General Information...................................................................1
User Reset ............................................................................... 30
iii
General Information
1.1. Introduction
Congratulations on your purchase of the Bluetooth Personal Data
Collector (PDC) with LCD display. Along with superior portability
and visually safe scanning Engine of, the PDC features a
real-time clock, a buzzer, a dual-color status LED, also an UART
port with optional Bluetooth or various communication cable for
connection to external equipment.
The on-board 64K EEPROM provides a robust, stable memory
space dedicated to storing scanned data. The PDC can retain
more than 2000 records construct by an UPC code with
timestamp.
The Personal Data Collector comes with a built-in basic data
collection firmware, called FREETASK that can scan and store
barcodes, and do simple edits on the stored data. Data can be
uploaded to a PC through the Bluetooth or RS-232 / USB cable.
WinTaskGen, a software program on the ZEBEX website, can be
used to create customized programs (Tasks) for download and
use with the PDC. A Task can have up to four operation
procedures to manage four data forms each with 16 separate data
fields.
For more advanced requirements, there are available libraries for
developing programs under the GCC environment. Contact your
agent if you are interested in this approach.
1
1.2. Unpacking
The PDC package should contain:
- 1 ea. Pocket-Sized Personal Data Collector
- 1 ea. DB-9(F) serial communication cable
( For data upload and download)
- 3 ea. AAA NiMH rechargeable batteries
- 1 ea Power Adapter
If any package contents are damaged or missing, please contact
your dealer immediately.
Optional Accessory
- Bluetooth USB Dongle
- USB-232 or USB-HID cable
( To transfer data from PDC to a PC)
2
1.3. Device Outline
LED
Down
LCD
Up Key
Function
Scan
UART port
Figure 1: Pocket-Sized P
ersonal Data Collector
3
1.4. Battery Care
In the interests of providing the best product performance possible,
the Personal Data Collector comes with high quality, rechargeable
Nickel Metal Hydride (NiMH) batteries and a Power Adapter. After
NiMH batteries are installed, connect the Power Adapter cable
and the batteries charge right in the unit.
Before you use new Personal Data Collector and new NiMH
batteries for the first time you should charge them fully at
least 6 hours. Please note that new NiMH batteries need to go
through three to five charge-dis-charge cycles before they reach
peak performance and capacity. For the first few times that you
use new NiMH batteries, you may find that they discharge fairly
quickly during use. This is normal until the batteries mature.
It is highly recommended that NiMH batteries always be operated
until fully discharged before recharging. If you recharge NiMH
batteries before they are fully discharged, they may develop a
pattern of inhibited output.
Under favorable conditions, NiMH batteries can last through
hundreds of recharges. You will get better performance if you
keep battery teams together. Don’t mix new and old batteries.
Note:
1. If the PDC will remain unused for an extended period (two
months or more) the batteries should be removed. Even when the
PDC is turned off, there is a very small amount of power
consumed, which can, over time, have a bad effect on batteries.
2. At the first time using Personal Data Collector after NiMH
4
batteries already loaded, please press and hold both v and ^ keys
for 30 sec. to turn on the PDC
The PDC supports to connect with a Bluetooth® radio device via
Serial Protocol Profile (SPP). It works like virtual serial cable once
connection pair between two devices is established.
Please make sure the Bluetooth® function is finely equipped on
the host device, as well as an application program is installed. If
an optional Bluetooth USB dongle is purchased, please refer to a
separate product manual on website for IVT software instruction.
For further enquiries, please contact your dealer.
1.5.1. Connection Mode:
Before establish a Bluetooth® connection between two devices, it
is necessary to define which device to be the “Master” during the
communication. The “Master” device holds the initiative to
connect or disconnect the “Slave” device. The “Slave” device
waits for the command from “Master” when it’s power on.
1.5.2. Bluetooth Device Address:
Each Bluetooth® device has a unique hex number with 12 digits
to identify itself during communication, as so called Bluetooth
Device (BD) address. It is essential to set up a target BD address
before making a pairing of SPP connection.
1.5.3. Personal Identify Number code:
A Personal Identify Number (PIN) code is used as a validation
password.
1.5.4. Pairing PDC as SPP Master:
When a pairing process is initiated by PDC, PDC is known as SPP
6
Master. PDC has to know the BD address of a target device as
well as sets a PIN code. PDC will send out the paring request to
the target device. The target device has to reply by the correct PIN
code set by PDC in order to establish a successful pairing
connection.
The PDC will show a successful pairing status after receiving
positive response from the target device, or a failed connection
with negative response. Otherwise, a timeout status will be shown
as if PDC has been waiting too long.
1.5.5. Pairing PDC as SPP Slave:
When PDC is powered on and Bluetooth® is activated, PDC is
ready for pairing process as a SPP Slave device. A PIN code has
to be set in PDC. At pairing process, the host device shall enter
the right PIN code to make a successful pairing.
1.5.6. Connect/disconnect with target devices:
The Master device decides to connect/disconnect with target
devices.
1.5.7. Reliable RF communication:
During transmission, each data is featured with protocol coding.
Transmission response would be made once data is received,
ACK or NAK. ACK indicates “acknowledged”, data is received and
decoded. NAK is meant “non-acknowledged” data is received but
cannot be recognized. Also use a STX/ETX packed and/or data
checksum is helped for verify if data is valid at receive host.
Data Format of packet
To send a data (record) to the remote application, the data is
7
encapsulated as below format if the item is set to enable:
STX SEQ Data TerminatorCKS ETX
1 Byte1 Byte Varies 1 or 2 Byte1 Byte 1 Byte
Title Definition
STX Start of packed data 02H
SEQ Sequential number of packed,
Use 020H to 07FH
DATA Record data
Terminator Data terminator
CKS Checksum, Use 020H to 07FH
ETX End of packed data 03H
1.5.8. Packed Example:
If record data is "ABCD" with STX/ETX, SEQ and CKS enable,
assume SEQ is ‘0’ (030H) the send out data is format as:
02H + 030H + "ABCD "+ 03AH + 03H
Checksum is calculated by add all data byte in the packed except
STX and ETX. If the result is over 07FH (ASCII extend) subtract
result by 080H, if the result is less than 020H (ASCII control code)
add result by 020H. This will let the checksum keep in ASCII
visible character.