Technical Support for Environmental Data Collection Software
Views: 451
Attachments: 0
Related Articles: 0
Feedback: 0
Helpful: 0
Not Helpful: 0
File Attachments
No attachments were found.

PDI NOAAPORT Receiver How-To

  • Author: Michael Maloney
  • Create Time: 01/30/2013 17:30:03
  • Last Update Time: 02/04/2013 14:13:47
 This article describes how to configure your LRGS for data reception with a PDI (Planetary Data Inc) NOAAPORT Receiver.

PDI is supported with LRGS Version 8.2 and later. Update your LRGS if necessary.

Confure the LRGS

The PDI configuration is similar to the configuration for the Marta Systems receiver in that the LRGS will listen for socket connections. The receiver will connect and start sending data. The difference is in the format of the data sent over the socket.

A sample configuration is as follows:


Select PDI for receiver type. If this is not in the list, update the client software you are using to connect to your LRGS, and then restart the real-time status display (e.g. with the "rtstat" command).

The default port for PDI is 18000.

Optionally you can enter the name of a "capture file". If this field is non-blank then every time the receiver (or anyone else) connects on port 18000 a file will be created with this name and a time-stamp extension (in the format yyyymmdd-hhmmss). This feature is for trouble-shooting only and you should disable it by blanking this field after the interface is working.

Save these changes, and exit the real-time status GUI.

Alternatively, you can configure the properties directly in the "lrgs.conf" file:
  noaaportEnabled=true
  noaaportCaptureFile=noaaport-cap
  noaaportReceiverType=PDI
  noaaportPort=1800

After changing the configuration (either manually or through GUI), you must restart the LRGS before the changes will take affect. To do this:

  cd $LRGSHOME
  rm lrgs.lock
(wait about 20 seconds)
  bin/startLRGS


Configure the PDI NOAAPORT Receiver

These instructions are provided by Stonie Cooper at PDI.

Look at the example file I provided, DCPdistribution.config-example.
The actual file you want to edit is a non-linked copy of /etc/pdinrs/DCPdistribution.config to follow this example.  If it is currently a link, copy the master to it and break the link - you do not want ot apply these changes to /etc/pdinrs/default/altDistribution.config.  Towards the top of the file, but after "distribution", you can add the example entry:

# Planetary Data, Incorporated; copyright 1998-2013
# file = Genericdistribution.config
#!BEGIN CONFIG
# Generic Product Main Settings
distribution
{
  WMO ^S..... KWAL
  {
    label=HADS Data
    uncompress=true
    action
    {
      socket > lrgs-host-name:18000:%X
      socket > localhost:3001:IDS|DDPLUS!%W!%X_/%L/%W
    }
  }

. . . .

The "WMO ^S..... KWAL" line just defines the product - it is any bulletin that arrives that has a WMO header that matches that regex - in this case, it should be all the HADS files.

Just monkey the lines down through the "action" - what is important for you is the two lines that start with the word "socket".  The second one goes to a standard LDM plugin for pushing onto the LDM queue.

Make the change to the /etc/pdinrs/DCPdistribution.config file to add this example at the top.  To make it go live, issue:

pdinrs -t DCP

And that will cause the NOAAPort application to reread the DCP config file.


Trouble Shooting

After starting the LRGS, look in the "lrgslog" file and verify that you see a message shortly after startup of the form:

INFO    2013/01/30-21:19:36 noaaport Listening for connections on port 18000

If you do not see this message, verify that the link is enabled. And then restart LRGS again.

Then, every time the PDI receiver makes a connection you should see two messages in the log like this:

INFO    2013/01/30-21:19:46 noaaport New client, captureFile = 'noaaport-cap-20130130-211946'
INFO    2013/01/30-21:19:46 noaaport New connection from localhost.localdomain

If you do not see these lines then the receiver is not connecting. Verify the receiver connection. Contact PDI for support if necessary.

Another possibility is that a firewall is preventing the receiver from connecting to the LRGS. This can be either the iptables firewall on the LRGS Linux box, or an external filewall between the receiver and the LRGS. Verify the firewall configuration and allow the receiver to connect to the LRGS on port 18000.


Post Feedback
This article is:
Name: *
Email: *
Comment:
Verification Code: *
*Required Field
Related Articles
No Related Articles were found.
Feedback
No Feedback was found.