Status in source: optional.
Technical details
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"genEquipmentControl",
"OBJECT-TYPE",
"SYNTAX",
"INTEGER",
"{",
"stopGenerator",
"(",
"1",
")",
",",
"startGenerator",
"(",
"2",
")",
",",
"resetLatchedAlarms",
"(",
"3",
")",
"}",
"ACCESS",
"read-write",
"STATUS",
"optional",
"DESCRIPTION",
"\"When written, the appropriate corresponding command action is sent to the generator. 1 = End generator test 2 = Start generator test 3 = Reset latched generator alarms which may be preventing a generator start This object is intentionally simplistic to allow for maximum flexibility. It IS assumed that the generator has sufficient intelligence to prevent an overcrank condition. Example 1: From a single SET and corresponding single 'start' command, the generator may automatically attempt starting 'n' times before giving up. Example 2: The transponder may be simple and send only the single 'start' command, and the EMS/end user is responsible for making 'n' attempts (by performing additional SETs to this object.) The choice between the methods depends on the specific application and vendor equipment.\"",
"::=",
"{",
"genDeviceEntry",
"22",
"}"
],
"syntax_tree": [
[
"SimpleSyntax",
"INTEGER",
[
"enumSpec",
[
[
"stopGenerator",
1
],
[
"startGenerator",
2
],
[
"resetLatchedAlarms",
3
]
]
]
],
null,
[
"MaxAccessPart",
"read-write"
],
[
"Status",
"optional"
],
[
"DESCRIPTION",
"When written, the appropriate corresponding command action is sent to the generator. 1 = End generator test 2 = Start generator test 3 = Reset latched generator alarms which may be preventing a generator start This object is intentionally simplistic to allow for maximum flexibility. It IS assumed that the generator has sufficient intelligence to prevent an overcrank condition. Example 1: From a single SET and corresponding single 'start' command, the generator may automatically attempt starting 'n' times before giving up. Example 2: The transponder may be simple and send only the single 'start' command, and the EMS/end user is responsible for making 'n' attempts (by performing additional SETs to this object.) The choice between the methods depends on the specific application and vendor equipment."
],
null,
null,
null,
null
]
}