- Joined
- Apr 14, 2015
- Messages
- 294
- Reaction score
- 36
- Age
- 75
I was curious.Out of curiosity, what kind of antenna caused this and why flying close to it?
I don't know type of antenna. It seems dipoles array antenna. Around 6 meters square size
I was curious.Out of curiosity, what kind of antenna caused this and why flying close to it?
Out of curiosity, what kind of antenna caused this and why flying close to it?
The moment when the copter entered inside the rf beam was not logged by the controller, this is the reason why you don't see abnormal data on the log. As you can see the copter reaches around 10 meters, then nothing else was logged.
I don't know, at 40meters distance from that antenna, the influence of magnetic field is strong. We can assume the radiation level was around 70dBm per square meter, may be less. I don't know
Another important detail we're not taking in to account is the fact that the transmission is pulsed and the 70dBm (?) per square meter was present for (only) around 60milliseconds (then the antenna interference pointed another direction). So this short period of interference generated the problem....
I was curious.
I don't know type of antenna. It seems dipoles array antenna. Around 6 meters square size
No. I mean that, if it was not a problem of the processor chip, during the uncontrolled descending phase we should see sensors data logged. The fact that the descending phase was not logged, could be related to a failed write to flash memory. Do you think it's easier to jam a processor or a lvds serial line?Are you saying that you believe that the flight continued (not including the uncontrolled descent) beyond the end of the log and, if so, how do you know that?
Assumptions based on my experience and internet readingsAre these statements based on measurements or just assumptions?
No. I mean that, if it was not a problem of the processor chip, during the uncontrolled descending phase we should see sensors data logged. The fact that the descending phase was not logged, could be related to a failed write to flash memory. Do you think it's easier to jam a processor or a lvds serial line?
May be you're right.Your hypothesis, if I understand it correctly, is sudden disruption of sensor data and a sudden end to logging, but with the FC still functioning, which seems improbable since it invokes at least two independent failures. FC shutdown only requires one failure.
I also don't even understand what evidence that makes you think that the flight continued after the log ended. If the FC shut down and the descent was uncontrolled then there would be no record of it.
We use essential cookies to make this site work, and optional cookies to enhance your experience.