# Export Controller Configuration

This menu is visible if the Scheduled task type is Export controller configuration.

Parameter | Description
--- | ---
Backup location | Enter a valid path to the location to which the export file is to be written. The default value is empty with an error indicator that shows the server does not recognize the location as a valid path. The path must be valid when the scheduled task is executed.
File name | The exported file is in the format : *.tar.gz It can later be used to import configurations to controllers or sent to Atlas Copco for debugging purpose or failure analysis. The default filename is something like PFExport_<controller-name>_<Date-code>.tar.gz. System variables can be used to differentiate and to create unique filenames.
Folder per controller | When set to Yes, each export will be saved in a separate sub folder. When set to No, the exports will be saved in the Save Location folder.
Folder name | System variables can be used to differentiate and to create unique folder names.
Delete old configuration files | When set to Yes, old controller configuration files stored with a unique file name will be deleted. The unique file name must contain a system variable. For example, <ControllerName>.

System variables can be used to specify file names and folder names for the export. They are added at runtime, to the file name or folder to create unique export files or locations.

The system variables are written inside brackets, and the following may be used:

- [ControllerName]

- [IpAddress]

- [ControllerSerialNumber]

It is possible to combine text with system variables. An example is Station_3_[ControllerName]_[IpAddress]. If the controller name is ABC and its IP address is 10.25.25.180, the resulting filename at runtime will be Station_3_ABC_10.25.25.180.tar.gz.

A scheduled file export can only occur if the controller is online at the time of the export and that the export path is valid.

Schedule
Parameter | Description
--- | ---
Enabled | When set to Yes, the scheduled task will run according to the scheduled configurations. When set to No, the scheduled task will not run.
Weekdays | Mark one or more weekdays when the task will run.
Time | Select a run time from the drop-down menu.
Start date | Select a start date for the run time from the calender icon.
Select end date | When set to Yes, the scheduled task will run according to the schedule until the end date. When set to No, the scheduled task will run according to the schedule from the start date.

After a task is executed, the results are shown in the Results menu.

Results
Parameter | Description
--- | ---
Status | The scheduled task status after running the task can show OK or NOK.
Controller | Displayed if available for the task.
Latest run | Time and date when the scheduled task was executed.
Error | Error code examples if the status is NOK. ControllerNotOnline ControllerNotFound NoWriteAccessToStorage ExportFailed ImportFailed FileNotFound TimedOut