AerobotROI
lvl.1
Italy
Offline
|
Hi all,
I'm really disappointed by our new M210 RTK V2. This is obviously NOT an enterprise solution. I think we should formally notify to DJI a very urget - and definitive - solution to the many issues this system has.
My short list is the following:
- D-RTK mobile station is NOT stable. Also, it's useful when used with just one RC, or when used to contrast interference, or if you need to PPK BUT just using X7 (not working with XT2).
- RTK with mobile station does not save RTK EXIF data if shooting manually (DJI, it happens when you make inspections, are you aware of this?), and it works with JUST ONE RC linked.
- If you need to work with two RCs - which is mandatory, especially for inspections) you CANNOT use D-RTK V2 to mitigate interferences, so you can work with simple GPS or link to local nRTK, losing other RTK benefits.
- By the way, notice that D-RTK V2 is for Matrice ONLY, so it won't work with Phantom RTK.
- Anyway, local nRTK does NOT store RTK positioning in images EXIF data.
- About shooting interval, the X7 camera is really, really, really slow when shooting in jpeg (both automatic trigger from mission planning, and manual triggering), actually making the X7 NOT usable for mapping. Using RAW files is even worse, of course. Our X7 is fairly fast when used on an inspire 2 (saving on microSD, NOT SSD).
- XT2 camera DOES NOT store ECEF data ( position and rotation of the sensor) on EXIF! This is really bad! We use ContextCapture for aerotriangulation, the software cannot AT XT2 images because of this lack. This is unacceptable.
- Also, the XT2 is a little slow when shooting (I mean shooting interval).
- When we plan a mission using DJI Pilot and the XT2, we cannot fly lower than 25 metres.
- Why the Phantom 4 Pro with GS PRO follows precisely the planned line, while the M210 RTK V2 with DJI Pilot planning moves from the planned grid?
- Please be aware that front left motor is always hotter than others, because it works more due to the left only support when using the X7 or the XT2. This obviously causes long term issues, since a motor which works more than others, it will have problems earlier. And likely it will have issues while flying. And it's a quad, you make your conclusions.
- CrystalSky is a close device, which is unreasonable. So cannot install the apps with features that DJI should include as default for enterprise clients. Actually, for DJI, we are NOT enterprise clients, we are richer clients who can pay more for these toys.
- Cameras are not supported by default by DJI Pilot Mission planning section. DJI GS PRO supports M210 RTK, but does not use RTK data, and does not include cameras as default.
- CrystalSky Ultra is HOT. I hope it will work in summer.
- Second RC, the one for payload operator, CANNOT review shot images and cannot control some aircraft options which could actually be useful when working with two persons on the field. As an example, the pilot in command may ask to the operator to turn off proximity sensors to get closer to subjects while inspectioning, but this is not possible.
- Second RC often misses link to the aircraft, resulting in time lost on the field.
And we could write even more.
I want to return this toy system. I would suggest to professionals to switch to Intel, Microdrones or others. Despite some minor complications (i.e. images shot with Falcon must be post linked to the flight mission data for EXIF registration, but it's a quick operation on the PC), they are professional platforms.
Is there anyone on my side? Are you really happy about your purchase?
|
|