The following is a list of the Radar Status Messages that appear on the D2D workstation Radar Status window. A brief description of the cause and a possible solution is added. An "xxxx" at the beginning of the line indicates RPG xxxx.

Messages are sent as ROUTINE, SIGNIFICANT (flashing), or URGENT (red banner box). An * at the end of a file name means its directory is given in the note at the end of this list.

I. The following messages are taken from the file, conDownMsg.txt. This file contains many of the messages sent to the workstation as a result of the dedicated or dial line going down. All messages are sent as SIGNIFICANT unless otherwise indicated.

xxxx: Disconnecting Line	The dedicated process, wfoApi, has exited disconnecting the line. This should be preceded by a more descriptive message inidicating why the line is going down.
S: dialing kxxx... kxxx: Line Connected several lines indicating that you are getting the GSM kxxx: RPG Narrowband = Commanded Disconnect several more lines from the GSM kxxx: Disconnecting line	The dial process, dialRadar, received an invalid password response from the RPG. This means either the RPG port password is incorrect, the AWIPS user password is incorrect, or the port phone number does not correspond with the assigned RPG port.
xxxx: Unable to dial RPG - request not sent	Either an invalid telephone number was sent to the modem, or the modem encountered a condition other than "RPG line busy...", "no answer from modem...", "No dial-tone", or "Call timeout".
xxxx: RPG line busy - request not sent	An attempt to dial the RPG failed since the line was busy. The request is not saved.
xxxx: No answer from remote modem - request not sent	An attempt to dial out to the RPG failed since there was no response from the remote modem. The request is not saved.
xxxx: No response from RPG	The file dialRadar has not received any messages for over 30 seconds, from either the RPG or its parent, DialServer. This may be a result of the necessary radar directories (-dirs) not being in place on the data server (ds1) and AWIPS being unable to store the requested radar product. Look at the dialRadar log to see what happened. If you see a message "... bind failed or rejected for client ...", this means that a connection could not be established with the RPG.
xxxx: No dial-tone - request not sent	The modem reported no dial tone.
xxxx: Call timeout - request not sent	The modem dialed out but the call timed out.
xxxx: Lost Connection	Either the dedicated or dial process has received a "Lost Connection" message from the lower level communications. This is usually an indication that the RPG has issued a disconnect on the line. Sometimes, the local communications has issued a disconnect, especially if the line is noisy.
xxxx: No port available - request will not be sent	An attempt to send out a request to an RPG failed since there were no ports available on the Simpact. The request is queued and sent out when a port becomes available.
xxxx: Hardware problem	This is a non-intuitive problem. In the case of a dial-out attempt, there are four possibilities: dialRadar could not find the file apidcfg.bin, which should be in /awips/fxa/bin and /opt/freeway/bin. dialRadar could not bind to the HDLC or X.25 protocol service. This could occur if another x25_manager process is already bound to that service. dialRadar could not open a connection to the Freeway server. Information in apidcfg.bin* is incorrect. dialRadar could not establish an X.25 connection. In the case of a dedicated connection, wfoApi received either a "dead socket" message or a "cs_error". In either case, wfoApi will exit and restart. If the "cs_error" persists, the Simpact might need to be rebooted. Look in the wfoApi log file to determine what happened.
xxxx: Unknown problem	There are a myriad of possibilities. The best solution is to reboot the Simpact. Look at the dialRadar or wfoApi log file to determine what happened.
xxxx: Unable to initialize system - request not sent	It either cannot read syncComms.config* or the attempt to open a connection to the Freeway server resulted in an error. Usually, one needs to look at the dialRadar log file to determine what happened.
xxxx: Problem with Freeway - disconnecting	This is usually the result of an error returned by the lower level communications. Look at the dialRadar log file to see what happened. Reboot the Simpact Freeway. [Note from WSR-88D Hotline: We have also seen this in conjunction with the "Off Hook" message at the PUP. This may indicate a Sprint Telco dial circuit problem.]
xxxx: Freeway not responding - disconnecting	This occurs when trying to set up an HDLC connection for dialing out to the RPG. This usually indicates that the Simpact is down or being rebooted.
xxxx: Freeway resetting - request not sent	The file dialRadar detected that the Simpact is being reset via "icpReset". The file dialRadar will exit.
xxxx: Out of space on data disk - requests will not be sent out	The file dialRadar tried to write to the data disk but there was no more disk space. (This message is sent as URGENT.)

II. These are messages sent from the file dialRadar directly to the D2D workstation.

Modem for radar xxxx not responding	Power the modem off/on and reissue the request. This message usually indicates the modem has hung while dialing RPG xxxx. This might indicate that line xxxx is very noisy. Check the RIOH light on the modem. If it stays on while there are no attempts to dial, then reset the modem. Usually the modem corrects itself after about 30 seconds and no corrective action is needed. (This message is sent as URGENT.)
Unable to dial RPG xxxx, so retrying a few times	While attempting to dial out to an RPG the modem could not complete the connection. It will attempt two more times and then exit if unsuccessful. (This message is sent as SIGNIFICANT.)
dialing xxxx ...	The dialRadar process is attempting to dial RPG xxxx. (This message is sent as SIGNIFICANT.)

III. The following messages are issued by the RadarMsgHandler and sent to the D2D workstation in response to messages from either dialRadar or wfoApi through the DialServer or RadarServer, respectively. (All messages are sent as ROUTINE unless otherwise indicated.)

xxxx: Line Connected	A connection has been established with RPG xxxx. (This message is sent as SIGNIFICANT.)
xxxx: RPS list sent successfully	The RPS List has been sent to RPG xxxx.
xxxx: RPS list not sent	The RPS List was not sent to RPG xxxx because either the number of requests in the RPS List exceeds that specified in the last column of portInfo.txt*, or there is no connection. Look in the RadarServer log file to determine the problem.
xxxx: Alert Request sent successfully	The alert request has been sent to RPG xxxx.
xxxx: Alert Request not sent	The alert request was not sent to RPG xxxx because there was no connection.
xxxx: One Time Request sent successfully	A one-time request has been successfully sent to RPG xxxx.
xxxx: One Time Request not sent	A one-time request was not sent to RPG xxxx for one of the following reasons: Inability to format the message. Failure in the process of sending the request (IPC error). No connection to RPG xxxx. Look in the dialRadar or wfoApi log file to determine the problem.

IV. The following messages are generated as a result of messages received from the RPG. (They are sent as ROUTINE.)

xxxx: User Alert Text Message Received	Received a UAM from the RPG.
xxxx: Free Text Message Received	Received an FTM from the RPG.
xxxx: Radar Coded Message Received	Received an RCM from the RPG.
xxxx: Received Alert Adap Params	Received an AAP from the RPG.
xxxx: aaaa bbbb hhmm rrrr eeee (eg. kftg: Z OTA 0204 1.0 0.5)	This is a product message received as a result of a one-time request, alert request, or as an unsolicited message where, aaaa = product mnemonic bbbb = request type (OTA: One-time request from an assoc. RPG, OTN: One-time request from a non-assoc. RPG, UNS: Unsolicted product, ALR: Product received as a result of alert request) hhmm = hour and minute of the volume scan rrrr = resolution of the product eeee = scan elevation

---

V. GSM (General Status Messages)

The following messages are generated as a result of receiving a General Status Message (GSM). Their meanings are defined in the NEXRAD PUP/RPGOP User's Manual. (These messages are sent to the workstation as ROUTINE.)

RPG Avail = ... RPG Narrowband = ... RPG Software = ... RPG Alarm = ... RDA Avail = ... RDA Software = ... RDA Alarm = ... Op Mode = ... New Prod Status = ... Base Data = ... Ded RPG Comms = ...

Usually, when there is a problem with the RPG or the RDA, it is indicated in these status messages. If there has not been any data for a while, look at the radar status window for these messages. There is also a graphic called the NEXRAD Unit Status Message (NUSM) that is selectable from the graphics display.

VI. PRR (Product Request Response) Messages

xxxx: aaaa zzzz bbbb hhmm rrrr eeee (eg. LRM LdShed(RPG CPU) RPS 0101 1.0 1.5)

This message is sent by the RPG in response to either a one-time request, an RPS List, or an alert request. (This message is sent as SIGNIFICANT.) The message is an indication as to why the RPG could not honor the request, where, aaaa = product mnemonic zzzz = reason the request could not be honored bbbb = request type (OTA: One-time request from an assoc. RPG, OTN: One-time request from a non-assoc. RPG, RPS: Routine Product Set List, ALR: Product received as a result of an alert request) hhmm = hour and minute of the request rrrr = resolution of the product eeee = scan elevation

VII. Alert Messages

xxxx: gggg Grp cccc Alert Area: nnnn Threshold: tttt uuuu (eg. kftg: Grid Grp "Comp Ref" Alert Area:2 Threshold:15 dBZ)	(This message is sent as URGENT.) The RPG sends this message when it detects that an alert threshold has been exceeded, where, gggg = group (Grid, Velocity, Forecast) cccc = category (look in alertTypes.txt*) nnnn = alert area 1 or 2 tttt = Threshold specified in request uuuu = units (look in alertTypes.txt*)
xxxx: Alert Cancelled: Grp: gggg Cat: cccc Alert Area: nnnn Threshold: tttt uuuu (eg. kftg: Alert Cancelled: Grp: Grid Cat: Comp Ref Alert Area:2 Threshold:15 dBZ)	(This message is sent as SIGNIFICANT.) The RPG sends this message when it detects that the condition that caused the alert has fallen below the threshold, where, gggg = group (Grid, Velocity, Forecast) cccc = category (look in alertTypes.txt*) nnnn = alert area 1 or 2 tttt = Threshold specified in the request uuuu = units (look in alertTypes.txt*)

Note: The following is a list of files mentioned along with their directories on the ds machines.

alertTypes.txt	$FXA_DATA/radar/alertRequest
apidcfg.bin	/awips/fxa/bin and /opt/freeway/bin
dialRadars.txt	/awips/fxa/data/localizationDataSets/XXX, where XXX is the site Id
portInfo.txt	/awips/fxa/data/localizationDataSets/XXX
syncComms.config	/awips/fxa/data