The Flash memory contains the file system used by the controller.
The Modicon M262 Logic/Motion Controller manages the following file types:
|
System function (/sys) |
Description |
|---|---|
|
Operating System (OS) |
Controller firmware that can be written to Flash memory. The firmware file is applied at next reboot of the controller. |
|
User functions (/usr) |
Description |
|---|---|
|
This file resides in Flash memory and contains the compiled binary code of the executable application. Each time the controller is rebooted, the executable application is extracted from the boot application and copied into the controller RAM (1). |
|
|
Source file that can be uploaded from Flash memory to the PC if the source file is not available on the PC (2). |
|
|
File that contains Ethernet and serial line parameters. The parameters specified in the file override the parameters in the executable application at each reset. |
|
|
Firewall parameters |
Settings used to configure the firewall of the M262 Logic/Motion Controller. These settings restrict access to authorized personnel and protocols only. See Firewall Configuration for more information. |
|
Files in which the controller logs events as specified by the application. |
|
|
(1) The creation of a boot application is optional in EcoStruxure Machine Expert, according to application properties. Default option is to create the boot application on download. When you download an application from EcoStruxure Machine Expert to the controller, you are transferring only the binary executable application directly to RAM. (2) EcoStruxure Machine Expert does not support uploading of either the executable application or the boot application to a PC for modification. Program modifications must be made to the application source. When you download your application, you have the option to store the source file to Flash memory. |
|
This table shows the file organization of the flash memory:
|
Disk |
Directory |
File |
Content |
Up/Downloaded data type |
|---|---|---|---|---|
|
/sys |
Pkg |
Temporary file |
Internal use |
N/A |
|
/usr |
App |
Application.app |
Boot application |
Application |
|
Application.crc |
– |
|||
|
Archive.prj (1) |
Application source |
– |
||
|
Cfg |
Machine.cfg (1) |
Configuration |
||
|
CodesysLateConf.cfg |
Name of application to launch. |
Configuration |
||
|
FirewallDefault.cmd |
Default firewall settings. By default, this file does not exist. It can be added optionally. |
Configuration |
||
|
/usr |
Log |
UserDefinedLogName_1.log |
All *.log files created using the data logging functions. You must specify the total number of files created and the names and contents of each log file using the datalogging feature. |
log file |
|
... |
– |
– |
||
|
UserDefinedLogName_n.log |
– |
– |
||
|
pki |
– |
Certificate store for M262 secured protocols. |
– |
|
|
Rcp |
– |
Main directory for Recipes. |
– |
|
|
Syslog |
crash.txt(1) LoggerFile_xxx.mel |
Record of detected system errors. For use by Schneider Electric Technical Support. |
Log file |
|
|
Visu |
– |
Used for the Webvisualization feature. |
– |
|
|
/sd0 |
– |
– |
SD card. Refer to Managing Script Files. |
– |
|
– |
User files |
– |
– |
|
|
(1) If the files had been created due to specific events or customer requirements. |
||||
NOTE: For more information on libraries and available function blocks, refer to Libraries.
When system, program or certain user activity creates specific file types, the M262 Logic/Motion Controller examines the file extension and automatically moves the file to a corresponding folder in flash memory.
The following table lists the file types that are moved in this way and the destination folder in flash memory:
|
File extensions |
Flash memory folder |
|---|---|
|
*.app, *.ap_, *.err, *.crc, *.frc, *.prj |
/usr/App |
|
*.cfg, *.cf_ |
/usr/Cfg |
|
*.log |
/usr/Log |
|
*.rcp, *.rsi |
/usr/Rcp |
Data logging files can become large to the point of exceeding the space available in the file system. Therefore, you should develop a method to archive the log data periodically on an SD card. You could split the log data into several files, for example LogMonth1, LogMonth2, and use the ExecuteScript command to copy the first file to an SD card. Afterwards, you may remove it from the internal file system while the second file is accumulating data. If you allow the data logging file to grow and exceed the limits of the file size, you could lose data.
|
NOTICE |
|
LOSS OF APPLICATION DATA |
|
oBackup SD card data regularly. oDo not remove power or reset the controller, and do not insert or remove the SD card while it is being accessed. |
|
Failure to follow these instructions can result in equipment damage. |
