[arm-allstar] TX time

w9sbe w9sbe at comcast.net
Sat May 28 16:23:04 EDT 2022


I turned off the time report on all my nodes except one, because they all sounded off within a fraction of a second from each other. The reverb effect made it hard to understand.Never had them have the time errors that u are seeing.Sent from my Galaxy
-------- Original message --------From: Patrick Perdue via ARM-allstar <arm-allstar at hamvoip.org> Date: 5/28/22  2:37 PM  (GMT-06:00) To: Don Backstrom - AA7AU via ARM-allstar <arm-allstar at hamvoip.org> Cc: Patrick Perdue <borrisinabox at gmail.com> Subject: [arm-allstar] TX time Here's something I've been trying to figure out for a while.I've got several ASL nodes and one HamVoIP node connected together full time.With three of these nodes set to the same timezone, the TX time is drastically different.Here are three examples, captured just a few seconds apart. From the HamVoIP node:TX time today....................................: 05:47:36.278 From one of the ASL nodes captured a few seconds prior:TX time today....................................: 04:14:20:328 From another ASL node captured a couple of minutes later, during an active QSO:TX time today....................................: 05:24:46:164All of these nodes have been connected with no drops. What would cause these reports to be so different if all nodes are connected like this? Would the best average actually come from a node that never goes into RX for any reason, and only transmits?_______________________________________________ARM-allstar mailing listARM-allstar at hamvoip.orghttp://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstarVisit the BBB and RPi2/3/4 web page - http://hamvoip.org


More information about the ARM-allstar mailing list