From selection to system diagnosis, through one front door.
AQUROV is your single point of contact for technical questions. Sales handles price, stock, standard items, bulk orders and distribution. Engineering handles parameter changes, compatibility, technical selection, drawings, customization and system integration. When a project grows into core redevelopment, the engineering capability is brought in behind AQUROV — your contact does not change.
- Product selection and compatibility checks
- Basic integration and wiring guidance
- System diagnosis and technical review
- Complex projects coordinated by AQUROV
Two roles, one contact
- Sales handles
- Price · stock · standard · bulk · distribution
- Engineering handles
- Parameters · compatibility · selection · drawings
- Mature variants
- Confirmed by sales against set rules
- Anything that changes product capability
- Confirmed by engineering
- Customer contact throughout
- AQUROV
Mature variants are confirmed by sales; capability changes go to engineering
Six kinds of technical help, one supplier.
Support starts before the order and stays with the product afterwards.
Product selection
Choosing between thrusters and ESCs, cameras and lights, enclosures and penetrators, sensors and control accessories against voltage, thrust, depth, weight and interface.
Compatibility check
Thruster + ESC, camera + housing + light, enclosure + penetrator, sensor + control accessories — mating, signal, voltage and current checked before you commit.
Basic integration
Wiring, mounting and interface guidance so components go into your build the way they were designed to go in.
System diagnosis
Symptom-level diagnosis: whether the cause sits in the component, in the integration, or in the operating conditions.
Technical review
A review of parameters, drawings and interfaces before any commitment — feasibility, compatibility and where the responsibility boundary sits.
Complex project flow
Core redevelopment, system integration and design work taken through a defined project path, coordinated by AQUROV.
.jpg?width=1200)
Some answers are free. Some work is a project.
Standard documentation, basic selection and a preliminary feasibility judgement come first, at no cost. Detailed system proposals, custom design, drawings and heavy engineering input are handled as project work.
Up front, before any commitment
- Standard product documentation
- Provided
- Basic selection support
- Provided
- Preliminary feasibility judgement
- Provided
- Detailed system proposal, custom design or drawings
- Project work
- Before that work starts
- Project reality and purchase intent are confirmed
- Engineering or proposal fee
- Charged when the scope requires it
Before a final answer, the parameters have to be complete
- Final selection
- Formal quotation
- Technical commitment
Until then we give a candidate range, and say clearly what is still missing
When the requirement outgrows a component order.
Core redevelopment, system-level design and full integration run as a project — with the same AQUROV contact you started with.
Requirement & qualification
What the project is, the quantity or project background, and the basic purchasing timeline. A real project without budget yet goes into long-term cultivation rather than being closed.
Scope & responsibility
We separate component supply, light customization and system-level engineering, and state the responsibility boundary before work begins.
Technical definition
Parameters, interfaces, drawings, performance requirements and materials are collected and completed — missing information is named, not assumed.
Proposal & quotation
A proposal or formal quotation follows the technical confirmation. A commercial-only answer never commits engineering scope.
Sample or prototype
Where the risk requires it, a sample or prototype stage validates the design against the confirmed requirement before any volume commitment.
Execution to batch
Batch production follows internal testing and your confirmation of the sample or test result, then repeat orders reuse the confirmed configuration.
Most questions are answered by a document.
Documentation comes first; a technical conversation is the next step, not the first one.
Document set
-
DatasheetParameters per product and versionOn request
-
ManualInstallation and operationOn request
-
Wiring & interface informationSignals, connectors, control sideOn request
-
CADMounting and envelopeOn request
-
Test reportWhere a report exists for the productOn request
Documents are released with each product and version. Ask for anything missing from your build.
What to send with a technical question
-
Product or modelAnd the order number where there is oneRequired
-
What you are trying to achieveThe build, the goal, the constraintRequired
-
Symptoms or measurementsWhat happens, and what you measuredIf applicable
-
Photos, video or drawingsOperating conditions includedIf applicable
Sales collects the case first and answers what it can; technical questions are handed to engineering, and the answer comes back to you from AQUROV.
Ask an engineering question →Describe the build and the constraint.
Product, quantity, application, key parameters and destination country — plus drawings, interfaces or symptoms where they apply. Selection and compatibility questions can be answered directly; anything that changes product capability goes to engineering.
AQUROV · Engineering Store