Hello, I just got a replacement for my previous Meteor 75 Pro and I tried to update the firmware to what I had on my last 75 Pro and now it's very jittery and keeps wanting to fly away. Those setting and firmware were flying perfectly fine on my last one so I know it's not them. I also updated to the latest BJ esc firmware just like I had on my previous one. So I tried to go back to the stock firmware and settings using the backup I created right when I first connected my newest 75 Pro, but then it doesn't recognize my gyro at all. I don't have that issue with newer Betaflight firmwares. I even tried to update to 4.5 firmware to no avail. Does this issue sound familiar or does anyone have a clue what's wrong? What could I be missing if it's not hardware related? Everything else seems to be working fine. I checked for errors in the motors tab, but all motors are synced and sound fine. I also tried default settings on all the firmware versions I've tried which is 3 different ones. Lmk if posting my cli dump helps. Im not at home rn, but i will when i get home. Thanks!

I have the Meteor75 Pro and really like it.

When you say "very jittery and keeps wanting to fly away" I think about too much vibration. Check all the screws for sufficient tightness and check that no FC components are touching the frame. Also check the props for damage.

Then, as I espouse all the time, increase the rpm filtering. In BF go into the PID tuning tab, then go to the filtering section. Slide both sliders from 1.0 to the left to 0.8. Don't change anything else. Then fly. If it fixes the problem, great. If it does not, then simply move the sliders back to 1.0, no harm done.

Might not be the same FC. There are about three versions of the FC that's currently used with different gyros on them. The ICM42688 version is really twitchy and hard to tune, the BMI270 version which I kind of like but needs low pass filtering and the old ICM20689 which i also don't mind but has a tendency to pitch left without input. It's possible you had the BMI270 on the old one and now have the ICM42688 version, which would need different settings (the BMI270 has some low pass filtering by default). Unless you need to upgrade firmware for some specific reason, don't do it. You took a working quad and broke it and now you have a non working quad. Same with the ESC's. Do not trust what is autodetected, ever. Go to the manufacturers website and find out what the exact targets are and be aware that sometimes they need a very specific version to work. Originally the Meteor came with the BB51 ESC chip that you couldn't run Bluejay on and I think they changed it to another one that may be unsupported. So check it is the correct one. Same with betaflight, the autodetect on mine said my BetaFPV 12A AIO used a MatekF411 target, which it doesn't, it needed a BETAFPVF4SX1280.

I suspect the gyro changed between quads, which is why your old settings have screwed it up. Your best bet is to grab the diff and dump from BetaFPV's website and apply it and see if that fixes it.

(09-May-2024, 05:15 PM)Pathfinder075 Wrote: Might not be the same FC. There are about three versions of the FC that's currently used with different gyros on them. The ICM42688 version is really twitchy and hard to tune, the BMI270 version which I kind of like but needs low pass filtering and the old ICM20689 which i also don't mind but has a tendency to pitch left without input. It's possible you had the BMI270 on the old one and now have the ICM42688 version, which would need different settings (the BMI270 has some low pass filtering by default). Unless you need to upgrade firmware for some specific reason, don't do it. You took a working quad and broke it and now you have a non working quad. Same with the ESC's. Do not trust what is autodetected, ever. Go to the manufacturers website and find out what the exact targets are and be aware that sometimes they need a very specific version to work. Originally the Meteor came with the BB51 ESC chip that you couldn't run Bluejay on and I think they changed it to another one that may be unsupported. So check it is the correct one. Same with betaflight, the autodetect on mine said my BetaFPV 12A AIO used a MatekF411 target, which it doesn't, it needed a BETAFPVF4SX1280.

I suspect the gyro changed between quads, which is why your old settings have screwed it up. Your best bet is to grab the diff and dump from BetaFPV's website and apply it and see if that fixes it.

Thanks for your reply! They gyros were the same. I figured out what was wrong with it. One of the screws is broken on one of the motors. I guess it was hanging on by a thread cause I went to take them off to put a little loctite on them and it popped off as soon as I touched it. It'll be near impossible to get it out at this point so I'll just have to send it back and get a replacement. It sucks cause I just got it back lol. Thanks for your help!

(09-May-2024, 04:55 PM)segler999 Wrote: I have the Meteor75 Pro and really like it.

When you say "very jittery and keeps wanting to fly away" I think about too much vibration. Check all the screws for sufficient tightness and check that no FC components are touching the frame. Also check the props for damage.

Then, as I espouse all the time, increase the rpm filtering. In BF go into the PID tuning tab, then go to the filtering section. Slide both sliders from 1.0 to the left to 0.8. Don't change anything else. Then fly. If it fixes the problem, great. If it does not, then simply move the sliders back to 1.0, no harm done.

Yeah I love it too! I had my last one flying so well! I figured out that one of the motor screws was sheered off. It was hanging on enough to still have the head in tact, but as soon as I went to take it off it easily popped off. Thanks for your reply!

The MatekF411 target seems to be a fairly universal target that works for other manufacturers' FCs. I recall an instance where JB used and recommended the MatekF411 target for a FC that did not have a factory firmware available.

In my case what I HATE about the Meteor65 Pro and Meteor 75 Pro FCs is that they do not have a hardware current sensor. This requires me to mess around with a virtual current sensor in BF. They recommended virtual settings for the Meteor85 Pro. I am trying those setting for mine. Almost all other modern FCs include hardware current sensors.