> The GPS docs "say" that the GPS chipset keep time to within 100ns. > However (and I assume this is to save power) they also say that the > position indication is only sent once per second.
100ns is really horrible GPS performance. However, it is likely more than good enough for using it to track time on a server. ntp over the net is good to the millisecond range anyway, and this is 4 orders of magnitude better. > In my case, the Bluetooth GPS would be talking to a Bluetooth dongle > hanging directly out a port of the server in question. ntpd will require direct access to the device, so it will need to be off the server in question. As to how accurate you'll be, that's another matter altogether. There's propigation delays that will give your system some fixed offset from true time. There's also likely going to be variance in latency due to bluetooth layer good, usb layer goo, interrupts, etc. This will likely be in the several tens to low hundreds of microseconds range given all the interconnect technology that's bettween the GPS receiver and the time keeping device. I don't think that the USB based com ports supports the pps time stamping interface. That's likely going to be what kills your project unless (a) the bluetooth dongle is connected via a sio port or (b) you hack the ucom driver to cope. You'd likely be money ahead by using a simpler, wired GPS receiver directly into a legacy serial port. Warner _______________________________________________ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
