pedzsan
lvl.4
Flight distance : 153625 ft
United States
Offline
|
So... this has been my experience.
TL; DR -- get a PC.
On an M1 Mac running Ventura, I got it "working" but not really. As stated in my update here, it worked with the Smart Controller that came with my Mavic 3 Cine but did not work with the FPV Controller nor the DJI Motion Controller (the first one). It appears to be a problem with Apple's USB driver below the point that the 3rd party kernel extensions can reach. There are two reasons for my belief.
1) With the Smart Controller, even before it was "working" there were signs that the Apple laptop saw something. There would be a prompt asking if I wanted to allow it to connect. But with the FPV controller and the Motion Controller, the Apple laptop doesn't do anything when they are plugged in.
2) The exact same situation with Parallels running a virtual PC. When the Smart Controller is plugged in, the Apple laptop as well as the virtual Windows machine "see" something. But when the other two controllers are plugged in, neither one do anything at all.
I got a super cheap $200 HP Windows 11 laptop and painfully struggled through the MS and HP horrors -- my god these things are SO broken is so many ways... but anyhow, I finally got DJI Assistant 2 to run on the new Windows 11 laptop and I plugged in my FPV controller and it worked just like it is suppose to. I "activated" it and then updated the firmware and finally got it linked with my Avata.
I'm a low level driver person but I don't know squat about USB and its protocol but my guess is that the Smart controller indicates that it is a different type of device in USB terms than the two FPV controllers and the Apple drive ignores the traffic from the FPV controller -- which seems extremely unwise in the USB world but I've actually had similar problems before. The iPhone will see USB headphones that have a microphone but it will not see just a USB microphone.
|
|