NOTICE: This version of the NSF Unidata web site (archive.unidata.ucar.edu) is no longer being updated.
Current content can be found at unidata.ucar.edu.
To learn about what's going on, see About the Archive Site.
This is with a 7.3m dish, although we have the signal split two ways (we have a primary and backup receiver).
With the S300 on the DVB-S2 signal (1154.15 MHz), I get the following: Signal Lock: On Data Lock: On Uncorrectable Rate: 0/Second Packet Error Rate: 0.0000e+00 Carrier to Noise C/N: 13.1dB Signal Strength: -50 dBm With the DVB-S signal, we get the following with the S300: Signal Lock: On Data Lock: On Uncorrectable Rate: 0/Second Viterbi Bit Error Rate: 1.0000e+01 Carrier to Noise C/N: 17.7dB Signal Strength: -48 dBm ldmd log error example:Apr 27 15:46:45 dvb2 readnoaaport[18989] ERROR: Missing fragment in sequence, last 2/53233140 this 4/53233140 Apr 27 15:46:45 dvb2 readnoaaport[18989] ERROR: Missing fragment in sequence, last 3/53233141 this 5/53233141 Apr 27 15:46:45 dvb2 dvbs_multicast[18988] ERROR: Gap in SBN last 57406505, this 57406507 Apr 27 15:46:46 dvb2 dvbs_multicast[18988] ERROR: Gap in SBN last 57406522, this 57406524 Apr 27 15:46:46 dvb2 dvbs_multicast[18988] ERROR: Gap in SBN last 57406530, this 57406532 Apr 27 15:46:46 dvb2 readnoaaport[18989] ERROR: Missing fragment in sequence, last 5/53233142 this 7/53233142 Apr 27 15:46:46 dvb2 readnoaaport[18989] ERROR: Missing fragment in sequence, last 11/53233143 this 13/53233143 Apr 27 15:46:46 dvb2 readnoaaport[18989] ERROR: Missing fragment in sequence, last 5/53233144 this 7/53233144 Apr 27 15:46:46 dvb2 dvbs_multicast[18988] ERROR: Gap in SBN last 57406555, this 57406557 Apr 27 15:46:47 dvb2 dvbs_multicast[18988] ERROR: Gap in SBN last 57406574, this 57406576 Apr 27 15:46:47 dvb2 dvbs_multicast[18988] ERROR: Gap in SBN last 57406581, this 57406583 Apr 27 15:46:47 dvb2 dvbs_multicast[18988] ERROR: Gap in SBN last 57406585, this 57406587 Apr 27 15:46:47 dvb2 dvbs_multicast[18988] ERROR: Gap in SBN last 57406598, this 57406600
Gilbert Sebenste wrote:
On Sat, 23 Apr 2011, Gilbert Sebenste wrote:Jose Nieves and I have been able to reproduce a bug where if the NOAAPort broadcast goes down for a significant amount of time (say 30 minutes), the Novra S-300 locks up and needs a hard reboot (unplug) to get it working inDVB-S2 mode. I have not tried to check this with the unit in DVB-S receive mode. More specifically, if you tune the receiver to anon-functioning frequency while in DVB-S2 mode, the S-300 will eventuallylock up. Just an FYI.I forgot to mention...I notified Novra's engineers, and they got back to me today (Saturday) saying they will look into it.Also, it appears as though it doesn't completely become unresponsive, but can take over a minute to access it with constant, repeated triesObviously, that's not good.In any case, for those of you running S-300s, could any of you do me favor? I am still getting a ton of dropped packets with a carrier to noiseabove 14 and a signal level of -44 dBm. I'd like to know if anyone is seeing the same thing. At least one entity is getting very good reception since the DVB-S2 broadcast moved to 1154.150 MHZ.*******************************************************************************Gilbert Sebenste ******** (My opinions only!) ****** Staff Meteorologist, Northern Illinois University **** E-mail: sebenste@xxxxxxxxxxxxxxxxxxxxx *** web: http://weather.admin.niu.edu *********************************************************************************_______________________________________________ noaaport mailing list noaaport@xxxxxxxxxxxxxxxxFor list information or to unsubscribe, visit: http://www.unidata.ucar.edu/mailing_lists/
-- ________________________________________________________ John Lalande University of Wisconsin-Madison Space Science & Engineering Center 1225 W. Dayton Street, Room 439, Madison, WI 53706 608-263-2268 / john.lalande@xxxxxxxxxxxxx
noaaport
archives: