Motor tests from mission planner are good and arming + spin up also good, until I set servo_blh_bdmask = 15 to enable bdshot on channels 1..4.
If I do that, one of the 4 motors/esc keeps beeping, and does not spin up, it is always the same motor. The others are spinning up without issues… I tried various combinations of servo_dshot_esc = 0 or 3, servo_dshot_rate 2 or 3 etc… but no luck so far.
I am wondering if the lucid H7 firmware supports bdshot? it comes with a _bl at the end but my other systems ( with a kakute h7 ) had _bdshot_bl at the end of the firmware name.
Parameter file attached ( the one that does work, if I change from this motor tests or arming starts to fail ).
I am using this combination without issue. The board supports bdshot. I have had issues with noise on the motor wire - I have built two copters with this combo and one is fine and the other has high error rates for bdshot. I was able to at least get it to fly by twisting the GND and VBAT wires on the ESC cable, but I still got high error rates, which makes me think the ESC is defective. Do check the cable as well - if its always the same motor its like the cable is broken - they are not very high quality, maybe try another.
I ended up trying two twist the gnd and vbat cables, then try a different cable, changed the esc, finally swapped the fc and then bdshot worked… I have no idea what could have happened to the first fc that might be interfering with bdshot.
The only peculiar thing in this build is a fairly long fc - esc cable, of approx 15cm. That can perhaps make it more sensitive to noise or other interference.
The fc I swapped was the ‘spare’ I ordered with the original one, i.e. 2 identical tbs lucid H7 boards.
I did look inside the connector on both sides, and they look fine. Also the fc-cable-esc-motor combo in my testing would work without bdshot enabled ( using Mission planner motor test feature ). Once I set servo_blh_bdmask to 15 the esc driging motor ‘A’ would not stop beeping, and not spin after arming, the others worked fine.
I have the set (fc-cables-esc) that caused the fault on my workbench now, so tests would be easy, dont know what to test though other than contact tbs for advice…
Will try to testfly the setup that now seems to work, but from my end it would be good to know that this is a stable setup. So if I can test something let me know and I’ll go fly
Get a log with the motors running and look at the ESC.Err entries - its a percentage, they should be close to 0, anything over 1 is bad, in my case it was 50. Also make sure you have a nice large cap on the ESC.
Two ESCs are below 1. One Esc is (from memory) 5-ish. The last ESC is over 50.
Edit: Motor 4. AM32. All on the same quads I was dealing with that had the Autotune issue. Increasing the caps help the auto tune problems, but I haven’t chased the ESC.Err. Only so many hours…
Did a first, very gentle, hover yesterday with the fresh fc, esc and cable setup… the machine flies ok which is always good for a first flight, its a bit sensitive on the controls but that can probably be solved in the next flights. The motors als sound a bit odd… but it flies!
I Looked at the ESC.err entries. I see two relatively small spikes, one on esc 1 of around 0.05, one on both esc 1 and 3 on disarm of around 0.1… i.e. all I can see on this flight is well below 1.
On the cap, I have a 63V - 1000uf rubicon zhl cap on the esc battery pads (almost). I’m not sure if the voltage is sufficient for 8S spikes, but run 6S at the moment.
For comparison, I also checked the ESC.err logs from the bench tests where a motor did not spin. I am not 100% sure I am looking at the right / most representative logfile because there are a lot… but I can see ECS.err spikes on ESC 1 and 3, both in the 0.05 and 0.03 range. So nothing significantly diffferent if compared to the flying configuration.
I haven’t looked at the logs in more detail yet, but from this I think the ESC.err values look acceptable, or did I miss anything?
I’m having something similar. Front right motor cutting in flight. Also will randomly not log RPM data for one or more ESCs. Pulling my hair out trying to isolate it. Trying to get through a manual tune but issue persists presenting as a desync on front right motor about 10 times now. Random, no pattern (could be hover within first 60 seconds or hard maneuvering 15 minutes in, totally random. Here’s two from today. Any thoughts?
What am32 version is used? I had problems with 2.19 while 2.18 was OK.
Although I don’t see anything specific issues you can try other version and play with dshot speed, try 600 and rate triple.
I noticed next things:
ESC might overheat - it states near 75c but it also can be wrong readings.
Need to address double peaks in gyro log - your props not in level - see screenshot
might bee to much filtration - lower att, your rig is not noisy
