Status in source: unconfirmed.
Technical details
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"essSnapshotCameraFilename",
"OBJECT-TYPE",
"SYNTAX",
"OCTET",
"STRING",
"(",
"SIZE",
"(",
"0",
".",
".",
"255",
")",
")",
"ACCESS",
"read-write",
"STATUS",
"mandatory",
"DESCRIPTION",
"\"<Definition>Indicates the filename used when storing new snapshot images. This parameter shall only consist of upper and lower case characters (A-Z, a-z), digits (0-9), underscores (_), periods (.), spaces, and the following case-sensitive field names enclosed in chevrons (<>): camera: A three digit camera number equal to essSnapshotCameraIndex. sequence: A three digit value that increments by one each time this camera is used to take a picture. This value shall roll-over from '999' to '000'. The initial value of this field and its value after a power outage is manufacture dependent. date: A six digit code indicating the UTC date in the format of YYMMDD. time: A six digit code indicating the UTC time in the format of HHMMSS. All implementations shall support all static character filenames with up to eight characters in the base filename, a period, and up to three characters in the filename extension. Support for longer filenames and the above fields are optional. For example, if this parameter has a value of 'latest.jpg', every snapshot taken is saved to 'latest.jpg' and overwrites any previous image saved to that filename. If this parameter has a value of '<date> <sequence>.jpg', each snapshot has a name (e.g., '060925 038') indicating the date it was taken along with a relatively unique code. While the second form prevents the inadvertent overwriting of filenames, it increases the likelihood of consuming large amounts of field device memory (eventually resulting in insufficientMemory errors) if not properly managed by the management station. <Informative>The filename does not necessarily define file format and it is left to the users to define an appropriate filename. For example, this object may be set to a value of ‘latest.bmp’. All implementations would be required to save their images with this filename; however, the image saved may vary. Some implementations may only save bitmapped images and the file would have an appropriate name. Other implementations may only save JPEG images and the ‘.bmp’ extension may be confusing. Other implementations may support both formats and use the extension in this field to select the storage format, while yet others may support both formats but ignore the extension assigned by this field (and use some other mechanism to select the storage format). A zero length filename may result in unexpected operations. An implementation may reject a zero length filename by responding with genErr. <DescriptiveName>SnapshotCamera.filename:text <Data Concept Type>Data Element <Object Identifier> 1.3.6.1.4.1.1206.4.2.5.2.14.2.6\"",
"::=",
"{",
"essSnapshotCameraEntry",
"6",
"}"
],
"syntax_tree": [
[
"SimpleSyntax",
"OCTET STRING",
[
"octetStringSubType",
[
[
0,
255
]
]
]
],
null,
[
"MaxAccessPart",
"read-write"
],
[
"Status",
"mandatory"
],
[
"DESCRIPTION",
"<Definition>Indicates the filename used when storing new snapshot images. This parameter shall only consist of upper and lower case characters (A-Z, a-z), digits (0-9), underscores (_), periods (.), spaces, and the following case-sensitive field names enclosed in chevrons (<>): camera: A three digit camera number equal to essSnapshotCameraIndex. sequence: A three digit value that increments by one each time this camera is used to take a picture. This value shall roll-over from '999' to '000'. The initial value of this field and its value after a power outage is manufacture dependent. date: A six digit code indicating the UTC date in the format of YYMMDD. time: A six digit code indicating the UTC time in the format of HHMMSS. All implementations shall support all static character filenames with up to eight characters in the base filename, a period, and up to three characters in the filename extension. Support for longer filenames and the above fields are optional. For example, if this parameter has a value of 'latest.jpg', every snapshot taken is saved to 'latest.jpg' and overwrites any previous image saved to that filename. If this parameter has a value of '<date> <sequence>.jpg', each snapshot has a name (e.g., '060925 038') indicating the date it was taken along with a relatively unique code. While the second form prevents the inadvertent overwriting of filenames, it increases the likelihood of consuming large amounts of field device memory (eventually resulting in insufficientMemory errors) if not properly managed by the management station. <Informative>The filename does not necessarily define file format and it is left to the users to define an appropriate filename. For example, this object may be set to a value of ‘latest.bmp’. All implementations would be required to save their images with this filename; however, the image saved may vary. Some implementations may only save bitmapped images and the file would have an appropriate name. Other implementations may only save JPEG images and the ‘.bmp’ extension may be confusing. Other implementations may support both formats and use the extension in this field to select the storage format, while yet others may support both formats but ignore the extension assigned by this field (and use some other mechanism to select the storage format). A zero length filename may result in unexpected operations. An implementation may reject a zero length filename by responding with genErr. <DescriptiveName>SnapshotCamera.filename:text <Data Concept Type>Data Element <Object Identifier> 1.3.6.1.4.1.1206.4.2.5.2.14.2.6"
],
null,
null,
null,
null
]
}