CSPP-GEO key APID errors
Posted: Fri Jan 27, 2023 10:09 pm
Hi,
My CSPP-Geo/Geo2grid is working 24/24h since a quite long time and I wasn't checking much until the Holidays. I noticed that in my GRB.log files, I have quite often a lot of the following errors:
jvm 1 | 2023/01/27 16:59:01.027 | Should never happen, invalid product key:
jvm 1 | 2023/01/27 16:59:01.027 | [ERROR] (GRBReceiver) Unable to route packet for key APID: a1, last product time seen: 0x0a1_2023-01-27T21:56:17.341
And APID a1 is CONUS Channel 02 and here's result I always get, large missing block in the bottom right. (File attached for the corresponding image of the error in GRB.log)
I see also in GOES-16 Image Viewer of Star Nesdis that they get the same missing block like me but only on the True Color composite, not channel 02 which is weird as True Color is made from C01, C02 and C03. It's doing that for a lot of CONUS per day and it began at least in the december or before.
And, I also get about 4 to 6 completely missing C02 Mesos for Meso-1 and also Meso-2 so about 8 to 12 per day for both. But I can't see them as missing in Star Nesdis. Also, they don't miss when using GRBImager, a software from Brett Casebolt (N6BY). It began to happen regularly starting on November 28th 2022. So could it be that something changed on that date in the GRB stream that CSPP-Geo is not aware? The corresponding errors are:
For Meso-1 missing C02 channel:
jvm 1 | 2023/01/27 19:48:35.528 | Should never happen, invalid product key:
jvm 1 | 2023/01/27 19:48:35.528 | [ERROR] (GRBReceiver) Unable to route packet for key APID: c1, last product time seen: 0x0c1_2023-01-28T00:48:25.208
And for Meso-2 missing C02 channel:
jvm 1 | 2023/01/27 08:09:05.663 | Should never happen, invalid product key:
jvm 1 | 2023/01/27 08:09:05.663 | [ERROR] (GRBReceiver) Unable to route packet for key APID: e1, last product time seen: 0x0e1_2023-01-27T13:08:55.180
There's no bad CRC when that happens, it's not bad signal reception. And why always Channel 2? If it was random, I would missing a lot in Full Disk and CONUS due to the huge amount of data per hour for those sectors and why the whole image, not just little blocks?
Do you get both CONUS Channel 02 missing blocks and whole Meso-1 and Meso-2 sometimes missing channel 02 with cspp-geo on G-16? I know also someone that has the same large missing blocks in the bottom right in Conus Channel 02 on GOES-18 with CSPP-Geo. Please help. I would also like to see a 1 or 2 days log of your GRB.log at University of Wisconsin! Thanks!
Regards,
Luc
VE2FXL
My CSPP-Geo/Geo2grid is working 24/24h since a quite long time and I wasn't checking much until the Holidays. I noticed that in my GRB.log files, I have quite often a lot of the following errors:
jvm 1 | 2023/01/27 16:59:01.027 | Should never happen, invalid product key:
jvm 1 | 2023/01/27 16:59:01.027 | [ERROR] (GRBReceiver) Unable to route packet for key APID: a1, last product time seen: 0x0a1_2023-01-27T21:56:17.341
And APID a1 is CONUS Channel 02 and here's result I always get, large missing block in the bottom right. (File attached for the corresponding image of the error in GRB.log)
I see also in GOES-16 Image Viewer of Star Nesdis that they get the same missing block like me but only on the True Color composite, not channel 02 which is weird as True Color is made from C01, C02 and C03. It's doing that for a lot of CONUS per day and it began at least in the december or before.
And, I also get about 4 to 6 completely missing C02 Mesos for Meso-1 and also Meso-2 so about 8 to 12 per day for both. But I can't see them as missing in Star Nesdis. Also, they don't miss when using GRBImager, a software from Brett Casebolt (N6BY). It began to happen regularly starting on November 28th 2022. So could it be that something changed on that date in the GRB stream that CSPP-Geo is not aware? The corresponding errors are:
For Meso-1 missing C02 channel:
jvm 1 | 2023/01/27 19:48:35.528 | Should never happen, invalid product key:
jvm 1 | 2023/01/27 19:48:35.528 | [ERROR] (GRBReceiver) Unable to route packet for key APID: c1, last product time seen: 0x0c1_2023-01-28T00:48:25.208
And for Meso-2 missing C02 channel:
jvm 1 | 2023/01/27 08:09:05.663 | Should never happen, invalid product key:
jvm 1 | 2023/01/27 08:09:05.663 | [ERROR] (GRBReceiver) Unable to route packet for key APID: e1, last product time seen: 0x0e1_2023-01-27T13:08:55.180
There's no bad CRC when that happens, it's not bad signal reception. And why always Channel 2? If it was random, I would missing a lot in Full Disk and CONUS due to the huge amount of data per hour for those sectors and why the whole image, not just little blocks?
Do you get both CONUS Channel 02 missing blocks and whole Meso-1 and Meso-2 sometimes missing channel 02 with cspp-geo on G-16? I know also someone that has the same large missing blocks in the bottom right in Conus Channel 02 on GOES-18 with CSPP-Geo. Please help. I would also like to see a 1 or 2 days log of your GRB.log at University of Wisconsin! Thanks!
Regards,
Luc
VE2FXL