Note
In the following text the term HS/FS is replaced by the term device.
1.What does this function do?
The retentive data of the device can be saved cyclically on up to 2 FTP servers. (Procedure)
The device can load the data from the FTP server into the flash when restarting (non-volatile memory).
The device can load the data from the FTP server into the flash when restarting (non-volatile memory).
2.What can this function be used for?
- Securing the retentive data of the device
- Restoring the retentive data, e.g., when exchanging the device
3.Read out
Set the parameters of up to 2 FTP servers for reading out retentive data in these masks.
The parameters for FTP 1 server and FTP 2 server are identical.
The parameters for FTP 1 server and FTP 2 server are identical.
- Host address: IP address or name of the FTP server
- Port of the FTP server: (Usually 21)
- Passive mode: (Yes/No). Further information can be found in the documentation of the FTP server
- User name: User name for logging in at FTP server
- Password: Password for logging in at FTP server
- Path: Path in which the retentive file is located (e.g. /array1/hstest/hs183f1/)
- Status object: Status object for reading out (format 8-bit 0-127)
The object can take on the following values:
1 = The data was successfully read out
2 = The data could not be read out
4.Write
Set the parameters of up to 2 FTP servers for writing retentive data in these masks.
The parameters for FTP 1 server and FTP 2 server are identical.
The parameters for FTP 1 server and FTP 2 server are identical.
- Host address: IP address or name of the FTP server
- Port of the FTP server: (Usually 21)
- Passive mode: (Yes/No). Further information can be found in the documentation of the FTP server
- User name: User name for logging in at FTP server
- Password: Password for logging in at FTP server
- Path: Path in which the retentive file is located (e.g. /array1/hstest/hs183f1/)
Comment: This path has to be created manually. It is not automatically created!
There has to be a "/" at the end of the path specified here! - Status object: Status object for reading out (format 8-bit 0-127)
The object can take on the following values:
0 = Start of writing
1 = The data has been saved
2 = The data has not been saved
3 = Reading back was faulty - Save cycle: The retentive memory is saved on the FTP server(s) approx. every 15 minutes (regular cycle).
- User-defined (2..96): A retentive file is saved on the FTP server(s) for each storage cycle entered here.
Example: Value=3, only every 3rd time (approx. every 45 minutes) is a retentive file stored on the FTP server. - Ring memory day: In the case of cyclical storage, at most 1x hour an additional retentive file (plus debug page) is stored on the FTP server(s). After 24 hours, this process begins again and overwrites the existing files.
- Ring memory month: In the case of cyclical storage, an additional retentive file (plus debug page) is stored on the FTP server(s) every day. After a month, this process begins again and overwrites the existing files.
5.Files that are saved on the FTP server(s)
2 retentive files are always saved. The daily and monthly ring memories are additionally extended by a debug page per entry.
The project ID is structured as follows: YYYYMMDDHHMMssmmm
The project ID is structured as follows: YYYYMMDDHHMMssmmm
- YYYY: Year
- MM: Month
- DD: Day
- HH: Hour
- MM: Minute
- ss: Second
- mmm: Millisecond
File name retentive file: _Project-ID_0.hsr and _Project-ID_1.hsr (Example: _20070306175209062_1.hsr )
If a daily ring memory is selected, the file names are as follows:
File name retentive file: _Project-ID_s_hh.hsr (hh is the placeholder for hours) (Example: _20070306175209062_s_16.hsr for 4 pm)
File name debug page: _Project-ID_ds_hh.html (Example: _20070306175209062_ds_16.html for 4 pm)
If a monthly ring memory is selected, the file names are as follows:
File name retentive file: _Project-ID_t_dd.hsr (dd is the placeholder for the day) (Example: _20070306175209062_t_7.hsr for the 7th day of the month)
File name debug page: _Project-ID_dt_hh.html (Example: _20070306175209062_dt_7.html for the 7th day of the month)
If a daily ring memory is selected, the file names are as follows:
File name retentive file: _Project-ID_s_hh.hsr (hh is the placeholder for hours) (Example: _20070306175209062_s_16.hsr for 4 pm)
File name debug page: _Project-ID_ds_hh.html (Example: _20070306175209062_ds_16.html for 4 pm)
If a monthly ring memory is selected, the file names are as follows:
File name retentive file: _Project-ID_t_dd.hsr (dd is the placeholder for the day) (Example: _20070306175209062_t_7.hsr for the 7th day of the month)
File name debug page: _Project-ID_dt_hh.html (Example: _20070306175209062_dt_7.html for the 7th day of the month)
6.When is saving done on the FTP server(s)?
- Depending on the setting of the "save cycle", approx. every 15 minutes when the option "every time" is selected, or on the user-defined multiple (entry in the "user-defined" field) of 15 minutes if "every time" is NOT selected.
- There are additional backups depending on the setting of the ring memory.
- Directly BEFORE downloading the HS/FS, if this is restarted through Expert via the item "Transfer -> Only restart".
- Directly BEFORE downloading the HS/FS when this is being reprogrammed
- Directly AFTER restarting the HS/FS if this has been reprogrammed. A new project ID is used.
7.Additional status objects
The following status objects (14-byte text) are sent when the device is started:
- Project ID
- Serial number of the device
The assignment is undertaken under Master data\Project\Project settings\Other\Status objects.
The project ID is also saved on the debug page in the System section.
The project ID is also saved on the debug page in the System section.
8.Acoustic signals
If there is an error during saving or reading, a double beep sounds 10 times in the HS/FS.
9.Other
Additional documents:
- General information on the Retentive memory.
- The Retentive memory stored externally help file.
10.Frequently asked questions
Can retentive data that has been saved with Expert be restored with the FTP Backup Server?
No, this retentive data can only be restored with the Expert.
Can retentive data that has been saved by Expert be read in again if an FTP backup server for reading and writing is simultaneously set up?
No. If an FTP backup server for backing up retentive data is active in the project, uploading the retentive data via Expert does not function because the data uploaded via Expert is overwritten by the data read out by the FTP server when subsequently starting up the HS/FS.
Where is the data on the subject of retentive memories located on the debug page and what does it mean?
The data is located in the Retentive memory section.
Explanation of the Retentive memory category of the debug page
| Field | Value | Description |
|---|---|---|
| Loading memory capacity | 1 | Loading of the retentive memory when the device starts from the save location: 0=Flash memory of the device 1=Flash memory of the device 9=FTP server |
| Loading status | OK | |
| Loading duration | 4,882 | In seconds |
| Loading size | 4760121 | Size in bytes |
| Loading status of | 08.03.2007 16:40:27 | Status of the retentive data |
| Saving time | 12.03.2007 11:55:36 | Last saved... |
| Saving memory capacity | 1 | In which memory capacity in the flash memory of the device |
| Saving status | OK | |
| Saving duration | 5.523 / 5.386 | In seconds flash memory area 1/2 |
| Saving size | 3007996 | Size in bytes |
| Saving number | 356 | How often was saving carried out while the device was running |
| Cut-off | 13 | If the value >zero, data was cut off. (See also status object "Number of cleanings") |
| Saving error number | 0 | |
| Saving error last | ? | Date and time of last error |
| Saving error reason | ? | Plain text (see also Exceptions) |
| Backup1 server | 192.168.0.28:21 | IP address of FTP server 1 |
| Backup1 path | /array1/hstest/opt2/ | |
| Backup1 time | 12.03.2007 11:55:48 | |
| Backup1 status | OK | Plain text |
| Backup1 duration | 1,696 | |
| Backup2 server | 192.168.0.30:21 | |
| Backup2 path | /array1/hstest/hs183f2/ | |
| Backup2 time | 12.03.2007 11:55:53 | |
| Backup2 status | OK | |
| Backup2 duration | 3,398 | |
| Restore1 server | 192.168.0.28:21 | Restoring of backup server1 |
| Restore1 path | /array1/hstest/hs183f1/ | |
| Restore1 time | 08.03.2007 16:41:44 | |
| Restore1 status | ERR | Plain text |
| Restore1 duration | 0,134 | |
| Restore2 server | 192.168.0.30:21 | Restoring of backup server2 |
| Restore2 path | /array1/hstest/hs183f2/ | |
| Restore2 time | 08.03.2007 16:41:45 | |
| Restore2 status | ERR | Plain text |
| Restore2 duration | 0,552 |