Status in source: optional.
Technical details
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"dcmReset",
"OBJECT-TYPE",
"SYNTAX",
"INTEGER",
"{",
"other",
"(",
"1",
")",
",",
"hardReset",
"(",
"2",
")",
",",
"softReset",
"(",
"3",
")",
",",
"commReset",
"(",
"4",
")",
",",
"factoryReset",
"(",
"5",
")",
",",
"userReset",
"(",
"6",
")",
",",
"tableClear",
"(",
"7",
")",
"}",
"ACCESS",
"read-write",
"STATUS",
"optional",
"DESCRIPTION",
"\"indicates the different types of resets that may be issued to the dcm device. The values and their meaning are: 1=Other 2=Hard Reset - (restart program, reset comms, clear all user settings, reset sensor boards, reset keyboard/display, reset cpu program memory, does not clear data files, resets to all factory defaults, stops current recording study) 3=Soft Reset - (restart program, does not reset comms, does not change user settings, does not reset sensor boards, resets keyboard/display, resets cpu program memory, does not clear data files, does not reset to factory defaults, stops current recording study) 4=Comms Reset - Resets the comms channel used to communicate with the field unit to user defaults. - It is recommended that all required elements are resynched by the dcm device to ensure that communications is not lost with the dcm unit (e.g. modem). 5=Factory Reset - User settings consist of all structures that can be written to. - Resets all user settings to factory defaults. 6=User Reset - Which objects/tables to reset and the values to reset them to is configured by the dcmURCTTable 7=Table Clear - The clear operation is based on the dcmTableClearTable \"",
"::=",
"{",
"dcmOpsStatus",
"1",
"}"
],
"syntax_tree": [
[
"SimpleSyntax",
"INTEGER",
[
"enumSpec",
[
[
"other",
1
],
[
"hardReset",
2
],
[
"softReset",
3
],
[
"commReset",
4
],
[
"factoryReset",
5
],
[
"userReset",
6
],
[
"tableClear",
7
]
]
]
],
null,
[
"MaxAccessPart",
"read-write"
],
[
"Status",
"optional"
],
[
"DESCRIPTION",
"indicates the different types of resets that may be issued to the dcm device. The values and their meaning are: 1=Other 2=Hard Reset - (restart program, reset comms, clear all user settings, reset sensor boards, reset keyboard/display, reset cpu program memory, does not clear data files, resets to all factory defaults, stops current recording study) 3=Soft Reset - (restart program, does not reset comms, does not change user settings, does not reset sensor boards, resets keyboard/display, resets cpu program memory, does not clear data files, does not reset to factory defaults, stops current recording study) 4=Comms Reset - Resets the comms channel used to communicate with the field unit to user defaults. - It is recommended that all required elements are resynched by the dcm device to ensure that communications is not lost with the dcm unit (e.g. modem). 5=Factory Reset - User settings consist of all structures that can be written to. - Resets all user settings to factory defaults. 6=User Reset - Which objects/tables to reset and the values to reset them to is configured by the dcmURCTTable 7=Table Clear - The clear operation is based on the dcmTableClearTable"
],
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: