hardware-tail.html 2.7 KB

12345678910111213141516171819202122232425262728293031323334353637383940414243444546474849505152535455565758596061626364656667686970717273747576777879808182
  1. <!-- hardware-tail.html begins here -->
  2. <h2 id="timing">PPS and GPSD:</h2>
  3. <p>Some GPS receivers offer a 1PPS (one pulse per second) output that
  4. GPSD is capable of passing along to <code>ntpd</code> for use as an
  5. extremely accurate clock source. These are marked as having PPS
  6. in the table above. The "Claimed Accuracy" figures are taken
  7. from manufacturers' data sheets, and have not been independently
  8. verified.</p>
  9. <p>Where specified, NTP time offsets have been measured by
  10. comparison with the NTP time service and reported by
  11. <code>gpsd</code>.</p>
  12. <p>Note that either a direct RS-232 connection or the "Magic Macx mod"
  13. (1PPS on the GPS chip connected to DCD on the serial-to-USB adaptor)
  14. is required for PPS. Typical gpsd/PPS users report ntp clock stability
  15. on the order of 1&mu;s (microsecond) for RS232, 1ms (millisecond) for
  16. USB. From GPSes that are native USB but not PPS-capable, GPSD can
  17. extract time information from the serial data accurate to about
  18. 250ms.</p>
  19. <a id="raw"></a>
  20. <h2>Raw Measurements and GPSD:</h2>
  21. <p>All gpses require "raw" measurements internally to compute a navigation
  22. solution. The ability for users to postprocess these measurements is then
  23. a function of firmware and protocol support.</p>
  24. <div>&nbsp;</div>
  25. <table style="border: 1px solid gray">
  26. <tr>
  27. <th>Receiver</th>
  28. <th>Raw</th>
  29. <th>Notes</th>
  30. </tr>
  31. <tr>
  32. <td>NavSync</td>
  33. <td style="text-align: center">No</td>
  34. <td>I asked them about raw measurements and they told me that a custom firmware build ($$$!) would be required, and that I probably wasn't authorized to get that data.</td>
  35. </tr>
  36. <tr>
  37. <td>SiRF</td>
  38. <td style="text-align: center">Partial</td>
  39. <td>sirfstar1 has raw data in message 5, sirfstar2 has raw data in message 28, sirfstar3 has some raw data in message 28 but carrier phase is not available. rumor has it that carrier phase is available as a premium feature in superstar3.</td>
  40. </tr>
  41. <tr>
  42. <td>u-blox</td>
  43. <td style="text-align: center">Partial</td>
  44. <td>The RXM-RAW message contains raw data. This is implemented in all Antaris chips. This is only implemented in the timing versions of Antaris4. In ublox5 it is "only available with premium feature raw data".
  45. </td>
  46. </tr>
  47. <tr>
  48. <td>Novatel SuperStarII</td>
  49. <td style="text-align: center">Partial</td>
  50. <td>Message #23 contains raw measurements in carrier-phase-enabled firmwares.</td>
  51. </tr>
  52. <tr>
  53. <td>Fastrax</td>
  54. <td style="text-align: center">Yes</td>
  55. <td>The "PSEUDO" message contains raw measurements</td>
  56. </tr>
  57. <tr>
  58. <td>Trimble</td>
  59. <td style="text-align: center">Yes</td>
  60. <td>Packet 0x5a contains raw measurements</td>
  61. </tr>
  62. <tr>
  63. <td>Thales AC12</td>
  64. <td style="text-align: center">Yes</td>
  65. <td>The PASHR,MCA message contains raw measurements.</td>
  66. </tr>
  67. </table>
  68. <hr>
  69. <script src="datestamp.js"></script>
  70. </div>
  71. </body>
  72. </html>