Appearance
What you need
The gateway
One CanCan running the Aquabase firmware, product ID 010010020 — either generation, but read the v2 warning at the bottom of this page before choosing.
One gateway serves one watermaker. It has a single watermaker device, and it listens to a single unit on its second bus.
On the Aquabase side
| An Aquabase watermaker with its own controller | the machine keeps its own panel and its own protections. The gateway reads what the controller broadcasts and sends it the same commands the panel sends |
| Access to the unit's CAN bus | two wires and a ground, brought out to the CanCan's second CAN connector |
The watermaker must be installed, commissioned and working before the gateway is fitted. The gateway reads a bus; it does not set up a watermaker.
The gateway recognises the ARUBA and SOROYA families, in their Comfort and Premium variants: it reads the model from the unit itself, and nothing has to be declared for it.
Wiring
| Connector | Goes to | Speed |
|---|---|---|
| CAN 1 | the boat's MUXEN bus | 500 kbit/s |
| CAN 2 | the Aquabase CAN bus | 62.5 kbit/s — fixed by the firmware, it cannot be changed by configuration |
62.5 kbit/s is slow for a CAN bus, and it is set twice over: the product definition asks for it, and the firmware sets it again at every start. Nothing you can configure will change it, so the Aquabase side must be running at that speed.
Both are ordinary 120 Ω CAN buses: two wires and a common ground, one 120 Ω termination at each physical end of each bus and nowhere else. The gateway is terminated only if it happens to be at the end of a segment.
The two buses stay electrically separate. Nothing from the MUXEN bus reaches the watermaker except the start, stop and rinse commands this firmware deliberately translates.
The box's own inputs and outputs
Two relays, two dry-contact inputs, two analog inputs — available here as on every CanCan, and independent of the watermaker function. See Reference. Give the I/O device an instance number of its own.
