SD Card File Structure¶
Note
The SD Card must be formatted with FAT16 file system. Another file system causes errors.
In the CPU, the SD Card is accessed like a PC floppy disk drive. The type of the file system is FAT16 (Microsoft DOS format). The file names are stored in 8.3 format (no “long” names) on the SD Card.
Caution
:strong:Removal of SD Card
Do not remove the SD card during access. Remove only when the RUN LED does not blink. Otherwise the SD card and/or files on it might get corrupted and/or normal PLC operation might be disturbed.
File Structure in Versions V1.0 and V1.1
In versions V1.0 and V1.1, the file structure on the SD Card looks as follows:
File structure on the SD Card, Versions V1.0 and V1.1
The root directory on the SD Card contains the command file SDCARD.INI (for a detailed description see the following section).
The subdirectory Firmware contains further subdirectories for the:
- CPUs PM571, PM581 and PM591
Each of these subdirectories contains the boot code
MixxB.gzaand the CPU firmwareMixx.gza. Boot code and firmware for the CPU PM582 are contained in the directory PM581.The subdirectory UserData contains the subdirectories:
- UserPrg, user program
- UserProj, source code of the user program
- UserDat, user data, and
- RetDat, retentive data.
These directories contain the user data.
xx in the file name represents the data file number.
File structure as of version V1.2
The SD Card file structure has been revised and expanded for version V1.2. The following\ new functions are implemented:
- Management of several boot code and firmware versions on one SD card.
- Each CPU has its own directory. Up to version V1.1, there were only directories for controller classes PM57x, PM58x and PM59x. Due to this, the PM581 and PM582 data were stored to the same directory, for example ..\PM581.
- Loading the field bus Communication Module firmware from the SD Card by specific settings in the file SDCARD.INI or using the PLC-Browser command.
- Management of several field bus Communication Module firmware versions.
- Saving/restoring RETAIN data (%M area excluded) to/from the SD Card via the user program and/or the PLC-Browser.
- Saving/restoring the PERSISTENT area (%R area) to/from the SD card via the user program and/or the PLC-Browser.
As of version V1.2, the file structure looks as follows:
File structure on the SD Card, Versions V1.2
File Structure as of Version V2.x
The SD Card file structure has been revised and expanded for version V2.x.
Note
The following list is a snap-shot of the V2.x file structure. The directory names of the actual firmwares may be different.
| Module Type | Directory (Root) | Data File (SDCARD.INI) |
Supported as of Version |
|---|---|---|---|
| CM572 | FIRMWARE\CM572\1_097\ | DPMAC500.E2D | V1.x |
CM574-RS CM574-RCOM |
FIRMWARE\CM574\2_1_3\ | C574.gza C574B.gza RCOM.PRG RCOM.CHK |
V1.3.x |
| CM575 | FIRMWARE\CM575\1_109\ | DNMAC500.E33 | V1.x |
| CM577 | FIRMWARE\CM577\1_100\ | CM577.e30 | V1.x |
| CM578-CN | FIRMWARE\CM578\1_101\ | COMAC500.E34 | V1.x |
| PM554 | FIRMWARE\PM554\ FIRMWARE\PM554\2_4_2\ FIRMWARE\PM554\1_3_0\ |
Pm55x.gza Pm55x.gza Pm55xB.gza |
V1.3.x |
FIRMWARE\PM554\ONB_IO\1_1_2 FIRMWARE\PM554\ONB_IO\ |
5500.app | ||
| FIRMWARE\PM554\RTC_BATT\1_6\ | RtcBatt.app | ||
| PM554-ETH | FIRMWARE\PM554ETH\ FIRMWARE\PM554ETH\2_4_2\ FIRMWARE\PM554ETH\2_0_2\ |
Pm55xE.gza Pm55xE.gza Pm55xEB.gza |
V2.0.x |
FIRMWARE\PM554ETH \ONB_IO\1_1_2\ FIRMWARE\PM554ETH\ONB_IO\ |
5505.app | ||
| FIRMWARE\PM554ETH\RTC_BATT\1_6\ | RtcBatt.app | ||
| PM564 | FIRMWARE\PM564\ FIRMWARE\PM564\2_4_2\ FIRMWARE\PM564\1_3_0\ |
Pm55x.gza Pm55x.gza Pm55xB.gza |
V1.3.x |
FIRMWARE\PM564\ONB_IO\1_1_2\ FIRMWARE\PM564\ONB_IO\ |
5501.app | ||
| FIRMWARE\PM564\RTC_BATT\1_6\ | RtcBatt.app | ||
| PM564-ETH | FIRMWARE\PM564ETH\ FIRMWARE\PM564ETH\2_4_2\ FIRMWARE\PM564ETH\2_0_2\ |
Pm55xE.gza Pm55xE.gza Pm55xEB.gza |
V2.0.x |
FIRMWARE\PM564ETH \ONB_IO\1_1_2\ FIRMWARE\PM564ETH\ONB_IO\ |
5501.app | ||
| FIRMWARE\PM564ETH\RTC_BATT\1_6\ | RtcBatt.app | ||
| PM572 | FIRMWARE\PM572\ FIRMWARE\PM572\2_4_2\ FIRMWARE\PM572\2_3_0\ FIRMWARE\PM572\Display\2_8 |
PM58xN.gza PM58xN.gza PM58xNB.gza Display.app |
V2.0.x |
| PM573-ETH | FIRMWARE\PM573ETH\ FIRMWARE\PM573ETH\2_4_2\ FIRMWARE\PM573ETH\2_3_0\ FIRMWARE\PM573ETH\Display\2_8\ |
PM58xN.gza PM58xN.gza PM58xNB.gza Display.app |
V2.0.x |
| PM582 | FIRMWARE\PM582\ FIRMWARE\PM582\2_4_2\ FIRMWARE\PM582\2_3_0\ FIRMWARE\PM582\Display\2_8\ |
PM58xN.gza PM58xN.gza PM58xNB.gza Display.app |
V2.0.x |
| PM583-ETH | FIRMWARE\PM583\ FIRMWARE\PM583\2_4_2\ FIRMWARE\PM583\2_3_0\ FIRMWARE\PM583\Display\2_8\ |
PM58xN.gza PM58xN.gza PM58xNB.gza Display.app |
V2.0.x |
| PM590-ARC | FIRMWARE\PM590ARC\ FIRMWARE\PM590ARC\2_4_2\ FIRMWARE\PM590ARC\2_3_1\ FIRMWARE\PM590ARC\Display\2_8\ |
Pm59xRD.gza Pm59xRD.gza Pm59xRDB.gza Display.app |
V2.3.x |
| PM590-ETH | FIRMWARE\PM590ETH\ FIRMWARE\PM590ETH\2_3_1\ FIRMWARE\ PM590ETH\2_4_2\ FIRMWARE\ PM590ETH\Display\2_8\ |
PM59xRD.gza PM59xRD.gza PM59xRDb.gza Display.app |
V2.0.x |
| PM591-ETH | FIRMWARE\PM591ETH\ FIRMWARE\PM591ETH\2_3_1\ FIRMWARE\PM591ETH\2_4_2\ FIRMWARE\PM591ETH \Display\2_8\ |
PM59xRD.gza PM59xRD.gza PM59xRDb.gza Display.app |
V2.0.x |
| PM591-2ETH | FIRMWARE\PM591_2.ETH\ FIRMWARE\PM591_2.ETH\2_4_2\ FIRMWARE\PM591_2.ETH\2_3_1\ FIRMWARE\PM591_2.ETH\Display\2_8\ |
Pm59xRD.gza Pm59xRD.gza Pm59xRDB.gza Display.app |
V2.4.x |
| PM592-ETH | FIRMWARE\PM592ETH\ FIRMWARE\PM592ETH\2_4_2\ FIRMWARE\PM592ETH\2_3_1\ FIRMWARE\PM591ETH\Display\2_8\ |
PM59xRD.gza PM59xRD.gza PM59xRDb.gza Display.app |
V.2.1.x |
| PM595-4ETH | FIRMWARE\PM595_4.ETH\ FIRMWARE\PM595_4.ETH\2_4_1\ FIRMWARE\PM595_4.ETH\2_4_2\ FIRMWARE\PM595_4.ETH\CMETH\2_7_22\ FIRMWARE\PM595_4.ETH\LEDBOARD\ FIRMWARE\PM595_4.ETH\LEDBOARD\1_5\ |
PM595.gza PM595B.gza PM595.gza ETHCFG.nxf LEDBoard.app LEDBoard.app |
V2.4.x |