Nope. There’s a similar issue here in the uk/eu with the drone category markings and the new regulations coming in. DJI didn’t incorporate the new rule requirements into the Air2, which is why I didn’t buy one. You can still fly it, but in a few years the regulations will be different, so I’d have to buy again. Plus, the resale will be much lower than in previous years. Thankfully, none of this affects the sub 250g rules so the Mini’s will be popular.
Would you buy an M2P at roughly it’s present full price now (roughly $1600)with remote id on distant horizon?
Great summary and analysis. I agree with your assessment. I don’t think that power will be a concern at all. It is a very small text file transmitted once per sec. Since the controller and drone are already transmitting and receiving continuously at a very high data rate this extra should be inconsequential.First, here is a link to a PDF for the executive summary of the remote ID rule: Click me
Second, I am a new drone pilot that just took the plunge and purchased an M2P, and I don't regret it.
Third, while I freely admit that I am a new drone pilot, I am not new to IT (professional software engineer) and I've spent time digging in to the specs and capabilities of the equipment. Based on that, I strongly believe that we have nothing to worry about. Before I state why I feel that way, here's the verbiage from section 1 of the summary:
•Broadcasts remote ID messages directly from the UA via radio frequency broadcast (likelyWi-Fi or Bluetooth technology), and broadcast will be compatible with existing personal wireless devices.
•Standard Remote ID message includes: UA ID (serial number of UA or session ID); latitude/longitude, altitude, and velocity of UA; latitude/longitude and altitude of Control Station; emergency status; and time mark.
•Remote ID message will be available to most personal wireless devices within range of the broadcast; however, correlating the serial number or session ID with the registrationdatabase will be limited to the FAA and can be made available to authorized law enforcement and national security personnel upon request.
•Range of the remote ID broadcast may vary, as each UA must be designed to maximize the range at which the broadcast can be received.
Based on what I have learned about the M2P, I think it is safe to say that the hardware is already there, so it should come down to just programming. It wouldn't surprise me to learn that most of the code is already there in the later firmware updates and just has to be enabled and tweaked as a needed to provide the necessary information; the manufacturers knew this was coming. I think that the worst case scenario would be a "motherboard" upgrade to the drone itself so that we would not have to mount an exterior device.
Having said all of that, I think our biggest concern is going to be power consumption and the impact on flight time. Indeed, the motors use the bulk of the power, but we'll now be transmitting more information and at regular intervals.
Dan
Hi Ken, thanks for the reply. If its just a small amount of info once-per-second then I agree that it should be negligible.Great summary and analysis. I agree with your assessment. I don’t think that power will be a concern at all. It is a very small text file transmitted once per sec. Since the controller and drone are already transmitting and receiving continuously at a very high data rate this extra should be inconsequential.
Sure, but I'd hope they are also interested in customer retention. This situation reminds me of the early days of HD video before the standards had been completed. Mitsubishi was making rear-projection HD TV's at that time and stated that once the standards were formalized that they "promised" to offer a "module" that could be retrofitted for a reasonable cost - it became know as the "Promise module" with a price tag of right at $1000 circa 2003. They really PO'd a lot of people, including me, and I haven't purchased another Mitsubishi product since.I don’t really trust DJI would make the feature available for the M2P even if it is possible. Their interest is to sell new drones.
I think DJI would enable RID for any drone that can transmit a Wi-Fi Broadcast message. If you own a Mavic and they do enable RID, you will be looking for a new drone. You will already be unhappy with DJI and will have a bias for any brand that is not DJI. They would want to avoid that. They would rather have you buy a next gen Mavic when your current one is done or dead then take the chance that you would buy a drone from a competitor.I don’t really trust DJI would make the feature available for the M2P even if it is possible. Their interest is to sell new drones.
First, here is a link to a PDF for the executive summary of the remote ID rule: Click me
Second, I am a new drone pilot that just took the plunge and purchased an M2P, and I don't regret it.
Third, while I freely admit that I am a new drone pilot, I am not new to IT (professional software engineer) and I've spent time digging in to the specs and capabilities of the equipment. Based on that, I strongly believe that we have nothing to worry about. Before I state why I feel that way, here's the verbiage from section 1 of the summary:
•Broadcasts remote ID messages directly from the UA via radio frequency broadcast (likelyWi-Fi or Bluetooth technology), and broadcast will be compatible with existing personal wireless devices.
•Standard Remote ID message includes: UA ID (serial number of UA or session ID); latitude/longitude, altitude, and velocity of UA; latitude/longitude and altitude of Control Station; emergency status; and time mark.
•Remote ID message will be available to most personal wireless devices within range of the broadcast; however, correlating the serial number or session ID with the registrationdatabase will be limited to the FAA and can be made available to authorized law enforcement and national security personnel upon request.
•Range of the remote ID broadcast may vary, as each UA must be designed to maximize the range at which the broadcast can be received.
Based on what I have learned about the M2P, I think it is safe to say that the hardware is already there, so it should come down to just programming. It wouldn't surprise me to learn that most of the code is already there in the later firmware updates and just has to be enabled and tweaked as a needed to provide the necessary information; the manufacturers knew this was coming. I think that the worst case scenario would be a "motherboard" upgrade to the drone itself so that we would not have to mount an exterior device.
Having said all of that, I think our biggest concern is going to be power consumption and the impact on flight time. Indeed, the motors use the bulk of the power, but we'll now be transmitting more information and at regular intervals.
Dan
We use essential cookies to make this site work, and optional cookies to enhance your experience.