...
1.1 Limitations in use/performance with other specific components
Main components
Component | Problem | Solution |
---|---|---|
Cage type: | Conflict between the top bracket fixture and the handrail post. | Use stainless ratchet straps or rope to tie the top part of the bracket to the pole. |
Extra equipment
Component | Problem | Solution / Løsning |
---|---|---|
Aeration devices that makes airbubbles inside the cage. Sold under names like(Midt-Norsk ring, Turbolift etc) | The echosounder picks up the bubbles and it creates a noisy image of the fish. | Echosounders are not compatible with aeration devices. |
Aside from these components, the equipment is compatible with any other component that is not directly interfering with it. It is compatible with predator nets.
...
1.2.1 Coverage for different cage sizes:
Cage type | Estimated total coverage |
---|---|
160m circumference | ~ 40% |
120m circumference | ~50% |
130m circumference | ~80% |
Square 40x40m | ~25% |
Square 30x30m | ~30% |
Square 25x25m | ~50% |
Performance is mainly affected by how well the sensors cover the feeding zone.
...
Ethernet 802.3ab compatible connection available for all barge services.
The server running the Bluegrove service on the barge needs access to these hosts and services:
Host | Service | Comment |
Barge feeding system | Feeding system API as defined by the vendor. | List of feeding systems:Feeding-system integrations and compatibility with Bluegrove |
Optional: | RTSP video stream. | Bluegrove also needs information on the which stream belongs to which cage. |
Required network performance to provide optimal services:
Service | Bandwidth | Uptime | Latency | Packet Loss | Jitter |
Network services on barge | 1 Gbit | 100% | 2 ms | 0 | 15% |
Info |
---|
What happens if the requirement is not met: Remote services Services are interrupted. Data is buffered for some time until recovery. |
3.2 Cage to barge network
Clear Ethernet 802.3ab compatible connection. By default, Bluegrove uses wireless radios, which is dependent on a clear line of sight from barge roof to cages. Ethernet 802.3ab compatible connection available for all cage services. Bluegrove could also use other cage to barge networking, given that all the necessary devices are accessible from the Bluegrove server.
Required network performance to provide optimal services:
Service | Bandwidth | Uptime | Latency | Packet Loss | Jitter |
Network services on cage | 200 Mbit | 100% | 5 ms | 0 | 15% |
...
Info |
---|
What happens if the requirement is not met: Services are interrupted. Data is buffered for some time until recovery. |
3.3 Internet access for the Bluegrove server
Services dependent on dedicated internet connection bandwidth with minimum requirements:
Service | Upload | Uptime | Latency | Packet Loss | Jitter |
Bluegrove remote servicing | 1 Mbps | 90% | 150 ms | 5% over 10 minutes | 15% |
Cloud data API
1 Mbps
90%
150 ms
5% over 10 minutes
15%
Bluegrove software solutions | 1 Mbps | 90% | 150ms | 5% over 10 minutes | 15% |
...
If the internet subscription has a monthly limit for traffic we need ; the Bluegrove services needs 100 GB a Month.
Ports used by the Bluegrove server
Type | Port | Used for | Traffic |
TCP | 1194 |
OpenVPN for access to Bluegrove cloud. | Incoming and outgoing | ||
TCP | 80 | HTTP outgoing for connection to API. Eg environmental data. HTTP incoming to be able to connect from the feed center. | Incoming and outgoing |
TCP | 443 | HTTP outgoing for connection to API. Eg environmental data. HTTP incoming to be able to connect from the feed center. | Incoming and outgoing |
Info |
---|
What happens if the requirement is not met: Remote services are interrupted. Data is buffered for some time until recovery. |
...
Services dependent on dedicated network connection bandwidth with minimum requirements:
Service | Upload | Uptime | Latency | Packet Loss | Jitter |
Feeding (remote, without video) | 5 Mbps | 100% | 150 ms | 1% over 10 minutes | 15% |
Feeding (remote, with video) | 30 Mbps | 100% | 150 ms | 1% over 10 minutes | 15% |
Upload bandwidth, uptime, latency, packet loss and jitter between devices on the barge network and the Feeding Operations Center.
...
Expand | ||
---|---|---|
| ||
Feeding system requirements version 0.0.6. This section defines general requirements for controlling a feeding system for sea-based and land based aquaculture. IntentionEnable the fish farmer to:
Definitions
Out of scope features
Required functionality:
|
6 Machine vision for pellet detection and health indicators.
6.1 Video streams in the RTSP protocol
RTSP streams from the camera is available on the network we have access to.
Information on the which stream belongs to which cage.
Info |
---|
What happens if the requirement is not met: The data from the video-stream is interrupted
|