Using File Memory |
|
|
|
| Section | |
File Names Handled by CPU Unit |
|
|
| |||
|
| The files described in the following table can be read or written by the CPU | ||||
|
| Unit. |
|
| ||
|
|
|
|
|
|
|
File type | File name |
| Extension | Contents | Description | |
|
|
|
|
|
|
|
Data file |
| ******** |
| .IOM | Specified ranges of I/ | • Contains word |
|
|
|
|
| O Memory | word through an end word in one memory |
|
|
|
|
|
| area. |
|
|
|
|
|
| • The following areas can be used: CIO, HR, |
|
|
|
|
|
| WR, AR, DM, and EM. |
|
|
|
|
|
| |
Program file | ******** |
| .OBJ | Complete user pro- | • Contains all the programs for cyclic tasks | |
|
|
|
|
| gram | and interrupt tasks, as well as task infor- |
|
|
|
|
|
| mation for one CPU Unit. |
|
|
|
|
|
| |
Parameter area file | ******** |
| .STD | • PLC Setup | • Contains all of the parameter data for one | |
|
|
|
|
| • Registered I/O | CPU Unit. |
|
|
|
|
| tables | • There is no need for the user to distinguish |
|
|
|
|
| • Routing tables | the various types of data contained in the |
|
|
|
|
| • CPU Bus Unit | file. |
|
|
|
|
| • The file can be automatically read to or | |
|
|
|
|
| Setup and other | |
|
|
|
|
| setup data | written from the CPU Unit simply by speci- |
|
|
|
|
|
| fying the extension (.STD) |
Files | Data files | AUTOEXEC |
| .IOM | I/O Memory data for | • There does not necessarily need to be a |
trans- |
|
|
|
| the specified number | data file in the Memory Card when the |
ferred at |
|
|
|
| of words starting from | automatic file transfer function is used at |
startup |
|
|
|
| D20000 | startup. |
|
|
|
|
|
| • The AUTOEXEC.IOM file always contains |
|
|
|
|
|
| DM Area data starting at D20000. |
|
|
|
|
|
| • All data in the file will be transferred to |
|
|
|
|
|
| memory starting at D20000 at startup. |
|
|
|
|
|
|
|
| Program | AUTOEXEC |
| .OBJ | Complete user pro- | • There must be a program file in the Mem- |
| files |
|
|
| gram | ory Card when the automatic file transfer |
|
|
|
|
|
| function is used at startup. |
|
|
|
|
|
| • Contains all the programs for cyclic tasks |
|
|
|
|
|
| and interrupt tasks, as well as task infor- |
|
|
|
|
|
| mation for one CPU Unit. |
|
|
|
|
|
|
|
| Parameter | AUTOEXEC |
| .STD | • PLC Setup | • There must be a parameter file in the |
| area file |
|
|
| • Registered I/O | Memory Card when the automatic file |
|
|
|
|
| tables | transfer function is used at startup. |
|
|
|
|
| • Routing tables | • Contains all of the parameter data for one |
|
|
|
|
| • CPU Bus Unit | CPU Unit. |
|
|
|
|
| • There is no need for the user to distinguish | |
|
|
|
|
| Setup and other | |
|
|
|
|
| setup data | the various types of data contained in the |
|
|
|
|
|
| file. |
|
|
|
|
|
| • All parameters in the file will be automati- |
|
|
|
|
|
| cally transferred to specified locations in |
|
|
|
|
|
| memory at startup. |
Note 1. Refer to information on file memory in the
2.All files transferred automatically at startup must have the name
AUTOEXEC.
81