TReK Release 3 Service Pack 3

TReK Release 3 Service Pack 3 is a service pack for TReK Release 3. Here's some information about this service pack.

When will it be available?
Release 3 Service Pack 3 was released on November 29, 2006.

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 was using the Windows registry to check for valid IP addresses in Telemetry Processing, Command Processing, and Remote Services. If the registry did not contain the correct information, TReK would incorrectly reject a valid IP address. TReK no longer uses the registry to verify an IP address.

• Floating point numbers no longer lose precision in the parameter recording/extraction files.

• The time format written to parameter recording/extraction files now includes milliseconds. The format is yyyy-mm-dd hh:mm:ss.sss. If you use Microsoft Excel to view these files the time column will automatically update to show a different format. If you would like to maintain the above format, select the column and choose Cells from the Format menu in Excel. On the dialog choose the Number tab and select Custom in the Category list. Enter the following (without the quotes): “yyyy-mm-dd hh:mm:ss.000”. The three zeros on the end should format the milliseconds correctly.

• During the process of extracting data from data recording files TReK can sometimes fail (hang) due to an internal timeout value. This problem is now fixed.

• TReK was not properly processing parameter dependencies that contained a ‘<’ or ‘<=’ in the operator1 field in the Dependency table in the database if the operator2 field was blank. This problem is now fixed. The problem would most likely appear for counter dependent parameters which are not usually found in user packets. There are no database updates associated with this fix.

• Telemetry Processing was incorrectly preventing source ports from being reused for UDP forwarding. This restriction only applies to TCP forwarding.

• A problem with the Monitor Limit and Monitor ES tables in the Telemetry Database application which caused the form to error off and close if the Sample Flag was unused when trying to save the form has been fixed.

 

EHS ECR Updates

• HM-3239 – This ECR modified the strings associated with the first Command Acceptance Response (CAR1) returned from MCC-H. These changes included updating the TReK Command API, but no recompilation is needed.

New or Enhanced Capabilities

• Data recording of GSE and GSE Merge streams now provides the capability to create Spacecraft Time (SCT) time files based upon an embedded spacecraft time that is stored in the Ground Receipt Time (GRT) area of the EHS packet header. If the embedded spacecraft time is replacing the GRT in the EHS header of the GSE packet, playbacks can reorder and remove duplicate GSE packets created from time overlapped real-time and dump streams using the SCT files.

• TReK has the ability to communicate with EXPRESS payloads using the EXPRESS interface. A TCP client socket can be shared between an EXPRESS packet in Telemetry Processing and an EXPRESS destination in Command Processing.

• TReK has added a UFO destination to Command Processing. A UFO destination allows commands to be sent to a network or device location. This provides the ability to define a command and its associated headers in the Command Database and send it to a destination that does not require any special communication (hand shaking).

• The Telemetry Processing application now provides the capability to modify the following EHS header fields when forwarding a packet: Project Identifier, Operational Support Mode, and Mission/Increment.

• The TReK User API has three new functions related to the logging of monitoring messages: SetMonitorLogFile, StartMonitorLogging, and StopMonitorLogging. See the Telemetry API Reference Manual for details.

• Command Processing now allows the user to choose the terminating character for strings.

• Command Processing now allows the user to choose a fill pattern for fixed length strings.