Your SICK ID gives you access to our extensive range of services. This includes direct online orders, price and availability checks, and access to our digital services.
Data Storage: (often also called "Parameter server") has been introduced with IO-Link specification V1.1 (following a IO-Link device with IO-Link protocol version V1.0 does not support the Data Storage mechanism).
Data Storage (following called DS) makes device replacement easy and comfortable. The IO-Link master holds the complete set of necessary parameters and writes those into the new device in case of a device replacement. To do so each parameter of an IO-Link device with DS-capability gets the information if it is relevant for a device replacement or not. All parameters which are relevant are read by the IO-Link Master and are saved in its Data Storage.
Of course all this only happens if the DS mechanism is activated in the used IO-Link master. The configuration is highly dependent on the manufacturer of the IO-Link master.
How does it work?
During the boot process of the IO-Link master, or after a new IO-Link device has been attached to the IO-Link master the parameter set of the device is compared with the parameter set in the DS of the IO-Link master. To do this easily a CRC is calculated out of the parameters and only the CRC of IO-Link master and IO-Link device are compared.
If the CRC is correct, the IO-Link master is downloading the saved configuration into the device. This way it is safe that the device is always using the configuration which was saved in the IO-Link master.
How to initially fill the Data Storage of the IO-Link master?
As soon as DS is activated in the IO-Link master it will upload the current parameter set of the device and consider this configuration as the one to be used for the future.
How to update the parameter set stored in the IO-Link master Data Storage?
As described above the most happens automatically if DS is activated. But when it comes to the handling of the stored dataset some things need to be considered:
Using SOPAS together with DS
If the device has a second parametrization possibility besides IO-Link (e.g. TCP/IP, USB) which is used to change parameters in most cases the IO-Link master will not update its parameter set accordingly. Thus on the next restart the IO-Link master will overwrite the new settings done by SOPAS with the settings from the DS.
If you like to resume the parametrization done in SOPAS in the DS the IO-Link device needs to signalize this to the master using an IO-Link Event. This event is produced by the device if it receives the System Command ParamDownloadStore (value 0x05).
--> To resume new parameters write an ISDU with value 0x05 to the System Command ISDU (index 2).
Using SICK function blocks together with DS
For the function blocks the same as for parametrization with other tools like SOPAS is true.
The IO-Link master is not automatically updating its DS. So if any parameter change which was done using function blocks should be resumed to the DS of the IO-Link master the ParamDownloadStore command needs to be used as well (see above).
--> To resume new parameters write an ISDU with value 0x05 to the System Command ISDU (index 2).
Editing parameters using the display or a teach button on the device directly
If parameters are changed using controls directly on a device the parameters will be automatically resumed by the IO-Link master. After a parameter change (or a teach-in) using the local control possibilities the device automatically send an event to the IO-Link master signalizing the necessary upload of the parameters.
--> Changes made using local parametrization possibilities are automatically resumed.
Normal ISDU communication in parallel to DS
Attention
The upload of a data set from the IO-Link device into the DS of the IO-Link master may take up to some seconds depending on the amount of data. During this time no other On-Request Data (sometimes called Service Data) could be read or written. Some IO-Link masters provide a feedback if the transfer is done or even a progress. Others provide no information. This is completely IO-Link master specific.
SICK function blocks have no possibility to provide this information.
For further literature to IO-Link DS see attachment.
