On 25/11/2015 18:33, Michael Black wrote: > Don't know if this helps but here's a histogram from my ALL.TXT file > that shows 0.1 as the common offset. This is 1M entries...an > interesting lack of 0.8 dts...hmmm...there's only one in my file. How > is DT rounded? 0.1 sounds like would include all the delay in getting > the signal started and the rig switch to transmit which probably > wouldn't show up in a loopback. Hi Mike,
Only clock errors can contribute to positive DT figures if the Rx station clock is accurate. Well that should be the case, but it appears that we have a "fudge offset" applied somewhere to remove expected processing latency from both ends of the path. The way tones are synthesised is not related to keying the rig. There will some delay added due to clock errors and sound buffering. As far as the Tx synthesiser is concerned the signal starts right on time (again assuming an accurate clock). The start time is 1s into the Tx period. The DT is calculated from the signal symbol transitions (actually the complete "frame" of the recovered signal) not the start or end time of transmission or reception. 73 Bill G4WJS. ------------------------------------------------------------------------------ Go from Idea to Many App Stores Faster with Intel(R) XDK Give your users amazing mobile app experiences with Intel(R) XDK. Use one codebase in this all-in-one HTML5 development environment. Design, debug & build mobile apps & 2D/3D high-impact games for multiple OSs. http://pubads.g.doubleclick.net/gampad/clk?id=254741551&iu=/4140 _______________________________________________ wsjt-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wsjt-devel
