Hey @rollys
I like that VTOL it looks pretty nice. The price is also nice considering this would be a first build. I don’t understand what the difference is between 4in1 and the tilt rotor plane. Do you know what it is.
Will read it some more.
Edit
Awe I get it …one is fixed motor with a pusher motor the other is tilt rotor. I lean towards the pusher motor and fixe motor position…Less things to go wrong.
Hi Greg,
Ok, I will install it in place or remove it from params (the lidar).
But what is the problem with the qloiter? What I’ve done wrong?
What is so special in mfe fw which is modified or missing in the standard ardu fw? I come from the it sector and I try to remove any 3rd party apps that can be variables in the scheme. Also I like to use the latest fw as that resolves some of our problems with our hw.
I don’t know but I would get QSTABILIZE and QHOVER modes working first with no AS Sensor and no LIDAR.
This has been covered in posts 310, 311, 325-330, and 341above. There are probably others. MFE exposes new parameters to the user that improves performance on the Freeman.
Freeman Firmware Exposed Params:
Q_A_RAT_PIT_FILT = 10
Q_A_RAT_RLL_FILT = 10
Q_A_RAT_YAW_FILT = 2.5
Q_ASSIST_ALT_MOD = 18
Q_LAND_DETECT = 3
Q_M_VP_F_COL_A = 0
Q_M_VP_F_COL_B = 0
Q_M_VP_F_THR_A = 0
Q_M_VP_F_THR_B = 0
Q_M_VP_M_COL_A = 0
Q_M_VP_M_COL_B = 0
Q_M_VP_M_THR_A = 0
Q_M_VP_M_THR_B = 0
Q_M_VP_RAT_PIT = 0.25
Q_M_VP_RAT_RLL = 0.25
Q_M_VP_RAT_YAW = 0.25
Q_P_ACCZ_FILT = 10
Q_RTL_LOIT_ALT = 100
Q_RTL_LOIT_MIN = 200
Q_RTL_LOIT_RAD = 45
Q_SLIP_GAIN = 0
Q_TILT_FIX_ANGLE = 0
Q_TILT_FIX_GAIN = 0
Q_TILT_SRV_SYNC = 0
Q_TILT_THR_DN = 75
Q_TILT_THR_UP = 20
Q_TRAN_RLL_MAX = 10
Q_TRAN_YAW_GAIN = 0.3
Hi all,
I read all your posts and wanted to thank you for your time and effort to share your experiences.
I’m looking to buy the Freeman 2300 VTOL, PNP version. AliExpress is charging close to $100 for tax (I’m in NY). Did that happen to you? The money goes straight to china, do they actually pay back that “tax” to authorities in the States? I tried an address in Georgia but they still charge the same amount.
My question is, what other sources are available to buy a PNP version?
Thanks
Hi cukabul,
Welcome to the MFE Freeman thread. If you live in NY, I don’t think the Freeman 2300 PNP version is available. I only see the kit version and the shipping cost is a ridiculous $1018 or more. Let us know if you see different.
I suspect the high shipping is only temporary and it will go back down to what it was before.
Cheers!
Hi Greg,
Thank you.
Wow, I just checked the link and yes the PNP is not available anymore and the shipping cost is $1018 lol. I will wait.
Thanks again.
Hi Greg, could not get the mission planner to install the customer firmware on the cube orange (v5) kept getting this error
Hi Greg,
Your post is helping me to initializing with 2100, congratulations.
I have a trouble to try a transition, is possible make it doing without specific firmware ? I am not using Firmware of MFE, I think Arduplane quadplane code could to do this perfectly, but not ! I was using in my Nimbus VTOL tricopter, no problem !
I’m having problems in the transition to fixed wing, as soon as it make the transition, the plane does not follow a straight line (auto mode), making turns to the sides, as you can see in the video below:
see logs and parameter here:
https://drive.google.com/open?id=11t8Bf4ztScL7Yp0_kqmwZiEW7LQMqPhf
Please, I will try this firmware, but, if you can see any trouble in my configuration, I like to continue using my version.
Than you soo much
That’s what mine does but it eventually takes off after a few yaws, I think airspeed sensor is an issue it must be calibrated
I was considering to buy an orange cube autopilot. Can someone confirm that the MFE firmware works with the cube orange?
I think this is transation problem, have a yaw value to VTOL mode and different value to Fixed Wing mode. Strange error !
I see at LOG have a difference power to front motors, one to low and other to high value exactly time when change to transition mode.
That’s odd. The Pixhawk 1 is essentially the same build as the Orange Cube. Only the really old Pixhawks with the 1MB flash memory issue have a different build to omit some features. You can try loading it with another app like QGC or even BetaFlight works great.
This is one of the issues seen when not using the MFE custom firmware. While you can certainly continue using the standard APM firmware and tune things yourself, I might suggest that you first try the MFE custom firmware so that you have a baseline of proper operation. From that point, you can then leave it as is or load the latest APM Plane firmware and start tuning. I would also recommend using FBWA mode instead of AUTO for your initial transitions.
Most of us on this thread are very happy with the custom MFE firmware. I never went back to test the standard APM Plane firmware but it seems like something is wrong in the yaw control settings. If my memory is correct, the plane would eventually stop yawing and start flying.
Good luck!
Edit: I didn’t see Paul’s post below but this could be the issue. Remember that your initial forward flights should be with the AS sensor disabled. You then calibrate the sensor (or leave it in calibrate mode for the first few flights), check the logs for proper AS operation, and then enable the sensor. In other words, you can calibrate the sensor without using it. Calibrating an Airspeed Sensor
 
It appears those firmwares are not compatible with orange cube, (tried them all ) 
Where is the source code for this? GitHub link?
Orange cube is Orange, not v5.
V5 is nothing to do with the cube.
Greg I think your assumption of the cube orange is a little incorrect.
Paul,
Which assumption was that? The image below that came with the MFE firmware? I only have Pixhawk 1s to test and it worked for me. So it’s possible that this documentation is incorrect. I thought @mike_E had success loading with an orange cube but maybe he wasn’t using the custom firmware. I get so many private messages that it may not be in a thread post above. Not sure what FC was used by @Hadits_Baroya.
MFE firmware had problems loading on both the black and orange cubes.
I used finwing’s firmware wo/any problems but I’m now using the last stable ver (4.07) from ardupilot.
I don’t have the _FILT params showing up but it flies reasonably well. The only problem was severe hunting after LO so I changed from an I2C to CAN gps (and have just gotten a HERE 3 to try).
Here’s a clip of an auto TO and transition to waypoint mode…
Looks great, Mike! Can you post your .param file? Have you ever seen the yaw issue on transition using standard firmware?
Cheers!
I have never seen that yaw problem… and I don’t have a pitot tube installed yet.
It’ll be a bit before I can get to the storage shed where the Freeman is resting to pull the latest params, I’m trying to get the Vtbird tilt motor working so its handy whereas the Freeman is behind a bunch of other “BIRDS” 
