DCP Message Status
Updated:
# Hours Fetched: Missing:
LOW BATTERY
Parity:
Partial:
Complete:
Parity: Location that contains an M (missing) in the Data portion of the message.
Partial: Location that has less than 24 hours of messages
Missing: Location that did not have a ANY messages (0) in the last 24 hours
Complete: Location with 24 or more messages
Reservoirs: Location that is considered a water reservoir - Can exist in one of the other 4 categories
# Hours Fetched: Missing:
LOW BATTERY
Parity:
Partial:
Complete:
Total Locations:
of these DCP are Reservoirs
of these DCP are Reservoirs
Click a row to expand Locations
Tap & Drag to Scroll
Legend
Parity: Location that contains an M (missing) in the Data portion of the message.
Partial: Location that has less than 24 hours of messages
Missing: Location that did not have a ANY messages (0) in the last 24 hours
Complete: Location with 24 or more messages
Reservoirs: Location that is considered a water reservoir - Can exist in one of the other 4 categories
- Glyphs Breakdown: (Note Column, etc)
- : Random Message : Message transmitted outside the regular hourly interval on a different channel than normal
- : Unknown Message : This is a message that did NOT have a channel set for goes-random or goes-self-timed
- : Parity Message : Message did not transmit properly
- * : Messages were found for this location, but the NESS ID did not match the netlist.
- * : Missing Transmission
- Purpose: This web page is intended to provide a quick look into the status of various Data Collection Platforms (DCP) that the Tulsa District Corps of Engineers uses.
- Locations that have more than 24 messages might have received a random/or other form of transmission during the last 24 hours. Check the message Time Rec to see if it is irregular.
- To Search: Enter the first 4 letters of a project, the SHEF ID (5 Letter), or the NESS ID (8 Character) into the search box. I.E. Keystone would be KEYS, Ft. Gibson would be FGIB, and Denison would be DENI. Click Reset to return to the search box.
- The numbers (##) before the Message Count show the count of missing data (M's) in a Parity Message.
- Locations listed in Parity Message with NO (##) had an unknown ARM (?), but no missing data (M).
- LOW BATTERY messages appear on a block when one of the hourly transmissions had a VB, BL, or YB greater than 0.00 and less than 10.99 volts.
-
You can share gages by appending ?dcp=ALTID/SHEFID/NESSID to the end of the web address.
- For Example:
-
Share Keystone Lake
ALT ID: https://wm.swt.ds.usace.army.mil/dcpstatus?dcp=KEYS
SHEF ID: https://wm.swt.ds.usace.army.mil/dcpstatus?dcp=KEYO2
NESS ID: https://wm.swt.ds.usace.army.mil/dcpstatus?dcp=CE609B50
-
Share Keystone Lake
- Pay attention to where your finger/cursor is when scrolling. Place it where you want
to scroll.
- For Example:
- If you mouse over the expanded data it will scroll within that box.
- If you mouse over the far right outside of that box it will scroll the entire page.
- If you continue to scroll at the end of a data set (DCP Messages), the entire page will start to scroll.
- Keybinds! You can now press Backspace or Escape to click the "Reset" button. This closes tabs and returns you to the top with a focus on the input.
- For Example:
- Type KEYS in search, press ENTER - read what you need
- Press BACKSPACE, returns to top and focuses input
- Type FGIB in search, press ENTER - read a new gages data
- Repeat!
Notes: