TReK Release 1.1 Service Pack 2

When will it be available?
June 11, 2001

Should I get this service pack?
This service pack is optional. It contains several enhancements and fixes but does not contain any critical fixes. Therefore, unless you are interested in one of the fixes or enhancements there is no need to get this service pack.

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. You can install it over TReK Release 1.1 or TReK Release 1.1 Service Pack 1. Please note that if you install this service pack you will automatically get the updates that were included in TReK Release 1.1 Service Pack 1.

What's In It?

Fixes

• The GetNewestDatazone and GetNextDatazone returned the API_NOT_ENOUGH_SPACE error whenever there was not enough space allocated. This prevented other errors from being returned that should have a higher priority. These functions now will return other errors (e.g., API_NO_DATA_AVAILABLE) before API_NOT_ENOUGH_SPACE.
  
  
• The TelemetryDatabase.mdb file that is delivered as part of the TReK installation contained a minor error in the definition for MSID108 in the PDSS Payload packet with an APID of 7 and the Suitcase Simulator packet with an APID of 7. MSID108 has a total of four samples, but this error would cause the last two samples to be incorrectly retrieved from the packet. This scenario is allowed by validation so no errors were generated when performing a validation of the database. The new database file will be copied into the database directory in the TReK install folder. However, if you already have a copy of this database file in your user directories, the old database will not be overwritten.
  
  
• If a GSE packet had a length greater than 4095 bytes, the Add GSE Packet option in the Telemetry Database application would generate an ERROR_700 message and the GSE packet would not be added to the database. This problem is now fixed. If you do not have a GSE packet format with more than 4095 bytes, the TReK software releases prior to this service pack will work correctly.

New or Enhanced Capabilities

• Telemetry Processing now supports two views: Packet List View and Packet Snapshot View. The Packet List View is the default and is the same view used in previous TReK releases. The Packet Snapshot View was added based upon a user request. This view shows eight packets per row instead of one packet per row. For each packet the Packet ID (APID), Packet Type, and Data Mode are shown in an abbreviated format (7-P-RT). This view provides a way to see the status of a large number of packets without scrolling. The colors apply to both views and you can switch between views. Please note that the Packet Snapshot View is "view-only". The Packet List View is still considered the primary view and must be used to change a packet's properties (activate, start recording, etc.).
  
  
• The TReK User API has 17 new functions. These functions allow you to guarantee that parameters are retrieved from the same instance of a packet. These functions were added based on a user request. The functions are:
  • GetOneSamePacketRawValue
  • GetOneSamePacketConvertedIntegerValue
  • GetOneSamePacketConvertedUnsignedIntegerValue
  • GetOneSamePacketConvertedDoubleValue
  • GetOneSamePacketConvertedStringValue
  • GetOneSamePacketConvertedTimeValue
  • GetOneSamePacketConvertedTimeStringValue
  • GetOneSamePacketCalibratedDoubleValue
  • GetOneSamePacketCalibratedStringValue
  • GetSamePacketRawValue
  • GetSamePacketConvertedIntegerValue
  • GetSamePacketConvertedUnsignedIntegerValue
  • GetSamePacketConvertedDoubleValue
  • GetSamePacketConvertedStringValue
  • GetSamePacketConvertedTimeValue
  • GetSamePacketCalibratedDoubleValue
  • GetSamePacketCalibratedStringValue
    
    
    

Other Notes

• The Telemetry Processing User Guide has been updated for this release and also incorporates changes from Release 1.1 Service Pack 1.
  
  
• The API Reference Manual has been updated to include the 17 new functions described above.
  
  
• No other documents have changed since Release 1.1