TReK Release 1

TReK Release 1 was released on July 18, 2000. The information below identifies issues that have been found with the TReK Release 1 software. There is an explanation of the issue and a work-around is provided if applicable.

Known Issues

• Range Dependent Sampling: if a state code has more than one corresponding range, TReK will only use the first range when extracting the parameter from the packet.
  
  
• Database Forms: The single quote character (‘) can cause problems when performing queries in the Telemetry Database Application. To workaround this problem use the * or ? Characters.
  
  
• Packet Size: If the size of the packet received by TReK is smaller than the size defined in the database; TReK may crash in some cases. This is most likely to happen with GSE Packets. (Fix in TReK Release 1.1 Service Pack 1).
  
  
• Telemetry Processing application: It is not possible to update the telemetry processing options using the Set Telemetry Processing Options dialog (or Advanced dialog) if you are running in a user account (vs. an account with system administrator privileges). Also, the error message that is displayed when this error occurs incorrectly identifies the fields that were modified and could not be updated. (Fix in TReK Release 1.1). Note: Please read the following procedure for a work-around: TelemetryProcessingOptionsWorkAround.pdf.
  
  
• The GetNewestDatazone and GetNextDatazone User API functions do not properly return API_NOT_ENOUGH_SPACE when this condition occurs. (Fix in TReK Release 1.1).
  
  
• If the Hard Disk reaches capacity during data recording, the Telemetry Processing application will stop functioning correctly and may crash. (Fix in TReK Release 1.1).
  
  
• Duplicate IP addresses can show up in the Browse For IP Address dialog box (in either Telemetry Processing or Training Simulator) if the PC's network cards are not installed properly. (Fix in TReK Release 1.1).
  
  
• If you create or edit a calibrator in the Telemetry Processing application, and you use overlapping ranges, the validation error message does not flag this error correctly. (Fix in TReK Release 1.1).
  
  
• Once a playback channel is in use, it cannot be assigned to another playback. This was an intentional design decision. However it has been brought to our attention that it may be necessary to use the same playback channel with multiple playbacks simultaneously. Therefore, we will change this functionality so you can select the same playback channel for multiple simultaneous playbacks. (Fix in TReK Release 1.1).
  
  
• Telemetry Processing application: In the Add A Playback Packet dialog, if you identify data recording files that contain Suitcase Simulator data, you must set the Data Mode to None. This is the only legal data mode for Suitcase Simulator data. If you set the Data Mode to one of the playback modes, the application does not present an error message like it should. When you push the OK button, the dialog will not go away and you won't see an error message. However, if you set the Data Mode to None, everything will work correctly. This problem has been corrected in TReK Release 1.1.
  
  
• The Telemetry Database application does not run correctly under a Windows 2000 restricted user account. (Fix in TReK Release 1.1 Service Pack 1).
  
  
• The Telemetry Processing application does not display an error message when an error is encountered while reading a data recording file during a playback. (Fix in TReK Release 1.1 Service Pack 1).
  
  
• If the TReK Install directory information in the registry is missing or is incorrect, the Training Simulator application will not function correctly and does not properly recover from this error condition. (Fix in TReK Release 1.1 Service Pack 1).
  
  
• If Spacecraft Time shortcuts and their associated target files (TReK Reciept Time) are moved to another directory or computer, a Telemetry Processing playback request that uses spacecraft time may not play the packets back in the proper order. (Fix in TReK Release 1.1 Service Pack 1).
  
  
• Telemetry Processing application: If a playback packet activation fails due to an input error (for example the IP address used to forward packets is incorrect), it is not possible to re-activate the packet even after the error has been corrected. (Fix in TReK Release 1.1 Service Pack 1).
  
  
• If you move the TReK Receipt Time (TRT) and Spacecraft Time (SCT) data recording files to another directory, and try to play back the data using Spacecraft Time, in some cases the packets will be played back in the wrong order. (Fix in TReK Release 1.1 Service Pack 1).