Chapter 6 - Reference
The following sections of this Chapter are external to this file, but available by htm link:
Notes
on Source Code
Known
Bugs
These are in the lower-left corner of the screen and are numbered. Errors start with the letter 'E' and indicate that some element of the radio or program operation was improper. Warnings start with the letter 'W' and indicate that the operator needs to consider the commands to be executed, to be sure that unexpected operation won't occur! Some errors are accompanied by a "beep," to catch the operator's attention. The following short descriptions should be helpful for understanding the errors.
E1-Serial Data Lost. Spectral data transmitted by the DSP arrived with an error in the check sum and is not being included in the spectral display updates. This is not unusual during mode changes when a data set may have been truncated.
E2-Invalid Status, Receive. About 20 status bytes are sent to the PC from the DSP during reception. Validity checks show if these have not been received correctly. This can again occur with mode changes without indicating a real problem. Status bytes are discarded if they are not valid.
E3-Illegal DSP Command. If the DSP receives a command that is out of the vocabulary, this is reported back to the PC as a status bit. These commands are ignored by DSP.
E4-Invalid Status Transmit. Status is sent to the PC during transmit, No spectral data is sent. At the time of issue for V2.0 a bug remained that causes some invalid E4 messages. It is apparently associated with the presence of an Escape character in the status data.
E10-Excessive Auto-Display Correction. Over 10 dB of correction is needed to keep the display centered. This indicates a major change in the RF gain of the system. If this gain shift is intentional, the Auto-Display (Alt-C) should be turned off and back on to reinitialize the operation.
E11-flattener Curve Fit. Indicates numerical error in the polynomial curve fit used for the "yellow" trace of EME-2 or LTI. Yellow trace will be invalid.
W12-No Clock Set. It is a warning that the software clock has not been set. For LHL7 and PUA43 modes it would be unusual to not need a clock set.
W13-Illegal during Audio Input. A command that was not proper for the Audio Processor has occurred.
W14-No Tvtr. To use a transverter setting (Ctrl-Alt-?), the UHFA.CFG configuration file must have the full set of information entered. Transverter settings without this data will not occur.
E15-No UT. Doppler corrections require a knowledge of Universal Time (UT).
E16-3rd LO Out of Range. In order to not have transient problems from re-locking the 5 kHz synthesizer when in transmit, only the 3rd, DSP LO can be changed during transmit. If this is shifted too far, it will fall outside the D/A and Crystal filter limits. The solution is to go into receive before making major shifts in the transmit frequency.
E17 - No Mem - Insufficient memory is available for the scrolling of the screen
W17 - Transmit overdrive
E20-Illegal number of bins in LHL-7. This is locked out normally, but can occur at startup. Use Alt-F3 and Alt-F4 to select a valid combination.
E21-PUA43 out of memory. Dynamic memory allocation has failed for the PUA43 mode and it will not be available. Check the users of DOS 640K memory as there should normally be adequate amounts of memory.
E22-PUA43 Illegal Time Tag. PUA43 uses a software triggered FFT to gather the spectral data. Along with this trigger goes a time tag that is in turn returned to the PC with the spectral data. This tag is checked to align the data with the proper symbol in reception. Data is discarded if a time tag error should occur.
E23-UT needed for LTI randomization. See E15.
E24-UT needed for PUA43 randomization. See E15.
W26-Beacon operation was started, but there is nothing in the CW Send Buffer. When transmit is started, nothing will be sent!
W27-Center Vertical Cursor was asked for, but the mode in use has no center defined (such as USB).
W28-Double Vertical Cursors were asked for, but the mode in use has no frequencies are defined (such as USB).
E30-PLL Un-Lock. There are 2 PLL's in the DSP-10 for the 126 and 19.68 MHz synthesizers. One of these is not locking properly, often because the tuning coil/capacitor is not set properly, or the DSP-10 has been tuned past the range of the PLL.
E40-Graphics Error. Make sure that the system has VGA 640x480 16 color as an option. Check the details of the graphic system that can be seen at startup time by setting "startup_detail 1" in the UHFA.CFG file.
E41-Memory error, Curve straightener for EME2 and LTI. See E21.
E42-CFG File Error. This covers a broad class of file errors. Check the availability of the drive/directory that held UHFA.EXE and will be the destination for UHFA.CFG. If there is a serious disk error, there may also be an text error message over the upper left corner of the screen. The absence of UHFA.CFG at startup is not an error and is the way to return to all the default configuration values.
E43-LTD File Error. This file saves long-term integration data. See E42.
E44-Other File Error. See E42.
W45-Ctrl C Trap. Control C is the default command for aborting program operation. This is a bit harsh for a program such as the DSP-10 and so it has been trapped and only generates this warning. Use Scrl-Alt-F4 to stop the program in an orderly way.
E46-Math Error. A floating point error has occurred. Every attempt is made inside the PC program to test values that can be a problem that generates this error. If one was missed, it will show up here. Please report these along with the conditions that seemed to create it to W7PUA.
E47-DAT File Error. This is the file that collects large amounts of detailed spectral data. See E42.
E48-Dynamic Memory Allocation for Filter Design. See E21.
E49-Math Error in Filter Design. Most of the common errors in filter parameter specification are trapped at the "Alt-B" Box and will produce messages there. If this error is encountered, check that the parameters are reasonable, as it would appear that the filter was not possible to design but was not caught at the B-Box time.
W50-The floppy drive is not allowed for the full data file. The default drive will be used. If the default is the floppy, there may be problems with filling the floppy quite quickly.
W51-An attempt was made to write to the floppy drive, but either the door was open, or there was no disk available. The disk save operation was not done, and needs to be retried with a floppy disk in place.
W54-Not enough memory available to open a dialog
box. The box was
not
opened, but other operations will continue.
W60 -"GGA Parse" The reading of the NMEA sentence GPGGA was not correct. (bug? same as W67)
W61- "DCD Timeout" No 1PPS (pulse per second) signal was found on the DCD line, pin 1 of the 9-pin serial line.
W62- UT+ check sum error in reading the binary data from the UT+ GPS.
W63- UT+ excessive message length meaning bad UT+ binary data was received
W64- GPS time out occurs when no GPS data is received in 5 seconds
W65- GPS fix not established, data was read, but indicated as having no fix in position.
W66- Time set failed meaning that the GPS time and position data was OK, but no DCD pulse occurred within the 1 second window.
W67- GPS NMEA GPGGA sentence error, sub error 1=bad parse, 2=checksum error.
W68 -GPS NMEA GPGSV sentence error, sub error 1=bad parse, 2=illegal number of messages, 9=check sum error.
W69- No GPS auto set is available, check the GPS type in the SCRL-F8 box.
E70- Error in creating time logging file.