En Unite Inst

UNITE
V2.1 Installation Manual
Ref. No. 0311475
August 2, 2010
Ahead of the Curve
SM
To contact SERCEL
Europe Nantes, France Sales; Customer Support; Manufacturing & Repair. B.P. 30439, 16 rue de Bel Air 44474 Carquefou Cedex Tel: +33 2 40 30 11 81, Fax: +33 2 40 30 19 48 Hot-Line: Land: +33 2 40 30 58 88 Marine: +33 2 40 30 59 59 Navigation: +33 2 40 30 69 87 E-mail: sales.nantes@sercel.com customersupport.land@sercel.com customersupport.marine@sercel.com customersupport.navigation@sercel.com repair.france@sercel.com streamer.repair@sercel.com www.sercel.com St Gaudens, France Vibrator Customer Support; Vibrator Manufacturing & Repair; Streamer Manufacturing & Repair. Tel: +33 5 61 89 90 00, Fax: +33 5 61 89 90 33 Hot Line: +33 5 61 89 90 91 Les Ulis, France Sales; Customer Support Tel: +33 1 69 93 83 60, Fax: +33 1 69 81 78 09 E-mail: sales.nantes@sercel.com Hot Line: +33 6 15 54 13 96 Brest, France Sales; Customer Support Tel: +33 2 98 05 29 05; Fax: +33 2 98 05 52 41 E-mail: sales.nantes@sercel.com Toulon, France Sales; Customer Support Tel: +33 4 94 21 69 92; Fax: +33 4 94 21 73 44 E-mail: sales.msd@sercel.com support.msd@sercel.com Toulouse, France Sales; Customer Support Tel: +33 5 61 34 80 74; Fax:+33 5 61 34 80 66 E-mail: sales@metrolog.com support@metrolog.com Alfreton, U. K. Streamer Manufacturing & Repair; Customer Support. Tel: +44 1 773 605 078, Fax: +44 1 773 541 778 E-mail: streamer.repair@sercel.com Liphook, U. K. Quest Geosolutions Ltd Tel: +44 1 428 751565, Fax: :+44 1428 751566 E-mail: enquiries@qgsl.com Larbert, U. K. (Sercel England Ltd.) Customer Support Tel: +44 1324 556 777, Fax: +44 1324 556 222 Trondheim, Norway (Optoplan AS) Tel: +47 73820500, Fax: +47 73820599 Russia Customer Support; Repair. Moscow, Russia Tel: +7 495 644 08 05, Fax: +7 495 644 08 04 E-mail: repair.cis@geo-mail.org support.cis@geo-mail.org Surgut, Russia Tel: +7 3462 28 92 50 North America Houston, USA Sales; Customer Support; Manufacturing & Repair; Tel: +1 281 492 66 88, Fax: +1 281 579 75 05 Hot-Line: +1 281 492 66 88 E-mail: sales.houston@sercel.com HOU_Customer.Support@sercel.com HOU_Training@sercel.com Calgary Sales; Customer Support; Manufacturing. Tel: +1 403 275 3544, Fax: +1 403 295 1805 E-mail: Cal_Customer.Support@sercel.com Middle East Dubai, U. A. E. Sales, Customer Support, Repair. Tel: +971 4 8832142, Fax: +971 4 8832143 Hot Line: +971 50 6451752 E-mail: dubai@sercel.com repair.dubai@sercel.com Far East Beijing, P. R. of China R & D. Tel: +86 106 43 76 710, Fax: +86 106 43 76 367 E-mail: support.china@geo-mail.com repair.china@geo-mail.com Xian, P. R. of China Manufacturing & Repair. Tel / Fax: +86 29 8222 9504 Xushui, P. R. of China Manufacturing & Repair. Tel:+86 312 8648355, Fax:+86 312 8648441 Singapore Streamer Manufacturing & Repair; Customer Support. Tel:+65 64 17 70 00, Fax:+65 6 545 1418
UNITE Installation Manual
In no event shall Sercel be liable for incidental or consequential damages or related expenses resulting from the use of this product, or arising out of or related to this manual or the information contained in it, even if Sercel has been advised, or knew or should have known of the possibility of such damages. The information included in this documentation is believed to be accurate and reliable. However, Sercel reserves the right to make changes to its products or specifications at any time, without notice, in order to improve design or performance and to supply the best possible product. This documentation does not form in any way a contractual agreement of sales promise on the part of Sercel. Software mentioned in this documentation is sold under a precise licence agreement and as such the documentation may cover technical areas for which the user may not have a final licence. No part of this documentation, or any of the information included herein may be modified or copied in any form or by any means without the prior written consent of Sercel. 2008, 2009 Sercel England Ltd. All Rights Reserved. Printed in France. Sercel, 428XL, AIB, CCU, DH, DPG, DSD, e-428, eSQC Pro,e-UNITE, FDU, FDU-428,Link, MGA, MRU, PFT, RAU, SGA UCI, ,VE464, VQC88 are all trademarks of Sercel. All rights reserved. UNIX is either a registered trademark or trademark of The Open Group in the United States and/or other countries.Microsoft and Windows are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries. Other product and company names mentioned herein may be the trademarks of their respective owners.
August 2, 2010
UNITE Installation Manual
Revision history
Date of revision
June 2008 Jan. 2009 June 2009 June 2010 p. 188
Chapters or pages affected
Description of revision or reason for change

Initial release V1.0 S16F-R1430 RAID storage system Release 2.1
August 2, 2010
Software Licence Agreement

Sercel is willing to license the accompanying software package to you only upon the condition that you accept all the terms contained in this licence agreement. Read carefully the following terms and conditions before opening the software media package. By opening the software media package you agree to the terms and conditions of this agreement. agreement between Licensee and any third parties. If Licensee is located in a country which requires registration of software licences with government authorities, Licensee shall be responsible for meeting all requirements of such registration.
II. PROPRIETARY RIGHTS

Licensee acknowledges that the Software is and remains the property of Licensor and contains trade secret information and Know How proprietary to Licensor and that any breach of the provisions of this Article by Licensee would cause Licensor to suffer immediate and irreparable harm. In the event of such breach, Licensor shall have, in addition to any and all remedies at law, the right to an injunction, specific performance or other equitable relief. Title to Software remains with Licensor at all times and no title or ownership of Software is transferred under this Agreement. Licensee shall take no action that might impair any right, title or interest of Licensor in or to the Software. Licensee shall not have any rights in or to any trademark or trade name owned by Licensor with respect to the Software. Licensee shall not disclose the Software to any third party without Licensor's prior written agreement. Licensee shall inform all its employees having access to the Software of the Confidential nature of the Software and their obligations with respect thereto. Licensee shall ensure that its employees and any third party to whom disclosure is authorised strictly abide by the confidentiality restrictions set forth in this Agreement.
I. SOFTWARE LICENCE
Software acquired under these terms and conditions is not sold, but merely licensed under the provisions of this Article I. 1.Licence Grant: Subject to the terms and conditions of this Agreement, Licensor grants to Licensee a personal, non exclusive, non transferable licence to use the object code version of the Software solely for licensee's own internal use. 2.Number And Type Of Licences: In consideration of payment of the licence fee, Licensor will provide Licensee with (a) password(s) corresponding to the Software. 3.Use Of Software: In support of its own internal use of the software, Licensee may only: (a) Use the object code version of the Software, (b) Copy the Software into machine readable or printed form for backup purposes only (2 copies maximum), provided that all copies and partial copies include Licensor's copyright notices, (c) Except with regard to training books and materials, copy the documentation as required for Licensee's own use, provided that all copies shall include Licensor's copyright notices. Except as expressly provided herein, Licensee may not: (a) Copy, modify, merge, reverse engineer, reverse assemble, decompile, or disassemble the Software, (b) Remove any labels or notices from the Software, (c) Distribute, publish, transfer, sublicense, or make the Software or program documentation available to other organisations or persons, (d) Create or attempt to create derivative works from the Software, (e) Transfer the Software to another Hardware without approval of Licensor and payment of the applicable fee, (f) Use the Software to violate the terms and conditions of any other software licensing
UNITE Installation Manual August 2, 2010
III. WARRANTY
Software warranty period is ninety (90) days from the date of installation. Licensor warrants that Software was developed with reasonable diligence and skill and that it substantially conforms to published documentation. Licensor's sole responsibility under this warranty shall be to correct or replace any Software which does not so conform, provided that Licensee notifies Licensor in writing during the warranty period. Licensee has had the opportunity to inspect Software: except as expressly provided above, Software is deemed to be accepted "AS IS" without further warranty. The warranty does not cover, and Licensor shall not be responsible for any failure or defect and resulting damage caused by installation or use of Software not furnished by Licensor, accident (including damage during shipment), neglect, misuse
5
Software Licence Agreement

or abuse, or exposure to conditions beyond the environmental power and operating constraints specified by Licensor. The warranty does not cover defects or failure resulting from modification or installation by someone other than Licensor or its authorised representative. tions thereof, provided Licensee has been given ten (10) days notice prior to termination, during which Licensee has failed to cure the breach to Licensor's reasonable satisfaction. Upon termination, Licensee shall return to Licensor all Software and copies thereof, including merged portions in any form, or provide written confirmation that Software and such copies/portions have been destroyed. Termination is without prejudice to any other rights or remedies available to Licensor at contract or at law. Termination does not relieve Licensee of its obligation to pay the licence fee(s), the maintenance fees up to and including the running period, as well as any other charges and fees due to Licensor. In addition, if any act by Licensee causes the cancellation or rescheduling of Licensee's order, Licensee shall reimburse Licensor for the resultant costs incurred.
IV. PATENTS AND COPYRIGHTS

Licensor shall defend, at its expense, any claim or suit brought against Licensee alleging that Software infringes upon a patent, copyright or other proprietary right, and shall pay all costs and damages finally awarded, provided that Licensor is given prompt written notice of such claim, reasonable information and assistance, and sole authority to defend or settle the claim. In the defence or settlement of the claim, Licensor may obtain for Licensee the right to continue using Software, replace or modify Software (without substantially changing the original functions of Software) so that it becomes non-infringing, or, if such remedies are not reasonably available, grant Licensee a refund for Software (net of reasonable depreciation) upon its return. Licensor shall not have any liability if the infringement is based upon modifications of Software or the use or sale of Software in combination with products not furnished by Licensor.
VII. GENERAL
Except for the obligation of payment, neither party shall be liable for non-performance caused by circumstances beyond their reasonable control including, but not limited to, work stoppages, delay in transportation, delay in delivery by vendors, fire, civil disobedience, war or acts of nature. Except as provided herein, this Agreement constitutes the entire agreement between the parties with respect to the subject matter hereof, and shall supersede and cancel all prior agreements or understandings either oral or written, including any different, conflicting or additional terms and conditions which may appear on any contract, purchase order or form submitted by Licensee. During the term of this Agreement, the relationship of Licensor to Licensee is that of an independent contractor only. This Agreement shall be governed, construed and interpreted in accordance with the laws of France. The Tribunal du Commerce of Nantes (Trade Court of Nantes) France, shall have the exclusive jurisdiction to resolve any dispute or disagreement between the parties relating to this Agreement. All notices, authorisations and requests in connection with this Agreement shall be in writing and shall be deemed given on the day they are received by hand, first class mail, "FAX" or "TELEX" at the addresses herein or thereafter notified by either party to the other in writing.
V. LIMITATION OF LIABILITY
Except as expressly set forth herein, there are no representations of warranties by Licensor, expressed or implied, including but not limited to implied warranties of merchantability and fitness for a particular purpose. Licensor does not warrant that the operation of Software shall be uninterrupted or error free, that the functions contained in the Software shall meet Licensee's requirements or operate in the combinations selected by Licensee, or that every error or defect may be corrected pursuant to the warranty or maintenance services. In no event will Licensor or its suppliers be liable for indirect, consequential, incidental, punitive, special or exemplary damages (including loss of data, production, profits or use of hardware) to Licensee or any other party. Under no circumstances will Licensor or its suppliers be liable for damages exceeding the amount of the licence fee paid for Software to Licensor by Licensee. These limitations will apply regardless of the form of action, whether in contract or tort.
VI. TERMINATION
Licensee may terminate the Agreement at any time. Licensor may terminate the Agreement if Licensee fails to comply with the terms and condi6
Table of Contents
Revision history . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4
Introduction
About the Unite documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . .16 The Unite system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17
Full-Wireless Unite configuration . . . . . . . . . . . . . . . . . . . . .17 Infill Unite configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . .20 RAU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .22 RAU-D . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .22 CAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .23 Data Harvester . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .23 Portable Field Terminal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .24 Central Control Unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .24 Accessories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .25 Peripheral equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .25
Wireless system operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .27

Communications Infrastructure . . . . . . . . . . . . . . . . . . . . . . . . .27 Infrastructure Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .28 Autonomous Mode operation . . . . . . . . . . . . . . . . . . . . . . . . . .30
IT topology information for Unite recorder deployment . . . . . . . . .33

Local user topology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .34
UNITE Installation Manual August 2, 2010 7
Table of Contents
Intranet user topology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .35 Internet user topology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .36 Intranet/Internet user topology . . . . . . . . . . . . . . . . . . . . . . . . . .37
Recorder installation
Networking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .40 Identifying Ethernet interface ports . . . . . . . . . . . . . . . . . . . . . . . . .43 AC Power requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .44 Server computer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .45
Shock-mount parts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .45 Server computer connectors . . . . . . . . . . . . . . . . . . . . . . . . . . . .46 Tape drive interface cards . . . . . . . . . . . . . . . . . . . . . . . . . . . . .48 Server hardware installation kit . . . . . . . . . . . . . . . . . . . . . . . . .49
LCI-428. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .50
Shooting system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .54
Auxiliary channels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .55 FDU-428 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .56

Links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .57
CAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .58 LCD display anchoring. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .59
Server software installation

Full-Wireless Unite configuration. . . . . . . . . . . . . . . . . . . . . . . . .62
Installing Linux Redhat Enterprise V4 . . . . . . . . . . . . . . . . . . .62
e-Unite server software. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .65

Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .65 Installing e-Unite server software . . . . . . . . . . . . . . . . . . . . . . .66
Setting up the disk volumes and RAID . . . . . . . . . . . . . . . . . . . . . .70 Single-machine Infill Unite configuration . . . . . . . . . . . . . . . . . .71
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .71
8 UNITE Installation Manual August 2, 2010
Table of Contents
Installing Host Redhat Enterprise Linux WS4 . . . . . . . . . . . .72 Installing 428XL server software on Host Linux . . . . . . . . . .80 Installing the VM and Unite OS . . . . . . . . . . . . . . . . . . . . . . . .80 Starting up the VM and the Unite OS . . . . . . . . . . . . . . . . . . . .80 Setting up the VM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .81 Setting up the local parameters in the Unite OS . . . . . . . . . . . .83 Disabling the Plot process on the 428XL . . . . . . . . . . . . . . . . .84 Installing e-Unite V2.1 software on Guest Red Hat . . . . . . . . .85
Two-machine Infill Unite configuration . . . . . . . . . . . . . . . . . . . .86

Settings for importing SEG-D files via NFS . . . . . . . . . . . . . . .87 Settings for copying SEG-D files from a NAS . . . . . . . . . . . . .90
Special instructions for VE464 users . . . . . . . . . . . . . . . . . . . . . . . .92 Server ID code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .93 Licence code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .94 Saving e-Unite parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .95 Uninstalling e-Unite server software . . . . . . . . . . . . . . . . . . . . . . . .96 Server software patches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .97 Firmware upgrading . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .101 Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .102
Terminal window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .102 Terminal window on a serial port . . . . . . . . . . . . . . . . . . . . . .102 USB stick management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .102
Client computer
Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .106 Installing RedHat Enterprise WS4 Update6 . . . . . . . . . . . . . . . . . .107
Hardware specific information . . . . . . . . . . . . . . . . . . . . . . . .107 Installing Linux RedHat on e-Unite Client computer . . . . . . .107
User account . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .111

Linux user account . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .111 Windows user account . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .112
Table of Contents
Installing Client software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .113 Screen management on Linux client. . . . . . . . . . . . . . . . . . . . . . . .116

Installing a screen management driver for Linux . . . . . . . . . .116 Multi-screen management . . . . . . . . . . . . . . . . . . . . . . . . . . . .116 Updating the NVIDIA driver . . . . . . . . . . . . . . . . . . . . . . . . . .119
Setting the computers IP address. . . . . . . . . . . . . . . . . . . . . . . . . .121

Linux Client host computer . . . . . . . . . . . . . . . . . . . . . . . . . . .121 Windows Client host computer . . . . . . . . . . . . . . . . . . . . . . . .122
Remote access to Server from a Linux Client . . . . . . . . . . . . . . . .124 Remote access to Server from a Windows Client . . . . . . . . . . . . .125
Installing Cygwin software . . . . . . . . . . . . . . . . . . . . . . . . . . .125 Configuring Cygwin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .127 Working with Cygwin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .128
Uninstalling e-Unite Client software . . . . . . . . . . . . . . . . . . . . . . .130 Client software patches. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .131 First-time log-in . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .134
PFT software
Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .136 Exiting the PFT application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .137 Installing PFT software from a USB drive . . . . . . . . . . . . . . . . . . .139 Installing ActiveSync on a Windows PC.. . . . . . . . . . . . . . . . . . . .141
Prerequistes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .141 Install Microsoft ActiveSync . . . . . . . . . . . . . . . . . . . . . . . . . .141 Connect the Nomad device via USB . . . . . . . . . . . . . . . . . . . .141 Set-up ActiveSync . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .142
Reinstalling the Nomad firmware. . . . . . . . . . . . . . . . . . . . . . . . . .144 Nomad device setttings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .149

Setting device parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . .149 Button settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .149
Table of Contents
Configuring Wireless Networking . . . . . . . . . . . . . . . . . . . . . .155 Generate System Information Snapshot . . . . . . . . . . . . . . . . .158
Install software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .160

Copy CAB files to the Nomad device . . . . . . . . . . . . . . . . . . .160 Install driver software on the Nomad . . . . . . . . . . . . . . . . . . .163 Install e-Unite software on the Nomad . . . . . . . . . . . . . . . . . .164 Reset the Nomad . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .166
Viewing Wireless Network Settings. . . . . . . . . . . . . . . . . . . . . . . .167 Transferring RAU List by USB drive. . . . . . . . . . . . . . . . . . . . . . .169 Configuring the PFT application . . . . . . . . . . . . . . . . . . . . . . . . . .170
Data Harvester software

Data Harvester Software Installation . . . . . . . . . . . . . . . . . . . . . . .172
Setting the IP address of a Data Harvester tablet PC . . . . . . . .173
Windows UCI software

Installing the UCI Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .176 UCI Networking set-up. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .178 RAU Firmware Update. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .180
Peripherals
Plotters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .182
Mount parts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .182 VERITAS V12 plotter settings . . . . . . . . . . . . . . . . . . . . . . . .184 V12 / e-Unite settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .185 Ethernet port upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .185
Infortrend S16F-R1430 RAID system . . . . . . . . . . . . . . . . . . . . . .188

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .188 Cabling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .188 Getting started . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .189
Table of Contents
Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .191
Tape drives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .196

Tape drive shock-mount assembly . . . . . . . . . . . . . . . . . . . . .196 Supported tape drives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .197 FUJI 3490-E or 3590 SCSI address . . . . . . . . . . . . . . . . . . . . .198 Resetting M2488 T4 drive initialisation parameters . . . . . . . .201 LTO drive SCSI address . . . . . . . . . . . . . . . . . . . . . . . . . . . . .204 CYPRESS 3490E-DIF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .205 3592 cartridge drive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .208
NAS server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .214

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .214 Shock-mount assembly . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .215 Attaching a NAS system to the e-Unite local network . . . . . .216 Setting up NAS parameters . . . . . . . . . . . . . . . . . . . . . . . . . . .217 Attaching a e-Unite NAS system to another network . . . . . . .222 Operating System software reinstallation . . . . . . . . . . . . . . . .223 NAS system rescue . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .226
FTP server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .229

Installing server software . . . . . . . . . . . . . . . . . . . . . . . . . . . . .229 Server settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .230
MDR or RVT300 virtual tape recorder . . . . . . . . . . . . . . . . . . . . .233 Vehicle Tracking box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .236
Field Equipment deployment

Infrastructure Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .238
System Planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .238
Deployment procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .243

Deploy CANs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .243 Deploy RAUs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .243
Table of Contents
Autonomous Operation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .245 RAU Field Deployment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .247 CAN Field Deployment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .251
Equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .251 Assembly . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .251
MESH Field Deployment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .255

Deployment Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .256 Mesh Viewer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .257
Antenna Mast Field Deployment . . . . . . . . . . . . . . . . . . . . . . . . . .267

Erecting the TeleMast . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .269 How to dismantle the Antenna Mast . . . . . . . . . . . . . . . . . . . .274
Fibre Optic Cable Deployment. . . . . . . . . . . . . . . . . . . . . . . . . . . .275

Fibre Optic Deployment (Two-Man) . . . . . . . . . . . . . . . . . . . .276 Fibre Optic Cable Retrieval . . . . . . . . . . . . . . . . . . . . . . . . . . .277
10 Connectors and cables

LCI-428. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .280
BLASTER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .280 XDEV2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .284
FDU-428 input connector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .285 Cables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .286

SGD-S Blaster Controller to LCI-428 . . . . . . . . . . . . . . . . . . .286 ShotPro to LCI-428 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .287 ShotPro I to LCI-428 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .288 Macha to LCI-428 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .289 BoomBox to LCI-428 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .290
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 291
13
Table of Contents
14
Chapter
Introduction
In this chapter:
About the Unite documentation (page 16) The Unite system (page 17) Wireless system operation (page 27) IT topology information for Unite recorder deployment
(page 33)
15
Introduction About the Unite documentation
About the Unite documentation

The documentation coming with the Unite system consists of the following manuals: Installation Manual (0311475): this manual, providing an introduction to the Unite System, installation information, some basic instructions for getting started with the system, and some system deployment information that will help get a Unite System operating in the field. Users Manual Volume 1 (0311476): describes the user interfaces of the various Unite System software packages and how to use them. Users Manual Volume 2 (0311477): contains reference information on data formats etc. Users Manual Volume 3 (0311478): contains technical reference information (e.g. filter charts, theory of tests, technical data, specifications). This manual assumes that you are familiar with Microsoft Windows and PC computers, and are familiar with standard menus, commands and operations. Throughout this manual, Sercel England Ltd is referred to as Sercel for the purposes of simplicity. Each and every occurence of the term Sercel can be used interchangeably with the term Sercel England Ltd.
16
Introduction The Unite system
The Unite system

In this section: Full-Wireless Unite configuration (page 17) Infill Unite configuration (page 20) RAU (page 22) RAU-D (page 22) CAN (page 23) Data Harvester (page 23) Central Control Unit (page 24) Accessories (page 25) Peripheral equipment (page 25)
Full-Wireless Unite configuration

The Unite System is a Land Seismic Data Acquisition System designed to provide ease of layout in difficult terrains or situations, using wireless techniques for all communications between the central unit in the recording truck and the remote acquisition units (RAUs). After the RAUs are deployed, a Portable Field Terminal (PFT) deployment tool is used in order to record the serial number of each RAU so that it can be associated with a Receiver Point in the Unite Control Interface (UCI). RAUs start acquiring data automatically when they gain GPS lock, and that data, along with GPS time-stamps, is written to their internal flash memory. If the RAU is within range of the recording truck, via a Cell Acces Node (CAN), the e-Unite server starts retrieving the data immediately. This mode of operation is referred to as Infrastructure mode. If the RAU is out of range of the communications infrastructure, the data is only retrieved when a Data Harvester comes within range of
the RAU (this mode of operation is referred to as Autonomous mode), or when the RAU is moved closer to a CAN.
GPS time Timestamped sample stream
Autonomous-mode RAU (stores data locally)
GPS time Data Harvester
GPS time
Complete shots UCI GPS receiver LCI-428 acquisition unit
e-Unite server
Shot descriptor files
SEGD files (NAS)
Auxiliary channels
CAN
Recording truck
5.8 GHz 2.4 GHz Infrastructure-mode RAU (real-time acquisition)
CAN
Figure 1-1 Full-Wireless Unite configuration
This installation manual is intended for the two operating modes. The Unite system is typically used as follows (see Figure 1-2 on page 19):
18
Shot Descriptor Files 2
CAN 3 RAU
1
RAU RAU RAU
SOURCE
e-428
(acquisition)
UCI
(completion)
6 5 Stacking Correlation SEGD finalization Completed Files
Data Harvester
Figure 1-2 e-Unite server (e-428 + UCI software)
1.
The acquisition unit (LCI-428) in the recording cab controls the source for each shot. The data from the RAUs within range of the communications infrastructure are transferred in real-time to the e-Unite server via the CANs. The e-428 application generates a shot descriptor file (including the shot header plus the data from auxiliary FDU channels). The UCI application complements the shot descriptor file with the data from the Infrastructure-mode RAUs, and waits for the data from the Autonomous-mode RAUs to be harvested. The data recorded in the RAUs operating autonomously is harversted via the Data Harvester Tablet PC. The time-stamped sample stream from the Data Harvester Tablet PC and the shot descriptor files are merged in the UCI on the e-Unite server in order to generate complete shot files. The e-Unite server processes the complete shot files and records them to SEGD files.
2. 3.
4. 5.
6.
19
Infill Unite configuration

GPS time Timestamped sample stream
Autonomous-mode RAU (stores data locally)
GPS time Data Harvester
GPS time
Complete shots UCI GPS receiver LCI-428 acquisition unit
e-Unite server
Shot descriptor files
SEGD files (NAS)
Auxiliary channels
CAN
Recording truck 5.8 GHz
2.4 GHz Infrastructure-mode RAU (real-time acquisition)
CAN
LAUX-428 428 Link
428 Link
LAUL
Figure 1-3 Infill Unite system
20
The Infill Unite configuration uses a traditional 428XL wireline telemetry spread jointly with Wireless patches. Wireless patches are used where cables cannot be deployed. In the Infill Unite system, two desktops are used: 428XL desktop, which may be available on the Server computer or a remote (Client) computer, allowing you to open the standard 428XL GUI (Graphic User Interface). The e-428 application controls shots, and generates SEGD files containing all wireline traces. If wireless channels are described in the spread, they are mute and the resulting traces in the SEGD files are dead. e-Unite desktop, only available on the server computer, allowing you to open the e-Unite GUI and the UCI GUI. Each SEGD file generated by the 428XL is imported into the UCI application. If it includes wireless traces, these (dead) traces are replaced with the matching harvested RAU traces. Otherwise SPS files can be loaded to the UCI and used to append RAU traces to the incoming 428XL SEG-D file. The UCI works the same way as in Full-Wireless configuration, but in the UCI applications Operation Recording Settings window, you will have to choose the Import SEG-Doption. There are two ways of installing an Infill Unite system: Either using a single machine: the e-Unite application is installed on a Virtual Machine (VM) created on a 428XL (e-428) host machine. Or using two machines: in high production environments, running the eUnite software on a separate server will give performance increases as well as allowing a separate user to manage the RAU boxes and final export without interrupting production, leaving the observer to concentrate on the 428XL as normal. No physical update to the 428XL server is required. One machine is used to host e428 server software, and another machine is used to host eUnite software. The two machines may or may not be attached to the same local network:
- If the two machine are attached to the same local network, the eUnite server will retrieve the SEG-D files to import via a NFS (Network File System) share with the 428XL server. - Otherwise, for example if eUnite server is set up at the base camp, the SEG-D files can be transferred from the 428XL server using any suitable media (NAS drive, USB drive etc.).
RAU
The Remote Acquisition Unit contains the necessary electronics for GPS, WLAN and data acquisition. The top dome of the RAU casing contains the GPS and WLAN antennae. The RAU is equipped with a theft protection. As soon as the external battery is unplugged, RAU will wake up every 10 minutes and will scan for an access point so as to send its GPS position.
Figure 1-4 RAU
RAU-D
The RAU-D is a remote acquisition unit that acquires data from a DSU3-SA rather than a geophone array. The DSU3-SA (Standalone 3-component Digital Sensor Unit) is an integrated package including station electronics and three digital accelerometers based on the MEMS (Micro-machined Electro-Mechanical Sensor) technology.
RAU-D DSU3-SA
Figure 1-5 RAU-D and DSU3SA
22
CAN
All RAUs operated in Infrastructure mode are grouped in cells controlled by Cell Access Nodes (CANs). Once data is acquired, each RAU immediately transmits it to its associated CAN via a 2.4 GHz wireless link, from where it is transmitted through the 5.8 GHz backbone to the Unite Central Unit for recording.
Antenna set (2.4 GHz, communications with RAU)
Cell Acces Node (CAN)
Backhaul kit (5.8 GHz, communications with other CAN)
Figure 1-6
An alternative fibre optic link is available to supplement the CAN backbone.
Data Harvester
The Data Harvester, hosted on a Tablet PC, is used to retrieve the seismic samples stamped with GPS time from each Autonomous-mode RAU, via a built-in wireless access point. The Data Harvester also harvests QC/state of health information, e.g. battery status. It cannot be used to set acquisition parameters (sample rate, filter, gain, etc.).
Figure 1-7 Data Harvester (DH)
23
Portable Field Terminal

The Portable Field Terminal (PFT) is used to associate the ID number of each RAU with the Stake ID at which it is placed.
Figure 1-8 PFT
Central Control Unit

e-Unite software
The e-Unite software controls the seismic source. It also performs all the requested computations (stacks, correlations) before recording data onto tapes or disks. e-Unite software includes a component (UCI server) that generates stake marker files and takes care of completing the shot files with the seismic data from the CAN and from the Data Harvester. Supported software platforms for the e-Unite system include Windows and Linux (server software runs on Linux only). Taking benefits of its client/server architecture, e-Unite allows secured remote access through Internet connections.
LCI-428
The LCI-428 is used as interface between the source controller and the e-Unite client/server architecture, in the recording cab.
Figure 1-9 LCI-428
24
Accessories
External battery charger for 12V SLA batteries (12V, 2A, 10bay, 110 V or 220/240 V). Optic fibre backhaul kit 500 m optic cable for CAN-to-CAN connection. Dongle for setup and checking of the RAU with no sensor connected.
Battery charger
Optic fibre backhaul kit
Dongle
Figure 1-10
Peripheral equipment
UCI software running on Windows
UCI also runs on Windows (used at staging areas to configure and test RAUs before deployment). The Windows version of the UCI is known as the CCU (Central Control Unit).
Tape drives
Cartridge tapes can be used as magnetic media for recording in demultiplexed format. The 3490 or 3590 cartridge drive makes it possible to record a 3480 IBM compatible cartridge tape, directly in the field. For dual drive recording, the standard software provides alternate or simultaneous recording without any additional devices. Up to 6 drives can be connected.
25
Removable disk
Large-capacity, removable disks rather than tape drives can be used to record your SEGD files, allowing zero-dead-time shooting. The SERCEL Network Attached Storage system (NAS) uses the Redundant Array of Independent Disks (RAID) technology, providing the data redundancy needed for a highly secure system.
Quality Control
SERCEL QC software (eSQC Pro) allows Quality Control of the seismic data.
Plotter
An external plotter can be attached to the network to generate a paper record of the acquired seismic data, either in read-after-write or in playback mode.
Printer
A standard colour printer allows automatic printouts of observers reports, or log from any operation, or snapshots.
26
Introduction Wireless system operation
Wireless system operation

Communications Infrastructure
Backhaul kit
. ax m
1 km max.
km
Wireless cell (380 RAUs max.)
Figure 1-11 Real-time acquisition
Real-time acquisition requires a communications infrastructure. This section describes the fundamentals of how this communications infrastructure operates.
Wireless Cells
The Wireless Cells in the network are provided by CANs, which contain IEEE 802.11b Access Points, to implement the network connectivity to the RAUs. The Wireless Cells may provide a single 802.11b channel supplied by a single Access Point, or the CAN may be configured with additional Access Points up to a maximum total of three, combined with sectored antennae, to divide the Wireless Cell into three sectors to increase available bandwidth within the cell.
Fibre-optic Backhaul
Although the Wireless Backhaul is suitable for use in most conditions of terrain and vegetation, the wireless range may be reduced by dense
vegetation, such that under some conditions, a Wireless Backhaul may be insufficient. As an option to a Wireless Backhaul, a Fibre-optic Backhaul kit is provided to connect a wireless cell to the central unit. The fibre-optic backhaul makes it possible to directly connect a fibre from CAN to CAN and save power consumption.
Infrastructure Mode
Basic Network Operation
The network operates on a centralised control basis, with all control residing in the recording truck. Communications between the central unit, CANs, and RAUs are carried out using the TCP/IP family of protocols ensuring robust communications. Packets that are sent out from the central unit are transmitted over the backhaul network to a CAN, where they are then routed through an Access Point onto the Wireless Cell and onwards to a RAU. Packets transmitted from a RAU follow the reverse path being carried through the Wireless Cell into an Access Point within the CAN, routed onto the Backbone network and then through this network to the central unit.
Network Control
When a Unite system is deployed with the networking infrastructure as described above, the RAUs operate under direct control from the central unit. The operator, through the central unit, can command the RAUs to perform the following operations (not a comprehensive list): Initiate channel instrumentation tests - Common mode rejection - Input noise - Distortion Initiate sensor instrumentation tests - Sensor gross leakage
- Sensor common mode rejection - Sensor resistance - Sensor distortion - Sensor DC offset Set acquisition parameters - Sample rate - Pre-amp gain Working hours window. Update firmware. Commence acquisition. Return acquired data (trace length from supplied T0). Return background noise data. Enter sleep mode. Additionally, the central unit automatically commands the RAU to provide the following information and displays it on the screen. Return status information - External battery voltage. - Internal battery charge level. - GPS lock status. - Wireless received signal strength indication. The operator can also command the CANs to perform the following operations: Change wireless channel set. Change wireless output power level. Select external RF amplifier. Enter backhaul mode (disables wireless access points). Enter sleep mode.
The central unit automatically commands the CANs to return the following information and displays it on the screen: Battery voltage. Current wireless channel set. Current wireless output power. CAN internal temperature.
Autonomous Mode operation

In Autonomous Mode, no communications infrastructure is used to transfer data and commands between the central unit and the RAUs. Instead, the RAUs record data continuously and store this data, along with GPS time-stamps in on-board, non-volatile memory. The recorded data is recovered from the RAUs by a Data Harvester whose functionality is described below.
Data Harvester
The Data Harvester is portable, such that it can be carried by one person for extended periods of time. It consists of a Tablet PC with built-in mass-storage unit (HDD) and wireless access point. Data Harvesters receive TBs from the e-Unite UCI.
20
0m
x ma
Figure 1-12 Harvesting
30
The Data Harvester can connect to one or more RAUs by wireless using the built-in wireless access point or CAN, and uses this link to upload all recorded data.
Figure 1-13 Harvesting via CAN
There is also a facility whereby the Data Harvester can be connected by Ethernet to a single RAU (or to multiple RAUs through a switch) to upload recorded data from it. The Data Harvester GUI has the following functionality: Displays progress of RAU harvesting. Displays list of RAUs already harvested. Displays list of RAUs with outstanding Timebreaks (uploaded from central unit). Allows filtering of RAU harvesting by line number. Connectivity: Connects to RAU via wireless access point. Connects to RAU via wired Ethernet. Communications: Uploads data from RAU. Transfers data to central unit. Uploads timebreak list from central unit.
31
RAU Operation
This section describes only the operation of the RAU that is specific to Autonomous mode. After performing boot up tests and waiting for its GPS module to lock, the RAU starts to acquire data without any other external prompting. The data is acquired using the acquisition parameters stored in nonvolatile memory, these parameters having been configured by the system operator through the UCI GUI previously. The previously configured parameters include a Working Hours window, which directs the RAU to enter a low-power mode when the actual time is outside of this window. Acquired data is stored with regular GPS time and position stamps into the onboard non-volatile data storage memory. Whilst operating in this mode, the wireless LAN operates in receive mode only, and scans the channels looking for a valid signal from a Data Harvester or from the system wireless infrastructure. If a valid signal is detected, the RAU connects with the communicating device, but continues to acquire and store data.
32
Introduction IT topology information for Unite recorder deployment
IT topology information for Unite recorder deployment

Two main packages should be distinguished in e-Unite software: e-Unite Server software: typically to be installed in the recording cab housing the seismic acquisition system. e-Unite Client software: processing and graphic user interface software that can be installed in the recording cab and on remote computers. Remote users can access the server through an Intranet or Internet connection. Access via the Internet or Intranet requires the installation of an additional computer (referred to as Seismic Gateway). There are four different ways of implementing e-Unite: Local user topology (page 34). Intranet user topology (page 35). Internet user topology (page 36). Intranet/Internet user topology (page 37). Note that UCI applications (UCI Line, UCI Operation, etc.) are not Client/Server applications. They only run on the server and therefore cannot be used remotely.
33
Local user topology

Local Area Network Extra Local user
Observer (Local user)
Unite Server
Figure 1-14 Local user topology
The table below summarizes the necessary steps for the implementation shown in Figure 1-14.
Where Who What 1.Install Operating System on server computer. 2.Install Server and Client software 3.Register extra local user 1.Install Client software. 2.Request Login from Observer. Recording cab Observer (local user) Extra local user
Sercel software package
34
Intranet user topology

Contractors Intranet (securized private network) Intranet remote user URL: http:// IP
Recording truck Crew #2 Local Area Network Seismic Gateway Observer Extra Local user Unite Server
Intranet IP address
Intranet remote user URL: http:// IP
Figure 1-15 Intranet user topology
Where Who What
Recording cab Observer (local user) Extra local user
Remote computer Remote user
Network Administrator
1.Install OS on server 1.Install Client computer. software. 2.Install Server and 2.Request Login Client software. from Observer. 3. Register extra users 1.Install OS. 2.Install Seismic Gateway software.
1.Install Client software 2.Request Login from Observer. Supply Intranet IP address or DHCP address
Seismic Gateway
35
Internet user topology

Internet Service Provider Public Internet Seismic Gateway Interface Crew #3 Local Area Network Seismic Gateway Extra Local user Internet remote user URL: http://www.crew3.com
Observer
www.crew3.com
(purchased address) Unite Server
Figure 1-16 Internet user topology
Where Who What 1.Install Operating System on server computer. 2.Install Server and Client software 3.Register extra users. 1.Install gateway Operating System. 2.Install Seismic Gateway software. 3.Install Interface software. 1.Install Client 1.Install Client software. software. 2.Request Login 2.Request Login from Observer. from Observer. Recording cab Observer (local user) Extra local user Remote computer Remote user Network Administrator
Gateway
Purchase Public Internet fixed IP address
36
Intranet/Internet user topology

Internet Service Provider Public Internet Contractors DMZ Administered by contractor Firewall www.contractor.com Intranet remote user Contractors Intranet (securized private network)
1
Internet remote user
http://crews.contractor.com/crew4
Seismic Gateway
URL: http:// IP
crews.contractor.com
(purchased address)
Contractors administration centre
Recording truck Crew #4 Local Area Network Seismic Gateway Observer Extra Local user UniteServer
Intranet IP address
Intranet remote user URL: http:// IP
Figure 1-17 Intranet/Internet user topology
37
Where Who What 1.Install Operating System on server 1.Install Client 1.Install Client computer. software. software. 2.Install Server and 2.Request Login 2.Request Login Client software. from Observer. from Observer. 3.Register extra users. Recording cab Observer (local user) Extra local user Remote computer Remote user Network DMZ Administrator
Supply Intranet IP address or DHCP address
1.Install gateway Operating System. Gateway 2.Install Seismic Gateway software
1.Install gateway Operating System. 2.Install Seismic Gateway software. 3.Purchase Public Internet fixed IP address 4.Register new crew
38
Chapter
Recorder installation
This chapter provides information for installing hardware in the recording truck. The client computer and peripherals, however, are not covered in detail in this chapter (see the specific chapters). In this chapter:
Networking (page 40) Identifying Ethernet interface ports (page 43) AC Power requirements (page 44) Server computer (page 45) LCI-428 (page 50) Auxiliary channels (page 55) FDU-428 (page 56) CAN (page 58) LCD display anchoring (page 59)
39
Recorder installation Networking
Networking
PFT (10.3....) DSD (172.30....) RAU (10.xx.xx.xx)
(10.xx.xx.xx) VE464 DPG 172.30.201.1 1 LCI-428 Ethernet switch 1 (10.2....) CAN
NAS (database) 1
172.30.128.1
Data Harvester
150.10.128.1 10.1.0.1 and 172.27.128.1

e-Unite client e-Unite server
172.27.128.42
172.27.128.2 FTP server 1 1 Seismic Gateway 172.27.128.20 1 1
Ethernet switch
Contractors Intranet Seismic Gateway Internet 1 RJ45, non twisted, grey, 5 m (6050047).
Figure 2-1 Recording truck networking (typical)

e-Unite server Double IP: 172.27.128.1
RAU 10.xx.xx.xx
10.3.xx.xx
PFT
and 10.1.0.1
CAN
10.xx.xx.xx NAS (database) 1 172.27.128.42 e-Unite client NAS (SEGD) 1 172.27.128.41 172.27.128.2 FTP server 1 1 1 1 172.27.128.99 1 Plotter Seismic Gateway Ethernet switch 1 172.27.128.20 172.27.128.11 1 172.27.128.10 10.2.xx.xx 1
Data Harvester
eSQC Pro server
eSQC Pro client
172.27.128.26
Contractors Intranet Seismic Gateway Internet 1 RJ45, non twisted, grey, 5 m (6050047).
Figure 2-2 Base camp networking (typical)
Note It is recommended to power off then power on the Ethernet
switch after re-assigning its RJ45 ports.

Local host
IP address 172.30.128.1
Local host FTP server
IP address 172.27.128.99
Unite server
150.10.128.1 172.27.128.1 10.1.0.1 VE432 DSD1 150.10.128.201
Unite client #1 Unite client #n
172.27.128.2 172.27.128.(n+1)
VE432 DSDn
150.10.128.(200+n)
CAN LCI-428 #1 172.30.201.1 RAU
10.xx.xx.xx
10.xx.xx.xx
eSQC-Pro server eSQC-Pro client
172.27.128.10 172.27.128.11
Data Harvester
10.2.xx.xx
PFT Seismic Gateway 172.27.128.20
10.3.xx.xx
Plotter 1 Plotter 2
172.27.128.26 172.27.128.27
NAS #1 (SEGD) NAS #2 (database)
172.27.128.41 172.27.128.42
NAS #3 (SEGD) NAS #4 (SEGD) NAS #5 (SEGD) NAS #6 (SEGD) NAS #7 (SEGD) NAS #8 (SEGD)
172.27.128.43 172.27.128.44 172.27.128.45 172.27.128.46 172.27.128.47 172.27.128.48
If you want to connect a network printer, look for a free address in the above table (except addresses in the range10.xx.xx.xx).
42
Recorder installation Identifying Ethernet interface ports
Identifying Ethernet interface ports

Whenever you want to make sure all Ethernet ports are properly connected, you can use the ping command to test whether a computer can reach the expected hosts across the network. This assumes that the SERCEL software is already installed on the computer and on the distant host. 1. 2. 3. See Networking (page 40) to find the IP address (xxx.xxx.xxx.xxx) of the host which should be visible to your computer. If your computer runs on Linux, open a Terminal window. If it runs on Windows, open a Command Prompt window. Type the command ping xxx.xxx.xxx.xxx and press Return (assuming xxx.xxx.xxx.xxx is the IP address of the host you want to connect to). 4. If you get a reply saying that a number of packets were sent and received, do not change anything. Otherwise, move the Ethernet cable to another port, on the distant host or on your computer, and ping the network again. Try again until you get a correct reply.
43
Recorder installation AC Power requirements
AC Power requirements
In order to help you determine the total AC power required and circuit breaker amperages, depending on the configuration of your recording cab, the table below gives the typical consumption of each device that your Unite system may include.
Unite LCI-428 VE464 DPG VE432 DPG Ethernet switch (typical) 110 VAC 2A 1.6 A 1.6 A 1A 220 VAC 1A 0.8 A 0.8 A 0.5 A =
HP XW 86000
13.2 A
6.6 A
CRT display (typical) LCD display (typical)
2.5 A 1A
1.2 A 0.5 A
NAS system Tape drive (typical)
4A 3A
2A 1.5 A
Plotter (typical)
4A
2A
Total =
44
Recorder installation Server computer
Server computer
WARNING
Be sure to install your workstations in an area where airflow is not obstructed, maintain proper clearance and provide appropriate air conditioning in the recording cab in order to meet the environmental requirements specified in the manufacturers documentation.
Shock-mount parts
Rear stop
250 6 holes, dia. 7mm 195
250
350
390
680 750
Figure 2-3. HP XW 8600 shock-mount assembly (Part No. 756086162)

Server computer connectors
Figure 2-4 HP Z800 rear panel Item

1 2 3 4 5 6 7 8 9 10 11 12 13 14
Description
Power cord connector. PS/2 mouse connector (green). IEEE-1394 connector. eth0 and eth1 network interfaces. See Identifying Ethernet interface ports (page 43) Audio line-in connector (blue). Side access panel key. Graphics connector. Audio line-out connector (green). Microphone connector (pink). USB 2.0 ports (6). PS/2 keyboard connector (purple). Serial connector. Cable lock slot. Power supply Built-In Self Test (BIST) LED.
46
Access panel key loop Universal chassis clamp lock opening Power supply Built-In Self Test (BIST) LED Padlock loop Cable lock slot
Additional Ethernet interface Graphic card
eth0 and eth1 network interfaces. See Identifying Ethernet interface ports (page 43)
FC QLA2342
PCI 32/33 PCI Express x16 GEN2 PCI Express x8 (x4) PCI Express x16 (x16, x8) GEN2 PCI Express x8 (1), Gen2 x8 (8) PCI Express x8 (x4) PCI-X 133
Figure 2-5 HP XW 8600
Note If for any reason, you replace any of the internal disks in the
server computer, then you have to reinstall the Operating System and e-Unite software.
47
Note For a tape drive that connects via a Fiber Channel port (e. g.
IBM 3592), the following interface board is required, depending on whether you install it in a PCI or PCI-Express slot in the computer: - QLOGIC QLA2342 (P/N 1660083296) in a PCI-X slot. - QLOGIC QLE2462 (P/N 1660084970) in a PCI-Express slot. See Tape drive interface cards (page 48).
Tape drive interface cards

Supplied in Sercel addon package
No No No Yes
Index
Card or adapter
Dual port Fiber Channel QLA2342 or QLA2462 Dual port Fiber Channel QLE2462 Adaptec single port SCSI AHA- 2944UW Adaptec dual port SCSI 39320
Periph. bus
FC FC HVD LVD/SE
Host bus
PCI-X PCIExpress PCI PCI-X
Driver
Red Hat WS 4.6 Red Hat WS 4.6 Red Hat WS 4.6 Red Hat WS 4.6
Sercel Part No.

1660083296 1660084970 3170311 3170297
B C D E
Tape drives Host computer 3592

HP XW 8600 B
LTO3
E
MDR
E
3590
D
3490 HVD
D
3490 SE
Not supported
48
Server hardware installation kit

(Part No. 1L61084838)
Item
VGA video cord Ethernet switch USB extender cord Adaptec dual port SCSI 39320 card RJ45 FTP cord, 5m
Part No.
3170231 3170277 3170278 3170297 6050047
Quantity
1 2 2 1 2
49
Recorder installation LCI-428
LCI-428
The LCI-428 is delivered to you with the four shock-absorbers already in place. If you need to remove them (e. g. for a rack-mount setup), remove the cover to gain access to the screws inside the unit.
21
81.1
35.9
Four shock-absorbers to be bolted to mount plate Eight M3 screws Eight holes (dia. 3.9 mm)
35.9
342 mm
260 mm
310 mm 438 mm
Figure 2-6 LCI-428 mounting dimensions
50
81.1
21
4 screws, M650 4 mounting holes (dia. 6.2)
Mount plate 756084647
242
300
350
492 514
Figure 2-7 Mounting plate (dimensions in mm)
51
To Ethernet switch
VE464 DPG
Ground
(or other Vibrator controller, or shooting system)
To Ethernet switch AC power
Ground
GPS receiver (mandatory)
10 m max.
2
Trimble Accutime Gold
Analog auxiliary channels
Figure 2-8 LCI-428 ports

1 2
P/N 1C14078465 (included in VE464 parts). GPS cord, 10 m max. recommended (P/N 1L11084742)
A remote input panel (P/N 1L22084238), to be mounted on a wall of the recording cab, together with 6-metre jumper cables, can be used to connect the spread to the Line and Transverse ports of the LCI-428.
52
2
Remote input panel Line jumper cable, 6 m (P/N 512 100 380)
6 holes, dia 4.5 mm
Right Trans
High Line
200 mm
Left Trans
Transverse jumper cable, 6 m (P/N 512 100 483)
Low Line
140 mm 300 mm
140 mm
Figure 2-9 Remote input panel mounting dimensions
220 mm
53
Shooting system
To connect a shooting system, see the manufacturers documentation and BLASTER signals (page 282).
Figure 2-10 Shooter encoder connected to LCI-428 (Blaster port)
See also Source controller interfacing (page 67) in Unite Users Manual Vol. 3.
54
Recorder installation Auxiliary channels
Auxiliary channels
To be able to fire shots, Unite requires one or more FDU AUX channels. FDUs can only be auxiliary channels, not seismic. Note that you must connect at least one auxiliary FDU channel, even if it not used. The signals to be recorded as auxiliary traces can be connected to the LCI-428 via an AXCUL-428 box. For each channel, a sticker indicates the Serial Number of the associated FDU-428 unit. The FDU Serial Number is associated with the auxiliary signal on the GUI, in the Aux Layout Setup.
Signals from source controller Low Line (typically) To other AXCUL-428 (or FDU link)
FDU-428 Serial Number
Figure 2-11 AXCUL-428
You can also use an Auxiliary Interface Box (AIB, Part No. 1C14079115). The AIB box is equipped with four pairs of banana jacks used as inputs, and four output cords that connect to the auxiliary FDUs.
Signals from source controller Low Line or High Line Inputs 1, 2, 3, 4 (banana jacks) Aux 1, 2, 3, 4
AIB
Auxiliary channels (max. 120)
Figure 2-12 AIB
See FDU-428 (page 56). For input voltage specifications, see FDU-428 input connector (page 285).
Recorder installation FDU-428
FDU-428
LCK2 socket
LED Grounding clamp
Figure 2-13 FDU-428
Operating temperature: -40 to +70C Storage temperature: -40 to +70C Maximum water depth: 15 m with WPSR cable, 1 m with ST+ type cable. The FDU is equipped with an LCK2 socket used to connect the input sensor. After an FDU is inserted into a line, its LED indicator is: normally off; slowly blinking if self-test errors are encountered; rapidly blinking if field test errors are encountered (e. g. because no geophone is connected).
IMPORTANT
To provide protection against lightning, the grounding clamp must be in contact with the ground.
56
Recorder installation FDU-428
Links
Links are made up of one or more FDUs, with customized cable lengths. Below are three typical examples of links. For assembly instructions, see 428XL Technical Manual.
FM4 plug 27.5 m 55 m 1-FDU Link 27.5 m
FM4 plug
FM4 plug 55 m 165 m 3-FDU Link
FM4 plug
FM4 plug
FM4 plug
55 m 330 m 6-FDU Link
Figure 2-14 : FDU links
WARNING
FDU links are not designed for use on cable drums.
57
Recorder installation CAN
CAN
3-sector antenna P/N: VIB800-0006 Ethernet #4 RF #1 RF #2 Ethernet #2 Ethernet #1 RF #3 Power (status) To central unit network Ethernet #3 Power (power)
P/N: VIB350-0026BU
P/N VIB-350-0100A
Figure 2-15 CAN Connectors
On completion of assembly of the antenna and antenna mast, connect the Antenna Cable Set to the coaxial antenna connectors (RF #1, #2, #3) on the CAN, taking care to match the coloured banding on the coaxial cable with the coloured marker on the CAN (see Figure 2-15). Take care to ensure that the N-type connectors are properly screwed on and not cross-threaded as this will considerably reduce wireless performance and may lead to equipment damage. If a Mesh wireless backhaul is used, connect the Mesh power/data cable (p/n: VIB-900-0018) to one of the 8-way data connectors on the CAN. If a fibre-optic backhaul is used, connect the fibre to one of the 8-way data connectors on the CAN. Once all other connections have been made, power can be applied by connecting batteries to one or both of the two power connectors. See also CAN Field Deployment (page 251).
58
Recorder installation LCD display anchoring
LCD display anchoring

An anchoring kit (Part No. 1L21084793) is available from SERCEL that allows you to protect an LCD screen from shocks when unused. Follow the procedure below to install the anchoring kit: 1. 2. 3. 4. Drill a hole (dia. 11 mm) in the table top, 170 mm from the wall. See Figure 2-16. Secure the LCD Monitor Arm to the table top with the mounting parts from the tool kit. Install the display on the arm, leaving a long enough loose length of connecting cable to allow for a 180 swing angle. Swing the display through 180 backward. With the screens front face resting against the wall, record the height (H) of the bottom edge above the table top (seeFigure 2-16).
4 5
LCD Monitor Arm
170
Figure 2-16
5.
Swing the display forward.
59
Recorder installation LCD display anchoring
6.
Drill four holes (dia. 12 mm) in the wall, 390 mm apart horizontally, 230 mm apart vertically, with the lowest two along a horizontal line at H + 60 mm (see Figure 2-17). Insert a hollow wall anchor into each hole. Secure the Display Anchor Base to the wall with four screws.
Display Anchor Base Display protected from shocks by strapping it in Anchor Base
7.
39
mm
H + 60 mm
230 mm
Figure 2-17
60
Chapter
Server software installation

In this chapter:
Full-Wireless Unite configuration (page 62) e-Unite server software (page 65) Setting up the disk volumes and RAID (page 70) Single-machine Infill Unite configuration (page 71) Two-machine Infill Unite configuration (page 86) Special instructions for VE464 users (page 92) Server ID code (page 93) Licence code (page 94) Saving e-Unite parameters (page 95) Uninstalling e-Unite server software (page 96) Server software patches (page 97) Firmware upgrading (page 101) Troubleshooting (page 102)
61
Server software installation Full-Wireless Unite configuration
Full-Wireless Unite configuration

Installing Linux Redhat Enterprise V4
If for any reason you have to install or re-install the Linux Redhat Operating System on the e-Unite server, use the procedure below. If this is a re-installation, first save the Licence code (page 94) and operating parameters (see Saving e-Unite parameters on page 95), and then power off the computer. The e-Unite system is supplied with two install disks. The e-UNITE V2.1 DVD contains Sercel e-UNITE software, and a kickstart installer that prepares the server for the Linux install. The second disk contains Linux RedHat Enterprise v4. You will be prompted to insert the Red Hat disk during the install.
CAUTION
This installation procedure will erase everything on the hard disk.

WARNING
After Linux Redhat is installed, a GRUB boot loader window shows up each time you power up or boot up the computer. Do not press any key (the boot loader window should disappear automatically). This procedure is for the server computer recommended by Sercel (HP Z800 with five disks). The installation procedure is the same if you use fewer disks. 1. 2. Power up the computer and press the prompted function key to interrupt the automatic boot sequence (F9 on HP computer). Insert the "e-UNITE V2.1 DVD". You must use the internal DVD drive (not an external USB drive).
62
3.
Depending on the type of machine, select Onboard or USB CDROM Drive from the Boot Device menu, and press Return, or choose the IDE-CDROM device option. When the message To install with Unite server setup (deletes ALL DATA) appears type uniteserver and press Enter. Select the type of keyboard, e.g. us for U.S. International or fr for French. Press Enter to continue. Note that with the US International option, you may have to press the space bar after typing a quote or double-quote character to enter that character. In the Time Zone window: choose your time zone and tick the "System clock uses UTC" checkbox. Click Next.
IMPORTANT
4. 5.
6.
It is very important that you select the correct time zone for local time to GPS time conversions. 7. You will now be prompted to insert the "Linux Redhat Enterprise V4" install disk. Insert the SERCEL REDHAT Enterprise V4.0 Update 7 (64 bit, Part No.1S30084876) DVD-ROM and click OK to continue.
IMPORTANT
Be sure to use the REDHAT DVD-ROM supplied by SERCEL, rather than the V4.0 DVD-ROM accompanying the machine. 8. 9. The installation program installs packages from the Redhat DVDROM (this takes about a quarter of an hour). After installation is complete, remove the DVD-ROM from the drive.
10. Click Reboot. 11. In the Welcome window, click Next. - In the Licence agreement window, choose Yes, then click Next.
- In the Date and Time window, click Next. 12. In the Display window, click Configure. 13. In the Configure window: - Expand the Generic LCD Display dropdown menu and select the 1280x1024 resolution. - Click OK. This takes you back to the Display window. 14. In the Display window: - Click in the resolution field and select the same resolution (1280x1024). - Click Next. 15. In the Red Hat Login window, select Tell me why I need to register and provide a Red Hat Login. Click Next. - In the Why register? window, select I cannot complete registration at this time. Remind me later. Click Next. - In the System User window, click Next. If a warning box appears, click Continue. - In the Sound Card window click Next. - In the Additional CDs window, click Next. - In the Finish Setup window, click Next. This completes the installation of Linux Redhat. To install e-Unite server software see e-Unite server software (page 65).
64
Server software installation e-Unite server software
e-Unite server software

In this section: Prerequisites (page 65) Installing e-Unite server software (page 66)
Prerequisites
Unless that is already done, connect the keyboard and display screen to the server computer.
Reinstallation
If this is a reinstallation: First save the Licence code (page 94) and operating parameters (see Saving e-Unite parameters on page 95) Uninstall the former release. See Uninstalling e-Unite server software (page 96).
Operating System
The Operating System is assumed installed (see Installing Linux Redhat Enterprise V4 on page 62). To eject any DVD or CD-ROM from the drive, right-click on the DVD/ CD-ROM icon on the desktop and choose Eject from the pop menu.
65
Installing e-Unite server software

WARNING
This procedure changes the system parameters (users, host name, etc.). 1. 2. Power on the server computer (unless already done). In the Login window: - Type root - Enter administrator as password. 3. Insert the e-Unite DVD-ROM into the drive. If the e-Unite DVD/ CD-ROM icon fails to appear automatically on the desktop, double-click on the Computer icon, and then open the DVD/ CD-ROM Drive by double-clicking on it. Wait until the icon appears on the desktop. In a Terminal window (see Terminal window on page 102), type the following commands: cd /media/cdrecorder (or cd /media/cdrom) ./installServer 5. Wait until the installation wizard appears (a dozen of minutes, depending on the DVD/CD-ROM drive speed).
4.
Figure 3-1
6.
In the Welcome to the Install Wizard for e-Unite Server 2.1 window, click Next.
66
7.
In the install location window, click Next.
Figure 3-2
8.
In the licence agreement window, select Yes and click Next.
Figure 3-3
9.
In the Linux User Account Information window click Next.
Figure 3-4
10. In the Senior Observer Details window enter the desired User name and password. Click Next.
Figure 3-5
67
11. The installation will now start. Progress is shown on the installation window.
WARNING
When the progress reaches almost 100% there will be a large delay of possibly more than an hour as the seismic data storage hard disks are reformatted into a RAID array. There is no progress update until AFTER this operation has completed.
Figure 3-6
12. In the Installation completed window click Finish.
Figure 3-7
WARNING
The installation is NOT FINISHED - only the first stage is complete. Do not eject the install DVD or reboot the server or close the Terminal window. Watch the terminal window for further progress messages. 13. Wait for the Welcome to Install Wizard for e-Unite UCI window to appear. Click Next.
68
Figure 3-8
14. In the install location window click Next.
Figure 3-9
15. The installation will now start. Progress is shown on the installation window. 16. In the Installation completed window click Finish.
Figure 3-10
17. Close terminal window. 18. Right click on the DVD icon on the desktop and select Eject. Remove the DVD. 19. Reboot the server (choose Logout from the main menu bar and then Restart the computer, then click OK).
Note After installing e-Unite software, install all mandatory Unite
patches, if any, in incremental numbering order. See Server software patches (page 97).
69
Server software installation Setting up the disk volumes and RAID
Setting up the disk volumes and RAID

Mirroring software RAID is used in the server, meaning that you can replace a single disk in the RAID without reinstalling.
70
Server software installation Single-machine Infill Unite configuration
Single-machine Infill Unite configuration

In this section: Overview (page 71) Installing Host Redhat Enterprise Linux WS4 (page 72) Installing 428XL server software on Host Linux (page 80) Installing the VM and Unite OS (page 80) Starting up the VM and the Unite OS (page 80) Setting up the VM (page 81) Setting up the local parameters in the Unite OS (page 83) Installing e-Unite V2.1 software on Guest Red Hat (page 85)
Overview
This installation procedure is intended for an Infill e-Unite configuration using the virtualization technology in order to use a single machine rather than two. In this configuration, the e-Unite application is virtualized on a 428XL (e-428) host machine as illustrated below.
e-Unite 428XL (e-428 software) Red Hat Linux WS 4.7 (guest) Unite VM
Red Hat Linux WS 4.7 (host) Figure 3-11
71
Installing Host Redhat Enterprise Linux WS4

If for any reason you have to install or re-install the Redhat Linux Operating System on the e-Unite server, use the procedure below. If this is a re-installation, first save the Licence code (page 94) and operating parameters (see Saving e-Unite parameters on page 95), and then power off the computer.
CAUTION

WARNING
After Redhat Linux is installed, a GRUB boot loader window shows up each time you power up or boot up the computer. Do not press any key (the boot loader window should disappear automatically). This procedure is for an e-Unite server computer with five disks (e. g. HP Z800). 1. Power up the computer and press the prompted function key to interrupt the automatic boot sequence (F9 on HP computer, otherwise F12). Insert the SERCEL REDHAT Enterprise V4.0 Update 7 (64 bit, Part No.1S30084876) DVD-ROM into the drive. Note that for an HP Z800 computer, Redhat V4 Update 7 is mandatory.
IMPORTANT
2.
Be sure to use the REDHAT DVD-ROM supplied by SERCEL, rather than the V4.0 DVD-ROM accompanying the machine. 3. Depending on the type of machine, select Onboard or USB CDROM Drive from the Boot Device menu, and press Return, or choose the Optical Drive or IDE-CDROM device option.
72
4.
When the message to install RedHat Enterprise Linux in graphical mode appears, press Enter (or wait until the timeout delay has expired). When the system asks if you wish To begin testing the media before installation, choose Skip (using the arrow keys). Press Enter. In the Welcome window, click Next. In the Language selection window, choose English. Click Next. In the Keyboard Configuration window, choose as appropriate, for example United Kingdom or U.S. International (if Qwerty) or French (if Azerty). Click Next. Note that with the US International option, you may have to press the space bar after typing a quote or double-quote character to enter that character. If a Mouse configuration window appears, leave the default setting unchanged (unless you know which type of mouse to choose). Click Next.
5.
6. 7. 8.
9.
10. If an Upgrade Examine window appears, choose Install RedHat Enterprise Linux WS. Click Next. 11. In the Disk Partitioning Setup window, choose Automatically partition. - Click Next. If a warning box appears, choose Yes. 12. In the Automatic Partitioning window: - Make sure the sda, sdb, sdc, sdd and sde partitions are selected. - Choose Remove all partitions on this system. - Make sure Review (and modify if needed) the partitions created is enabled. Leave other options unchanged. - Click Next. - In the warning box that pops up, choose Yes. 13. In the Disk Setup window, select VolGroup00. - Click Delete.
- In the Confirm Delete window, click Delete. This takes you back to the Disk Setup window. 14. Select /dev/sda2. Click Edit. 15. In the Edit Partitions: /dev/sda2 window: - From the File System Type pull-down menu, select Swap. - Choose Fixed size. - Enter 16000 into the Size field (16000 MB). - Choose Force to be a primary partition. - Click OK. This takes you back to the Disk Setup window. 16. Click New. In the Add Partition window: - Unselect sdb, sdc, sdd and sde. - Type / in the Mount Point field. - From the File System Type pull-down menu, select ext3. - Only sda should be selected. Make sure Fixed size is selected. - Enter 8000 into the Size field (8000 MB). - Choose Force to be a primary partition. - Click OK. This takes you back to the Disk Setup window. 17. Click New. In the Add Partition window: - Unselect sdb, sdc, sdd and sde. - Type /var/tmp in the Mount Point field. - From the File System Type pull-down menu, select ext3. - Only sda should be selected. Make sure Fixed size is selected. - Enter 2000 into the Size field (2000 MB). - Click OK. This takes you back to the Disk Setup window. 18. Click New. In the Add Partition window: - Unselect sdb, sdc, sdd and sde.
- Type /export/home in the Mount Point field. - From the File System Type pull-down menu, select ext3. - Only sda should be selected. Make sure Fixed size is selected. - Enter 100000 into the Size field (100000 MB). - Click OK. This takes you back to the Disk Setup window. 19. Edit /dev/sda1 (/boot) or create a new /boot partition if doesn't exist. In the Edit Partitions: /dev/sda1 window: - Type /boot in the Mount Point field. - From the File System Type pull-down menu, select ext3. - Allowable drives: only sda1 should be selected. Make sure Fixed size is selected. - Enter 100 into the Size field (100 MB). - Click OK. This takes you back to the Disk Setup window. 20. Select /dev/sda. Click New. - From the File System Type pull-down menu, select ext3. - Type /var/dump in the Mount Point field. - Unselect sdb, sdc, sdd and sde. Make sure Fixed size is selected. - Enter 165000 into the Size field (165000 MB). - Click OK. This takes you back to the Disk Setup window. 21. Select /dev/sda. Click New: - From the File System Type pull-down menu, select ext3. - Type /var/dump0 in the Mount Point field. Make sure Fixed size is selected. - Unselect sdb, sdc, sdd and sde. - Enter 165000 into the Size field (165000 MB). - Click OK. This takes you back to the Disk Setup window.
22. Select /dev/sda. Click New: - From the File System Type pull-down menu, select ext3. - Type /unitea in the Mount Point field. - Unselect sdb, sdc, sdd and sde. - Choose the Fill To Maximum Allowable Size option. - Click OK. This takes you back to the Disk Setup window. 23. Remove all existing partitions (and/or logical or physical volumes) on sdb, sdc, sdd and sde. Below is the resulting final partitioning:
Hard Drives: /dev/sda /dev/sda1 /boot ext3 102 /dev/sda2 swap 16002 /dev/sda3 / ext3 8001 /dev/sda4 Extended /dev/sda5 /var/dump0 /dev/sda6 /var/dump /dev/sda7 /export/home /dev/sda8 /var/tmp /dev/sda9 /unitea /dev/sdb Free /dev/sdc Free /dev/sdd Free /dev/sde Free
ext3 ext3 ext3 ext3 ext3
165004 165004 99998 2000 497756
24. Click Next. 25. In the Boot Loader Configuration window, leave the default settings unchanged. Click Next. 26. In the Network Configuration window: - Select eth0. - Click Edit. Set the options as follows: - Unselect the Configure using DHCP option. - Select the Active on Boot option (done by default).
- IP address: enter 172.27.128.1 for the ip-eth0 address (visible to the seismic recording system). - Netmask: enter 255.255.255.0 as Submask for ip-eth0. - Click OK. - If a second Ethernet card is installed, select eth1. - Click Edit. Set the options as follows: - Unselect the Configure using DHCP option. - Select the Active on Boot option (done by default). - IP address: enter the ip-eth1 address visible to the local network (172.30.128.1). - Netmask: enter the Submask for ip-eth1 (that is 255.255.0.0). - Click OK. - Set the hostname: choose the Manually option. - Leave the hostname field unchanged (localhost.localdomain). - Click Next. A warning box (Error With Data) should show up, warning you that the Gateway and DNS fields are left blank. Click Continue to dismiss those warnings. 27. In the Firewall Configuration window, choose No Firewall.
IMPORTANT
From the Enable SELinux? drop-down menu, select Disabled. Click Next. To dismiss the warning box (No Firewall) that shows up, click Proceed. 28. In the Additional Language Support window: choose English (USA). Click Next. 29. In the Time Zone window: choose your time zone and tick the "System clock uses UTC" checkbox. Click Next.
IMPORTANT
It is very important that you select the correct time zone for local time to GPS time conversions. 30. In the Set Root password window, - Root password: enter the desired Root password (e. g. administrator) for the e428 server and keep it in a safe place. - Confirm: type again your password to confirm. Click Next. 31. In the Package Installation Defaults window: - Choose Customize software packages to be installed. - Click Next. 32. In the Package Group Selection window: - In the Desktops group, select KDE Desktop Environment (leave other settings unchanged). - In the Applications group, remove (unselect) Games. - In the Servers group: - Select Web Server. - Select Mail Server. - Select Legacy Network Server. Click on Details. Select rsh-server (leave other settings unchanged). Click OK. - In the Development group, select Legacy Software Development. - In the System group, select System Tools. Click on Details. Select wireshark-gnome (if Redhat v4 update 6; or etherealgnome if Redhat v4 update 4) and sysstat. - Leave other settings unchanged. - Click Next. 33. In the About to Install window, click Next.
34. The installation program installs packages from the Redhat DVDROM (this takes about a quarter of an hour). 35. After installation is complete, remove the DVD-ROM from the drive. 36. Click Reboot. 37. In the Welcome window, click Next. - In the Licence agreement window, choose Yes, then click Next. - In the Date and Time window, click Next. 38. In the Display window, click Configure. 39. In the Configure window: - Expand the Generic LCD Display dropdown menu and select the 1280x1024 resolution. - Click OK. This takes you back to the Display window. 40. In the Display window: - Click in the resolution field and select the same resolution (1280x1024). - Click Next. 41. In the Red Hat Login window, select Tell me why I need to register and provide a Red Hat Login. Click Next. - In the Why register? window, select I cannot complete registration at this time. Remind me later. Click Next. - In the System User window, click Next. If a warning box appears, click Continue. - In the Sound Card window click Next. - In the Additional CDs window, click Next. - In the Finish Setup window, click Next. This completes the installation of Redhat Linux. Then you must install 428XL server software (see below).
Installing 428XL server software on Host Linux

1. Use the standard procedure to install 428XL server software (see 428XL Installation manual Installing 428XL server software). Create the .plot folder in the Host Linux /var/dump directory. To do that, open a Terminal window in the host Linux and type: mkdir /var/dump/.plot chmod ugo+rwx /var/dump/.plot
2.
Then you must install the virtual machine (VM) and the Red Hat Linux for e-Unite (see below).
Installing the VM and Unite OS

Note that the OS installation process is fully automated and you won't be prompted for anything. The installation must be done as root: 1. 2. 3. Insert the e-UNITE VM DVD into the drive. Open a Terminal and go to the DVD root directory: cd /media/cdrom Run the installation script: ./install.sh
This command takes approximately 15 minutes to complete. Then you must start up the VM and the Unite OS (see below).
Starting up the VM and the Unite OS

1. 2. 3. Log off from the host and log back in as user428. Double-click the Unite Player icon on the desktop. Log in as root at the Linux login prompt (password: administrator).
Then you must set up the VM (see below).
80
Setting up the VM
Follow the steps below to do a few post-installation settings in your VM (Connecting the DVD drive, Enabling SEG-D file sharing, Setting up the network adapters connection type).
Connecting the DVD drive

1. 2. Open the Virtual Machine menu. From the menu list, select Removable Devices, CD/DVD, Connect to DVD-ROM XXX.
Enabling SEG-D file sharing

The SEG-D files generated by the master 428XL are imported into the e-Unite through a file sharing mechanism. 1. 2. 3. 4. Open the Virtual Machine menu. Select Virtual Machine Settings. Click the Options tab. Select the Shared Folders entry in the left panel (the path /var/dump/.plot with 428XL as name is defined in the Folders list). Select Always enabled in the Folder Sharing options (right-hand panel). Click Save.
5. 6.
81
Figure 3-12
Setting up the network adapters connection type

1. 2. 3. 1. 2. 3. Open the Virtual Machine menu. From the menu list, select Removable Devices, Network Adapter. Select Bridged. Open the Virtual Machine menu. From the menu list, select Removable Devices, Network Adapter 2. Select Bridged.
Do it again for the 2nd network adapter:
If the Network Adapters fail to get reconnected at the VM power-on then: 1. 2. Open the Virtual Machine menu. Select Removable Devices / Network Adapter (a red cross should appear to say it is disconnected).
82
3.
Click Connect.
Do it again for Network Adapter 2. Then you must set up local parameters in the Unite OS (see below).
Setting up the local parameters in the Unite OS

Keyboard type
The default keyboard type is set to UK (standard delivery with the HP machine). If you are using another type of keyboard: 1. 2. 3. 4. 5. Open the Red Hat Applications menu. Choose System Settings > Keyboard. Type the root password when prompted (administrator). Select the correct type of keyboard. Click OK.
Date, Time and Time Zone

To adjust your date, time and time zone: 1. 2. 3. 4. Open the Red Hat Applications menu. Choose System Settings > Date & Time. Type the root password when prompted (administrator). In the Date and Time tab: - Pick the correct date in the calendar. - Set the local time in the Time panel. 5. In the Time Zone tab: - Pick your time zone. - Tick System clock uses UTC at the bottom of the window. 6. Click OK.
83
Display
Adjust your display if required: 1. 2. 3. 4. Open the Red Hat Applications menu. Choose System Settings > Display. Type the root password when prompted (administrator). In the Hardware tab: - Click the Configure button. - In the Monitor window, open the Generic LCD Display list. - Select LCD Panel 1280x1024. - Click OK. 5. Back to the Display settings window, select the Settings tab: - Select 1280x1024 in the Resolution field. - Select Millions of Colors in the Color Depth field. 6. Click OK.
Disabling the Plot process on the 428XL

As SEGD files generated by the 428XL are made available to e-Unite via a shared folder (/var/dump/.plot), you must disable the Plot process on the 428XL to prevent it from altering the content of that folder. To do that: 1. 2. 3. 4. Go to $SOLHOME/workSpace/param: cd $SOLHOME/ workSpace/param Edit the path process file: gedit pathProcess.e-428.0.user428.svr428 Comment the following line (add a "#" at the beginning): prmPlot ../bin.linuxV2_6/prmPlotFftw Add the following line just after the comment line: prmPlot
84
5.
Save the file and exit. (As a result, plotting is no longer available from the 428XL desktop).
Installing e-Unite V2.1 software on Guest Red Hat

1. After the Guest Linux has booted, install e-Unite Server software on the Guest OS, using the same procedure as if you were installing it for the Full-Wireless configuration. See Installing e-Unite server software (page 66). approximately 25 minutes to complete (WARNING: the last few percent of the progress bar may take 20 mins to complete). 2. For the Infill configuration, you must install e-Unite Client software on the server computer (on the Guest OS). See Installing Client software (page 113).
Note The e-Unite V2.1 server software installation takes
This completes the installation of the Single-machine Infill e-Unite configuration. To get started, see Key steps to using Infill Unite (page 37) in Unite Users Manual Vol. 1.
85
Server software installation Two-machine Infill Unite configuration
Two-machine Infill Unite configuration

This Infill Unite configuration requires two machines which may or may not be attached to the same network: one is used to host e428 server software, and another machine is used to host eUnite software. 1. Use the standard procedure to install the Operating System and e428 server software on the 428XL server computer (see 428XL Installation manual). To install eUnite software on the second machine, use the same procedure as for a Full-Wireless Infill configuration. See Full-Wireless Unite configuration (page 62).
2.
To get started, see Key steps to using Infill Unite (page 37) in Unite Users Manual Vol. 1.
Note In the UCI applications Operation Recording Settings
window, you will have to choose the SEG-D Importoption. Depending on whether or not the two machines are attached to the same network, there are different ways of importing the SEG-D files generated by the 428XL into the Unite UCI: If the two machines are on the same network, you can use an NFS mount point and share the /var/dump/.plot directory of the 428XL server so that the UCI can read the SEG-D files. See Settings for importing SEG-D files via NFS (page 87). Otherwise (e. g. eUnite host machine at the base camp), you can export 428XL SEG-D files to a NAS and then connect the NAS to the eUnite machine to import the SEG-D files. See Settings for copying SEG-D files from a NAS (page 90).
86
Settings for importing SEG-D files via NFS

428XL Server
As SEGD files generated by the 428XL are made available to e-Unite via a shared folder, you must disable the Plot process on the 428XL. To do that, see Disabling the Plot process on the 428XL (page 84). To make the SEG-D files available to the eUnite server via a NFS share: 1. 2. Log in as root to the 428XL server. If the 428XL has not been run yet since installing, you will need to create the /var/dump/.plot directory and set the permissions: mkdir /var/dump/.plot chmod ugo+rwx /var/dump/.plot 3. 4. Insert the eUnite DVD into the 428XL server. From the Desktop browse to the tools/linux/rpms/RHEL4 then double-click on the system-config-nfs-1.2.8-1.noarch.rpm file and follow the prompts to install the NFS networking configuration tool. NFS Shares can now be configured from the Desktop. To do so, from the Desktop open Applications > System Settings >Server Settings > NFS.
Figure 3-13
5.
Share /var/dump/.plot as shown below: - Click the Add button, then fill in the entries as below:
87
Figure 3-14
eUnite Server
The eUnite software is installed on a separate server to the 428XL in the standard way. Modify the IP addresses to avoid conflicts. 1. 2. Log in as root on the eUnite server and open the Network window in the Applications > System Settings menu. In the Network Configuration window: - Select eth1. - Click Edit. - Replace 172.30.128.1 in the address field (Statically set IP addresses) with 172.30.128.100. - Click OK. - Select eth0. - Click Edit. - Replace 172.27.128.1 in the address field (Statically set IP addresses) with 172.27.128.100. - Click OK. - Select eth1:1. - Click Edit and make sure the IP address for this device is 150.10.128.1.
- Exit by clicking Cancel. - Remove this profile: click Delete. - Save your modifications: File > Save. - Reactivate all inactive profiles (click Activate once the profile to activate has been selected). - Quit the Network Configuration window. 3. 4. Open a Terminal window and execute: service network restart (all services should restart OK). Open the /etc/hosts file: gedit /etc/hosts - Modify the line containing: 172.27.128.1 svr428 hciPrinter svr_zeh_1 loghost svr428 by replacing 172.27.128.1 with 172.27.128.100 - Save the file and exit. 5. Reboot the server. We now need to set up the eUnite server to automatically access the shared directory we set up on the 428XL server. 1. 2. Log in as root. Create a directory that the 428XL network share will be mounted to. Open a command prompt and type: mkdir /import Open the auto mount master file: gedit /etc/auto.master Add the following line to this file: /import /etc/auto.import --timeout 60 Save and quit the text editor. Open the auto mount detail file: gedit /etc/auto.import
3. 4. 5. 6.
89
7.
Add the following line to this file:
segd -rw,soft,intr,retrans=1,timeo=5,rsize=8192,wsize=8192 172.27.128.1:/var/dump/.plot
8. 9.
Save and quit the text editor. Create a link to the NFS mount: ln -s /import/segd /export/home/user428/import
10. You can now log out of root and log back in as user428. 11. In the UCI applications Operation window, open the Recording Settings window and set up the eUnite acquisition mode to be SEG-D Import, and set the import directory to /export/home/user428/import (i.e import in your home folder). 12. Connect the 428XL and eUnite servers using an ethernet link between the two client network cards.
Settings for copying SEG-D files from a NAS

The eUnite software is installed at base camp on a separate server in the standard way. The SEG-D files can be transferred from the 428XL server using any suitable media (NAS drive, USB drive etc.).
428XL Server
No physical update to the 428XL server is required. At the end of the day copy the SEG-D files to your media for transport back to base camp.
eUnite Server
1. 2. Use JExport on the eUnite server to mount the NAS or other media containing the SEG-D files. Create a directory that the SEG-D files from the 428Xl will be copied to: mkdir /var/dump/import
3.
In the UCI applications Operation window, open the Recording Settings window and set up the eUnite acquisition mode to be SEG-D import, and the import directory to be your newly created network share: /var/dump/incoming When the SEG-D files arrive from the 428XL first make sure the UCI is NOT ARMED.
WARNING
4.
The UCI must not be armed when copying files into the import folder. This is because when copying files they can be copied in an arbitrary order, and the UCI requires that either all the files are present before arming, or that files are added in chronological timebreak order. 5. 6. Copy the SEG-D files from the media to the /var/dump/incoming folder on the eUnite server. Arm the UCI. The files will be imported.
91
Server software installation Special instructions for VE464 users
Special instructions for VE464 users

If a VE464 is used as the source controller, you must edit the /var/dump/UNITE/ITS_DATA/ProspectDb/settings.ini file as indicated below for the Time Breaks to be properly processed: 1. 2. 3. 4. Close the UCI application. Open the file /var/dump/UNITE/ITS_DATA/ProspectDb/settings.ini Add the followng line: timingTolerance_us=20 Save your changes and quit the editor.
92
Server software installation Server ID code
Server ID code
To complete server installation the licence code supplied to you by SERCEL must be entered via the JInstall client. The JInstall software is included in the client installer. The client software must be installed on the server before you can set the licence code. See Installing Client software (page 113) for instructions on how to install the client applications. When you contact Sercel to get a licence code for your system, you have to supply a server ID. The licence code is based on the Identification number associated with the computer. To get the server ID number either: Use the e-Unite JInstall window. The server ID number is displayed next to the e-Unite password at bottom of the main tab. Use the serverId command line tool supplied on the e-Unite DVD in /media/cdrecorder/e-UNITEV2.1/linux/server/serverId. This must be run as root. If you add or move or remove any Ethernet interface card, then you may have to request a new licence code from SERCEL.
93
Server software installation Licence code
Licence code
The e-Unite system will not be fully functional until the licence code (password) supplied to you by SERCEL is entered in the JInstall window.
Figure 3-15
Because you have to enter the licence code again whenever you reinstall e-Unite software, be sure to save it (e. g. on a USB stick) and keep it in a safe place.
94
Server software installation Saving e-Unite parameters
Saving e-Unite parameters

Prior to uninstalling e-Unite software (for example if you want to install a new release), save your operating parameters as follows: 1. Open the JLog window. Right-click on the Parameters folder and choose Open.
Figure 3-16
2.
Save the file to a USB stick (using the Save command from the File menu).
Figure 3-17
When you subsequently want to recover your settings, use the Load command from the File menu and then select Apply from the Setup menu (or use this toolbar button: ).
95
Server software installation Uninstalling e-Unite server software
Uninstalling e-Unite server software

If, for any reason, you need to uninstall e-Unite server software, do the following: 1. 2. Save the Licence code (page 94) and your operating parameters (see Saving e-Unite parameters on page 95). Either re-install Linux on the server following instructions in section Installing Linux Redhat Enterprise V4 (page 62) recommended or follow the instructions below. Log out. Log in as root. In a Terminal window (see Terminal window on page 102),run the following commands: /export/home/uci/patch/uninstall/uninstall rm -rf /export/home/388family rm -rf /export/home/e-428 rm -rf /export/home/ve464 rm -rf /export/home/zeh 5. Reboot the workstation (choose Logout from the main menu bar and then Restart the computer, then click OK).
3. 4.
96
Server software installation Server software patches
Server software patches

You can install (or uninstall) patches on the server computer by using the Patch Installer window on a Client computer. If Client software is hosted on a Windows computer, see Remote access to Server from a Windows Client (page 125).
Installing a Server software patch

IMPORTANT
Software patches, if any, provided to you by Sercel must be installed in incremental order. You must install all Mandatory-type patches. To install a Server software patch: 1. 2. 3. Power off the server computer (choose Shutdown in the Administration window) and power off the LCI-428 if any. Power on the server, log in as user428, and wait until log-in is complete. Open a Terminal window (see Terminal window on page 102). Stop the server by typing in s (wait until Shutting down Tomcat ..... is displayed). - Open the Server Patch Installer window, either by clicking on the e-Unite Server Patcher icon on the desktop, or by typing the following in a Terminal window: /export/home/e-428/patch/patcher.sh &
97
e-Unite server
Click
Figure 3-18 Patch Installer window
The left-hand pane shows which patches are already installed, if any. 4. If the patch to install is supplied to you on a CD-ROM, insert it into the server computers drive. If it is stored on a USB stick, plug in the USB stick. Click on the Install New Patch button in the Patch Installer window. If any warning window appears, click OK. In the dialog box that shows up, go to the folder containing the patch to install (on a Linux host, choose /media/cdrecorder for a CD-ROM, /media/usbdisk for a USB stick), and select the patch (s**v****.jar). Click on the Open button. This installs the patch and updates the Patch Installer window (wait until the message Install done appears).
e-Unite server
5.
6.
e-Unite (server)
Messages
Figure 3-19
The Interface Level field may or may not be incremented, depending on the changes implemented by the patch. To view the Interface Level, click on the top-level (server or client) folder in the Patch Installer window, then click on the Details tab. The
Interface Level is used to check for compatibility between Server and Client software each time any user connects to the server (if interface levels do not match, an error message appears and the connection request is rejected). 7. Click on the new patch in the Patch Installer window, then click on the Readme tab for more information on the patch you installed. Close the Patch Installer window. If required, type eject in the Terminal window to release the CDROM.
8. 9.
10. Reboot the computer. 11. After reboot is complete, power on the LCI-428 (if any).
Uninstalling a Server software patch

If, for any reason, you wish to uninstall any patches, you must do that in decremental order, starting from the highest number. To uninstall a Server patch: 1. 2. 3. Power off the server computer and LCI-428. Power on the server, and wait until log-in is complete. Open a Terminal window (see Terminal window on page 102). Stop the server by typing in s (wait until Shutting down Tomcat ..... is displayed). - Open the Server Patch Installer window, either by clicking on the e-Unite Server Patcher icon on the desktop, or by typing the following in a Terminal window: /export/home/e-428/patch/patcher.sh & The left-hand pane shows which patches are already installed. 4. Right-click on the patch you want to uninstall, and select Uninstall from the menu that pops up. If any warning window appears, click OK.
99
e-Unite server
e-Unite
Right-click
Messages
Figure 3-20
Wait until the message Install done appears. 5. 6. 7. Close the Patch Installer window. Reboot the computer. After reboot is complete, power on the LCI-428 (if any).
100
Server software installation Firmware upgrading
Firmware upgrading
After installing a new release of e-Unite software (and patches if any), you have to update LCI-428 firmware, using the Download setup menu in the GUIs Line window. See The Download setup (page 296) in Unite Users Manual Vol. 1.
101
Server software installation Troubleshooting
Troubleshooting
When you contact SERCELs customer support centre for assistance, you may be requested to supply log files so that support engineers can trace your problem and fix it more quickly. To do that, see System status archive tool (File Packager) (page 208) in Unite Users Manual Vol. 1. Also, you can use the Publish command in the Log window to get a compressed copy of your setup parameters or operator reports, etc., that can be downloaded from the crews Web site. See The crews Web site (page 209) in Unite Users Manual Vol. 1. Below are a few basics that may help if, for any reason, you are requested to type any Linux command on the server computer, or to type commands to control a serial port, etc. See also Identifying Ethernet interface ports (page 43).
Terminal window
To open a Terminal window on the server computer, right-click on the desktop and choose Open Terminal from the popup menu.
Terminal window on a serial port

To open a Terminal window on a serial port, type minicom in a Terminal window.
USB stick management

Inserting a USB stick causes a removable disk icon to appear on the desktop. Right-click on it and then select the appropriate command from the popup menu (Open, Unmount Volume).
WARNING
All USB sticks must be removed when reinstalling Linux, or their contents may be erased.
102
If for any reason, the USB stick fails to mount, or is not recognized by the system, try the following procedure: 1. 2. 3. 4. 5. 6. 7. 8. 9. Log in as root. Open a Terminal window (you can press the Return key to check for the prompt). Plug in the USB stick. Type more /etc/fstab Wait for the USB directory to mount. This can be /media/flash or /media/diskonkey or /media/usbdisk or any other. If no USB directory appears, type dmesg Near the end of the display, look for something like sde : sde1 (sde1 stands for the DEVICE). Type mkdir /media/usb (USB is now the file system). Type mount /dev/DEVICE /media/usb -t vfat (replace DEVICE by the one identified above).
This should mount the USB stick. It should be available from the Desktop environment.
103
104
Chapter
Client computer
This chapter describes how to install and uninstall e-Unite Client software on a computer. Typically, Client software is installed on a Windows host computer, but you may as well want to install it on a Linux host.
Overview (page 106) Installing RedHat Enterprise WS4 Update6 (page 107) User account (page 111) Installing Client software (page 113) Installing a screen management driver for Linux
(page 116)
Setting the computers IP address (page 121) Remote access to Server from a Linux Client (page 124) Remote access to Server from a Windows Client
(page 125)
Uninstalling e-Unite Client software (page 130) Client software patches (page 131) First-time log-in (page 134) Multi-screen management (page 116)
105
Client computer Overview
Overview
The following Operating Software can be used for e-Unite Client host computers: Red Hat Linux WS4 Update 6, recommended by Sercel. If, for any reason, you need to install or reinstall Linux, see Installing RedHat Enterprise WS4 Update6 (page 107). WindowsTM XP SP3. This manual does not include any specific procedure for installing WindowsTM. If required, contact your system administrator to install WindowsTM. Prior to installing e-Unite Client software, whether on a Linux or a Windows host computer, it is recommended to create a Unite user account (user428) with no administrator privilege. See User account (page 111). Then, log in with that user account to install e-Unite Client software. See Installing Client software (page 113).
106
Client computer Installing RedHat Enterprise WS4 Update6
Installing RedHat Enterprise WS4 Update6

In this section: Hardware specific information (page 107) Installing Linux RedHat on e-Unite Client computer (page 107)
Hardware specific information

Prior to installing RedHat, read hardware specific information supplied by Sercel if any.
Installing Linux RedHat on e-Unite Client computer

If for any reason you have to install or re-install the Linux RedHat Operating System on a Client computer, use the procedure below. The e-Unite system is supplied with two install disks. The e-UNITE V2.1 DVD contains Sercel e-UNITE software, and a kickstart installer that prepares the server for the Linux install. The second disk contains Linux RedHat Enterprise v4. You will be prompted to insert the Red Hat disk during the install. If this is a re-installation, power off the computer.
CAUTION

WARNING
After Linux RedHat is installed, a GRUB boot loader window shows up each time you power up or boot up the computer. Do not press any key (the boot loader window should disappear automatically). This procedure is for an e-Unite client computer. 1. Power up the computer and press the prompted function key to interrupt the automatic boot sequence (F9 on HP computer).
107
2. 3.
Insert the "e-UNITE V2.1 DVD". You must use the internal DVD drive (not an external USB drive). Depending on the type of machine, select Onboard or USB CDROM Drive from the Boot Device menu, and press Return, or choose the IDE-CDROM device option. When the message To install with Unite client setup (deletes ALL DATA) appears, type uniteclient and press Enter. Select the type of keyboard, e.g. us for U.S. International or fr for French. Press Enter to continue. Note that with the US International option, you may have to press the space bar after typing a quote or double-quote character to enter that character. In the Time Zone window: choose your time zone. Click Next.
IMPORTANT
4. 5.
6.
It is very important that you select the correct time zone for local time to GPS time conversions. 7. You will now be prompted to insert the "Linux Redhat Enterprise V4" install disk. Insert the SERCEL REDHAT Enterprise V4.0 Update 7 (64 bit, Part No.1S30084876) DVD-ROM into the interncal DVD drive and click OK to continue.
IMPORTANT
Be sure to use the RedHat DVD-ROM or CD-ROM supplied by SERCEL, rather than the one accompanying the machine. 8. 9. The installation program installs packages from the Redhat DVDROM (this takes about a quarter of an hour). After installation is complete, remove the DVD-ROM from the drive.
10. Click Reboot. 11. In the Welcome window, click Next.
108
- In the Licence agreement window, choose Yes, then click Next. - In the Date and Time window, click Next. 12. In the Display window, click Configure. 13. In the Configure window: - Expand the Generic LCD Display dropdown menu and select the 1280x1024 resolution. - Click OK. This takes you back to the Display window. 14. In the Display window: - Click in the resolution field and select the same resolution (1280x1024). - Click Next. 15. In the Red Hat Login window, select Tell me why I need to register and provide a Red Hat Login. Click Next. - In the Why register? window, select I cannot complete registration at this time. Remind me later. Click Next. - In the System User window, click Next. If a warning box appears, click Continue. - In the Sound Card window click Next. - In the Additional CDs window, click Next. - In the Finish Setup window, click Next. 16. Log in as root. Enter the root password (e. g. administrator) 17. Click on the Applications menu and select System settings then Server Settings, then Services. In the Service Configuration window: - Scroll until the kudzu option is visible. Disable the kudzu option (click to the left to clear the check box). - Scroll until the sendmail option is visible. Disable the sendmail option (click to the left to clear the check box).
109
- From the File menu, select Save Changes. - From the File menu, select Quit. This completes the installation of Linux Redhat.
110
Client computer User account
User account
Prior to installing e-Unite Client software, you must create user account user428, with no administrator privilege.
Note user428 is automatically created by the e-Unite server software
installation.
Linux user account

To create a UNITE user account on a Linux host computer, do the following: 1. 2. 3. In the Login window, type root Enter the password (e. g. administrator). Open a Terminal window (see Terminal window on page 102) and create a new directory: mkdir -p /export/home 4. 5. Click on the red hat icon and select System Settings then Users and Groups. In the window that pops up, click on the Add User button.
Figure 4-1
6.
Enter user428 as user name and password. Set the home directory to /export/home/user428. Click OK.
111
Client computer User account
7. 8. 9.
user428 should now appear in the list of users on the client computer. Click Quit. Log out.
Windows user account

To create a UNITE user account on a Windows host, do the following: 1. 2. 3. Right-click on the My Computer icon in the workspace, and choose Manage from the popup menu. In the Computer Management window, expand the Local Users and Groups folder. Right-click on the Users folder and choose New User from the popup menu.
Figure 4-2
4.
In the New User window, enter user428 as login name in the User Name field, and enter user428 as password.
112
Client computer Installing Client software
Installing Client software

If this is a reinstallation, uninstall the former release first. See Uninstalling e-Unite Client software (page 130). The procedure below is typically intended for a local user computer running on WindowsTM or Linux, or an extra local user computer, or a remote user. On a Linux host computer, log in with the user428 user account (password: user428). To install e-Unite Client software, do the following: 1. 2. Insert the e-Unite install disc into the drive. Use the file browser or explorer to open the Client directory on the DVD-ROM: e-UNITE-V2.1/linux/client for a Linux host computer (in /media/cdrecorder); or e-UNITE-V2.1\windows\client for a Windows host computer. 3. Run the installation file: - On a Linux host computer, type the following commands in a Terminal window: cd /media/cdrecorder/e-UNITE-V2.1/linux/client (or cd /media/cdrom/e-UNITE-V2.1/linux/client) ./e-UNITE_ClientInstaller-v2.1-linux.bin - On a Windows host computer, double-click on this file: e-UNITE_ClientInstaller-v2.1_windows.exe 4. Follow the instructions prompted in the Install Shield wizard window. Click Next.
113
Figure 4-3
5.
In the install location window and delete warning windows, click Next.
Figure 4-4
6.
In the successive licence agreement windows, carefully read the terms of each agreement. Choose yes. Click Next.
Figure 4-5
7.
The installation will now start. Progress is shown on the installation window.
114
Figure 4-6
8. 9.
In the Installation completed window, click Finish. Close all windows. - Eject the DVD-ROM (on a Linux host, select the e-UNITE ... icon on the desktop, right-click and select Eject from the popup menu). - Remove the DVD-ROM from the drive.
10. On a Linux host, click on the Applications menu and select Preferences, then Sceensaver. - From the Mode dropdown menu, select Disable Screen Saver. - Click Close. 11. Reboot the computer. To open the GUI, double-click on the icon available on your computers desktop. See Unite Users Manual Vol. 1.
Note for Windows XP users:
Unite
- Open the Internet Explorer window; - Select Internet Options from the Tools menu; - Click on the Advanced tab; - Scroll until the Security options are visible; - Choose Allow active content to run in files on My Computer.
115
Client computer Screen management on Linux client
Screen management on Linux client

In this section: Installing a screen management driver for Linux (page 116) Multi-screen management (page 116) Updating the NVIDIA driver (page 119)
Installing a screen management driver for Linux

After first-time installation of e-Unite software, follow the procedure below to run the NVIDIA driver installation script (graphicInstall.sh) from the e-Unite DVD supplied by SERCEL, located in this folder: /media/<cdrom_name>/e-UNITE-V2.1/linux/tools To install the driver from the e-Unite DVD: 1. 2. 3. 4. At the Linux Login Panel, log in as root and type administrator as password. Open a Terminal window. Type cd /media/cdrecorder/e-UNITE-V2.1/linux/tools/ Type ./graphicInstall.sh <Nber_of_screen> nokvm (for example: ./graphicInstall.sh 2 nokvm for 2 screens connected and no kvm box installed). Type reboot
Multi-screen management (page 116).
5.
Note To change the number of screens, change 4/3 to wide, etc. see
Multi-screen management
Each computer can be equipped with up to four display screens. You have to install the adequate number of graphic cards in the computer.
116
IMPORTANT
After adding a Graphic card and connecting an additional display unit, or moving a Graphic card to another slot, you need to reinstall the Operating System and e-Unite software. If you have two or more screens, use the procedure below to configure the system: 1. 2. Open a Terminal window. Type: cd /usr/local/binsh ./configureDisplay.sh <n> <type of resolution> <orientation> where <n> = number of screens connected, i. e. 1 to 4 <type of resolution> (optional) = standard or wide <orientation> (optional) = linear or matrix (defaults to linear).
3.
Type reboot
Be sure the display screens are connected to the appropriate graphic accelerator card port so that the mouse pointer can jump to the suitable border from one screen to the other when moved horizontally. (Either change the connections or move the screens as required). See Figure 4-7 on page 118.
WARNING
Use either SVGA-type or DMI-type cables. Do not mix the two types. Do not use any SVGA/DMI converter. (The display units you purchase from SERCEL are supplied along with the necessary cables).
Note To connect wide 22 in. screens, preferably use the VGA ports
on the client computer.
117
Matrix setup 1 3
Figure 4-7 : Multi-screen workstation

Updating the NVIDIA driver

If for any reason the NVIDIA driver that is already running on the computer, from a previous installation, needs to be updated, a new driver is delivered in an e-Unite software patch. Copy the patch to a USB stick, then install the new driver as follows: 1. 2. Boot the computer in Single mode. Install the driver from the USB stick.
Booting in Single mode

1. 2. 3. 4. 5. 6. 7. 8. 9. Wait for the Linux GRUB window. Press any key. Keep the first line selected: Red Hat Enterprise Linux WS (2.6 .... ELsmp) Press the e key (within 10 seconds). Select the second line. Press the e key. At the end of the line, type single (with a space character ahead). Press the Return key. The new line should look like this: <t ramdisk_size ........ single Press the b key (this causes the computer to boot up).
10. Wait a few seconds for the single-mode boot to be complete until the prompt sh-3.00# appears.
Installing the driver from a USB stick

1. 2. Insert the USB stick. If for any reason the USB stick is not recognized, see USB stick management (page 102). Type the following commands: cd /media/... (replace /media/... by the file system). cp graphicInstall.sh /tmp
cd /tmp chmod +x graphicInstall.sh ./graphicInstall.sh 1 nokvm umount /media/... (replace /media/... by the file system). 3. 4. Remove the USB stick. Type reboot.
See Multi-screen management (page 116).
120
Client computer Setting the computers IP address
Setting the computers IP address

Unless the Client host computer also hosts Server software you have to assign an IP address to it so that it can communicate with the server computer.
Linux Client host computer

When you installed Linux on the client computer the IP address was automatically set to 172.27.128.2. If you need to connect several client computers, you must choose a different address for each of them. To change the IP address, do the following: 1. From the Applications menu, select System Tools and then Network Device Control. Enter the password for the root user account if the system asks you to do so. In the Network Device Control window, choose the eth0 network interface and click Configure (enter the password for the root user account if the system asks you to do so).
2.
Figure 4-8
3. 4.
In the Network Configuration window, double-click on the eth0 network interface. Choose Statically set IP addresses.
121
5.
In the IP address field, enter the IP address you want to assign to the Client computer on the 172.27.128._ network (e. g. 172.27.128.2). See Networking on page 40. In the Subnet mask field, enter 255.255.255.0. Click OK.
172.27.128.2
6.
Figure 4-9
Note In the case of a computer also hosting server software, you may
have to open this window (Ethernet Device) and make sure the Statically set IP addresses option is activated (instead of DHCP).
Windows Client host computer

To set the IP address of a Client computer running on WindowsTM, do the following: 1. From the Start menu, choose Settings, then Network Connections.
Figure 4-10
2. 3.
122
Right-click on the Local Area Connection and select Properties. Click on Internet Protocol (TCPIP) in the list box and then click on the Properties button.
4. 5.
Choose Use the following IP address. In the IP address field, enter the IP address you want to assign to the Client computer on the 172.27.128._ network (e. g. 172.27.128.2). See Networking on page 40. In the Subnet mask field, enter 255.255.255.0.
6.
4
172.27.128.2 255.255.255.0
Figure 4-11
7.
Click OK.
123
Client computer Remote access to Server from a Linux Client
Remote access to Server from a Linux Client

You can use the procedure below to type commands or browse through files on the Server computer from a Linux Client computer, for example if the Server computer has no keyboard or display. 1. 2. Open a Terminal window on the Client computer (right-click on the desktop and choose Open Terminal from the popup menu). Type the command
xhost + 172.27.128.1
(this allows the Server to display text in the Client computers Terminal window). 3. Still in the Client computers Terminal window, type the command
rlogin 172.27.128.1 l user428
(in place of user428, you can use any other account dedicated to the e-Unite application). 4. 5. Type the password for the Servers user428 account (normally without pressing Return). After logging in to the Server, type the command
setenv DISPLAY 172.27.128.X :0.0
(where 172.27.128.X is the IP address of the Client computer on which you typed the previous commands). 6. 7. To launch the Linux file explorer, type
nautilus &
To log out, type

logout
By default, none of the above commands is persistent.
124
Client computer Remote access to Server from a Windows Client
Remote access to Server from a Windows Client

If Client software is hosted on a Windows computer, Cygwin provides a Linux-like interface on the Win32 platform, allowing you to start, stop or restart the server even though the server host has no keyboard or display.
WARNING
The Cygwin user interface will not work unless the Windows user account is the same as the Server user account (user428).
Installing Cygwin software

1. 2. 3. On the e-Unite client PC, log in as Administrator. Open the cygwinInstaller directory on the Cygwin CD-ROM. Double-click on the cygwin_setup.exe file. In the Cygwin Setup window, click Next.
Figure 4-12
4.
Choose Install from Local Directory. Click Next.
125
Figure 4-13
5.
You must select the root directory (c:\cygwin) as the directory where to install Cygwin. Choose the recommended options (All users, Unix/binary). Click Next.
Figure 4-14
6.
Use the Browse button to select the CD-ROM drive and the cygwinInstaller directory. Click Next.
Figure 4-15
7.
Choose to install all packages (click on the arrow to choose Install instead of Default). Click Next.
126
Click to choose Install
Figure 4-16
8.
Wait until installation is complete.
Configuring Cygwin
To set up Cygwin parameters for the e-Unite server, do the following: 1. 2. 3. 4. 5. 6. Log in with the UNITE user name. See Windows user account (page 112). Open the cygwin directory on the Unite CD-ROM. Double-click on the sercel_config.exe file. Choose to uncompress the file to the C:\cygwin directory. In the C:\cygwin directory, double-click on the sercel_config directory. Set up the Sercel configuration by double-clicking on the confX.cmd file. As a result the following icons should be available on the desktop: cygwinmain, startddterm, startdttfile, startSga.
127
Figure 4-17
Working with Cygwin

Starting the X-server
The X-server needs to be started only once, by double-clicking on the cygwinmain icon:
Figure 4-18
As a result the X-server appears in the taskbar.
Opening an xterm Terminal window

Double-click on the startxterm icon:
startxterm
Figure 4-19
128
Opening a Nautilus file manager window

Double-click on the startNautilus icon:
startNautilus
Figure 4-20
129
Client computer Uninstalling e-Unite Client software
Uninstalling e-Unite Client software

If, for any reason, you need to uninstall e-Unite Client software, use the following procedure. 1. 2. 3. Login as user428. Close all e-Unite windows. On a Linux client, go to Applications > Sercel > e-UNITE > Uninstall > Uninstall. On a Windows host, select Programs > e-UNITE-client > Uninstall from the Start menu
Windows Start menu bar
e-UNITE
e-UNITE e-UNITE
e-UNITE
Figure 4-21
4.
This opens the uninstall wizard for e-Unite Client window.
Figure 4-22
5. 6.
Click Next in the successive windows, and finally click Finish. Reboot the computer.
130
Client computer Client software patches
Client software patches

Note To install/uninstall server patches, see Server software patches
(page 97).
Installing a Client software patch

IMPORTANT
Software patches, if any, provided to you by Sercel must be installed in incremental order. You must install all Mandatory-type patches. To install a Client software patch: 1. 2. Log in as user428. On a Linux host, double-click on the Patcher icon on the desktop. On a Windows host, select the Patcher menu item from the Start > Programs menu.
e-UNITE
e-UNITE
Windows Start menu bar e-UNITE
e-UNITE
Figure 4-23
This opens the Patch Installer window. The left-hand pane shows which patches are already installed, if any.
e-Unite client
Click
Figure 4-24
3. 4. 5.
Click on the Install New Patch button in the Patch Installer window. Click OK to dismiss the warning box saying that you must close the application (you must have done that at step 1). In the dialog box that shows up, go to the folder containing the patch to install (on a Linux host, choose /media/cdrecorder for a CD-ROM, /media/usbdisk for a USB stick), and select the patch. Click on the Open button. This installs the patch and updates the Patch Installer window.
e-Unite client
6.
Click
e-Unite (client)
Figure 4-25
The Interface Level field may or may not be incremented, depending on the changes implemented by the patch. To view the Interface Level, click on the top-level folder in the Patch Installer window, then click on the Details tab. The Interface Level is used to check for compatibility between Server and Client software each time any user connects to the server (if interface levels do not match, an error message appears and the connection request is rejected). 7. Click on the new patch in the Patch Installer window, then click on the Readme tab for more information on the patch you installed.
132
Uninstalling a Client software patch

If, for any reason, you wish to uninstall any patches, you must do that in decremental order, starting from the highest number. To uninstall a patch, right-click on it in the Patch Installer window and select Uninstall from the menu that pops up.
e-Unite client
4
Right-click
e-Unite
Figure 4-26
133
Client computer First-time log-in
First-time log-in
If you are using your e-Unite system for the first time, see Opening a user session (page 188) in Users Manual Vol. 1 to launch the e-Unite GUI and then select the appropriate options and settings in the JInstall window (licence code, etc.) and in the JConfiguration window to match your survey requirements.
134
Chapter
PFT software
This chapter describes how to reinstall the PFT software on a Trimble Nomad handheld device.
Overview (page 136) Exiting the PFT application (page 137) Installing PFT software from a USB drive (page 139) Installing ActiveSync on a Windows PC. (page 141) Reinstalling the Nomad firmware (page 144) Nomad device setttings (page 149) Install software (page 160) Viewing Wireless Network Settings (page 167) Transferring RAU List by USB drive (page 169) Configuring the PFT application (page 170)
135
PFT software Overview
Overview
The directory containing the Sercel PFT software also contains drivers and other software used on the handheld device, such as Microsoft ActiveSync. Nomad Firmware (includes the Windows Mobile operating system). Drivers for the Trimble Nomad. Drivers for the RFID scanner. To install the PFT software see Installing PFT software from a USB drive (page 139). To reinstall everything on the PFT handheld device, see Installing ActiveSync on a Windows PC. (page 141) Reinstalling the Nomad firmware (page 144) Nomad device setttings (page 149) Install software (page 160).
136
PFT software Exiting the PFT application
Exiting the PFT application

The PFT application is designed to hide Windows Mobile to make it difficult for an untrained operator to access the operating system, and change settings that may adversely affect the operation of the device. Unlike most applications there is no obvious way to exit the application. 1. From the application's main screen tap the Create a new named list button.
Figure 5-1
2.
Tap the keyboard icon at the bottom to pop-up the on-screen keyboard.
Figure 5-2
3.
In the List name box type pft quit and tap the Enter key. The PFT application will exit revealing the Windows Mobile desktop
137
PFT software Exiting the PFT application
Figure 5-3
The Windows Start menu can be accessed via the Windows logo on the top left. The PFT application can be restarted via the Unite PFT shortcut in the Start menu or by rebooting the device.
138
PFT software Installing PFT software from a USB drive
Installing PFT software from a USB drive

The PFT will automatically update itself whenever it connects to the server, if the server contains a newer version of the PFT CAB file. However, the PFT software can also be installed/re-installed from a USB drive. To install PFT software from a USB drive: 1. 2. Copy the PFT CAB file to a USB drive. Insert the USB drive into the the USB Host port of the Nomad device.
External power Mini-USB Client USB host Audio jack
Figure 5-4
3.
Tap the Start Button followed by Programs, followed by File Explorer:
Figure 5-5
In File Explorer, tap the Look in drop-down followed by the Hard Disk entry:
PFT software Installing PFT software from a USB drive
Figure 5-6
Find the PFT CAB file, named XXXX_PFT.CAB (where XXXX is the build number) and tap to install. Follow on screen prompts and select install on device.
140
PFT software Installing ActiveSync on a Windows PC.
Installing ActiveSync on a Windows PC.

Microsoft ActiveSync allows you to transfer files to and from your Nomad Trimble to a Windows PC. ActiveSync is used by the Nomad firmware installer so must be installed before the firmware can be updated.
Prerequistes
A laptop/desktop PC running Windows XP or Windows Vista. A USB to mini-USB cable to connect the Nomad to the Windows PC. A USB drive.
Install Microsoft ActiveSync

1. Install ActiveSync on the Windows PC by double-clicking <DVD drive>:\UNITEV4.1\windows\PFT_1.4.1\WindowsPC\Active Sync 4_5.msi 2. Follow the onscreen instructions to complete the installation.
Connect the Nomad device via USB

Connect the Nomad PDA device to the computer via a USB cable. The Mini USB port should be used to connect the Nomad (see below).
Mini-USB Client
Figure 5-7
141
Set-up ActiveSync
1. Once connected (after a brief delay) Active Sync will display the device partnership setup as show below.
Figure 5-8
2.
Click Next on this screen, then uncheck the Synchronize directly with a server option as indicated below, then click Next:
Figure 5-9
3.
Uncheck all of the Synchronization Options as shown below, then click Next:
Figure 5-10
4.
Leave the Allow Wireless Connections box unchecked in the next screen as demonstrated below, then click Next.
Figure 5-11
142
5.
Click the Finish button to complete the device partnership as shown below:
Figure 5-12
6.
When completed the following screen will be present:
Figure 5-13
Note The Explore icon lets you browse the Nomad device's file
system, similar to that of a USB drive. This is useful for transferring files to and from the device.
143
PFT software Reinstalling the Nomad firmware
Reinstalling the Nomad firmware

This describes how to reinstall everything on the Nomad device (everything from the Operating System to the Sercel software will be reinstalled).
Note Reinstalling the Operating System deletes the contents of the
Nomad flash file system. Make sure any RAU lists are transferred to the UCI before reinstalling the device. Make a backup copy of any other files you wish to keep. 1. 2. Make sure any RAU lists on the device are uploaded to the UCI before installing the Nomad firmware. Make a backup copy of any other files that you wish to save. Backed-up files must be copied off the Nomad to a USB drive on a Windows PC. On the Windows PC, double-click the Nomad firmware installer NomadUpdateV-_-_-WWE.exe. This can be found on the DVD in <DVD-drive>:\UNITEV-.-\windows\PFT_-.-.-\WindowsPC If a file security warning appears, select Run:
3.
4.
Figure 5-14
5.
Click the Setup button to start the installation:
144
Figure 5-15
6.
The extractor will run:
5
Figure 5-16
7.
Click Next in the Firmware update installer:
Figure 5-17
8.
Read the onscreen instructions that follow then click Next:
Figure 5-18
9.
Accept the license agreement then click Next:
145
Figure 5-19
10. Click Next in the update information screen:
Figure 5-20
11. In the subsequent screens follow the on-screen instructions. Note the illustration below indicates where each of the buttons are on the device that the Enter USB mode procedure requires.
Expansion cap
Notification LED
Battery LED
Application Soft Key Start Tab Function Key Power
Application Soft Key OK Backspace today Enter
Number pad and Navigation key
Figure 5-21 Numeric data keypad

12. After the instructions have been followed correctly the next button on the screen will be enabled. Also note that the screen on the PDA will change to the Firmware Update indicating that it is now in USB mode as indicated below
5
Figure 5-22
13. After clicking Next on the above screen, the firmware update will commence, showing the following progress on both the Nomad screen and the overall setup screen:
Figure 5-23
14. When the update is complete click Next in the screen above to show the update firmware completion screen, click Finish on the screen:
147
Figure 5-24
15. The Nomad device will have completed reboot and you will be prompted to set up the device, both on the Nomad and Active sync. It is recommended at this point to disconnect the device. Cancel the ActiveSync screen on the laptop/desktop. 16. Follow the Nomad setup screen (calibrating the device, setting the date and optional password).
148
PFT software Nomad device setttings
Nomad device setttings

Setting device parameters
Select Start (top left) then settings as shown below:
5
Figure 5-25
Button settings
1. In the settings applet select the personal tab if not already, then select Buttons:
Figure 5-26
2. 3.
Each of the button entries must be set to None except the Left Softkey. Leave it assigned to <Left Softkey>. Select a button then select <None> from the Assign a program dropdown list:
149
Figure 5-27
4.
Repeat this until all buttons (except the Left Softkey) are set to <None>.
Figure 5-28
5. 6.
Tap the Keyboard Options tab at the bottom right of the screen. Ensure the Sticky Fn Key is disabled as shown below:
Figure 5-29
150
Menu settings
1. Tap the OK button at the top right to return to the Personal settings tab, then select the Menus icon:
Figure 5-30
2.
Uncheck all of the entries in the Menus list:
Figure 5-31
3.
Tap the OK button in the top right to return to the Personal settings tab, then tap the Today entry:
Figure 5-32
151
4.
Tap the Items tab to display the items that appear on the Today screen:
Figure 5-33
5.
Uncheck all of the items in the Items list so that nothing will appear on the Today screen as well as unchecking the Today timeout option:
Figure 5-34
152
Input settings
1. Tap the OK button to return to the settings applet then tap the Input icon:
Figure 5-35
2.
Select the Word Completion tab and uncheck all of the options:
Figure 5-36
3.
Tap the Options tab then uncheck all entries on this page:
Figure 5-37
4.
Tap the OK button at the top right to get back to the Personal settings tab then tap the System Tab:
Figure 5-38
Other Settings
1. Tap the Clock & Alarms icon to display the Clocks & Alarm applet, then tap the More tab and uncheck the Display the clock option then tap OK at the top right:
Figure 5-39
154
2.
Tap the Error Reporting icon on the System settings applet, then Disable error reporting, followed by the OK button at the top right:
5
Figure 5-40
3.
Tap the X at the top right of the Settings applet to return to the desktop.
Configuring Wireless Networking

Configuring Wireless Network Lock
Network Lock prevents the Nomad device connecting to wireless access points other than the CANs provided with the eUnite system. 1. Tap Start followed by Programs to display the installed programs applet as shown below:
Figure 5-41
2.
Scroll down to the bottom right and tap the Wireless Access icon:
155
Figure 5-42
3. 4. 5.
Tap the Add new entry. Type VibtechBSS. Click Add. Select the Limit network visibility in the Wireless network status drop-down followed by Exit:
Figure 5-43
6.
Tap the X at the top right of the Programs applet to return to the desktop.
156
Setting the IP address

1. 2. 3. Click the Network Adapters tab at the bottom of the screen. Select Work from the My network card connects to drop-down list. Click on Marvell SDIO8686 Wireless Card in the list of network adapters.
Figure 5-44
4. 5. 6.
Select the Use specific IP address radio button. The PFT's IP address is based on the PFT ID number shown on the label on the back of the device. All PFT's must have an IP address in the range 10.3.xx.xx where xx is a number from 0 to 255 and xx.xx is the PFT ID as a 16-bit value. If the PFT ID is less than 255 then the IP address is 10.3.0.<ID>. - For example PFT-9 will have the IP address 10.3.0.9. If the PFT ID is greater than 255 then the IP address is calculated as follows - The first two components are always 10.3. - The third component is the ID / 256 rounded down to an integer value.
7. 8.
157
- The fourth component is the ID - (third_component * 256) - For example, PFT-1234 will have the IP address 10.3.4.210. 9. Enter the PFT IP address and set the Subnet mask: to 255.0.0.0. 10. Leave the Default Gateway field blank. 11. Click OK.
Figure 5-45
Generate System Information Snapshot

OPTIONAL: a System Information Snapshot contains details of the Nomad device and software installed on the device. 1. Tap Start followed by Settings then tap the System tab, scroll to bottom and tap the System Information icon:
Figure 5-46
158
2.
Using the directional arrows at the bottom right scroll until the Snapshot tab is visible, tap it then ensure the snapshot file location is \My documents\PFT-<ID>SysInfo.txt then tap Generate Snapshot:
5
Figure 5-47
3.
Tap the OK button at the top right of the screen, followed by the X at the top right of the System settings applet to return to the desktop.
159
PFT software Install software
Install software
Copy CAB files to the Nomad device
1. On a Windows PC, copy the contents of the WindowsMobile folder from the e-Unite install DVD to a USB drive. The WindowsMobile folder can be found at <CD drive>:\UNITEV-.x\windows\PFT_x.x.x\WindowsMobile. Insert the USB drive into the USB Host port of the Nomad.
2.
USB host
Figure 5-48
3.
Tap the Start button followed by Programs, followed by File Explorer:
Figure 5-49
4.
In File Explorer, tap the drop-down list in the top left corner. Select the Hard Disk entry
Note Hard Disk is Windows Mobile terminology for an external
USB flash drive or other external USB storage device.
160
Figure 5-50
5. 6. 7.
The File Explorer should now be showing the contents of the USB drive. Find the WindowsMobile folder that was copied from the PC. Tap Menu, then Edit and Copy:
Figure 5-51
8. 9.
Tap the Look in drop-down followed by My Device: In My Device tap the temp entry:
Figure 5-52
10. In the Temp folder, tap and hold a blank part of the screen to display the context menu, then select Paste:
161
Figure 5-53
11. The WindowsMobile folder should now be copied across to the device. Before removing the USB key, the system snapshot generated earlier (Generate System Information Snapshot on page 158) should be copied and stored on the USB key to allow recording of the system details on a log. Using steps similar to that above: - Navigate to the folder on the device where the snapshot was stored. - Tap and hold the file to display the context menu. - Select Copy from the context menu. - Navigate back to the USB key. - Tap and hold the screen to display the context menu. - Select Paste from the menu.
162
Install driver software on the Nomad

1. 2. In File Explorer, navigate to the \Temp folder on My Device. Tap the WindowsMobile folder to display its contents.
5
Figure 5-54
3. 4.
Go to the Drivers directory. Tap each cab file to install the driver.
Note When a cab file is installed, there should be no interaction
required unless a USB key has been left in. Should this be the case, select Device and click Install.
Figure 5-55
5.
During the installation of the SocketScan cab file, you will be prompted to remove the device from the cradle and soft reset. Ignore this for the time being and tap the OK button on the dialog followed by the OK button at the top right.
163
Figure 5-56
Install e-Unite software on the Nomad

1. 2. 3. 4. Reboot the device by holding down the power button for at least 5 seconds. In File Explorer, navigate to \Temp\WindowsMobile\Sercel on My Device. As before, tap each of the CAB files to install them. When all of the cab files have been installed, copy the latest PFT CAB file by tapping and holding until the context menu appears, then navigate to the root of the device:
Figure 5-57
5.
In the root of the device tap Menu then New Folder. Set the name of the new folder to Donotdelete. (Note: ensure the case matches exactly).
164
Figure 5-58
6.
When the cab file has been copied to the folder, rename it to Initial_PFT (again, make sure the case matches exactly). This is used by the auto installer should anything go wrong with an upgrade installation.
Figure 5-59
165
Reset the Nomad

Perform a warm restart on the device by holding down the power button for 5 - 8 seconds. A countdown should display, followed by the devices boot screen.
Figure 5-60
When the device restarts it should automatically start the PFT application.
166
PFT software Viewing Wireless Network Settings
Viewing Wireless Network Settings

These settings are automatically configured when the Sercel PFT software is installed. This section is for information only. To view the VibtechBSS network settings: 1. Tap Start followed by Settings then tap the Connections tab, on the connections tab tap the Network Cards icon.
Figure 5-61
2.
Configure Wireless Networks should contain an entry for VibtechBSS. Tap the name to view its settings.
Figure 5-62
PFT software Viewing Wireless Network Settings
3.
If any of the settings are incorrect it will prevent the NOMAD connect to a CAN though Windows Mobile may show the device as connected.
The easiest way to restore these settings is to re-install the PFT CAB file.
Note Only re-install the same version of the PFT, otherwise
outstanding RAU lists may be lost.
168
PFT software Transferring RAU List by USB drive
Transferring RAU List by USB drive

A USB drive can also be used to transfer RAU lists to the UCI if wireless networking is unavailable. 1. 2. Exit the PFT by create a named list with the name pft quit. See Exiting the PFT application (page 137). Tap the Start button followed by Programs, followed by File Explorer:
Figure 5-63
3. 4. 5. 6. 7. 8. 9.
Browse to My Device > Program Files > PFT > PFT Lists. Select all files in this directory. Go to Menu > Edit > Copy. Browse to Hard Disk (the USB drive). Go to Menu > Edit > Paste. Remove the USB drive and insert it into the eUnite server. Copy the RAU list files from the USB drive to /export/home/user428/PFTLists on the eUnite server.
169
PFT software Configuring the PFT application
Configuring the PFT application

By default the PFT is ready to use when it is installed using the PFT CAB file. However, there are some configuration settings that can be tweaked if necessary. To view/edit these settings: 1. 2. 3. 4. 5. The settings file can be found on the device at \Program Files\PFT\Vibtech\PFT.ini Copy the file to a PC using Active Sync (via a USB cable) or a USB flash drive. View and edit the file on the PC. Copy the file back to the device to the original location. The PFT will read the new settings on its next restart.
The file contains the following settings that can be modified.

Table 5-1
Parameter
FileTransfer.remoteHost FileTransfer.ftpPollInterval_ms
Description
IP address of the FTP server. Interval (in milliseconds) between FTP connection attempts. Translatable text Line scanning direction.
Default
10.1.0.1 5000 ms
Translatable.LowToHigh Translatable.HighToLow Translatable.NoDirection
Low To High
Translatable text. Line scanning direction. High To Low Translatable text. Line scanning direction. N/A
Other settings should not be modified.
170
Chapter
Data Harvester software

This chapter describes how to install Data Harvester software. It is assumed that all of the basic Windows installations and drivers have been performed.
Data Harvester Software Installation (page 172)
171
Data Harvester software Data Harvester Software Installation
Data Harvester Software Installation

To install the Data Harvester software on an Xplore tablet PC, copy the DH installer to the Tablet PC using a USB flash drive. The DH installer (version 4.1) is located in the following folder on the e-Unite DVD: [root]\UNITEV4.1\windows\Unite_DataHarvester_v4.1.0_8123.exe.
IMPORTANT
The Data Harvester installer software must be the same version as the software installed on the UCI host. eg. if you have installed Unite_V4.1.0_8123.exe on the UCI, then install Unite_V4.1.0_8123.exe on all Data Harvester tablet PCs. Copy the installer software to the tablet PC and double-click on the Installer icon. The software will automatically install. Once the Data Harvester software has been installed, a shortcut will be created on the desktop. Double click on this shortcut to run the Data Harvester.
172
Setting the IP address of a Data Harvester tablet PC

All Data Harvester tablet PCs are allocated a unique IP address when they are shipped from Vibtech. However, if a tablet PC is replaced, or Windows is re-installed, it may be necessary to set the IP address of the machine. If possible, re-use the previously allocated IP address. If this is not available, choose an IP adress in the range10.2.xx.xx where xx.xx is the Data Harvester ID. This is usually shown on a label on the back of the Data Harvester tablet PC. Keep a record of the IP address of the Data Harvester for future reference. To set the IP address, go to Start > Control Panel > System >Advanced > Environment Variables. In the System Variable table look for a DH_ID entry. If it is not there create it. Set the DH_ID to the Data Harvester ID.
173
174
Chapter
Windows UCI software

This chapter describes how to install UCI software on a Windows PC. It is assumed that all of the basic Windows installations and drivers have been performed.
Installing the UCI Software (page 176) UCI Networking set-up (page 178) RAU Firmware Update (page 180)
175
Windows UCI software Installing the UCI Software
Installing the UCI Software

The Windows version of the e-Unite UCI software can be installed on Windows PC and used in a staging area to update firmware on RAUs, and set acquisition parameters and working hours' parameters before RAUs are deployed in the field. The UCI Software is provided in an installer package that you can run by double-clicking on the Unite_v4.1.0_8123.exe file. It can be found on the SERCEL e-Unite DVD in the UNITEVx.x\windows folder. Before running the installer you should ensure that no Unite System Software applications are currently running. In the event that an application is left running, the installer should detect this and ask you to close any running applications to allow it to complete successfully. The install process is as follows: This dialog informs you which version of the Unite System you are installing. Click on Next to continue.
Figure 7-1
176
Windows UCI software Installing the UCI Software
Figure 7-2
This dialog allows you to select if the UNITE system should install itself as the default handler for SEG-D and SEG-Y files based on their extensions. Click on Next to continue.
Figure 7-3
The installer then runs and once complete, the dialog shall look as shown above. Click on Close to finish. On completion, the UCI main programmes icon will be placed on the Windows Desktop.
177
Windows UCI software UCI Networking set-up
UCI Networking set-up

The UNITE System requires that the computers networking address is configured with a specific setup. This is what allows the RAUs to detect and connect to the UCI successfully. To set this up, please follow these steps: 1. 2. 3. Open the Control Panel Open Network Connections Select the LAN connection you will use to attach to the root CAN to communicate with the RAUs and open its Properties. You should end up with the following dialog:
Figure 7-4
4.
Select Internet Protocol (TCP/IP) from the list of items the connection uses and click on Properties.
178
Windows UCI software UCI Networking set-up
5.
Set theTCP/IP properties to be IP Address 10.1.0.1 and the Subnet mask: 255.0.0.0 as shown below.
Figure 7-5
6.
Click OK and the setup will be complete.
179
Windows UCI software RAU Firmware Update
RAU Firmware Update

This section describes the process for updating the firmware in the RAU. RAU firmware is included in the installers for the UCI. Whenever a RAU connects to the UCI (via a wireless or wired connection) it automatically receives new firmware if updated firmware is available. The firmware is downloaded to the RAU's flash memory, and the RAU automatically reboots. On restart the RAU is running the new firmware.
180
Chapter
Peripherals
In this chapter:
Plotters (page 182) Infortrend S16F-R1430 RAID system (page 188) Tape drives (page 196) NAS server (page 214) FTP server (page 229) MDR or RVT300 virtual tape recorder (page 233) Vehicle Tracking box (page 236)
181
Peripherals Plotters
Plotters
The switches on the rear panel of the plotter should be set as shown below:
2 (On) 1 (Off)
Power On/Off
AC Power
Ethernet port
Figure 8-1 Plotter rear panel
Mount parts
4 screws, M650 4 screws, M512 Mount plate 756084647
Figure 8-2
182
8 screws, M616
Mount plate 756084647 4 standoffs, 756085132
4 screws, M650
Mount plate 756084647
Figure 8-3
8
8 mounting holes (dia. 6.2) Mount plate 756084647 242 300 350
492 514
Figure 8-4 Mounting dimensions in mm
183
VERITAS V12 plotter settings

Note If you want to reuse a plotter from a 408UL system, it must be
upgraded with an Ethernet port (upgrade kit part No. 1L21084066). See Ethernet port upgrade (page 185).
Physical interface configuration

- Remove the 2 screws securing the hinged rear panel, and flip it open. - Make sure the 40-pin ribbon cable is connected to the Short Line connector. - Make sure the 2-pin jumper (J15) is set to S. - Close the rear panel.
Configuration procedure
Power on the plotter. The display should read "IDLE M1". Press <ON/OFF LINE>. The display should read "OFF LINE". Press <MENU>. The display should (briefly) read the first option label "SEL MODE", and its value "USER M1". Examine options from "SEL MODE" to "BEEPER" using the following sequence: Change the current option value if necessary using <up> or <down> blue key, the display should read the new value of the option (see table below). Press <MENU> to display next option label. When done press <ON/OFF LINE>. The display should read "IDLE M1".
184
V12 / e-Unite settings

(Firmware version 3.1 or higher).
Table 8-1 V12 / e-Unite settings
Option SEL MODE SEL TEST CONTRAST SPEED MEDIA SCALING VERT EMU FF LENGTH SCANWIDTH BEEPER Label value USER M1 INACTIVE C5 (or higher) 4.0 IPS LT/HV PAPER NO SCALE 203 spi 2" LONG 296 bytes PULSED Comment User configuration location Auto test launcher Plot contrast Paper speed Paper thickness. For later-production paper choose HV Film. Plot scaling Vertical resolution in scans per inch Form feed length in inch Plot width in bytes per scan (1 byte = 8 dots). Paper out audio beep.
Ethernet port upgrade

An Ethernet port is required on the Veritas V12 plotter in order to attach it to the Unite system. To install the upgrade kit (SERCEL part No. 1L21084066), if required, do the following: 1. 2. 3. 4. Remove the left side cover. Flip open the rear panel. Unplug the ribbon cable from the plotter printed circuit board. Remove the DB37 connector mount bracket. Remove the connector and ribbon cable assembly.
185
Remove the two screws securing the rear panel
Notch required for Ethernet card mount bracket
Figure 8-5
5.
Remove the slotted plastic strip. Using cutting pliers and a file or a soldering iron, cut off two teeth from the plastic strip as shown in Figure 8-5 in order to make a notch in it so that the Ethernet card can be mounted. Put the slotted plastic strip back in place. Slip the ribbon cable from the Ethernet card into the cabinet and then secure the Ethernet card. Secure the Ethernet port panel and the Ethernet card mount bracket. Connect the ribbon cable from the Ethernet card to the interface card.
6. 7. 8. 9.
10. Plug the ribbon cable from the interface card into Short Line connector on the plotter printed circuit board. 11. Put the self-adhesive interface card mount plate in place and secure the interface card to it.
186
Self-adhesive mount plate Interface card
Ethernet port panel
Plotter printed circuit board
Ethernet card
L S
J15
Short Line
8
Figure 8-6
12. Set the J15 jumper to the S position. 13. Put the left side cover and rear panel back in place.
187
Peripherals Infortrend S16F-R1430 RAID system
Infortrend S16F-R1430 RAID system

Introduction
With the standard Unite server configuration, the seismic data is stored on the SATA disks inside the server computer. A higher data storage capacity can be achieved through the use of an optional external disk array (SERCEL Part No. 1L21087665, including a controller enclosure from Infortrend, disks, a Fibre Channel interface card for the server computer, and an Ethernet cord).
Figure 8-7 S16F-R1430 disk array
The S16F-R1430 RAID storage system from Infortrend is equipped with redundant and hot-swappable components to ensure continuous and reliable operation. It provides 4 Gbps Fibre Channel interface for high-speed data transfer. The configuration supplied by SERCEL (8 disks) has a 5.37 Tbyte storage capacity.
Cabling
Data transfer between the disk array and the server computer uses a Fibre Channel port. The following interface board is required in the computer, depending on whether you install it in a PCI or PCI-Express slot: QLOGIC QLA2342 (P/N 1660083296) in a PCI-X slot. QLOGIC QLE2462 (P/N 1660084970) in a PCI-Express slot. An Ethernet port is used for administration.
188
eth0 (ASF connector)
Ethernet
AC power S16F-R1430 Fiber channel FC QLA2342 AC power
Figure 8-8 Cabling to HP XW 8600 Server computer
Getting started
The disk array is properly configured prior to shipment from SERCEL. If, for any reason, you have to configure your system, see Troubleshooting (page 191).
Power on
1. 2. Plug in the power cord of each built-in power supply unit. Power on the two power supply units.
Connecting to the server

1. 2. Connect the Fiber Channel and Ethernet cables to the server. See Cabling (page 188). Power on the Server computer. It usually takes less time for the Server computer to boot up than it does for the disk array. If the Server and the disk array are powered up simultaneously and the Server finds the disk array is not ready when it tries to access it (on the request for mounting the /var/dump file system), then
189
the Server computer may reboot automatically, which is alright. If after the automatic reboot the disk array is still not ready on the request to mount the file system, the /var/dump directory will not be accessible for writing. A message is published in the log file of the e428 application (/var/ltmp/e428ServerLog.txt). 3. Open a Terminal window and check for successful connection to the disk array, using the ping command: > ping storage1 (Return) If you get a reply saying that a number of packets were sent and received, do not change anything. Failure to get a correct reply may mean that the disk array is not attached to the correct Ethernet port on the server computer. Move the Ethernet cable to another port on the server, and ping the network again. Once the network is properly installed, check the firmware version on the display of the disk array by selecting its View System Information menu. Use the arrow buttons until the firmware information is displayed. This should read 3.64P.07:
Firmware Version: 3.64P.07
If you do not have the correct firmware version, you must upgrade it. See Disk array firmware upgrade (page 193) for details.
Disk array import

WARNING
The disk array import procedure cannot be undone, meaning that you will not be able anymore to use the SATA disks inside the server computer for data storage (unless you reinstall the Operating System and Unite software). 1. In the Terminal window on the server computer, log in as root by typing: su
190
(press Return, type the root password, press Return).

The root Login and Password to enter is the one you defined when installing the servers Operating System (typically administrator). 2. Type the following two commands: cd /export/home/e-428/snPrm/systLin/infortrend ./inforImport
Troubleshooting
The RAID storage system is fully configured prior to shipment from SERCEL. If, for any reason, you have to configure your system, use the procedure below.
Power on
1. 2. Make sure the Ethernet cable is NOT connected to the Server. Power on the two power supply units.
IP configuration
Follow the steps below to configure the IP address of the disk array: 1. 2. Press and hold down the ENT button for more than 2 seconds (long press). Use the up and down arrow buttons to select the View and Edit Config Params menu.
View and Edit Config Params
3.
Press the ENT button once (short press).

Communication parameters
4.
Press ENT again.

LAN IP Configuration
191
5.
Press ENT twice.

L0[LAN] IP
6.
Press ENT again.

View & Setup IP Address
7.
Use the up and down arrow buttons to enter the disk array's IP address: 172.27.128.60
Input Addr:
Press ENT to store each digit.

Input Addr: 172.27.128.60
8. 9.
Press ENT to store the last digit of the IP address. Press ENT again, this time for more than 2 seconds, to store the entire address.
Net Mask:
10. Likewise (steps 7, 8, 9), set the Net Mask Address: 255.255.255.0. 11. This completes the IP configuration procedure. Press the ESC button to go back to the main menu. 12. Reset the controller (see below).
192
Resetting the controller

WARNING
This will erase all the data earlier stored on the disk array. 1. 2. 3. 4. 5. 6. 7. 8. 9. Long press the ENT button. Select the System Functions menu. Select the Shutdown this controller menu. Press ENT. Press ENT again and hold it down for more than 2 seconds. Wait until resetting is complete. Power off the disk array and the server computer. Connect the Ethernet cable. Power on the disk array. Wait until boot-up is complete.
10. Power on the server computer.
Disk array firmware upgrade

Check the firmware version on the display of the disk array by selecting its View System Information menu. Use the arrow buttons until the firmware information is displayed. This should read 3.64P.07. If you do not have the correct firmware version, you must upgrade it by following the steps below: 1. 2. 3. Log in on the server computer. Open a browser (Firefox) window. Connect to the following address: http://storage1
193
Figure 8-9
4.
Select Configuration from the User Name dropdown menu, and click LOGIN.
Figure 8-10
194
5. 6. 7.
Expand the Config menu in the left-hand panel and select the System menu. In the Download/Upload section to the right, select Download FW. Click on the Browse button and select the file: /export/home/e-428/snPrm/systlin/infortrend/ FA364P07_234_IFT_ESS16FR1430.BIN
8. 9.
Click on APPLY. Select Shutdown the controller.
10. Click on APPLY. 11. Power off the disk array. 12. Power off the server computer. 13. Power on the disk array and wait until boot-up is complete. 14. Power on the server computer.
Disk array initialization

1. In the Terminal window on the server computer, log in as root by typing: su (press Return, type the root password, press Return). The root Login and Password to enter is the one you defined when installing the servers Operating System (typically administrator). 2. 3. Type: cd /export/home/e-428/snPrm/systLin/infortrend Launch the initialization shell by typing the following command line: ./inforReset
195
Peripherals Tape drives
Tape drives
Tape drive shock-mount assembly
Figure 8-11 : Tape drive shock-mount parts
For CD490-E: shock-mount assembly part No. 752075848A. For CD590: shock-mount assembly part No. 1653077133A.
320 340 0
(Dimensions in mm)
20
20
320 340
20
6 mounting holes (dia. 7)
0
20
752075848A (CD490-E)
250
1653077133A (CD590)
300
480 500
Figure 8-12 : Tape drive mount plate
580 600
196
Supported tape drives

To see the list of supported tape drives, open the following file in the text editor: /export/home/sn408Xxl/sn408Sol/workSpace/tapes/devices.par This file does not only contain the list of supported devices but also the parameters for each of them. Example: "FUJITSU ", (a) Vendor Id (a) Product Id (b) Device class (c) Write retry page code (d) Write retry param code (e) Space to OEM support (f) The device class should be one of the following: 3592_CLASS, 3480_CLASS, 3490E_CLASS, 3590_CLASS, DLT_CLASS, LTO_CLASS, DAT_CLASS or NEW_CLASS. You can add new devices, with the appropriate parameters.
CAUTION
"M2488ED ", (b)
3490E_CLASS, (c)
2, (d)
0x9005, (e)
0; (f)
The following parameters must be supplied:
Extreme care is required if you add any device that has not been tested by Sercel, because it may not be exactly compliant with the SCSI standard and may need a software patch to work properly.
197
FUJI 3490-E or 3590 SCSI address

Setting 3490-E or 3590 SCSI address
The SCSI device address on the cartridge drive is properly set prior to shipment from SERCEL. However, after replacement or after connecting one additional cartridge drive, for example, you may need to change the SCSI address. This can be done using the five keys (SHIFT, TEST, START, UNLOAD, RESET) and the LED display on the front panel of the cartridge drive. The necessary instructions are provided below. Power up the cartridge drive. Wait for self-tests to be completed (about 30 seconds). If any cartridge is loaded in the drive, remove it. At this stage the front panel display should read : * or *0 Change the target ID.
WARNING
With the Unite system, only addresses 0 to 5 are allowed.
Note Remove medium changer magazine (if mounted) prior to
performing the procedure below. The following procedure describes the steps required to set the Target ID. Step 1 Press and hold both the TEST and UNLOAD keys, wait for OFFLINE to be displayed then release both keys (if there is an outstanding SCSI command or if there is a tape loaded in the tape drive then Off-line mode cannot be entered). Once the keys are released then the first item, DIAGMODE, in the main Off-line menu will be displayed. (Keys must be held for approximately 2 seconds before Off-line mode is entered).
198
Step 2 Step 3 Step 4
Press the START pushbutton until SETTING is displayed. Press the TEST pushbutton. The first option, 70: S.TAR, is displayed. Press TEST to view the setting. The setting may be incremented by pressing START or decremented by pressing SHIFT and START. Press TEST to return to 70: S.TAR Press SHIFT and START until 89: (3490-E) or 92: (3590) WTROM is displayed. Press TEST to view settings at option 89: WTROM. Press START until y is displayed. Press the TEST pushbutton to write the setting to ROM. Press TEST to return to WTROM. Press RESET twice to return to *.
Step 5 Step 6 Step 7 Step 8 Step 9 Step 10 Step 11
After self-tests are complete (this takes about 30 seconds), the display should read *0 or * unless the SCSI address display option is enabled (see below). The drive is ready for use with its new address.
Displaying SCSI address on FUJI 3490-E or 3590 operator panel

The Target ID (see above) can optionally be displayed on the cartridge drive operator panel when no cartridge is loaded. Power up the cartridge drive Wait for self-tests to be completed (about 30 seconds) If any cartridge is loaded in the drive, remove it. At this stage the front panel display should read: * or *0 (unless the SCSI address display option is already enabled).
Note Remove medium changer magazine (if mounted) prior to
performing the procedure below.

The following procedure describes the steps required to display the Target ID (SCSI address) on the operator panel. Step 1 Press and hold both the TEST and UNLOAD keys, wait for OFFLINE to be displayed then release both keys (if there is an outstanding SCSI command or if there is a tape loaded in the tape drive then Off-line mode cannot be entered). Once the keys are released then the first item, DIAGMODE, in the main Off-line menu will be displayed. (Keys must be held for approximately 2 seconds before Off-line mode is entered). Press the START pushbutton until SETTING is displayed. Press the TEST pushbutton. The first option, 70: S.TAR, is displayed. Press START until 74: S.*N is displayed. Press TEST to view the setting. The setting can be changed by pressing START or SHIFT and START.
Step 2 Step 3 Step 4 Step 5
The display should read *N: YES for the SCSI address to appear on the operator panel Step 6 Step 7 Step 8 Step 9 Step 10 Step 11 Step 12 Press TEST to return to 70: S.TAR Press SHIFT and START until 89: (3490-E) or 92: (3590) WTROM is displayed. Press TEST to view settings at option WTROM. Press START until y is displayed. Press the TEST pushbutton to write the setting to ROM. Press TEST to return to WTROM. Press RESET twice to return to *.
After self-tests are complete (this takes about 30 seconds), the display should read *N (where N is the SCSI address).
200
Resetting M2488 T4 drive initialisation parameters

In the event of record errors on a 3490E M2488 T4 FUJITSU drive, use the procedure below to reset the initialization parameters. 1. 2. Power off the drive. Connect an RS cable between a PC Com port and the drive Com port. Use one of the following cables according to the PC Com port:
DB25 socket to DB9 socket 2 (tx) 3 (rx) 4 (rts) 5 (cts) 6 (dsr) 7 (gnd) 20 (dtr)
_______ 2 (rx) _______ 3 (tx) _______ 8 (cts) _______ 7 (rts) _______ 4 (dtr) _______ 5 (gnd) _______ 6 (dsr)
DB9 socket to DB9 socket 3 (tx) 2 (rx) 4 (dtr) 5 (gnd) 6 (dsr) 7 (rts) 8 (cts)
_______ 2 (rx) _______ 3 (tx) _______ 6 (dsr) _______ 5 (gnd) _______ 4 (dtr) _______ 8 (cts) _______ 7 (rts)
3.
Open a new Hyperterminal session by selecting: Start menu > Programs > Accessories > Communication > Hyperterminal
Figure 8-13
201
4.
Click on Configure and set the following parameters: - 19200 bauds - 8 data bits - No parity - 1 stop bit - Hardware flow control
5. 6.
Connect to the Com port (Click on the Call icon). Power on the drive. The display should read the startup internal tests result. Wait for the final SYSTEM INITIALIZATION COMPLETE message:
Figure 8-14
7.
Figure 8-15
8.
Type Help to get help on current menu available commands: >help OPPANEL SERVO HARDWARE Emulate offline operator panel Servo code debug menu Hardware support menu
202
CODELOAD DEBUG HELP
RS-232 codeload operations menu Debug menu Display help for current menu
CODE_REVISION Print code revision
****** MAIN ****** 9. Type Hardware >hardware ****** HARDWARE ****** q - return to prior menu group 10. To see the Hardware menu available commands, type Help help DDMT EDMT Disable deadman timer Enable deadman timer
NVRAM-DEFAULTS Set NVRAM to default values & reset HELP Display help
11. To restore the factory configuration and reset the drive, type nvram-defaults >nvram-defaults PROCESSOR RESET (after offline, running from WCS) Copyright (c) 1995-1999 Fujitsu Limited Code built: 990527 04 UCT
Version: 7 B01 OS START OS TASK INITIALIZATION COMPLETE SYSTEM INITIALIZATION COMPLETE 12. Power Off the drive.
LTO drive SCSI address

The SCSI device address on the cartridge drive is properly set prior to shipment from SERCEL. However, after replacement or after connecting one additional cartridge drive, for example, you may need to change the SCSI address. This can be done using the buttons on the rear panel. 1. Power off the drive. 2. Press the + or - button to choose the desired SCSI address.
Press + or - button to set SCSI address
Figure 8-16 : LTO rear panel
204
CYPRESS 3490E-DIF
The procedure below is for configuring a CYPRESS 3490E-DIF SCSI tape recorder based on an MP-8400-series cartridge drive. Prior to using the tape drive with the Unite system, the EMULATION parameter must be set to STK, and the COMPRESSION parameter must be set to OFF. All other parameters must be left at the default setting. To do that, use the three buttons available under the display. (For details, refer to the manufacturers User Manual).
STAND BY OFL 18/36w
8
Configuring the tape drive
- Power up the tape drive. Wait until the self-test is completed. - After STAND BY appears on the front panel display, do the following:
STAND BY OFL 18/36w Press button 1 to go to Offline.
OFFLINE UNLOADED ONL DEN func SCSI func ID 5 CHG
Press button 3 (Func).
EXIT
MENU FUNCTIONS CONF DIAG >>> ENTER PASSWORD EXIT ---- ----
Press button 1 (Conf).
Press 3, then 2, then 3 (this enters the password).
205
CONFIGURE SCSI DRIVE
>>>
Press 2 to select DRIVE
COMPRESSION ON EXIT CHG >>> COMPRESSION OFF EXIT CHG >>>
Press 2 (CHG) to turn compression OFF.
Press 3 (>>> ) three times until EMULATION is selected.
EMULATION ECHO EXIT CHG >>> EMULATION STK EXIT CHG >>> SAVE SETUP ? YES NO TEMP ARE YOU SURE ? YES EXIT CONFIGURE SCSI DRIVE CONFIGURE 18WRT EXIT
Press 2 (CHG) to change Emulation to STK.
Press 1 (EXIT).
Press 1 to save.
Press 1 to confirm.
>>>
Press 3 (>>> ) twice.
>>>
Press 2 (EXIT).
MENU FUNCTIONS CONF DIAG >>> MENU FUNCTIONS ---- EXIT >>> OFFLINE UNLOADED ONL DEN func STAND BY 18/36w OFL
Press 3 (>>> ) twice.
Press 2 (EXIT).
Press 1 to go to On Line.
206
Changing the SCSI address

Power up the tape drive. Wait until the self-test is complete. After STAND BY appears on the front panel display, do the following:
STAND BY OFL 18/36w Press button 1 to go to Offline.
OFFLINE UNLOADED ONL DEN func SCSI func ID 5 CHG
EXIT
Press button 2 as many times as necessary to set the desired SCSI address (with the Unite, only addresses 0 to 5 are allowed).
SCSI func
ID X CHG
EXIT
Press 3 (EXIT).
SAVE SETUP ? YES NO ---ARE YOU SURE ? YES EXIT SCSI func ID X CHG
Press 1 to save.
Press 1 to confirm.
EXIT
Press 3 (EXIT).
OFFLINE UNLOADED ONL DEN func STAND BY OFL 18/36w
Press 1 to go to On Line.
207
3592 cartridge drive

Firmware revision
3592 Firmware level required: D3I0_4E9 or higher.
QLA card installation

A QLOGIC Optic FC Dual port PCI card (QLA2342L-CK) must be installed in the e-Unite server computer. The card must be equipped with the appropriate bracket for installation in a full-height PCI slot. See Tape drive interface cards (page 48).
Connecting 3592 drives

Note Put dustcaps in place on unused connectors.
Port 0 1 0 1
QLA card
Server computers rear panel
LC/LC multi-mode FC cable Power
Figure 8-17 Rear view (2 drives)
208
Port 0 1
QLA card
Server computers rear panel
LC/LC multi-mode FC cable Power
Port 0 1
Power
Figure 8-18 Rear view (4 drives)
To set the parameters of each drive, install the Service control panel on top of the enclosure and connect the serial cable from the control panel to the desired drives serial connector on the front panel.
Service control panel
Service control panel
Navigate Upper drive Serial cable Lower drive Lower Upper Software Reset (1) Up (3) Down (4) Select (Enter) (5)
Maintenance (2)
Figure 8-19 Front view

Setting drive parameters

1. 2. 3. 4. Be sure no cartridge is loaded in the drive. Use the standard shutdown procedure to power off the e-Unite server computer. Connect the serial cable from the Service panel to the desired drives serial connector on the front panel. Press the software Reset button (see Figure 8-19 on page 209). As a result the OPTIONS menu is available on the Service panel.
Use Use to scroll through menu to select or enter or scroll through options OPTIONS SERVICES
Figure 8-20 SERVICES menu
WARNING
Do not use the FORCE ERROR DUMP menu. 5. Press the maintenance button (see Figure 8-19 on page 209). - Select CE OFFLINE MODE. - Select CONFIG-INSTALL. Be sure FORCE ER LOG IS OFF is selected (otherwise fugitive errors might arise during recording). - Select DRV. OPTIONS then DRV. FEATURES. Be sure "J1A RACK" is selected. Note that some tape drive enclosures may require rack mount library information in the DRV. OPTIONS menu. - Press the software Reset button to quit the maintenance menu. This takes you back to the OPTIONS menu. 6. 7.
210
Select SERVICES. Select SET ONLINE.

- Select PORT 0 (assuming the ports are connected as shown in Figure 8-17 on page 208). 8. Still from the SERVICES menu, select FIBRE OPTIONS. - Select SET PORT 0. - Select SET SPEED. - Select 2 GB, then YES. - Select SET TOPOLOGY, then L-PORT, YES. - Select SET HARD ADDRESS. See the table below for the equivalent SCSI address that will be assigned to the drive, depending on the port ID number you choose from the SET HARD ADDRESS menu. For example, choosing e8 as port ID will assign 1 as equivalent SCSI address to the drive in the lower slot.
Table 8-2 SCSI address assignment (Solaris only)
Port ID
ef e8 e4 e2 e1 e0
Drive location
Upper Lower Upper Lower
Equivalent SCSI ID
0 1 2 3 4 5
SET HARD ADDRESS Use then CANCEL e0 e1 SAVE DATA --VALID--
to choose the desired Port ID number
Figure 8-21
- Make sure the right-hand column reads VALID for the selected address. - Select SAVE DATA, then YES.
Note The above table is only intended for a computer running on
Solaris. With a computer running on Linux, the SCSI address is automatically assigned by Linux itself. If two or more 3592 tape drives are attached to the system and you want to know which address is assigned to each drive, insert a cartridge into one drive and look at the indicators in the Export window to see which drive has a cartridge inserted (or move the mouse pointer to each Tape indicator to display the status popup). 9. Press the software Reset button. 10. Power up the workstation. See if the drive appears in the Recorder main window.
Manual calibration
With firmware code level D3I0_4E9 or higher, automatic calibration is intentionally inhibited in order to preclude any spurious interruption of recording. As a result, if the drive determines that a calibration is required, then a CALIB message will appear on the drive message display (on the bezel) and on the Service panel (if connected) every time the tape is unloaded, until a manual calibration is done by using the following procedure: 1. 2. 3. 4. Connect the control panel to the desired drive (see Figure 8-19 on page 209). Be sure the drive is powered up, no jobs are running, no tape is loaded. Push the maintenance button (2). Select CE OFFLINE. You may get a CONFIRM OFFLINE MENU at this step if drive believes a job might be running. 5. 6. Select UTILITIES. Select CALIBRATE DRIVE. This takes you to the LOAD SCRATCH TAPE MENU.
212
7. 8.
Load a scratch tape in the drive. After the tape is loaded and Ready, select PROCESS LOADED TAPE. The CE WAIT MENU should appear. Wait until the procedure is complete (this takes approximately 4 to 5 minutes).
9.
After the procedure is complete, the CE DIAGS GOOD or CE DIAGS FAILED MENU is displayed.
10. Select UNLOAD DRIVE (you need not wait for Unload to complete). 11. Select BACK TO CE MENUS. This takes you back to the CE OPTIONS MENU. 12. Push the settings button (2). 13. Select OPERATOR MODE.
Note If a tape is already loaded before you get to step 7, you have to
Unload it before proceeding.

Note If the tape loaded is File Protected, a "Tape write prot'd" Status
message will be displayed at step 8. Unload it and then proceed with an unprotected tape.
Note The Calibration procedure will write on the tape, but it writes in
an area that does not contain customer data. The tape used does not need to be new or unused, but should be a known good tape.
Note If the Calibration procedure succeeds, the new values are saved
in non-volatile memory.
Firmware update
If, for any reason, firmware needs to be updated, use an FMR cartridge from IBM or created from another 3592 drive. See IBM documentation.
213
Peripherals NAS server
NAS server
Overview
The NAS (Network Attached Storage) system comes in three versions: Model B (white enclosure), Model C (black enclosure), Model D (black enclosure too, with a label mentioning Model D), and 1-TB Model XA (labelled XA). The NAS system is supplied by SERCEL with the following configuration: Linux (Storiq) Operating System. Dual-Ports Gigabit network card. On a Model-B system, the100MB network card on the motherboard is unused. On a Model-C system, the 1-GB network port available from the motherboard is used. On a Model-D or -XA system, the 1-GB network port is available from the PCI slot. root login with spider77 as password for console mode general administration and using Webmin. storiq login with spider77 as password for graphical mode.
IMPORTANT
Model D
Figure 8-22 Model D
RAID1 (mirror) mounted disks with a 380 Gbyte storage capacity.
Affix a sticker on the enclosure to identify it as Disk# 1 or Disk# 2. The NAS system is fully configured prior to shipment from Sercel. Apart from setting networking parameters, you do not normally have any software installation work to do (if required, see Operating System software reinstallation on page 223).
IMPORTANT
To power off the NAS system, briefly press the POWER button on the front panel.
Shock-mount assembly
Shock-mount assembly part No. 756083303.
Adjustable stop position
8
See below
Figure 8-23 : NAS shock-mount parts
250
230 340 320
(Dimensions in mm)
Figure 8-24 : Lower mount plate

Attaching a NAS system to the e-Unite local network
NAS server
PCI
e-Unite server
eth0
(User Network)
eth2
(Service port)
eth1
(e-Unite local network)
172.27.128.1 172.27.128.41 (42)
Ethernet switch
Figure 8-25 Model-B system (Operating Software version 1.0)
NAS server
PCI
e-Unite server
eth1
(User Network)
eth0
eth2
(User Network)
172.27.128.1
Ethernet switch
172.27.128.41 (42)
Figure 8-26 Model-C system (Operating Software version 1.1 or 2.0)
NAS server
e-Unite server
eth0
(User Network)
PCI
eth2
eth1
(User Network)
172.27.128.1
Ethernet switch
172.27.128.41 (42)
Figure 8-27 Model-D system (OS version 2.0) or XA (OS version 3.1)
216
IMPORTANT
NAS# 2 (IP address 172.27.128.42 typically) is automatically assigned to the DOL database. NAS# 1 (IP address 172.27.128.41 typically) is automatically used to record SEGD files.
Note To power up the NAS system, press the POWER button
on its front panel. (To power off, briefly press the POWER button).
Setting up NAS parameters

To configure the NAS disk, connect a standard PC display, mouse and keyboard to the enclosure.
8
VGA display
USB PCI PCI
PS2 mouse PS2 keyboard
VGA display
USB
Model B
Model C or D or XA
Figure 8-28
Setting the NAS disk identification number

The NAS disk should be identified as Disk# 1 or Disk# 2, by means of a sticker visible on its enclosure. For the host name number to be consistent with the identification number appearing on the sticker, you may have to change the setup parameters by doing the following: 1. Depending on which model you are using, log in as storiq or root: - On a Model-B system: enter storiq as Username and spider77 as password. Click on the Xterm icon in the toolbar at the foot of the desktop (or select it from the ICEWM menu). In the Terminal window, type:
su - root spider77
(press Return). (the password is not viewed). Press Return.
- On a Model-C or -D or -XA system: enter root as Username and spider77 as password. 2. 3. Change directory to /usr/local/binsh, by typing:
cd /usr/local/binsh
To configure the disk as Disk# 1, type:

./setNas1Id
or, to configure it as Disk# 2, type:

./setNas2Id
4.
Reboot (type reboot in the Terminal window). NAS model you are using, is shown in Table 8-3.
Table 8-3 Default port assignment
NAS enclosure NAS port eth0
User Network e-Unite local network e-Unite local Network e-Unite local Network
Note The default assignment of network ports, depending on which
Model
B C D XA
Software version
1.0 1.1 or 2.0 2.0 3.1
eth1
e-Unite local network User Network User network User network
eth2
User Network User Network User Network
Should any malfunction appear on the e-UNITE local network port, you can use the setNas command to reassign the ethernet ports of the machine, as an interim solution. To do that, use the following syntax:
./setNas<x>Eth<y>
replacing
<x> <y>
by 1 for Nas1, or 2 for Nas2 by 0 or 2 or 1.

218
The setNas1Id command returns the system to the default port assignment.
Note For Model-B users only:
- It is important to note that only the Gigabit ethernet ports (eth1 and eth0) have been qualified by Sercel. Using the Fast Ethernet port (eth2) may result in lesser performance. - With software version 1.0, the default IP address automatically assigned to the eth1 port (by loading software or using the setNas1Id command) is one for a 408UL network. You have to enter the address for the e-Unite network (172.27.128.41 or 42) manually. See Figure 8-31 on page 220.
NAS IP address on the User Network

To attach the NAS disk to a network other than the e-Unite local network, use the following procedure to configure the User Network port: 1. 2. Power up the machine. For Model-C or -D or -XA users only: log in with root as Username and spider77 as password, and then type gdm to get inside GNOME desktop manager; Log in as storiq with spider77 as password. Launch Mozilla (click on the icon at the foot of the desktop or select it from the ICEWM menu). In the Mozilla window, click on the StorIQ Administration shortcut. Accept licence notifications if any. This opens the Webmin login window. Log in with root as Username and spider77 as password. Click on the Networking tab, then on the Network Configuration icon.
3. 4. 5.
6. 7.
219
Networking Logout
Network configuration
Figure 8-29
8.
Click on the Network Interfaces icon.

Network Interfaces
Figure 8-30
9.
Depending on which model you have, see Figure 8-31, or Figure 832 below.
Click on eth0 to enter User Network Name address

eth0 eth1 eth2
Type
IP Address 172.27.128.41
Netmask 255.255.255.0
Active at boot?
Figure 8-31 Model B (software version 1.0)
Note With software version 1.0, the IP address automatically
assigned to the eth1 port is one for a 408UL network. You have to enter the address for the e-Unite network (172.27.128.41 or 42) manually.
220
Click on eth1 or eth2 to enter User Network address
Name eth0 eth0:1 eth1 eth2
Type (virtual)
IP Address 150.10.128.41 172.27.128.41
Netmask 255.255.0.0 255.255.255.0
Active at boot?
Figure 8-32 Model C or D (OS version 1.1 or 2.0) or XA (3.1)
Note With software version 1.1 or 2.0, the eth0 interface is visible to
a 408UL or e-Unite local network with no need to make any changes. 10. Set the appropriate IP address and Netmask for the ethernet port to be visible to the users private network.
Figure 8-33
Click Save. 11. In the Network Configuration window, click on the Apply Configuration button (see step 8). 12. Click on Logout on the right-hand border of the Webmin window (see step 7). 13. Remove the display, mouse and keyboard. See Attaching a NAS system to the e-Unite local network (page 216).
221
WARNING
Your changes are lost after you run the setNas1Id command (used to set the systems identification number). The setNas1Id command returns the system to the default port assignment (see Table 8-3 on page 218).
Attaching a e-Unite NAS system to another network

The settings of the User Network port (eth0 interface for Model B, eth1 interface for Model C or D or XA), should allow the disk to be visible to the desired external network. See NAS IP address on the User Network (page 219).
IMPORTANT
Be sure appropriate network security services are implemented within the user network you are attaching the NAS system to. Connect the User Network port to an Ethernet port on a UNIX workstation and mount the exported (/mnt/raid) directory at the workstations mount point, using the command: mount <Host name or IP address>:/mnt/raid /<mount point> To copy your SEGD files from the NAS system to a tape, you can also use the Copy+ software tool available from SERCEL on a computer running on Linux or a personal computer running on Windows (and equipped with an SCSI port). See Unite Users Manual Vol. 3 (Copy+ software tool on page 17).
222
Operating System software reinstallation

If, for any reason, you need to reinstall software, connect a standard PC display, mouse and keyboard to the enclosure, then install the appropriate software version, depending on which NAS model you have: NAS Sercel version 1.0 (page 223) for a Model-B system; NAS Sercel version 1.1 or 2.0 or 3.1 (page 225) for Model C or D or XA.
NAS Sercel version 1.0

1. 2. Power up the NAS unit. Insert the NAS Sercel version 1.0 StorIQ CD-ROM into the drive so that the machine can boot on the CD-ROM. To boot on the CDROM, briefly press the Power button, wait until power off is complete, and then briefly press the Power button again. When boot is prompted, press Return (or wait half a minute). The log-in window should appear. Log in under the following account: - User: 5. 6. 7. 8. 9.
storiq
3. 4.
- Password: spider77 Double-click on the StoriQ Installation icon (in the upper right corner of the screen). Enter the password: spider77 Click OK to dismiss the message that shows up. When Installation process is finished appears (in the Finished window), click OK. Wait until the RAID 1 reconstruction is complete (this may take about 2 hours or more). The reconstruction progress can be monitored using the command cat /proc/mdstat. The message resync followed by a percentage should appear, meaning that
223
the RAID 1 reconstruction is in progress. Periodically relaunch the cat command by simply pressing the up arrow key (), then Return to see if reconstruction is complete. 10. To eject the CD-ROM, briefly press the Power button. Follow the step-by-step instructions prompted and wait until the system power is off. 11. Press the Power button to power up the system. Wait until the StorIQ Welcome window appears. 12. Log in with storiq as Username and spider77 as password. 13. Click on the Xterm icon in the toolbar at the foot of the desktop (or select it from the ICEWM menu). In the Terminal window, type:
su - root spider77 cd /mnt chmod 777 raid
(press Return). (the password is not viewed). Press Return.
14. Press Ctrl D 15. Press Ctrl D 16. Launch Mozilla (click on the icon at the foot of the desktop or select it from the ICEWM menu). 17. In Mozilla window, click on the StorIQ Administration shortcut button. Accept licence notifications if any. This opens the Webmin login window. 18. Log in with root as Username and spider77 as password. Click NO to dismiss the message that shows up. 19. Click on the System tab. 20. Click on Bootup and Shutdown. 21. Use the scrollbar to go to proftpd, and then click on the proftpd link.
22. Choose Yes for the Start at boot time? option. 23. Click on Save. (This should set proftpd to Yes). 24. Briefly press the Power button to power off the system.
NAS Sercel version 1.1 or 2.0 or 3.1

1. 2. Power up the NAS unit. Insert the NAS Sercel version 1.1 or 2.0 or 3.1 StorIQ CD-ROM into the drive so that the machine can boot on the CD-ROM. To boot on the CD-ROM, briefly press the Power button, wait until power off is complete, and then briefly press the Power button again. When boot is prompted, press Return (or wait half a minute). The log-in window should appear. Log in under the following account: - User:
storiq
3. 4.
- Password: spider77 - Click OK. 5. 6. 7. 8. 9. Double-click on the StoriQ Installation icon (in the upper right corner of the screen). Enter the password: spider77 and click OK. Click OK to dismiss the message that shows up. When Installation process is finished appears (in the Finished window), click OK. To eject the CD-ROM: - Briefly press the Power button. - Wait for the CD-ROM to be ejected. - Follow the step-by-step instructions prompted and wait until the system power is off.
225
10. Press the Power button to power up the system. After the system has booted up, the yellow light on the front panel remains on, meaning that RAID 1 reconstruction is in progress. 11. Wait until reconstruction is complete (this may take about 2 hours or more). To see if reconstruction is complete, do the following: - Log in as root, with spider77 as password; - Type the command raid_cli info - You can periodically relaunch the raid_cli info command by pressing both Shift and 1 twice and then Enter. (The command returns the percentage completed, or OK when complete). 12. After reconstruction is complete, reboot the NAS (briefly press the Power button to power down).
NAS system rescue

If the main system software isn't usable for some reason ( hardware of software failure) it's still possible to operate the StorIQ system in rescue mode. The system software is installed on both internal disk drives (sda and sdb). rescue mode will boot up from the secondary drive.
How to start in rescue mode

If the system is powered but unusable, you may power it down by keeping the power button pressed for 5 seconds. If the primary drive (sda) still works Power up the system. After the "XPC" splash screen, an intellique screen is displayed. If the primary drive is working, you'll see a text menu with two options: storiq rescue
226
Use the keyboard cursor keys to highlight "rescue" and hit "enter" key. The system will start in rescue mode (from the secondary disk drive, sdb). If the primary drive is unavailable (disconnected or unreadable): The system will display only one option at the "Intellique" screen: rescue-critical If the screen stays blank If the "INTELLIQUE" screen doesn't show up and the screen stays blank, the disk controller may be locked up by a failed disk drive or cable (hardware failure). Try disconnecting the primary (sda) drive may help. To do so, power down the system, unplug power cord, open chassis and unplug the primary drive (sda) SATA connector. Identifying the primary (sda) connector Facing the back of the system (model SK22G2), the primary disk is connected the right SATA connector on the motherboard. See Figure 8-34.
Chassis front
SATA connectors
Chassis backside
Figure 8-34
227
Working in rescue mode "rescue mode" should operate normally. However you should immediately proceed to backup your data before reinstalling the system (in case of a software problem) or returning the system for maintenance (in case of an hardware failure).
228
Peripherals FTP server
FTP server
Installing server software
1. Insert the e-Unite CD-ROM into your PCs drive and open the PCTOOLS directory. Double-click on the FILEZILLA_SERVER_x_x_x.exe file. In the Licence Agreement window, click I accept. In the Choose Components window, click Next. In the Choose Install Location window, choose the folder in which to install server software. Click Next
2. 3. 4.
Figure 8-35
5.
In the Startup Settings window, click Install. Follow the instructions prompted. After FTP server software is installed, see Server settings (page 230).
Figure 8-36
229
Server settings
1. Double-click on the FTP server user interface icon on the desktop. In the Connect to Server window, click OK. This opens the server user interface window.
Figure 8-37
2. 3.
From the Edit menu in the FileZilla Server window, select Users. In the General page, click on the Add button to create a user account.
Figure 8-38
4.
In the User account window, enter the same User Account name as in the e-Unite GUI Export window. See Unite Users Manual Vol. 1.
Figure 8-39
Click OK.
5.
Still in the General page, choose Password and enter the same Password as in the e-Unite GUI Export window. Be sure Enable Account is enabled.
Click to enter password
Figure 8-40
6.
Select the Share Folder page. Be sure the Show Relative Path option is enabled.
Set permissions
Be sure H appears here
Set as Home directory
Enable Show relative path
Figure 8-41
Note Be sure the letter H appears ahead of the shared folders. If
that is not the case, click on the Set as Home dir button.
231
7.
From the Edit menu in the FileZilla Server window, select Settings.
Enter 0
Figure 8-42
8. 9.
Be sure the No Transfer timeout setting reads 0. Click OK to save your settings.
232
Peripherals MDR or RVT300 virtual tape recorder
MDR or RVT300 virtual tape recorder

Instead of writing and reading to and from tape, the Mirage Data Recorder (MDR) or Removable Virtual Tape recorder (RVT300) utilizes two Removable Disk Modules (RDMs) with RAID 1 protection against data lost. The RDM pairs can be written to, dumped from, stored, erased, and returned to the field for re-use like conventional tape cartridges.
Disk 1 Disk 2
Key locks
8
Power switch
Figure 8-43 Front panel
The MDR (RVT300) attaches to the e-Unite server computer via an SCSI port, and emulates a standard tape cartridge system. It allows you to create cartridges that are 100% inter-changeable with a conventional tape cartridge drive, by archiving to an IBM3590 or LTO tape drive attached to its Archive (LVD SCSI) port.
HOST (Port 0) to e-Unite server computer
ARCHIVE (Port 1) to tape drive
Figure 8-44 Rear panel

The table below shows a typical way of handling acquired seismic data in the field with two pairs (A and B) of Removable Disk Modules.
Recording truck Base camp
1 - Record to MDR. Upper (pair A Disk 1) Lower (pair A Disk 2) 2 - Remove pair A and take Disk 1 to base camp. - Insert Disk 1 (from pair A) into upper slot. 3 - Insert pair B. Upper (pair B Disk 1) Lower (pair B Disk 2) - Record to MDR. - Erase volume when Archive complete. - Remove Disk 1; take it to recording truck. - Launch Archive function. Upper (pair A Disk 1) 3590
3 - Remove pair B and take Disk 1 to base camp. - Insert Disk 1 (from pair B) into upper slot. 4 - Insert pair A.
Upper (pair A Disk 1) Lower (pair A Disk 2) - Record to MDR. - Erase volume when archive complete. - Remove Disk 1; take it to recording truck. and so forth. - Launch Archive function. Upper (pair B Disk 1) 3590
5 and so on
The first time two blank disks are installed in an MDR (RVT300), they are configured with identical ID numbers to run in mirrored mode. Each disk should be marked with whatever convention you like, specifying
which pair and which slot it is assigned to (Disk1 in the upper slot / Disk2 in the lower slot). For example, you might affix a sticker reading A1 and standing for Pair A, upper disk. If one disk fails during acquisition, recording is allowed to continue so long as the other disk keeps working properly. After the disk pair is removed from the MDR (RVT300), for example because recording space is running out, only one of the mirrored disks should be transported (e. g. to the base camp) at any time. This prevents any accidental loss of data if the disk is damaged during transport. You cannot reuse a disk pair until one of its disks has all its data volumes marked as archived, verified and erased by using the Archive function. The other disk in the pair does not need to be erased. If, for any reason, you need to reconfigure a disk pair, use the Configuration menu on the MDR (RVT300). For details on how to use each menu, see the Users Guide supplied together with the MDR (RVT300).
235
Peripherals Vehicle Tracking box
Vehicle Tracking box

The tracking box connects to the workstation through a serial line (A and/or B port of the server computer).
Position Port A Tracking box Service message or printer Port B Waypoint, service message Port A Server computer
Figure 8-45 : Vehicle tracking box serial ports
See also Unite Users Manual Vol. 1 (Positioning -Vehicle tracking).
236
Chapter
Field Equipment deployment

In this chapter:
Infrastructure Network (page 238) Deployment procedure (page 243) Autonomous Operation (page 245) RAU Field Deployment (page 247) CAN Field Deployment (page 251) MESH Field Deployment (page 255) Antenna Mast Field Deployment (page 267) Fibre Optic Cable Deployment (page 275)
237
Field Equipment deployment Infrastructure Network
Infrastructure Network
This section describes the recommended procedure for deploying a Unite system Infrastructure Network when intended to be operated in the Infrastructure Mode. Firstly, it is recommended that a suitable location be found for the recording vehicle. If VHF radio links are required for communicating with dynamite controllers or vibrators, then a suitable location may be central to the active part of the spread, preferably on high ground, but without overhead foliage or other obstructions such as power lines. Before beginning deployment of the field equipment, a certain amount of system planning is recommended.
System Planning
When planning the layout of the Infrastructure network, the following factors need to be taken into account: 1. 2. 3. 4. 5. RAU density (ie the number of RAUs that will connect to one CAN). CAN - RAU Wireless range. CAN - CAN Wireless range (if wireless backhaul is required). Prospect Topography. Vegetation.
RAU Density
The RAU density will depend mainly on the acquisition parameters, i. e. receiver group interval, but will also be influenced by the CAN RAU Wireless range. The following table gives an indication of RAU density with varying receiver geometry and CAN - RAU wireless range.
238
Table 9-1 RAU density per CAN under varying conditions Receiver Line Receiver Interval Group Interval CAN-RAU Wireless Range 250m 15m 20m 25m 2D 33m (110ft) 50m 67m (220ft) 120m 160m 200m 264m (866ft) 400m 536m (1760ft) 150m 200m 250m 330m (1100ft) 500m 670m (2200ft) 15m 20m 25m 33m (110ft) 50m 67m (220ft) 15m 20m 25m 33m (110ft) 50m 67m (220ft)
15 10 7 109 61 39 22 9 5 87 49 31 18 7 4 21 14 10 213 120 76 44 19 10 171 96 61 35 15 8 30 20 14 436 245 157 90 39 21 349 196 125 72 31 17 33 25 20
350m
46 35 28
500m
66 50 40
The maximum RAU density is 200 RAUs per CAN, a higher density than this will not work, and the optimum RAU density is 100-200 per CAN. As can be seen in Table 9-1 it is possible with certain combinations of receiver geometry and wireless range to exceed the maximum allowable density, therefore it is important to ensure that the wireless range of the CANs is appropriate to the survey geometry.
239
CAN - RAU Wireless Range

The achievable range between RAU and CAN is determined primarily by the following factors: Transmit power. Vegetation in the line-of-sight. Antenna height. Line-of-sight obstructions. The level of transmit power is limited by regulation and varies from one country to another. In some countries the CANs will be equipped with In-line RF amplifiers to increase the transmit power, while in other countries they are not permitted. If you are in any doubt as to whether your CANs are equipped with RF amplifiers, please contact Sercel or their agent in your country. In certain circumstances, it may be necessary to reduce the wireless range. For example, a very high-resolution survey in an area with good wireless propagation characteristics may cause the RAU density to be too high otherwise. In this case, the RF amplifiers (if fitted) would need to be removed from the CAN. If no RF amplifiers are fitted, the CAN transmit power can be adjusted from the UCI. Vegetation such as long grass (into which RAUs are placed) or trees will reduce the wireless range. The actual attenuation will vary according to the density and type of vegetation, so it is advisable to raise the RAUs out of any long grass if possible. The information contained in Table 9-2 can be used to estimate CAN to RAU wireless range under various conditions. The height differential between the CAN antenna and the RAUs is an important factor in determining range, and it is always preferable to have the CAN antenna as high as possible. Therefore, to achieve maximum range, it is always advisable to place the CANs on high points on the terrain where possible.
240
Due to a physical effect known as Fresnel interference, the wireless range can be increased by raising the RAUs from the ground by as little as 1 metre. The wireless range can be drastically reduced by line-of-sight obstructions such as buildings or very thick trees. The nature of the broadband wireless signal is such that it will not penetrate buildings and very poorly penetrates trees. Therefore such solid line-of-sight obstructions will effectively limit the wireless range. The same applies to topographical features such as hills.
Table 9-2 CAN - RAU Wireless Range Estimates Range Estimates CAN Power Setting RF Amplifer 100mW No Amplifier 30mW
50m 125m 250m
Dense trees
250m 100m
Light trees
500m 250m
Open area
1000m 500m
CAN - CAN Wireless Range

The achievable range between CANs is determined primarily by the following factors: Antenna height. Line-of-sight obstructions. The level of transmit power is limited by regulation and varies from one country to another. The Mesh Node is supplied preconfigured for the relevant regulations in your country. In order to provide a high sustained data throughput, the Wireless Backhaul uses a carrier frequency in the 5.4GHz - 5.8GHz band. Radio signals at these high frequencies do not penetrate line of sight obstructions very well. As a result, any obstructions such as trees will dramatically reduce the achievable range between CANs. It is advisable to place additional CANs to avoid obstructions altogether rather than placing them closer together as illustrated in the sketch in Figure 9-1.
RAU Positions
Obstructed line of sight
Additional CAN to avoid obstruction
Figure 9-1 Avoiding Line-of-sight obstructions

Field Equipment deployment Deployment procedure
Deployment procedure
Once the recording vehicle, UCI and support equipment, and Root CAN have been brought into operation, the field equipment deployment should be deployed in the sequence given below.
Deploy CANs
The CANs and Mesh Nodes should be deployed radially from the recording vehicle as described in detail in the chapters headed CAN Field Deployment (page 251) and MESH Field Deployment (page 255). As each CAN and Mesh Node is deployed and brought into operation it should appear on the CAN list in the UCI. At this point it is necessary to assess the quality of the backhaul wireless link using the Mesh Viewer. If required, the CAN may need to be relocated to improve the quality of the link. As the RAUs connect to the UCI, their status is displayed, including GPS lock status, battery status, geophone resistance. If any of these fall outside of acceptable limits, then the RAU in question should be visited and the problem corrected.
Deploy RAUs
The RAUs should be deployed at the receiver groups, powered up and brought into operation as described in detail in the chapter headed RAU Field Deployment (page 247). As the RAUs connect to the UCI, their status is displayed, including GPS lock status, WLAN signal strength, battery status, geophone resistance. If the WLAN signal strength is too low (<-80dBm) or GPS lock is not achieved or sporadic, then the RAU may need to be repositioned to improve it. Each RAU should have its ID number associated with the Stake ID at which it is placed using the Portable Field Terminal (PFT). This information should then be transferred to the UCI.
243
Field Equipment deployment Deployment procedure
Figure 9-2 PFT
See Portable Field Terminal user guide (page 161) in Users Manual Vol. 1.
244
Field Equipment deployment Autonomous Operation
Autonomous Operation
This section describes the recommended procedure for deploying a Unite System for Autonomous Operation. Unlike the Infrastructure Mode of operation, no network deployment is required for Autonomous Operation, therefore the deployment procedures are much simpler in comparison, however, more care must be taken to ensure that the equipment is working properly at the time of deployment as there is no real-time status monitoring in this mode. A suitable location should first be found for the recording vehicle. If VHF radio links are required for communicating with dynamite controllers or vibrators, then a suitable location may be central to the active part of the spread, preferably on high ground, but without overhead foliage or other obstructions such as power lines.
System Planning
As no infrastructure is required to be deployed, no system planning is necessary.
Pre-deployment configuration
Before the RAUs are deployed in the field, it is essential that they are connected to a computer running the UCI software to ensure that they are configured with the correct parameters for the survey. The UCI software runs on the e-Unite server. The Windows version of UCI software can be installed on a PC at a staging area. If both are used it is essential that they are set up with the same acquisition parameters. The following parameters must be set up before RAUs are connected to the UCI: Sample interval. Pre-amplifier gain. Working hours.
Field Equipment deployment Autonomous Operation
This also ensures that the RAUs are programmed with the latest firmware version available.
PC running UCI software
CAN RAU
Figure 9-3
For details, see RAU acquisition parameters (page 42) in Users Manual Vol. 1.
Field Equipment Deployment Procedure

Once the RAUs have been configured, they can be deployed in the field using the procedure described in RAU Field Deployment (page 247).
246
Field Equipment deployment RAU Field Deployment
RAU Field Deployment

The Remote Acquisition Unit contains the necessary electronics for GPS, WLAN and data acquisition. The unit can be powered from its internal battery with a power dongle attached to the battery port. An external battery normally powers the unit. The battery connector also has a power dongle configured to switch the RAU on. The external battery will charge the internal battery. There is a 30 second delay between disconnecting the external battery before the RAU switches off. This delay is deliberate to allow Hot Swapping of external batteries. The RAU can be forced to stay powered up by the connection of a dongle to the power connector. The main power connector also has pins for making a full ethernet wired connection to the RAU for the data harvester and maintenance. The top dome of the RAU casing contains the GPS and WLAN antennae. The RAU should be deployed in as clear a sight of the sky as possible, and away from local obstacles, which might obstruct GPS or WLAN signals. The RAU should also be set vertically upright to gain the maximum number of satellites as possible.
IMPORTANT
Please use the attached dust caps at all times when the equipment is not connected. This will keep the contacts clean and prolong the life of your equipment.
RAU Power connector
RAU Geophone connector
Figure 9-4 RAU connectors
247
Op LED (Operation and battery)
Comm LED (Comms and GPS status)
Figure 9-5 RAU Showing LEDs
Once power has been applied to the RAU, it will boot up and perform initial internal tests. Once booted, the GPS will start to acquire satellites. The RAU will enter Autonomous mode after one minute or after attaining GPS lock, whichever is the longer. On entering Autonomous mode the RAU will check the working hours against the GPS time and will either start acquiring and storing data or will go to sleep mode depending upon the working hours configuration. Normally the RAU will take just a few minutes from power on to attain GPS lock (warm start). However, if powered on for the first time in a new prospect area, or after a lengthy period of time on standby, (several days) additional time must be allowed for the RAU to download navigation data from the satellite network. Depending on the strength of signal and the particular RAU location, this could take some time, (up to 20 minutes in extreme cases). Once downloaded the RAU will store this information, and any subsequent power cycles will cause the RAU to warm start resulting in a faster time to lock. On the top of the RAU are two tri-coloured LEDs (red, amber and green). One LED (Op) is dedicated to displaying operational (go/no-go) and battery status, and the other (Comm) to communications (RSSI) and GPS status. Viewed from the front of the RAU (with the dome behind the LED windows), the Op is on the left
and the Comm is the right LED. The status is indicated by a combination of colour and blinking mode. Two blinking modes are used: Flashing: LED blinks on and off in a regular pattern about once a second. Heartbeat: LED is mostly off with a brief blink every 5 s. LED indications towards the top of Table 9-3 take precedence over the others. XXX indicates the state allows the lower states to use the LED.
Table 9-3 Dongle In
Condition Critical Low Battery Boot Loader Fails to Start Boot Loader Fails Critical Internal Failure (e.g. boot test fail) Low (or no external) battery + Sensor Resistance Pass Op LED OFF Amber Flashing Red Red Amber Comm LED OFF Amber OFF OFF XXX
Running correctly (e.g. booted) + Sensor Resistance Pass Heartbeat Green XXX Low (or no external) battery + Sensor Resistance Fail Flashing Amber XXX XXX Green Amber Red Flashing XXX Heartbeat XXX
Running correctly (e.g. booted) + Sensor Resistance Fail Flashing Green Good WLAN RSSI ( -78 dBm) or Ethernet link up Moderate WLAN RSSI (< -78 dBm) Poor WLAN RSSI (< -85 dBm) or No Infrastructure Connection (Autonomous ) No GPS Lock GPS Lock XXX XXX XXX XXX XXX
Note Any flashing colour on the right comm LED indicates No GPS
Lock, but the colour of the flashing LED indicates the RSSI condition.
249
In Autonomous mode, in normal operation, the Op Led will be hearbeat green and the Comm LED will be steady red, indicating operational, no wireless/LAN connection and GPS locked.
Table 9-4 Dongle Out/Asleep + External Power Present
Condition Internal Battery Charging Internal Battery Charge Cycle Stopped (Battery Full) Op LED Flashing Red Off Comm LED Flashing Red Green
Table 9-5 Dongle Out/Asleep + No External Power Present

Condition RAU Off Op LED Off Comm LED Off
250
Field Equipment deployment CAN Field Deployment
CAN Field Deployment

Equipment
The following equipment is required: CAN - part nr. VIB-999-0006 Battery ( 2 quantity) - customer supplied with cable assembly VIB350-0075 or part nr. VIB-400-0006 Three sector antenna - part nr. VIB-900-0019 Antenna cable set (3 quantity coaxial cable of 10m length combined into a single bundle) - part nr. VIB-350-0026BU Shelley clamp - part nr. VIB-850-0016 In-line RF amplifiers (3 quantity - optional) - part nr. VIB-800-0046C Antenna mast - part nr. VIB-900-0019 Fibre optic cable - part nr. VIB-999-0010
Assembly
IMPORTANT
Please read through all steps of the assembly procedure and referenced chapters before commencing assembly.
WARNING
Do not apply power to the CAN until all other assembly steps have been described, as damage to sensitive electronics components may occur.
Antenna
Normally, the Unite System is supplied with the antenna assembly fully assembled and mounted to the top section of the antenna mast, however the instructions for performing this assembly are included here for completeness.
The first step is to assemble the top section of the antenna mast. The Three sector CAN Antenna and (if required) the Mesh Node are attached to the top section of the antenna mast. The three sector antenna is attached as follows Start by loosening the jubilee clips at the top and bottom of the antenna assembly, then insert the mast section into the centre of the antenna assembly and push it through until flush with the top and then tighten the jubilee clips. Loosen the Shelly clamp sufficiently for it slide over the antenna mast section and slide it up to within about 3 - 4cm from the bottom of the three sector antenna assembly, then tighten the mast-mount part of the clamp. Before progressing further, familiarise yourself with the In-line RF Amplifier bundle. Each amplifer has an orientation mark indicating the antenna end of the amplifier. Loosen the outer fixings of the Shelley clamp and fit the In-line RF Amplifer bundle into the gap between the inner and outer clamps with the antenna end closest to the three sector antenna, then retighten the outer clamp. Screw the antenna connectors from the three sector antenna onto the antenna ends of the In-Line RF Amplifiers, noting the coloured banding on the coaxial cable leading to the antennas. Take the 10 m antenna cable set and take note of the coloured banding on each individual cable. Now screw each cable onto an In-Line RF Amplifier taking care to match the coloured banding on the coaxial cable with the coloured banding on the antenna cable attached to the antenna side of the amplifier. Please note that the N-type connectors used are easily cross-threaded. If this happens, a poor connection will be made resulting in reduced wireless performance. wireless backhaul 30 degree directional antenna is attached to the antenna mast by means of hose clips which fit around the mast
1The
1.
If a fibre optic backhaul is to be used in place of a Mesh wireless backhaul, this step can be omitted.
252
section to hold the metal mounting plates on the antenna. The antenna should be mounted below the Shelley clamp. Mesh Node comes with a mounting bracket which is attached to the antenna mast using two U-clamps. The bracket should be fitted to the antenna mast using the U-clamps before the Mesh Node is fitted by means of four bolts, and positioned close enough to the directional antenna that the antenna cable can reach from the antenna to the connector on the Mesh Node.
IMPORTANT
1The
It is important that the Mesh Node is mounted such that the directional antenna points in the same direction as the Red sector of the three sector CAN antenna. the Mesh power/data cable to the RJ45 connectors on the Mesh Node. Please see MESH Field Deployment on page 255 for important information on this.
2Connect
On completion, the antenna mast can be fully assembled as detailed in Antenna Mast Field Deployment on page 267.
IMPORTANT
When assembling the mast, it is important that the Red sector of the three-sector antenna is aligned on the same compass bearing as the Red sector on all other CAN antennas deployed. It is recommended that the Red sector is aligned to point to the next CAN upstream towards the recorder vehicle (the location of the Root Node for the Mesh)
1.
2.
If a fibre optic backhaul is to be used in place of a Mesh wireless backhaul, this step can be omitted. If a fibre optic backhaul is to be used in place of a Mesh wireless backhaul, this step can be omitted.
253
CAN
On completion of assembly of the antenna and antenna mast, connect the Antenna Cable Set to the coaxial antenna connectors on the CAN (see Figure 9-6), taking care to match the coloured banding on the coaxial cable with the coloured marker on the CAN. Take care to ensure that the N-type connectors are properly screwed on and not crossthreaded as this will considerably reduce wireless performance and may lead to equipment damage. If a Mesh wireless backhaul is used, connect the Mesh power/data cable to one of the 8-way data connectors on the CAN (see Figure 9-6). If a fibre-optic backhaul is used, connect the fibre to one of the 8-way data connectors on the CAN (see Figure 9-6).
Ethernet #4 RF #1 RF #2 Data connectors Ethernet #2 Ethernet #1 RF #3 Power (status) Ethernet #3 Power (power)
Data connectors
Power connectors
Antenna connectors
Figure 9-6 CAN Connectors
Once all other connections have been made, power can be applied by connecting batteries to one or both of the two power connectors.
254
Field Equipment deployment MESH Field Deployment
MESH Field Deployment

The Mesh backhaul is used to provide a wireless interconnection between the CANs and links the CANs to the central unit (UCI). Each CAN has a Mesh Node connected to it, and they are deployed at the same time as the CAN. Each Mesh Node is equipped with an omnidirectional Downstream antenna and a 30o directional Upstream antenna. Additionally, each Mesh Node has two RJ45 style connectors which are used to determine the function of the Mesh Node in the network hierarchy. The Mesh Node is normally mounted on the top section of the antenna mast also used to mount the CAN antenna. Each Unite Infrastructure network requires one Root Node, which is normally located at the UCI and connected to a CAN at the recorder vehicle. To configure a Mesh Node as the Root Node, cable VIB-3500100 is used to connect to the CAN. This cable simultaneously powers the Mesh Node and makes an ethernet connection to it through the Root Node connector - that is the connector furthest from the Downstream antenna. All other CANs in a Unite Infrastructure network are interconnected using Mesh Nodes configured as Relay Nodes. To configure a Mesh Node as a Relay Node, cable VIB-350-0100B is used to connect to the CAN. This cable has one connector, clearly marked with a red band, which provides power to the Mesh Node through the Root Node connector, and a second connector which makes an ethernet connection through the Relay Node connector - that is the connector closest to the Downstream antenna. To assist with the field deployment of the Mesh network, the Mesh Viewer application should be run on the UCI. This application graphically shows the Mesh Nodes as they connect to the network and provides metrics relating to the quality of the wireless connection such as wireless signal strength and data throughput. The following information is important to the deployment of the Mesh Network
Deployment is easiest if the Nodes are deployed radially from the Root Node The data connection hops from Relay Node to Relay Node, so the location of the each Mesh Node relative to the next one in the chain is important Because the Upstream antenna is directional, it is important to know the bearing of the next upstream (ie towards the Root Node) Relay Node. When a Relay Node is deployed it must be oriented such that the Upstream antenna is oriented on this bearing. The nominal line-of-sight wireless range of each hop is 1000m. The wireless range can be drastically reduced by vegetation such as trees. It is better to use an extra Relay Node to go around line-of-sight obstacles.
Deployment Procedure
The Mesh Nodes are deployed simultaneously with the CANs, however, the following steps specific to the Mesh deployment should be followed. 1. The Mesh Viewer application should be started on either the UCI or a computer connected by ethernet to a CAN, preferably the Root CAN (ie the CAN connected directly to the UCI). The Root Node, that is the Mesh Node connected directly to the Root CAN should be deployed and made operational. All the relevant parameters should be checked using the Mesh Viewer. The Relay Node physically closest to the Root Node should be deployed and brought into operation. Within a few minutes of being powered up, this Node should be visible on the Mesh Viewer. The Received Signal Strength should be checked, and a data throughput test performed. The maximum throughput possible is 22Mb/s, but perfectly adequate operation can be maintained at lower data rates depending on the number of recording channels deployed and the type of source. For impulsive operations, the lowest data throughput acceptable is 6Mb/S, while
2.
3.
256
for Vibroseis operations, it is not recommended to operate with lower than 11Mb/s throughput. 4. Continue deploying Relay Nodes radially from the recorder, and at each deployment check the RSSI (Received Signal Strength) and data throughput using the Mesh Viewer as above.
Mesh Viewer
Screen Layout
Figure 9-7 Mesh Viewer Screen
The Mesh Viewer Screen is composed of three interrelated information elements, marked in Figure 9-7 as A, B, and C. A The Network Screen The Network Screen is where both logical (topology view) and physical (map view) relationships between the nodes is shown. These two different view types are described later. Parent-child relationships are depicted by connecting lines. Node status updates
change LED and node icon channel values. B The Properties List All pertinent information for a selected node is available at a glance on the Properties List. This includes hardware information, MAC addresses, IP settings, AP information, etc. This information is refreshed with each new heartbeat update from each node. C Status Update Windows Dynamic information about the active network is posted in the Activity Window. Signal strength and transmit rates between nodes can be monitored here along with other information sent by nodes via periodic heartbeat updates. Note that the Activity Window contains 3 tabs: Heartbeat, Macro actions and Client/Station Activity. These are described next.
Figure 9-8 Activity Window tabs
Hearbeat tab A heartbeat is an information packet broadcast by each node in the network. The last received heart beat is highlighted (blue).
Figure 9-9
The Heartbeat tab in the Activity Window contains a list of all active nodes on the network (above). Information about each node is updated with each passing heartbeat from that node. The Time Stamp displays the date and time of the last heartbeat. The heartbeat may be temporarily changed to as low as 1 per
second this is particularly useful when antennas are being aligned for best reception. Restore the value to between 10-20 seconds after the alignment is completed. Adjusting heartbeat rate is described under Node Configuration. Note that the root node will not possess any such uplink information or parent information, since it has no parent node. Macro Actions The Macro Actions of the nodes are updated with heartbeats as well. Macro actions pertain to actions performed on a user-selectable group of nodes. Group Selections and Macro Actions are described later under Macro Actions..
Figure 9-10
Client Activity The Client Activity tab allows the user to view all client activity for each particular node. To select nodes to appear in the tab, go to the Tools tab and click on Show Station Activity.
Figure 9-11
Click on the desired nodes MAC ID, in the resulting pop up window. Then click on the + button to add the node to the STA Activity Enabled list. After selecting all nodes of interest, click Ok. The nodes will then appear under the Client Activity tab.
259
Figure 9-12
Note: The nodes may not appear immediately as the STA information packet is sent out with the Heartbeat Status update packet. Thus, if the Heartbeat Rate is set to 15 seconds, it may take up to 15 seconds for the nodes to appear under the Activity tab.
Note When finished viewing client activity, disable the nodes from
STA Activity List . This reduces needless traffic over the backhaul.
Viewing Node Status

By clicking on different elements of the Node Icon it is possible to access various items of status information for the Node.
Figure 9-13 Node Icon
1.
Double-click on any node icon to bring up the nodes information in the Properties Window (left of the Network screen). There will also be a check mark in the node icons message window indicating selection. Right-click on the node icons message window to change the display. Options for display are: node name, uplink transmit rate (Mbps), signal strength of parent downlink (dBm), board temperature, and node configuration (4350, 4455, etc). Setting the default description is described in a later section.
2.
260
3.
Hover the mouse over the LEDs on top of the Text Box. Tool tip text shown relates to the signal strength or transmit rate. This text is updated every heartbeat. How to change the data type and color of LED is described later. Hover the mouse over the blue boxes below the Text box. Tool tip text shown relates to the channel of a radio. This text is updated every heartbeat and will change based on which parents downlink the uplink radio connects to.
4.
Figure 9-14 Port Indicators
Along the bottom of the node icons are Port indicators. Each indicator represents a different wireless or wired link. Wireless links are labeled Wlan0, Wlan1, WLan2. Ethernet (wired) links are Ixp0 and Ixp1. and Note that the root node icons do not have a wlan1. Root nodes have a wired uplink connection to the Internet via ixp0 (left Ethernet port).
RF Information
To acces the RF Information for a Mesh Node, right-click on a node icon, and select RF Space Information from the Advanced Tools section.
261
Figure 9-15 RF Space Information
Then, click the Update button. It takes around 10 to 15 seconds for the information to be displayed. The Saturation column [1] shows the CSMA/CA normalized degree of activity for each channel. Using it one can determine the average burst TCP bandwidth available for use in the medium. In the shown example, for Channel 1 (2412 MHz), the available TCP burst bandwidth is [(10022.46) * 20]/100 = 15.50 Mbps, assuming the theoretical maximum for 802.11b/g to be 20 Mbps) The saturation column also shows the percentage of transmissions that needed to be retried. The Activity Map column [2] provides a visual description of each access points usage of the channel. The average and maximum sensed power levels are also reported using a Tool-tip.
Figure 9-16
262
IMPORTANT
When updating the RF space Information, the unit does not forward any packets from clients or other connected mesh units, therefore using the RF space information frequently is not recommended. Click the browse button [3] to get a view of the channel usage organised by network. This brings up a window showing signal, saturation and retry levels organised by network. Each downlink/Client AP radio has its own tab that is filled with information.
9
Figure 9-17
Configuring Mesh Nodes

To configure an individual node, right-click on the blue area (as opposed to the message window) of the node icon. From the options list, select Configure Node (right). This brings up the Node Configuration window. The Node Configuration window is where the majority of the network management takes place. Each white box represents a changeable property (Node Name, IP Address, etc.), whereas the grey boxes are read only.
263
Figure 9-18 Node Configuration Window
A The Node Name is a label for the node which will appear inside the node icons message window as well as in the Properties List B The Country Code determines the channels at which the node operates. Country Code should not be changed unless appropriate. C Preferred Parent is the upstream node of choice. This is used to force a preferred route only if required. D Heartbeat Interval is the rate at which nodes broadcasts its information to the NMS/other nodes. It may be temporarily changed to 1-2 seconds to help with antenna alignment/diagnostics. Normal range of 10-20 seconds is suggested. E Mobility Mode can be set to Stationary, Mobile Infrastructure or Mobile. For Units with the optional Scanner radio, the Mobile mode
uses the Deployment distance and Speed (F) to determine sampling intervals. On Unite Networks, only the Stationary Mode is required. F The Deployment distance and Speed are used by Mobile Infrastructure and Mobile modes to determine sampling intervals. This is not required on a Unite Network G Import and Export relates to data stored as a template. Templates are extractions exported from one node configuration that may be imported into a group of nodes, in order to reduce repetitive typing.
Performance Testing
Right-click on a node icon and select Performance Test from the Advanced Tools section.
9
Figure 9-19
The Performance Monitor window provides options for selecting TCP or UDP [1], the number of performance samples [2], the Bandwidth (for UDP) [3] and Type of Test (single-sided or dual) [4] Clicking on the Run Test button [4] starts the performance test. The results are displayed in the output button below the window.
265
Figure 9-20
The performance test uses the mesh unit as one endpoint and the PC running the Network Viewer as another, to measure the TCP/IP throughput between them. In the figures below, the solid blue lines show the throughput measurement path.
Figure 9-21
266
Field Equipment deployment Antenna Mast Field Deployment
Antenna Mast Field Deployment

This section describes the erection and dismantling of the TeleMast and equipment for use with the Unite System CAN and Mesh antennas. Vibtech recommend this type of mast for use with their equipment. The TeleMast system was specifically designed to allow for the rapid, safe, and successful deployment of tactical antenna arrays in the field, under all conditions. This extremely versatile mast is completely selfcontained, and requires no special training or tools for deployment. Vibtech reccomends that two people erect the mast and this can be performed in less than five minutes. The TeleMast can be deployed to heights from 8 to 40 feet (2.44 to 12 metres) and does not require support from vehicles, hard shelters, or other fixed structures. As standard, a 28 ft (8.5 m) TeleMast is supplied with the Unite System.
WARNING
Extreme care must be taken when erecting and dismantling any mast in case of contact with overhead power cables. Contact could result in serious injury or death.
267
Figure 9-22 Erection of CAN antenna
Figure 9-23 28 foot (8.5 metre) TeleMast kit
268
The kit consists of the following components Steel Tripod with Level. Steel Base Pole. 6 ea. Steel Center Mast Poles. 40' Guying Kit (40' Rope, 3-Point Guy Collar, 3 ea. Ground Stakes, 3 ea. Rope Stays). Steel Base Plate Kit (4 ea. Steel Base Plates). Staking Kit (1 ea. Hammer, 4 ea. Ground Stakes). Military Specification Nylon Carry Bag.
The complete 28 foot MobileMast kit weighs 62.7 pounds (28.5 kg).
Erecting the TeleMast

For ease of erection, the mast is best erected on a flat surface with the underlying ground able to have ground stakes driven in to safely secure the base plates and guy ropes. If a flat surface is not available, then the mast can be erected on an uneven surface and made level by adjusting the tripod legs. In both cases, the tripod must be level and that is achieved by monitoring the inbuilt bubble level. After unpacking the mast from the carry bag, first check that all the components are present. Attach the three base plates to the tripod legs, securing each with the attached hitch pin.
269
Figure 9-24 Tripod with base plates attached
The fourth base plate is attached to the mast centre pole. Open the tripod legs and make sure the base plates are flat on the ground. The lower collar must be fully pressed down to secure the tripod legs in position. Insert the first mast section from above into the upper collar and lower it down until it reaches the lower collar, then secure in the lower collar by tightening the lower collar handle.
Figure 9-25 Guy Collar
Place the guy rope collar onto the centre mast near to the top, but allowing room for the CAN antenna to be mounted on the uppermost part of the mast. Attach the guy ropes and the CAN 3-sector antenna assembly with its antenna cables attached.
Extend the tripod by releasing the turn knobs on the three legs and lift until the lower collar is approximately at chest level. Adjust the tripod legs until the tripod upper collar is level using the built in bubble level. Before staking the tripod it is important that it is as level as possible. If the tripod is not level, as the mast height increases, the leaning of the mast will become increasingly obvious and the range of the antenna will be severely reduced. The tripod needs to be raised high enough to allow the centre mast poles to be inserted through the lower collar. Once this is achieved the tripod can be secured by driving the stakes through the holes provided in each of the base plates. The ground stakes should be driven in at an angle towards the centre of the mast.
Figure 9-26 Correct staking of tripod
CAUTION
Be very careful when hammering stakes into the ground as there may be buried cables
IMPORTANT
Ground stakes must be used to secure any mast system which has to be erected over 12 feet (3.66 metres)
Insert each mast section through the bottom of the lower collar until the desired height of mast is achieved. As each mast section is inserted the turn handle on the lower collar can be used to secure the centre mast pole in place.
Figure 9-27 Inserting mast through lower collar
Allow enough room below the mast section in the collar to allow the next section to be inserted. Each mast section has a ball plunger at the top and can be adjusted by using a flat head screwdriver. This will reduce rotation of the mast sections. Once the desired height is achieved, the last section with the base plate attached is placed under the lower collar and clipped to the bottom of the mast. Release the clamp on the lower collar and the mast will rest onto the base plate. Now the stakes can be driven into the ground at the desired positions and the guy ropes attached.
Figure 9-28 Position the ground stakes
272
Figure 9-29 Attach guy ropes to stakes
Drive the stakes into the ground at an angle of approximately 45degrees angled away from the tripod and the guy rope ring is facing the tripod. For optimum stability, the guy ropes should be secured to the stakes at least 2/3 of the height of the mast away from the base of the tripod. eg. for a mast 28 feet high - approx. 18 feet from the tripod base.
WARNING
Do not overtighten the guy ropes. When guying the AntennaMast be sure not to over tighten the guy ropes. The objective of guying is to stabilize the center mast section, reduce masthead sway, and provide stability during wind loading. If the guy ropes are over tightened the downward load on the mast is increased and the overall load capacity of the mast is reduced and the AntennaMast can become unstable.
Figure 9-30 Adjust guy ropes
Using the attached guy rope hand clamp, (pictured above), tighten the guy rope by sliding the clamp towards the mast and away from the mast to loosen. When the reqired tension is achieved the rope is locked in
position by hooking the rope over the two hooks inside the clamp handle. Tension each guy rope until all are even and the mast is straight and perpendicular. You may need to adust each rope again until the mast is straight and the tension on each rope is evenly distributed.
How to dismantle the Antenna Mast

1. Slightly loosen the guy ropes and then loosen the turn knob and remove the base pole. Lifting slightly on the base pole allow enough space below to remove it from the mast. Tighten the turn knob so that the next pole remains in place. Remove the next mast section using the same process. Repeat the process for the remaining mast sections using the same procedure as above until all of the mast sections have been removed. Store the mast sections in the carry bag. Unclip the guy ropes from the ground stakes and wind them on to the rope stay until ready to unclip from the guy collar. Remove the ground stakes and store them along with the guy ropes in the carry bag. Remove the guy collar. Remove the ground stakes from the tripod and store them in the carry bag. Collapse the tripod and allow the nested legs to recess into the tripod legs. Fold the tripod and tighten the turn handle on the tripod legs. You may find it easier and quicker to store the tripod with the base plates attached. Store the tripod in the carry bag.
2. 3.
4.
5. 6. 7.
274
Field Equipment deployment Fibre Optic Cable Deployment
Fibre Optic Cable Deployment

The requirements for the backbone encompass physical and topological considerations as well as data throughput. The number of CANs used in the system and the separation between the CANs will be entirely flexible to allow different sizes of area to be surveyed. The UCI will connect to the backbone, via an ethernet cable, connected to any CAN2 port. The UCI can therefore be located anywhere in the survey area. During a survey, the CANs may be re-deployed to alter the area being observed. The backbone supports this change in topology. The fibre optic cable is field tactile constructed from a Polyurethane outer jacket with each fibre surrounded by aramid yarn. The cable has a tensile (tension) strength of 2000 N and crush resistance of 440 N/cm and is operational in temperatures from -55C to +85C.
WARNING
The minimum bend radius is six turns on a 10 x cable O/D mandrel which for the 2-core used is 5.5 cm or 11 cm diameter. To avoid damaging the cable or lowering system performance, the cable shouldn't be handled or deployed with a minimum bend (or kink) radius. The maximum range of a concatenated fibre optic backhaul cable (without splices) is 6 km. The recommended maximum number of splices per 500 m cable is three. The system optical power budget (worst case) is 9 dB. The cable loss is 1.5 dB/km and a splice adds a loss of 1 dB/splice. These figures can be used to determine a length and any splice combination limit, e.g. a 2km cable would have a loss of 3 dB and within this 2 km we could have a maximum of 6 splices giving another 6 x 1 dB of loss thereby totalling the 9 dB limit.
275
Fibre Optic Deployment (Two-Man)

The fibre is best deployed by firstly positioning and finalising the CAN positions. The fibre drum should be laid at the first CAN position and the cable deployed off the drum towards the second CAN position with the short pigtail end of the reel still securely attached to the drum outer case, since the drum will rotate during cable deployment, see Figure 931. A second field crew member, remaining with the drum, should ensure that the cable doesn't become tangled off the drum. Field crew should remain in radio contact at all times. The fibre should be deployed allowing sufficient slack in the cable in case it ever gets caught or dragged.
Figure 9-31 Fibre Optic Cable on Drum
WARNING
Care should be taken when handling the fibre optic connectors by ensuring that undue strain isn't applied between the connector and fibre cable. Never pull or deploy the cable off the drum using the connector, always handle the cable. Never deploy the cable with the cable taut over rough ground, shrubs, bush, trees, rocks, etc. Fibre deployed over roads and between vehicle access routes should have sufficient slack on both sides. Once deployed between the CANs, the fibre should be connected to the CANs
276
An alternative method is to connect the fibre off the main drum to the first CAN. The fibre reel can then be two man trailed to the second CAN ensuring that sufficient slack is maintained on the cable at all times to prevent undue strain being applied to the already connected first CAN end. Once deployed the cable can be connected to the second CAN creating an immediate network connection.
Fibre Optic Cable Retrieval

The fibre is retrieved by disconnecting the fibre connector from the remote CAN and walking the fibre back towards the drum carefully looping it in large loops. In large distance deployments a second field crew member may disconnect the short pigtail end of the drum from the first CAN and securely attach it to the drum outer case. The fibre can then also be reeled in (where location and terrain permits) ensuring that the cable doesn't become tight indicating a snag somewhere up the line. Once fully retrieved the fibre connector should be carefully attached to the drum using the magnetic clamp.
WARNING
Never retrieve the cable with the cable taut over rough ground, shrubs, bush, trees, rocks, etc. Always use the attached dust cap. This keeps all contacts clean and reduces wear and so prolongs the life of the equipment. Once retrieved ensure that both fibre connectors are suited attached to the drum to prevent damage during transit.
277
278
Chapter
10
Connectors and cables

In this chapter:
LCI-428 (page 280) FDU-428 input connector (page 285) Cables (page 286)
279
10
Connectors and cables LCI-428
LCI-428
BLASTER
LCI-428
BL CR0 BL CR1 BLEN1 S_FO BLEN1 S_FO1 BLEN1 CR0_B1 CR1_B1 FO_B1 FO1B1 FO2B1
BLASTER1
p S T M N
_EGOINB1
EXT_GO
Vcc
EGOIN1B1 5 to 12 V H J External
470 ohm _EGOINB2
From BLASTER 2
EGOIN2B1
GO
GND
BLEN1 S_TB_PLUGS
_TBINB1
Vcc
TBIN1B1
470 ohm _TBINB2
From BLASTER 2
TBIN2B1
TB
L
S_TB
S_TBOUT1
BLEN1 CLKO1B1 PILOT_CLK

PLL 17.9 MHz
CLKOUT17.9 CLKO2B1 TXB1 RXB1 BLEN1
A B C D
_RDYINB1
EXT_RDY RDYEN
Vcc RDYIN1B1 470 ohm RDYIN2B1

F G
From BLASTER 2
_RDYINB2
From BLASTER 2
Vcc
RDYENB2 RDYENB1
E
GNDB1
Jumper in cable
R
Figure 10-1 Blaster1 connector
280
LCI-428
BL CR0 BL CR1 BLEN2 S_FO BLEN2 S_FO2
BLEN2 CR0_B2 CR1_B2 FO_B2 FO1B2 FO2B2
BLASTER 2
p S T M N
To BLASTER 1
_EGOINB2
_EX_GO2
Vcc
EGOIN1B2 5 to 12 V H J External
470 ohm
EGOIN2B2
GO
GND
BLEN2
To BLASTER 1
_TBINB2
_ETBIN2
Vcc
TBIN1B2
470 ohm
TBIN2B2
TB
L
S_TB
S_TBOUT2
BLEN2 CLKO1B2 A B C D
From BLASTER 1
CLKOUT17.9 CLKO2B2 TXB2 RXB2 BLEN2
10
To BLASTER 1
_RDYINB2
_EXT_RDY1
Vcc RDYIN1B2 470 ohm RDYIN2B2

F G
To BLASTER 1
Vcc
RDYENB2 RDYENB2
E
GNDB2
Jumper in cable
R
Figure 10-2 Blaster2 connector
281
10
BLASTER signals
EGOIN1 External GO command (Signal). EGOIN2 External GO command (Ground). Used to trigger an acquisition cycle from an external device. Trigger current; Min.: 2 mA Max.: 50 mA A 470 resistor is in series connection with the optoisolator. The diagram below illustrates the case where the command is generated by a relay.
LCI-428
5 VDC
EGOIN EGOUT
External Go command
0 VDC
Figure 10-3
TBIN1 TBIN2
External TB (Signal) External TB (Ground) Time Break input, from a firing device. Used to synchronize the detonation with the recording system. Trigger current: Min.: 2 mA Max.: 50 mA A 470 resistor is in series connection with the optoisolator. Minimum pulse duration: 20 s.
282
FO1 FO2 External Firing Order. Relay contact closed by the Firing Order generated by the Unite. (pulse duration: 200 ms). Contact rating: 50 mA Max. Contact resistance: 100 max. See also Source controller interfacing (page 67) in Unite Users Manual Volume 3. Note: for Micro-seismic operations, pin T must be wired to pin K, and pin L wired to ground (pin R).
Serial port (TXB, RXB): 9600 Bd. 8 data bits. 1 Start bit. 1 Stop bit. No parity.
10
283
10
XDEV2
Pin Signal
GND CPS_1S GPS_CLK_P GPS_CLK_N CTS_RS232_OUT RTS_RS232_IN TX_RS232 RX_RS232 READY_IN1 READY_IN2 FO_OUT1 FO_OUT2 TB_IN1 TB_IN2 AUX_OUT1 AUX_OUT2
A B N C P D E F R M
L K S J H G
Viewed from wiring side
A B C D E F G H J K L M N P R S
284
Connectors and cables FDU-428 input connector
FDU-428 input connector

The female (hollow) pin is the positive terminal.
+ Figure 10-4
+ -
Applying a positive voltage to the positive terminal, with respect to the negative terminal, results in a positive sample in the SEGD file and an upward signal on the camera record. Auxiliary channel differential input voltage: Linear operation: 2.26 V max. with G1600 (0 dB) gain; 565 mV max. with G400 (12 dB) gain. Maximum allowable (safe but clamped): 5 V regardless of gain. Destructive: 10 V regardless of gain. See also Utilities (Trace sign inversion) in Unite Users Manual Vol. 3.
10
285
10
Connectors and cables Cables
Cables
SGD-S Blaster Controller to LCI-428
1 2 3 4 5 6 7 8 9 KCK2 plug Analog Uphole +-500 mV to SYSTEM plug of Controller SGD-SP D TxD RxD ExtGo GND AngUH ConfTB GND TB FO Shield 1 2 3 4 5 6 7 8 9 10 M N LCI-428 BLASTER port K L R C H J Cannon DB9 (not used)
See also Source controller interfacing (page 67) in Unite Users Manual Volume 3.
286
ShotPro to LCI-428
2 k
UH
D B
500
2 k
+
200
Auxiliary channels
TB GND
J K
K L
FO
E F
M N
GND TxD RxD
R P N
R D C
10
Shot Pro Blaster connector
LCI-428 BLASTER port
287
10
ShotPro I to LCI-428
110 k
+
36
Auxiliary channel
TB GND
J N
K L
FO
w K
M N
GND TxD L
R D
Shot Pro I Blaster connector
288
Macha to LCI-428
UH
C D
+ Auxiliary channels
RFTB Macha System connector START
E F
+ -
G H
H J K L
TB GND Macha Control connector
A B
FO
A F
M N
GND Macha Data connector TxD
B A C D
R D C
10
289
10
BoomBox to LCI-428
2 k
UH
30
100
2 k
+
200
Auxiliary channels
TB GND
16 20
K L
FO
10
R TxD RxD 8 9 BoomBox Blaster connector D C
290
Index
A B C D E F GH I J K L M N OP QR S T U V W X Y Z
Index
IM = Installation Manual U1 = Users Manual Vol. 1 U2 = Users Manual Vol. 2 U3 = Users Manual Vol. 3
type, VE464 U1: 494
Numerics
3592 cartridge dirve IM: 206
A
Abort
button, Operation U1: 309 Plot U1: 562
Absolute
spread U1: 276 Spread, tests U1: 283
Accelerated
weight drop U1: 219 Acceptance tests U3: 91 Acquisition Error description (SEGD) U2: 23 graphic view, normal U1: 526 index, process type U1: 315 Length (SEGD) U2: 20 local U1: 522 Nb U2: 152 normal U1: 525 Number (SEGD) U2: 23 numeric view, normal U1: 529 type, Process type U1: 315
Acquisition type tables (SEGD) U2: 22 Action (see Shortcuts) Activity window U1: 239 Add button U1: 26 to query U1: 437 Additional blocks (SEGD general header) U2: 14 effects U1: 432 Address 428XL local network IM: 38 Client computer IM: 119 FUJI 3x90, changing IM: 196 FUJI 3x90, displaying IM: 197 Intranet IM: 75 LCI card U1: 216 LTO, changing IM: 202 MAC U1: 220 Administration server U1: 193 Advance II U3: 70 Advanced connection parameters U1: 189 process type U1: 314 Again Plot U1: 562 AGC plotter U1: 572 Air gun (SPS) U2: 68, U2: 116 pressure psi (SPS) U2: 82, U2: 132 Alarm Positioning U1: 427 Alert system U1: 427 Alias filter
Frequency at - 3dB point (SEGD)
U2: 19
Slope (SEGD) U2: 19 Angle from skew (SPS) U2: 64, U2: 76, U2: 112, U2: 126 Antenna deployment IM: 265
291
Index
Height U2: 156 channels, Comments U1: 273 channels, deployment IM: 53 channels, Gain U1: 272 channels, Instrument tests U1: 284 trace scaling U1: 574 trace, description U1: 319
Apply
All, Survey setup U1: 262 button U1: 27 Sensor, Survey setup U1: 262
APS
File format U2: 149
Average
distortion U2: 150, U2: 152 force U2: 150, U2: 152 ground stiffness U2: 150, U2: 152 ground viscosity U2: 150, U2: 152 phase U2: 150, U2: 152
Archiving
configuring U1: 221 system status U1: 208
Array
disk IM: 186 Forming (SEGD) U2: 19
AWD U1: 219
Arrays, sub, number of U2: 82, U2: 132 Assembly Location (SEGD) U2: 33 Serial number (SEGD) U2: 33 Type (SEGD) U2: 33 Authorization granting U1: 194 Auto Corr Peak Time U1: 318 Export U1: 446 Level, vib drive U1: 516 Lift, VE464 U1: 496 noise editing U1: 350 Auto/Manual noise editing threshold U1: 350 VE464 U1: 508 Autocorrelation peak time (SEGD) U2: 23 Automation Continuous, shooting U1: 336 Discontinuous, shooting U1: 336 Manual, shooting U1: 337 shooting U1: 336 Aux Channel contents (SPS) U2: 65, U2: 78, U2: 113, U2: 128 Line U1: 271 Process Descriptor U1: 319 Traces, number of U2: 20 Auxiliary channel, description U1: 271 channels U1: 271
292
B
Backup
setup U1: 236
Backward
playback U1: 457 Base scan interval (SEGD) U2: 15 Basic sweep signal (Acquisition type)
U1: 495 Basic Type

LOG, dB/Hz U1: 480 LOG, dB/octave U1: 483 Setup U1: 477 Taper U1: 478 Tn U1: 484
Baud
rate, TDMA (VE464) U1: 500
Bearing
source line U1: 506
Beginner U1: 201 Blaster Advance II U3: 70

connector, LCI-428 IM: 278, IM: 279 controllers U1: 353 id (SEGD) U2: 21 MACHA U3: 77 SGDS U3: 78 Shallow Sequencer U3: 75 Shot Pro U3: 71 signals IM: 280 status (SEGD) U2: 21
Index
type U1: 219 button (mouse) U1: 253
Blasters
interfacing U3: 67
Change
button U1: 26
Blocking trace U1: 450 Blocks in General Trailer U2: 16 BoomBox U1: 219 wiring IM: 288 Break Point U1: 329 Browser settings U1: 190 Buffer U1: 216 Build feature query U1: 436 Button U1: 19 Bypass file exports U1: 447 Bytes per scan (SEGD) U2: 14
Changing LCI U1: 214 Channel

auxiliary, description U1: 271 data error overscaling (SEGD) U2: 35 edited status (SEGD) U2: 36 filter (SEGD) U2: 35 filter response U3: 25 gain control method (SEGD) U2: 18 gain scale (SEGD) U2: 35 increment (SPS) U2: 70, U2: 87, U2: 119, U2: 137 number (SEGD) U2: 33 process (SEGD) U2: 36 sample to mV conversion factor (SEGD)
U2: 36
Set End Time (SEGD) U2: 18 Set Number (SEGD) U2: 27 set number (SEGD) U2: 18 Set Starting Time (SEGD) U2: 18 set, number of channels in U2: 18 sets per record U1: 234, U2: 15 TDMA (VE464) U1: 500 type (SEGD) U2: 34 type id (SEGD) U2: 36 Type Identification (SEGD) U2: 18 type, Log shooting setup U1: 551 Channels, number of (SPS) U2: 65, U2: 77, U2: 113, U2: 127
C
Cable
BoomBox IM: 288 Macha IM: 287 path U1: 257 SGD-S Blaster IM: 284 ShotPro IM: 285, IM: 286
Callisto
user guide U1: 581
Camp
distance to, alarm U1: 430
CAN
deployment IM: 235, IM: 249
Charge
Depth U2: 81, U2: 131 Length U2: 81, U2: 131
Capacitance
error (SEGD) U2: 32 high limit (SEGD) U2: 32 low limit (SEGD) U2: 32 value (SEGD) U2: 32
Cartridge
insertion U1: 467
Cartridge drive
Shock-mount parts IM: 194 Cartridge drive. See Tape drive Centre
Checkerboard view U1: 255 Circular bearing of H256 (SPS) U2: 64, U2: 75, U2: 112, U2: 126 Click U1: 19 right, Line window U1: 254 Client installing IM: 103 main window U1: 201 SPS U2: 63, U2: 73, U2: 111,
293
Index
U2: 123 Clipping
method (noise elimination) U1: 377 noise editing type U1: 348 plotter U1: 577
Control
type (SPS) U2: 67, U2: 81, U2: 115,
U2: 131
unit serial number (SEGD) U2: 35 unit type (SEGD) U2: 35
Clock
time w.r.t. GMT (SPS) U2: 63, U2: 73, U2: 111, U2: 124
Conversion
sample to mV U2: 36
Converting
coordinates U1: 438 samples to mV U3: 87
Cluster U1: 342 CMRR

Instrument test U1: 286
Code
Producer U1: 234
COG
Easting U2: 156 elevation U2: 156 file U2: 156 Northing U2: 156 radius threshold U1: 399 source position (estimated) U1: 420 status U2: 156 to source deviation U2: 156
Comments
Auxiliary channels U1: 273 observer, setup U1: 352 SEGD U2: 25 setup, Operation window U1: 332
Common
Mode Rejection U1: 286
Communications
protocol, source controllers U3: 67
Compound
basic sweep signal U1: 491
Computation Domain U2: 153 Connection crew Web site U1: 209 opening a session U1: 188 Connectors Blaster1 IM: 278 Blaster2 IM: 279 FDU Input IM: 283 Continuity test limit U1: 267 Continuous shooting U1: 336
294
Coord. status final/prov (SPS) U2: 68, U2: 82, U2: 116, U2: 132 Coordinate location (SPS) U2: 63, U2: 73, U2: 111, U2: 123 Coordinates converting U1: 438 Copy and Paste U1: 29 function (Export window) U1: 458 tape, file U3: 12 Copying files to tape U1: 465 CopyMedia U3: 12 Copyrights U1: 227 Correction rate, DGPS U1: 499 Correlation After Stack, process type U1: 325 After stack, theory of U1: 379, U1: 381 Before Stack, process type U1: 323 data distribution U1: 386 Frequency domain U3: 84 more about U1: 384 pilot, choosing U1: 317 Time domain U3: 84 Correlator, noise supp (SPS) U2: 67, U2: 81, U2: 115, U2: 131 Create selection U1: 437 Crew name U1: 230 name, Comment (SPS) U2: 65, U2: 77, U2: 113, U2: 127 number U1: 474
Index
setup U1: 230 vibrators U1: 474 type, setup U1: 395
Crossline
spacing, AGC U1: 574
Crosstalk
Instrument test U1: 285
Custom
basic sweep signal U1: 486 sweep, loading to VE464 DPG U1: 518
Customer
support U1: 227
Cut off
error (SEGD) U2: 32 high limits (SEGD) U2: 32 low limit (SEGD) U2: 32 value (SEGD) U2: 32
Cygwin IM: 123
D
Damp coeff, natural freq. (SPS) U2: 66, U2: 114 Damping coeff, natural freq (SPS) U2: 79, U2: 129 Data Bypass U1: 447 computation domain, vib QC U1: 503 harvester IM: 21 record sorting order (SPS) U2: 60, U2: 108 Data Harverster connecting U1: 180 disconnecting U1: 180 harvesting U1: 182 status U1: 184 uploading data U1: 183 Data Harvester user guide U1: 177 Data harvester software, installing IM: 133, IM: 169 Date of survey (SPS) U2: 63, U2: 72, U2: 111, U2: 122 SEGD U2: 23 Datum U1: 439
Datum Type setup Datum U1: 439 Ellipsoid U1: 439 Geoid U1: 439 Day of Year U2: 153 of year (SPS) U2: 69, U2: 85, U2: 117, U2: 135 Dead seis traces, number of U2: 20 Deboost basic sweep signal U1: 492 Default Channel type, Log U1: 551 Delay at end of Acq. U1: 344 at end of VP U1: 344 basic sweep signal U1: 490 lift up U1: 517 no-move alarm U1: 430 refraction, process type U1: 315 setup, Operation window U1: 344 speed alarm U1: 431 Delete button U1: 27 Deployment antenna IM: 265 CAN IM: 249 Fibre optic cable IM: 273 RAU IM: 245 deployment IM: 235 Depth charge U2: 81, U2: 131 towing U2: 82, U2: 132 Descale Multiplier (SEGD) U2: 18 Description absolute spread U1: 276 Auxiliary channels U1: 271
Channels (Aux), Instrument tests
U1: 284
Channels (tests) U1: 283 Generic Line U1: 278 Generic spread U1: 279 of grid units (SPS) U2: 63, U2: 74, U2: 111, U2: 125
295
Index
of survey area (SPS) U2: 63, U2: 72, U2: 111, U2: 122 Receiver section U1: 264 Survey U1: 263 high U1: 516 low U1: 516 tape, install U1: 221
Desktop U1: 191 Detect end of tape U1: 467 Deviation, COG to source U2: 156 Dialog box U1: 19 Digital pilot, additional U1: 496 pilot, choosing U1: 495 pilot, correlation U1: 317 Discontinuous shooting U1: 336 Disk array IM: 186 buffer U1: 216 record, setup U1: 235 space, monitoring U1: 468 Display Traces per inch U1: 577 Distance no-move alarm U1: 430 Distortion U2: 150, U2: 152 Instrument test U1: 285 Sensor test U1: 289 Diversity enhanced (theory of) U1: 381 stack U1: 346 stack (theory of) U1: 379 Double-click U1: 19 Download from crew Web site U1: 210 setup (firmware) U1: 296 DPG number of U1: 219 Slave U1: 475 Drag U1: 19 Drag and drop base camp U1: 414 recording unit U1: 414 source (Positioning) U1: 416 Drive level U2: 150, U2: 152
296
Drive. See Tape drive Driver

graphic, Linux Linux graphic driver IM: 114
DSD
Get U1: 512 network U1: 475 Network, Navigation U1: 356 setting U1: 511 status, get U1: 499
Dump
Output button U1: 316 to SQC U1: 335
Dump stacking fold (SEGD) U2: 23 Duplicating, tape, file U3: 12
E
Easting, COG U2: 156 Editing Noise U1: 346
number of windows (noise) U1: 348 Spike U1: 376 system parameters (Log) U1: 543 type (noise) U1: 348 Zeroing Length (noise) U1: 348 Zeroing Taper Length (noise) U1: 348
Effect
speed alert U1: 432
Elevation
antenna height U2: 156 COG U2: 156 reference U1: 398
Ellipsoid U1: 439 Ellipsoidal model U1: 398 Emergency alarm U1: 427 Enable instruments U1: 215 Enabled
Index
export U1: 437 header (SEGD) U2: 25 header blocks (SEGD) U2: 16 header length (SEGD) U2: 15 label U1: 449 tape label U1: 235
End
colour map scale U1: 434 of media U1: 454 of tape, detecting U1: 467
EOF U1: 453 EOM U1: 454 eSQC Pro IM: 24 Estimated source COG U1: 420 e-Unite software licence U1: 217 Event log viewer U1: 557 Excitation Overload U2: 153 Expanded file number (SEGD) U2: 16, U2: 17 Explosive source type setup U1: 339 Explosive (SPS) U2: 68, U2: 116 Exponent, subscans U2: 18 Exponential basic sweep signal U1: 484 time, plotter U1: 573 Export Auto/Manual U1: 446 client window U1: 441 enabled U1: 437 Exports configuring U1: 221 Extended channel set number (SEGD) U2: 19, U2: 27
Channel Sets/Scan Types (SEGD)
F
Factor to metre (SPS) U2: 63, U2: 75, U2: 111, U2: 125 FDU INPUT connector IM: 283 Input polarity IM: 283 unit type (SEGD) U2: 33 Feature property names U1: 434 Fibre optic cable deployment IM: 273 Field computer system(s) (SPS) U2: 63, U2: 73, U2: 111, U2: 123 electronics, upgrading U1: 296 on/off U1: 248 record increment (SPS) U2: 70, U2: 87, U2: 119, U2: 137 record number (SPS) U2: 70, U2: 87, U2: 119, U2: 137 tape number (SPS) U2: 70, U2: 87, U2: 119, U2: 137 update mode U1: 287 field equipment IM: 235 Field Units (see Instruments) File count (SEGD) U2: 23 duplicating U3: 12 Header block (SEGD) U2: 14 Load/Save U1: 561 number (SEGD) U2: 14, U2: 27 number, recording U1: 237 packager U1: 208 Files per tape U1: 450 per tape (SEGD) U2: 23 Filter alias Hz, dB pnt, slope (SPS) U2: 65, U2: 77, U2: 113, U2: 127
297
U2: 16
file number (SEGD) U2: 27 header (SEGD) U2: 20 header blocks (SEGD) U2: 16 header flag (SEGD) U2: 19 header length (SEGD) U2: 15 QC, vib U1: 503 receiver line number (SEGD) U2: 28 receiver point number (SEGD) U2: 29 Record Length (SEGD) U2: 16
External
Index
low Hz, dB pnt, slope (SPS) U2: 65, U2: 78, U2: 113, U2: 128 notch Hz, -3 dB points (SPS) U2: 65, Transform U3: 84
Frequency
domain U3: 84 Nyquist U1: 231
U2: 113
notch Hz, -3dB points (SPS) U2: 78,
U2: 128 playback U2: 159 response, channel U3: 25 servo control U1: 515 type U1: 231 type (SEGD) U2: 23 Filters plotter U1: 575 Firing Order (FO), process type U1: 314 Firmware updating U1: 296 First Notch Frequency (SEGD) U2: 19 Timing Word (SEGD) U2: 27 waypoint U1: 403 Fleet Ready U1: 342 vibrator, APS format U2: 150, U2: 152 vibrator, crew U1: 475 Floppy disk specifications (SPS) U2: 60, U2: 61, U2: 108, U2: 109 Force U2: 150, U2: 152 Overload U2: 153 Format APS U2: 149 code (SEGD) U2: 14 SEGD U2: 11 SEGD, Rev 2.1 U2: 39 Source controllers U3: 67 SPS, initial U2: 55 SPS, Rev. 2.1 U2: 101 SPS-like U2: 149 synthetic file U2: 47 version num. (SPS) U2: 63, U2: 72, U2: 111, U2: 122 Forward playback U1: 457 Fourier
298
From channel (SPS) U2: 70, U2: 87, U2: 119, U2: 137 From receiver (SPS) U2: 70, U2: 88, U2: 119, U2: 138 FTP server U1: 221 server setup U1: 452 server, installing on PC IM: 227 FUJI 3x90 address, changing IM: 196 address, displaying IM: 197 Functions Test U1: 281 VE464 U1: 508
G
Gain
Auxiliary channels U1: 272 code U1: 276 code, absolute spread U1: 276 error, Instrument test U1: 286 Instrument tests U1: 284 shooting setup, Log U1: 550
Gap U1: 264 General

Header block 1 (SEGD) U2: 14 Header block 2 (SEGD) U2: 16 Header block 3 (SEGD) U2: 17 Header Block Number (SEGD) U2: 16,
U2: 17
Trailer blocks, number of U2: 16
Generate
report U1: 437
Generic
spread U1: 278 spread, description U1: 279
Geodetic datum
parameters (SPS) U2: 63, U2: 74, U2: 111, U2: 124 spheroid (SPS) U2: 63, U2: 74,
Index
U2: 111, U2: 124 Geographic AGC U1: 573 Geographic (see Topographic) Geoid U1: 439 Geoidal model U1: 398 Geophysical contractor (SPS) U2: 63, U2: 73, U2: 111, U2: 123 Geozone alarm U1: 428 Get DSD U1: 512 DSD status U1: 499 Getting started U1: 187 Global rendering, plotter U1: 577 Go starting a shot U1: 308 to waypoint U1: 374 Topographic view U1: 249, U1: 251 GPS correcting Stake ID errors U1: 108
differential corrections, VE464 TDMA
Guest
privileges U1: 195
Guidance
overview U1: 373 vibrator, enabling U1: 335
H
Hardware
installing IM: 37, U1: 49
U1: 499
time management U1: 232
Grabbing VP U1: 400 Graphic

driver, Linux IM: 114 view, normal acquisition U1: 526 view, Positioning window U1: 404
Graphic view (see Topographic) Graphics how to select U1: 29 Gravity test U1: 286 Grid coord. at origin (SPS) U2: 64, U2: 75, U2: 112, U2: 125 origin (SPS) U2: 64, U2: 75, U2: 112, U2: 125 Ground stiffness U2: 150, U2: 152 viscosity U2: 150, U2: 152
Harvester IM: 21 Harvesting U1: 182 HDOP U2: 153 Header external, size U1: 234 Header record description (SPS) U2: 72, U2: 122 specification (SPS) U2: 62, U2: 110 Height, antenna U2: 156 Help language U1: 190 send, emergeny alarm U1: 428 Hide layer (Positioning) U1: 408 High drive level U1: 516 Line, sync U1: 496 High-cut filter, plotter U1: 575 playback filter U2: 160 Histogram view U1: 261 Historic editing type (SEGD) U2: 22 range (SEGD) U2: 22 taper length (SEGD) U2: 22 threshold Init value (SEGD) U2: 22 zeroing length (SEGD) U2: 22 Historical Noise Editing U1: 346 History Line window U1: 260 Hold/Var U1: 350 Hot Line U1: 227
299
Index
Hour of day (SEGD) U2: 14 Instrument
Code (I) tables (SPS) U2: 65, U2: 113 Code (SPS) U2: 70, U2: 87, U2: 119,
I
Icon U1: 20 ID vibrator U1: 475 Identity card U1: 228 Identity Card U1: 209 Impulse Sensor test U1: 288 Impulsive process type U1: 321 Stack process type U1: 322 Increment Marker U1: 271 Shot U1: 339 VP to do U1: 341 Index box U1: 20 Source Point U1: 304 Init Thresh U1: 350 Inline spacing, AGC U1: 574 Input servo control loop U1: 515 Inserting cartridge U1: 467 Install window U1: 214 Installing Client software IM: 103, IM: 111 Data Harvester software IM: 133, IM: 169 Ethernet plotter IM: 180 FTP server on PC IM: 227 hardware IM: 37, U1: 49 patch (client) IM: 129 patch (server) IM: 95 Redhat, server IM: 60, IM: 70 server software IM: 63 UCI, Windows IM: 173 Vehicle tracking box IM: 234
300
U2: 137
Crosstalk U1: 285 Distortion U1: 285 Gain error U1: 286 Noise U1: 285 Phase error U1: 286 Pulse test U1: 286 tests U1: 284
Instruments Colour U1: 251 Show/hide U1: 251 Interfacing source controller U3: 67 Internal time break (SEGD) U2: 22 Interpolation U1: 578 Intranet address, configuring IM: 75 IP address 428XL local network IM: 38 Client computer IM: 119 Intranet IM: 75
J
Julian
day, backup setup U1: 236 Julian day (SEGD) U2: 14
L
Lab
distance to, alarm U1: 430
Label
external U1: 449 properties U1: 433 tape, external U1: 235
Landscape plotter U1: 576 Language help U1: 190 Last

record, playback U1: 456
Index
Lat. Long
initial line (SPS) U2: 64, U2: 75, U2: 112, U2: 126 scale factor (SPS) U2: 64, U2: 75, U2: 112, U2: 125
Lat. of standard parallel(s) (SPS) U2: 63, U2: 75, U2: 111, U2: 125 Latitude reference, vibrator guidance U1: 335 Launcher bar, customizing U1: 200 icons U1: 199 Layer rename (Positioning) U1: 408 show/hide (Positioning) U1: 408 Layout setup U1: 269 LCI address U1: 216 changing U1: 214 Leakage error (SEGD) U2: 32 limit (SEGD) U2: 32 Sensor test U1: 287 Test limit U1: 268 value (SEGD) U2: 32 Length record (SEGD) U2: 23 record, process type U1: 314 time, plotter U1: 578 Zeroing (noise) U1: 348 Zeroing Taper (noise) U1: 348 Level auto, vib drive U1: 516 Licence code, entering U1: 217 information about U1: 197 Plotter U1: 217 Lift up delay U1: 517 Limits (see Test limits) Line Generic U1: 278 name U2: 150, U2: 152 name (SPS) U2: 69, U2: 70, U2: 83,
U2: 87, U2: 88, U2: 117, U2: 119, U2: 133, U2: 137, U2: 138 name, COG U2: 156 number U1: 263 number format (SPS) U2: 64, U2: 76, U2: 112, U2: 126 sequence number, SPS U2: 111, U2: 123 skipping U1: 279 splitting U1: 271 Linear basic sweep signal U1: 479 Phase U1: 231, U1: 232 phase filter U3: 26 Link examples IM: 55 List box U1: 20 Listening time U1: 314 Live seis traces, number of U2: 20 Load Thresh U1: 350 Loading Custom sweep (VE464 DPG) U1: 518 system parameters U1: 544 Local acquisition U1: 522 disk U1: 216 ellipsoidal model U1: 398 network IM: 32 user U1: 189 LOG dB/Hz U1: 480 dB/octave U1: 483 Log files, compressing IM: 100 Log in connecting to server U1: 188 installing server software IM: 64 name U1: 190 Long. of central meridian (SPS) U2: 64, U2: 75, U2: 112, U2: 125 Look
301
Index
sensors U1: 249, U1: 251 increment U1: 271
Look&Feel U1: 192 Loop servo control U1: 515 Low drive level U1: 516 stacks, number of U2: 36 Trace U1: 349
Trace Percentage (SEGD) U2: 22 Trace Value U1: 349 Trace Value (SEGD) U2: 22
Mass
overload U2: 153 warning U2: 152
Max
of max, Aux (SEGD) U2: 23 of max, Seis (SEGD) U2: 23 speed U1: 431 speed, scale U1: 402
Low-cut
Filter frequency (SEGD) U2: 19 Filter slope (SEGD) U2: 19 filter, plotter U1: 575 Playback filter U2: 160
LTO address, changing IM: 202
M
MAC address U1: 220 MACHA U3: 77 Macha wiring IM: 287 Macha blaster U1: 219 Management sessions U1: 196 time U1: 232 Manual Export U1: 446 noise editing U1: 350 scale, Line window U1: 261 shooting U1: 337 Manual/Auto noise editing threshold U1: 350 VE464 U1: 508 Manufacturers code (SEGD) U2: 14 serial nb (SEGD) U2: 14 Map grid easting (SPS) U2: 69, U2: 84, U2: 117, U2: 134 northing (SPS) U2: 69, U2: 84, U2: 117, U2: 134 Marker
302
MDR IM: 231 Media copy U3: 12 Micro-seismic enabling U1: 335 Min High Drive U1: 517 Low Drive U1: 516 Minimum Phase U1: 232 phase filter U3: 46 Minute of day (SEGD) U2: 14 Mode display, plotter U1: 577 operating U1: 335 Model ellipsoidal U1: 398 geoidal U1: 398 Monitoring disk space U1: 468 Mounting parts IM: 43 Mouse Buttons U1: 20 buttons U1: 20 Centre button U1: 253 Move alarm U1: 430 MRU U1: 222 Multi-component recording (SPS) U2: 65, U2: 78, U2: 113, U2: 128 Multiple swath U1: 330 tests U1: 289 Multi-screen IM: 114
Index
Mute
channel U1: 274 Instrument test U1: 285 Sensor test U1: 288 Test limit U1: 267
N
Name
crew U1: 230 feature, colour map U1: 434 Log in U1: 190 plotter U1: 220 property, query builder U1: 436 user U1: 209
Noisy
stacks, number of U2: 36 Trace % U1: 349 trace percentage (SEGD) U2: 22 Nominal towing depth U2: 82, U2: 132
Normal
acquisition U1: 525
NAS IM: 24
archiving system U1: 221 Rescue mode IM: 224
NAS system IM: 212 connecting IM: 214

IP address on user network IM: 217 reinstalling IM: 221 shock-mount parts IM: 213 user network IM: 220
Normalization plotter U1: 573 Northing, COG U2: 156 Notch U1: 575 frequency (SEGD) U2: 19 playback filter U2: 160 Number of Auxes (SEGD) U2: 20
blocks of General Trailer (SEGD)
U2: 16
channel sets per record (SEGD) U2: 15 channels (SPS) U2: 65, U2: 77, U2: 113, U2: 127 channels in this channel set (SEGD)
Navigation option U1: 357 shooting mode U1: 356 Network DSD U1: 475 DSD, Navigation U1: 356 Networking 428XL local network IM: 38 Client computer IM: 119 Next Plot U1: 562 record, playback U1: 457 NFS disk setup U1: 451 server U1: 221 No move U1: 430 reply U1: 429 No. sub arrays, nom depth (SPS) U2: 82, U2: 132 Noise Editing U1: 346 editing, setup U1: 345 elimination type (SEGD) U2: 22
U2: 18
dead Seis traces (SEGD) U2: 20 DPG modules U1: 219 live Seis traces (SEGD) U2: 20 plotters U1: 220 sample skew 32 byte extensions (SEGD)
U2: 15
samples in trace (SEGD) U2: 20 samples per trace U2: 26 samples per trace (SEGD) U2: 28 Seis traces (SEGD) U2: 20 stacks low (SEGD) U2: 36 stacks noisy (SEGD) U2: 36 subscans exponent (SEGD) U2: 18 traces (SEGD) U2: 20 vibrators in pattern U1: 504 windows (SEGD) U2: 22 windows, noise editing U1: 348
Numeric
pilot, additional U1: 496 pilot, choosing U1: 495 pilot, correlation U1: 317
303
Index
view, Line window U1: 259 view, normal acquisition,VE464
Parameters
loading (Log) U1: 543 saving (Log) U1: 543 system, editing U1: 543
U1: 529 Nunits, len, width (SPS) U2: 66, U2: 67, U2: 79, U2: 80, U2: 114, U2: 115, U2: 129, U2: 130 Nyquist U1: 231
Password
expiry date U1: 194 opening a session U1: 190
O
Observer
comments, setup U1: 352 privileges U1: 195
Off
Line U1: 239
Paste U1: 29 Patch client IM: 129 server IM: 95 Path colour U1: 257 Pattern
number, creating U1: 504 orientation U1: 505 setup U1: 504 vibrator, choosing U1: 332
Offset
removing U3: 89 to coord. location (SPS) U2: 63, U2: 73, U2: 111, U2: 123
Peak
distortion U2: 150, U2: 152 force U2: 150, U2: 152 phase U2: 150, U2: 152
On
Line U1: 239
Open
session U1: 188
Operating mode U1: 335 Operation table U1: 304 Option button U1: 20 Options Navigation U1: 357 Slip-sweep U1: 335, U1: 365 Orientation pattern U1: 505 plotter page U1: 576 Output Dump U1: 316 stack U1: 316 Xdump U1: 316 Overload U2: 153
P
Page
setup, plotter U1: 576
304
Peg (see Topographic stake) Peripherals Install setup U1: 219 Permission U1: 195 PFT IM: 22 Phase U2: 150, U2: 152 angle (SEGD) U2: 17 Control (SEGD) U2: 17 error (Instrument test) U1: 286 Linear U1: 231, U1: 232 Minimum U1: 232 Pilot digital, additional U1: 496 digital, choosing U1: 495 digital, correlation U1: 317 Pilot length (SEGD) U2: 23 Plate Warning U2: 152 Playback filters U2: 159 record U1: 455 Plot U1: 576 abort U1: 562 Again U1: 562
Index
Next U1: 562 contractor (SPS) U2: 63, U2: 73, U2: 111, U2: 123 layers U1: 393
Plotter
AGC U1: 572 ethernet, installing IM: 180 general IM: 24 licence U1: 217 mode, display U1: 577 name U1: 220 number of U1: 220 processing U1: 572 scaling U1: 574 type U1: 220
Plug
process type, FO U1: 314
Point
Number (Marker) U1: 270
Point (to) U1: 21 Point Code

FDU channels U1: 265 SPS U2: 69, U2: 83, U2: 117,
U2: 133 Point Depth (SPS) U2: 69, U2: 83, U2: 117, U2: 133 Point Index U2: 150, U2: 152, U2: 156 SPS U2: 69, U2: 70, U2: 83, U2: 87, U2: 117, U2: 119, U2: 133, U2: 137 Point number U2: 150, U2: 152 COG U2: 156 SPS U2: 69, U2: 70, U2: 83, U2: 87, U2: 117, U2: 119, U2: 133, U2: 137 Point record description (SPS) U2: 83, U2: 133 specification (SPS) U2: 69, U2: 117 Polarity FDU input IM: 283 SEGD U2: 15 Portable field terminal (PFT) IM: 22 Portrait plotter U1: 576 Pos. proc. contractor (SPS) U2: 63, U2: 73, U2: 111, U2: 123 Positioning
Post-plot date of issue (SPS) U2: 63, U2: 72, U2: 111, U2: 122 P-P bar/m,prim/bubble (SPS) U2: 82, U2: 132 Pressure sensor, enabling U1: 523 Pressure Overload U2: 153 Prestack within field units (SEGD) U2: 22 Preview colour mapped attributes U1: 434 Printer IM: 24 Privileges U1: 195 Process Type setup, generating U1: 328 type, Log shooting setup U1: 551 type, overview U1: 313 Type, SEGD U2: 22 Type, setup U1: 332 Processing Crossline spacing, plotter U1: 574 filter, plotter U1: 575 Geographic AGC, plotter U1: 573 Inline spacing, plotter U1: 574 Normalization, plotter U1: 573 plotter U1: 572 Time, exponential U1: 573 Window length (AGC) U1: 573 Wz velocity, plotter U1: 573 Producer code U1: 234 Project code and description (SPS) U2: 64, U2: 76, U2: 112, U2: 126 Projection U1: 439 type (SPS) U2: 63, U2: 74, U2: 111, U2: 124 type, setup U1: 397 zone (SPS) U2: 63, U2: 74, U2: 111, U2: 125 Projection Type setup Projection U1: 439 Properties
305
Index
in graphic view, Line U1: 254 object label U1: 433
Random
basic sweep signal U1: 485 Lift up delay U1: 517
Property
name, query builder U1: 436
Rate
refresh U1: 205 sample U1: 231
Protocol
source controllers U3: 67
Pseudorandom
basic sweep signal U1: 485
RAU
deployment IM: 235, IM: 245
Pulse
basic sweep signal U1: 489 Instrument test U1: 286
Raw
Impulsive Stack process type U1: 322 process type, Correlation U1: 324 servo control U1: 516 Vib Stack process type U1: 326
Q
QC
choice, vib U1: 503 data (How to view) U1: 254 extended, vib U1: 503 limits, vib U1: 502
Ready
fleet U1: 342
Reboot
server U1: 198
Receiver
code (Rx) tables (SPS) U2: 66,
Quadrant bearing of H256 (SPS) U2: 64, U2: 76, U2: 112, U2: 126 Quality COG radius threshold U1: 399 Control IM: 24 Vib position accuracy U1: 401 warning setup U1: 399 Quality Control check records (SPS) U2: 68, U2: 116 Query add to U1: 437 builder U1: 436
U2: 114
index (SPS) U2: 70, U2: 88, U2: 119,
U2: 138
line number (SEGD) U2: 28 point easting (SEGD) U2: 30 point elevation (SEGD) U2: 30 point index (SEGD) U2: 28 point northing (SEGD) U2: 30 point number (SEGD) U2: 28 point, skipping U1: 279 section U1: 264
Record
disk, setup U1: 235 identification U2: 150, U2: 152 identification (SPS) U2: 69, U2: 70, U2: 117, U2: 119 identification, COG U2: 156 Instrument tests U1: 282 last, playback U1: 456 length (SEGD) U2: 23 length, Intrument tests U1: 285 length, process type U1: 314 next, playback U1: 457 type (SEGD) U2: 15
R
R,S,X file quality control (SPS) U2: 68, U2: 116 Radio management, vib U1: 498 Radius alarm, distance to camp U1: 430
alarm, distance to recording unit
U1: 430
shooting setup, Log U1: 551
RAID
disk array IM: 186
306
Record length SEGD U2: 15

Index
Redhat
installing, server IM: 60, IM: 70 Wireline telemetry U1: 240
Reverse
button U1: 27
Reference
latitude, vibrator guidance U1: 335
Reversed
Marking option U1: 271
Refraction
delay, process type U1: 315 delay, SEGD U2: 21
Revision
SEGD U1: 233 Revision Number (SEGD) U2: 16 Rewind tape U1: 454 Right click, Line window U1: 254 Role U1: 195 RVT300 IM: 231
Refresh
rate U1: 205
Registering user U1: 194 Relation record

description (SPS) U2: 87, U2: 137 specification (SPS) U2: 70, U2: 119
Release
tape drive U1: 454
Remote
network IM: 33, IM: 34, IM: 35 user U1: 189 user, installing IM: 111
S
Sample
conversion to mV U3: 87 int. Record Len. (SPS) U2: 65,
Rename
layers (Positioning) U1: 408
U2: 113
int., Record Length (SPS) U2: 77,
Rendering
global, plotter U1: 577 setup, plotter U1: 576
U2: 127 Rate U1: 231

skew extensions, number of U2: 15 skew, SEGD U2: 27 to mV conversion factor U2: 36
Reply
alarm U1: 429
Report
generate, query U1: 437
Repository U1: 216 Rescue NAS system IM: 224 Reset button U1: 27
queries and classification U1: 435
Sample Rate SEGD U2: 20 Samples

in trace, number of U2: 20 per trace, number of U2: 26, U2: 28
Save
Thresh U1: 351
Saving
system parameters U1: 544
Resistance
error (SEGD) U2: 31 high limit (SEGD) U2: 31 low limit (SEGD) U2: 31 Sensor test U1: 287 value (SEGD) U2: 31
Scalability
installation settings U1: 223
Scale
factor (SPS) U2: 64, U2: 75, U2: 112,
U2: 125
histograms U1: 261
Response, Channel filter U3: 25 Restart server U1: 198 Retrieval

Scaling
plotter U1: 574 Scan Type
307
Index
Header (SEGD) U2: 18 Number (SEGD) U2: 27 per record (SEGD) U2: 15 Resistance test U1: 287 Seismonitor U1: 290 sensitivity (SEGD) U2: 34 show/hide U1: 249 test limits U1: 266 tests U1: 287 Tilt model U1: 288 Tilt test U1: 288
Scrollbar U1: 21 Second

Notch Frequency (SEGD) U2: 19 of minute (SEGD) U2: 14
SEGD
Code U1: 267 format U2: 11 format, Rev 2.1 U2: 39 revision, choosing U1: 233 setup U1: 233 Trace Blocking U1: 450
Sensor Type
FDU channels U1: 266 Number (sensor tests) U2: 30 SEGD code U2: 29
Sequence
Line, SPS U2: 111, U2: 123
Seis traces, number of U2: 20 Seismic datum (SPS) U2: 69, U2: 84, U2: 117, U2: 134
instrument header records (SPS) U2: 77, U2: 127 receiver header records (SPS) U2: 79,
Sequencer
Shallow U3: 75
Sequential
time, plotter U1: 577 trace, plotter U1: 577
Serial
number, tape U1: 235
U2: 129
setup, Operation U1: 335 source header records (SPS) U2: 80,
Server
administration U1: 193 FTP U1: 221 log on to U1: 188 NFS U1: 221 software, installing IM: 63 start/stop U1: 198
U2: 130
trace scaling U1: 574
Seismonitor
Sensor test U1: 290
Select U1: 21 Selecting

graphical objects U1: 29 in graphic view U1: 253 table cells U1: 28 text U1: 28 traces to plot U1: 569
Servo
input U1: 515 setting U1: 515
Session
manager U1: 196 opening U1: 188
Set
channel, number per record U1: 234 DSD U1: 511 Servo U1: 515
Selection
create U1: 437
Senior
Observer, privileges U1: 195
Sensor
Coulour code U1: 249 Distortion test U1: 289 Impulse test U1: 288 Leakage test U1: 287 Noise test U1: 288
308
Sets, channel U2: 15 Settings browser U1: 190 help U1: 190 Setup Crew, vibrators U1: 474 Observer comments U1: 352
Index
SFL
Spread First Line U1: 331
SFN
Spread First Number U1: 331
SGD-S
Blaster cable IM: 284
SGDS U3: 78 Shallow

Sequencer U3: 75
Shock
mount parts IM: 43
Shock-mount
Cartridge drive IM: 194 NAS system IM: 213
Shooter U1: 353 Shooting U1: 353

Navigation mode U1: 356 setup, Log U1: 550 system U1: 219 systems, interfacing U3: 67
Shortcut
Line window U1: 255
Shot
automation U1: 336 Depth, charge len. (SPS) U2: 68,
U2: 116
depth, charge len. (SPS) U2: 81,
U2: 131 Id U1: 329

Id, Log shooting setup U1: 551 increment U1: 339 Nb U2: 152 number (SEGD) U2: 20 starting U1: 308
ShotPro
install U1: 219 interfacing U3: 71 wiring IM: 285, IM: 286
Show
layer (Positioning) U1: 408
Shutdown
server U1: 198
Size
external header U1: 234 vert. stk fold (SPS) U2: 67, U2: 115
Size, vert. stk fold (SPS) U2: 80, U2: 130 Skew, sample, number of extensions U2: 15 Skipping lines (spread description) U1: 279 receiver points U1: 279 Slave 428XL U3: 68 DPG U1: 475 Slip time U1: 365 time, selecting U1: 344 Slip-sweep U1: 365 enable U1: 335 mode used (SEGD) U2: 23 Snaking U1: 271 Software e-Unite, licence U1: 217 patch (client) IM: 129 patch (server) IM: 95 updating U1: 296 version (SEGD) U2: 23 Software, installing server IM: 63 Soil, drill method (SPS) U2: 68, U2: 81, U2: 116, U2: 131 Source aux nb (SEGD) U2: 23 code (Sx) tables (SPS) U2: 67, U2: 115 COG file U2: 156 easting (SEGD) U2: 23 elevation (SEGD) U2: 23 Explosive U1: 339 Line U1: 330 line bearing U1: 506 Line Number (SEGD) U2: 17 northing (SEGD) U2: 23 Point Index U1: 304 Point Index (SEGD) U2: 17 Point Number (SEGD) U2: 17 point setup, generating U1: 334 point, setup U1: 329 Receiver U1: 330 Set Number (SEGD) U2: 17
309
Index
type, setup U1: 338 updating U1: 111
Spacing
crossline (AGC) U1: 574 inline (AGC) U1: 574
Standard
process type U1: 314
Start
colour map scale U1: 434 time, plotter U1: 578
Speed
alarm U1: 432 maximum U1: 431 maximum, scale U1: 402
Starting
e-Unite server U1: 198
Spike
editing U1: 376
Split
line U1: 271
Spread
absolute U1: 276 generic U1: 278 number (SEGD) U2: 20 setup U1: 275 SFL U1: 331 SFN U1: 331 Superspread U1: 332 Superspread, Line window U1: 277 type U1: 331 type (SEGD) U2: 21
SPS
Rev. 2.1 U2: 101 Sercel (over 10000 traces) U2: 98
SPS-like file format U2: 149 SQC dump to U1: 335 Stack
Correlation after, process type U1: 325 Correlation before, process type
U1: 323 distance U1: 505

Impulsive, process type U1: 322 Output button U1: 316 Vibroseismic, process type U1: 326
Stacking Fold U2: 153 SEGD U2: 22 Stacks, number of Low U2: 36 Noisy U2: 36 Stake (see Topographic stake) Stake ID U1: 107
correcting with GPS position U1: 108
310
Static correction (SPS) U2: 69, U2: 83, U2: 117, U2: 133 Statistics VE464 U1: 533 Status codes U1: 531 DSD, get U1: 499 Step negative U1: 361 Vibroseismic source U1: 341 Stiffness (ground) U2: 150, U2: 152 Stop button, Operation U1: 308 Stopping e-Unite server U1: 198 Storage disk array IM: 186 Streamer cable number (SEGD) U2: 19 Subarrays, number of U2: 82, U2: 132 Subscan exponent U2: 18 Superspread U1: 332 Line window U1: 277 Support customer U1: 227 Surface elevation, reference U1: 398 elevation, SPS U2: 69, U2: 117 Surface elevation SPS U2: 84, U2: 134 Survey description U1: 263 setup U1: 262 Swath backup setup U1: 236 first line (SEGD) U2: 20 first number (SEGD) U2: 20 Id U1: 330
Index
multiple U1: 330 name U1: 237 type U1: 237 type, format, density (SPS) U2: 65, U2: 77, U2: 113, U2: 127 Tape/disk identifier (SPS) U2: 63, U2: 72, U2: 111, U2: 122
Sweep
basic signal (Acquisition type) U1: 495 freq start, end (SPS) U2: 67, U2: 115 frequency start,end (SPS) U2: 81,
Taper U1: 478

length start, end (SPS) U2: 67, U2: 81, U2: 115, U2: 131
U2: 131
length (SEGD) U2: 23 slip time U1: 365 slip, enable U1: 335 type, length (SPS) U2: 67, U2: 81, U2: 115, U2: 131
TB
window, process type U1: 315 window, SEGD U2: 20
Sync
high line U1: 496
Syntax (see Description) Synthetic file format U2: 47 file syntax U1: 292 Signal type U1: 292 System shooting U1: 219 tools, troubleshooting IM: 100
Tb to T0 time (SEGD) U2: 22 TDMA Baud rate U1: 500 channel U1: 500 VE464 U1: 498 Terminal Linux IM: 100 Test acceptance U3: 91 functions U1: 281
limit Continuity U1: 267 Leakage U1: 268 Noise U1: 267 Sensor U1: 266 Tilt U1: 267 multiple U1: 289 Record, type (SEGD) U2: 20 setup U1: 281 shortcut (Topographic view) U1: 249,
T
Table
how to select U1: 28 operation U1: 304
Tape
copy U3: 12 drive IM: 23 drive address 3592 IM: 206 FUJI 3x90, changing IM: 196 FUJI 3x90, displaying IM: 197 LTO IM: 202 drive, install U1: 221 drives, supported IM: 195 Label U1: 449 label (SEGD) U2: 23 label, external U1: 235 Number U1: 449 number of files U1: 450 number, SEGD U2: 23 setup, Export window U1: 449
U1: 251
Spread U1: 283
Text
box U1: 21 how to select U1: 28
Third Notch Frequency (SEGD) U2: 19 Threshold COG radius U1: 399 Hold/Var (SEGD) U2: 22 Init U1: 350 Init Value, noise editing U1: 349 Load U1: 350 Save U1: 351 type tables (SEGD) U2: 22 updating (noise elimination) U1: 377
311
Index
Tilt
correction, enable U1: 215 error (SEGD) U2: 31 limit (SEGD) U2: 31 Model U1: 288 test U1: 288 Test limit U1: 267 value (SEGD) U2: 31 Noisy percentage U1: 349 Number (SEGD) U2: 27 number of samples in U2: 20 selecting, plot U1: 569 Sequential, plotter U1: 577
Trace Header
Extension (SEGD) U2: 27 Extension Block 1 (SEGD) U2: 28 Extension block 2 (SEGD) U2: 30 Extension block 3 (SEGD) U2: 31 Extension block 4 (SEGD) U2: 32 Extension block 5 (SEGD) U2: 32 Extension block 6 (SEGD) U2: 33 Extension block 7 (SEGD) U2: 35 Extensions (SEGD) U2: 19, U2: 28 SEGD U2: 27
Time U2: 153

delay, FTB-SOD (SPS) U2: 65, U2: 78, U2: 113, U2: 128 domain, correlation U3: 84 exponential, plotter U1: 573 Interpolation U1: 578 Length, plotter U1: 578 listening U1: 314 management U1: 232 Sequential, plotter U1: 577 SPS U2: 69, U2: 85, U2: 117,
Traceability
field equipment U1: 258
Traces
per inch U1: 577 total number of U2: 20
U2: 135
Start, plotter U1: 578
Time break SEGD U2: 21

window, SEGD U2: 27
Tn U1: 484
basic sweep signal U1: 484 To channel (SPS) U2: 70, U2: 87, U2: 119, U2: 137 To receiver (SPS) U2: 70, U2: 88, U2: 119, U2: 138
Toggle
button U1: 21
Tools
USB key management IM: 100
Topographic stake U1: 249 view U1: 246 Total number of traces (SEGD) U2: 20 Towing depth U2: 82, U2: 132 Trace auxiliary, description U1: 319 blocking U1: 450 data block U2: 26 edit (SEGD) U2: 27 Low U1: 349
312
Traces, number of Aux U2: 20 Dead seis U2: 20 Live seis U2: 20 Seismic U2: 20 Tracking box, installing IM: 234 Positioning window U1: 417 VE464 U1: 501 vehicle setup U1: 402 Trailer, general U2: 16 Transmission troubleshooting U1: 257 Troubleshooting tools, system IM: 100 Transmission U1: 257 Type blaster U1: 219 Model, Polarity (SPS) U2: 65, U2: 66, U2: 67, U2: 77, U2: 79, U2: 80, U2: 113, U2: 114, U2: 115, U2: 127, U2: 129, U2: 130 of process (SEGD) U2: 22 of source (SEGD) U2: 20 plotter U1: 220
Index
A B C D E F GH I J K L M N OP QR S T U V W X Y Z U
UCI
installing, Windows IM: 173
Values
query builder U1: 437 Valve Overload U2: 153 Var/Hold U1: 350 VE432 Version U2: 153 VE464 functions U1: 508 Vehicle Tracking box IM: 234 Velocity plotter U1: 573 Vertical datum description (SPS) U2: 63, U2: 74, U2: 111, U2: 124 Stack (SEGD) U2: 19
Uninstalling
patch (client) IM: 129 patch (server) IM: 95
Unit
serial number (SEGD) U2: 33 type (SEGD) U2: 33
Units
how to select U1: 253 spacing X, Y (SPS) U2: 66, U2: 67, U2: 79, U2: 80, U2: 114, U2: 115, U2: 129, U2: 130
Unload
tape U1: 454
Unselect
in Line topographic view U1: 253
Vib
position accuracy U1: 401 position Easting U2: 150, U2: 152 position elevation U2: 150, U2: 152 position Northing U2: 150, U2: 152 Status Code U2: 152
Update
field U1: 287 vib fleet U1: 511
Updating
firmware U1: 296 stake ID U1: 111
Vibrator
drive level (APS) U2: 150, U2: 152 fleet (APS) U2: 150, U2: 152 guidance U1: 373 guidance, enabling U1: 335 number (APS) U2: 150, U2: 152 pattern setup U1: 504 QC choice U1: 503 QC limits U1: 502 Radio management U1: 498 type U1: 219 type (SEGD) U2: 17 Vibroseis (SPS) U2: 67, U2: 115
Upgrading
field electronics U1: 296
Uphole
time (SEGD) U2: 21 time (SPS) U2: 69, U2: 84, U2: 117,
U2: 134 Upload U1: 210 URL

opening a session U1: 189
USB
key IM: 100
View
Graphic (normal acquisition) U1: 526 Histogram U1: 261 Numeric (normal acquisition) U1: 529 numeric, Line window U1: 259 topographic, line U1: 246 Viscosity (ground) U2: 150, U2: 152
User
info U1: 233 local IM: 32 name U1: 209 registering U1: 194 remote IM: 33, IM: 34, IM: 35
VP
V
VA (plotter) U1: 577
grabbing radius U1: 400 Id U1: 329

313
Index
to do, increment U1: 341
VSR
enable U1: 335
W
Water
depth (SPS) U2: 69, U2: 84, U2: 117,
U2: 134
gun (SPS) U2: 68, U2: 116
Waypoint first U1: 403 Weathering thickness (SPS) U2: 68, U2: 81, U2: 116, U2: 131 Wiggle U1: 577 Window Length, AGC U1: 573 Number of (noise) U1: 348 TB U2: 20 TB, process type U1: 315 Wz Velocity, AGC U1: 573
X
Xdump
Output button U1: 316
Y
Year (SEGD) U2: 14
Z
Zeroing
Length (noise) U1: 348 method (noise elimination) U1: 377 noise editing type U1: 348 Taper Length (noise) U1: 348
Zoom
Line window U1: 253
314

En Unite Inst

Hochgeladen von

Dokumentinformationen

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

En Unite Inst

Hochgeladen von

Copyright:

Verfügbare Formate

UNITE

V2.1 Installation Manual

Ref. No. 0311475

Ahead of the Curve

UNITE Installation Manual

UNITE Installation Manual

Chapters or pages affected

Description of revision or reason for change

Software Licence Agreement

II. PROPRIETARY RIGHTS

Software Licence Agreement

IV. PATENTS AND COPYRIGHTS

UNITE Installation Manual August 2, 2010

Wireless system operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .27

IT topology information for Unite recorder deployment . . . . . . . . .33

Auxiliary channels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .55 FDU-428 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .56

CAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .58 LCD display anchoring. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .59

Server software installation

e-Unite server software. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .65

Two-machine Infill Unite configuration . . . . . . . . . . . . . . . . . . . .86

User account . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .111

Installing Client software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .113 Screen management on Linux client. . . . . . . . . . . . . . . . . . . . . . . .116

Setting the computers IP address. . . . . . . . . . . . . . . . . . . . . . . . . .121

Reinstalling the Nomad firmware. . . . . . . . . . . . . . . . . . . . . . . . . .144 Nomad device setttings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .149

Configuring Wireless Networking . . . . . . . . . . . . . . . . . . . . . .155 Generate System Information Snapshot . . . . . . . . . . . . . . . . .158

Install software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .160

Data Harvester software

Windows UCI software

Infortrend S16F-R1430 RAID system . . . . . . . . . . . . . . . . . . . . . .188

Tape drives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .196

NAS server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .214

FTP server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .229

Field Equipment deployment

Deployment procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .243

MESH Field Deployment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .255

Antenna Mast Field Deployment . . . . . . . . . . . . . . . . . . . . . . . . . .267

Fibre Optic Cable Deployment. . . . . . . . . . . . . . . . . . . . . . . . . . . .275

10 Connectors and cables

FDU-428 input connector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .285 Cables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .286

UNITE Installation Manual August 2, 2010

UNITE Installation Manual August 2, 2010

UNITE Installation Manual August 2, 2010

Introduction About the Unite documentation

About the Unite documentation

UNITE Installation Manual August 2, 2010

Introduction The Unite system

The Unite system

Full-Wireless Unite configuration

Introduction The Unite system

Autonomous-mode RAU (stores data locally)

GPS time Data Harvester

Complete shots UCI GPS receiver LCI-428 acquisition unit

Shot descriptor files

SEGD files (NAS)

5.8 GHz 2.4 GHz Infrastructure-mode RAU (real-time acquisition)

Figure 1-1 Full-Wireless Unite configuration

UNITE Installation Manual August 2, 2010

Introduction The Unite system

Shot Descriptor Files 2

6 5 Stacking Correlation SEGD finalization Completed Files

Figure 1-2 e-Unite server (e-428 + UCI software)

UNITE Installation Manual August 2, 2010

Introduction The Unite system

Infill Unite configuration