No patent liability is assumed by TOSHIBA Corporation with respect to use of information, illustrations,
circuits, equipment or examples of application in this publication.
TOSHIBA Corporation reserves the right to make changes and improvements to this publication and/or
related products at any time without notice. No obligation shall be incurred other than as noted in this
publication.
This publication is copyrighted and contains proprietary material. No part of this book may be reproduced,
stored in a retrieval system, or transmitted, in any form or by any means — electrical, mechanical,
photocopying, recording, or otherwise — without obtaining prior written permission from TOSHIBA
Corporation.
PROSEC, TOSLINE and TOSDIC are trademarks or registered trademarks of TOSHIBA Corporation.
IBM is a registered trademark of International Business Machines Corporation.
Microsoft, MS-DOS, Windows and Windows NT are registered trademarks of Microsoft Corporation in the
U.S.A. and other countries.
Ethernet is a registered trademark of Xerox Corporation.
DeviceNet is a trademark of the Open DeviceNet Vender Association, Inc.
This manual contains important information for the operator to operate this product safely and correctly
and avoid bodily injury and property damage.
Grasp the meanings of the following marks and their descriptions before reading this manual.
Hazard Classifications
Indicates a potentially hazardous situation which, if not avoided,
WARNING
CAUTION
Note: 1. Serious injury means loss of sight, injury, burns (high temperature, low temperature), electrical
shock, fracture, or intoxication which leaves aftereffects or requires hospitalization or need to
go to the hospital for a long time.
2. Injury means hurt, burn, or electrical shock which does not require hospitalization or going to
the hospital for a long time.
3. Property damage means extended breakdown of assets and materials.
could result in serious injury or death.
Indicates a potentially hazardous situation which, if not a avoided,
can result in minor or moderate injury, or property damage. It can
also be used to alert against unsafe practices.
Notation of Markings
Indicates a "may not" mark.
Prohibited
Mandatory
Caution
Note: The description of forbiddance, mandatory, and caution marks are subject to change, depending
on the labels on the main unit.
The concrete forbiddance is indicated with a pictograph or wording.
Indicate a mandatory action that you should never fail to do.
The concrete content is indicated inside or near the circle with a
pictograph or wording.
Indicates a caution.
The concrete content is indicated inside or near the triangle.
Make certain to ground the transmission
paths by grounding with 100ɹ or less ground
resistance exclusively for each segment.
Ground at one point.
Noncompliance may cause transmission
errors.
Noncompliance may cau se an elect ric sh ock
or a fire.
CAUTION
Mandatory
Avoid installing or storing the controller in the
following environment:
• A dusty place.
• A place in which a corrosive gas (SO
or combustible gas generates.
• A place subjected to vibration or shocks
exceeding pe rmissible values.
• A place that causes condensation due to
sudden temperature changes.
• Low or high temperature outside of
installation conditions.
• High humidity outside of installation
conditions.
• Direct sunshine.
• Near equipment that emits a strong radio
wave or magnetic field.
, H2S)
2
Mandatory
Do not impress high voltage to a connector or
a terminal board exceeding rated voltage,
such as 100V AC. Always connect to correct
polarity. Incorrect polarity may cause an electric shock or a fire.
Mandatory
Install the equipment in a place affording
easy maintenance servicing and checks.
Otherwise, a trouble may be caused during
a failure, resulting in a major accident.
Forbidden
Do not block the ventilation port or suction/
exhaust port of the equipment.
Otherwise, overheating or other phenomena may cause a fire or a failure.
Mandatory
Noncompliance with the installation
conditions described in this manual during
system installation or wiring may disable
the controller to demonstrate its design
performance and may cause equipment
malfunction or failures.
ii
Mandatory
Always install the module after turning the
external power supply off. Otherwise, the
module failure or an electric shock may
result.
model 2000/3000 Computer Module C2/C3 Windows NT Version
Page 5
2. Safety Precautions during Maintenance Servicing or Checks
Always turn the power off when plugging or
unplugging a module or a board, or when
connecting equipment.
Otherwise, an electric shock accident or
equipment failure may result.
CAUTION
Forbidden
Exercise reasonable care and do not drop, collide with other article or apply a strong shock
to the equipment or a board.
Otherwise, a failure may result.
Mandatory
Make certain that the external power is turned
off before mounting or dismounting the
module after installing cables in it.
Otherwise, an electric pole will appear on the
backside of the external terminal board,
potentially causing an electric shock.
Mandatory
Place a conducting mat or a conducting bag
(bag containing a spare board or other part) on
a grounded table and put a board or the
module removed from a unit or a base unit on
the table.
Otherwise, parts may be damaged by static
electricity or other phenomenon.
Mandatory
Discharge static electricity charged on human
body by touching a grounded metal before
touching the equipment or a board.
Otherwise, static electricity may cause
equipment malfunction or a failure.
Mandatory
Clean equipment, a module or board dirtiness
using a soft cloth. Use a cloth moistened with
water and wringed if dirtiness is stiff.
The equipment, the module or a board left
dirty may cause a wrong decision or
malfunction.
6F8C0894
Forbidden
Do not use benzine, thinner or other solvent
when cleaning a module or a board.
Otherwise, a panel, module or board may
deform or discolor.
iii
Page 6
3. Safety Precautions in Replacing Parts with Ended Life
Make certain to set the switch of any
equipment to the OFF position before replacing
a power fuse or an alarm fuse installed in the
equipment.
Otherwise, an electric shock or a fire may
result.
4. Safety Precautions in Daily Operation
WARNING
Mandatory
Make certain to check that the power supply
capacity, frequency, voltage and regulation
meet the equipment specification.
Otherwise, the controller will not be able to
demonstrate its design performance and may
cause equipment damage, a fire due to
overheating, or other trouble.
Mandatory
In case the ambient or internal temperature of
the equipment increases abnorm all y or the
equipment fails, stop operating and turn the
power off to the equipment. Then contact the
Toshiba distributor in your area.
Continuing to operate the equipment without
taking any action may result in a fire due to
overheating or other trouble.
iv
model 2000/3000 Computer Module C2/C3 Windows NT Version
Do not touch the ICs, terminals, connectors,
solder surfaces or other parts insid e the
modules, except the operation section (setting
switches insi de the module).
Otherwise, ICs, LSIs or other devices may be
destroyed by static electricity, resulting in a
failure. An injury by the terminal of a parts
lead wire or a burn by a high-temperature part
may result.
Forbidden
Do not disassemble or remodel the
equipment, module or a board.
Otherwise, equipment safety may be lost
and equipment malfunction or failure may
potentially result.
Forbidden
Do not bend, pull or twist the power cord or
cable too strongly.
This may cause wire breakage or heating.
Forbidden
Do not insert a metal piece or drop a paper clip
through a clearance in the equipment body.
A fire or other trouble may result.
5. Safety Precautions During Transportation, Storage and Scrapping
CAUTION
Mandatory
Comply with ordinances or regulations of
the local government in your area when
discarding the product.
Forbidden
When transporting or storing, put the product
in a conducting bag and pack it in a crated
box.
Otherwise, a failure may result.
The equipment has been designed and manufactured for use in an industrial environment.
However, the equipment is not intended to be used for systems which can endanger human life
(Note 1).
Consult Toshiba if you intend to use the equipment for a special application which involves human
life and has great influence on the maintenance of the public function (Note 2). This is why such
application requires special care on the operation, maintenance, and control of the system (Note 3).
(Note 1) The systems which can endanger human life are life maintenance systems, equipment
installed in the surgery, and other medical equipment.
(Note 2) The systems which involve human life and have great influence on the maintenance of the
public function mean the main control system of a nuclear power plant, safety and
protection system of a nuclear power facility, transport operation and control systems for
mass transportation, control systems of aviation and space systems, and other systems
and subsystems where safety is critical.
(Note 3) "Special care" means to build a safety system (foolproof design, fail safe design,
redundancy design, etc.) in full consultation with Toshiba's engineers.
Immunity
Toshiba is not liable for any loss caused by fire, earthquake, action by a third party, or other
accidents, or the operator's intentional or accidental misuse, incorrect use, or use under abnormal
condition.
Toshiba is not liable for any incidental loss caused by the use or non-use of this product, such as
loss of business profits, suspension of business, or loss or change of data on memory.
Toshiba is not liable for the loss caused by an operation contradictory to any of the instructions
stated in this manual.
Toshiba is not liable for the loss caused by an incorrect operation in combination with other
equipment.
Toshiba is not liable for the loss caused by a malfunction in combination with an application program
made by the customer.
NOTE:
Use cellular phones and PHSs at least one meter away from the working equipment, transmission
cables, and I/O bus cable. Otherwise, the system can malfunction.
vi
model 2000/3000 Computer Module C2/C3 Windows NT Version
This manual describes Windows NT, the operating system of Microsoft Corporation,
installed in the Computer Modules C2/C3 of the Integrated Controller, with a focus on the
features added or extended to the operating system. The reader is invited to read
manuals of Microsoft for the full information on Windows NT.
This manual is composed of the following chapters:
Chapter 1 Windows NT
Chapter 1 describes initial settings of Windows NT, which is preinstalled, and other
matters.
Chapter 2 I/O Bus Support Software
The C2/C3 can directly control the parallel bus I/O modules. This chapter describes
the I/O bus support features, which control the modules, and API.
Chapter 3 RAS Support Software
This chapter describes the RAS features of the C2/C3 and usage of them.
Turning the power off before normal ending of Windows NT may damage the file system
and important files. In the worst case, Windows NT cannot potentially be started.
Make certain to execute finish processing of Windows NT before turning the power off.
Also, make certain to supply the power that is always stable.
Detection of Abnormal Temperature
If the operating environment is not suitable, the inside temperature of the main unit may
exceed the specified value, which potentially presents a hazard of a system fault due to
equipment malfunction.
The C2/C3 monitors the CPU temperature through the RAS feature and generates an
alarm in case the temperature exceeds a preset value (currently 55
trouble. It is strongly recommended that application systems incorporate a program that
detects this alarm. The program should inform the operator about a trouble and stop the
system till the cause for a temperature error is removed when it receives such notice.
See the XrasUserWindow Command in "RAS Support Software" in chapter 3 for a
method to detect a temperature error by a specific application program.
File Backing Up
o
C), to notify a
Back up important files from time to time by copying files into backup files. Important files
cannot be restored in case they are lost by an unanticipated accident, unless they are
stored in backup files.
Changing Registry Value
Changes of the registry, which stores set values and registration information of Windows
NT require very careful execution. If an error is made in making a change, system
startup may be disabled.
Service Pack1 Installation
Reinstall the Service Pack when the system configuration is added or changed, such as
network protocol addition.
Caution for setting memory space addresses for PCMCIA card
Note that memory addresses 0xC8000 to 0xCA000 cannot be used for a PCMCIA card
or other card when mounting a card to use memory spaces in PCMCIA slots.
This is not shown in the Windows NT resource display , but a graphic chip also uses these
addresses.
1. A collection of Windows NT bug correction modules supplied by Microsoft. The
Service Pack is stored in the root directory of Drive C in "SP6a" or other name.
2
model 2000/3000 Computer Module C2/C3 Windows NT Version
When shipped from the factory, Windows NT is set as follows:
Version
Windows NT4.0 Workstation (Build 1381 Service Pack 6)
This is the version as of May 29 2000. The Service Pack version may vary depending on
the release status of Microsoft Corporation.
The Service Pack is stored in the hard disk as C:¥SP6a.
QFE (Quick Fix Engineer in g)
after installing SP6a.
Registered User Name
administrator (No password)
Guest (No password)
User management is executed by [User Manager] inside [Control Tool Group] after
logging on by "administrator" when adding a new user or setting or changing a password.
Network
No software setting
When using the 10BASE-T port on the C2/C3 main unit, use the network driver supplied
as an accessory, instead of a Windows NT CD-ROM driver.
Make certain to reinstall the Service Pack after setting the network.
2
also is stored under SP6a. Be sure to install QFE also
1
Graphic
Standard VGA Driver
Using the graphic driver supplied as an accessory (NeoMagic MagicGraph 128/Z/ZV),
the C2/C3 accomplishes screen display with a resolution of 1024 x 768 and 65,536 color
pallet colors.
The device drivers and other applications are stored under the following directories
during preinstallation. This directory configuration is the same as that in the backup CDROM.
i386A device driver supported by Windows NT as a standard
provision.
DRVLIBA device driver by driver distribution service of CompuServe of
the United States manufactured by a third party.
DRVLIBJA device driver manufactured by a third party in Japan
(Japanese version only)
SUPPORT¥USPRNDRV A printer driver supplied with Windows NT of the US version as
a standard provision.
TOSHIBAA network driver graphic driver for Ethernet port of the main
unit.
SP6aService Pack 6a (contains QFE)
A path for the driver storage directory needs be specified when installing a driver or other
application. If the CD-ROM cannot be used when "E:¥i386" or other data is displayed,
execute by specifying "C:¥i386" in the field for path name specification.
These directories store drivers needed in driver installation during a system configuration
change or in other instances. These drivers can be deleted without affecting Windows
NT operation if system configuration changes are not required.
These directories will not be created when the customer reinstalls Windows NT. Specify
driver paths for directories needed for driver installation, to read from the CD-ROM. If the
CD-ROM is assigned to Drive E, specify "E:¥driver path name."
Floppy Disks Attached
The floppy disks supplied with the equipment store modules of various features
described in this manual.
Revision Upgrading
When the version of the preinstalled Windows NT is upgraded, the latest version of
Windows NT has to be purchased separately.
The customer needs to purchase and install the Service Pack separately for revision
upgrading. The latest Service Pack can be purchased at cost through a Web site or from
Microsoft.
4
model 2000/3000 Computer Module C2/C3 Windows NT Version
This chapter describes the I/O bus support software.
This software supports data from the C2/C3 input to and output from the various I/O
modules connected to the I/O bus. This software enables direct access of the I/O
modules from Windows NT, thereby easily accomplishing system construction with only
the C2/C3.
The following advantages can be derived by using this software:
• Easy creation of an I/O control application system merging screen control and network
features.
• This means that linkage with SCADA (supervisory control and data acquisition)
software can be accomplished easily.
• An enhanced development environment of Windows NT can be used when creating
an I/O access program.
• Processing of a high parallelism by using multi process and multi thread.
• The same machine can develop and execute programs.
References:
The reader is recommended to read the following documents also after reading this
manual:
• Sequence Controller S3 Main Unit Instruction Manual(6E8C3783)
figure 2-1shows the maximum hardware configuration of C3 supported by this software.
2.2 Hardware Configuration
Basic Unit
576-Points/Basic Base (BU719)
Expansion Units 1-1 to 1-7
Expansion Units 1-1 to 1-7
Expansion Units 1-1 to 1-7
Maximum Number of Points for Two Systems
10432 points/When expansion base for 11 boards is used
5962 points/When expansion base for 6 boards is used
Maximum Number of Points for Up To Three Systems
15360 points/When expansion base for 11 boards is used
8640 points/When expansion base for 6 boards is used
Maximum Number of Points for Up To Four Systems
20288 points/When expansion base for 11 boards is used
11328 points/When expansion base for 6 boards is used
2
1280 points/When expansion base for 11 boards is used
960 points/When expansion base for 6 boards is used
Expansion Unit
1984 points/When expansion base for 11 boards is used
1344 points/When expansion base for 6 boards is used
Expansion Unit
2688 points/When expansion base for 11 boards is used
1728 points/When expansion base for 6 boards is used
Expansion Unit
3392 points/When expansion base for 11 boards is used
2112 points/When expansion base for 6 boards is used
Expansion Unit
4096 points/When expansion base for 11 boards is used
2496 points/When expansion base for 6 boards is used
Expansion Unit
4800 points/When expansion base for 11 boards is used
2880 points/When expansion base for 6 boards is used
5504 points/When expansion base for 11 boards is used
3264 points/When expansion base for 6 boards is used
Expansion Unit
Figure 2-1 Maximum Hardware Configuration of C3 2 Basic Unit
The API needed for an application to access an I/O module is mounted as DLL. The file
name of DLL is "g3iolib.dll."
The API provides interfaces for data input and output, various initializations, module error
information acquisition and other purposes.
2.3.2Service
The service manages startup function registration when interrupts from the application
are generated. In case an I/O module specified for startup is interrupted, the user
function registered in advance is executed. The service manages batch input/output
data between the driver and application.
The parameters to specify operations by the batch input/output feature are stored in the
registry. For the complete information, see "2.7 Batch Input/Output"
2.3.3Tool
The tool is a GUI tool that operates on Windows NT. Using this tool, the following
settings can be executed and information can be displayed.
(1) Individual mapping
The tool sets the types of mounting slots and modules of the I/O modules. Specify
mounting slots by a channel number, unit or a position inside a unit. Specify module
types by selecting from X, Y, X+Y, iX, iY and iX+Y.
The set information will be stored in the registry and will be looked up when the driver
starts up.
8
model 2000/3000 Computer Module C2/C3 Windows NT Version
Individual mapping information, which is specified once, can be cancelled and automatic
mapping can be executed.
(2) Display of result of automatic mapping
In case individual mapping is not specified, the driver will execute automatic mapping
when the system is started. The tool displays results of automatic mapping.
(3) I/O bus mapping address change
Addresses of a memory space to be used by the I/O bus can be changed.
A change is not required in normal operations. A change is needed only if an address
conflicts when a PC card is used.
The following two addresses can be selected:
A) 0xD0000-0xD7FFF (Default)
B) 0xD8000-0xDFFFF
(4) Setting I/O bus time-out diagnosis time
An I/O bus time-out diagnosis time is set. If ACK is not returned within a preset time, a
hardware error will be declared and subsequent I/O bus accesses will be disabled.
A diagnosis time can be set between 4µs minimum and 60µs maximum in increments of
4µs. Default is set at 32µs.
The following settings can be executed by directly changing registry values using the
registry editor:
• Execute/non-execute on startup of module diagnosis
Whether or not to diagnose faults of the I/O modules executed by the device driver
should be executed beginning system startup can be specified.
Key: DiagStart
Value: 0 (Non-execute on start [default]) or 1 (Execute on start)
If execution is not started on start, diagnosis can be started using the function
"IobusSetDiag."
• Module diagnosis time interval
A time interval to execute the foregoing module diagnosis is specified.
Key: DiagInterval
Value: An integer larger than 0 (in seconds); default value 5
• Number of retry sessions during module error detection
The number of retries executed when an error occurs in module accessing is specified.
The driver tries accessing for the specified number. If errors still continue, the status of
the module is set to "error" and this module will be excluded in subsequent accessing.
By increasing this value, the resistance to temporary module errors increases. However,
the input/output speed will lower.
Key: RetryCount
Value: An integer larg er than 0 (in cycles); default va lue 5
2
2.3.4G3 I/O Driver
A G3 I/O access driver that functions as an I/O driver of Windows NT. The driver
processes data input/output from applications via API and initialize requests.
Operations of this driver are transparent to the application program.
This software implements the features provided by S3 and S2 designed exclusively for I/
O module control. The integrated controller basically differs from the so-called PLC in
hardware and software and an application system must be designed heeding to the
following when constructing an application system.
2.4.1Specification Limitations and Cautions
• In case more than one controller are installed in the same basic unit, only one
controller installed in Slot 0 can control the I/O modules.
• The interrupt response time may vary depending on the system environment
(hardware and software configur ations and other elem ent s).
• Intervals of interrupts from modules that may generate interrupts such as CDDIs and
intervals of timer interrupts by software must be designed taking the load of the entire
system into consideration. If intervals are too short, the response performance of the
entire system may be lowered.
• A feature equivalent to the fixed-time scan feature in S3 can be implemented using
Win32API. The interval accuracy depends on the features and performance provided
by Windows NT.
• Depending on how the priority is set by application, operation of this software may
delay by operations of other Windows applications.
• If I/O module accessing causes a time-out, scan execution period by the service will
delay.
2.4.2Programming Precautions
• Application programs are created as Win32 applications.
The application programs call functions supplied by this support software and access
the I/O modules.
• Fixed-cycle interrupts can be implemented by using a feature provided by Win32API.
• In both floating scanning and fixed-time scanning, the control structure such as
repeating has to be described by an application itself.
• The startup timing of application programs that use the features of this software is the
same as in starting ordinary Win32 applications.
• Execution of a program without releasing the CPU will deteriorate the response of the
entire system.
• Functions can be started up by interrupts such as CDDIs. These functions are
executed as threads and a library (libcmt.lib) compatible to multithreads must be linked
during coding.
For the complete information, see the API referen ce "Io bus Reg Cal lba ckF un c."
• Function ending and data sending to an actual device of batch output functions in this
support software are not synchronized. Data is stored by output operation of the
service.
For the complete information, see "2.7 Ba tch Input/Output"
10
model 2000/3000 Computer Module C2/C3 Windows NT Version
• The feature "In case one scan processing time exceeds a preset time in fixed-time
scanning, scanning will change to floating scan, but will reset to fixed-time scanning
when the processing time returns" in S2/S3 is not provided. If this processing is
needed, it must be processed by an application program.
• Modes corresponding to HALT, HOLD and DEBUG in mode control processing
provided by S2/S3 are not available.
• Normally operated in a mode corresponding to RUN or RUN-F. The mode will change
to the ERROR mode if a critical error occurs, stopping the access feature.
Whether normal operations correspond to RUN or RUN-F depends on coding of the
application program.
• User data is initialized by data setting by an application program.
• A feature to latch user data in a power failure is not provided.
2.4.4Purchasing and Development Environment
• This software is authorized to be installed in one each application development
machine and target machine only. The user is requested to kindly purchase this
software for each of target machines in case more than one target machine are used.
• A C/C++ development environment for Windows NT, such as Visual C++ of Microsoft,
needs be purchased in developing application programs.
The input and output modules supported by this software are listed below. For the
complete information of each module, see related information of the I/O modules.
As a rule, the I/O bus support API is used in the following flow:
(1) Gets a file handle by CreateFile (WIN32 API).
(2) Gets results of automatic mapping by IobusGetMappedinfo. (Option)
(3) Registers callback function for interrupts by IobusRegCallbackFunc. (Option)
(4) Specifies module diagnosis during I/O execution by IobusSetDiag. (Option)
(5) Issues Iobus{RecvData|SendData|RecvDataDirect|SendDataDirect} and executes
batch data input and output and direct input and output.
Executes registration functions when an interrupt generates or at a fixed cycle.
(6) Repeats Step 5) for a necessary number of operations.
(7) Releases the file handle gotten in Step 1) by CloseHandle (WIN32 API) and ends the
flow.
Functions are provided by g3iolib.dll and g3iolib.lib and these functions are prefixed
"Iobus." When using each function, include Header File g3iolib.h.
The files will be stored in the following positions:
C:¥Program Files¥TOSHIBA¥G3IO¥bin¥g3iolib.dll
C:¥Program Files¥TOSHIBA¥G3IO¥include¥g3iolib.h
C:¥Program Files¥TOSHIBA¥G3IO¥lib¥g3iolib.lib
14
model 2000/3000 Computer Module C2/C3 Windows NT Version
Directories and libraries are set as follows in Visual C++5.0 (and subsequent versions) of
Microsoft:
• Directory Setting
Set a directory to search header files and library files.
(1) Select "Option (O) ..." in the "Tool (T)" Menu.
(2) Select "Directory" Tab.
(3) Select "Include File" in "Directory to Show (S)."
(4) Add "C:¥Program Files¥TOSHIBA¥G3IO¥include" to the new path.
(5) Click "OK" to complete setting.
2
• Library Setting
(1) Select "Set (S) ..." in the "Project (P)" Menu.
(2) Select "Link" Tab and add g3iolib.lib to "Object/Library Module (L)."
This section describes operating principles of batch input and output in this support
software and useful information for creating application programs.
G3 I/O
G3 I/O
Driver
ドライバ
G3 I/O
G3 I/O
Mutex
Mutex
Input File
入力ファ
イル
2.7 Batch Input/Output
2
アプリケーション1
Application 1
Figure 2-3 Configuration of Batch Input/Output Software
2.7.1Operating Principles
Batch input and output is accomplished by interaction among the I/O driver (g3iodrv.sys),
I/O service (g3iosrv.exe), function IobusSendData () and IobusRecvData.
Input and output data is the data that is produced when the input and output registers of
the I/O modules are in a continual state.
• Operation on Input Side
(1) The I/O service accesses each input module through the I/O driver and collects input
data.
(2) Data collected from each input register is stored in an input file as byte streams.
(3) The applications issue Function lobusRecvData.
(4) Exclusive processing (mutex secure) is performed inside the function to access an
(5) Securing mutex, data will be transferred from an input file to the user buffer.
(6) Simultaneous with transfer, input module information is obtained.
(7) The applications return from the function.
• Operation on Output Side
(1) The applications issue Function lobusRecvData.
(2) Exclusive processing (mutex secure) is performed inside the function to access an
output file.
(3) Securing mutex, data will be transferred from the user buffer to an output file.
(4) The applications return from the function.
(5) The service reads data from the output file.
(6) Read data is written in the output module through the driver.
The service on the input side periodically stores input module data in the input file
regardless of application operations. The service on the output side queues for updating
of file data from the application and transfers data to the output module when updating is
confirmed.
Completing one cycle each of operation for input and output, the service pauses for
ScanCycle*100ms and proceeds to the next operation cycle.
In case "1" is specified in Registry Value Scan Policy , the service can neither secure
mutex nor perform file exclusive control in file accessing. As the number of application
processes increases, the time to secure mutex also increases. As a result, the operation
cycle sometimes lengthens. This setting avoids phenomena of operation cycles
becoming unstable. Nevertheless, elimination of exclusive control may result in data,
which is being accessed, exchanged with a function and data consistency cannot be
guaranteed.
The service starts and processes different threads on the READ and WRITE sides.
2.7.2Application Creation
Applications that use batch input and output proceed as follows:
(1) Gets the number of input and output modules and totals of word numbers on the
input and output sides using IobusMappedinfo() and verifies that the numbers agree
with the system configuration.
(2) The input and output sides secure buffers that satisfy the total size of the number of
words on both the input and output sides. The buffers may be secured dynamically
or statically.
(3) Data is input and output using IobusSendData() and Iobus RecvData().
(4) The IO information structure () is externally looked up inside functions and a check is
made whether or not errors have occurred with the modules.
(5) Return to (3).
18
model 2000/3000 Computer Module C2/C3 Windows NT Version
Parameters that specify service scanning operations can be controlled by the registry.
HKEY_LOCAL_MACHINE¥System¥CurrentControlSet¥Services¥g3iosrv
• Scan Operation Policy
Specify whether data consistency warranty should be given the priority or the scan cycle
time is given the priority before performing scanning.
Key: Scan Policy
Value: 0 (priority given to data consistency [default]) or 1 (priority given to cycle time)
• Scan Operation Cycle
Specify a time to hibernate after finishing one scan. A short hibernation time achieves
carefully-thought-out I/O, but increases the CPU load, thereby potentially affecting other
processes and threads adversely.
Key: ScanCycle
Value: An integer larger than 1 (in millisecond), default value 5 (500msec)
2.7.4mutex (Exclusive Control)
In case many processes or threads are requesting access, the service or the function
may not be able to secure mutex. The time-out times for them are fixed at
G3WRITEWAIT and G3READWAIT.
If the service cannot secure Mutex, files are not read or written during this cycle and next
scan operation is processed. If the IobuxSendData/IobusRecvData function cannot
secure Mutex, the function will make an error return, allowing fetching of
ERROR_TIMEOUT by GetLastError().
In case the foregoing event occurs, the function can retry. However, the access
frequency should be adjusted to prevent such time-outs.
As part of the RAS features of this software, a driver and hardware self-diagnostic feature
is implemented.
Table 2-5 Self-Diagnosis Items (When driver is loaded)
Diagnosis ItemDiagnosis
Access Authority CheckCheck is made whether or not
own controller can access the I/O
modules.
I/O Collation CheckIf individual mapping is specifi ed,
mapping information and
implementation status are
collated.
Operation When Trouble is
Detected
Records "No access auth ority" in
event log. All subsequent data
input/output requests from
applications will become errors.
Records "Information mism atc h"
in event log. All subs equent da ta
input/output requests from
applications will become errors.
Table 2-6 Self-Diagnosis Items (When application is executed)
Diagnosis ItemDiagnosis
MIF Time-OutCheck is made if response
comes back within sp ecifi ed time
during module access.
Module Error Diagnosis
(Option: Can be set/reset
by API)
Module error status is
periodically checked.
Operation When Trouble is
Detected
Records "MIF time-out" in event
log.
Records "error" in module
management table. This
information can be fet ched by
API.
2.8.2Event Log
This software records the following trouble information and alarm messages in the event
log of Windows NT. The event log can be checked using the event viewer.
• The service "Source" will be stored in g3iosrv and in "Application" of the event log.
CategoryMessageMeaning
Informationdetect unreaded message
WarningCan't set service version to driver Service driver cannot be registe red in the
Table 2-7 Event Log Messages of G3 I/O Service
Detected that previous interrupt
(chan %d, unit %d, mod %d)
No %s module founded
(%s: Input or Output)
No Mailslot created
(chan %d, unit %d, mod %d)
Invalid(%s) value(%d).
Use default
information is not fetched in a function
when an interrupt was generated from
channel %d, unit %d or module %d.
Means that "interrupt omission" has
occurred.
An input module or output module does
not exist.
It does not affect operation.
→
driver.
An interrupt was generat ed from cha nnel
%d, unit %d or module %d, but Mailslot
to notify to function is not created.
Illegal value (%d) was specified by
Registry Key %s. Use an implicit value.
→
20
model 2000/3000 Computer Module C2/C3 Windows NT Version
Table 2-8 Event Log Messages of G3 I/O Device Driver
2
InformationModule has been suspended The module has been suspended.
(IobusModSuspend executed)
Module has been resumedOperation of the module has been
resumed. (IobusModResume executed)
WarningRESET command executedG3 I/O bus resetting has been requested.
(IobusDoRest executed)
ErrorCan't setup I/O space.Failed to initialize I/O space.
Can't read registryFailed to get the Registry.
Can't setup memory spaceFailed to initialize memory space.
Can't setup symbolic link.Failed to create symbolic link.
can't assign resourcesFailed to secure resources.
Can't control modules (Invalid
slot)
Can't connect interrupt.Failed to register interrupt.
Module check failedModule collation produced mismatch.
Detect illegal interruptIllegal interrupt has occurred.
Slot mounting position is illegal and
modules cannot be controlled.
22
model 2000/3000 Computer Module C2/C3 Windows NT Version
Gets results of I/O automatic mapping by the driver.
Parameters
hDeviceDriver handle gotten by CreateFile.
iomapPointer to IOMAP structure arrangement.
The arrangement should be 3D arrangement of NCHANNEL X
NUNIT X NMODULE.
2.9.4IobusSetDiag
BOOL
IobusSetDiag (
HANDLEhDevice
);
Specifies I/O module diagnosis execute. Execution of this function is equivalent to I/O
error map create function of T3/T3H.
I/O module diagnosis checks the module error status when accessing a module.
Execution of this feature, therefore, increases overhead. Detected module errors can be
gotten by Function IobusGetDiagInfo.
Parameters
hDeviceDriver handle gotten by CreateFile.
2.9.5IobusResetDiag
BOOL
IobusResetDiag (
HANDLEhDevice
);
Resets I/O module diagnosis execute specified by IobusSetDiag or the registry. This
function can be called any time.
Parameters
Parameters
hDeviceDriver handle gotten by CreateFile.
24
model 2000/3000 Computer Module C2/C3 Windows NT Version
);
Specifies a function to be called when an interrupt generates in a specified module.
Calling this function will create a thread to queue for an interrupt to generate. An
interrupt will create other new thread, which will execute the function Func.
The thread, which called this function, will reset immediately.
Data by interrupt can be selected by looking up the InterruptedData structural
arrangement, which is an internal variable of DLL.
The InterruptedData structure is a structure consisting of the foll owing members:
To look up this structural arrangement, use the Keyword _declspec keyword of the
extended attribute syntax and declare by using the storage class attribute dllimport
unique to Microsoft.
typedef struct InterruptData {
DWORDTimeStamp;
WORDXw;
WORDReserved;
} InterruptData_t;
The application to use this function will be the Multithread Application.
The link of the C Run Time Library (libcmt.lib) compatible to multithread will be needed.
Specify Option /MT, /D, or "_X86_" when executing the CL Command.
When Visual C++ is used, specify the Multithread Run Time Library in the Dialog Box
"Project Options."
When creating threads in other place by an application that uses this function, use
_beginthread or _beginthreadex. Do not use CreateThread or ExitThread. For the
complete information, see the section which describes _beginthread.
2.9 API References
2
Parameters:
FuncFunction to be started
cChChannel No. (0 to 4, 0: Basic unit)
cUnitUnit No. (0 to 7, 0: Basic unit)
cModModule No. (0 to F)
);
Data is input in batch from the input register.
The area specified by pwData must be an area sufficient to store input data.
Parameters:
hDeviceThe driver handle gotten by CreateFile.
wLengthInput data length (unit: word)
wOffsetOffset beginning from first data segment of the input register to
access (unit: word)
IpwDataPointer to input data. Data is handled as continuation of input register
data
Return Values:
When normally ended, a value other than 0 is returned for this function.
When abnormally ended, return 0 and call GetLastError () to know error details.
An ERROR_TIMEOUT generates if mutex cannot be secured during accessing.
2.9.8Remark
The module data when data is read by issuing this function can be checked by looking up
Symbol ModuleStatus. ModuleStatus is in word arrangement as in arguments used in
Function IobusGetDiagInfo. See IobusGetDiagInfo for the complete information of the
data.
26
model 2000/3000 Computer Module C2/C3 Windows NT Version
hDeviceThe driver handle gotten by CreateFile.
wLengthOutput data length (unit: word)
wOffsetOffset beginning from first data segment of the output register to
IpwDataPointer to output data. Data is written as continuation of output
2.9 API References
2
access (unit: word)
register data
Return Values:
When normally ended, a value other than 0 is returned for this function.
When abnormally ended, return 0 and call GetLastError () to know error details.
An ERROR_TIMEOUT generates if mutex cannot be secured during accessing.
);
A wLength length is directly input to data pwData from an address specified by cCh,
cUnit, cMod or cOffset.
A check is not made whether or not a module actually exists or an input device exists at
the specified address. This has to be confirmed by an application.
An area sufficient to store the data length specified by wLength must be provided in
IpwData.
Data is input in a unit of word.
Parameters:
hDeviceThe driver handle gotten by CreateFile.
cChChannel specification
0-Basic unit
1-Channel 1
2-Channel 2
3-Channel 3
4-Channel 4
cUnitUnit No. in each channel (Counted beginning 0)
cModModule No. in each unit (Counted beginning 0)
cOffsetOffset inside a module (in unit of word)
wLengthLength of data input (in unit of word)
IpwDataPointer to input data
28
model 2000/3000 Computer Module C2/C3 Windows NT Version
Data pwData is directly output to an address specified by cCh, cUnit, cMod or cOffset for
the wLength length.
A check is not made whether or not a module actually exists at the specified address or
the device can output. This has to be confirmed by an application.
Data is output in a unit of word.
2.9 API References
2
Parameters:
hDeviceThe driver handle gotten by CreateFile.
cChChannel specification
0-Basic unit
1-Channel 1
2-Channel 2
3-Channel 3
4-Channel 4
cUnitUnit No. in each channel (Counted beginning 0)
cModModule No. in each unit (Counted beginning 0)
cOffsetOffset inside a module (in unit of word)
wLengthLength of data output (in unit of word)
IpwDataPointer to output data
Inhibits access of modules specified by cCh, cUnit and cMod. This feature is used when
inhibiting access prior to exchange when changing an I/O module in an online state.
This feature will have no meaning if it is executed with a module already in a suspend
state. This function becomes an error if a specified I/O module does not exist.
2.9 API References
2
Parameters:
hDeviceThe driver handle gotten by CreateFile.
cChChannel specification
0-Basic unit
1-Channel 1
2-Channel 2
3-Channel 3
4-Channel 4
cUnitUnit No. in each channel (Counted beginning 0)
cModModule No. in each unit (Counted beginning 0)
Resets access inhibit of modules specified by cCh, cUnit and cMod. This feature is used
when resuming access by software after completing an I/O module change in an online
state.
This feature will have no meaning if it is executed with a module already in a accessible
state. This function becomes an error if a specified I/O module does not exist.
Parameters:
hDeviceThe driver handle gotten by CreateFile.
cChChannel specification
0-Basic unit
1-Channel 1
2-Channel 2
3-Channel 3
4-Channel 4
cUnitUnit No. in each channel (Counted beginning 0)
cModModule No. in each unit (Counted beginning 0)
32
model 2000/3000 Computer Module C2/C3 Windows NT Version
This support software supports features that enhance the RAS (reliability, availability and
serviceability) performance of the Integrated Controller Computer Module.
3.1.1Features of RAS Hardware Processing
This support software has the following RAS features related to hardware processing by
the RAS hardware.
• LED lighting control
• RAS memory read and write
• Internal trouble or error detection (Fan stop, abnormal temperature)
The RAS hardware uses the following I/O areas and interrupts and must be set to avoid
competition with other expansion boards. If the RAS hardware competes with other
expansion board, operation of the software cannot be guaranteed.
I/O Areas
• 0x0140 - 0x016F: Basic RAS I/O
• 0x0061, 0x0070 - 0x0071: NMI control I/O (I/O on the main board)
• 0xC140 - 0xC141: CPU thermometer I/O
Interrupts
• IRQ5 is used
Aside from hardware processing of the RAS board, this support software has the
following features:
3.1.2Function to Inform User of Interruption
This informs the user application program of the interruption signal.
The interruption signal is classified into the following two types.
• Maskable interruption: This becomes an interruption signal when it is registered
with the registry. The interruption No. is 5.
• Non-maskable interruption: WDT, Power Supply off, AC voltage decrease or System memory parity error/Multi-bit error becomes the interruption signal.
When the non-maskable interruption occurs, the automatic shutdown processing is done.
In the following cases, however, hardware resetting is done.
• When AC voltage decrease, system memory parity error/multi-bit error or PCI bus
system error was detected.
• When the non-maskable interruption continues for about 2 seconds or longer.
3
3.1.4RAS Information Processing Function
RAS information when starting, during operation, and when ending, is logged in the
WindowsNT event log. It is also possible to write in and read from the non-volatile
memory.
3.1.5Get DIP Switch State
This feature reads the ON/OFF state of the 4bit DIP switch installed on the front panel of
the equipment.
3.1.6LED Lighting Control
This software controls LED 0, which is installed as a standard provision, as follows:
Recovery from
abnormal condition
Temperature trouble
recovery
Fan stop recovery
Extingu
ished
Green
Red
RAS Service Start
Abnormality has
occurred
NMI has occurred
Temperature error
Fan stop
3.1.7Functions of RAS Software Processing
In addition to the hardware processing of the RAS board, this Support Software has RAS
window functions to display and set these RAS information, making it possible to monitor
and control the operatin status of the system.
Also, it has interfaces for user application programs, and it is possible to create user
application programs to cope with system abnormalities, etc. using the RAS function
processing commands or methods. By means of these user functions, it is possible to
construct systems with higher reliability.
34
model 2000/3000 Computer Module C2/C3 Windows NT Version
This Support Software is a program to operate unde r the Windo wsN T envir on men t, and
consists of the following 5 modules.
• RAS device driver
This device driver operates under the control of the I/O manager of WindowsNT
Executive, and it is a driver program to process access to the RAS board, interruption
from the RAS board, and request from the user application program.
• RAS service
Service program to perform processing of messages from the RAS device driver, event
log processing, and shutdown processing.
• RAS window
Window program to display the information of the RAS board and change the registry
information of the RAS Support Software.
• RAS Support Software DLL
Dynamic Link Library (DLL) to make interface between RAS device driver and user
The following shows the list of RAS support commands which can be used by the user
application programs (VC++, etc.). The following pages describes the syntax, argument,
returned value, and explanation for each command.
Command nameOutline
CreateFile (Win32)Open command
CloseHandle (Win32)Close command
XRasGetVersion RAS support software version reading command
XRasGetDriveErrorRAS driver error information reading command
XRasUserWindowRAS message receive window setting command
XRasUserMailslotRAS message receive mail slot setting command
XRasDlDigital signal input command
XRasDODigital signal output command
XRasDilntDI interruption setting command
XRasPowerLedPower LED indication command
XRasAlarmMemoryUser RAS memory reading command
XRasWriteMemoryUser RAS memory writing command
XRasReadSysMemorySystem RAS memory reading command
XRasWDTWDT setting command
XRasResetWDTUser WDT reset command
XRasUserShutdownUser shutdown command
XRasThermometerCPU temperature information reading command
XRasThermometerExCPU peripheral temperature information reading command
XRasBatteryBattery information reading command
XRasGetSwitchStatSwitch status Read
XRasGetHardwareRevisionHar-dware Revision Read
XRasSetLedMain Unit LED Control
XRasSetLedExMain Unit LED Control
36
The data types explained in the following sections are those defined by WindowsNT, and
for the application program, it is necessary to include windows.h and winioctl.h.
Since the data types, constants, etc. defined by the RAS Support Software are described
in xrasdll.h, the user application program must include this header file as well. For linking
the user application, it is necessary to link XRasDLL.lib (RAS DLL library). These
xrasdll.h and XRasDLL.lib exist under the directory specified when installing.
model 2000/3000 Computer Module C2/C3 Windows NT Version
• InzErrReg (registering error information)
This indicates that the information registered in the registry was an abnormal value.
If the registering was abnormal, bit to correspond to that information is set.
In such a case, the default value is used for the registered value for starting up.
The following shows the definition of bits to correspond to information.
IEREG_INTERRUPT Interruption No. abnormality error
IEREG_SERVICE Service shutdown diagnosis time abnormality bit
IEREG_USER User shutdown diagnosis time abnormality bit
IEREG_SHUTDOWN Shutdown execution diagnosis time abnormality bit
IEREG_SWDT System WDT abnormality bit
IEREG_HEALTHY Healthy signal abnormality bit
• InzErrAdr (converting erro r infor mation)
This indicates that the I/O address used by the RAS Support Software could not be
converted to the address controlled by WindowsNT.
If this error occurs, the RAS Support Software cannot normally operate and no
interruption processing is done (if Power key is turned, power is turned off).
What can be used is only the open, close, version reading, and driver error information
reading commands. The following shows the definition of bits to correspond to the
information.
IEADR_RAS 0x0140 to 0x016F converting disability bit
IEADR_SYSCON 0x0061 converting disability bit
IEADR_NMI 0x0070 to 0x0071 converting disability bit
IEADR_OPL 0x0178 to 0x017B or 0x0388 to 0x038B converting disability bit
IEADR_THM 0xC140 to 0x141 converting disability bit
• InzErrRes (resource error information)
This indicates that the hardware resource to be used by the RAS Support Software could
not be obtained.
This error, like the converting error, restricts the operation of the RAS Support Software.
The following shows the definition of bits to correspond to the information.
IERES_RES Hardware resource acquisition abnormality bit
IERES_SHUTDOWN Shutdown routine registering abnormality bit
• InzErrInt (interrupti on error information)
This indicates that the interruption handler of the RAS Support Software could not be
registered. This error , like the converting error, restricts the operation of the RAS Support
Software. The following shows the definition of bit to correspond to the information.
IEINT_CONNECT Interruption registering abnormality bit
• InzErrNmi (NMI error information)
This indicates that the NMI handler of the RAS Support Software could not be registered.
This error, like the converting error, restrics the operation of the RAS Support Software.
The following shows the definition of bit to correspond to the information.
IENMI_DESCRIPTOR NMI registering abnormality bit
42
model 2000/3000 Computer Module C2/C3 Windows NT Version
• RasAlive (RAS board error informati on )
This indicates if the RAS board is inserted. If the RAS board is inserted, TRUE is set, or if
it is not inserted, FAL SE is set.
This information becomes valid when InzErrAdr, InzErrRes, InzErrInt, and InzErrNmi are
normal. If the RAS board is not inserted, the operation of the RAS Support Software is
restricted, like the converting error.
• RasServ ic e (R AS service e r ro r information)
This indicates if the RAS service is started. If the RAS service is started, a value other
than 0 is set, or if it is started, 0 is set.
This information becomes valid when InzErrAdr, InzErrRes, InzErrInt, and InzErrNmi are
normal and the RAS board is inserted. If the RAS service is not started, the operation of
the RAS Support Software is restricted, like the converting error.
Xrasp_GetDriveError structure, Pxrasp_GetDriverError pointer type, and described
constant (IExxx_xxx) are defined in xrasdll.h.
hDeviceRAS driver open handle
hWndUser window handle
Returned value
If the command is normally completed, TRUE is returned. When error occurs, FALSE is
returned.
Explanation
Command for setting the user window to receive messages from the RAS Support
Software.
The following shows messages to be transmitted by the RAS Support Software.
Since WM_USER+ (RAS message ID : registered in registry) is used for the message to
be transmitted, operation to a window using this message ID cannot be guaranteed. In
such a case, the registering of the RAS message ID should be changed. For the window
set with this command, shutdown processing must be done when the NMI message is
received. For this reason, when the window is deleted, it is necessary to issue the
command with NULL set to the user window handle.
• Fan stop (wParam=RASMSG_FAN_STOP)
This is transmitted when the fan stop is detected.
• Fan recovery (wPa ram=RASMSG_FAN_STOP_RE COVER)
This is transmitted when recovery is made after fan stop is detected.
• Temperature abnormality (wParam=RASMSG_OVER_THERMO)
This is transmitted when temperature abnormality is detected.
• Temperature recovery (wParam=RASMSG_OVER_THERMO_RECOVER)
This is transmitted when recovery is made after temperature abnormality is
detected.
• DI change (wParam=RASMSG_DI0, RASMSG_DI1, RASMSG_DI2, RA SMSG_DI3)
RASMSG_DI2, RASMSG_DI3)
This is transmitted when DI change is detected.
44
model 2000/3000 Computer Module C2/C3 Windows NT Version
• Mirroring disk abnormality
(wParam=RASMSG_ILLEGAL_MIRRORDISK0,RASMSG_ILLEGAL_MIRRORDISK1)
This is transmitted when abnormality is detected when the mirroring disk is
connected.
• NMI occurrence (wParam=RASMSG_NMI)
This is transmitted when the first NMI is detected after the system starts up. NMI
factor is set to IParam.
31 5 4 3 2 1 0
IParam
Pow er K ey Off
Remot e Initializ e
WDT occurrence
After receiving this message, the user must do internal shutdown processing and issue
the user shutdown command (XRasUserShutdown) or the user power off command
(XRasUserPowerdown).
After NMI occurrence, the messages of fan stop/recovery, temperature abnormality/
recovery, DI change, and mirroring disk abnormality are not transmitted.
3.2.6RAS Message Receive Mail Slot Setting Command
Syntax
BOOLsts, flag;
HANDLE hDevice;
PHANDLElpMail;
sts = XRasUserMailslot( hDevice, flag, lpMail );
Argument
hDeviceRAS driver open handle
flagMail slot creating flag
lpMailAddress to buffer in which created mail slot handle is stored
Returned value
If the command is normally completed, TRUE is returned. When error occurs, FALSE is
returned.
Explanation
Like the RAS message receive window setting command, this command is to make
preparation for receiving messages from the RAS Support Software.
In the case of the RAS message receive wind ow setting co mma nd, the user application
program to receive the messages must be a window program, but if this command is
used, even a user application program not having such window handle as console
application can receive the messages.
By executing this command, the mail slot to receive messages from the RAS Support
Software is created/deleted.
If TRUE is set to the mail slot creating flag of the argument, the mail slot is created or if
FALSE is set, it is deleted.
To receive the message, firstly create the mail slot with this command and issue the
receive command of Win32 API (ReadFile) to the mail slot handle of the returned value.
Then when the user application receiving the message ends, issue this command and
delete the mail slot.
As the priority for transmitting the RAS messages, the RAS Support Software firstly
checks if there exists the mail slot created with this command.
If it exists, it transmits the messages only to the mail slot. If the mail slot does not exist,
then it checks if the receiving window exists. Thus, even if the receiving window is set,
the message is not transmitted to the receiving window if the receiving mail slot is set.
Like the RAS message receive window setting command, the application program set
with this command requires shutdown processing when the NMI message is received.
For this reason, when the application program ends, it is necessary to delete the mail slot
by issuing this command.
Message data which can be read by using the receive command (ReadFile) are 8 bytes
consisting of message ID and detailed data. They are stored in the buffer as shown
below.
46
model 2000/3000 Computer Module C2/C3 Windows NT Version
• Fan recovery (message ID : RASMSG FAN_STOP_RECOVER)
This is transmitted when recovery is made after fan stop is detected.
• Temperature abnormality (message ID : RASMSG_OVER_THERMO)
This is transmitted when temperature abnormality is detected.
• Temperature recovery (message ID : RASMSG_OVER_THERMO_RECOVER)
This is transmitted when recovery is made after temperature abnormality is
detected.
• DI change (message ID : RASMSG_DI0, RASMSG_DI1, RASMSG_DI2, RASMSG_
DI3)
This is transmitted when DI change is detected.
• NMI occurrence (message ID : RASMSG_NMI)
This is transmitted when the first NMI is detected after the system starts up. The
NMI factor is set to the detailed data portion. The following shows the content of
the detailed data portion.
3
31 5 4 3 2 1 0
De taile d data
Pow er Key Off
Remot e Initia lize
WDT occurre nce
After receiving this message, the user must do the internal shutdown processing and
issue the user shutdown command (XRasUserShutdown) or the user power off
command (XRasUserPowerdown).
After NMI occurrence, the messages of fan stop/recovery, temperature abnormality/
recovery, DI change, and mirroring disk abnormality are not transmitted.
hDeviceRAS driver open handle
lpDIAddress to the buffer in which the DI information is stored.
Returned value
If the command is normally completed, TRUE is returned. When error occurs, FALSE is
returned.
Explanation
Command to read the state of the digital input signal of the RAS board.
The following figure shows the contents of the DI information stored in the buffer.
48
model 2000/3000 Computer Module C2/C3 Windows NT Version
hDeviceRAS driver open handle
dwLedPower LED indication information
Returned value
If the command is normally completed, TRUE is returned. When error occurs, FALSE is
returned.
Explanation
Command to make green/red the indication color of LED on the front of equipment. The
following figure shows the contents of the LED indication information of the argument.
31
The indication may be used by the healthy signal of the RAS Support
Software, and in such a case, care must be taken. The indication when power is turned
on is green.
0
Indicat ion color (= 0: green, = 1: red)
50
model 2000/3000 Computer Module C2/C3 Windows NT Version
hDevice RAS driver open handle
dwAdr User RAS memory leading address
dwSize Number of bytes to be read
lpBuffer Address of buffer in which data read are stored
3.2 RAS Support Commands
3
Returned value
If the command is normally completed, TRUE is returned. When error occurs, FALSE is
returned.
Explanation
Command to read the data of the user RAS memory portion.
Since the RAS Support Software does not operate this user RAS memory, the user can
use it freely.
The following table shows the range of leading address and the range of the number of
bytes to be read of the argument.
The leading address + number of bytes to be read must not exceed the size of the user
hDevice RAS driver open handle
dwAdr Leading address of system RAS memory
dwSize Number of bytes to be written
lpBuffer Address of buffer in which data written are stored
Returned value
If the command is normally completed, TRUE is returned. When error occurs, FALSE is
returned.
Explanation
Command to read the data of the user RAS memory portion.
Since this system RAS memory is used by the RAS Support Software, no writing
can be done.
The leading address of the argument is in the range of 0 to 0xff, and the number of bytes
to be read must be specified within the range of 1 to 0x100.
The addresses 0xe0 to 0xff correspond to 0x00 to 0x1f of user RAS memory, and same
contents can be read.
The leading address + number of bytes to be read must not exceed 0x100.
52
model 2000/3000 Computer Module C2/C3 Windows NT Version
hDevice RAS driver open handle
dwAdr Leading address of system RAS memory
dwSize Number of bytes to be written
lpBuffer Address of buffer in which data written are stored
3.2 RAS Support Commands
3
Returned value
If the command is normally completed, TRUE is returned. When error occurs, FALSE is
returned.
Explanation
Command to read the data of the user RAS memory portion.
Since this system RAS memory is used by the RAS Support Software, no writing
can be done.
The leading address of the argument is in the range of 0 to 0xff, and the number of bytes
to be read must be specified within the range of 1 to 0x100.
The addresses 0xe0 to 0xff correspond to 0x00 to 0x1f of user RAS memory, and same
contents can be read.
The leading address + number of bytes to be read must not exceed 0x100.
hDevice RAS driver open handle
dwWDT WDT setting information
Returned value
If the command is normally completed, TRUE is returned. When error occurs, FALSE is
returned.
Explanation
Command to set Watchdog Timer (WDT).
The time can be set in the range of 524ms (set value1) to 2 minutes and 13 seconds (set
value255) in the units of 524ms. If the set value is 0, WDT is prohibited. WDT setting
cannot be done after NMI occurrence or after shutdown starting.
If the bit 15 of the WDT setting information is 0, the RAS Support Software automatically
reset the WDT by the timer interruption (500ms cycle), but if the bit 15 is 1, no resetting is
done by the RAS Support Software. In such a case, it is necessary for the user
application program to periodically issue the user WDT reset command to reset the WDT.
31 15
At the time of power on, user WDT registered in the registry is operating. In case a user
WDT which was previously registered in the registry is time out, WDT is disabled at the
time power is on.
7
0
WDT tim e
Resetting method(=1:us er re settin g)
54
model 2000/3000 Computer Module C2/C3 Windows NT Version
If the command is normally completed, TRUE is returned. When error occurs, FALSE is
returned.
Explanation
Command to instruct the RAS Support Software to execute the shutdown.
If the NMI occurrence message is received with the RAS message receive window
setting command (XRasUserWindow), the user application program must do its own
shutdown processing and issue this command or the user power off command
(XRasUserPowerdown).
When this command is issued, the RAS Support Software starts the shutdown of
WindowsNT. If this command was not issued with the NMI message despite the fact that
the user's window was set with the RAS message receive window setting
command, the shutdown of WindowsNT is automatically started assuming that this
command was issued, after the elapse of the user shutdown diagnosis time registered
with the registry.
56
model 2000/3000 Computer Module C2/C3 Windows NT Version
Page 71
3.2.15 CPU Temperature Information Reading Command
This software controls lighting of the 4bit LEDs of the main unit individually.
Parameters
hDeviceThe driver handle gotten by CreateFile.
dwStateSpecify the LED lighting status by the following format:
•
3•
1•7430
COL3 COL2COL1 COL0 LED3LED2LED1LED0
LED0 - Specify 1: LED0 lit, 0: extinguished
LED1 - Specify 1: LED1 lit, 0: extinguished
LED2 - Specify 1: LED2 lit, 0: extinguished
LED3 - Specify 1: LED3 lit, 0: extinguished
COL0 - Specify 1: LED0 color red, 0: green
COL1 - Specify 1: LED1 color red, 0: green
COL2 - Specify 1: LED2 color red, 0: green
COL3 - Specify 1: LED3 color red, 0: green
3.2 RAS Support Commands
3
dwMaskSpecify whether or not LED operation is required by the following mapping.
If "Specified," lighting of the LED is controlled in accordance with specification by
dwState.
If "Not specified," the state before this function is issued will be maintained regardless of
LED 0 can be controlled while the RAS service is in operation.
The difference with the xRASSetLed function is that this software can control individual LEDs.
For the RAS Support Software, it is necessary to register all the following registry
information (they are automatically registered by installing the RAS Support Software).
If the registered value of each entry of parameter is abnormal, it operates using the
default value.
3
3.3.1Registry information of RAS drive
Under ¥HKEY_LOCAL_MACHINE¥SYSTEM¥CurrentControlSet¥Service¥XRAS
registry key
Value entry nameTypeDefault value
ErrorControlREG_DWORD0x01
GroupREG_SZExtended Base
StartREG_DWORD0x02
TypeREG_DWORD0x01
VersionREG_SZVersion No. of this Support Software
Interruption No.InterruptREG_DWO RD0x05
Healthy signalHealthyDoREG_DWORD0x04
System WDTSystemWdtREG_DWORD60
User WDTUserWdtREG_DWORD0
Service shutdown diagnosis timeTimerServiceREG_DWORD60
User shutdown diagnosis timeTimerUserREG_DWORD360
Shutdown execution diagnosis time TimerShutdownREG_DWORD600
OptionOptionREG_DWORD0x00
3.3.2Registry information of RAS service
Under ¥HKE Y_LOCAL_MACHINE¥SYSTEM¥CurrentControlSet¥Service¥XRASService
registry key
Value entry nameTypeDefault value
DisplayNameREG_SZToshiba RAS Service
ErrorControlREG_DWORD0x01
ImagePathREG_EXPAND_SZ
ObjectNameREG_DWORDLocalSystem
GroupREG_SZExtended Base
StartREG_DWORD0x02
TypeREG_DWORD0x1 10
%SystemRoot%¥system32¥XRassrv.exe
64
model 2000/3000 Computer Module C2/C3 Windows NT Version
RAS service thread priorityServicePriorityREG_SZNormal
RAS message IDMessageIDREG_DWORD0x1000
RAS mail slot nameMailslotNameREG_SZXRASMSG
RAS mail slot receiving diagnosis
time
Forced shutdown diagnosis timeTimerForceShutdown REG_DWORD240
MailslotReadTimeOut REG_DWORD60000
3.3.3Registry information of RAS window
Under
¥HKEY_LOCAL_MACHINE¥SYSTEM¥CurrentControlSet¥Control¥XRASWindowregistry
key
NameValue entry nameTypeDefault value
RAS window start styleStartupREG_SZNormal
RAS window object nameObjectNameREG_SZXRASWINDOW
Normal window position (X)NormalPos.xREG_DWORD0
Normal window position (Y)NormalPos.yREG_DWORD0
Mini window display levelMiniLevelREG_SZTopMost
Mini window position (X)MiniPos.xREG_DWORD0
Mini window position (Y)MiniPos.yREG_DWORD0
RAS include file install pathInstPathIncludeREG_SZ(No default)
RAS library file install pathInstPathLibraryREG_SZ(No default)
3.3 RAS Support Software Registering
3
3.3.4System WDT(XRAS : SystemWdt)
This specifies the time of system WDT of the RAS Support Software.
After NMI occurrence, the RAS Support Software sets WDT to be reset with the RAS
service software, regardless of the present WDT state. This WDT is called system WDT.
Should the system WDT be set, the hardware will be reset, and so due care must be
taken. The following shows the setting range. The values are to be set in the units of
524ms.
2(1048ms) to 255(abt. 2 minutes) (Default value is 60 : abt. 30 seconds)
3.3.5Service Shutdown Diagnosis Time (XRAS : TimerService)
This specifies the diagnosis time of service in shutdown.
After NMI is detected, the RAS driver informs the RAS service of the NMI occurrence.
And the RAS service informs the RAS driver of the receiving. This period is called service
shutdown diagnosis time.
If the RAS service does not respond within this diagnosis time, it is judged that the RAS
service is unable to operate and the hardware will be reset, and so due care must be
taken when setting. The following shows the setting range. The values are to be set in
the units of 500ms.
2(1 second) to 1200(10 minutes) (Default value is 60 : 30 seconds)
3.3.6User Shutdown Diagnosis Time (XRAS : TimerUser)
This specifies the diagnosis time of the user in shutdown.
After NMI occurrence, the RAS Support Software sends the NMI occurrence message to
the user window set with the RAS message receiving window setting command
(XRasUserWindow). The user window receiving the message must do its internal
shutdown processing (data saving, etc.), issue the user shutdown command
(XRasUserShutdown), and instruct the RAS Support Software to shut down the
WindowsNT.
After the message is sent, the RAS Support Software monitors the time until the user
shutdown command is issued. This time is called user shutdown diagnosis time. If the
user shutdown command is not issued within this diagnosis time, it is judged that the user
window program is unable to operate, and the RAS Support Software shutdown
processing will proceed as if the user shutdown command was automatically issued. The
following shows the setting range. The values are to be set in the units of 500ms.
2(1 second) to 1200(10 minutes) (Default value is 360 : 3 minutes)
3.3.7Shutdown Execution Diagnosis Time (XRAS : TimerShutdown)
This specifies the diagnosis time in the shutdown of WindowsNT.
The RAS Support Software monitors the time from the start of WindowsNT shutdown
processing to the end of actual shutdown. This is called shutdown execution diagnosis
time.
If the shutdown is not completed within this diagnosis time, it is judged that the
WindowsNT is unable to operate, and the hardware is reset, and so due care must be
taken when setting. To make this diagnosis time invalid, set OxFFFFFFFF. This is
effective when it is desired to stop the system in the shutdown state (desired not to
reboot the system). (It can be utilize when the UPS function is used) The following shows
the setting range. The values are to be set in the units of 500ms.
2(1 second) to 1200(10 minutes) (Default value is 600 : 5 minutes)
3.3.8RAS Service Thread Priority (XRASService : ServicePriority)
This specifies the execution priority of the RAS service thread.
The values which can be set are shown below.
Set valuePriority
TimeCritical31
High26
Normal (default value)24
Low13
66
model 2000/3000 Computer Module C2/C3 Windows NT Version
This specifies the RAS message value to be sent to the user application program by the
RAS Support Software.
This value is added to WM_USER and informed to the window procedure of the user
application program. The following shows the setting range.
0 to 0x7BFF (Default value is 0x1000 : WM_USER+0x1000)
The above range is applied when WM_USER is 0x0400, and actually the total of
WM_USER and set value is to be in the range of 0x7FFF or lower.
The program designer of the window to receive the RAS message must set a window
message ID not used.
3.3.10 RAS Mail Slot Name (XRASService : MailslotName)
This specifies the name of the mail slot to be created with the RAS message receiving
mail slot setting command.
For the mail slot name to be specified here, a name not used by other program within the
system must be described.
As the default, the name XRASMSG is set.
3
3.3.11 RAS Mail Slot Receiving Diagnosis Time (XRASService :
MailslotReadTimeOut)
This specifies the diagnosis time of the receiving command (ReadFile) to the mail slot
created with the RAS message receiving mail slot setting command.
In case of time-out of the receiving command, the error information obtaining command
(GetLastError) returns ERROR_SEM_TIMEOUT.
The values are to be set in the units of ms, and as the default, 60000 (60 seconds) is set.
If 0 is set as the set value, the receiving command immediately ends if there is no
message. If the set value is 0xffffffff, it waits until the message is sent.
3.3.12 Forced Shutdown Diagnosis Time (XRASService :
TimerForceShutdown)
This specifies the diagnosis time in the forced shutdown of WindowsNT.
As the WindowsNT shutdown method, the RAS Support Software takes two steps.
Firstly, it tries to shut down the WindowsNT while informing the application of the
shutdown. If there exists any process which does not respond, the shutdown is
temporarily stopped (dialogue box is displayed and key input is waited for), leading to the
situation that a system of unmanned operation, etc. cannot normally complete the
shutdown. To avoid such a situation, the RAS Support Software provides the diagnosis
time, and at time-out, it forcefully shuts down the WindowsNT (forcefully ends the
application program).
This diagnosis time is called forced shutdown diagnosis time.
Since the shutdown execution diagnosis time (TimerShutdown) is started from the start of
the first shutdown, this forced shutdown diagnosis time must be set shorter than the
diagnosis time to make it effective. If the shutdown execution diagnosis time is shorter,
the equipment is reset before the forced shutdown is made.
If this diagnosis time is too short, the forced shutdown will be executed in the midst of
shutdown, and WindowsNT may not normally be shut down. For the detail, see the
restrictions of "3.4 RAS Shutdown Processing"
The following shows the setting range. The values are to be set in the units of 500ms.
2(1 second) to 1200 (10 minutes) (Default valve is 240 : 2 minutes)
This specifies the start style (normal window/mini window) of the RAS window.
Set valueStart style
Normal (default value)Normal window
MiniMini window
3
3.3.14 RAS Window Object Name (XRASWindow : ObjectName)
This specifies the object name of the object to be used for double start prevention by the
RAS window. The object name specified here must be a name not used by other
program within the system.
As the default, the name XRASWINDOW is set.
3.3.15 Normal Window Position (X) (XRASWindow : NormalPos.x)
This specifies the window position of X axis of the normal window.
The window position shown differs depending on the setting of the display.
The default value is 0, ultimate left side.
3.3.16 Normal Window Position (Y) (XRASWindow : NormalPos.y)
This specifies the window position of Y axis of the normal window. The default value is 0,
highest side.
3.3.17 Mini Window Display Level (XRASWindow : MiniLevel)
This specifies the display level of the mini window.
Set valueDisplay level
TopArranged at the highest level of Z sequence
TopMost (default value)Arranged always as the front window even when non-active
3.3.18 Mini Window Position (X) (XRASWindow : MiniPos.x)
This specifies the window position of X axis of the mini window. The default value is 0,
ultimate left side.
3.3.19 Mini Window Position (Y) (XRASWindow : MiniPos.y)
This specifies the window position of Y axis of the mini window. The default value is 0,
highest side.
3.3.20 RAS Include File Install Path (XRASWindow : InstPathInclude)
The path name which installed the include file (xrasdll.h) of the RAS Support Software is
recorded. This information is used when uninstalling is done.
RAS include file install path name : XRAS.BAS
68
model 2000/3000 Computer Module C2/C3 Windows NT Version
The path name which installed the library file (XRasDLL.lib) of the RAS Support Software
is recorded. This information is used when uninstalling is done.
3.3.22 Option (XRAS : Option)
This is a set value for future use, and 0 must be set.
The RAS Support Software has the function to automatically shut down the WindowsNT
when NMI (excluding voltage decrease system memory parity error/multi-bit error and
PCI bus system error) is detected.
The automatic shutdown operation differs depending on whether the user application
program is receiving the RAS messages with the RAS message receiving window setting
command (XRasUserWindow).
8 7
(1) NMI occurrence. The RAS driver sets the system WDT. If the NMI factor is system
memory parity error/multi-bit error, PCI bus system error or voltage decrease, the
information is left in the RAS memory and the hardware is reset.
(2) The RAS driver informs the RAS service of the NMI message. It starts to monitor the
service shutdown diagnosis time (TimerService).
(3) The RAS service informs the RAS driver that the NMI message was received. Then,
the RAS driver clears the service shutdown diagnosis time and starts to monitor the
user shutdown diagnosis time (TimerUser) if there is the RAS message receiving
user or the shutdown execution diagnosis time (TimerShutdown) if there is no user.
Also, the RAS service moves to the processing of [7] if there is no RAS message
receiving user.
(4) The RAS service informs the RAS message receiving user of the NMI occurrence
message.
(5) The RAS message receiving user performs post-processing in the program and
issues the user shutdown command (XRasUserShutdown) or the user power off
command (XRasUserPower dow n) .
(6) When the user shutdown command is issued or the user shutdown diagnosis time
time-out occurs, the RAS driver informs the RAS service of the shutdown execution
message. Also it starts to monitor the shutdown execution monitor time
(TimerShutdown).
(7) The RAS service executes the shutdown in the method to inform the application of
the shutdown. Also it starts to monitor the forced shutdown diagnosis time
(TimerForceShutdown).
(8) After the time-out of the forced shutdown diagnosis time, the shutdown is forcefully
done.
1
RAS driver
6 2 3 5
4
Us er applicat ion program RAS service
70
model 2000/3000 Computer Module C2/C3 Windows NT Version
3.4.2Restrictions on WindowsNT shutdown in the RAS Support
Software
(1) If the RAS Support Software is started and then stopped (uninstall, etc.), the power
cannot be turned off even if the power key is set to OFF.
This phenomenon is caused by temporarily setting the RAS board circuit. In case the
RAS support software is stopped, shut down Windows NT manually , then temporarily
turn the power off by switching off the power switch located on the backside. By this,
the power is turned off by switching off the switch beginning next operation.
(Windows NT is not shut down)
(2) If the forced shutdown functions and the shutdown is executed in the midst of the
shutdown processing of WindowsNT, the shutdown may not normally be executed.
With the RAS Support Software, the following RAS windows are prepared.
These windows are developed from the main window of the RAS window.
This makes it possible to process the RAS information display and RAS command
execution at the GUI level.
3
RAS windowDescription
Status windowWindow to display the information of RAS Support Software
DIO windowWindow for setting DI information display, DO output, and DI
interruption
WDT windowWindow to display present WDT state and set WDT
Alarm windowWindow to output alarm sound
RAS memory windowWindow for reading/writing of user RAS memory and displaying
system RAS memory
Event log windowWindow to display event information on RAS Support Software
Registry windowWindow to display and change registry information on RAS
Support Software
DI O windo w
WDT window Status wind ow
Main wind ow
Standard size Sm all size
Alarm wind ow
RAS m emory wind ow Event log win dow
Registry wind ow
72
model 2000/3000 Computer Module C2/C3 Windows NT Version
The main window is the basic window of the RAS window, and from this window,
development is made to various windows.
If the RAS board is not installed or RAS device driver is not installed, the buttons of DIO
window, WDT window, alarm window, and RAS memory window are made invalid, and
they cannot be opened.
If the desk top area is made smaller or font size is made larger, the whole of the RAS
window may not be displayed on the screen. In such a case, the whole of the window can
be checked by moving the window by selecting the movement of the system control
menu through the keyboard.
Menu
3.5 RAS Windows
3
Status window button
DIO window buttonn
WDT window button
larm test window
button
RAS window
end button
RAS memory
window button
Event log
window button
Registry window
button
Mini-window
button
• Menu
The menu consists of 3 items, [SELECT], [MINI WINDOW], and [Other], and each has
the following function.
[SELECT]
This menu item is to select a RAS window, and each window name is displayed, and by
selecting it, the specified window can be opened.
[MINI WINDOW]
This menu item is to set the operation of the mini window, and the following two items can
be checked.
No checkCheck
Highest level displayDisplay is made at the highest
level only when active
Mini window startMain window is displayed when
RAS window is started
6F8C0894
Always displayed at the highest
level
Mini window is displayed when
RAS window is started
The status window is to display the status information of the RAS Support Software.
By pressing the [REFRESH] button, the information displayed is updated.
For the operation environment item, the information of the present operation environment
is displayed.
If the RAS service is not started, "unknown" is displayed for the RAS service related
information (RAS service thread priority, RAS message ID, RAS mail slot name, RAS
mail slot receiving diagnosis time, forced shutdown diagnosis time) or if the RAS driver is
not started, "unknown" is displayed for all the information.
Display itemContent
Interruption No.Interruption No. used by RAS board is displayed.
Healthy detection meansHealthy signal output means of RAS Support Software
Driver related
System WDT timeSet value of each time and actual time
User WDT time
Service shutdown diagnosis time
are displayed.
User shutdown diagnosis time
Shutdown execution diagnos is
time
RAS service thread priorityPriority of RAS service thread is displayed
RAS message IDWindow message ID used in RAS message informing
Service related
RAS mail slot nameMail slot name used for RAS mail slot is displayed
RAS mail slot receiving diagnosis
time
Forced shutdown diagnosis timeSet value of forced shutdow n diagno sis time and actua l
3.5 RAS Windows
3
is displayed.
is displayed.
RAS mail slot receiving diagnosis time is displayed. If
the receiving diagnosis time is infinite, "FOREVER" is
displayed.
time are displayed.
3.5.7DIO Window
The DIO Window processes LED 0 display settings on the GUI level. The other features
are for extension and have no meanings.
WDT window can process at the GUI level the setting of WDT supported by the RAS
Support Software. When the WDT window is opened, the present set information is
displayed.
If the RAS board is not installed or RAS device driver is not installed, the main window
and mini window buttons are made invalid and this window cannot be opened.
Reset selection
button
WDT count
WDT time
• Reset select button
Button to select the resetting method of WDT. Either system reset or user reset is
selected.
• WDT count
Item to set the count value of WDT. It can be set in the range of 2 to 255 counts (1
count = 524ms). If 0 is set, WDT is prohibited.
• WDT time
The time of the WDT count set is displayed. If WDT is prohibited, nothing is displayed.
• Set button
By pressing the set button, the WDT information set with the reset select button and
WDT count is actually set.
• Reset button
This is valid only when the WDT resetting method is the user reset, and by pressing
this button, WDT resetting can be done.
3.5 RAS Windows
3
Setting button
Reset button
3.5.10 Alarm Window
The buttons of the main and mini windows are made invalid.
The RAS memory window can process at the GUI level the reading/writing of the user
RAS memory and reading of the system RAS memory supported by the RAS Support
Software.
If the RAS board is not installed or the RAS device driver is not installed, the main
window and mini window buttons are made invalid and this window cannot be opened.
If the extended RAS memory functions (Operating Time Monitoring, Thermometer Trend,
and NMI Trigger Information) are being executed, the area in the extended memory
which is available to the user becomes smaller.
• System RAS memory
000h to 0DFh of the system RAS memory are displayed. 0E0h - 0FFh are omitted
because of the user RAS memory.
82
model 2000/3000 Computer Module C2/C3 Windows NT Version
• User RAS memory
User RAS memory is displayed. They correspond to 0E0h - 0FFh of the system RAS
memory.
• Refresh button
By pressing the refresh button, the display is updated to the display of the newest RAS
memory information.
• Extension memory button
With a system supporting the extension RAS memory, the extension portion of the
user RAS memory can be displayed/edited by pressing the extension memory button.
With a system not supporting the extension RAS memory, the button is made invalid
and clicking cannot be done.
• User memory correction button
By pressing the user memory correction button, the window for writing the user RAS
memory is displayed and the user RAS memory can be changed.
3
Write selection
ddress selection
Present value
Byte data
Batch write data
Write button
• Write select
Button to select writing method of the user RAS memory. Either batch writing or byteunit writing is selected.
• Batch data
If writing is done in the user RAS memory by the batch writing method, the data of all
the user RAS memories can be written at once by entering the data in this area and
pressing the write button.
• Address select
When writing is done in the user RAS memory using the byte-unit writing method, the
address of the target user RAS memory is entered in this item.
• Byte data
When writing is done in the user RAS memory using the byte-unit writing method, the
data to be written is entered in this item and the write button is pressed, and then the
data are actually written in the user RAS memory.
• Present value
When writing is done in the user RAS memory using the byte-unit writing method, the
value presently written in the user RAS memory selected with the address select.
• Write button
By pressing the write button, the input data are written in the user RAS memory.
84
model 2000/3000 Computer Module C2/C3 Windows NT Version
The event log window displays the event log information logged by the RAS Support
Software. In this window, maximum 256 events are displayed. More old events can be
checked through the event viewer.
Event log information
3.5 RAS Windows
3
Refresh button
3.5.13 Refresh button
By pressing the refresh button, the display of the event log window is updated to the
newest information.
The event log information logged by the RAS Support Software is displayed sequentially
from the newest information. By double-clicking on each event of the event log
information with the mouse, the detailed information of the event is displayed.
3
Computer name
Previous event button Event data
• Date
Date of this event log logged is displayed.
• Time
Time of this event log logged is displayed.
• Computer name
The computer name which logged this event log is displayed.
• Event ID
The event message identifier of the RAS Support Software is displayed.
• Event source
The indentifier of the event log logged by the RAS Support Software is displayed.
• Event type
The type (information/warning/error) of this event is displayed.
• Event explanation
The explanation of this event log is displayed.
• Event data
Data attached to this event log are displayed.
• Preceding event button
For moving to a newer event than this event log.
• Next event log
For moving to an older event than this event log.
• Event count
The count value of the event log displayed in this window is displayed.
In case of 1/256 display, there are 256 events in total, and of them, the newest event is
displayed.
Time
Date
Next event button Event count
Event description
Event type Event ID
Event source
86
model 2000/3000 Computer Module C2/C3 Windows NT Version
Loading...
+ 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.