TReK Release 2 Service Pack 2

When will it be available?
Released on June 16, 2003.

How do I install the service pack?
You simply download the service pack (single file) and double click on it. This will start an installation process that will update several files in the TReK bin directory. That's all you need to do. You don't have to uninstall the TReK software to install this service pack.

What's In It?

Fixes

• TReK would sometimes use a floating-point string representation that would be rejected by the POIC because it exceeded the length allowed by one character. This problem is now fixed.
  
  
• The Telemetry Database application generated an error when trying to add a GSE packet that already exists in a database. The error occurred when trying to delete the old GSE packet definition. This problem is now fixed.
  
  
• When viewing packets during a playback, if the message buffer size is set to the number of messages in the recording file, all the packets will show up in the viewer except the last one. This problem is now fixed.
  
  
• When viewing packets during a playback, if the playback packet properties were modified, causing a reactivation, the viewer window could not be displayed again (choosing the menu item would not bring up the dialog). This problem is now fixed.
  
  
• Occasionally, GSE packets deletion would fail due to a failure in cleaning up processing elements associated with parameter recording. This problem is now fixed.
  
  
• When converting commands from an EHS partial database, variable length fields with an IUNS data type were not properly handled. This problem is now fixed.
  
  
• When converting EHS partial command or telemetry database files, the process would generate an error and not finish successfully if a field had a double quote within the data. This problem is now fixed.

EHS ECR Updates

• Implemented ECR HM-2915. This allows the user to interactively change expired passwords during the ERIS login process. In addition, the user can change ERIS passwords that will soon expire through the TReK user interface.
  
  
• Implemented ECR HM-2953. This allows a user to select Custom Data Packets to be sent at the rate of the fastest source packet. The GSE changes associated with this ECR are not yet available from the POIC.
  

New or Enhanced Capabilities

• Telemetry Processing and Command Processing applications -- The Add ERIS Session dialog now provides a way to select or type a host name for the POIC. You may still type the IP address if desired.
  
  
• A new record scheme is now available in Telemetry Processing and Command Processing that allows data to be recorded into directories based on time. See the TReK Record File Format Definition Document (TREK-USER-031) for details.
  
  
• The Command API will now return detailed error codes describing on board problems for FSV1 messages. The new error codes are numbered 14201 to 14303 inclusive. There are gaps in these numbers.
  
  
• A new column is available in the Commands, Headers, and Fields dialogs in command processing that allows you to know if something is complete or incomplete.
  
  
• The TReK receipt time for a packet can now be retrieved via one of the Get…TimeValue() function calls in the Telemetry API. See the new function GetPacketReceiptParameterName() in the Telemetry API Reference Manual or online help for more details.
  
  
• Performance enhancements for Data Playback, Data Recording, Parameter Extraction and Telemetry Trainer. Data Playback, Telemetry Trainer and Data Forwarding can now transmit data at much higher and more accurate rates.
  
  
• Telemetry Processing now allows a packet to be deactivated.
  
  
• Command Processing now allows a destination to be deactivated.
  
  
• In previous versions of TReK, the database information was always saved in the configuration file for activated packets. It is now possible to choose whether or not to save the database information in a Telemetry Processing configuration file. This option is available on the Telemetry Processing Options dialog and defaults to save the information.
  
  
• Five new documents are included in this release. The TReK Record File Format Definition Document (TREK-USER-031) provides the details of the record file’s formats used by TReK for all releases. The TReK Choosing an Uplink Function Tutorial (TREK-USER-032) is useful in helping you decide which of the TReK Command API functions to use in your applications. The TReK How To Build A Visual Basic .NET Display Tutorial (TREK-USER-033) explains how to use the TReK API in Visual Basic .NET. The TReK How To Build A Visual C++ .NET Computation Tutorial (TREK-USER-034) explains how to use the TReK API in Visual C++ .NET.
  
  
• The Telemetry Processing data playback capability now supports the sending of data based on user specified bits per second in addition to the previous capabilities.
  
  
• The Telemetry Training application now supports the capability to send data in bits per second in addition to the previous capabilities.
  
  
• Telemetry and Command Database applications now support creating databases on a network drive.
  
  
• The Command Processing application can be configured to prompt the user for confirmation of each command request initiated from the Commands dialog. This feature is off by default. Commands issued from user programs via the TReK Command API will not use the prompt.