1. Toshiki's HOME
  2. Computer Area
  3. Room of OASYS Pocket3
  4. Power consumption of Pocket3

Power consumption of Pocket3

I was measured with a digital multimeter the power consumption of the Pocket 3.

Standby power consumption

First, I tried to measure the current consumption during standby(power OFF).

Standby current (mA)
Supply(Voltage) Pocket3 Pocket2
Main
machine
2nd
machine
NiMH x 2 (2.4V) 0.04 0.06 0.04
Alkaline x 2 (3.0V) 0.08 0.08 0.05
DC Adapter (3.0V) 0.08 0.08 0.05
NiMH x 3 (3.6V) 0.09 0.10 0.06
Alkaline x 3 (4.5V) 0.13 0.14 0.09

Previously, it was said the current consumption is large Pocket3 as compared to Pocket1/Pocket2. From the above results, it is likely Apparently. In addition, individual difference of Pocket3 also seems large. Current will also become large if voltage becomes large. For efficiency, it is desirable to maintain low voltage long time. Power supply voltage is too low, lithium battery for backup might rapidly deplete. Therefore, about 3V of power supply voltage is good.

In the above three machines, there was no difference according to whether a memory card. And, in the main machine, I tried to study be a change in the backup lithium battery of new and one that was degraded by using a long period of time, but there was no difference at all to them.

Current consumption in OASYS mode

Next, I tried to measure the current consumption in the OASYS mode.
I tried the change of the current value due to the LCD background color (black or white).
The unit of an upper table is milliampere, a lower unit becomes ampere from here.
Please be careful.

Current in OASYS mode (unit: A)
LCD conditionPocket3Pocket2
Main
machine
2nd
machine
Two inserted
memory card
No memory cardNo memory cardNo memory card
Main
menu
Most
Dark
White
background
0.130.120.120.09
Black
background
0.130.130.120.09
UsuallyWhite
background
0.120.120.110.08
Black
background
0.130.130.110.09
Most
Bright
White
background
0.120.120.110.08
Black
background
0.130.120.110.08
Document
editing
screen
Most
Dark
White
background
0.130.120.110.08
Black
background
0.130.130.120.09
UsuallyWhite
background
0.130.120.100.08
Black
background
0.130.130.110.08
Most
Bright
White
background
0.120.120.100.08
Black
background
0.130.120.100.08

All feeding method is genuine power adapter.
The following tendencies can be guessed from the above result.
It seems that the current consumption is less :

However, these may be ranges with error.

DOS mode current consumption

Measuring instrument: same as the above.
Feeding method: genuine wall adapter.
Concentration of a liquid crystal: Standard concentration of white background all.
Backup lithium battery: Main machine is using a new battery, and 2nd machine is degraded by long term using.
Memory card slot: Dos formatted memory card in both slot.

DOS mode current consumption (unit: Ampere)
Comparison of the application using and the command promptMain
machine
2nd
machine
DOS promptHardware CPU savingPDC resident0.120.10
PDC non-resident0.120.10
None Hardware CPU savingPDC resident0.120.10
PDC non-resident0.210.17
Application (NIFP)
running
Hardware CPU savingPDC resident0.130.11
PDC non-resident0.220.17
None Hardware CPU savingPDC resident0.130.11
PDC non-resident0.220.17

In the case of a command prompt, if a CPU stop is set up by the SETUP(or BATCHECK) command or caused to the resident PDC, it goes into power saving. However, in NIFP use, there is no effect at all to set CPU stop and PDC is functioning effectively. Other applications, CPU stop setup becomes enabled or disabled by software.
This is based on the structure of application.
If it software uses the standard input routine of DOS, CPU stop setting is enabled. Maybe, power-saving process is performed automatically inside DOS.
On the other hand, in the case of the software which is using the own input routine for the purpose of such as high-speed processing, automatic power saving processing of DOS does not work. Even then, if PDC resides in advance, it interrupts between an own input routine and hardware, and performs power saving processing instead of DOS.


Vz consumption current (Unit: A)
Comparison of the original Vz for Pocket3
and the Konno version Vz
Main
machine
2nd
machine
The original Vz
edit screen
Hardware CPU savingPDC resident0.130.10
PDC non-resident0.220.17
None Hardware CPU savingPDC resident0.130.10
PDC non-resident0.220.17
The original Vz
filer
Hardware CPU savingPDC resident0.130.10
PDC non-resident0.220.17
None Hardware CPU savingPDC resident0.130.10
PDC non-resident0.220.17
Konno version Vz
edit screen
Hardware CPU savingPDC resident0.130.10
PDC non-resident0.120.10
None Hardware CPU savingPDC resident0.130.10
PDC non-resident0.130.10
konno version Vz
filer
Hardware CPU savingPDC resident0.130.10
PDC non-resident0.130.10
None Hardware CPU savingPDC resident0.130.10
PDC non-resident0.130.10

Once, Vz was a famous editor at high speed. Naturally, Vz is using the DOS-independent input routine. From the current consumption of the original version, this is obvious.
On the other hand, by including a power-saving routine similar to the PDC portion of the input routines, the konno version is performing power saving control by itself. This effect sounds great.


Room of OASYS Pocket3
Computer Area
Room layout


All contents are Copyright © 2017 Toshiki, All rights reserved.
Toshiki / toshiki @ jcom.zaq.ne.jp