Differences
This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
intro [2019/10/15 14:00] – nikolal | intro [2022/09/19 11:34] (current) – external edit 127.0.0.1 | ||
---|---|---|---|
Line 1: | Line 1: | ||
====== Introduction ====== | ====== Introduction ====== | ||
+ | The goal of the project, is to be able to perform persistent tracking of acoustic fish tags through combining sensor readings from multiple vessels through multilateration. To further break this down, a scenario of the type of mission is given below. | ||
- | The Otter ASV is a 2 meters long catamaran propelled by two electrical fixed thrusters. This means that steering has to be done through differential thrust by the controller. | + | ^ # ^ Mission Phase ^ Description ^ |
+ | | 1 | Transport | Bring the equipment to the deployment area. | | ||
+ | | 2 | Deployment | Assemble and prepare the vessel. Ensure supporting systems (Server/ | ||
+ | | 3 | Travel | ||
+ | | 4 | Collaborative search | Search area is divided between vessels. Ends after first tag detection. If first search yields no result, perform predetermined action, like searching again or extending search area. | | ||
+ | | 5 | First tag contact | First contact with acoustic tag. The detecting vessel waits or tries single vessel tag positioning. Other vessels congregate to its vicinity, entering formation. | | ||
+ | | 6 | All vessel tag contact | Enter tag formation to commence collaborative fish tracking. | | ||
+ | | 7 | Collaborative fish tracking | Keep formation around tag to estimate its position. | | ||
+ | | 8 | Tracking end | Mission finished or battery level low – wait for pickup or return to predetermined point (like deployment point). | | ||
+ | | 9 | Berthing/ Dismantling equipment | Removing the vessel from the water.| | ||
+ | | 10 | Transport | Pack up equipment and leave deployment area | | ||
+ | ===== Collaborative Fish Tracking ===== | ||
- | ===== The control box ===== | + | {{ : |
- | The control box is based around a Raspberry Pi 4 with 4GB of RAM. Connected through it's GPIO pins is a [[https:// | + | A visual representation |
+ | is shown in the figure. Here, the three Fish Otters have gained contact with a tagged fish, | ||
+ | and is using multilateration to estimate its position. Based on the estimate, decisions are | ||
+ | then made regarding the next position of the formation. The formation also has to try to | ||
+ | minimize GDOP, while at the same time avoiding surrounding hazards | ||
+ | thruster usage. Reducing motor usage is beneficial because it conserves | ||
+ | and reduces noise in the medium (water). Increased noise makes it harder for the acoustic | ||
+ | receiver to discern tag transmissions and may also influence | ||
- | {{ : | + | The communication between the operator and the vessels, can, as shown in the figure |
- | ===== The thrusters ===== | + | go through |
- | The thrusters used by the Otter are two [[https:// | + | network. Either one, or both at once is to be used, with the expectation that bandwidth |
- | ===== The batteries ===== | + | and increased network control will be benefits of the AirMax channel, while range is the |
- | The batteries are of the shelf [[https:// | + | benefit |
- | ===== The hull ===== | + | |
- | Delivered by Maritime Robotics, | + | Positioning |
+ | system. The GNSS can be used as an inverted analogy for the fish tracking performed by | ||
+ | the Otters. In the GNSS, the satellites transmit signals, | ||
+ | In the fish tracking scenario, the Otters have the same role as the satellites, but instead | ||
+ | receives | ||
+ | |||
+ | ===== The NTNU Fish Otter ===== | ||
+ | The target vessel for the system | ||
+ | {{ : | ||
- | //Insert image of Otter hull here// | ||