TReK Release 1.1

TReK Release 1.1 was released on November 27, 2000. It was an update to TReK Release 1. Below you will find information about the fixes and enhancements included in TReK Release 1.1. There is also a list of known issues with TReK Release 1.1.

Fixes for Problems Found in TReK Release 1

• The Set Telemetry Processing Options dialog in the Telemetry Processing application had three problems: 1) It was not possible to update the options from a user account, 2) The Set To Defaults button updated the Process Packet Queue Size, Record Packet Queue Size and Forward Packet Queue Size fields with the wrong defaults, and 3) If an error occurred while updating the options, the error message that was posted incorrectly listed all the options instead of the ones that the user was attempting to change. All three of these problems have been corrected.
  
  
• The GetNewestDatazone and GetNextDatazone User API functions do not properly return API_NOT_ENOUGH_SPACE when this condition occurs. This has been corrected.
  
  
• If the Hard Disk reaches capacity during data recording, the Telemetry Processing application will stop functioning correctly and may crash. This has been corrected.
  
  
• 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. This has been corrected.
  
  
• If you create or edit a calibrator in the Telemetry Processing application, and you use overlapping ranges, the validation error message has been updated so it correctly flags this error.

New or Enhanced Capabilities

• You requested it -- we added it. TReK finally has a display capability. The Telemetry Processing application now provides a way to automatically generate a display. You can display any measurements that TReK is processing and you don't have to write a single line of code. It is very fast and you can save your displays within your Telemetry Processing configuration file. The TReK API will always be available but this will provide a very fast way to create a display without having to use the API. We hope you will find this useful.
  
  
• You can now configure the time interval used for packet statistics recording. For example, you can set the time interval so the statistics data is written to the file every 30 seconds (or every 60 seconds, or every 2 minutes, etc.).
  
  
• The Generic Display has been updated so you can retrieve data from a Suitcase Simulator packet.
  
  
• In TReK Release 1, once a playback channel was in use, it could not be assigned to another playback. This functionality has been changed so that you can select a playback channel even it it is already in use.

Known Issues with TReK Release 1.1

• Telemetry Processing Error Message, #2087 Packets Not Recorded, generated too many times when disk full error occurs. (Fix in TReK Release 1.1 Service Pack 1)
  
  
• Data Playback will not work when using Spacecraft Time data recording files that were moved from one machine to another. (Fix in TReK Release 1.1 Service Pack 1)
  
  
• Range and counter dependent sampling not working. (Fix in TReK Release 1.1 Service Pack 1)
  
  
• There was an error in the Telemetry Processing application‘s display capability with regard to GSE parameters. For GSE measurements that arrived as calibrated data it was not possible to set the display type to calibrated. (Fix in TReK Release 1.1 Service Pack 1)
  
  
• Adding a very large number of measurements to a Telemetry Processing display can cause a performance problem. (Fix in TReK Release 1.1 Service Pack 1)
  
  
• If a TReK registry key in the local user area is deleted, TReK does not add it back. (Fix in TReK Release 1.1 Service Pack 1)
  
  
• The GetNewestDatazone and GetNextDatazone functions in the TReK API can incorrectly return API_NOT_ENOUGH_SPACE in some cases in Release 1.1. (Fix in TReK Release 1.1 Service Pack 1)
  
  
• 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. (Fix in TReK Release 1.1 Service Pack 1)
  
  
• 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. (Fix in TReK Release 1.1 Service Pack 1)
  
  
• 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. (Fix in TReK Release 1.1 Service Pack).
  
  
• It is possible to add duplicate playback packets to the Telemetry Processing packet list. (Fix in TReK Release 1.1 Service Pack 1)