Century R&D Investment Institute

Data Acquisition

1. Connecting Cables:
   • Serial Cable (RS-232): Commonly used to connect ECDIS devices to the USV’s onboard computer. Ensure that the ECDIS supports RS-232 output.
   • USB Cable: If the ECDIS supports USB output, this can be a convenient option for direct connection.
   • Ethernet Cable: For ECDIS systems that support network-based communication (e.g., NMEA 2000 or TCP/IP), an Ethernet connection may be used.

2. Port Names:
   • COM Ports: For serial connections (RS-232), the port name may vary based on the operating system. For example, in Windows, it might be something like COM1, COM2, etc. In Linux, it could be /dev/ttyS0, /dev/ttyUSB0, etc.
   • USB Ports: When using USB, the operating system will typically assign a virtual COM port (e.g., COM3 in Windows) which can be identified using device management tools.
   • Network Ports: When communicating over Ethernet, ensure you know the IP address and port number used by the ECDIS. This could be something like 192.168.1.10:2000.

3. Data Formats:
   • NMEA 0183 Sentences: These are standard ASCII text sentences that convey navigational information. For example:
     • $GPGGA,123456.00,3739.1234,N,12222.1234,W,1,08,0.9,545.4,M,46.9,M,,*47
     • Here, GGA is the sentence type, and it contains information such as time, latitude, longitude, and fix quality.
   • NMEA 2000: This uses a more complex binary format for data transmission. It encapsulates various messages related to navigation, vessel status, and environmental conditions.
   • S-57/S-100 Files: These formats are used for vector charts and other navigational data. They can be read using libraries that support these standards (e.g., GDAL for S-57 data).

Data Processing

1. Data Parsing:
   • Use libraries or custom code to parse NMEA sentences and extract relevant information. For NMEA 0183, each sentence can be split by commas, and specific fields can be processed based on the sentence type.
   • For NMEA 2000, you may need to utilize a library that supports this binary format, as it often requires handling CAN bus messages.

2. Data Interpretation:
   • Convert raw data into structured formats. For example, latitude and longitude from NMEA sentences can be converted from string format to floating-point numbers for calculations.
   • For S-57 or S-100 data, use GIS libraries to interpret and render the navigational charts.

3. Real-time Data Handling:
   • Implement a loop that continuously listens for incoming data from the ECDIS. This can be done using a multithreading approach to ensure that data acquisition does not block other processes.
   • Store the processed data in memory or a local database for quick access during operations.

4. Data Validation:
   • Implement checks to ensure the integrity of incoming data. This may include validating checksums for NMEA sentences and ensuring that positional data falls within expected ranges.

5. Integration with Navigation Algorithms:
   • Use the processed data as inputs for navigation algorithms, such as path planning or collision avoidance systems. This involves integrating ECDIS data with other sensor inputs (e.g., GPS, IMU) for a comprehensive situational awareness.

6. User Interface Updates:
   • Ensure that the user interface reflects real-time changes in navigational data. This might involve updating graphical displays, maps, and alerts based on the processed information.

By focusing on these aspects of data acquisition and processing, the USV software can effectively utilize ECDIS data to enhance navigation and operational capabilities.