CageEye technical infrastructure requirements
In short
Stable power on the cage and barge
Stable internet
Detailed requirements
These requirements define the optimal environment for CageEye systems. If any of the requirements are not met the CageEye service will be negatively impacted.
Related documents:
Environmental parameter limitations: https://bluegrove.atlassian.net/wiki/spaces/BKB/pages/991723588
1 Physical requirements
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
CageEye is verified to be compatible with:
Aeration device: Midt-Norsk ringen and equivalent devices that primarily makes bubbles above ø1mm.
Predator nets
Potentially challenging components
Component | Challenge | Solution / Løsning |
|---|---|---|
Aeration/diffusion devices that makes airbubbles smaller than Ø 1mm. | The echosounder may pick up on the bubbles and get a poor measurement of the fish position. | Place the aeration/diffusion device outside the measurement volume. |
Aside from these components, the equipment is compatible with any other component that is not directly interfering with it.
1.2 Cage requirements
Minimum 15m deep nets, which gives a 13m sensor head distance.
1.5 Operational feeding system with integration.
CageEye is compatible with these feeding systems. The blowers, dosing, changers, piping, feed spreaders need to be in working condition.
What happens if the requirement is not met:
You will not get feeding data and you might not be able to feed.
2 Power Requirements
2.1 Power at barge
The CageEye system requires max 500w @ 230V 50hz at the barge.
The system complies with the international EMC standards: IEC/EN 60950-1, IEC/EN 61000-3-3, IEC/EN 61000-6-1 and IEC/EN 61000-6-3.
A ground fault circuit interrupter (GFCI) must be used to enhance safety and minimize risk from insulation faults, moisture ingress, or cable damage.
To maintain continuous system uptime, a Uninterruptible Power Supply (UPS) is recommended.
What happens if the requirement is not met:
System operation halts immediately when power to the server or antenna is interrupted. The use of a UPS mitigates service disruption caused by power loss events.
2.2 Power at cage
Estimated continuous power consumption for all sensor devices in the cage is approximately 60 W.
The CageEye system requires 60 W @ 230 V / 50 Hz outlet at the cage.
Circuit Protection
The power supply should be protected with a circuit breaker rated between 6 A and 16 A.
Note: Using an oversized breaker may reduce protection against overloads. Initial testing suggests that 6 A breakers suffice, but this must be verified on-site depending on total load and cable sizing.
Ground Fault Protection
Ground fault protection (e.g., RCD or RCBO) is strongly recommended to protect personnel and equipment from short circuits or insulation faults.
What happens if the requirement is not met:
System operation halts immediately when power to the server or antenna is interrupted, unless the cage has a UPS that mitigates it.
3 Network Requirements
CageEye uses two operating models. Customer managed network, and unmanged network.
3.1. Network performance requirements
Service | Upload | Uptime | Latency | Packet Loss | Jitter |
Remote real time monitoring and/or feeding control | 5 Mbps | 100% | 150 ms | 1% over 10 minutes | 15% |
3.2 Unmanaged networks
CageEye will install a server on the barge that needs to be on the same network as the feeding systems and the feeding cameras. Remote connections to operations centers can be set up in cooperation with the customers technical staff. CageEye needs to use radios to communicate with the sensors on the cages.
3.2.0 Ports used by the CageEye server
Type | Port | Used for | Traffic |
TCP | 1194 | Communication through OpenVPN with CageEye cloud servers; and remote servicing. | Incoming and outgoing |
What happens if the requirement is not met:
Dataflow and remote services are interrupted. Data is buffered for some time until recovery.
3.3 Managed networks
For a detailed requirements for operating in customer managed networks see this page. [Private]https://bluegrove.atlassian.net/wiki/spaces/TRB/pages/1305903173/CageEye+Cybersecurity+practices#Operating-in-customer-managed-networks. Ask a CageEye representative to get access to this page.
3.4 Optional: Cage to barge network with radio.
If no cage to barge network is available, CageEye can set up a cage to barge network with radio. We typically use the 5GHz band. We use Ubiquity Rocket AC on the barge, and Ubiquity Bullet AC on the cage.
We configure the radio to use given frequencies between 5190-5940 GHz, alternatively the radio can be configured to automatically seek out new frequencies detects interference.