Appendix 2 How to Use User ROM Card with

the MICREX-SX SPH300

Page
Appendix 2 How to Use User ROM Card with the MICREX-SX SPH300 ............... App.2-1
1. Introduction .......................................................................................................................... App.2-1
2. How to offline download data to U_ROM ............................................................................. App.2-3
3. How to offline modify a project stored in a U_ROM ............................................................. App.2-3
4. How to online modify a program stored in a U_ROM .......................................................... App.2-5
 Appendix 2 How to Use User ROM Card with the
MICREX-SX SPH300
Appendix 2 How to Use User ROM Card with
the MICREX-SX SPH300
MICREX-SX NP1PS-32R/74R/117R can transfer and save a project of zipped executable program, source program, comment,
variable names, etc. (hereinafter called zipped project) of PLC as well as executable program to a user ROM card. In addition,
even when the CPU module is running, it is possible to upload them or download only zipped project.
This appendix explains how to download or upload programs to or from a user ROM card. Hereinafter user ROM card is
referred to as “U_ROM”.

1. Introduction
1) Appearance of CPU module
2) Key switch
8) User Rom 1) Status indication LED
card (option) UROM
RUN ONL
ERR
UROM
3) CPU No.
User ROM card RUN
ALM
setting switch
STOP BAT
connector cover TERM
Specification plate
CPU
No. (on the right side panel of module)
User ROM card
LOADER
eject button
4) Loader connector
Loader connector
cover
7) Version seal
5) USB connector
(loader connector)

6) Data backup USB connector

battery cover

Battery
connector Battery cover

U_ROM is disabled when the key switch is set to a position other than “UROM”.
U_ROM can be mounted and removed, whether the CPU is running or stopped. Before mounting or removing U_ROM, be
sure to check that the key switch is set to “UROM” and that the “UROM” LED is unlit.
It is possible to offline upload or download executable program and/or zipped project to or from a U_ROM. “Offline” here
means the operation with a U_ROM that is mounted in the PC card slot or CF card reader of a personal computer in which
Expert (D300win) is installed. On the other hand, “online” means the operation with a U_ROM that is mounted on the CPU
module.
2) Preparation for using U_ROM online (proceed to 3) when U_ROM is used offline)
U_ROM needs to be initialized when it is used for the first time. For initialization, it is mounted on the CPU module.
1) Turn OFF the power supply to the CPU module.
2) Mount the U_ROM on the CPU module.
3) Set the key switch to “UROM”.
4) Turn the power supply ON, and the CPU module will recognize the U_ROM. (The “UROM” LED lights up.)

Then, the CPU module come in “fatal failure” condition (the ONL LED as well as the ALM LED lights up), which, however,
is the correct response when a U_ROM that is not yet initialized is mounted. The following are displayed on the [Failure
diagnosis] dialog box and the [Detail RAS] dialog box:
Fatal failure CPU module memory error (*)
User program saving ROM error (*)
ROM error
User ROM directory structure error

App.2-1
Appendix 2 How to Use User ROM Card with
the MICREX-SX SPH300

5) When [Resource initialization] is executed from Expert (D300win), the CPU module is initialized. At the same time, the
U_ROM is also initialized. (When the executable programs and data that you don’t want to delete are stored in the CPU
module, make their backup files in advance with SX control utility.)

Preparation for using U_ROM offline

[Caution] The format of U_ROM that can be recognized by the CPU module is only “FAT”. Neither “FAT32” nor “NTFS” can
be recognized by the CPU module. U_ROMs formatted by WindowsXP can be recognized only by the CPU module with
V59 or later software version. If a U_ROM with 32MB or greater memory capacity is formatted by WindowsXP, FAT32 is
selected as standard. So, it is necessary to change the selection to “FAT” before formatting is started.

Mount a U_ROM in your personal computer and check the drive in advance.
Menu for dealing with U_ROM on Expert (D300win)

To initialize a U_ROM that is used for the first time, see the following figure.

Drive name of personal

computer in which the
U_ROM is inserted

App.2-2
 Appendix 2 How to Use User ROM Card with
the MICREX-SX SPH300

2. How to offline download data to U_ROM

This paragraph explains the method for offline download.
For online download, when ordinary download to the CPU module is performed, the data is downloaded not only to the CPU
module but also to the U_ROM. (Zipped project, however, is downloaded only to the U_ROM.)
1) Download to U_ROM after making, compiling and checking a program.

Drive name of personal

computer in which the
U_ROM is inserted

Select the
CPU module.

Select all items

3. How to offline modify a project stored in a U_ROM

1) Upload the project from the U_ROM
Note: If a project of the same name already exists in specified folder of the personal computer, it will be overwritten (a
confirmation message for overwriting is displayed.).

Drive name of personal

computer in which the
U_ROM is inserted

Specify a folder on the

personal computer side
to transfer the data.

Check the
project name.

When uploading is completed successfully

App.2-3
 Appendix 2 How to Use User ROM Card with
the MICREX-SX SPH300

2) Program modification
When the retain area continues being used or when the “variable name linkage” function is used with POD, etc., it is possible to
set such that previous values continue to be used for the addresses of already existing variables.

3) Download to U_ROM after compiling and checking the program

Drive name of personal

computer in which the
U_ROM is inserted

Select all items

4) With the power supply to the CPU turned OFF, operate as follows:
Remove the U_ROM from the personal computer, and mount it on the CPU module.
Set the key switch to “UROM”.
When the power is turned ON, the modified program is executed (see notes 1 and 2).
(When the power is turned once OFF and then ON again, the content of the U_ROM is transferred to the CPU module, and the
program is executed. If the content of the U_ROM coincides with that of the CPU module, no data is transferred.)
Notes: 1) In the following cases, the retain memory is initialized. When mechanical adjustment data and other important data
are stored in the retain memory, make backup files of the retain memory data with SX control utility and recover the
backup data after the user ROM starts running.
• When a U_ROM that is only formatted by Expert (D300win) and has no project is mounted
• When a U_ROM that is written a project whose memory allocation was changed with the [Memory allocation
setting…] function is mounted
2) If the program stored in the CPU does not coincide with the content of the U_ROM, the program stored in the
U_ROM is converted and transferred to the CPU. Here, it takes ordinary startup time plus several minutes (30
seconds for 32k steps to 90 seconds for 117K steps and additional 60 seconds when memory optimization is
necessary) for the CPU to start up. With multi-CPU system, disconnection is detected on the CPUs that start up
late, but the system can started normally when the power is turned once OFF and then ON again after all the CPUs
are started.

App.2-4
 Appendix 2 How to Use User ROM Card with
the MICREX-SX SPH300

4. How to online modify a program stored in a U_ROM

It takes much time in zipping and downloading when zipped project is downloaded each time a POU is changed. Therefore, in
this paragraph, the method for downloading zipped project at the end of operation is explained.
Because a zipped project is large in volume and requires much time for downloading, it is recommended to use the Ethernet or
USB port having high transmission rate.
1) Uploading of project
* This can be made during operation.

Specify a folder to unzip.

Notes: 1) If unzipped in the same project, existing project is overwritten.

2) If a library of the same name as that existing in the U_ROM exists in
the library folder of the personal computer, a confirmation message for
overwriting is displayed. You can unzip the project without overwriting.
The figure at right shows the screen when uploading is completed
successfully.

2) On the [Configuration setting of MICREX-SX] dialog box, operate as follows in advance.

Uncheck this box.

Note: With this setting, online change does not cause to download zipped project.

App.2-5
 Appendix 2 How to Use User ROM Card with
the MICREX-SX SPH300

3) Download only the program while a program is modified or checked

When there is a change in the system structure definition, check also the [System definition] box.

4) Download zipped project to U_ROM at the end of modification or checking

* Download is possible also when the CPU is running.

[Reference] Required time for project upload/download

Size of project Number of program steps: 8.5k
Zipped project: approx. 1M bytes
Via COM port (RS-232C): approx. 6 minutes
Via Ethernet or USB port: approx. 1 minute to 1 minute 30 seconds

App.2-6
 Appendix 3 CPU System Memory

page
Appendix 3 CPU System Memory ............................................................................ App.3-1
(1) Resource operating status %MW10.0 (read-only) ........................................................................ App.3-1
(2) Resource switch/user ROM status %MW10.1 (read-only) ............................................................ App.3-2
(3) Resource fatal failure factor %MW10.2 (read-only) ...................................................................... App.3-2
(4) Resource nonfatal failure factor %MW10.4 (read-only) ................................................................ App.3-3
(5) CPU error factor %MW10.6 (read-only) ........................................................................................ App.3-3
(6) Memory error factor %MW10.8, %MW10.9 (read-only) ................................................................ App.3-4
(7) SX bus error factor %MW10.10, %MW10.11 ................................................................................ App.3-4
(8) Application error factor %MW10.12, %MW10.13 (read-only) ....................................................... App.3-5
(9) User fatal failure %MW10.14 to %MW10.16 ................................................................................. App.3-5
(10) User nonfatal failure %MW10.18 to %MW10.20 ......................................................................... App.3-5
(11) System definition error factor %MW10.22 to %MW10.29 (read-only) ........................................ App.3-6
(12) Application program error factor %MW10.38, %MW10.39 ......................................................... App.3-8
 Appendix 3 CPU System Memory
Appendix 3 CPU System Memory

(1) Resource operating status %MW10.0 (read-only)

Indicates the operating status and mode of resource (CPU module)
SPH SPH
Address Name Description 300 200

%MX10.0.0 Running Set ON while the CPU is running.

%MX10.0.1 Stop Set ON while the CPU is down.
%MX10.0.2 Fatal failure Set ON when a fatal resource error occurred.
%MX10.0.3 Nonfatal failure Set ON when a nonfatal resource error occurred.
%MX10.0.4 Redundancy / Working Set ON when the CPU is specified as "Working" CPU of a redundant ---
system.
%MX10.0.5 Redundancy / Standby Set ON when the CPU is specified as "Standby" CPU of a redundant ---
system.
%MX10.0.6 1:1 redundancy Set ON when the system is in 1:1 redundant mode. ---
%MX10.0.7 N:1 redundancy Set ON when the system is in N:1 redundant mode. ---
%MX10.0.8 Non-automatic operation Set ON while in non-automatic operation mode.
mode
%MX10.0.9 Automatic operation mode Set ON while in automatic operation mode.
%MX10.0.10 Preceding state mode Set ON while in preceding state mode.
%MX10.0.11 Battery less run mode Set ON while in battery less run mode.
%MX10.0.12 Not used --- ---
%MX10.0.13 SX bus-connected module Set ON when all the modules that are directly connected to the SX
Note) fail-soft mode bus are adapted to fail-soft operation and individual resetting.
%MX10.0.14 Processor bus master Set ON when the CPU module is controlling the processor bus.
%MX10.0.15 SX bus master Set ON when the CPU module is controlling the SX bus.
: Supported, --- : Not supported

Non-automatic operation mode

In this mode, the CPU does not start running even when the system power is turned ON with the key switch on the CPU
module front panel set to “RUN” or “TERM”. This mode is set by “Running specification at power on” of [Resource setting of
MIC…] dialog box. For SPS, this mode is activated when there is no boot project.
Automatic operation mode
In this mode, the CPU starts running when the system power is turned ON with the key switch on the CPU module front panel
set to “RUN” or “TERM”. This mode is set by “Running specification at power on” of [Resource setting of MIC…] dialog box.
(Default is “automatic operation” mode.) For SPS, this mode is activated when there is a boot project.
Preceding state mode
In this mode, the CPU starts running when the system power is turned ON with the key switch on the CPU module front panel
set to “RUN”, or the CPU comes in the state (running or stopped) that had been taking effect just before the power was last
turned OFF when the system power is turned ON with the key switch set to “TERM”.
Battery less run mode
In this mode, all memories are initialized to their initial values or zero when the system power is turned ON. Neither battery
connection check nor battery voltage check is made in this mode. This mode is set by “Running specification at power on” of
[Resource setting of MIC…] dialog box. When both battery less run mode and preceding state mode are activated, automatic
operation mode is enabled.
For standard CPU, battery less run mode is not enabled unless a user ROM card is inserted,

Note: <When %MX10.0.13=0 (Fail-soft operation mode is disabled for the modules on the SX bus>
For common modules, fail-soft operation is not performed; for SX bus directly connected I/O modules, fail-soft operation
is not performed even when enabled from the loader (Expert (D300win)).
<When %MX10.0.13=1 (Fail-soft operation mode is enabled for the modules on the SX bus>
For common modules, fail-soft operation is performed; for SX bus directly connected I/O modules, fail-soft operation is
performed according to the fail-soft operation setting made from the loader (Expert (D300win)).

App.3-1
Appendix 3 CPU System Memory

(2) Resource switch/user ROM status %MW10.1 (read-only)

This area indicates the status of the CPU module switches that control the resources.
SPH SPH
Address Name Description 300 200

%MX10.1.0 CPU number Indicates the 4-bit number (0 to F) that is set with the CPU No. setting
| switch on the CPU module front panel. However, the setting range of ---
%MX10.1.3 CPU module is 0 to 7.
%MX10.1.4 Not used --- ---
%MX10.1.5
%MX10.1.6 User ROM card mounting 1: Mounted, 0: Not mounted
condition Note 1

%MX10.1.7 User ROM card write protect 1: Write protected, 0: Write permitted (enabled when %MX10.1.6=1)
Note 1

%MX10.1.8 STOP position Set ON when the key switch is set to STOP.
%MX10.1.9 TERM position (lower) Set ON when the key switch is set to TERM (lower).
%MX10.1.10 TERM position (upper) Set ON when the key switch is set to TERM (upper).
(see notes 2 and 3)
%MX10.1.11 RUN position Set ON when the key switch is set to RUN.
%MX10.1.12 Not used
| --- ---
%MX10.1.15

Notes: 1) Applicable only to user ROM card (compact flash card) adapted models.
2) The TERM position flag is set ON also when the key switch is unfixed.
3) For user ROM card adapted high-performance CPU modules, this flag is set ON when the key switch is set to
UR8M_TERM.
(3) Resource fatal failure factor %MW10.2 (read-only)
This area indicates the failure factors that cause to stop the resource (one-CPU system).
SPH SPH
Address Name Description 300 200

%MX10.2.0 CPU error Set ON when a fatal failure occurs on the local CPU module.
%MX10.2.1 Power supply error Set ON when power-off occurs.
%MX10.2.2 Memory error Set ON when an error occurs on the local CPU module internal memory.
%MX10.2.3 SX bus error Set ON when SX bus error occurs, such as disconnection of cable or
loop-back plug.
%MX10.2.4 Application error Set ON when an error is found in application program or system definition.
%MX10.2.5 I/O module error Set ON if an I/O module under control of the local CPU module fails
when fail-soft operation mode is disabled.
When fail-soft operation mode is enabled for the failed I/O module, the
entire system continues to run.
%MX10.2.6 Common module error Set ON when a common module on the SX bus other than the local
CPU module fails.
%MX10.2.7 Redundancy relay switching Set ON if fails to switch over to the standby module while running in ---
error redundant operation mode.
%MX10.2.8 Not used --- ---
%MX10.2.9
%MX10.2.10 Remote I/O module error for Set ON when the system becomes down due to a failure of remote --- ---
remote I/O master board I/O unit or module.
%MX10.2.11 Driver error --- ---
%MX10.2.12 Not used --- ---
%MX10.2.13 Other hardware error Set ON when the CPU No. setting switch is abnormal.
%MX10.2.14 Not used --- ---
%MX10.2.15 User fatal failure Set ON when one bit of the user fatal failure flags (%MX10.14.0 to
%MX10.16.15) is set ON by application program.

App.3-2
 Appendix 3 CPU System Memory

(4) Resource nonfatal failure factor %MW10.4 (read-only)

This area indicates the failure factors that allow the resource to continue running.
SPH SPH
Address Name Description 300 200

%MX10.4.0 Not used --- ---

%MX10.4.1
%MX10.4.2 Memory error Set ON when an error occurs on the local CPU module internal memory.
%MX10.4.3 SX bus error Set ON when an error occurs on the SX bus.
%MX10.4.4 Application error Set ON when an error is found in application program or system definition.
%MX10.4.5 I/O module error Set ON if an I/O module under control of the local CPU module fails when
fail-soft operation mode is enabled. (See note.)
%MX10.4.6 Common module error Set ON when a common module on the SX bus other than the local CPU
(see note) module fails.
%MX10.4.7 Not used --- ---
|
%MX10.4.9
%MX10.4.10 Remote I/O module error Set ON when an error occurs on a remote I/O module or unit. --- ---
For SPS, the system becomes down because fail-soft operation is not
supported.
%MX10.4.11 Not used --- ---
%MX10.4.12 User ROM card - CPU Set ON when the content of user ROM card does not coincide with that ---
Note
mismatch of the CPU internal memory.
The contents to compare are system definition, project, password, etc.
%MX10.4.13 Other hardware error Set ON when the key switch or the loader/general-purpose
communication changeover switch is abnormal.
The CPU module operates by assuming that "TERM" be enabled if the
key switch is abnormal or assuming that loader side be selected if the
loader/general-purpose communication changeover switch is abnormal.
%MX10.4.14 Battery error Set ON when the data backup battery voltage drops too low or the battery
is dead.
%MX10.4.15 User nonfatal failure Set ON when one bit of the user nonfatal failure flags
(%MX10.18.0 to %MX10.20.15) is set ON by application program.

Note: Applicable only to user ROM card (compact flash card) adapted models.
* Common modules are those directly connected to the SX bus without occupying an I/O area (CPU module,
communication module, etc.)

(5) CPU error factor %MW10.6 (read-only)

Address Name Description

%MX10.6.0 Arithmetic processor error Hardware error of arithmetic LSI in the CPU module
%MX10.6.1 OS processor error Hardware error of OS control LSI in the CPU module
%MX10.6.2 Not used
|
%MX10.6.15

App.3-3
Appendix 3 CPU System Memory

(6) Memory error factor %MW10.8, %MW10.9 (read-only)

Address Name Description Level

%MX10.8.0 System ROM error Set ON when an error occurs on the system ROM in the CPU module. Fatal failure
%MX10.8.1 System RAM error Set ON when an error occurs on the system RAM in the CPU module. Fatal failure
%MX10.8.2 Application ROM error Set ON when an error occurs on the application program ROM in the Fatal failure
CPU module. See note 1.
%MX10.8.3 Application RAM error Set ON when an error occurs on the application program RAM in the Fatal failure
CPU module.
%MX10.8.4 Not used
|
%MX10.8.14
%MX10.8.15 Memory backup error Set ON when no data is stored in the power-failure data retain memory. Fatal failure
See note 2.
%MX10.9.0 Not used
|
%MX10.9.14
%MX10.9.15 Memory backup error Set ON when no data is stored in the power-failure data retain memory. Nonfatal failure
Can be set OFF by application program. See note 2.

Notes: 1) Set ON also when an error occurs on the user ROM card.
2) For high-performance CPUs, which bit is set ON in case of memory backup error depends module version.
V**.25 or older: %MX10.8.15 is set ON, V10.30 or later: %MX10.9.15 is set ON.
Operation after the occurrence of memory error
In case of memory backup error, the entire user memory area is cleared to zero. However, in case %MX10.8.0 to 3 is set ON,
because of high probability of hardware failure, it is highly probable that the fatal failure recur due to memory error even when
the power is turned once OFF and then ON again.
(7) SX bus error factor %MW10.10, %MW10.11
SPH SPH
Address Name Description Level 300 200

%MX10.10.0 SX bus LSI error Set ON when an error occurs on the SX bus control LSI. Fatal failure
%MX10.10.1 Duplicate station No. Set ON when there are multiple modules having the same SX bus Fatal failure
station No. in one configuration.
%MX10.10.2 Connected module Set ON when the number of modules connected to the SX bus Fatal failure
count over exceeds 254.
%MX10.10.3 Not used --- ---
|
%MX10.10.12
%MX10.10.13 SX bus transmission Set ON when a transmission error occurs on the SX bus. Fatal failure
error
%MX10.10.14 Processor bus access Set ON when an error occurs in accessing the processor bus. Fatal failure
error (When access error factor exists on the local module)
%MX10.10.15 I/O refresh slow-down Set ON when input/output data is not updated via the SX bus for Fatal failure
128 ms or longer time.
%MX10.11.0 Not used --- ---
|
%MX10.11.13
%MX10.11.14 Processor bus access Set ON when an error occurs in accessing the processor bus. Fatal failure
error (When access error factor exists on the remote module)
Can be set OFF by application program.
%MX10.11.15 Not used --- ---

App.3-4
 Appendix 3 CPU System Memory

(8) Application error factor %MW10.12, %MW10.13 (read-only)

SPH SPH
Address Name Description Level 300 200

%MX10.12.0 System definition error Set ON when an error is found in the system definition. Fatal failure
%MX10.12.1 Application program Set ON when an error is found in the application program. Fatal failure
error
%MX10.12.2 Not used --- ---
|
%MX10.12.15
%MX10.13.0 Not used --- ---
%MX10.13.1 Application program Set ON when an error is found in the application program. Nonfatal
error failure
%MX10.13.2 Not used --- ---
|
%MX10.13.15

(9) User fatal failure %MW10.14 to %MW10.16

SPH SPH
Address Name Description 300 200

%MX10.14.0 User fatal failure factor 0 If one of these bits is set ON by application program, the CPU becomes
| | down due to fatal failure.

%MX10.14.15 User fatal failure factor 15

%MX10.15.0 User fatal failure factor 16
| |
%MX10.15.15 User fatal failure factor 31
%MX10.16.0 User fatal failure factor 32
| |
%MX10.16.15 User fatal failure factor 47

(10) User nonfatal failure %MW10.18 to %MW10.20

SPH SPH
Address Name Description 300 200

%MX10.18.0 User nonfatal failure factor 0

If one of these bits is set ON by application program, the CPU comes in
| | nonfatal failure condition but continues running.
When the status of the bit is changed from ON to OFF by application
%MX10.18.15 User nonfatal failure factor 15 program, the CPU recovers from nonfatal failure condition.
%MX10.19.0 User nonfatal failure factor 16
| |
%MX10.19.15 User nonfatal failure factor 31
%MX10.20.0 User nonfatal failure factor 32
| |
%MX10.20.15 User nonfatal failure factor 47

App.3-5
Appendix 3 CPU System Memory

(11) System definition error factor %MW10.22 to %MW10.29 (read-only)

SPH SPH
Address Name Description Level 300 200

%MX10.22.0 Not used --- ---

%MX10.22.1 System structure Set ON when the content of the system structure definition stored Fatal failure
definition error in the CPU module does not coincide with real system structure.
%MX10.22.2 System running Set ON when tact period is set to 0.5 ms for the system in which Fatal failure
definition error multiple common modules are connected in one configuration or
which uses standard CPU.
%MX10.22.3 System DO setting Set ON when the SX bus directly connected module for which Fatal failure
error system DO (output) is set is not a digital output module.
%MX10.22.4 Redundancy setting Set ON when there is a memory copy range setting error in the Fatal failure ---
error system redundancy definition.
%MX10.22.5 Fail-soft start up mode Set ON if fail-soft start up is enabled when there is no module Fatal failure
selection error adapted to fail-soft operation in the system.
%MX10.22.6 Not used --- ---
|
%MX10.22.9
%MX10.22.10 CPU running definition Set ON when the CPU No. set in the system structure definition Fatal failure
error does not coincide with the switch setting on the CPU module.
%MX10.22.11 CPU memory boundary Set ON when the memory space used by application program Fatal failure
definition error exceeds the total memory capacity.
%MX10.22.12 Not used --- ---
|
%MX10.22.15
%MX10.23.0 CPU I/O group definition Set ON when an input module is defined as output. Fatal failure
error (for default tasks)
%MX10.23.1 CPU I/O group definition
error (for level 0 tasks)
%MX10.23.2 CPU I/O group definition
error (for level 1 tasks)
%MX10.23.3 CPU I/O group definition
error (for level 2 tasks)
%MX10.23.4 CPU I/O group definition
error (for level 3 tasks)
%MX10.23.5 Direct I/O fail-soft Set ON when an error is found in the fail-soft operation setting for Fatal failure
definition error direct I/O.
%MX10.23.6 Remote I/O master 0 Set ON when an error is found in the fail-soft operation setting. Fatal failure
fail-soft definition error
%MX10.23.7 Remote I/O master 1
fail-soft definition error
%MX10.23.8 Remote I/O master 2
fail-soft definition error
%MX10.23.9 Remote I/O master 3
fail-soft definition error
%MX10.23.10 Remote I/O master 4
fail-soft definition error
%MX10.23.11 Remote I/O master 5
fail-soft definition error
%MX10.23.12 Remote I/O master 6
fail-soft definition error
%MX10.23.13 Remote I/O master 7
fail-soft definition error
%MX10.23.14 Not used --- ---
%MX10.23.15

App.3-6
 Appendix 3 CPU System Memory

SPH SPH
Address Name Description Level 300 200

%MX10.24.0 I/O module hold Set ON when hold is defined for a module other than output Fatal failure
definition error modules or for an output module set for system DO.
%MX10.24.1 Direct I/O running Set ON when an error is found in the operation setting for a Fatal failure
definition error module directly connected to the SX bus.
%MX10.24.2 Not used --- ---
|
%MX10.24.15
%MX10.25.0 Remote I/O master 0 Set ON when an error is found in the running definition for remote Fatal failure
running definition error I/O master.
%MX10.25.1 Remote I/O master 1
running definition error
%MX10.25.2 Remote I/O master 2
running definition error
%MX10.25.3 Remote I/O master 3
running definition error
%MX10.25.4 Remote I/O master 4
running definition error
%MX10.25.5 Remote I/O master 5
running definition error
%MX10.25.6 Remote I/O master 6
running definition error
%MX10.25.7 Remote I/O master 7
running definition error
%MX10.25.8 Not used --- ---
|
%MX10.25.15
%MX10.26.0 Processor-link 0 Set ON when an error is found in the running definition for P-link, Fatal failure
running definition error PE-link or FL-net.
%MX10.26.1 Processor-link 1 Processor-link 0 corresponds to the module of line No. "8";
running definition error processor-link 1, to the module of line No. "9".
%MX10.26.2 Processor-link 2
running definition error
%MX10.26.3 Processor-link 3
running definition error
%MX10.26.4 Processor-link 4
running definition error
%MX10.26.5 Processor-link 5
running definition error
%MX10.26.6 Processor-link 6
running definition error
%MX10.26.7 Processor-link 7
running definition error
%MX10.26.8 Not used --- ---
|
%MX10.29.15

Note: The system definition error factors include the errors that are blocked by Expert (D300win) and therefore do not occur
during ordinary operation.

App.3-7
Appendix 3 CPU System Memory

(12) Application program error factor %MW10.38, %MW10.39

SPH SPH
Address Name Description Level 300 200

%MX10.38.0 Application program Set ON when the execution time of default task exceeds the set Fatal failure
WDT error value of watchdog timer.
%MX10.38.1 Application execution Set ON when an error, such as temporary size over, occurs when Fatal failure
error executing a user program.
%MX10.38.2 Not used --- ---
|
%MX10.38.10
%MX10.38.11 FB instance setting Set ON when specified storage address does not exist. Fatal failure
error
%MX10.38.12 Initial value setting Set ON when the set initial value exceeds the defined range of Fatal failure
error storage area.
%MX10.38.13 SFM boundary Set ON when a memory size greater than the maximum capacity Fatal failure
definition error of system FB instance memory is set.
%MX10.38.14 POU instruction error Set ON when an error is found in the POU. Fatal failure
%MX10.38.15 Task registration error Set ON when an error is found in the task registration. Fatal failure
%MX10.39.0 Missing level 0 task Set ON when a task is omitted from execution. Nonfatal
%MX10.39.1 Missing level 1 task Can be set OFF by application program. failure

%MX10.39.2 Missing level 2 task

%MX10.39.3 Missing level 3 task
%MX10.39.4 Level 0 task slow-down Set ON when program execution is deferred and the preset Nonfatal
%MX10.39.5 Level 1 task slow-down constant cycle cannot be kept. failure
Can be set OFF by application program. (fatal failure
%MX10.39.6 Level 2 task slow-down for SPS)
%MX10.39.7 Level 3 task slow-down
%MX10.39.8 Not used --- ---
|
%MX10.39.14
%MX10.39.15 Tact period monitoring Set ON when real tact period does not coincide with the system Nonfatal
error definition. failure
Can be set OFF by application program.

Note: The error factors include the errors that are blocked (by checking during compilation, for example) by Expert (D300win)
and therefore do not occur during ordinary operation.

App.3-8
Mitsui Sumitomo Bank Ningyo-cho Bldg.,
5-7, Nihonbashi Odemma-cho, Chuo-ku, Tokyo 103-0011, Japan
Phone: +81-3-5847-8011
Fax: +81-3-5847-8172
URL http://www.fujielectric.co.jp/fcs/eng/