66
77namespace OpenEphys . Onix1
88{
9-
109 /// <summary>
1110 /// Sends loopback data to the load testing device for closed-loop latency measurement.
1211 /// </summary>
1312 /// <remarks>
1413 /// This data IO operator must be linked to an appropriate configuration, such as a <see
1514 /// cref="ConfigureLoadTester"/>, using a shared <c>DeviceName</c>.
1615 /// </remarks>
17- [ Description ( "Sends analog output data to an ONIX breakout board." ) ]
16+ [ Description ( "Sends loopback data to an ONIX breakout board." ) ]
1817 public class LoadTesterLoopback : Sink < ulong >
1918 {
2019 /// <inheritdoc cref = "SingleDeviceFactory.DeviceName"/>
@@ -24,16 +23,16 @@ public class LoadTesterLoopback : Sink<ulong>
2423 public string DeviceName { get ; set ; }
2524
2625 /// <summary>
27- /// Creates and sends an loopback frame to the load testing device.
26+ /// Creates and sends a loopback frame to the load testing device.
2827 /// </summary>
2928 /// <remarks>
30- /// A loopback frame consists the <c>ulong</c> loopback value provided by <paramref name="source"/>
29+ /// A loopback frame consists of the <c>ulong</c> loopback value provided by <paramref name="source"/>
3130 /// that is prepended to a <see cref="ConfigureLoadTester.TransmittedWords"/>-element <c>ushort</c>
3231 /// array of dummy data. When the frame is received by hardware, the loopback value is subtracted from
3332 /// the current hub clock count on the load testing device and stored. Therefore, if the loopback
34- /// value is is that of a previous <see cref="DataFrame.HubClock"/> from the <see
33+ /// value is that of a previous <see cref="DataFrame.HubClock"/> from the <see
3534 /// cref="LoadTesterData"/> with the same <see cref="DeviceName"/> as this operator, this difference will provide a
36- /// hardware-timed measurement of real-time latency. The the variably-sized dummy data in the loopback
35+ /// hardware-timed measurement of real-time latency. The variably-sized dummy data in the loopback
3736 /// frame is used for testing the effect of increasing the frame size, and thus the write
3837 /// communication bandwidth, on real-time latency.
3938 /// </remarks>
0 commit comments