...
The CageEye system requires 2 kW 2kW @ 230V 50hz at the barge.
...
| Info |
|---|
What happens if the requirement is not met: Service stops as soon as the power to the server and antenna is broken. This is mitigated by using a UPS(battery). |
2.2 Power at cage
Estimated continuous power requirements for all sensor devices in cage: 60 W
Estimated maximum power consumption in the future 500 W
The CageEye system requires 60 W @ 230V 50hz outlet at the cage. The power supply must have a 3-16A fuse.Estimated continuous power requirements for all sensor devices in cage: 60 W
Estimated maximum power consumption in the future 500 W
| Info |
|---|
What happens if the requirement is not met: Service stops as soon as the power is interrupted. This is mitigated by using a UPS(battery). |
...
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 Video stream. | Note: Bluegrove also needs information on the which stream belongs to which cage. |
...
3.2 Cage to barge network
Ethernet 802.3ab compatible connection. By default, Bluegrove uses wireless radios, which is dependent on a clear line of sight from barge roof to the cages. Bluegrove could also use other cage to barge networking, given that all the necessary devices are accessible from the Bluegrove server.
Ethernet 802.3ab compatible connection.
Required network performance to provide optimal services:
...
Service | Upload | Uptime | Latency | Packet Loss | Jitter |
Bluegrove remote servicing | 1 Mbps | 90% | 150 ms | 5% over 10 minutes | 15% |
Bluegrove software solutions(data flow, ML model updates etc.) | 1 Mbps | 90% | 150ms | 5% over 10 minutes | 15% |
...
Type | Port | Used for | Traffic |
TCP | 1194 | Communication through OpenVPN for access to with 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 centerservers; and remote servicing. | Incoming and outgoing |
| Info |
|---|
What happens if the requirement is not met: Remote Dataflow and remote services are interrupted. Data is buffered for some time until recovery. |
...
Service | Upload | Uptime | Latency | Packet Loss | Jitter |
Feeding Real time feeding (remote, without video) | 5 Mbps | 100% | 150 ms | 1% over 10 minutes | 15% |
Feeding Real time feeding (remote, with video) | 30 Mbps | 100% | 150 ms | 1% over 10 minutes | 15% |
...