TReK Release 1.1 Service Pack 1

When will it be available?
March 28, 2001

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

• Arriving Packet Size vs. Size Identified in Database -- First of all, you should never see this problem -- but you know how that goes.... Suppose you are using TReK to receive and process Ground Support Equipment packets shipped to you from the POIC. You need to be sure that the packet definition in the TReK database matches the packet definition being used by the POIC. If they don't match then this means that TReK will receive a packet that is possibly too short or too long compared with what it is expecting. With TReK Release 1.1 (and earlier releases), this problem caused TReK to crash. This is a known problem that was identified at the TReK Release 1 ORR. If everything is working as it should, you should never run into this problem. But since things sometimes don't go as they should, we decided to fix this problem now rather than waiting until a later release. Service Pack 1 contains this fix. If by chance you end up in this type of configuration (with a mismatch between the TReK packet definition and the EHS packet definition), TReK will now be able to recover gracefully from this problem. Your packet won't get processed correctly since TReK does not have the correct database information, but TReK will not crash.
  
  
• When you use the TReK data recording feature, TReK records data into files in the location (drive/directory) you specify. If by chance you run out of disk space on that drive, TReK will post an error message (Message # 2087 Packets Not Recorded). In TReK Release 1.1, TReK posted this message too many times. Service Pack 1 fixes this problem so that a message is only posted every few minutes until the problem is resolved (you turn off data recording or free more disk space).
  
  
• In TReK Release 1.1: If you run out of disk space while you are recording data, and you attempt to stop recording, the Telemetry Processing application's packet recording status will indicate that recording is still on even though it has stopped. This has been fixed. 
  
  
• Data playback fails to execute -- If you move the TReK Receipt Time (TRT) and Spacecraft Time (SCT) data recording files to another machine and try to play back the data on the other machine, using the spacecraft time, the playback fails to execute. The problem occurs because the SCT's target TRT file is not properly identified. Service Pack 1 will fix this problem by correctly identifying the SCT's target TRT file. However, please remember that it is important to keep the SCT and TRT files in the same directory when you move the data recording files to a new location.
  
  
• Counter and range dependent sampling was not working correctly in TReK Release 1.1. This has been fixed.
  
  
• Data playback -- packets are played back in the wrong order -- 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. This has been fixed.
  
  
• In TReK Release 1.1 there was an error in the Telemetry Processing application‘s display capability with regard to GSE measurements. For GSE measurements that arrived as calibrated data it was not possible to set the display type to calibrated. This has been fixed.
  
• Adding a very large number of measurements (thousands) to a single Telemetry Processing display can cause a performance problem. To protect against this, a limit has been placed on the number of measurements that can be added to a display. The default is 1000, but can be changed.
  
  
• In previous releases of TReK, if you accidentally deleted a key from the user portion of the registry, TReK would not add the key again. This would not cause TReK to fail, but TReK could only run using the hard coded default value for that key. TReK will now recreate deleted keys when a TReK application is started.
  
  
• The GetNewestDatazone and GetNextDatazone functions in the TReK Application Programming Interface (API) incorrectly returned API_NOT_ENOUGH_SPACE when the size_of_data value passed in was less than the size of the entire CCSDS packet. This has been fixed.
  
  
• The Telemetry Database application did not run correctly in a Windows 2000 restricted user account. This has been fixed.
  
  
• There was an error in the Telemetry Processing application's display capability. If Sensing was selected for a parameter that did not have an assigned calibrator, sensing was not performed as it should have been. This has been fixed.
  
  
• The Set To Defaults button on the Telemetry Processing application's Set Telemetry Processing Options dialog incorrectly reset the value for Maximum Time File Is Open. This has been fixed.
  
  
• The Telemetry Processing application does not display an error message when an error is encountered while reading a data recording file during a playback.. This has been fixed.
  
  
• If multiple recording files are identified during a data playback request, and the packets were recorded at a rate that was greater than once per second, recorded packets at the beginning of the second and subsequent record files may not be played back. This has been fixed.
  
  
• 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. This has been fixed.
  
• 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. This has been fixed.
  
  
• It is possible to add duplicate playback packets to the Telemetry Processing packet list. This can occur if a configuration file is opened and then the Add A Playback Packet dialog is used to add a packet that is a duplicate of one of the packets in the list. This has been fixed.
  
  
• 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. This has been fixed.
  
  
• The following messages in the Telemetry Processing application were either updated or added. Since the Telemetry Processing User Guide was not re-delivered with this service pack, the updated/added messages are listed below:
  • Message 2087: Some or all of the incoming packets are not being recorded! Please check to be sure you are not out of disk space.
  • Message 2175: A converted value cannot be retrieved if the measurement does not have an appropriate converter. Some of the measurements you selected do not have data types that support conversion, so a converted value cannot be displayed. Also, any data that arrives as calibrated data cannot be displayed as converted data.
  • Message 2185: Some of the measurements you selected do not arrive as unprocessed data, so unprocessed data cannot be displayed.
  • Message 2186: There is a limit on the number of measurements that can be added to a display (<#> measurements). Your display currently has <#> measurements.  You can add <#> more measurements.
  • Message 2187: The Telemetry Processing application cannot continue. There is not enough disk space available to create the temporary files the application needs in order to run.
  • Message 2188: The Telemetry Processing application cannot continue. The information in the registry that identifies the target location for the TReK tmp directory points to a directory that does not exist.
  • Message 2189: Packet <Packet ID> [<{Packet Type>, <Data Mode>] -- An error occurred during packet recording shutdown. It was not possible to properly close the data recording file currently in use. Due to this error, it may not be possible to play data back out of this file.
  • Message 2190: Packet <Packet ID> [<Packet Type>, <Data Mode>] -- An error occurred during packet recording shutdown. It was not possible to properly name the data recording file currently in use. Due to this error, it may not be possible to play data back out of this file.
  • Message 2191: An error occurred while reading data out of a data recording file. Due to this error the corresponding playback was stopped.

   

New or Enhanced Capabilities

• If you've read the TReK Getting Started Guide, then you know that TReK creates a directory called "tmp" which it uses to hold temporary files . In TReK Release 1.1, this directory was always created in the Application Data folder for the user account (most of the time that was on C drive). However, with this service pack you can now control where this directory gets created. Why would you want to do this? You probably wouldn't. However, we had one customer who was very low on disk space and needed a way to ask TReK to create this directory in a different location. Therefore we added this enhancement. For most folks you can just let TReK do its thing and not even worry about this. But if you're in a bind due to low disk space this provides a way to control your configuration. For more information please see the TReK FAQ page.