Setting Up the Real-Time Communication Test
Other versions of this page are also available for the following:
.gif "A hyphen indicates that the information in this topic is not relevant for this platform, or that the platform does not support the API that is listed.")
.gif "A checkmark indicates that the information in this topic is relevant for this platform, and that any API listed is also supported on this platform.")
8/27/2008
The setup for the Real-Time Communication Test is simple, as illustrated in the following diagram.
.gif "Bb203079.263c700d-0ea5-4710-a058-54d9fa1a6ef1(en-US,WinEmbedded.60).gif")
The following procedure demonstrates how to set up and run the Real-Time Communication Test.
Setting up and running the Real-Time Communication Test
Connect the host device and the subordinate device to the network, and verify the connection between them.
Connect the audio output from the Windows XP machine to the microphone of the host device and the subordinate device.
Start the media player on the Windows XP machine to play some audio clips repeatedly.
Run RTCSlave.exe on the subordinate device.
From this point, follow one of two methods:
- If the Windows Embedded CE 6.0 Test Kit (CETK) is connected to the host device, in the Windows Embedded CE Test Kit window, append –c "-FileTest \RTC_Tests.xml -FileVars \RTC_Vars.xml -s SlaveDeviceNetworkName**"** to the default command line for the test, where SlaveDeviceNetworkName is the network name of the subordinate device.
- Run the test.
- OR -
- Copy the required exe, dll, and xml files to the root directory of the host device.
- On the host device, run the following command:
tux -o -d rtchost.dll –c "-FileTest \RTC_Tests.xml -FileVars \RTC_Vars.xml -s SlaveDeviceNetworkName "
where SlaveDeviceNetworkName is the network name of the subordinate device.