HEADER Section
Header has general information about Application Project.
There are max 11 parameters in a header:
1.
Name
- Application Project name, it's used only for a user for project
identification, it takes 12 characters max.
2.
Date
– Project creation date, this parameter is also used for a user, it takes
12 characters max.
3.
Time
- Project creation time, used for a user, it takes 10 characters max.
4.
Date Format
– defines way of interpreting the Date type column and way
of displaying Date on LCD. It is important to define the same type of date in
User input database or User output database. Example:
dd/mm/yyyy
5.
Time Format
– this parameter is analogical to “Date format”,
example :
hh:mm:ss
.
6.
Database Columns Separator
– defines character for separating columns
in User input database. If you don't include User input database to
Application Project “Database Separator” will be used in User output
database received from HHR. It can be comma, semicolon, tabulator(\t),
space(\s),...
7.
LOG
– defines whereas Log Table is used or not in the Application;
LOG_true indicates that Log Table will be used in application and
LOG_false that Log Table won't be used.
The size of characters in this parameter has got meaning.
8.
Decimal Point
– defines the decimal point used to separate integer part
from fractional part in User input database, it is used also during receiving
User output database.
9.
Bluetooth
– this parameters defines if Bluetooth in application program is
used or not. If enabled (BT_true) then HHR after every transponder read,
sends information through Bluetooth protocol to master device with
transponder number, date and time of reading.
Before reading (and sending) the Bluetooth connection must be made.
Other option of using Bluetooth is sending information from HHR 3000
PRO to master device at user's command, to use this property user have
to disable(BT_false) Bluetooth in HEADER section. Bluetooth essentials
are explained in Appendix D.
BT_true – Bluetooth enabled;
BT_false – Bluetooth disabled.
10.
Global
– this parameter defines whereas globals will be loaded from file or
it will be included in Application Program.
If you choose to load Globals from file you have to place a “
global in.txt
”
file in the same catalog with Application Program.
During receiving database globals will be automatically loaded from a HHR
to “global out.txt” this file will be placed in the same catalog with User
Output Database.
GL_file
indicates that globals will be loaded from a text file, and
D01B2.4 HHR 3000 PRO Manual
17/75
Содержание HHR 3000 PRO
Страница 15: ...D01B2 4 HHR 3000 PRO Manual 15 75...
Страница 67: ...D01B2 4 HHR 3000 PRO Manual 67 75...