Western Coastal and Marine Geology

Two Levels of YoNav - Server & Client

[ Home | Staff | Marfac Software | Software Downloads | YoNav Documentation | Contents ]

YoNav Software Documentation:
   Features | Quick Start | Installing | Connecting External Devices | Start YoNav Server | Configure Devices
   Troubleshooting | Create a New Survey | YoNav Data Formats


YoNav Server

The Server manages the hardware issues of the cruise. It deals with serial port considerations, GPS receivers, etc. The Server implements survey line computations, Kalman filtering, geodetic datum manipulation and map projection software. It also does the entire data recording function. The Server can run as a stand-alone application with a minimal user interface that will log all sensors configured.

screen capture of yonav server seismic version


YoNav Client

The Client manages the graphical map display, survey line selection, generation and editing.

YoNav Server is the main interface between the navigation sensors and the computer. YoNav Client is the interface between you and the YoNav Server. The YoNav Client can only run after the YoNav Server has been started; it can not run without a server. (The YoNav Client automatically launches the Server when it starts; you do not need to start the Server separately.)

The YoNav Client receives all of its data from the YoNav Server and the user. The YoNav Client allows the user to set the scale, background map settings and certain preferences regarding how the real-time map behaves.

screen capture of yonav client showing ship track lines with navigation


The NavSock DLL

When any YoNav Server dependent application is started, the sockets services are required. To facilitate the sockets services, YoNav 2.x and later the NavSock DLL is invoked to provide the connection between the client application and the YoNav server.

screen capture showing yonav server sockets connection

The YoNav server may be launched locally if it is on the same machine as the YoNav client application, or it may be lauched by providing the IP address or the machine name on which the server is currently running. To ensure a successful connection, be sure that the machine names and IP addresses are up to date in the HOSTS file. The HOSTS file is located in \winnt\system32\drivers\etc. A sample hosts file is listed below.

# Copyright (c) 1993-1995 Microsoft Corp.
#
# This is a sample HOSTS file used by Microsoft TCP/IP for Windows NT.
#
# This file contains the mappings of IP addresses to host names. Each
# entry should be kept on an individual line. The IP address should
# be placed in the first column followed by the corresponding host name.
# The IP address and the host name should be separated by at least one
# space.
#
# Additionally, comments (such as these) may be inserted on individual
# lines or following the machine name denoted by a '#' symbol.
#
# For example:
#
# 102.54.94.97 rhino.acme.com # source server
# 38.25.63.10 x.acme.com # x client host

xxx.xxx.xxx.xxx localhost
xxx.xxx.xxx.xxx MARFACxxx
xxx.xxx.xxx.xxx MARFACxxx


Information listed by topic  Information listed by location Information listed by project title Home Search

U.S. Department of the Interior    U.S. Geological Survey    Western Coastal & Marine Geology
URL: http://walrus.wr.usgs.gov/marfac/TwoLevel.html
for more information, contact John Gann
maintained by Laura Zink Torresan
Last updated 7 November 2006 (lzt)