5
SETTINGS AND PROCEDURES BEFORE OPERATION
5.7 Battery Specifications, Installation and Replacement
5.7.3 Replacing battery
5 - 33
1
OVERVIEW
2
SYSTEM
CONFIGURATION
3
SPECIFICATIONS
4
FUNCTIONS
5
SETTING AND
PROCEDURES
6
I/O NUMBER
ASSIGNMENT
7
MEMORIES AND
FILES
8
INSTALLING /
UNINSTALLING
(b) When a battery error has occurred
*1
1) The ERR. LED turns on, indicating that a battery error (error code: 1600,
BATERY ERROR) has occurred.
The error code can be checked on the <<Module information>> tab of the C
Controller setting utility.
2) The data of the date and time, event No. (0xC000020E), and battery error
(error code: 1600, BATERY ERROR) are added to the event history.
The event history can be confirmed on the <<Event history>> tab of the C
Controller setting utility.
3) By calling the QBF_ReadStatusEx function from the user program, the LED
information, presence of a battery error can be checked.
* 1 Occurrence of a battery error will not change the CPU operation status. (If the CPU was in the
RUN status, the module remains in the RUN status.)
Even if a battery error occurs, data of the standard ROM and battery-backed-up RAM files are not
cleared immediately.
However, if the battery is not replaced within the guaranteed time indicated in this section (2) after
the error occurrence, data of the standard ROM and battery-backed-up RAM files may be erased.
(c) Battery replacement
Replace the battery within the guaranteed time after battery error occurrence.
(
this section (2))
For creating a battery error detection program, use the QBF_Y_Out_BitEx
function to turn on any output (Y) when detecting a battery error by the
QBF_ReadStatusEx function.