Pull_Up said:
The NAZA inside is certainly stickered up differently to the standard one (It says "Your Flying Camera" on it, no reference to Naza). Why they would need to differentiate Vision NAZAs from others in the facotry if they were bang-on identical hardware I don't know - other than them wanting consistent branding, even under the lid?
I can think of a reason why they would have them labeled differently, especially in the factory

my v1 has a "standard" naza-m but it also has a small "phantom" sticker on the side of it . . . My guess is they have firmwares with MINOR differences, purely to limit features or functions. Apple would do a similar thing with iPods/iPhones and iPads as they may run the same OS, but apple will allow an iPhone to make calls, but they won't for an iPad (despite the fact it's possible with the hardware).
I have some hunches about why certain things have been done the way they have, but without cracking the firmware of (any) naza, I'm unable to prove anything! I'm getting more and more tempted to buy a V2 or vision, purely to hack it up (first thing on my list would be running 3rd party batteries

). The v2 has the ability to be controlled via a signal NOT sent from the traditional receiver (panoramic photos make the vision yaw (???) ) and the "waypoint" feature for the naza v2 (specifically the vision) still hasn't been released as yet. . . .
Pretty much every car these days has an OBD2 port, this allows access to the ECU via a CAN-Bus style connection, sounds good! A university in America done some testing etc, and found that they could (with basic hardware) wirelessly connect to a "target" vehicle, and by "Spoofing" the data on the CAN they were able to control EVERYTHING in the car, from wipers to air-con, engine rpm and full control on brakes (force on and prevent from working!!!), google car shark

interesting read.
What if I told you that all current vision owners are Beta testing DJI's latest additional feature! I'm assuming that the vision is using the CAN to send control signals to the naza, this is a pretty cool feature, and opens up the door for follow me modes and other features etc. but before you implemented it fully, you would want to be sure it's not prove to bugs!
A simple way to do this would be to implement it on only one channel, and make sure that channel responds 100% even time that action is called upon (if it failed often, we'd have a splattering of "my panoramic photos don't work right" style threads). Now all this would require minor differences in the firmwares (the vision naza has to know it is aloud to yaw when the request comes in via CAN, but for now a v2 can't). As for the critical flight algorithms (direct motor speed control), IOC, RTH etc will be identical from the v1, vision and v2. This is why "Fly-always" still occur.