Feature of System
Development Concept
Hardware
Software
Basic Specifications
Model Name 8
System Configuration
Hardware Block Diagram
Supported Software
Precautions
Basic Software
2.1
2.1.1
2.1.2
2.1.3
2.2
2.2.1
2.2.2
2.2.3
2.2.4
2.2.5
2.2.6
2.3
2.3.1
2.3.2
2.3.3
2.3.4
2.3.5
2.3.6
2.3.7
2.3.8
2.3.9
2.3.10
2.3.11
2.3.12
Overview
Software Configuration
Memory Map
Drive Configuration
Basic System Operation
Overview
Power ON Process
Power OFF Process
Battery Voltage Monitoring Process
Low Consumption Current Process
How to Replace or Recharge Batteries
Supported Devices 39
Display Unit 39
EL Backlight
Touch Panel
Disk
Serial Communication
PC Card
Clock Timer 49
Buzzer 50
Barcode Reader
Infrared Communication (Ir)
Keys
Sensors
System Menu
3.1
3.2
3.3
3.4
3.5
3.6
3.7
3.8
3.9
3.10 YMODEM Utility 64
Overview
Basic Operation
List of Functions
Key Click Sound Setup
Buzzer Volume Setup
Contrast Adjustment 59
Auto Backlight Setup
Auto Power OFF Setup
Touch Panel Calibration
5
6
6
6
6
6
7
9
9
10
12
15
15
15
16
17
19
19
21
25
28
33
37
41
42
43
45
47
51
52
53
54
55
55
56
56
57
58
60
61
62
2
3.11 FLINK Command 68
3.12 System Date/Time Setup 71
3.13 Command Prompt 72
3.14 RAM Disk Size Change 73
3.15 Disk Format 75
3.16 System Initialization 77
3.17 Password Entry 78
Chapter4 MS-DOS 79
4.1 Overview 79
4.2 How to Write CONFIG.SYS and AUTOEXEC.BAT 81
4.3 Card Boot 84
Chapter5 Keyboard Controller 87
5.1 Overview 87
5.2 Keyboard Control 88
5.3 Touch Panel Control 90
5.4 Sensor Control 91
5.5 Backlight Control 92
Chapter6 Drivers 95
6.1 Overview 95
6.2 System Driver 96
6.2.1 Function 96
6.2.2 Startup Method 96
6.3 Clock Control Driver 97
6.3.1 Function 97
6.3.2 Startup Method 98
6.4 Keypad Driver/Hardware Window Manager 99
6.4.1 Function 99
6.4.2 Startup Method 100
6.5 PenMouse Driver 101
6.5.1 Overview 101
Startup Method 102
Functions 102
Application Development 110
Overview 110
Notes on Developing Application 111
Development Environment 112
Development Environment 112
Application Development Library 112
Simulation Driver 113
Program Development Procedure 114
Creation of Execution File 115
Debugging Through Simulation 117
Operation Check on IT-2000 (Using COM2KEY/XY) 119
Installation of Application Program 120
Simulation Driver 122
System Driver Simulator (SYSDRVP.COM) 123
8.9 COM2Key Utility 217
APPENDIXA TFORMAT.EXE 218
APPENDIXB PC Card Driver 219
APPENDIXC Acquisition of Suspend/Resume Event and
Power Status
222
4
Preface
The IT-2000 Technical Reference Manual (hereinafter referred to as this document) is provided to
assist the user in developing programs to run on the Casio IT-2000 (hereinafter referred to as this
terminal or IT-2000 or HT in this manual). Microsoft C/C++ Ver.7.0 or later, and the manuals
supplied with it, is required to develop programs for this terminal.
Read Chapter 1 of this manual in its entirety to understand the features of this terminal.
Important notices to user
The information contained in this document may be modified without a prior notice.
Casio Computer Co., Ltd. shall not be liable for any outcome that result from the use of this
document and the terminal.
Copyright notice
The contents of this document are protected by the Copyright Law of Japan.
This document may not be reproduced or transferred in part or in whole, in any form without
permission from Casio Computer Co., Ltd.
The MS-DOS copyright is the proprietary of Microsoft and is protected by the United States
Copyright Law and International Treaty provisions.
The MS-DOS software shall not be modified, reverse-engineered, decompiled, or disassembled. Any
form of reproduction is also absolutely prohibited.
About trademarks
AT and IBM PC/AT are registered trademarks of International Business Machines
Corporation in the United States.
MS, MS-DOS, Microsoft C/C++, Visual C ++, Visual Basic, and MS-Windows are registered
trademarks of Microsoft Corporation in the United States.
5
1. Overview
1.1 Features of System
1.1.1 Development Concept
The IT-2000 is a data collection terminal for business use. After years of refinement Casio
Computer Co., Ltd. has developed its hand-held type terminals so that they yield high speed and
a high functionality in comparison to general personal computers. This allows improved efficiency
in software development.
It has adopted the IBM PC/AT architecture and incorporated an IBM PC/AT compatible BIOS. It
uses MS-DOS Ver. 6.22 for its OS. This has drastically improved the software development
environment and compatibility to IBM PC/AT family applications.
The adoption of a power-saving type 32-bit CPU, the Intel 80486GX, allows the terminal to operate
continuously for eight hours (when the backlight is off).
1.1.2 Hardware
Global IBM PC/AT architecture standard is adopted.
Compact design: 85 (W) x 196 (L) x 30 (H) mm, 430 g (approx.)
Uses a 32-bit CPU (Intel 80486 GX) for 25 MHz high-speed operation.
High-resolution (192 x 384 pixels), large-size liquid crystal touch panel.
Supports various interfaces, including RS-232C (8-pin, 14-pin), IR, and PC card.
High environmental adaptability: Operation temperature at between -5 and 50, water splash
proof capability conforms to the IPXII standard, etc.
Uses a small-size, large capacity lithium-ion battery pack as the main battery.
Incorporates a large capacity flash ROM drive as the user drive.
1.1.3 Software
MS-DOS Ver. 6.22 as the operating system.
IBM PC/AT-compatible BIOS makes it easy to develop user application programs.
Uses APM 1.1, for advanced low-power consumption capability.
6
PC card slot conforms to PCMCIA Release 2.1 supporting various PC cards.
Implements IrDA 1.1 protocol for high-speed infrared communication.
System menu makes it easy to maintain the IT-2000 and install user application programs.
Provides various development support tools including C-language libraries and communication
utilities for developing business application programs.
1.1.4 Basic Specifications
IT-2000
Architecture
IBM PC/AT architecture
External dimensions and weight
Dimensions: 85 (W) x 196 (L) x 30 (H) mm
Weight: 430 g (approx.)
CPU
Intel 80486GX(32-bit)
Memory
DRAM: 4 MB
F-ROM: 0/4/8/12/16/24 MB (depending on the model)
MASK ROM: 8 MB, Windows file (IT-2000W only)
BIOS ROM: 1 MB (BIOS section: 256 KB, Drive C image: 768 KB)
Display and input
LCD panel: 192 x 384 dots (FSTN semi-transparent LCD),
The software used with this terminal can be divided into two categories: the system software that
includes the BIOS, OS, and device drivers and the user software such as the development tools.
The system software is stored on the DINOR FLASH ROM (1 MB), and the user software is
supported from the SDK CD-ROM (version 4.0) supplied by Casio at free of charge. The following
paragraphs describe the software.
BIOS
The BIOS program is stored in the DINOR FLASH ROM. 256 KB of DINOR FLASH ROM is
allocated specifically as the BIOS storage area.
The BIOS of this terminal consists of the standard PC/AT BIOS section, PEN BIOS for supporting
the touch panel, extension BIOS for supporting devices inherent to this terminal, and APM BIOS for
attain the low-power consumption capability.
MS-DOS Main Part
The main part of the MS-DOS Ver. 6.22 is stored in drive (C:).
In drive (C:) 768 KB of memory area in the DINOR FLASH ROM (1 MB) is allocated. Because of
the capacity limitation, only the essential MS-DOS files are stored in drive (C:). Therefore, if using
an MS-DOS file that is not included in the main part, copy it from the Backup CD-ROM (title on
CD-ROM: MS-DOS version 6.22 Software) to the F-ROM drive (D:) or RAM disk (A:).
For information about each MS-DOS file refer to an MS-DOS manual, commonly available at book
stores.
Device Drivers and System Files
These files must be loaded via CONFIG.SYS or AUTOEXEC.BAT at boot-up. These files are all
stored in drive (C:).
If reading the internal clock with INT21h the significant data should include and be limited to
the seconds digits. On this terminal the time is read directly from the RTC so that the correct
time can be attained at any moment, even during extended continuous use. As a result the 1/100
of a second digit is ignored. (refer to Chapter 6.3 “Clock Control Driver”)
If it is necessary to reboot the system from an application, use the dedicated system library.
However, the reboot operation that uses INT19h of the BIOS I/F does not work.
Many commercial PC programs use a VGA screen (80 (H) x 25 (V)). If these programs are run
on this terminal (24 (H) x 24 (V)) part of the message may not be displayed on the screen.
Writing to a PC card should always be performed by terminating the write action through the
flash-out process. Otherwise, if system operation is suspended while writing to an SRAM card
or ATA card, the data on the card may be damaged.
To activate this flash-out process use the “_dos_commit()” function of Visual C/C++ or
Commit Function(68h) of DOS.
Layout your screen display in such a manner that dark characters lie on a white background.
With LCDs a white background provides the most legible displays. If intermediate colors (half
tones) are desired, use the following two colors (tones).
Note:
Due to technical reasons the display of the B/W LCD may change to reverse video if an
application program developed by the user on a PC is executed without modification on this
terminal. To restore the normal display use the Reverse Video Utility (refer to Chapter 8.8
“Reverse Video Utility”).
Key input operation is disabled for about one second after the Power has been turned on.
This is not a malfunction. This occurs because the monitoring timer starts operating the
moment the Power switch is turned on and does not allow key input for about one second
until this timer expires. Thus, key input is not possible.
If an LB1 event (low main battery voltage) occurs, the alarm buzzer starts sounding and system
operation is suspended in about 10 minutes. If the alarm buzzer starts sounding, terminate the
current operation as soon as possible and recharge the main battery.
12
This system will not execute an alarm indication for an LB2 event (low sub-battery voltage) or
LB3 event (low SRAM card battery voltage). Therefore, the application program side must
acquire the alarm status via the system library and display an appropriate alarm message.
If the volume of the buzzer is set to zero by the System Menu or system library, the LB1 (low
main battery voltage) alarm will not be heard. Also, other sounds issued by the system will be
inaudible.
If the system is booted from a PC card and if a large-size program that resides on the card is
called from AUTOEXEC.BAT file, an error may result. To avoid this problem refer to Chapter
4.2 “How to Write CONFIG.SYS and AUTOEXEC.BAT".
The time limits that can be set for the Auto Power OFF (APO) function are 0 minute, 1 minute
and 30 seconds, 2 minutes and 30 seconds, up to a maximum of 15 minutes and 30 seconds.
This timer has an error of +/-23 seconds.
Do not open the battery compartment lid while the power is on. If it is opened accidentally, an
emergency alarm sounds. In case such the event occurs, close the lid at once.
When you change the main battery, be sure to switch off the power before opening the lid.
An SRAM card formatted with the DT-9000 (a Casio handy terminal) cannot be used or
formatted with the IT-2000.
If the battery pack is installed for the first time after purchase, or if it is installed after the main
unit has not been used for a long period of time, install the battery and wait approximately eight
seconds before turning the power on. This must be done because it takes approximately eight
seconds until sufficient power can be raised for the emergency process. And, during this
interval the power cannot be turned on even if the Power switch is turned on.
If the power is turned on for the first time after purchase and there is no installed application,
the System Menu will always appear. Before using applications call this System menu to install
them. (refer to Chapter 7.4.3 “Operation Check on IT-2000 (Using COM2KEY/XT)”)
The backlight is turned off by means of the ABO (Auto Backlight OFF) function. However, it
is turned off 1.3 seconds after the setup time. This is because the system has 1.3 seconds of
monitoring time before the internal timer is started.
13
Do not input “^P” from the DOS prompt. If it is input, “^P” requests DOS to redirect console
output to printer. However, the IT-2000 does not have the printer being installed, it will enter
into wait mode.
For more information about the system library refer to Chapter 7.6.2 “System Library”.
Also, refer to Chapter 2.2.4 “Battery Voltage Monitoring Process” for information about the
low-battery voltage notification function.
14
2. Basic Software
2.1 Overview
2.1.1 Software Configuration
The following diagram shows the software configuration of the IT-2000.
Driver
Keypad LibrarySystem Library
Int33h
Keypad
Driver
Pen BIOSExtended BIOSAPM BIOS
Application
Layer
MS-DOS
Layer
Hardware & BIOS
Layer
OBR Library
System Driver
PenMouse
AT Architecture + Original Hardware
Fig. 2.1
Note: The PenMouse driver and Keypad driver cannot co-exist on the system.
The drive configuration differs for each model as described in the following:
If F-ROM drive is supported
Drive A:
[Read and Write]
[Read Only]
[Read and Write]
[Read Only]
[Read Only]
[Read and Write]
RAM disk
This drive is prepared for use after the RAM disk size is specified from
the System Menu. The contents of this RAM disk will not be erased
through a boot process or by pressing the RESET switch.
Basic drive (DINOR FLASH ROM)Drive C:
This drive starts up MS-DOS. The main body of MS-DOS and
maintenance programs such as the System Menu, etc., are stored in this
drive.
F-ROM driveDrive D:
Application programs are stored on this drive. The drive size (storage
capacity) differs depending on the model.
Drive for Windows files (IT-2000W only)Drive E:
A ROM that stores Windows files is assigned to the drive E: on
Windows models.
This is a reserved drive on DOS models. In this case note that if this
drive is accessed , an INT24h error will occur.
Drive for booting a cardDrive F:
This read-only drive functions only while a card is being booted.
For information about the mechanism of booting a card refer to
Chapter 4.3 “Card Boot”.
PC card driveDrive G:
This drive is required if the application program accesses the PC card.
This drive is prepared for use by loading the PC card driver via
CONFIG.SYS.
Note:
The drive letter of each drive is reserved. Therefore, these drive letters are not changed even if the
RAM disk is not used.
The drive configuration described in "If F-ROM drive is not supported" on page 18 will be used
only if the drive D: is unformatted or is not recognized by the system for some reason.
However, this will rarely occur because the drive D: has been formatted at the factory.
17
If F-ROM drive is not supported
Drive A:
[Read and Write]
RAM disk
This drive is readied for use after the RAM disk size is specified from
the System Menu. The contents of this RAM disk will not be erased
through a boot process or by pressing the RESET switch.
Basic drive (DINOR FLASH ROM)Drive C:
[Read Only]
This drive is used to start MS-DOS. In this drive not only the main body
of MS-DOS but also the maintenance programs such as the System
Menu, etc., are stored. This is a read-only drive.
Reserved driveDrive D:
[---]
This is a reserved drive.
If this drive is accessed, an INT21h error will result.
Drive for booting a cardDrive E:
[Read Only]
This is a read-only drive that functions only while a card is booted.
For information about the mechanism of booting a card refer to
Chapter 4.3 "Card Boot”.
PC card driveDrive F:
[Read and Write]
This drive is required if the application program accesses the PC card.
This drive is prepared for use by loading the PC card driver via
CONFIG.SYS.
18
2.2 Basic System Operation
2.2.1 Overview
Basic operation of this system on the terminal consists of the suspend/resume process and boot
process operated by means of the Power switch and RESET switch, as shown in the following
diagram.
OFF STATE
OFF Process
OFF EVENT
System Menu
Fig. 2.3
During normal operation the system status will move between the ON state and the OFF state,
shown in the above diagram, by pressing the power key.
ON KEY
Application BOOT
RESET SWITCH
System Menu BOOT
RESET SWITCH
System Menu BOOT
ON KEY
System Menu BOOT
ON EVENT
ON Process
INITIAL STATE
ON STATE
OFF Process
OFF EVENT
SUSPEND
STATE
The SUSPEND state is a state from which the previous state can be returned to at any time. The
process of returning from the SUSPEND state to the ON state is called the resume process.
The RESET switch is used to either re-start the system or to initiate the System Menu, which is the
maintenance program. Press this RESET switch to start hardware initialization followed by initiation
of the System Menu. This process is called the System Menu boot process.
If an OFF event occurs while the System Menu is operating, the system shifts to the OFF state.
If the ON key is pressed in the OFF state, the boot process is executed again and an appropriate
application program will be loaded. This process is called the application boot process.
19
The following table summarizes the power-on processes provided for this terminal.
System Menu boot
process
Application boot processSearches for CONFIG.SYS and AUTOEXEC.BAT prepared
Resume processRestores the memory conditions that existed before the power
Always executes CONFIG.SYS and AUTOEXEC.BAT located
in drive (C:) for starting up the MS-DOS.
by the user and starts up MS-DOS from the drive where they are
located.
was turned off and continues operating according to the
conditions.
20
2.2.2 Power ON Process
Overview
The ON process is provided to make the system ready for use (ON state). The actual process varies
depending on the settings at that point in time and the last OFF factor (the cause of the OFF action).
ON factors:
Pressing the Power switch
Pressing the RESET switch
Power ON alarm
Reception of RING signal
Mounting on the I/O Box
OFF factors:
Pressing the Power switch
Pressing the RESET switch
Auto Power OFF (APO)
Power OFF by software
Auto Power OFF due to lower battery voltage
Emergency Power OFF due to lower battery voltage
Note:
For more information power OFF factors refer to Chapter 2.2.3 "Power OFF Process".
This ON process is divided into two processes: the "Resume process" for continuing the previous
process and the "Boot process" for re-loading MS-DOS. The Boot process can be further broken into
the "Application boot" and the "System Menu boot" processes.
Fig. 2.4
Boot Process
ON Process
Resume Process
Application Boot Process
System Menu Boot Process
Application Boot Process
Searches CONFIG.SYS and AUTOEXEC.BAT files according to the priority given to each drive
and, if these files are found, sets the drive where these files are located as the current drive.
(refer to ”Application Boot Process” on the next page).
21
System Menu Boot Process
Pressing the RESET switch sets the drive C: as the current drive, and MS-DOS is loaded from
that drive. As a result, the System Menu that includes the maintenance program will be initiated
(refer to “System Menu Boot Process” on this page).
Resume Process
This process restores the conditions that existed before the power was most recently turned off.
Any application program that was running at that point in time can be continued.
The contents of the above listed processes will be described in the following sections.
Application Boot Process
The application boot process is used to initiate application programs that have been installed in the
system by the user. The main system will search for CONFIG.SYS and AUTOEXEC.BAT files
according to the priority given below.
The system assigns the first drive on which the files are found as the current drive, and boots MSDOS from the drive C. Consequently, if the CONFIG.SYS and AUTOEXEC.BAT files created by
the user are located on one drive, MS-DOS will be booted from the drive assigned as the current
drive. Under factory defaults it is apparent that the CONFIG.SYS and AUTOEXEC.BAT files
created by the user cannot be found. If this occurs, therefore, the CONFIG.SYS and
AUTOEXEC.BAT files located in the drive C: are selected and the System Menu will be initiated.
Priority of the drives:
If the F-ROM drive is provided
[Card drive (F:)] -> [RAM drive (A:)] -> [F-ROM drive (D:)] -> [Basic drive (C:)]
If the F-ROM drive is not provided
[Card drive (E:)] -> [RAM drive (A:)] -> [Basic drive (C:)]
Note:
The RAM disk (A:) is valid for use only if setup is made through the System Menu.
System Menu Boot Process
The System Menu boot process is used to initiate the System Menu, which is nothing but a
maintenance program for this terminal system. The System Menu boot process will be executed only
if the RESET switch at the rear of the main unit is pressed.
If, in addition, a power OFF factor is encountered during the execution of the System Menu, the next
boot process will be the Application boot process.
22
Note:
The RESET switch can be used not only for initiating the System Menu but also as the forced
restart witch when the user application program under development hangs. However, note that if
the RESET switch is pressed while the disk is being written to, the data may be corrupted.
Therefore, the RESET switch should be pressed only while the power is off.
Clock data or information on the RAM disk will not be lost if the RESET switch is pressed.
Resume Process
When the power is turned on the resume function resumes system operation under the conditions
that existed the last time the power was tuned off. Application programs are continued as soon as the
power is resumed.
Setup of Resume Process ON/OFF
The default settings have been made so that every OFF factor encountered during the operation of an
application program is the objective of the resume process. However, these default settings can be
modified so that the system reacts differently to OFF factors by means of the system library. For
example, according to the default settings, pressing the Power switch will suspend and resume the
execution of an application program. However, it is also possible to simply reboot the system with
the Power switch without activating the resume function if such a setup is made. However, note that
this setup is not permanent. The resume process is replaced by the boot process once only right after
the system library is called.
ON Factors
Various ON factors used to turn on the system are explained below.
Pressing the Power switch
If the Power switch is pressed while the system is off, the system power can be tuned on. When
the power is turned on the system operation sequence proceeds as described in "Relationship
between OFF Factors and ON Processes" on page 24.
Pressing the RESET switch
Press the RESET switch to turn on the system power. In this case the System Menu will always
be initiated.
This terminal has the Auto Power ON function which automatically starts the system. This Auto
Power ON function can operate in one of the following three ways:
23
Auto Power ON function (only affects the resume process) activated by alarm
The system power can be turned on (resumed) at the specified time by means of an alarm.
However, this will not function if the next start-up method is set to the boot process in the system
library.
Auto Power ON function activated by the RING signal
This function can be used if a modem is connected to the 14-pin expansion interface. In this case
the system power can be turned on by the detection of the RING signal from the modem.
Remember that Power ON by means of the RING signal is prohibited by default. Execute this
function using the system library to enable the Power ON function to be activated by the RING
signal. System operation after the power is turned on follows the sequence described in "
Relationship between OFF Factors and ON Processes" on this page.
Auto Power ON activated by mounting on the I/O Box
The system power can be automatically turned on as soon as this terminal is mounted on the I/O
Box. However, this function is effective only if power is supplied to the I/O Box. This function is
enabled by default, however, it can be disabled using the system library. System operation after
the power is turned on proceeds according to the sequence described in "Relationship between
OFF Factors and ON Processes".
Relationship between OFF Factors and ON Processes
As described in the above overviews, the ON process (the Boot process or Resume process) will run
differently depending on the last OFF factor (what caused the OFF) and the conditions that existed
when the power was turned OFF. The following table shows the relationship between the OFF
factors and the ON processes that take place the next time the power is turned on.
OFF factor If an application is running If the System Menu is on
Power switch
Auto Power OFF
Software OFF
Low battery voltage
(LB1)
Low battery voltage
(LB0)
RESET switch pressed System menu boot process System menu boot process
Note:
Depends on whether the resume function is enabled or disabled. With this setup the next boot
process can be designated as the Application boot process.
Resume process
or Application boot process
(see note below.)
Resume process
Application boot process
24
2.2.3 Power OFF Process
Overview
Turns off the system power. However, the power to all the devices is not turned off and some can be
used for storing the information required for the next resume operation. This process is called the
suspend process and the state of the system while off is called the suspend state.
The suspend process can be divided into two categories: one is the normal suspend process which is
the usual off method and the other is the critical suspend process to execute the emergency escape
process for protecting the system from drops or bumps. Either of these suspend processes will be
selected depending on the OFF factor, as described later.
Normal Suspend Process
If the Power switch is held down for more than one second while system is on, the system power
will be turned off. The process that takes place at this time is the normal suspend process. Before
this suspend process is executed, the application currently running is informed of the suspend
request (OFF factor) by the system. Then the system stores the information required for resumption
and turns off the power.
Hereinafter the suspend process (or OFF process) refers to the normal suspend process.
For information about the method used by each application to detect the occurrence of an OFF factor
(suspend event), refer to Appendix C Acquisition of Suspend/Resume Event and Power Status.
Critical Suspend
This is a suspend process that takes place in an emergency. Since this critical suspend process should
achieve its escape process with very little power in the system, only essential information can be
retained.
The system will not inform the application currently running of the fact that it is critically
suspended. However, the application will be informed of the fact that it was critically suspended at
resumption.
For information about the method used by each application to receive this information, refer to
Appendix C Acquisition of Suspend/Resume Event and Power Status.
25
OFF Factors
The OFF factors refer to various causes that make the system enter the OFF state (suspend state), as
follows:
OFF factor Description Suspend
Power switch System operation can be suspended by holding down
the Power switch for more than a second. (see note)
Auto Power OFF
(APO)
Software Power OFF The system can be made to enter the suspend state by
Power OFF due to
time-out of low
battery voltage
(LB1) alarm
If main battery
voltage falls to an
inoperable level
(LB0)
Power OFF due to
RESET switch
pressed
System operation automatically shifts to the suspend
state if key or touch panel operation is not performed
for a specified period of time.
The duration until Auto Power OFF occurs can be set
and modified through the System Menu or system
library.
calling the system library from the application
program.
The system will issue an alarm (buzzer) if the
remaining battery voltage falls below the low main
battery voltage alarm level. If this occurs, recharge the
battery or replace it within ten minutes. If the battery is
not replaced or recharged the system automatically
shifts to the suspend state to protect the data.
If the terminal is used while the LB1 alarm, mentioned
above, is sounding, the main battery voltage may reach
the LB0 level. If this occurs the system will execute
the critical suspend process and forcibly turn off the
power. Therefore, if the LB1 alarm sounds, recharge
or replace the battery as soon as possible.
Press the RESET switch to forcibly turn off the system
power. If this is attempted to initiate the System Menu,
it is strongly recommended to complete the application
running at present then turn off the system power with
the Power switch before hand.
Normal
Normal
Normal
Normal
Critical
Restart
For more information about LB0 and LB1, refer to Chapter 2.2.4, "Battery Voltage Monitoring
Process".
For information about the system library refer to Chapter 7.6.2. “System Library”.
For information about the System Menu refer to Chapter 3 “System Menu”.
For information about the method used by each application to acquire a power ON/OFF event, refer
to Appendix C Acquisition of Suspend/Resume Event and Power Status.
26
Note:
Hold down the Power switch for more than one second until the power is off. This is done to
prevent the power from accidentally being turned off by the user. In addition, key input will not
be enabled for approximately one second after the Power switch has been pressed.
This occurs because the monitoring timer starts operating the moment the Power switch is
pressed and does not allow key input for about one second until this timer expires.
After this interval, key input becomes possible.
27
2.2.4 Battery Voltage Monitoring Process
This terminal uses a main battery (lithium-ion battery pack) for driving the main unit, and a primary
sub-battery (lithium battery) and a secondary sub-battery (lithium-vanadium battery) for backup.
Application programs can acquire the status of these batteries through the APM BIOS or system
library. Refer to Appendix C Acquisition of Suspend/Resume Event and Power Status.
Battery Operation Scheme
The following diagram shows how each battery operates within the system.
Monitors
primary
sub-battery
voltage.
(LB2)
Fig. 2.5
[A] This is the power supply route where the fully charged main battery is installed.
While the power is on, the main battery supplies power to all the devices, including the main circuit,
PC card slot and DRAM, and, at the same time, it charges the secondary sub-battery.
Sub-battery
Primary
sub-battery
Objective devices of backup
[A] Charge
Secondary sub-battery
(Rechargeable)
[C]
(DRAM, etc.)
[B]
Main battery
(During ON)
[A]
Monitors main battery
voltage (LB1LB0)
[A]
(CPU and controllers, etc.)
[A](During ON)
PC Card Slot
Main circuit
SRAM Card
Monitors
SRAM card
voltage. (LB3)
In the suspend state, it stops the supply of power to the main circuit and PC card, but continues to
supply power to the DRAM and charge the secondary sub-battery. In this route neither the primary
nor the secondary sub-batteries are used.
[B] This is a power supply route operating where the main battery is absent or not fully charged.
The DRAM is back-upped by the voltage of the secondary sub-battery. The primary sub-battery is
not used.
[C] This power supply route operates if the main battery and secondary sub-batteries are not fully
charged. The DRAM is backed-up by the voltage of the primary sub-battery. If the voltage of this
primary sub-battery falls below the limit level, an LB2 event occurs.
28
Low Voltage Level
The IT-2000 continuously monitors the voltage of the main battery, the primary sub-battery, and the
SRAM card battery. This allows an application program to determine through the system library if
the voltage of each battery reaches a warning level.
The following table summarizes the low battery voltage warning levels, which application programs
can acquire through the system library.
NameAbbreviat-
Low main battery
voltage warning level
Low sub-battery
voltage warning level
Low SRAM card
battery voltage
warning level
Objective
ion
LB1Main batteryIndicates that the main battery voltage
LB2Sub-batteryIndicates that the sub-battery voltage has
LB3SRAM card
battery
battery
has reached a limit level that requires a
warning to be issued. The system sounds
the buzzer to issue an alarm. If this
occurs, the user must replace the main
battery within ten minutes. If the battery
is not changed within ten minutes, the
system automatically executes the
suspend process.
reached a limit level that requires a
warning to be issued. Since the system
does not issue an alarm, the application
program must execute a warning by
acquiring the status from the system
library.
The sub-battery must be replaced
according to the procedure described later.
Indicates that the SRAM card battery
voltage has reached a limit level that
requires a warning to be issued. Since the
system does not issue an alarm, the
application program side must execute a
warning by acquiring the status from the
system library. The SRAM card battery
must be replaced according to the
procedure described later.
Description
There is also a main battery inoperable level (LB0). This is the status of the main battery when its
voltage falls below LB1. If this happens, the system executes an emergency power off (critical
suspend). Therefore, this level is also referred to as the emergency escape process level.
This status cannot be acquired from the application side, since the system turns off the power as
soon as the voltage reaches LB0.
29
Main Battery Voltage Monitoring
(a)
(c)
(d)
If the main battery voltage reaches LB1, the system issues a warning buzzer. If this warning buzzer
sounds, either start recharging the battery or replace it with a fully charged battery as soon as
possible.
If one of these measures is not taken within ten minutes, the system will forcibly turn off the power
for safety. The following diagram shows the main battery voltage against the time axis.
Main
Battery
voltage
LB1
Generate warning
buzzer.
Turn OFF power
automatically
(b)
Voltage level to
allow operation
Start to
recharge
LB0
(e)
10 minutes
Fig. 2.6
(a) If the main battery voltage reaches LB1, the low battery voltage warning alarm sounds.
(b) Unless the main battery is either replaced or recharged within ten minutes, the system power is
automatically turned off to protect the data.
(c) If the main battery voltage falls further and reaches LB0, the system automatically shuts off the
power to the main unit (critical suspend).
(d) If the main battery voltage drops below LB0, the main unit power cannot be turned on even if the
Power switch is pressed.
(e) If the main unit is mounted on the I/O Box or connected to the AC adaptor, charging of the
battery is initiated and the main battery voltage will gradually increase.
(f) Once the main battery voltage has been recharged to an operable level, it is possible to turn on
Time
the power to the main unit.
30
Loading...
+ 194 hidden pages
You need points to download manuals.
1 point = 1 manual.
You can buy points or you can get point for every manual you upload.