ARS – Archive store value

Block SymbolLicensing group: STANDARD

Function Description
If RUN = on, the ARS block writes the value at the u input to the archive. The type of the value at the input is determined by the type parameter, and the type of the archive item is the same. The subtype parameter allows you to specify the type of alarm that alarm blocks write (e.g. L->H for a logical alarm, or HiHi for a numeric alarm). The value of the parameter can be 0 to 7 and is not used for arrays. This parameter is usually not used. The meaning of the other parameters is the same as for other blocks for writing to the archive.

If type = Reference, an array (column vector or matrix) is expected. If it is a matrix, each of its columns is saved as a separate file in the archive (i.e., in one tick task with this block, as many entries as the matrix of columns will stand out in the archive).

Note 1: In the case of arrays, the archive subsystem is limited to 255 values in one item. At the same time, there is a limit of 512 bytes of data in one item, so for the Short type, at most 128 values are saved, for the Long type at most 64 values, and for the Double type at most 32 values. If the input array is longer, the block saves the specified number of values from the beginning of the array and does not report any errors.

Note 2: In the case of a string, the archive subsystem is limited to 65535 bytes (characters in UTF8 encoding may be less). If the input text is longer, the block saves the first 65635 bytes from the beginning of the array and does not report any errors. Some reading functions may have a small buffer, and such a long text cannot be read, so it is recommended not to exceed 4080 bytes (characters if only characters from the English keyboard are used).

Note 3: The id parameter usually serves to link the item in the archive to the source block/signal (and alarm in some cases). Therefore, its uniqueness is checked across the entire configuration. The ARS block is considered a low-level block that writes an event to the archive without further context and checks. Therefore, the uniqueness of the id parameter is not checked here. For example, if numeric or text items start appearing in the archive for a binary alarm, they are almost certainly generated by some ARS block (or an analogous function in the script of the REXLANG block).

This block does not propagate the signal quality. More information can be found in the 1.4 section.

2024 © REX Controls s.r.o., www.rexygen.com