The Flash memory contains the file system used by the controller.
The total size of the Flash memory is 128 MB, of which 10 MB is available for the application.
The Modicon LMC058 Motion Controller manages the following file types:
|
Type |
Description |
|---|---|
|
Executable application |
User application. This is the binary code that is executed when the controller is in the RUNNING state. |
|
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, serial line, and firewall parameters. The parameters specified in the file override the parameters in the executable application at each reboot. |
|
|
Files in which the controller logs events as specified by the application. |
|
|
HTML page |
HTML pages displayed by the web server for the website embedded in the controller. |
|
Operating System (OS) |
Controller firmware that can be written to Flash memory. The firmware file is applied at next reboot of the controller. |
|
Retain variable |
Remanent variables |
|
Retain-persistent variable |
|
|
(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. |
|
There are two ways to create the boot application:
oSelect the option during the application download process.
oChoose Online > Create boot application at any point after download.
If you do not create a boot application, the controller will enter the EMPTY state after the next reboot.
This table shows the file organization of the flash memory:
|
Disk |
Directory |
File |
Content |
Up/Downloaded Data Type |
|---|---|---|---|---|
|
/sys |
OS |
M258FW1v_XX.YY (1) |
Firmware of core 1 |
Firmware |
|
M258FW2v_XX.YY (1) |
Firmware of core 2 |
|||
|
M258_top_Vxx.bit |
Firmware |
|||
|
Version.ini |
Control file for firmware version |
|||
|
|
NXCIF50-RTE.bin |
Profibus firmware file |
Firmware |
|
|
cifxdps.nxf |
||||
|
Web |
Index.htm |
HTML pages displayed by the web server for the website embedded in the controller. |
Website |
|
|
Conf.htm |
||||
|
... |
||||
|
/usr |
App |
Application.app |
Boot application |
|
|
Application.crc |
|
|||
|
Application.map |
|
|||
|
Archive.prj (2) |
Application source |
|
||
|
App/MFW |
DeviceID_X.fw (2) |
Expansion modules Firmware |
Firmware |
|
|
Cfg |
Machine.cfg(2) |
Configuration |
||
|
CodesysLateConf.cfg(2) |
oName of application to launch oRouting table (main/sub net) |
Configuration |
||
|
/usr |
Dta |
UserDefinedDtaName_1.Dta |
All *.Data files created using the DataFileCopy function block |
Data files |
|
... |
||||
|
UserDefinedDtaName_n.Dta |
||||
|
Log |
UserDefinedLogName_1.log |
All *.log files created using the data logging functions. Specify the total number of files created and the names and contents of each log file. |
log file |
|
|
... |
||||
|
UserDefinedLogName_n.log |
||||
|
Ntx |
NXCIF50-RTE.bin |
Profibus firmware file |
Firmware |
|
|
cifxdps.nxf |
||||
|
SysLog |
crashC1.txt(2) crashC2.txt(2) crashBoot.txt(2) |
This file contains a record of detected system errors. For use by Schneider Electric Technical Support. |
log file |
|
|
PLClog.txt(2) |
This file contains system event data that is also visible in EcoStruxure Machine Expert online by viewing the Log tab of the Controller Device Editor. |
|||
|
FWLog.txt |
This file contains a record of firmware system events. For use by Schneider Electric Technical Support. |
|||
|
Eip |
My_Machine_Controller.eds My_Machine_Controller.gz My_Machine_Controller.ico |
These files are necessary to configure and operate your controller as an EtherNet/IP Master. |
Configuration and icon files |
|
|
/bd0 |
– |
– |
USB memory |
Application Configuration log file Firmware Website |
|
(1) v_XX.YY represents the version (2) If any |
||||
NOTE: Use the sysFile, sysDir, and CAAFile libraries to access to /bd0 and /usr. For more information on the function blocks of these libraries, refer to the CoDeSys Libraries topic in the EcoStruxure Machine Expert online help.
When system, program or certain user activity creates specific file types, the LMC058 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 quite large to the point of exceeding the space available in the file system. You should, therefore, develop a method to periodically archive the log data on a USB key. For example, you could split the log data into several files, e.g. LogMonth1, LogMonth2, and use the ExecuteScript command (refer to the Modicon LMC058 Motion Controller PLC System Functions and Variables PLCSystem Library Guide) to copy the first file to a USB key, and thereafter, 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 DATA |
|
Back up your *.log files to a USB key on a regular schedule that avoids saturating the available free space in your controller file system. |
|
Failure to follow these instructions can result in equipment damage. |
