Depth, Heading & HPR SHARED MEMORY HYPACK ® SURVEY HYSWEEP® SURVEY Network: Position & Time Sync Network: Multibeam Data Network: Heading & HPR POS/MV Inertial System Seabat 7125 ZDA and 1 PPS Time Sync HYPACK does NOT require 1PPS 6 You can improve your time synchronization from +/- 10mSec to +/- 1mSec by using a HYPACK 1PPS Box. POS/MV (UTC), Seabat (UTC), Single beam on a COM port (No time sent). If you have a device that sends datagrams with UTC time stamps, then the answer is: Yes Examples of when time synch to UTC is required: GPS (UTC), Seabat (UTC), TSS DMS/05 (No time sent), Gyro (No time sent). Without it, data will not be good MB MB MB MRU MRU MRU MRU POS POS + time Asynchronous data are correlated with time tags. All devices must use the same time base – UTC time or PC time. Network and COM inputs Time Tagging Very Important. Exception is GPS ($GPGGA has a UTC time tag). Typically, Motion and Heading messages do not contain time tags. Serial RS-232: For lower data volume like GPS. Interfacing Bringing in the data Network: For high volume data like multibeam. Time HYPACK SURVEY HYSWEEP SURVEY POS, TIDE DRAFT MRU, HDG, Nadir Depth MRU MB GYRO HDG HPR MBĤ Asynchronous data are correlated with time tags. HYSWEEP® Configuring a Multibeam System Multibeam sonar Motion sensor Heading sensor GPS (via HYPACK hardware) Tide (via HYPACK Hardware) Dynamic Draft (via HYPACK Hardware) SV: Sensor and/or Profile Also: Scanning Laser For Topographic Surveyģ GPS Pos HYPACK SURVEY HYSWEEP SURVEY MRU MB GYRO HDG HPR MB
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |