Would be nice if GLM could also be distributed through HRIT, but going to doubt it (at least for this year). They don't have it in the NOAAPORT stream (at least not yet), which further causes me to decrease the changes of it happening for now. The GLM data is small so wouldn't see why it couldn't. As of now, I know for sure GLM products will be going out soon on the GEONETCast Americas feed.
GOES 16 GRB downlink vs GVAR
- Thread starter GOES 12 GVAR user
- Start date
- Latest activity Latest activity:
- Replies 702
- Views 93K
Would be nice if GLM could also be distributed through HRIT, but going to doubt it (at least for this year). They don't have it in the NOAAPORT stream (at least not yet), which further causes me to decrease the changes of it happening for now. The GLM data is small so wouldn't see why it couldn't. As of now, I know for sure GLM products will be going out soon on the GEONETCast Americas feed.
You are right, the files are small. However, NOAA has a contract with 2 providers of lightning data that they send encrypted on noaaport right now. So putting free lightning data up on one of their feeds didnt go over well for the moment. I ingest it on the RCHP feed, and send the files over to the NOAAPORT ingest server using LDM. EDEX, NOAA's ingest app, is set up to decode and process them already. Word is they will be adding it to NOAAPORT at some point. It was suggested they put it on HRIT, but no promises have been made yet.
As to its performance, it is as good or better than the current commercial data out there, and updates from GOES every 20 seconds.
The custom firmware was sent by Ayecka, and it works, but it takes sometimes hours to lock. They want to sell TWO rack mounted receivers to receive GRB. VERY pricey. So the effort shifted to the PC cards from TBS, DD, and Omicom.
Im using the DD card and it works with both feeds at the same time fine. Has issues locking at first that we are working with the manufacturer. We have to pull the coax off and on to get it to lock. Once locked, its solid.
I wanted to put up some more data here.
So here's what I'm posting. I am putting up SDR screenshots comparing GOES R to GOES S.
First I want to state that my feed was having a problem due to a coax jumper. I have determined the measurements may be down by 10 dB in these pictures.
The hard truth of that can be seen in the image on page 2 post 26 when I did one of my first posts of the results with the SDR.
However when these two screenshots were taken the results were the same in the feed's working order so the outcome should be good.
I had a number of problems that day that resulted in a job that should have took an hour took 4 to complete.
First screenshot is of GOES S at an 8 dB C/N
Next is GOES R at an 7.8 dB C/N, the signal is at least 4-5 dB down over GOES S.
Will that coax issue change the outcome of the issues I've been having, I don't think so but I will be interested to see how the SDR looks now after it has been addressed.
So here's what I'm posting. I am putting up SDR screenshots comparing GOES R to GOES S.
First I want to state that my feed was having a problem due to a coax jumper. I have determined the measurements may be down by 10 dB in these pictures.
The hard truth of that can be seen in the image on page 2 post 26 when I did one of my first posts of the results with the SDR.
However when these two screenshots were taken the results were the same in the feed's working order so the outcome should be good.
I had a number of problems that day that resulted in a job that should have took an hour took 4 to complete.
First screenshot is of GOES S at an 8 dB C/N
Next is GOES R at an 7.8 dB C/N, the signal is at least 4-5 dB down over GOES S.
Will that coax issue change the outcome of the issues I've been having, I don't think so but I will be interested to see how the SDR looks now after it has been addressed.
You are showing only 2 MHz of spectrum which is not enough to estimate the SNR. To get the full GRB spectrum you need either an SDRPlay with 8 MHz bandwidth or an AirSpy with 10 MHz.
Keeping fingers crossed that replacing the bad coax cables will not give you a better signal.
Just as an alternative, I've posted below the link to a suite of SDR tools which includes a ported version of GQRX I use under LINUX. You might want to give it a shot as it could make it easier to discern the SNR.
pothosware/PothosSDR
Like N6BY mentioned, hopefully you can increase the input rate to something above 8MSPS to get the full spectrum.
Just as an alternative, I've posted below the link to a suite of SDR tools which includes a ported version of GQRX I use under LINUX. You might want to give it a shot as it could make it easier to discern the SNR.
pothosware/PothosSDR
Like N6BY mentioned, hopefully you can increase the input rate to something above 8MSPS to get the full spectrum.
Last edited:
I can agree with that. I can't be sure that HDSDR may be seeing more but don't display it. That's one of the drawbacks with HDSDR. I haven't tried any other software as they required newer OS's the what I'm using.
Could load up something on the Win 7 computer....
I figured that the results were reasonable showing a lower signal exp. with that cable issue.
How are you seeing GOES 17 Brett?
Thanks, We'll see soon as that cable is slated to be replaced, Though I can remember a signal no more then 8 dB C/N at any one time using the DVB-S2 receivers.
KWX in your screenshot it shows what looks like 2 signals. Are those both polarization's?
I'm curious to know what kind of signal you show from GOES 17 with Airspy.
Yeap, sure looks like two signals, but it is not... only RHCP. The grayed out signal peaking at 70 that you see is the peak in the signal level, so anytime there's data coming in, then you'll see it maxing out at that level. I'll be giving GOES 17 a look this week. If you can get 8dB then that's good. I know, before tweaking my system further, I was in the 8.3 avg range and with rain it would avg about 7.5 or so, which would still be well above the 6.4 no go value. Of course, we would like to see higher values but at least you'll be getting data instead of nothing. By the way, give the canantenna a shot, with the can I used, cause you never know.
In regards HDSDR, you can zoom out in order to see the whole bandwidth, assuming your SDR supports higher MSPS.
Thanks for the info
It may also have to do with the OS support.
I have some useful info from Jenn there at CSPP.
This is what I wanted to pass along but was waiting for permission to use the info.
Here's why I say I will need a 12' dish or more here.
There in Madison WI they use a 7.3 meter dish and get an 18 dB C/N.
When I did crunch some numbers it showed with what I already had the requirements that 12' dish will be needed here for GOES 16.
She also wanted me to pass along that James Mcnitt of NOAA can answer more questions related to this issue.
contact: james.mcnitt@noaa.gov
I think that is the email address.
Great, look forward to see what you get off of GOES 17.
8 dB C/N so far has only resulted in a 40% signal quality here so that for me hasn't been enough.
I've thought about it but the waveguide isn't the problem. I'll know more here when GOES 17 gets up and going.By the way, give the canantenna a shot, with the can I used, cause you never know.
I'm zoomed out look at the screenshots. My SDR must not support the wide bandwidth. 2 Megs is all I can get.
It may also have to do with the OS support.
I have some useful info from Jenn there at CSPP.
This is what I wanted to pass along but was waiting for permission to use the info.
Here's why I say I will need a 12' dish or more here.
There in Madison WI they use a 7.3 meter dish and get an 18 dB C/N.
When I did crunch some numbers it showed with what I already had the requirements that 12' dish will be needed here for GOES 16.
She also wanted me to pass along that James Mcnitt of NOAA can answer more questions related to this issue.
contact: james.mcnitt@noaa.gov
I think that is the email address.
Another round of tests are done here:
This is the final test for GOES 16 here with the 10' dish as I can't get any more out of it. Will need the 12 footer.
First info from GOES 17. Waiting for the GRB to go into full run. My last chance for the 10' dish to work.
This is the final test for GOES 16 here with the 10' dish as I can't get any more out of it. Will need the 12 footer.
First info from GOES 17. Waiting for the GRB to go into full run. My last chance for the 10' dish to work.
Are you able to receive RHCP or LHCP data through GRBstreamer on GOES16? Based on the info you've provided so far, you should be able to. On the bright side, you have enough dB to get you going while you work on upgrading the dish to get that higher SNR.
No, I haven't got any data off the streams. From what Brett said looking at the ts dumps, 40% signal quality is not enough for any good BBF's. He saw headers but that's all.
Yep, from what Brett and you have gotten there I should be able to get something but Nope. From what I see the signal doing I'm real close to be getting good data but it's outside of the 10' dish gain.
Both receivers (TBS, Omnicom) show a 40-42% max signal quality. So unless those 2 aren't working I should be getting honest results.
The TBS may have been too early discounted by me, it may yet work for this.
The only bright side here is that I know a 24' dish works near me in Madision WI.
I will be able to get something off of GOES 17 when it comes into operation or I have a major problem with something.
That's a nice looking commercial dish there. Should serve someone well. I already have two 12' dishes here. One mesh in use and a solid that's in my collection. That's an unbeatable offer.
I can confirm that GOES-17 GRB is on today, but they are sending 'fill frames'.
I replicated KWX's cookie can feed and was able to stream several thousand BBFrames this afternoon, but at a 5% error rate.
What's puzzling me is that I can lock and stream GRB with the SNR in the low 7's. But after additional fine tuning of the dish and getting the SNR up to 8.1, it would neither lock nor stream.
Below is a spectrum capture that I just made of GOES-17. GRB is strong and steady, along with HRIT and the telemetry signals.
Users Who Are Viewing This Thread (Total: 0, Members: 0, Guests: 0)
Who Read This Thread (Total Members: 48)
- GOES 12 GVAR user
- N6BY
- clucas
- waylew
- mc6809e
- catamount
- K3dmurphy
- a33
- cyberham
- Mr Tony
- FTA4PA
- b4pjoe
- stecle
- freddylq
- one_db_compression
- primestar31
- mr_rye89
- Grashoper
- wds657
- DangerousDyke
- ghulands
- caramel
- Arion
- jorgek
- lonelyfool123
- juventusbrown
- N5XZS
- Elsguy
- c-spand
- brice52
- PrunePicker
- Alexrules11
- arlo
- wagonman76
- weather01089
- byron
- Titanium
- phlatwound
- Lajaba
- kps
- WhyLow
- tgro870
- fireball517
- DarrylZ
- voomvoom
- JD1003
- JFOK
- Claudio Max
