Getting Started with DJI M210 - Able to connect but can't control thru FlytPilot

#1

Hi all. I’ve use the search bar, but nothing similar came up. So I decide to post this.

I was following this guide but I am stuck at the last part (DJI Simulation). I was able to control the simulation drone thru RC but not FlytPilot. I am in a building, do I need GPS to arm the simulation drone?

My build is:

  1. Nvidia Jetson TX2 with Ubuntu 16.04 and
  2. DJI M210

For OSDK, I have followed DJI ROS setup guide with advance sensing enable.

Attached are the run and start logs. Let me know if you need to know anything else. Please help, thanks.

Start Log

================== FlytOS Startup Log ================
Fri Feb 15 11:07:46 2019:	Launching initial Log Server - you can check logs at http:///logs
Fri Feb 15 11:07:47 2019:	FlytOS will try to auto-detect autopilot in these ports : /dev/ttyACM0, /dev/ttyUSB0, /dev/ttyUSB0, /dev/ttyGS0, udpin:0.0.0.0:14550, /dev/ttyTHS2, /dev/ttyTHS3, 
Fri Feb 15 11:07:47 2019:	FlytOS will try to auto-detect autopilot in the above ports with baudrate: 115200, 921600, 230400, 57600, 
Fri Feb 15 11:07:47 2019:	Refer http://docs.flytbase.com/docs/FlytOS/Debugging/FAQ.html, if your serial port or baudrate is not included in the list. Also notify us at http://forums.flytbase.com/ so that we add it to our default list
Fri Feb 15 11:07:47 2019:	PX4/APM: Trying to open /dev/ttyACM0 with baudrate 115200
Fri Feb 15 11:07:47 2019:	[autopilot detect] check if connection to autopilot is indeed on port: /dev/ttyACM0
Fri Feb 15 11:07:47 2019:	[autopilot detect] visit http://docs.flytbase.com/docs/FlytOS/Debugging/FAQ.html to find how to configure port in FlytOS
Fri Feb 15 11:07:47 2019:	DJI: Trying to open /dev/ttyUSB0 with baudrate 921600
Fri Feb 15 11:07:48 2019:	Detected serial port: /dev/ttyUSB0 at baudrate: 921600
Fri Feb 15 11:07:48 2019:	Detected autopilot: dji
Fri Feb 15 11:07:48 2019:	DJI autopilot detected
Fri Feb 15 11:07:48 2019:	Checking internet availability...
Fri Feb 15 11:07:48 2019:	Internet connection established
Fri Feb 15 11:07:48 2019:	Checking license on server..
Fri Feb 15 11:07:50 2019:	Check license status: 200 OK, Response: True
Fri Feb 15 11:07:51 2019:	License activation is: True
Fri Feb 15 11:07:51 2019:	Auto-Update: ON
Fri Feb 15 11:07:51 2019:	Download-Ready: False
Fri Feb 15 11:07:51 2019:	Downloaded version: null
Fri Feb 15 11:07:51 2019:	Blacklisted version: 
Fri Feb 15 11:07:51 2019:	Starting FlytOS...
Fri Feb 15 11:07:51 2019:	Checking for new updates
Fri Feb 15 11:07:51 2019:	Checking internet availability...
Fri Feb 15 11:07:51 2019:	Internet connection established
Fri Feb 15 11:07:52 2019:	Checking license on server..
Fri Feb 15 11:07:55 2019:	Check license status: 200 OK, Response: True
Fri Feb 15 11:07:55 2019:	Checking for updates on server..
Fri Feb 15 11:07:57 2019:	Check updates status: 200 OK, Response: 1.56
Fri Feb 15 11:07:57 2019:	FlytOS version is already up-to-date.
Fri Feb 15 11:07:58 2019:	Updating server with current FlytOS version:1.56
Fri Feb 15 11:08:00 2019:	Set update status: 200 OK, Response: True
Fri Feb 15 11:08:00 2019:	Exiting Startup.
========================================================

Run Log flyt_runlogs_2019-02-15_10-53.log (106.8 KB)

#2

Hello @hann,

Sorry for the delayed response.
Are you still facing this issue?

while starting up the DJI simulator, what exact latitude and longitude did you specify?
I will try to replicate this issue on our end, in the meantime, can you please try with latitude and longitude values outside of China?

#3

Howdy @srv-admin. Here is some update.

  1. Yesterday I got the chance to test this again in an open field where GPS signal is abundance (I got 6000+ flux/4.6m error using GPS Status app). However, after going through the Simulation again, I have no luck. In the run logs, I can see commands received but it needs GPS Lock. I’ll attach both logs below.

  2. I have tried both, default china coordinate as well as local. No change. I’m using this (3.140426, 101.6298253).

  3. I also try arming the M210 alone (no onboard computer attached) at the exact spot, no problem. It got “Ready to go (GPS)”, 11+ Satellite and full bar GPS on the DJI Go 4.

  4. One more thing, on the FlytConsole, what does Satelite 4 means (refer picture below)? Is it 4 out of 5 or something?

Hope this gives some clues.

Startup Logs
================== FlytOS Startup Log ================
Tue Feb 19 10:50:50 2019: Launching initial Log Server - you can check logs at http:///logs
Tue Feb 19 10:50:52 2019: FlytOS will try to auto-detect autopilot in these ports : /dev/ttyACM0, /dev/ttyUSB0, /dev/ttyUSB0, /dev/ttyGS0, udpin:0.0.0.0:14550, /dev/ttyTHS2, /dev/ttyTHS3,
Tue Feb 19 10:50:52 2019: FlytOS will try to auto-detect autopilot in the above ports with baudrate: 115200, 921600, 230400, 57600,
Tue Feb 19 10:50:52 2019: Refer http://docs.flytbase.com/docs/FlytOS/Debugging/FAQ.html, if your serial port or baudrate is not included in the list. Also notify us at http://forums.flytbase.com/ so that we add it to our default list
Tue Feb 19 10:50:52 2019: PX4/APM: Trying to open /dev/ttyACM0 with baudrate 115200
Tue Feb 19 10:50:52 2019: [autopilot detect] check if connection to autopilot is indeed on port: /dev/ttyACM0
Tue Feb 19 10:50:52 2019: [autopilot detect] visit http://docs.flytbase.com/docs/FlytOS/Debugging/FAQ.html to find how to configure port in FlytOS
Tue Feb 19 10:50:52 2019: DJI: Trying to open /dev/ttyUSB0 with baudrate 921600
Tue Feb 19 10:50:53 2019: Detected serial port: /dev/ttyUSB0 at baudrate: 921600
Tue Feb 19 10:50:53 2019: Detected autopilot: dji
Tue Feb 19 10:50:53 2019: DJI autopilot detected
Tue Feb 19 10:50:53 2019: Checking internet availability…
Tue Feb 19 10:50:58 2019: Internet connection established
Tue Feb 19 10:50:59 2019: Checking license on server…
Tue Feb 19 10:51:11 2019: Exception while checking license on server: HTTPSConnectionPool(host=‘my.flytbase.com’, port=443): Read timed out. (read timeout=10)
Tue Feb 19 10:51:11 2019: License validity could not be confirmed on the server
Tue Feb 19 10:51:12 2019: License activation is: True
Tue Feb 19 10:51:12 2019: Auto-Update: ON
Tue Feb 19 10:51:12 2019: Download-Ready: False
Tue Feb 19 10:51:12 2019: Downloaded version: null
Tue Feb 19 10:51:12 2019: Blacklisted version:
Tue Feb 19 10:51:12 2019: Starting FlytOS…
Tue Feb 19 10:51:13 2019: Checking for new updates
Tue Feb 19 10:51:13 2019: Checking internet availability…
Tue Feb 19 10:51:13 2019: Internet connection established
Tue Feb 19 10:51:14 2019: Checking license on server…
Tue Feb 19 10:51:22 2019: Check license status: 200 OK, Response: True
Tue Feb 19 10:51:23 2019: Checking for updates on server…
Tue Feb 19 10:51:24 2019: Check updates status: 200 OK, Response: 1.56
Tue Feb 19 10:51:24 2019: FlytOS version is already up-to-date.
Tue Feb 19 10:51:25 2019: Updating server with current FlytOS version:1.56
Tue Feb 19 10:51:27 2019: Set update status: 200 OK, Response: True
Tue Feb 19 10:51:27 2019: Exiting Startup.
========================================================

Run Logs: flyt_runlogs_2019-02-19_10-50.log (151.4 KB)

Pic from the RC and FlytConsole:


Note the signal from RC and No GPS Lock on the FlytConsole.

#4

Thanks for sharing such a detailed analysis.
We are currently trying to replicate this on our end. You should get a response from us in a day.

#5

That is awesome. Hope to hear from you guys very soon. @srv-admin

#6

We have identified the problem.
In other DJI platforms, DJI provides the health of GPS fix. We use this data to detect if the GPS reported by DJI is valid or not. Unfortunately, for DJI M210, they are reporting an incorrect value of the GPS fix because of which we are suggesting that the Position data is not valid.

We are working on trying to look for a bypass or fix this issue. Expect a response from us soon.

#7

Good to hear that @srv-admin and I appreciate your prompt response. Please keep me posted. Thanks.

#8

We are coordinating with the DJI SDK team to get a fix on this issue.
In the meantime, I have found a way out.

As soon as you MANUALLY arm the drone via RC, the DJI starts sending valid data.
You can then use FlytOS to control the drone.

We saw this behaviour in the DJI simulator. Hence, I would suggest testing this on the simulator itself.
We will soon try to test this on a real drone.

One more thing, on the FlytConsole, what does Satelite 4 means (refer picture below)? Is it 4 out of 5 or something?
In the case of DJI, Satellite 4 suggests the quality of GPS lock from 0-5, with 5 being the best quality.

#9

That’s interesting. Do you mean the M210 gives different kind of data in simulation compared to actual? I will give this another try sometime later. But from my previous trials, I managed to manually arm the M210 using RC in simulation, however taking control using the FlytPilot gave GPS Lock error in the run logs. That’s why I decided to test this outdoor where the GPS is abundance. Am I missing some silly steps here? Like pressing a button/change rc mode etc.? I don’t know. Lol.

My M210 setup for simulation:

  1. M210 connected to a Laptop running DJI Assistant 2 using USB-USB cable. M210 mode switch to the most left (Laptop).
  2. TX2 with FlytOS is connected to an office wifi router and to the M210 using USB-TTL cable.
  3. Laptop connected to same office wifi router.
  4. FlytConsole shows valid connection (green “Connected”, voltage, HUD, etc).

Upon simulation and manually armed using RC, the HUD/compass give response. However, like I said before, controlling the M210 in simulation using FlytPilot (I entered the TX2 IP address and get valid connection) gave me the GPS Lock error as per run logs attached above. Anything wrong with my setup?

#10

All the steps seems OK.
Thank you for mentioning the steps.
Let me get back to you on this by the end of day.

Let’s focus on first getting the it up and running with the DJI simulator.

#11

Hi @srv-admin,

It has been a while. Do you have any update on this?

#12

Hi @hann

Did you try following my above steps? Is it still not working in simulator?
We are in constant touch with DJI SDK team, they are trying to replicate and fix it on their end.

#13

Hi @srv-admin,

Currently, the M210 is occupied by someone else. So, I am not be able to retry. But I will as soon as I possibly can.

From my previous test, I did manually arm using RC in the Simulation, but I didn’t get GPS Lock (However, HUD and compass are showing the right thing). So any command I gave will show No GPS Lock error in the run logs.

When you say,

does that mean using FlytPilot as well?

Thanks
Hanif

#14

Yes.

DJI Support team has not been of much help to us. I will keep probing them.

#15

Hi @srv-admin,

Since you have mentioned this earlier, is it still possible to bypass the GPS Lock? What are the consequences?

Update: I managed to retest this on the DJI Simulation, the drone can be armed MANUALLY using RC, but controlling using FlytPilot/web-based Joystick isn’t possible (No GPS Lock, Satellite shows only 5 unit, RC shows 15).

Thanks
Hanif

#16

Sorry for the delayed response. Please allow me to get back to you on this in a day or two.

#17

Hi @srv-admin,

Just another update: https://i.imgur.com/DdfKWuw.mp4

As you can see, I can manually arm and control the aircraft using RC, but unfortunately controlling using FlytPilot seems impossible. Note the red “No GPS Lock” in the FlytConsole. This can also be seen in the run logs where the FlytOS can’t take command since there is no GPS Lock.

#18

Hey sorry for the delays from our end. We couldn’t get further into this since last few days. Please allow us some more time to get this fixed.

Thanks for your patience.

#19

Hi @srv-admin,

Have you got the chance to look into this?

Thanks.

#20

Seems like it got fixed in the latest version of DJI M210 Firmware. We are not being able to replicate this at our end (with the latest firmware). Can you please try again.