Skip Navigation Links 
NOAA logo-Select to go to the NOAA homepage National Weather Service      Select to go to the NWS homepage
Meteorological Development Laboratory banner

Right Arrow User Guides

Right Arrow Docs/Pubs

Right Arrow Other Links

Contact us

FSI Troubleshooting Tips

If your problem is not mentioned in the Troubleshooting Tips below, please try our Field Reports page, which contains communications between the developers and the field.

Version # and
Symptom Potential Solution
Version 0.2

No radar data is being displayed, and FSI is in a one-panel mode.

There are several known reasons for this condition:


The FSIprocessor and/or rssd has stopped running

With the assistance of your ITO, check the process list (‘ps –lef’ from the command line) on the px1f machine to see if the FSIprocessor or rssd processes are running. If either or both are not running, issue these commands as user fxa@px1f


The products in RPS list do not match those in FSIproducts.txt

The px1f:/awips/fxa/data/FSIproducts.txt file determines which products the FSI will process. These product numbers must also be defined in your RPS list for each radar. If they do not, you must edit either file so that the product numbers that FSI is requesting have a corresponding entry in the RPS list. Ask for ITO assistance when editing the FSIproducts.txt file.

The 0.5° Reflectivity product is not in the RPS list

The FSI requires this one product, at a minimum, to launch. Edit your RPS list to include the 0.5° Reflectivity product. Be sure you include the product number corresponding to that listed in the FSIproducts.txt file (see above).
Version 0.2

Incomplete volume scans, and FSI is in a four-panel mode.

Check to see if you have all the elevation angles in your VCPs defined in your RPS list. For Reflectivity and Velocity, 8-bit (level 256) data are preferred. For Spectrum Width, only 4-bit (level16) data are viewable.

NOTE: If the elevations scans below 1.8° are missing, most likely, super-resolution products are defined in an RPS list for a radar that does not produce super-resolution products (e.g., pre-ORPG10). You need to remove the super-resolution products from that radar’s RPS list in order for FSI to process the normal-resolution products at the lowest elevation angles.

NOTE: If TDWR high elevation scans are intentionally omitted from your RPS list for VCP 80, the corresponding elevation scan numbers must be removed from the line associated with the TDWR and VCP of interest in this file:


Version 0.2

No maps to choose from in Maps menu.

This is a symptom with the users’ personal configuration file default reset problem described at the end of the last section. To fix this, exit FSI, from the command line, type fsi_def from the command line, and then restart FSI.
Version 0.2
No storm motion.
AWIPS users choose the storm motion vector (SRM) from the AWIPS Radar Display Controls. If the user chooses “Average Storm Motion from STI”, the STI product must be included in the RPS list. Otherwise, if the user chooses to use a “Custom Storm Motion”, the storm motion must be set to something other than zero
Version 0.2

/awips/fxa/data/localizationDataSets/OAX/userMotion.txt is of zero size.

When a workstation is re-localized (required for FSI install), it "zeroes" out the userMotion.txt file. In order to get values in there again, you need to make any change in your Radar Display Control settings for storm motion. That message will then go away, and FSI will use the motion setting you just entered.


SCAN | FFMP | SAFESEAS | Fog Monitor | GUARDIAN | FSI | Rip Current | SNOW
Autonowcaster | VLab

    US Dept of Commerce
    National Oceanic and Atmospheric Administration
    National Weather Service
    Meteorological Development Laboratory
    1325 East West Highway
    Silver Spring, MD 20910
    Page Author:
    Page last Modified: January 06, 2009.
Information Quality
Privacy Policy
Freedom of Information Act (FOIA)
About Us
Career Opportunities