EVO Max technology guide · Canada
A‑Mesh changes how compatible aircraft and controllers communicate. It does not replace GPS.
A‑Mesh is the communications and collaboration layer. Visual SLAM is the positioning and navigation layer used when GNSS is weak or unavailable. Understanding that difference is the starting point for evaluating relay and multi-aircraft EVO Max workflows.
Quick answer: Autel A‑Mesh lets compatible EVO Max aircraft and ground terminals form a network for functions such as one-controller multi-aircraft management, relay operation, coordinated polygon missions and information sharing. It can change the route that commands and data take around a physical obstruction. It does not create unlimited range, navigate the aircraft without GNSS or authorize a Canadian BVLOS mission.
What Is Autel A‑Mesh?
A conventional drone connection is easy to picture: one controller exchanges commands, telemetry and video with one aircraft. Autel calls that a Single Link. A‑Mesh adds compatible aircraft and controllers as network nodes instead of treating every aircraft as an isolated link.
In Autel’s terminology, the Lead Controller coordinates the team, the Lead Aircraft serves as a communications hub and a Member Aircraft communicates through that structure. Autel documents functions including A‑Mesh Control, Formation Flight, Polygon Mission, Relay Operation, an observer-style Autel Mobile Awareness Kit (AMAK) mode and shared PinPoints. The exact functions available depend on the aircraft generation, firmware, controller configuration and region.
| Technology | Question it answers | What it does not prove |
|---|---|---|
| A‑Mesh | How can compatible aircraft and ground terminals communicate, relay and collaborate? | That the aircraft can navigate without GNSS or that the mission is legally authorized. |
| Visual SLAM | How can the aircraft estimate position and navigate when GNSS is weak, blocked or unavailable? | That radio communication around every obstruction will remain available. |
| Autonomy Engine | How can environmental data support path planning, obstacle avoidance and return-to-home behaviour? | That every route is safe, fully autonomous or suitable without pilot review. |
| SkyLink | How does the normal aircraft-to-controller command and image-transmission link operate? | That a manufacturer-rated maximum will be achieved in the real environment. |
The useful mental model: A‑Mesh is a network architecture. It can provide another communication path through a lead aircraft, but every node still operates within real radio, battery, terrain, interference and configuration limits.
How Is A‑Mesh Different From a Normal Drone Connection?
Single Link
Controller ↔ Aircraft. The pilot manages one aircraft over its direct command-and-control and video link. If terrain or a structure blocks that path, the link may degrade.
A‑Mesh topology
Controller ↔ Lead Aircraft ↔ Member Aircraft. Compatible nodes can be linked for relay, multi-aircraft management and information sharing.
The enterprise value is not a magical increase in every range number. It is the ability to redesign the communication topology. A lead aircraft positioned with a good path to both the controller and the member aircraft may bridge a route that a direct controller-to-member link cannot serve reliably.
How A‑Mesh Relay Operation Works
Autel’s documented relay workflow is straightforward: establish the A‑Mesh team, select and position the lead aircraft above an obstruction, then switch pilot control to the member aircraft and fly it toward the mission area. The lead aircraft remains the communication bridge.
Conceptual relay path
This is a simplified planning diagram, not a range or clearance guarantee.
Relay operation may be useful around hills, industrial structures or other terrain that interrupts a direct radio path. It does not remove physical radio limits. The relay aircraft must be positioned, powered and monitored; the network can still be affected by distance, obstructions, interference, battery state and a failure or shutdown of the lead node.
Autel’s EVO Max documentation specifically warns that the lead aircraft functions as the bridge and should not be powered off while a member aircraft is airborne. That operational dependency belongs in the risk assessment and contingency plan—not only in a sales demonstration.
Can One Controller Manage Multiple EVO Max Drones?
Autel documents an A‑Mesh Control interface in which the Lead Controller can select all aircraft, the Lead Aircraft or a Member Aircraft. It also provides views for aircraft status and camera feeds. This can reduce interface switching during a coordinated mission, but it does not reduce pilot workload to zero.
Historical Autel guidance for EVO Max V1.8 described a maximum of two aircraft and two smart controllers. A later EVO Max Series user manual also describes adding one additional aircraft to a team. These are version-specific references, not a promise that every current or future EVO Max configuration has the same limits. Confirm the exact aircraft, smart controller, application and firmware before designing a procurement or operating concept around a node count.
Polygon Missions and Coordinated Operations
Autel’s A‑Mesh Polygon Mission can divide a polygon route into segments for linked aircraft. Conceptually, one aircraft can work one portion of the area while another works the remaining portion. This may improve coverage for a suitable mapping, search or inspection mission.
It is not defensible to claim that two drones automatically complete the work twice as fast. Launch sequencing, separation, batteries, operator workload, crew roles, terrain, route geometry, data requirements, communications and Canadian operating rules all affect useful field productivity.
Is A‑Mesh the Same as a Drone Swarm?
No—not in the broad sense commonly implied by “autonomous swarm.” Autel documents multi-aircraft networking, coordinated polygon missions and a Formation Flight function in which a member aircraft maintains a defined spatial relationship to the lead aircraft. Those are specific networked behaviours. They do not by themselves demonstrate decentralized swarm intelligence, collective goal formation or autonomous adaptation across an unrestricted fleet.
Use precise language: “multi-aircraft networking,” “coordinated mission” or “formation function” describes the documented capability. “Autonomous swarm” should only be used when the exact configuration and behaviour support that claim.
How A‑Mesh Shares Video, Telemetry and PinPoints
A‑Mesh is not only about flight commands. Autel documents access to aircraft status, camera feeds and shared PinPoints. Its AMAK mode allows an additional controller to join as an observer that synchronously views the Lead Controller’s screen without aircraft-control authority.
That separation can matter in public-safety and inspection workflows. The pilot can retain flight control while another team member views a thermal or visual feed. A shared PinPoint can help a command or field team communicate the same target location. The result is a more useful information flow than passing one controller between people.
Pilot
Maintains aircraft control and monitors flight status, separation, link condition and mission execution.
Observer terminal
Views supported camera feeds or split-screen information without gaining aircraft-control permission in AMAK mode.
Incident or asset team
Uses shared imagery, telemetry and target markers to support a field decision or inspection response.
Information sharing should still be designed around data security, account access, retention and organizational procedure. A second screen is helpful only when the team knows who may view the feed, who may create or edit a PinPoint and how operational decisions are recorded.
A‑Mesh vs GNSS-Denied Navigation: What Is the Difference?
GNSS and communications are separate dependencies. An aircraft may have a healthy controller link while satellite positioning is weak inside a structure. It may also have excellent GNSS outdoors while a building blocks the direct radio path to the controller.
Autel describes EVO Max as using high-precision visual navigation based on SLAM—simultaneous localization and mapping—to support positioning when satellite signals are obstructed or weak. That is the capability relevant to GNSS-denied navigation. A‑Mesh remains the communications and collaboration layer.
| Scenario | Primary technical need | Why |
|---|---|---|
| GNSS is healthy, but a building blocks the controller link | A‑Mesh relay may help | The problem is the communication path, not the aircraft’s satellite position. |
| The radio link is healthy, but GNSS disappears indoors | Visual SLAM is relevant | The aircraft needs visual positioning and navigation support; mesh networking does not replace GNSS. |
| GNSS is weak and the direct radio path is obstructed | Visual navigation + A‑Mesh may both matter | One technology supports positioning; the other supports communication and collaboration. |
How Visual SLAM Works With A‑Mesh
The EVO Max platform is interesting because several layers can work together. Autel’s marketing describes an autonomy engine for path planning and obstacle avoidance, multi-sensor environmental perception, Visual SLAM navigation and A‑Mesh networking. They should be evaluated as related but distinct systems.
From sensing to team collaboration
None of these layers makes the environment risk-free. Visual navigation depends on usable visual information and operating conditions. Obstacle sensing has detection limits. Route planning requires human review. Mesh nodes depend on radio geometry and power. A deployable system is the combination of hardware, software, trained crew, procedures and an authorized mission.
Where Does A‑Mesh Actually Matter?
The strongest use cases begin with a communication or team-coordination problem—not with the desire to operate multiple aircraft because the interface permits it.
Divide a search area or bridge terrain
Compatible aircraft may work different search segments while a lead node supports communication around terrain. The value is coverage flexibility and a common operating picture, subject to crew and regulatory limits.
Separate flight control from viewing
A pilot can retain control while an observer terminal views a supported camera feed and shared PinPoints help the response team reference the same target.
Work around complex structures
Buildings, plants, substations and terrain can obstruct a direct radio path. A planned relay position may change the link geometry, but it does not remove inspection-site hazards.
Coordinate aircraft and field information
Multiple viewpoints, aircraft status and target markers may improve situational awareness when the operating plan defines who flies, who observes and who acts on the information.
Does A‑Mesh Automatically Enable BVLOS in Canada?
No. A‑Mesh is a technical capability, not regulatory authorization. Transport Canada’s current Level 1 Complex framework permits certain lower-risk BVLOS operations only within defined conditions. The pilot needs a Level 1 Complex certificate, the operation must be conducted under an RPAS Operator Certificate, and the aircraft must meet the safety requirements for the exact operation. Lower-risk BVLOS is also limited by airspace, altitude, aerodrome distance and population-density conditions.
Transport Canada separately lists flying more than one drone BVLOS as a medium-complexity special operation. Its current guidance says an SFOC-RPAS is required for operations beyond the Basic, Advanced or Level 1 Complex rules. A purchase of two A‑Mesh-capable aircraft therefore does not create permission to fly both beyond visual line of sight.
Before using A‑Mesh in an operating concept, verify the exact number of aircraft, VLOS/BVLOS status, airspace, population environment, pilot qualifications, RPOC, safety-assurance status, crew plan and any SFOC requirement. Start with Transport Canada’s current rules, not a manufacturer use-case graphic.
A‑Mesh Limitations Enterprise Buyers Should Understand
- No unlimited communication range
- No automatic GNSS-denied navigation
- No automatic Canadian BVLOS authorization
- Functions can be firmware-dependent
- Node count may be version-dependent
- Controller roles must be confirmed
- Relay aircraft creates a mission dependency
- RTK compatibility must be checked
- Radio terrain and interference still matter
- Battery and contingency plans still matter
Autel’s 2024 V1.8 A‑Mesh guide is a useful example of why configuration evidence matters. It stated a two-aircraft and two-controller limit and said RTK was not compatible with A‑Mesh Control at that firmware stage. Treat those points as a dated configuration note—not an evergreen specification. Ask for current evidence for the exact Canadian aircraft, smart controller, application version, firmware and intended function.
Which SpeedyDrone Autel Platforms Support These Capabilities?
SpeedyDrone’s current Autel EVO Max Series collection lists two mission-oriented bundles built on the EVO Max flight platform. Choose by sensing requirement first; then confirm that the exact networking, controller and firmware configuration supports the intended operating concept.
Zoom + thermal
EVO MAX 4T XE Bundle
Start here when long-range visual detail, thermal observation and infrastructure inspection are the sensing priorities.
View 4T XE Bundle
Starlight + thermal
EVO MAX 4N Bundle
Start here when very-low-light observation, nighttime response and thermal awareness are the mission priorities.
View 4N BundleProduct availability, package contents, software access and supported functions can change. Use the linked SpeedyDrone pages for the current listings and request configuration confirmation before purchase.
What Should a Canadian Team Confirm Before Buying?
Do not start with “How many drones can we connect?” Start with the obstruction, data, coverage or coordination problem the operation must solve. Then test whether A‑Mesh meaningfully improves the workflow.
- Exact mission and operating environment
- Required visual, thermal or starlight payload
- Aircraft and Smart Controller versions
- Current firmware and application version
- A‑Mesh node and role limits
- RTK and A‑Mesh compatibility
- Relay location and lost-link response
- Expected video and telemetry consumers
- VLOS/BVLOS and multi-aircraft status
- Canadian authorization and crew requirements
- Acceptance test and failure scenarios
- Training, spares and technical support
Bottom Line
Autel A‑Mesh is best understood as a way to connect compatible EVO Max aircraft and terminals for relay, coordinated control and information sharing. Visual SLAM addresses a different problem: positioning and navigation when GNSS is degraded. The autonomy engine and environmental sensors add still more layers.
The platform becomes useful when those layers are matched to a defined mission, confirmed on the exact hardware and firmware, tested under realistic conditions and operated within Canadian rules. The buying question is not simply whether A‑Mesh sounds advanced. It is whether the network design solves a real communication or coordination constraint without adding unmanaged complexity.
Frequently Asked Questions
What is Autel A‑Mesh?
Autel A‑Mesh is a networking architecture for compatible EVO Max aircraft and ground terminals. It supports documented functions such as multi-aircraft control, relay operation, coordinated missions and information sharing. Available features depend on the exact configuration and software version.
Is A‑Mesh the same as GNSS-denied navigation?
No. A‑Mesh supports communications and collaboration between compatible nodes. Visual SLAM supports aircraft positioning and navigation when GNSS is weak, blocked or unavailable.
Can an EVO Max aircraft act as a radio relay?
Autel documents a relay workflow in which the Lead Aircraft is positioned to maintain communication and acts as a bridge between the Lead Controller and a Member Aircraft. Range and reliability still depend on the real radio environment, configuration and operating conditions.
Can one controller manage multiple EVO Max aircraft?
Autel documents A‑Mesh Control for selecting all aircraft, a Lead Aircraft or a Member Aircraft. Historical guidance and later manuals describe a two-aircraft team, but limits are version-dependent and must be confirmed for the exact aircraft, controller, application and firmware.
Does A‑Mesh make EVO Max a drone swarm?
Not in the broad autonomous-swarm sense. Autel documents networking, formation and coordinated polygon-mission functions. Those specific behaviours should not be generalized into decentralized swarm intelligence.
What is AMAK in Autel A‑Mesh?
AMAK means Autel Mobile Awareness Kit. Autel describes it as an additional controller that can synchronously view the Lead Controller’s screen and supported aircraft camera views without aircraft-control permission.
Does A‑Mesh automatically make BVLOS legal in Canada?
No. A‑Mesh is a technical capability, not operating authorization. Canadian BVLOS operations must fit the applicable Transport Canada category and requirements. Transport Canada currently lists flying more than one drone BVLOS as a medium-complexity special operation.
Which SpeedyDrone EVO Max model should I choose?
Choose the EVO MAX 4T XE Bundle when zoom plus thermal inspection is the priority. Choose the EVO MAX 4N Bundle when starlight-assisted low-light observation plus thermal imaging is the priority. Confirm current availability and the exact A‑Mesh configuration with SpeedyDrone before purchase.
What should be tested before an A‑Mesh deployment?
Test device linking, controller roles, relay placement, link quality, video and telemetry sharing, lost-link behaviour, battery contingencies and the intended mission route. Verify the exact firmware, application, RTK interaction and Canadian operating requirements.
Sources and further reading
- Autel Robotics: Introducing A‑Mesh Networking Technology with the EVO Max Series
- Autel Robotics: EVO Max Series overview
- Autel Robotics: EVO Max Series Multi-rotor Drone User Manual V1.2.5
- Transport Canada: Level 1 Complex operations
- Transport Canada: Get permission for special drone operations
- SpeedyDrone Canada: Autel EVO Max Series
Planning an EVO Max Networked Operation?
Send SpeedyDrone your mission, operating environment, required payload, aircraft count, controller plan and deployment timeline. We can help compare EVO Max configurations and identify the technical questions that should be confirmed before purchase.
Request an EVO Max Configuration Review Explore EVO Max Series
