[NOAAPORT #ZLV-851048]: LDM misses data on NOAAPORT via satellite

Hi,

re:
> Quick question to your list ldmd.conf for the LDM configuration EXEC lines
> 
> I see that you have a 224.0.1.6 multicast 

Correct.

re:
> the listing sheet that I have of
> the addresses does not have that one listed.

This was added by the NWS as a test for distributing NBM data in its own
channel.  The test is scheduled to end on December 8.

re:
> Therefore, I do not have a PID for the Novra receiver. 
> Can you tell me what the PIDs you have in your receiver or at least
> for this channel? 

The announcement of the test did not mention a different PID, only the
port 1206.  I was left assuming that they were/are not using a new
PID for the test.

re:
> Is there a current listing of these on the internet?

My searching for updated information has always indicated that a number
of the NOAA webpages that list information like this have not being updated
recently, so I can't give you a reference, sorry.

Here is the URL for a NOAA document dated October 26 that was an update
to the schedule for testing dissemination of the NBM fields in a separate
channel.

https://www.weather.gov/media/notification/pdf2/scn20-91sbn_channel_realignmentaaa.pdf

You will see that this document incorrectly refers to port numbers as PIDs.

Just so you can compare which PIDs you have your Novra S300N (or some other
DVBS2 unit) configure for, here is a 'cmcs' listing from one of our units:

CMCS 192.168.1.20> show pids

        MPE PIDs being processed:       101     102     103     104     105
                                        106     107     108     150     151

        PIDs being forwarded raw:

re:
> Also, is there a user's group for LDM that I can keep more up to date on
> some of these items?

New LDM releases are announced on the address@hidden email
list.  You can (un)subscribe to email lists that we maintain online at:

https://www.unidata.ucar.edu/support/index.html#mailinglists

They are also listed in the News section of our webpage:

https://www.unidata.ucar.edu

re:
> Thanks for your help thus far, I will work to implement these changes
> you mentioned Friday this coming week and report back after some testing.

OK, but, if the NWS follows their schedule, the NBM test should end 
on Monday.  Whether or not they will keep to this schedule is unknown
(after all, the start of the test was delayed).

Comment:

- we are going to leave the setup for port 1206 in the anticipation
  the NWS will declare the test successful and implement the distribution
  change permanently

- In reviewing the NOAAPort ingest log files, I note that the NBM products
  being distributed via port 1206 are being put into the HDS and
  IDS|DDPLUS feedtypes

  This is different from what was seen before the test, so I have to
  believe that there has been a change to the (header of) the products
  that is causing them to be inserted into the "wrong" (meaning
  unexpected) feedtypes.  These would not be the only products that
  are not following published standards for the information included
  in NOAAPort broadcast headers, so this was not shocking to me, at
  least.

I'll be on the lookout for your email.

Cheers,

Tom
--
****************************************************************************
Unidata User Support                                    UCAR Unidata Program
(303) 497-8642                                                 P.O. Box 3000
address@hidden                                   Boulder, CO 80307
----------------------------------------------------------------------------
Unidata HomePage                       http://www.unidata.ucar.edu
****************************************************************************


Ticket Details
===================
Ticket ID: ZLV-851048
Department: Support NOAAPORT
Priority: Normal
Status: Closed
===================
NOTE: All email exchanges with Unidata User Support are recorded in the Unidata 
inquiry tracking system and then made publicly available through the web.  If 
you do not want to have your interactions made available in this way, you must 
let us know in each email you send to us.