Intelli-G compatibility with DJI M600 (or any DJI A3/N3 + LB2) platforms
- F-Port (Shutter) to ADC4 connection is only necessary for Scenario E - Photogrammetry (geo-tagging) missions, using D-RTK/DJI-GPS
By connecting Intelli-G to the DJI A3/N3 SDK port (see DJI A3 setup video), any of the following main usage scenarios can be set up in conjunction with DJI M600 or any other platform controlled by DJI A3/N3 + LB2:
- Scenario A: Non-DJI cameras and DJI Ronin-MX, using non-DJI remote control systems
- Scenario B: Non-DJI cameras, using the DJI LB2 slave remote (scenarios B and C can work simultaneously)
- Scenario C: Non-DJI gimbals (AlexMos, Gremsy, Movi ...), using the DJI LB2 slave remote (scenarios B and C can work simultaneously)
- NEW & Recommended - Scenario D: Non-DJI cameras and non-DJI gimbals (AlexMos, Gremsy, Movi ...), using DJI Expansion Kit
- NEW - Scenario E: Photogrammetry (geo-tagging) missions, using D-RTK/DJI-GPS
|3rd party cameras||DJI gimbal (DJI Ronin MX)||3rd party gimbal (AlexMos, Gremsy, Movi, etc.)|
|3rd party RC system (Futaba, FrSky)||Intelli-G Scenario A||Intelli-G Scenario A||Direct connection to RC receiver|
|DJI LB2 single remote||N/A||DJI Internal||N/A|
|DJI LB2 two remotes||Intelli-G Scenario B||DJI Internal||Intelli-G Scenario C (scenarios B and C can work simultaneously)|
|DJI LB2 remote and expansion kit||Intelli-G Scenario D||DJI Internal||Intelli-G Scenario D|
Scenario A - Non-DJI cameras and DJI Ronin-MX, using non-DJI remotes
To solve the 2.4Ghz interference issues you can also use RC modules such as TBS Crossfire Transmitter and Receiver, which can be easily attached to most of existing RC systems. These modules are inexpensive and ensure a great deal of flexibility. Once you have such a solution you will no longer be affected by interferences.
Scenario B - Non-DJI cameras, using DJI LB2 slave remote
Scenario C - Non-DJI gimbals (AlexMos, Gremsy, Movi ...), using DJI LB2 slave remote
Scenario D - Non-DJI cameras and non-DJI gimbals (AlexMos, Gremsy, Movi ...), using DJI Expansion Kit
Until recently it was impossible to use a single DJI LB2 remote to control Intelli-G, since it implied running our specialized app (Intelli-GO) instead of DJI GO, in order to connect to the SDK of DJI A3 flight controller.
Intelli-GO can only be run on the slave remote since DJI GO is needed to fly the aircraft. More details on this solution can be found in scenarios B and C (links).
However, it is now possible to use a new approach by making use of the DJI Expansion kit.
The DJI Expansion kit is the reason why DJI did not enable the F-Ports on A3 flight controller (as they had on their previous A2 flight controller). Check the discussion on this thread (https://forum.dji.com/thread-85188-1-1.html – search for word "port"). It shows that the F-ports are re-enabled in case you have such an expansion kit. This means that, by using the expansion kit on a standard DJI LB2 remote, you can map the extra channels to Intelli-G. This approach is also suitable in single operator scenario.
This new setup does not interfere at all with the standard use of DJI remotes and thus, the slave remote can be used as envisioned by DJI (including for viewing purposes).
For a more real-feel, you can check the Intelli-G Tutorial that emphasizes the use of Intelli-G in combination with the DJI Expansion Kit: https://youtu.be/_sS4io_kym0.
Also, here’s a video on mapping and usage of the DJI Expansion Kit (on any LB2 remote): https://youtu.be/QWDZPb1CeMM
Scenario E - Photogrammetry (geo-tagging) missions, using D-RTK/DJI-GPS
This is a somewhat different usage of DJI M600 (or any DJI A3/N3 + LB2) platforms, and thus, detailed in a separate article (www.intelli-g.com/RTK).