Subject: Product Outage/Anomaly:(Update #3) NOAA-15 AVHRR Global This is a multi-part message in MIME format. --Boundary_(ID_ekIl+F7f02DcOnAC+O7KIA) Content-type: text/plain; charset=windows-1252; format=flowed Content-transfer-encoding: 8BIT *Update #3:* The resync command was loaded into the stored command table and sent 4 times per day starting on April 20, 2018, results were still inconclusive. The corrupted imagery may have cleared shortly after the resync commands were sent, however it this effect lasts, sometimes several orbits, sometimes one orbit. Engineering has now increased the resync to once an orbit at the acceding node starting on April 26, 2018, it has partially corrected the problem, though some barcoding is still present (less than 1 orbit in 14 per day). Investigation continues. Current status can be found at: https://www.star.nesdis.noaa.gov/icvs/status_N15_AVHRR.php *Update #2*The manual resync was tested on April 17, 2018 at ~1544 UTC.The test was inconclusive as the resync was sent during a period when the global imaging was relatively uncorrupted. Engineering plans on having the resync command loaded in the stored command table and sent 3 times a day to see if there *Update #1*The N15 AVHRR global imaging continues to be corrupted, however the issue appears to periodically correct itself at 0730Z daily and remain that way for several orbits afterward. This has been determined to likely be caused by the daily at that time. Therefore, sending the correct this issue. This will be tested by engineering on April 17, 2018 at ~1410Z. *Topic:*NOAA-15 AVHRR Global Image Outage *Date/Time Issued:*April 30, 2018 2248Z *Product(s) or Data Impacted:*AVHRR Imaging Products *Date/Time of Initial Impact:*April 12, 2018 0000Z *Impacts on Users and Significance:*AVHRR imaging products have been impacted. *Date/Time of Expected End:*April 13, 2018 1130Z *Length of Outage:*~36 Hours *Details/Specifics of Change:* The N15 AVHRR global imaging became corrupted on April 12 at ~0000Z due to sync issues. This may be caused by erratic scan motor current due to loss of lubricant. The problem appears to have corrected itself, as the global image is no longer corrupted. The issue is still under investigation. *Contact Information for Further Information:*ESPC Operations at ESPCOperations@noaa.gov at 301-817-3880 __and/or other contacts as necessary *Web Site(s) for applicable information:*N/A This message was sent to ESPC.Notification@noaa.gov . You have been sent this and other notifications because you have opted in to receive it. If for any reason, you wish to unsubscribe, please contact ESPC Help Desk at ESPCOperations@noaa.gov or (301) 817-3880 . Please note: it make take up to two business days to process your unsubscribe request. --Boundary_(ID_ekIl+F7f02DcOnAC+O7KIA) Content-type: text/html; charset=windows-1252 Content-transfer-encoding: 8BIT

Update #3: loaded into the stored command table and sent 4 times per day starting on April 20, 2018, results were still inconclusive. The corrupted imagery may have cleared shortly after the resync commands were sent, however it effect lasts, sometimes several orbits, sometimes one orbit. Engineering has now increased the resync to once an orbit at the acceding node starting on April 26, 2018, it has partially corrected the problem, though some barcoding is still present (less than 1 orbit in 14 per day). Current status can be found at: https://www.star.nesdis.noaa.gov/icvs/status_N15_AVHRR.php<

Update #2 The manual resync was tested on April 17, 2018 at ~1544 UTC. The test was inconclusive as the resync was sent during a period when the global imaging was relatively uncorrupted. on having the resync command loaded in the stored command table and sent 3 times a day to see if there improvement. Investigation continues.

Update #1 The N15 AVHRR global imaging continues to be corrupted, however the issue appears to periodically correct itself at 0730Z daily and remain that way for several orbits afterward. This has been determined to likely be caused by the sent daily at that time. Therefore, sending the command every orbit may correct this issue. This will be tested by engineering on April 17, 2018 at ~1410Z.

Topic: style="font-size: 12.0pt;line-height:115%;font-family:"Times New Roman","serif";mso-fareast-font-family: "Times New Roman";color:#222222">NOAA-15 AVHRR Global Image Outage

Date/Time Issued: style="font-size: 12.0pt;line-height:115%;font-family:"Times New Roman","serif";mso-fareast-font-family: "Times New Roman";color:#222222">April 30, 2018 2248Z

Product(s) or Data Impacted: AVHRR Imaging Products

Date/Time of Initial Impact: style="font-size:12.0pt;line-height:115%;font-family:"Times New Roman","serif"; mso-fareast-font-family:"Times New Roman";color:#222222">April 12, 2018 0000Z

Impacts on Users and Significance: style="font-size:12.0pt;line-height:115%;font-family:"Times New Roman","serif"; mso-fareast-font-family:"Times New Roman";color:#222222">AVHRR imaging products have been impacted.

Date/Time of Expected End: style="font-size: 12.0pt;line-height:115%;font-family:"Times New Roman","serif";mso-fareast-font-family: "Times New Roman";color:#222222">April 13, 2018 1130Z

Length of Outage: style="font-size: 12.0pt;line-height:115%;font-family:"Times New Roman","serif";mso-fareast-font-family: "Times New Roman";color:#222222">~36 Hours

Details/Specifics of Change:

The N15 AVHRR global imaging became corrupted on April 12 at ~0000Z scan motor current due to loss of lubricant. The problem appears to have corrected itself, as the global image is no longer corrupted. The issue is still under investigation.

Contact Information for Further Information: ESPC Operations at ESPCOperations@noaa.gov at 301-817-3880 and/or other contacts as necessary

Web Site(s) for applicable information: N/A

This message was sent to ESPC.Notification@noaa.gov. have been sent this and other notifications because you have opted in to receive it. If for any reason, you wish to unsubscribe, please contact ESPC Help Desk at ESPCOperations@noaa.gov or (301) 817-3880. note: it make take up to two business days to process your unsubscribe request.





--Boundary_(ID_ekIl+F7f02DcOnAC+O7KIA)--