changes to GOES-18 GRB stream?

[rfnoise@gmail.com]

A couple of days ago, something changed on the GRB stream that my Novra S400 box receives. The S400 forwards all CADUs to CSPP GEO software for processing.

I first noticed the change when the CADUs/min changed from an average of 947 CADUs/min to something > 1500 CADUs/min. On the CSPP side i get periodic sequence errors and resulting image corruption as a result.

I'm posting this to simply understand if anyone else has experienced any issues with GOES-18 GRB this week.

I've included 2 screenshots of the monitoring software for the GRB/CADU stream so you can see the before and after events.

Thanks
Joe

[jbraun]

Hi Joe,

We have not seen any issues with GOES-18 this week on our processing machines here at SSEC/UW-Madison. Are you still dealing with issues impacting your processing? If so, have you checked for potential interference?

If you are still having problems or encounter issues in the future, please let us know either via the forum or email - csppgeo.issues@ssec.wisc.edu. We would appreciate any grb.log files as well as the time range and date you encounter these problems.

Thanks,
Jess

[rfnoise@gmail.com]

Hi Jess

Thanks for the reply. Today I rebooted my Novra S400pro box (again) and that seemed to clean up the issues as far as CSPPGEO software was concerned. However, there does seem to be a change in CADU rate that i cannot explain - it's still persists. Normally that would not be an issue, but the little ARM processor in the S400 is near or at 100% as a result of the increased CADU rate. Perhaps it is/was having trouble keeping up and was dropping packets (that would explain the sequence / counter errors in CSPP GEO).

I would be curious to see what others are seeing for CADU rates? Here is copy / paste from CSPPP GEO software log file.

469 + 582 + 839 = 1890

In the past, prior to this week, the average was 975.

[jbraun]

Hi Joe,

One of my colleagues took a look and while the numbers can fluctuate, the current CADU numbers you shared in your screenshot are similar to what we are and have been seeing consistently within our processing for quite some time. We are not aware of any immediate and/or recent changes to the CADU rate.

This is just one snipped from the logs from one of my colleagues:

Code: Select all

jvm 1    | 2024/01/10 18:12:16.531 | [INFO ] (CaduService) VCID5 (Right) CADUs per minute: 433
jvm 1    | 2024/01/10 18:12:16.531 | [INFO ] (CaduService) VCID6 (Left) CADUs per minute: 526
jvm 1    | 2024/01/10 18:12:16.531 | [INFO ] (CaduService) VCID63 (Idle) CADUs per minute: 931

~Jess

[rfnoise@gmail.com]

Jess

Thank you for the info. It seems that the source of the issue was indeed my s400 Novra box. The CPU was constantly at 100% leading to dropped / malformed packets. I solved the problem by going back to a previous version of the firmware and now CPU is running at < 70% and CADU packet rate is back to normal for my monitoring SW (that interfaces with the s400).

Thanks!
Joe