1 / 31

Emergency Data Distribution Network

Proposal to add an independent GOES DCS Reception and Distribution System to complement the NESDIS Wallops Island Facility Presented by Ernest Dreyer, USGS/WRD January 23, 2008. Emergency Data Distribution Network. Overview. Review EDDN project Provide a current status.

bdavid
Download Presentation

Emergency Data Distribution Network

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Proposal to add an independent GOES DCS Reception and Distribution System to complement the NESDIS Wallops Island Facility Presented by Ernest Dreyer, USGS/WRD January 23, 2008 Emergency Data Distribution Network

  2. Overview • Review EDDN project • Provide a current status

  3. EDDN Project GOALS • Receive data from all DCPs transmitting in the GOES DCS independently of Wallops Island. • Locate facility at a receive site(s) sufficiently distant from Wallops Island to achieve event independence. • Implement additional pilot signal at a location other than Wallops Island. • Distribute data independently of Wallops Island.

  4. STIWG/NESDIS Proposal • Locate the emergency distribution system at the USGS EROS Data Center in Sioux Falls, South Dakota. • USGS and NOAA/NESDIS will share the costs for procurement of the Direct Readout Ground Station system. • System will be primarily operated by USGS with support from NESDIS. • Operational costs will be shared among users who agree to participate and NESDIS.

  5. Limitations • Contains no system to • Make new assignments • Data will be acquired from any transmitting DCP and so an internal schedule will not be necessary. • Generate abnormal platform response messages - changed!!! • Messages will be checked for abnormal conditions as long as there is access to a PDT file.

  6. Limitations (cont.)‏ • Distribution will initially be over the Internet using the DDS protocol. • No DOMSAT transmissions • No direct land-lines • Depends on the existence of a usable pilot signal.

  7. Basic EDDN System • DRGS system with 2 antennas for GOES East and West ( at least 7M )‏ • DOMSAT system for data from Wallops Island • LRGS systems for acquiring and distributing data. • Web Server for reporting system status.

  8. Some Features required of theEDDN GOES Receive System • Receive both 100 and 300 baud messages on the same channel. • Support a backup pilot signal and be able to switch to the backup if the primary signal fails.

  9. Diagram of Proposed System

  10. System Monitoring • Use Big Brother system monitoring • Write Big Brother clients for monitoring • DRGSs via the DAMS NT event socket • LRGSs via system logs • Other events significant to the operations of system • Big Brother can • Display current status on web site • Send notifications to email groups • Page users

  11. System Control • After initial setup, system should operate with a minimum of operator intervention. • System will be remotely managed using a remote system console assisted by on-site support.

  12. Current Status of EDDN

  13. Calendar of Contract Events • Contract Awarded in July 2007 to Microcom Design Inc. • Contract began in Early August 2007. • Contract to be completed in February 2008.

  14. Status of EROS Installation • Antennas • GOES East: New 7.5M antenna has been installed. • GOES West: Existing 8.1M antenna has been refurbished. • DOMSAT: New 2.4M antenna has been installed. • Backup: Backup 3.8M antenna has been installed. • Cabling • All power cables have been installed. • All communications cables have been installed.

  15. Status of EROS Installation(cont)‏ • GOES Receivers • GOES Receivers are installed and receiving data from all domestic channels on GOES East and West. • To Be Done • Testing and fine tuning system will continue until final acceptance. • Operational training will occur during the last two weeks of February. • Integration into operational systems will begin in March.

  16. Installing Conduits

  17. Cabling from Warehouse to Main Building

  18. Hole for 7.5M Antenna Pad

  19. 7.5M Antenna for GOES West

  20. 7.5M Antenna for GOES West

  21. Three New Antennas

  22. 8.1M Antenna at EROS for GOES East

  23. GOES Receive Equipment at EROS

  24. EROS System Diagram

  25. Status Display on EROS LRGS

  26. Status of Other Related Activities • LRGS Software • Version 6.1 of LRGS software is being tested and refined. • Public EDDN Web Server • A Web server (lrgseddn1.cr.usgs.gov) is being constructed to provide: • Status of the public LRGSs • Access to Big Brother Monitoring Page • Server Pages that • Describe the EDDN • Describe message format • Describe how to obtain and install LRGS software • Make available relevant Documentation • Accessible mirror of the LRGS software source code repository

  27. Status of Other Related Activities • User Registration • A Synchronization scheme has been established to mirror user information for users registered on the NESDIS LRGS systems. • When scheme has been implemented, users already registered with NESDIS will automatically be registered with the EDDN system. • A proposal for a new format for user Ids is under consideration. • Note: Password authentication will be enabled.

  28. Status of Other Related Activities • User Access • EDDN system can be accessed in the same manner as the current LRGSs at Wallops. • For current LRGS users, if they upgrade to version 6.1, they can configure their LRGS to include the EDDN LRGSs as dynamic backups.

  29. <!-- #------------------------------------------------------------------ # Lrgs Configuration #------------------------------------------------------------------ # # This is an example LRGS configuration file. # # Data storage area archiveDir=/usr/opt/LRGS/archive numDayFiles=31 # Status snapshot interval htmlStatusSeconds=10 # DDS connections from other systems ddsListenPort=16003 ddsRequireAuth=false # DOMSAT configuration enableDomsatRecv=true domsatTimeout=60 loadDomsat=true domsatClass=lrgs.domsatrecv.DomsatSangoma # Remote DDS connections enableDdsRecv=true ddsRecvConfig=/usr/opt/LRGS/ddsrecv.conf recoverOutages=true mergePref1=DOMSAT mergePref2=DDS Example of LRGS Configuration

  30. <!-- This file holds the DDS Receiver Configuration. --> <ddsrecvconf> <connection number="1" host="lrgseddn2.cr.usgs.gov"> <name>lrgseddn2</name> <port>16003</port> <enabled>true</enabled> <username>usgs.wrd.va</username> <authenticate>true</authenticate> </connection> <connection number="2" host="cdadata.wcda.noaa.gov"> <name>CDADATA</name> <port>16003</port> <enabled>true</enabled> <username>usgs.wrd.va</username> <authenticate>true</authenticate> </connection> </ddsrecvconf> Example of DDS Configuration

More Related