Specifications

3.5 Complete System / Duration Testing
To perform the complete system and duration test, the hardware from a second MCS-DR PC was
used to emulate the DP subsystem and provide a stream of data for the MCS-DR PC under test.
The duration tests involved streaming data from the emulated DP and having it recorded on an
MCS-DR PC. Tests confirmed that the hardware is capable of the required rates. The test was to
generate packets with a specific pattern on the emulated DP, transmit them to MCS-DR PC under
test, and record the packets to disk. Following the recording part of the test, the recorded file was
then checked to confirm that no errors were introduced in the data transfer/storage process. This
test used the TBN packet size of 1008 bytes, the first eight of which indicate a serial identifier, and
the remaining 1000 bytes were patterned with an 8-bit counter value that rolled over to 0 when it
reached 255. For ten hours, packets were transmitted at a data rate of 115 MiB/s, and the resulting
recording was successfully verified to match the transmitted pattern.
4 Ongoing and Future Efforts
Several tasks still remain to be completed before the MCS-DR will be CDR-ready, though testing so
far indicates that no identifiable and significant risk remains. Software changes will likely be a matter
of reworking the interface and command set to suit the MCS and other subsystems. Outstanding
tasks include:
∙ Documentation Tasks
– MCS-DR ICD and MIB specification
∙ Software Tasks
– MCS Common ICD compliance verification
– Application 1
st
“Release” Candidate
– Source code review and validation
– Doxygen source code documentation
– Regression testing
– Evaluate possibility of USB-bootable image with RAID internal to Studio XPS system
∙ Hardware Tasks
11