SeaNet
capabilities
key features



Key SeaNet Communications Node Features:
  • BatchFile Transfers via DataPipes: Transfer large files to shore for processing and have them transferred back to the ship in the most cost-effective manner. Older Inmarsat units transfer data at roughly 9600 bits per second as compared to SeaNet’s newer technology, which operates at 64,000 bits per second (actual throughput may vary). Large files such as side-scan sonar data, satellite imagery, scientific plots, and video clips are easily transferred to destination computers on the Internet.

    SeaNet Scenario: Meteorological sensors are installed on several SeaNet-equipped ships. Sensor data are collected by shipboard data-logging software designed by shipboard scientists. In addition to providing access to shipboard scientists, the software is modified so that it places one-minute data subsamples for each sensor in a directory on the shipboard computer. Each time the SeaNet link is brought up, the files in the directory holding the meteorological data, which has been configured as a SeaNet DataPipe, are compressed into a single file and sent across the link to shore. The shipboard files are deleted once it is verified that the shore-side node has received them. Shore-side software processes the data immediately and makes it available on the scientific team’s shoreside web site.

  • Interactive Internet Capability: SeaNet systems can transparently connect one or more shipboard computers directly to the Internet. The computer responds as if it were on a 64,000 bits per second link on shore. SeaNet-supported cruises have used this capability for web-browser sessions, ftp transfers of vendor-supplied software updates, and data-center queries, among others. The only difference noticed by users is the associated per minute satellite communication costs.

    SeaNet Scenario: A sophisticated oceanographic instrument package is designed for deployment from a winch on a conducting cable. It is also equipped with an ethernet port for on-deck data download, diagnostics, and reprogramming. The package malfunctions, and the diagnostics are not making sense. The shipboard technician connects the instrument to the ship’s LAN via an ethernet port. He then opens an interactive SeaNet connection, effectively connecting the ship’s LAN to the LAN at his lab. The instrument designer uses the interactive link to upload new software, fixing the problem.

  • WebMirroring: Keep your ship and shore web sites updated automatically while at sea. SeaNet systems can be configured to associate any ftp-accessible directory on the Internet with a directory on a shipboard computer. Files dropped in one directory are transferred to the other every time the SeaNet link is activated.

    Two examples of WebMirroring projects are:

    SeaNet Scenario: A shipboard drop box is created on a shipboard ftp server so that shipboard investigators and a student reporter can leave photos, digital movies, journal entries, and stories in it as the cruise proceeds. Each time SeaNet connects to shore, the dropbox contents are delivered to a shoreside ftp server for pickup by the web designer. At the same time, changes made to the shoreside web site are mirrored to the shipboard web site so that shipboard personnel can view a copy of the shoreside web site while the SeaNet link is down.