19c2daa00SOllivier Robert<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> 29c2daa00SOllivier Robert 39c2daa00SOllivier Robert<html> 49c2daa00SOllivier Robert 59c2daa00SOllivier Robert <head> 6ea906c41SOllivier Robert <meta http-equiv="content-type" content="text/html;charset=iso-8859-1"> 79c2daa00SOllivier Robert <title>RIPE NCC interface for Trimble Palisade</title> 8ea906c41SOllivier Robert <link href="scripts/style.css" type="text/css" rel="stylesheet"> 99c2daa00SOllivier Robert </head> 109c2daa00SOllivier Robert 119c2daa00SOllivier Robert <body> 129c2daa00SOllivier Robert <h3>RIPE NCC interface for Trimble Palisade</h3> 13*2b15cb3dSCy Schubert<p>Last update: 14*2b15cb3dSCy Schubert <!-- #BeginDate format:En2m -->21-Oct-2010 23:44<!-- #EndDate --> 15*2b15cb3dSCy Schubert UTC</p> 169c2daa00SOllivier Robert <hr> 179c2daa00SOllivier Robert <img src="../pic/driver43_2.jpg" alt="Trimble Acutime 2000" align="right"> 189c2daa00SOllivier Robert <h4>Synopsis</h4> 199c2daa00SOllivier Robert Address: 127.127.43.<i>u</i><br> 209c2daa00SOllivier Robert Reference ID: <tt>RIPENCC</tt><br> 219c2daa00SOllivier Robert Driver ID: <tt>RIPENCC</tt> 229c2daa00SOllivier Robert <h4>Description</h4> 239c2daa00SOllivier Robert <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> 249c2daa00SOllivier Robert <h4>Why this driver?</h4> 259c2daa00SOllivier Robert <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> 269c2daa00SOllivier Robert </p> 279c2daa00SOllivier Robert <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> 289c2daa00SOllivier Robert 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"> 299c2daa00SOllivier Robert <h4>RIPE NCC clock card</h4> 309c2daa00SOllivier Robert <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> 319c2daa00SOllivier Robert <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> 32ea906c41SOllivier Robert <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> 339c2daa00SOllivier Robert <p></p> 349c2daa00SOllivier Robert <h4>Monitor Data</h4> 359c2daa00SOllivier Robert <p>In the <tt>filegen clockstats</tt> file the following (example) data is collected:</p> 369c2daa00SOllivier Robert <pre> 379c2daa00SOllivier Robert52445 41931.275 127.127.40.0 U1 20.6.2002 11:38:51 13 11 389c2daa00SOllivier Robert52445 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 399c2daa00SOllivier Robert52445 41931.465 127.127.40.0 S1 07 1 1 02 59.3 291.5 39.3 409c2daa00SOllivier Robert52445 41931.485 127.127.40.0 S1 11 2 1 02 59.9 138.0 60.2 419c2daa00SOllivier Robert52445 41931.525 127.127.40.0 S1 01 4 1 02 48.4 185.7 28.3 429c2daa00SOllivier Robert52445 41931.555 127.127.40.0 S1 14 5 2 02 32.7 41.0 15.4 439c2daa00SOllivier Robert52445 41931.585 127.127.40.0 S1 20 6 1 02 59.9 256.6 78.0 449c2daa00SOllivier Robert52445 41931.615 127.127.40.0 S1 25 8 2 00 0.0 86.6 20.1 459c2daa00SOllivier Robert</pre> 469c2daa00SOllivier Robert <p>This is in the form of:</p> 479c2daa00SOllivier Robert <pre> 489c2daa00SOllivier RobertAll output lines consist of a prefix and a message, the prefix is: 499c2daa00SOllivier Robert[days since epoch] [sec.ms since start of day] [peer address] 509c2daa00SOllivier Robert 519c2daa00SOllivier RobertAnd all individual messages: 529c2daa00SOllivier Robert 539c2daa00SOllivier Robert*Primary UTC time packet: 549c2daa00SOllivier RobertU1 [date] [time] [trackstat] [utcflags] 559c2daa00SOllivier Robert 569c2daa00SOllivier Robert*Comprehensive time packet: 579c2daa00SOllivier RobertC1 [date] [time] [mode] [bias] [biasunc] [rate] [rateunc] [utcoff] [latitude] [longtitude] [alt] [vis sat](x8) 589c2daa00SOllivier Robert 599c2daa00SOllivier Robert*Tracking status packet: 609c2daa00SOllivier RobertS1 [prn] [channel] [aqflag] [ephstat] [snr] [azinuth] [elevation] 619c2daa00SOllivier Robert</pre> 629c2daa00SOllivier Robert <h4>Additional Information</h4> 639c2daa00SOllivier Robert <p><a href="../refclock.html">Reference Clock Drivers</a></p> 649c2daa00SOllivier Robert <hr> 65ea906c41SOllivier Robert <script type="text/javascript" language="javascript" src="scripts/footer.txt"></script> 669c2daa00SOllivier Robert </body> 679c2daa00SOllivier Robert 689c2daa00SOllivier Robert</html> 69
