Status in source: mandatory.
Technical details
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"dcmMEStatus",
"OBJECT-TYPE",
"SYNTAX",
"INTEGER",
"{",
"other",
"(",
"1",
")",
",",
"error",
"(",
"2",
")",
",",
"validating",
"(",
"3",
")",
",",
"monitorMode1On",
"(",
"4",
")",
",",
"monitorMode2On",
"(",
"5",
")",
",",
"idle",
"(",
"6",
")",
"}",
"ACCESS",
"read-only",
"STATUS",
"mandatory",
"DESCRIPTION",
"\"Indicates the status of this study. The values are: - other (1) = Not defined below. - error (2) = There was an error in the ‘Monitor Study’ found by the device when it was commanded to enable a Monitor Mode. Check the dcm Error Code Table (dcmErrCodeTable) for more information regarding the error. - validating (3) = The device is currently validating the configured study. The device can only be in this state if the value of the dcmDREControl object has been set to ‘validate’ or a Monitor Mode was enabled. - monitorMode1On (4)= Indicates that the device has successfully enabled Monitor Mode 1. Monitor Mode 1 is an asynchronous mode of operation where the device shall asynchronously stream out data packets (as defined by the ‘Data’ field in the Data Structure Table for the specified study) without any protocol wrapper. The time between the device sending each data packet is defined by dcmMETimeInterval. This mode should only be enabled in a point to point communications architecture since there is no protocol wrapper around the streamed data. This mode has been included for compatibility with existing systems. - monitorMode2On (5) = Indicates that the device has successfully enabled Monitor Mode 2. Monitor Mode 2 is a synchronous mode of operation in which each data packet must be polled for by the application. The encoding of each data packet shall be defined by the ‘Data’ field of the Data Structure Table for the specified type of study) The dcmMEPollNow column in this row shall be used to poll for each data packet. Each time the application performs a ‘Get’ on the dcmMEPollNow column, the device shall respond by sending a data packet. The data packet shall contain all of the associated data from the time of the last poll up to the current time. - idle (6) = No Monitor Modes are enabled.\"",
"::=",
"{",
"dcmMEEntry",
"6",
"}"
],
"syntax_tree": [
[
"SimpleSyntax",
"INTEGER",
[
"enumSpec",
[
[
"other",
1
],
[
"error",
2
],
[
"validating",
3
],
[
"monitorMode1On",
4
],
[
"monitorMode2On",
5
],
[
"idle",
6
]
]
]
],
null,
[
"MaxAccessPart",
"read-only"
],
[
"Status",
"mandatory"
],
[
"DESCRIPTION",
"Indicates the status of this study. The values are: - other (1) = Not defined below. - error (2) = There was an error in the ‘Monitor Study’ found by the device when it was commanded to enable a Monitor Mode. Check the dcm Error Code Table (dcmErrCodeTable) for more information regarding the error. - validating (3) = The device is currently validating the configured study. The device can only be in this state if the value of the dcmDREControl object has been set to ‘validate’ or a Monitor Mode was enabled. - monitorMode1On (4)= Indicates that the device has successfully enabled Monitor Mode 1. Monitor Mode 1 is an asynchronous mode of operation where the device shall asynchronously stream out data packets (as defined by the ‘Data’ field in the Data Structure Table for the specified study) without any protocol wrapper. The time between the device sending each data packet is defined by dcmMETimeInterval. This mode should only be enabled in a point to point communications architecture since there is no protocol wrapper around the streamed data. This mode has been included for compatibility with existing systems. - monitorMode2On (5) = Indicates that the device has successfully enabled Monitor Mode 2. Monitor Mode 2 is a synchronous mode of operation in which each data packet must be polled for by the application. The encoding of each data packet shall be defined by the ‘Data’ field of the Data Structure Table for the specified type of study) The dcmMEPollNow column in this row shall be used to poll for each data packet. Each time the application performs a ‘Get’ on the dcmMEPollNow column, the device shall respond by sending a data packet. The data packet shall contain all of the associated data from the time of the last poll up to the current time. - idle (6) = No Monitor Modes are enabled."
],
null,
null,
null,
null
]
}
- NTCIP published standard MIB annexes (reviewed modules)
· Publisher's source file: NTCIP 1206:2005, Object Definitions for Data Collection and Monitoring (DCM) Devices Published November 2005 — original PDF
· Official record
Module: DCM-MIB1
See published definition above
Module imports
{'TMIB-II': ['devices'], 'RFC-1212': ['OBJECT-TYPE'], 'RFC1155-SMI': ['Counter']}Source data warning: Recovered from a file whose complete MIB does not parse. The original assignment and definition are preserved. Registration and implementation details may be inaccurate; consult the original file. Other damaged or unresolved declarations are not established registrations.
Source data warning: This record is transcribed from a published NTCIP MIB annex. The downloadable text is a derived transcription with page furniture and section headings masked; the unmodified original PDF is authoritative. Native definitions, DESCRIPTION and STATUS are retained. A published object definition does not establish support by any particular device.
Source data warning: A typographic closing DESCRIPTION quotation delimiter occurs immediately at a native SMI field boundary. Normalize this delimiter only in the derived transcription; retain the literal published definition, full description and unchanged numeric assignments.
Source data warning: A typographic closing quotation mark terminates a DESCRIPTION in this PDF. Normalize that delimiter only in the derived MIB transcription; preserve the literal published definition and unmodified PDF. No numeric assignment changes.
Source data warning: A typographic opening DESCRIPTION quotation delimiter occurs immediately at a native SMI field boundary. Normalize this delimiter only in the derived transcription; retain the literal published definition, full description and unchanged numeric assignments.
Source data warning: Potentially inaccurate interpretation of historical NTCIP namespace references: TMIB-II. These exact source files require the reviewed bindings shown below. The numeric roots used here are the explicit assignments in normative Annex A.2 of published NTCIP 8004 v02 (2010), physical pages 43–44. This does not establish that every historical module revision is identical. The annex also prints enterprise instead of RFC 1155 enterprises and declares Protocols while referencing protocols; those spelling interpretations are disclosed. The original IMPORTS, numeric suffixes and definitions remain unchanged. Verify both originals before implementation.
· Download NTCIP1206v0123f.pdf — DCM-MIB1 (MIB transcription)
Related source files and packages:
Show more related files and packages
- NTCIP published standard MIB annexes (reviewed modules)
· Publisher's source file: NTCIP 1206:2005, Object Definitions for Daqta Collection and Monitoring (DCM) Devices Published November 2005 (superceded by NTCIP 1206 v02) — original PDF
· Official record
Module: DCM-MIB1
Same published definition
Module imports
{'TMIB-II': ['devices'], 'RFC-1212': ['OBJECT-TYPE'], 'RFC1155-SMI': ['Counter']}Source data warning: Recovered from a file whose complete MIB does not parse. The original assignment and definition are preserved. Registration and implementation details may be inaccurate; consult the original file. Other damaged or unresolved declarations are not established registrations.
Source data warning: This record is transcribed from a published NTCIP MIB annex. The downloadable text is a derived transcription with page furniture and section headings masked; the unmodified original PDF is authoritative. Native definitions, DESCRIPTION and STATUS are retained. A published object definition does not establish support by any particular device.
Source data warning: A typographic closing DESCRIPTION quotation delimiter occurs immediately at a native SMI field boundary. Normalize this delimiter only in the derived transcription; retain the literal published definition, full description and unchanged numeric assignments.
Source data warning: A typographic closing quotation mark terminates a DESCRIPTION in this PDF. Normalize that delimiter only in the derived MIB transcription; preserve the literal published definition and unmodified PDF. No numeric assignment changes.
Source data warning: A typographic opening DESCRIPTION quotation delimiter occurs immediately at a native SMI field boundary. Normalize this delimiter only in the derived transcription; retain the literal published definition, full description and unchanged numeric assignments.
Source data warning: Potentially inaccurate interpretation of historical NTCIP namespace references: TMIB-II. These exact source files require the reviewed bindings shown below. The numeric roots used here are the explicit assignments in normative Annex A.2 of published NTCIP 8004 v02 (2010), physical pages 43–44. This does not establish that every historical module revision is identical. The annex also prints enterprise instead of RFC 1155 enterprises and declares Protocols while referencing protocols; those spelling interpretations are disclosed. The original IMPORTS, numeric suffixes and definitions remain unchanged. Verify both originals before implementation.
· Download NTCIP1206v0123f-1.pdf — DCM-MIB1 (MIB transcription)
Related source files and packages: