Agreed,
Apart from an issue being FW regionally specific (it appears too far spread however) due to DJI’s fly constraints around the world as I do believe DJI has to accommodate specific rules and reg’s with specific regionally FW’s
It also could be.........During MA's production runs, their purchasing dept brought in/allowed in IC's that manufacturing ran where the chip changed die’s or something, a rev/production lot numbers changed and a change(this) happened mid run (hence first run MA's seem ok, mine). A tolerance that DJI might have designed within slipped out of a window somewhere somehow due to a inadvertant IC change.
Sometimes with mixed batchs of a certain "SAME" IC as in the proposed above case, some of them won’t run properly under the exact same or similar code/s that the others do/did during beta testing.
I say this only because I used to work in sustaining engineering and dealt with this a few times in my life. I’m not saying it is happening with DJI specifically, just saying it happens and it’s happened to me a few times.
If this or similar is the case, eng is trying (hence the loooong silence at this point) to indentify what chip/s rev/lot #’s isn't working properly under this and/or the various latest FW’s, how many went out the door and are looking to either re-write the FW so it globally is compatible with all the chips OR…..
Perhaps the chips are simply bad and are too far out of spec and won't run properly under ANY code. In this last case, there most likely is no work-around and they have a BIG problem!! They'll have to recall and replace all of them and someone in purchasing gets fired........
Total guess however, perhaps it's all pilot error.
|