Tag Archives: HRIT

Some LNA tests for HRIT/LRIT

So I was talking with @luigi on OSP RocketChat and he noticed that one of the LNA’s I suggested alogn with the LNA4ALL (the SPF5189) got a comment on ebay saying that it doesn’t work on L Band.

So that was weird to me, since I have 5 of them, and one currently in use with my GOES setup. So I decided to do a small and crude benchmark for L Band comparing no LNA with LNA4ALL and SPF5189.

Continue reading

GOES 16 Test Week Results

In the week from March 27th to 31 NOAA performed some new downstream tests over HRIT link on GOES-16. The idea was to transfer some CMI (Cloud and Moisture Imaging) products and see if the software developers and current stations could receive it fine. Before starting talking about that, please notice that all data sent so far is stated as test data and should not be used for any real world measurements. As NOAA states (and I forwarded on my last post):

The user of that link assumes all risks related to the use of their data and NOAA disclaims and any and all warranties, whether express or implied, including (without limitation) any implied warranties of merchantability or fitness for a particular purpose.

So I kept my dish pointed to GOES-16 all over the week and did record the Monday testing (that contained CMI images) and recorded all files sent all over the week. Some of them are automatically posted on Twitter / Instagram by my OSP Bot but not all of them. I had discovered some issues with my Virtual Channel Ingestor on GOES Dump, and also most of the new data was not being handled correctly by Goes Dump. Working together with @usa_satcom we managed to almost zero-out the bugs in GOES Dump.

Continue reading

GOES 16 Test Week

Yesterday I received an email from NOAA (I’m on their “tester” list) about some tests on GOES-16 that will happen this week. Before I start talking about what will be the tests I want to be clear that GOES-16 is NOT operational yet and any data received from the LRIT/HRIT downlink are test only data. This means the user of that link assumes all risks related to the use of their data and NOAA disclaims and any and all warranties, whether express or implied, including (without limitation) any implied warranties of merchantability or fitness for a particular purpose.

So this week ( from 27th to 31th march ) HRIT will go into a new test phase that will send out DCS, Environmental Messages and charts through. They also will send from 16h to 20h UTC on Monday (27th) some CMI (Cloud and Moisture Imaging) data. That might be interesting for anyone that have a 1.5m+ dish that can run Linear Polarization at 1694MHz and be interested in trying out the super-alpha version of OpenSatelliteProject, that is already compatible to HRIT.

Please keep in mind that while OSP does support HRIT, it doesn’t mean it will support the new products coming out from HRIT link. They’re currently testing sending NetCDF files over HRIT, and so far OSP doesn’t support those. In normal case (no bugs) the output product should be stored in a folder named Unknown with the filename provided by NOAA. Regardless of that I will be trying to record the IQ / decoder output in the CMI period and run the OSP over all week in GOES-16.

While running in GOES-16 the Twitter / Instagram bots will not be outputing any GOES-13 data (sadly I only have one dish so far) but may output the products from GOES-16.

Some usefull links for you if you’re interested in more information:

GOES 16 in the house!

Few *times* ago I started to check on GOES 16 transmissions to see if I can get any data from it and make OpenSatelliteProject work with it. Me and @usa_satcom noticed that the HRIT signal was transmitting using differential encoding that was not predicted on NOAA’s HRIT Specification (You can check it here http://www.goes-r.gov/users/hrit-links.html ). So I decided to send an email to NOAA asking what was the current HRIT specs for GOES-16. Of course I expected no answer from them (they would probably be really busy with GOES-16 Testing), but surprisingly they answered sending the specs and saying that any feedbacks would be helpful and appreciated. So the HRIT indeed uses Differential Encoding (NRZ-M to be more specific). Knowing that I could start changing OpenSatelliteProject to be compatible with HRIT.

Continue reading