[Git][NTPsec/ntpsec][master] NIST guideline conformance, full URLs.

[Matt Selsky]

Matt Selsky pushed to branch master at NTPsec / ntpsec


Commits:
82e1734a by Paul Theodoropoulos at 2018-10-23T06:04:03Z
NIST guideline conformance, full URLs.

- - - - -


1 changed file:

- docs/driver_trimble.txt


Changes:

=====================================
docs/driver_trimble.txt
=====================================
@@ -10,7 +10,7 @@ include::html.include[]
 ["verse",subs="normal"]
 Name: trimble
 Reference ID: GPS
-Serial Port: /dev/trimble__u__; 9600bps 8N1/8O1
+Serial Port: /dev/trimble__u__; 9600 bps 8N1/8O1
 
 == Description ==
 
@@ -204,7 +204,7 @@ NTP error messages. Log entries generated by the driver will be of the form:
 
 [[t1]]+time1+ 'time'::
   Specifies the time offset calibration factor, in seconds and fraction,
-  with default 0.0. 'time1' should be set to about 20 milliseconds when using a
+  with default 0.0. 'time1' should be set to about 20 ms when using a
   Thunderbolt.
 
 [[t2]]+time2+ 'time'::
@@ -269,7 +269,7 @@ packets for time transfer, so use the 'Port A' RS232 connector. Operation with
 'Port B' is not supported. The event input must be attached to the host serial
 port's RTS or TXD lines -- set xref:f3[+flag3+] accordingly. The host will
 pulse the event input which will cause the receiver to emit a timestamp packet.
-Jitter of less than 400ns has been observed with a Palisade on a machine with
+Jitter of less than 400 ns has been observed with a Palisade on a machine with
 '-24 precision' using a 16550-compatible serial port and RTS for event
 triggering.
 
@@ -366,7 +366,7 @@ https://www.endruntechnologies.com/documentation.htm
 Check the receiver's LEAP setting. Incorrect values will cause a time offset.
 See the note for this command in the receiver manual.
 
-Jitter of less than 100ns has been observed with a Praecis Cf on a machine with
+Jitter of less than 100 ns has been observed with a Praecis Cf on a machine with
 '-24 precision' using a 16550-compatible serial port and RTS for event
 triggering, but the offset relative to a Palisade on the same machine may vary
 in steps by several microseconds, likely due to the receiver switching between
@@ -395,10 +395,10 @@ https://lists.ntp.org/pipermail/hackers/2006-April/002216.html
 
 Due to the lack of an event input the driver uses the timecode packet
 transmitted by the Thunderbolt shortly after the beginning of each second, but
-this packet is not very well aligned: delay varies from 7ms to 32ms depending
+this packet is not very well aligned: delay varies from 7 ms to 32 ms depending
 on the number of satellites the receiver is attempting to track, and the delay
 is not included in the timecode. For this reason the xref:t1[+time1+] should be
-set to about 20ms. The link:driver_pps.html[+pps+] driver should be used along
+set to about 20 ms. The link:driver_pps.html[+pps+] driver should be used along
 with this driver for best results, but a hardware modification is required to
 route the receiver's 1PPS output to the serial port DCD line for serial PPS.
 
@@ -438,10 +438,8 @@ mailto:sven_dietrich at trimble.com[*Sven-Thorsten Dietrich*] +
   Sunnyvale, CA 94088-3642 +
 
 mailto:fernandoph at iar.unlp.edu.ar[*Fernando P. Hauscarriaga*] +
-  www.iar.unlp.edu.ar/~fernandoph +
+  http://www.iar.unlp.edu.ar/~fernandoph +
   Instituto Argentino de Radioastronomia +
-  www.iar.unlp.edu.ar +
-
-*(last updated September 19, 2017)*
+  http://www.iar.unlp.edu.ar +
 
 include::includes/footer.txt[]



View it on GitLab: https://gitlab.com/NTPsec/ntpsec/commit/82e1734adc6e587eca5e9b7bcdefa22cbea01f21

-- 
View it on GitLab: https://gitlab.com/NTPsec/ntpsec/commit/82e1734adc6e587eca5e9b7bcdefa22cbea01f21
You're receiving this email because of your account on gitlab.com.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ntpsec.org/pipermail/vc/attachments/20181023/355bddba/attachment-0001.html>