-
Add a processor module to your project. ⮫ “Creating a new project ”
-
Double-click the PLC node in the device tree.
This will open a new window with tabs for the device configuration:
-
“Communication Settings” ⮫ “Tab 'Communication Settings'”
-
“PLC Settings” ⮫ “Tab 'PLC Settings'”
-
“Version information” ⮫ “Version information”
-
“Statistics” ⮫ “Statistics”
-
“Files” ⮫ “Tab 'Files'”
-
“Log” ⮫ “Log”
-
“PLC Shell” ⮫ “PLC shell commands”
-
“Users and Groups” ⮫ “Tab 'Users and Groups'”
-
“Access Rights ”⮫ “Tab 'Access Rights'”
-
“Symbol Rights” ⮫ “Tab 'Symbol Rights'”
-
“PM5xxx Hardware” ⮫ “Changing the processor module type”
-
“CPU Parameters” ⮫ “Tab 'Parameters'”
-
“IEC Objects” ⮫ “Tab '<device name> IEC Objects'”
-
“I/O mapping list” ⮫ “I/O mapping list”
-
“I/O-Bus I/O Mapping”⮫ “Live values in views with I/O components”
-
“Task Deployment” ⮫ “Tab 'Task deployment'”
-
“Applications” ⮫ “Tab 'Applications'”
-
“Backup and Restore” ⮫ “Tab 'Backup and Restore'”
-
“Status” ⮫ “Status”
-
“Diagnosis” ⮫ “Device diagnosis”
-
“Diagnosis History” ⮫ “Diagnosis history”
-
“License Information” ⮫ “View license information”
-
“Information” General information about the device (name, vendor, version etc.)
-
-
Select the “CPU Parameters” tab to configure the parameters for the processor module. ⮫ Table
-
Use the “PM5xxx Hardware” tab for later on changes of “Terminal Base Type” or “Processor Module Type” ⮫ “Changing the processor module type”.
-
Select the “I/O mapping list” tab to create mapping variables with better usability support compared to the tree structured view. ⮫ “I/O mapping list”
-
Select the “Backup and Restore” tab to create a backup or restore the project. ⮫ “Tab 'Backup and Restore'”
-
Select the “Diagnosis” tab to know what errors have occurred in the project. ⮫ “Device diagnosis”
|
Parameter |
Default |
Value |
Description |
|---|---|---|---|
|
Error LED |
On |
On |
The error LED lights up for errors of all classes, no fail-safe function activated. |
|
Off by E4 |
Warnings (E4) are not indicated by the error LED, no fail-safe function activated. |
||
|
Off by E3 |
Warnings (E4) and minor errors (E3) are not indicated by the error LED, no fail-safe function activated. |
||
|
POU control |
Control LED ERR with POU PmErrLedSet |
||
|
Check battery |
On |
On |
The presence of the battery and the battery status are checked. If no battery is available or the battery is empty, a warning (E4) is generated and the ERR LED lights up. |
|
Off |
The presence of the battery is not checked. No warning (E4) is generated. The LCD display "Batt" (triangle) can not be acknowledged! This also applies if a battery is installed but empty. |
||
|
Stop on error class |
Diagnosis of at least error class 2 |
Diagnosis of at least error class 2 |
In case of a fatal or severe error (E1-E2), the user program is stopped. |
|
Diagnosis of at least error class 3 |
In case of a fatal, severe or minor error (E1-E3), the user program is stopped. |
||
|
Diagnosis of at least error class 4 |
In case of a fatal, severe or minor error (E1-E3) or a warning (E4) the user program is stopped. |
||
|
Diagnosis - Add PLC name to node name |
Off |
Off |
Diagnosis - Add PLC name to node name. |
|
On |
|||
|
PLC behavior after voltage dip |
Halt |
Halt |
Behavior of the PLC after short voltage dip: reboot or halt. |
|
Reboot |
|||
|
Diagnosis history |
On |
On |
Enable the diagnosis history. |
|
Off |
Disable the diagnosis history. |
||
|
Max. Diagnosis history entries |
1000 |
1000 |
Max. number of entries kept by the diagnosis history. |
|
Missed cycle behavior |
Next |
Next |
Skip the current cycle and start task in time on next cycle. |
|
ASAP |
Start the task immediately. |
||
|
Communication Schema |
Default |
Default |
Balanced priority for communication via communication modules (CMs) and onboard Ethernet communication. |
|
Communication modules |
Priority and high performance for communication module (CM) based communication via sync tasks. Lower priority for onboard Ethernet and I/O bus. |
||
|
Onboard Ethernet |
Priority for onboard Ethernet communication (e.g. via Modbus TCP). Lower priority for communication via communication modules (CMs). |
||
|
Real time onboard Ethernet |
Very high priority for onboard Ethernet communication (e.g. EtherCAT PROFINET Ethernet). Low priority for communication via communication modules (CMs). |
||
|
Automated reboot after E2 error |
Off |
Off |
Not automated reboot after E2 error. |
|
On |
Automated reboot after E2 error. |