More Flite Test Electrohub Trouble - Flip 1.5 Board
- Thread starter Tphillip96
- Start date
havnmonkey
Junior Member
It looks like your midpoints are off too far. Take off the props and enable the ESC's. Arm the copter and push the the throttle up until the motors spin... Now watch the four motor levels in the gui, I suspect two of them will spin up higher by themselves and continue to accelerate without you touching the throttle.
Mine did that until I correctly trimmed my TX, if you cannot edit your transmitters subtrim you'll have to edit in the gui itself.
Mine did that until I correctly trimmed my TX, if you cannot edit your transmitters subtrim you'll have to edit in the gui itself.
Tphillip96
Member
Here it is -
Also here is a picture of my radio
makattack
So what's next? Do I change the MIDRC and how is that done and to what values?
Thanks
You'll have to edit the config.h file in the Arduino IDE and reflash the firmware. Before doing that, you might want to check to see if in fact your trim switches are centered. I'm not familiar with that TX, but on most with digital trim switches (which is what that looks like), you need to push them up / down until you hear a unique tone that's not going up nor down in pitch.
The link I sent earlier has details on MIDRC, and based on your pictures, I would probably set it to 1483 or so... whatever value works to get that UI display to show 1500 on roll, pitch, yaw with neutral sticks.
The link I sent earlier has details on MIDRC, and based on your pictures, I would probably set it to 1483 or so... whatever value works to get that UI display to show 1500 on roll, pitch, yaw with neutral sticks.
Tphillip96
Member
Oh, yes the trim on my TX are set to the center.
And how do you know if your throttle stick is exactly neutral? Flying Mode 2, that stick does not pop back to center like the other ones. Also the MIDRC would change all of the motor speed or just one because on the GUI picture below one of the motors is lagging about 100RPM's behind?
Doing a static, full throttle test with no props on will give you different results depending on how you've placed your quad. If you look at your roll and pitch indicators, they aren't fully level, so the board will try to compensate by giving different thrust... in this case, it almost looks like it's trying to yaw. I don't know, but I don't think that's a very good test.
The MIDRC wouldn't affect throttle, or at least make any difference. It only makes a difference for the roll, pitch and yaw channels because the flight controller has to know what "neutral" is -- or middle for those channels. If it sees anything other than 1500, it thinks you're trying to input roll, pitch, yaw, or all of the above... which is actually what I think that graphic shows. Not only is the quad not level, but you're sending command input of about 1485 to roll, pitch, and yaw... so that would kind of explain why those motors are being commanded with different levels.
A quick test might be to use those trim buttons to try to get your midrc points to 1500, then see if it does the same thing in the gui when you throttle up.
The MIDRC wouldn't affect throttle, or at least make any difference. It only makes a difference for the roll, pitch and yaw channels because the flight controller has to know what "neutral" is -- or middle for those channels. If it sees anything other than 1500, it thinks you're trying to input roll, pitch, yaw, or all of the above... which is actually what I think that graphic shows. Not only is the quad not level, but you're sending command input of about 1485 to roll, pitch, and yaw... so that would kind of explain why those motors are being commanded with different levels.
A quick test might be to use those trim buttons to try to get your midrc points to 1500, then see if it does the same thing in the gui when you throttle up.
Tphillip96
Member
Ok thanks, I will definitely set my MIDRC to 1500 as soon as possible.
Tphillip96
Member
So I finally found some time to work on my quad and I did as makattack recommended
- And judging from MultiWiiconf every thing looks to be solved. I guess I will see how it fairs tomorrow when I maiden it!
Thanks For everyone's help!
- And judging from MultiWiiconf every thing looks to be solved. I guess I will see how it fairs tomorrow when I maiden it!
Thanks For everyone's help!
Last edited:
Tphillip96
Member
So I just maiden my quad and the problem persisted. 😣 So as a test, and since I used bullets for my motor connections I decided to move the motor that seems to be weaker, and to my surprise the quadcopter flipped to the side I moved the weaker motor to.
- So I was just wondering if midpoints are the problem or not? Or is it a isolated problem with the motor.
Also I have double checked and triple checked everything from where the escs are plugged into the Flip 1.5, making sure all of my trim is set to center on my TX, changing the MIDRC, and even making sure the props are on right.
- So what should I do now?
- So I was just wondering if midpoints are the problem or not? Or is it a isolated problem with the motor.
Also I have double checked and triple checked everything from where the escs are plugged into the Flip 1.5, making sure all of my trim is set to center on my TX, changing the MIDRC, and even making sure the props are on right.
- So what should I do now?
Is the motor you moved spinning in the correct direction? You didn't mention double checking motor direction.
Does the motor itself spin freely?
Even with a weak motor, I would think the flight controller could compensate unless the motor doesn't spin at all.
Does the motor itself spin freely?
Even with a weak motor, I would think the flight controller could compensate unless the motor doesn't spin at all.
Last edited:
Tphillip96
Member
1. Yes, the motor is spinning in the correct direction
2. What do you mean by freely (yes it moves without TX input)
3. Yes the motor spins, really could not tell that one motor is slower by just looking at it, even at full throttle.
- So I am going to do some more tests in MultiWiiCon, is there anything I should test specifically?
Also if anyone has any ideas just write away.
Tphillip96
Member
Will Do, thanks.
Tphillip96
Member
Hi Know its been a while but I caught In school. Anyways I am still having the same issue.
Here are the test screenshots -
This is Half Throttle with none of the arms down:
This is Half Throttle with the Front Right arm down:
This is Half Throttle with the Front Left arm down:
This is Half Throttle with the Back Right arm down:
This is Half Throttle with the Back Left arm down:
Any thoughts??
Here are the test screenshots -
This is Half Throttle with none of the arms down:
This is Half Throttle with the Front Right arm down:
This is Half Throttle with the Front Left arm down:
This is Half Throttle with the Back Right arm down:
This is Half Throttle with the Back Left arm down:
Any thoughts??
Welcome back and hope you're enjoying your Summer break!
So, the first screenshot is the most interesting. I'm assuming that all the sticks are neutral, with the throttle at 50%. If that's the case, it's clear that your midpoints are all wrong. They should read 1500 when all sticks are neutral -- including throttle at 50%.
One of the most important RC configuration setup with your TX/RX and multiwii/baseflight/cleanflight is to get your endpoints to 1000 minimum, 2000 maximum, and 1500 at midpoint.
Until that happens you won't be able to fly or if you will, it'll not fly well.
I looked through the old posts. I thought you had sorted out the MIDRC issue... I guess not or the trim switches got bumped / aren't neutral?
Another thing... the motors don't seem to behave as I would expect. Have you tried erasing the EEPROM and reflashing the software?
So, the first screenshot is the most interesting. I'm assuming that all the sticks are neutral, with the throttle at 50%. If that's the case, it's clear that your midpoints are all wrong. They should read 1500 when all sticks are neutral -- including throttle at 50%.
One of the most important RC configuration setup with your TX/RX and multiwii/baseflight/cleanflight is to get your endpoints to 1000 minimum, 2000 maximum, and 1500 at midpoint.
Until that happens you won't be able to fly or if you will, it'll not fly well.
I looked through the old posts. I thought you had sorted out the MIDRC issue... I guess not or the trim switches got bumped / aren't neutral?
Another thing... the motors don't seem to behave as I would expect. Have you tried erasing the EEPROM and reflashing the software?
Last edited:
Foam Addict
Squirrel member
+1 on that. My Flip tricopter flew horribly till I tried wiping the eeprom. Actually after that it flew really nicely... I wish I still had that thing...
Tphillip96
Member
No I have not tried erasing the EEPROM. How is this done?
Tphillip96
Member
So I just erased the EEPROM, what is the next step? Do I reflash the board without that line of code?
