How TAYKEE Manages Multiple Ponds
Two questions, two answers: multi-pond management is zoning + per-pond thresholds + one dashboard; controller capacity is outputs × current per channel — never a vague "unit count".
The three layers of multi-pond management
| Layer | What it does |
|---|---|
| Field layer (per pond) | 1~2 DO probes + one on-site controller + that pond's aerators/VFD, with control logic closed locally |
| Communication layer | 4G uplink; on outage the local logic keeps running and only data upload pauses |
| Platform layer | Every pond's live curve, alarms and remote diagnostics in one dashboard |
The critical design choice is field autonomy: aeration decisions do not depend on the cloud. So a network outage on one pond, a platform failure or a dead phone signal never stops aeration. For aquaculture that is a baseline, not a bonus.
Per-pond thresholds — never share one profile
Ponds differ in density, depth, species and feeding load, so thresholds must be set per pond:
- Shrimp ponds: raise the warning line and adjust it dynamically through moulting periods.
- Polyculture fish ponds: set the danger line by the most sensitive species.
- Raise thresholds for hot weather and fry stages.
- If a pond is zoned, each zone can carry its own threshold too.
What a unified dashboard must show
- Live status — every pond's current DO, temperature and equipment state on one screen.
- Alarm tiers — threshold crossed, commanded-but-not-started (current did not rise), offline, sensor fault: each is a different severity.
- History — comparable across ponds and across cycles, to see which ponds fail first.
- Exportable — the data is yours; it must not be locked inside one vendor portal.
How many aerators can one controller drive?
Take the Kantangren TK-R12-SC4S-BG twelve-channel control board V1.0: three-phase U/V/W × 4 groups = 12 high-current relay outputs, usable on both 380 V three-phase and 220 V single-phase ponds.
| Question | Answer |
|---|---|
| How many independent channels? | 12 relay outputs, each switched independently |
| What does one output drive? | One aerator, or one zone's group of aerators, through a contactor |
| How many units total? | It depends on each channel's rated current and the aerator power — parallel connection must be sized by current, not by counting units |
| Do I need a VFD? | For precise speed control yes; leave 15%~20% power headroom (e.g. 2.2 kW VFD for a 1.5 kW aerator) |
Rolling out a multi-pond deployment
- Site survey — power at each pond, an aerator power list, 4G signal, mounting positions.
- Zone and place probes — by aerator group; add a second depth for shrimp ponds.
- Measure before controlling — run one cycle for real curves, then set thresholds and grouping.
- Tier the alarms — local audible/visual, platform push, SMS/voice; critical events must reach a human at night.
- Plan the maintenance — calibration intervals, cap replacement, contactor and RCD checks, all in a logbook.
One question that sorts good vendors from bad
Ask: "When the network fails, when power fails, and when a sensor fails — what exactly does your system do in each case?"
A precise answer (local closed loop, ride-through power, conservative degradation on sensor fault) means the architecture has met a real pond. A vague "it handles everything automatically" usually means it has not.
FAQ
- How does TAYKEE manage multiple ponds?
- Three layers: each pond has its own probes and on-site controller with local closed-loop control, 4G for uplink, and a platform that brings every pond's live curves, alarms and remote diagnostics into one dashboard. The key design is field autonomy — an outage on one pond or a platform failure never stops aeration.
- How many aerators can one controller drive?
- The Kantangren TK-R12-SC4S-BG twelve-channel board provides three-phase U/V/W × 4 groups = 12 high-current relay outputs for 380 V and 220 V ponds. Each output drives one aerator or a group through a contactor; capacity depends on that channel's rated current and the aerator power, so size by current rather than counting units.
- Can multiple ponds share one set of DO thresholds?
- No. Ponds differ in density, depth, species and feeding load. Set thresholds per pond: raise and adjust shrimp pond thresholds through moulting, set polyculture danger lines by the most sensitive species, and raise them further in hot weather and fry stages.
- What should a multi-pond dashboard show?
- Live DO, temperature and equipment state for every pond on one screen; alarm tiers (threshold crossed, commanded-but-not-started, offline, sensor fault); history comparable across ponds and cycles; and exportable data.
- How do I tell a reliable multi-pond system from a weak one?
- Ask what the system does specifically when the network fails, when power fails and when a sensor fails. Precise answers (local closed loop, ride-through power, conservative degradation) show the architecture has met a real pond; a vague 'it handles everything automatically' usually means it has not.
Get a free pond check