Desperately need help analysing log files!!

[whizz101]

[wangyeee]

[whizz101]

Looks like it's time for an AQ7......with increased EMI hardening over the 6!

[JussiH]

I am almost sure that the root cause of your problem is not EMI.

The reason "EMI hardening" was relevant on AQ6 was to protect the Analog voltages from interference. This was important to make sure that data did not get corrupted by noise. The term "EMI hardened IMU" basically just means that signals and reference voltages was run through som Opamps to stabilize them. Once you mount a DIMU on a AQ6, the sensors basically connects directly to the MCU´s SPI pins.

In a full digital IMU like on M4, EMI is only a problem if it skews data during transmission. A noisy 1 or 0 is still a 1 or 0

[wangyeee]

I do believe the power supply of AIMU is well filtered. And since the DIMU is just on top of AIMU, I assume that they shares same power supply. That's why I said "the DIMU will benefit from it".

The MPU6000 is analog gyro/accel integrated with ADC, signal processing and others. The SPI bus makes it more reliable against EMI than analog signal. But this alone does not make the IMU immune to EMI. Since I haven't got a scope to verify, I can only say EMI is one possible cause.

BTW, I have my M4 installed on a H4-680 frame with 4s battery and 4108 motor. I add one dedicate battery for FC and gimbal which works well.

Regards,
Ye

[whizz101]

I have now mounted my M4 N4 in a quad with the same esc,s and still running on 6 cells.

I had the same problems with spikes in my motor outputs. But when using Max's "test" firmware all is good. Tomorrow i will do as many flights as i can and see if my original problem presents itself.

[Patscherpofel]

any update to this problem you have?

I have the exact same problem with a camera quad randomly going nuts from time to time (every 3-5min)...in all flight modes. I also see the spikes and I also use the M4 N4 combo , which is the first AQ FC I own

I gave up on the setup and use different hardware because it was extremely dangerous to use but now that I read this thread I have hopes again to find the problem
I will check which firmware I used first

[Patscherpofel]

I tried a lot of things , different fw, pids, different frames
but all with the same problem...good flying performance and then out of nowhere the motor outputs react like crazy
no special stick input , no external influence
logs look exactly like in this thread in the beginning
its an m4n4 on 6s from viacopter

very dangerous and I will probably give up now

[Patscherpofel]

I read that having both comms enabled might lead to conflicts on an m4
and I allways had them enabled for BT and OSD
any more info on this?
I am on the the 1923 fw right now

edit...now I also saw the warning in the pop out window on the com settings..damm...I missed the info on this before

[sandmen]

Where did you read, that both comms enabled, can make conflicts ?

Gesendet von meinem A0001 mit Tapatalk