WinFrog is an integrated navigation and data management software package. It was developed by Racal Pelagos, Inc. of San Diego, California (currently Fugro Pelagos, Inc.). IODP uses it to manage and collect data from the following sources:
In addition to data collection, WinFrog:
WinFrog software is installed on two mirrored PC computers in the Underway (UW) lab. Either one can be set up as the “Master”, with the other one ready as the back-up machine.
The master machine must have the hardware security key (blue dongle) connected to it, allowing the software to be run. Only one of the two PCs (WinFrog 1 & 2) can be running WinFrog on the network at a time since they share the same IP address. A machine without the key can only run in “Demo” mode, acting as the Smart Remote .
When switching between WinFrog 1 & 2 as the master, it is best to:
There will be another machine running the software as a Smart Remote that will display our position for the ship-wide video distribution. This remote machine currently resides in the MCS’s server-room.
The current version of WinFrog is V.3.10.19. The original software disk should be stored in the UW lab. WinFrog operates on Windows XP. WinFrog 1 & 2 each have a 4-port RS-232 serial expansion board to connect to the external devices (GPS, gyro, bathymetry). Since version 3.7.14, WinFrog has an IODP requested modification, Position Averaging Utility, to perform site fixes. A Site Fix can be created using the “Unintelligent Design Team” SiteFix Software (LabView program.)
Electronic versions of the WinFrog Vendor User Guide are available as reference material on the WinFrog computers and in the WinFrog Software.
WinFrog uses an initiation file (WinFrogini.wfg) to save all of the current settings (e.g., what vehicles are defined, coastlines, and window configurations) and any changes in the program's default settings, including, but not limited to the:
• Placement of the open window
• Names and placement of any defined vehicles and devices
• Geodetic parameters
It also contains the version of WinFrog that created the file. The file is used to configure WinFrog every time the program is started and is created in the system directory (C:\Users). This file is created in the following folder (Windows 10): C:\Users\Public\). The file is overwritten and saved when WinFrog is exited properly.
Regularly save a copy of the WinFrogini.wfg file, both on the working computer and as a backup. Currently there is no set place to save the backup file; however, one of the servers would be best.
1. Launch WinFrog from the desktop (Figure 2.) On the Master, the program should open with no problems.
— If a dialogue box opens up asking if you want to run in “demo” mode, then cancel and try opening WinFrog again.
— If the program does not open after a few tries, it is usually a problem with the WinFrogini.wfg file. Replace the WinFrogini.wfg file with one of the previously saved versions.
2. Click File -> System Config File... -> Load. If there appears to be a problem with the setup of the I/O Devices, vehicle graphics or vehicle text window, upload a recently saved WinFrog configuration file.
— Always reboot the computer after any kind of computer crash or freeze.
— If WinFrog still does not open after trying all of this, call an MCS to trouble shoot. The worst-case scenario is that WinFrog will have to be reinstalled.
3. Save a new System Configuration file by clicking File -> System Config File… -> Save. This file can then be loaded at any time to reset the system configuration to the saved parameters.
Note: Name the file using the following naming convention: Exp#_date.cfg (e.g., 317_20100123.cfg).
WinFrog will write its *.dat and *.raw data output files to a directory. Before you launch WinFrog, create and setup a new Expedition specific directory (follow the procedure in the next section.) This folder contains the following sub-folders:
To set up working directories, perform these steps:
In WinFrog, the JOIDES Resolution is a Vehicle. The vehicle configuration process allows the user to create a new vehicle or modify an existing vehicle.
To create a new vehicle or configure an existing vehicle, perform these steps:
You may also configure vehicle tracking offsets from the Configure Vehicles window. These offsets correspond to different devices that are added to the vehicle and are entered in relation to the moon pool. When adding a new device to the vehicle you may enter its offset manually or choose it from the Configure Offsets list(Figure 7).
WinFrog has the ability to display shorelines or bathymetric contours in its Graphics window by means of loading a “Picture” file. This file has a “.pic” file extension, and it is an ASCII, comma-delimited text format.
The file consists of three record types:
See the WinFrog Vendor User Guide for exact definitions of the individual data fields.
The data points in these files may be:
The usual source for third-party files is the National Geophysical Data Center (NGDC.) The NGDC provides world-wide digitized shorelines over the Internet free of charge. This is the recommended source for displaying coastline data in WinFrog for an IODP Expedition.
The USGS Coastline Extractor was created by Rich Signell and is hosted by NOAA/National Geophysical Data Center (NGDC.) It can be downloaded as part of the GEOphysical DAta System (GEODAS) software tool. The link is:
• https://ngdc.noaa.gov/mgg/geodas/trackline.html
The Coastline Extractor is downloaded on both WinFrog Machines. The coastline data can be extracted without internet access. To download a source file, perform these steps:
The data from the Coastline Extractor must be reformatted to WinFrog’s .PIC file format using the MakePic.m Matlab script (or Makepic.py python script.)
To convert the file, perform these steps.
NOTE from x369 Tech Report: The MakePic.exe DOS executable will not run in the new Win10 Enterprise 64-bit environment. Makepic.exe was installed on the GC3 PC for use. |
A header must be included on the first line of the .pic. The following header is typically used: “2, Coast, 7, 0, 0”. Each parameter (separated by the comma) is defined below.
2 | Picture Control Records | Always use number 2 |
Coast | Name of the picture segment | Leave as Coast |
7 | Pen color for the Graphics window | 0= black 1= red 2=yellow 3=green 4=cyan, 5=blue 6=magenta 7=white 8=gray |
0 | Line style for the Graphics window | 0 = solid 1 = dashed |
0 | Reserved for future use | NA |
To make your picture file the Working Picture File, perform these steps.
Geodetic data are used in geodesy, navigation, surveying by cartographers and satellite navigation systems to translate positions indicated on their products to their real position on Earth. The systems are needed because the Earth is not a perfect sphere. Examples of map data are:
The difference in co-ordinates between data is commonly referred to as datum shift. The datum shift between two particular datums can vary from one place to another within one country or region, and can be anything from zero to hundreds of meters (or several kilometers for some remote islands).
The Trimble GPS report Latitude and Longitude coordinates in WGS 84 by default. It is recommended to set the WinFrog Geodetics to WGS84 UTM (Universal Transverse Mercator Projection.) WinFrog converts the Latitude and Longitude into Eastings and Northings (meters from an origin.) The UTM parameters in WinFrog have -50000.00m False easting. The origin is defined by the UTM zone. The UTM zone is a function of longitude.
To set the geodetics, perform these steps (Figure 8):
Note: It is important when performing a Site Fix to select the correct UTM zone. Long transits between sites can mean several zone changes. Be sure when running the Position Averaging Utility the zone for that Site Fix is correct.
WinFrog v3.10 can display complex coastline data and maps by creating or loading a Blue Marble Layer (BML.) This file type has a .BML file extension. WinFrog has a utility to create the .BML from different file sources (Geotiff maps, vector maps, etc.) See the WinFrog help for more information.
Once you have configured the JOIDES Resolution Vehicle, you are ready to add vehicle devices. The devices covered in this section are the:
Both WinFrog PCs (WF1 and WF2) are equipped with National Instruments RS232-USB routers that allow them to connect 4 com ports each. The Bathy2010 depth sounder and SeaSpy Magnetometer are connected to the WinFrog machines through COM ports. The other instruments (GPS and Gyro) and data distribution are wired via TCP/IP into the ships network. The TCP/IP connections are labeled as COM0 devices in WinFrog Vehicle devices. The current com port designations are detailed in Figure 9 and listed below:
COM Port Configurations on WinFrog1 and WinFrog2 using NI RS232-USB router or TCP/IP:
To add a device select Configure -> I/O Devices -> Add menu and select each device to be added. This procedure is the same for all devices.
Device | Host Address | Port Number | Device Name | Offset FWD/AFT | Offset PORT/STB | Elev. |
Trimble Aft GPS | 165.91.72.118 | 5018 | Aft Trimble GPS – IN | -73.9m | 0m | |
Trimble Forward GPS | 165.91.72.116 | 5018 | Fwd Trimble GPS – IN | 52m | -7m | 16m |
Note: Either Trimble can act as the Aft or Forward GPS device. The offsets given are for the position of the Aft or Forward Antennas. Make sure the host IP address for the Aft or Forward device matches with the Trimble unit set up in that location.
The origin for the JOIDES Resolution is usually set to the moonpool, therefore, the offset of the GPS antennas from the moonpool must be entered. From the Configure Vehicle-Devices window:
This section covers sending navigation information to another system. National Marine Electronics Association (NMEA) is the output format. NMEA is output from the GPS and Gyro devices. The GPS and Gyro are connected to the ship’s network via TCP/IP. This section discusses outputting NMEA navigation data from WinFrog (via RS232 COM Ports or TCP/IP.) to the Bathy2010, SeaSpy Magnetometer, JR Data Server, a data file, the “Unintelligent Design Team” Labview SiteFix program.
Configure the device according to the table below:
Device Name | Connect Using | IP Address | COM/Port number | Connection Options/Type | Device Parameters |
---|---|---|---|---|---|
NMEA to Bathy | RS232 COM Ports | n/a | COM13 | n/a | 9600, 8, 1, none |
NMEA to SeaSpy | RS232 COM Ports | n/a | COM11 | n/a | 9600, 8, 1, none |
NMEA to JR Data Server | TCP/IP | 165.91.72.122 | 128 | Listen |
This section covers recording the water depth data from the Bathy2010 system into WinFrog. If the information is received directly from another computer, you must use a null modem serial cable.
After all devices are added, the available data items should look like Figure 17 (left panel.)
The vehicle text window displays navigation, recording, and waypoint information.
To configure the vehicle text, perform these steps:
An example of what the text configuration will look like in Vehicle Window is shown in Figure 20. An extra row can always be added, for survey line information, in the event of a seismic survey. To specify an available item to a specific row, select the row number in the Row pull down menu in Figure 19.
Waypoints are sets of coordinates (longitude and latitude) that identify a point in physical space. In GPS navigation, a “route” is usually defined as a series of two or more waypoints. To follow such a route, the GPS user navigates to the nearest waypoint, then to the next one in turn, until the destination is reached. Our drill sites and ports-of-call are waypoints.
To add a waypoint, perform these steps:
To set up waypoint tracking, perform these steps:
When a waypoint is selected to track, the name and range will appear in the Vehicle Window.
Logging data in WinFrog is performed by what are called Events. The user must define the data to be collected and at what interval of time. Data are written to two files:
The destination folders for these files are set up in the working directories window and should be set up at the beginning of each Expedition.
Data is collected at all times (for transits and while on-site) throughout an expedition. Start the:
To start logging an event for a transit or at a hole, perform these steps:
Click OK and the Event Secondary Configuration window opens (Figure 25). This is an option to setup another event log file with a new filename.
In the Vehicle Window, notice how the fields related to eventing are enabled and ready to be started (Figure 26).
On the Main Screen, click the green Event Start (FX) icon (Figure 27) to start data logging. Now data are being logged.
To stop event logging, perform these steps:
Keep the same name and continue logging to it by appending more data (the user will be prompted with the option to append or overwrite).
The naming scheme has changed in the new Winfrog version. |
The Operations Superintendent will need a position (latitude, longitude) for each hole. The position will be determined by averaging the navigation data fixes recorded while the drill string is in the hole. The data are from the IODP Forward and Aft GPS. Although a separate Site Fixer program is available to IODP Techs, WinFrog also has a Site Averaging Utility.
When coming on site, stop your transit data event and start a new data event for the site’s first hole as described in the Data Event set-up procedure. Remember to create a new event data file (ex. U1337A.dat) for each hole.
WinFrog utilizes a utility called Position Averaging to average a position for a vehicle. Fugro Pelagos modified their position averaging utility for IODP in order for us to utilize recorded data files to determine hole positions.
To average a position for a vehicle, perform these steps:
Once the file has been selected, the time window of data must be selected. Determine the time window in which the drill string was in the Hole (GMT) by performing the steps in the Procedure: Determine Hole Position. To be safe, shave off 15 minutes or so from the beginning and end of the window. This will throw out most of the potential outliers as the ship settles into position. The key is to only use data collected when the pipe is actually in the hole.
During Expedition 321, the Operations Manager suggested using a time range of core 3’s time on deck (TOD) to the TOD of the last core of the hole.
To determine Position, perform these steps:
From Figure 31, select the Save option and navigate the file to be placed in the Expedition’s position folder. An .rtf file is created, where the screen capture can be pasted and a PDF generated. Print the document and give to the OPS Manager (and/or Staff Scientist if you wish). Save a copy to the Position folder.
If the position is not acceptable go back to Determine Position of a Hole (Figure 29) and try the following:
•Change the window of time (this may take a few tries).
•If you can identify some bad data, go to the Observed Data section, select those points not to be used, and click Re-Calculate.
WinFrogNavigationUserGuide.pdf - Feb. 24, 2020