Technical Reports

PTC 220 MHz Radio: ITCR Closed Track Test 1 Test Report

  • 14
  • Feb
  • 2012
AUTHOR: Meteorcomm LLC
OFFICE: RRS
REPORT NUMBER: 00002467-A
SUBJECT: Positive Train Control, Signal and Train Control, Grants & Financial Assistance
KEYWORDS: Railroad Safety Technology Grant
ABSTRACT: The first phase of closed track testing, referred to as CTT 1, of the PTC communication system entailed the installation and operation of the PTC communication system at the Transportation Technology Center (TTCI) located near Pueblo, Colorado. This facility was used to test the communication system under controlled field conditions using real locomotives and operating at speeds in excess of 100 mph. The installation of the PTC communication system at TTCI included three base radio installations, eight wayside communication site locations, one mobile locomotive, one stationary locomotive site, a simulated local back office at TTCI, and a simulated remote back office located at the MCC facility in Renton, WA. All endpoints, which includes WIU, TMC, and back office applications, were simulated. After installation, basic functionality of the system elements was verified and pretest activities were completed. Pretesting included system configuration and deb, RF coverage measurements, basic messaging tests, and validation of basic radio network operation. Basic RF measurements such as bit error rate (BER) established that there was little or no impact on RF link performance due to locomotive speeds of 80 mph and higher. Similar results were seen for message latency between the remotes and the back office. This result is due primarily to the benign RF environment surrounding the test bed, obviating the need for mitigation measures typically employed in the field. During CTT 1 there were 108 test cases executed that directly tested system functionality. In addition there were numerous test runs to validate system operation and obtain performance benchmarks. Out of the 108 tests executed, 64 test cases passed, 24 failed, and 20 were blocked. Failures covered a variety of areas including latency, fragmentation, mobility, and QoS. Most of these failures were traced to messaging SW related defects. The blocked tests cases primarily covered latency, special handling, and mobility.

####