Status in source: mandatory.
Names: rmcPassageCtrlEntry
Technical details
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"rmcPassageCtrlEntry",
"OBJECT-TYPE",
"SYNTAX",
"RmcPassageCtrlEntry",
"ACCESS",
"not-accessible",
"STATUS",
"mandatory",
"DESCRIPTION",
"\"Configuration and control parameters of the passage detector table. The number of rows within this table must be the same as within the Metered Lane Configuration Table. If this table is supported, there shall be a passage detector for each metered lane. The rows within this table cannot be managed following the same principles applied to other tables. It is anticipated that, if passage detectors are utilized within an implementation, each metered lane will have one passage detector. However, not every metered lane might have a physical passage detector and must therefore be set into 'recalled' using the rmcPassageMode object in order to utilize the passage detection functionality.\"",
"INDEX",
"{",
"rmcMeterNumber",
"}",
"::=",
"{",
"rmcPassageCtrlTable",
"1",
"}"
],
"syntax_tree": [
[
"row",
"RmcPassageCtrlEntry"
],
null,
[
"MaxAccessPart",
"not-accessible"
],
[
"Status",
"mandatory"
],
[
"DESCRIPTION",
"Configuration and control parameters of the passage detector table. The number of rows within this table must be the same as within the Metered Lane Configuration Table. If this table is supported, there shall be a passage detector for each metered lane. The rows within this table cannot be managed following the same principles applied to other tables. It is anticipated that, if passage detectors are utilized within an implementation, each metered lane will have one passage detector. However, not every metered lane might have a physical passage detector and must therefore be set into 'recalled' using the rmcPassageMode object in order to utilize the passage detection functionality."
],
null,
null,
[
"INDEX",
[
[
0,
"rmcMeterNumber"
]
]
],
null
]
}