1 / 7

Goes DCS High Data Rate Transition Report

This report provides information on the status of high data rate channels and transmitters in the GOES DCS system. It also includes updates on low data rate channels and instructions for platform updates in DADDS.

thomasvhall
Download Presentation

Goes DCS High Data Rate Transition Report

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. Goes DCS High Data Rate Transition Report Wednesday, November 17, 2010 Gaithersburg, MD Letecia Reeves, GOES DCS Customer Service NOAA/NESDIS/OSPO

  2. High Data Rate/Auto Detect Channel Status • 88 HDR & 17 100/300 Auto Detect Channels • 37 - 300 baud Goes West • 39 - 300 baud Goes East • 6 - 1200 baud Goes West • 6 - 1200 baud Goes East • 5 – 100/300 Auto Detect Goes West • 12 – 100/300 Auto Detect Goes East

  3. High Data Rate Transmitters • 21,220 transmitters assigned to 300 baud • 16,420 are currently active • 1,294 transmitters assigned to 1200 baud • 525 are currently active • 2,370 transmitters assigned to Auto Detect • 1,530 are currently active

  4. Low Data Rate Channel Status • 70 LDR channels (not including random) • 44 - 100 baud Goes West • 35 - 100 baud Goes East • 5,440 100 baud Assignments • 2,930 Currently Active

  5. HDR Channel Assignment Status • Former International Channels opened up, allowing additional time slot availability • Continue your efforts in clearing off of the 100 baud channels. Turn in 100 baud assignments no longer utilizing.

  6. Platform Updates in DADDS • Batch files should include only the parameters that needs to be updated. For example, a batch file can be as short as… UPD PDT 1234ABCD & OWNER_ID = ABC123 & END

  7. Platform Updates Cont. • Batch files should be sent immediately after receiving requested IDs • Certain parameters can be updated by user • Currently the only way for POC to be entered into the database is by registering them.

More Related