1132451Sroberto<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> 2132451Sroberto 3132451Sroberto<html> 4132451Sroberto 5182007Sroberto <head> 6182007Sroberto <meta http-equiv="content-type" content="text/html;charset=iso-8859-1"> 7182007Sroberto <title>RIPE NCC interface for Trimble Palisade</title> 8182007Sroberto <link href="scripts/style.css" type="text/css" rel="stylesheet"> 9182007Sroberto </head> 10132451Sroberto 11182007Sroberto <body> 12182007Sroberto <h3>RIPE NCC interface for Trimble Palisade</h3> 13285612Sdelphij<p>Last update: 14285612Sdelphij <!-- #BeginDate format:En2m -->21-Oct-2010 23:44<!-- #EndDate --> 15285612Sdelphij UTC</p> 16182007Sroberto <hr> 17182007Sroberto <img src="../pic/driver43_2.jpg" alt="Trimble Acutime 2000" align="right"> 18182007Sroberto <h4>Synopsis</h4> 19182007Sroberto Address: 127.127.43.<i>u</i><br> 20182007Sroberto Reference ID: <tt>RIPENCC</tt><br> 21182007Sroberto Driver ID: <tt>RIPENCC</tt> 22182007Sroberto <h4>Description</h4> 23182007Sroberto <p>This is a special driver developed to be used in conjuction with the RIPE NCC clock card in the RIPE NCC Test Traffic Measurements project.</p> 24182007Sroberto <h4>Why this driver?</h4> 25182007Sroberto <p>The reason why we created a seperated driver for an antenna for which already a (vendor supplied) driver exist is a design decision. To be more specific, the standard Trimble interface uses a 12 pin connector. The cable sold by Trimble to connect to this wire is a very thick cable. Certainly not something you wish to run for several 100 meters through your building. And if you wanted to run it for 100 meters, you always would have to really run the cable, and didn't have the option to use existing wiring.<br> 26182007Sroberto </p> 27182007Sroberto <p>This is where we wanted more flexibility. We wanted to be able to use existing wiring in buildings. That leaded us to CAT-5(UTP) which only gives us 8 wires. Therefor we decided to redesing the use of the Trimble antenna. The Trimble supports two modes: EVENT driver and PPS mode. The default is to use the EVENT mode which needs all 12 wires. We only use the PPS timestamps for which we have enough with 8 wires. For our purposes this is more than fine.</p> 28182007Sroberto More information about the project can be found on the <a href="http://www.ripe.net/test-traffic" target="_new">Test Traffic Measurements</a> website. <img src="../pic/driver43_1.gif" alt="RIPE NCC clock card" align="right"> 29182007Sroberto <h4>RIPE NCC clock card</h4> 30182007Sroberto <p>The card is very a simple PCI card. The only feature on the bus it uses is the power supply. It uses this power supply to power the Trimble GPS antenna.</p> 31182007Sroberto <p>The card basicly just is a RS422 to RS232 converter. It gets the Trimble's RS422 signal on a RJ45 connector and transforms that to RS232 on a DIN9 connector. This connector should be loopbacked on the back of the machine to the serial port. As said, the card doesn't do any PCI data transfers.</p> 32182007Sroberto <p>The schematics of the interface card is available here: <a href="http://www.ripe.net/projects/ttm/Host_testbox/gps_if.pdf">gps_interface_schematic.pdf</a>. You are free to create this card yourself as long as you give some credit or reference to us. Note that we don't sell these cards on a commercial basis, but for interested parties we do have some spares to share.</p> 33182007Sroberto <p></p> 34182007Sroberto <h4>Monitor Data</h4> 35182007Sroberto <p>In the <tt>filegen clockstats</tt> file the following (example) data is collected:</p> 36182007Sroberto <pre> 37132451Sroberto52445 41931.275 127.127.40.0 U1 20.6.2002 11:38:51 13 11 38132451Sroberto52445 41931.395 127.127.40.0 C1 20062002 113851 6 364785 110.2 450 6.7 13 5222.374737 N 0453.268013 E 48 7 11 0 1 -14 20 0 -25 39132451Sroberto52445 41931.465 127.127.40.0 S1 07 1 1 02 59.3 291.5 39.3 40132451Sroberto52445 41931.485 127.127.40.0 S1 11 2 1 02 59.9 138.0 60.2 41132451Sroberto52445 41931.525 127.127.40.0 S1 01 4 1 02 48.4 185.7 28.3 42132451Sroberto52445 41931.555 127.127.40.0 S1 14 5 2 02 32.7 41.0 15.4 43132451Sroberto52445 41931.585 127.127.40.0 S1 20 6 1 02 59.9 256.6 78.0 44132451Sroberto52445 41931.615 127.127.40.0 S1 25 8 2 00 0.0 86.6 20.1 45132451Sroberto</pre> 46182007Sroberto <p>This is in the form of:</p> 47182007Sroberto <pre> 48132451SrobertoAll output lines consist of a prefix and a message, the prefix is: 49132451Sroberto[days since epoch] [sec.ms since start of day] [peer address] 50132451Sroberto 51132451SrobertoAnd all individual messages: 52132451Sroberto 53132451Sroberto*Primary UTC time packet: 54132451SrobertoU1 [date] [time] [trackstat] [utcflags] 55132451Sroberto 56132451Sroberto*Comprehensive time packet: 57132451SrobertoC1 [date] [time] [mode] [bias] [biasunc] [rate] [rateunc] [utcoff] [latitude] [longtitude] [alt] [vis sat](x8) 58132451Sroberto 59132451Sroberto*Tracking status packet: 60132451SrobertoS1 [prn] [channel] [aqflag] [ephstat] [snr] [azinuth] [elevation] 61132451Sroberto</pre> 62182007Sroberto <h4>Additional Information</h4> 63182007Sroberto <p><a href="../refclock.html">Reference Clock Drivers</a></p> 64182007Sroberto <hr> 65182007Sroberto <script type="text/javascript" language="javascript" src="scripts/footer.txt"></script> 66182007Sroberto </body> 67132451Sroberto 68285612Sdelphij</html> 69
