brett8883
Well-Known Member
Exactly.My understanding so far has been to overcome interference in areas dense with competing signals.
Exactly.My understanding so far has been to overcome interference in areas dense with competing signals.
After watching some comparisons, I don't think the main reason to get the RC Pro is the difference in transmission. Currently, I think the difference, if any, is negligible. I'm not sure if that will, or can, change with future firmware upgrades.
The added functionality is huge.For me, the primary reason for using the RC Pro is that it is more functional and feels better in my hands when flying, compared to the toy-like standard controller.
I have been using iPad Minis (4 & 5) with my Phantoms for years, and do not like the small screen. I may have to rig up a holder to mount a screen from the HDMI output (which defeats the all-in-one concept).
It is very disappointing not to have a decent controller to use with my iPad Mini 5...
I would argue longer range means stronger penetration for trees at least. But someone smarter here with that stuff could correct me.The stronger battery goes hand in hand with Longer range.
It also allows you to fly In More Extreme winds much longer also, , the Range is just a selling point that everyone loves as it is to a fast car. Eyes light up at 10 miles , but the reality is 3000 ft for most missions.
Phantomrain.org
Gear to fly in the Rain ,Capture the Storm.
Its all to do with progress! This guy explains it well, I believe he designs RF systems or repairs them, either way he has but this together to explain.Still this bandwith issue is somehow not explained (as also mentioned in the comments) and therefore think it's not the true reason:
Transmission quality
So why should there be a bandwith issue with the SC and the Air 2S, when they use they same specification of raw data? I can see, why 1080p/60 is not possible with the M3, but not why the SC is claimed to have a problem with stepping down. There should be some fallback mode to 1080p/30 and I am sure DJI could do that (as this guy points out several times, it's all based on software).
- M2P: 1080p/30 12 MBit/s with SC
- Air 2S: 1080p/30 12 MBit/s with SC (and addtional 10 ms latency)
- M3: 1080p/60 low latency
And why the heck is the RC Pro not compatible with the Air 2S?
That doesn't make sense at all, but if DJI just willingly intends so.
I watched that video of course before and especially asked the question to him in the comments with no reply yet.Its all to do with progress! This guy explains it well, I believe he designs RF systems or repairs them, either way he has but this together to explain.
The whole Ocusync thing is very confusing IMO as they refer to the video transmission & the control/telemetry as Occusync ‘the overall system’ but they implement different versions of it at the same time! O2 for telemetry and control and O3+ for the video return.I watched that video of course before and especially asked the question to him in the comments with no reply yet.
Fact is, what he also explained in detail: the SC has the capability to run Air 2S but says, it's not working well (tried it with a friend's drone, never had a problem). It's SDR and while DJI implements P1 and S1 here and there, the only reason for the SC not working with the M3 may be indeed the bandwith needed for 1080p/60 low latency. That however could be solved with a reduced transmission of 1080p/30 12 MBit/s I guess, like the predecessors use. You remember, it's all SDR.
So the question is, why he suspects a bandwith limit with the Air 2S already (using the same transmitting quality) in special. Is it really based on the chips, is it sloppy software development ... But probably only DJI really knows ... or maybe not and they are just as confused as consumers with their back and forth in compatibility.![]()
Can you clarify the "flying backwards after a certain point" part? I'm intrigued.He didn't know that it's best to return flying backwards after a certain point and he was not nearly high enough.
You'll get even more with the RC-Pro, because it offers 4x the power output over the RC-N1.With the latest firmwares, the RC-N1 will now receive a little "update" when linking it to a drone. It tells the RC-N1 which protocol to use, O2, O3, or O3+, depending on the aircraft. That hasn't always been the case, until recently. I flew my A2S with my RC-N1 today for the 1st time since it is O3 capable, and I got considerably more distance than before flying in the same area. A mile and a half, with plenty of interference around...
Works fine with mine, but mine was purchased for the M3, rather than bought in the discounted A2S Combo bundle for only $550, since they didn't include the RC-N1 controller. Was yours part of that bundle? It's likely a FW update miscue. The hardware is identical. It just needed a FW update to make it dual compatible, and then it runs a small FW patch each time you change from the A2S to the M3 and back again. The other bug was changing the drone overwrites the settings for the C1 and C2 buttons back to their defaults.I would if I could. It won't stay connected to my A2S which is a known issue for some users. Mine is at DJI right now. Anxious to see what a working one is like.
Mine was bought standalone, I believe with the .01x (M3) firmware installed. I remember having to upgrade it to the .03x (A2s) firmware.Works fine with mine, but mine was purchased for the M3, rather than bought in the discounted A2S Combo bundle for only $550, since they didn't include the RC-N1 controller. Was yours part of that bundle? It's likely a FW update miscue. The hardware is identical. It just needed a FW update to make it dual compatible, and then it runs a small FW patch each time you change from the A2S to the M3 and back again. The other bug was changing the drone overwrites the settings for the C1 and C2 buttons back to their defaults.
.
We use essential cookies to make this site work, and optional cookies to enhance your experience.