Hello Greg,
sorry for the delay, got side tracked today.
Please find attached the para file with I am trying to use. I downloaded it for the same directory where I got the firmware for the orange cube.
It is on the MFE download site on github
here is the link https://github.com/makeflyeasy/MFE_ArduPlane/tree/main/Freeman
Thanks
WernerMFE Freeman 2300 .param (19.5 KB)
Werner,
The .param file you attached is for using the Pixhawk outputs from the MFE documentation. The outputs do not match my DIY version so you need to choose which setup you want to follow.
Also, be sure that the safety switch has been activated so that the servo outputs can follow your R/C input controls.
Good luck!
Hi,
I had a crash today. I would like to share to you the video, parameters and the log. We were doing a auto mission, and the plane crashed while transition. The communication with the plane lost in the air, couldnāt figure out the reason. Tried to change mode to qhover but the plane was not responding. Hope someone can figure out what happened so we fix the mistake.
https://drive.google.com/drive/folders/1yCtmIBlAKg-3c74APDsPKDkQylYaXqex?usp=sharing
Hi Ozan,
I am sorry to hear about your plane crash. I did a cursory check of your log and suspect that it stalled in flight. The air speed was lower than the ground speed which suggests a tail wind or perhaps an uncalibrated sensor. Since your ARSPD Min/Max values were 12-26 m/s, I also suspect that maybe your throttle was set to minimum instead of mid-stick. However, I am not certain if this matters in AUTO mode since I havenāt used it in a few years.
Lastly, your Q_ASSIST_SPEED setting was 0 so the plane could not save itself on a stall. This setting should be at the stall speed of 10m/s for safety.
Hi,
Thanks for reply. The throttle was always mid-stick through the whole thing. But that shouldnāt make a difference in auto mode I believe. The vehicle had a slight side wind during transition and yes I also suspect that the airspeed sensors calibration was off. Using sdp33 sensor. Recently changed from 5520. But the parameters of the previous airspeed sensor was on with some offset. I believe that was the major problem. But I didnāt understand why the throttle command is not %100 through the transition? Is that normal? Can you give a look?
We also suspect that the battery had over-demanded and exploded
.
But Iām not sure if the battery expolsion was after or before the crash. I suspect that because the log and the video transmission stops mid air. Iām pretty sure I switched to qhover flight mode before crash but I canāt see that in the logs. Thats a custom made 6S8p battery btw.
Your throttle stick setting was at the mid-position so that was not an issue. When the transition was completed, both Motor 1 and Motor 3 revād up to full power and the current draw increase showed that it was drawing full current to both motors. However, if the plane had already stalled, it may not have helped. It really needed to go into the Q_ASSIST_SPEED safety mode. This should have been tested before doing an AUTO flight. I always stall test fly my VTOLs at a high altitude by lowering the throttle in FBWA mode. It gives you peace of mind that the plane can save itself.
Cheers!
Thank you. Will do that next time.
See you later with good news.
Hi Greg,
Awesome build, i was wondering if you can share a log file with a successful build. I am trying to build one, but i have some tuning problems, like the tilting motors are moving to little when I change from manual to qstab. Cheers 
!
Hi Razvan,
It sounds more like you want a .param file. I can easily attach one below. Remember that I am using the MFE custom build below so there are new parameters visible not in the normal release code. We went through those above. Good luck!
ArduPlane v3.10.0-dev (effeebfe)
2020-08-07 10-06-00.log.param (20.9 KB)
Hey, thanks 
Hope this will make my life easier. thanks again , really helpful to have a param list that works fine.
Also I am using the newer version of ardupilot, will this affect the param list?
Cheers
Yes, my .param list is for the MFE custom firmware, not the standard APM Plane release.
Keep reading the posts above. I recall others using the standard APM Plane releases.
Good luck!
@GregCovey
Hey Gregā¦been a whileā¦Hope you donāt mind but I had a question. Not specifically for the Freeman but I assume it would apply. So here goes. When the lift motors, non tilting ones finish their task and stop. How do you keep the props from spinning wildly and causing unwanted drag.
Just curiousā¦
Hi Ricky,
Iāve never had that issue. Sometimes, the prop will turn slowly but typically not at all. It has never spun fast enough to cause an issue, even with our 18" props. Perhaps when the ESC is powered, but the motor is off, there is some residual force keeping it from spinning wildly.
Cheers!
Ah ok thanks Greg I very much appreciate it.
cheers
hi, can i use a tattu 6s 22000 mah in this plane?
Hi Victor,
I donāt see why not. Itās a quality battery pack for UAVs.
Good luck!
TLDR; Iām joining the fun and I have two (one kit and one PNP) Freeman 2100 on the way.
It took me a while, but I finally finished reading this thread.
As Iāve mentioned in the Fighter 4+1 thread, I purchased a Fighter kit last week from Banggood. When I placed the order for the Fighter kit, I also ordered a Believer kit. Iāve wanted a Believer ever since seeing ArxangelRCās review of the airplane. My plan was to modify the Believer into a tilt rotor quad plane. I figured the Fighter would help learn how to build and fly a quad plane and I could use what I learn to make my Believer quad plane.
I obviously hadnāt done enough research since I soon learned the Freeman is a modified Believer. I was fortunate that Banggood hadnāt shipped the Believer yet so I cancelled that order and ordered a Freeman kit and āPNPā from AliExpress. From reading this thread, I understand the āPNPā version is really a kit which includes the motors, servos and some electronics.
Thanks to everyone here for sharing their experiences. I feel bad for those of you who have had serious crashes. Thanks for letting us know what happened so we can hopefully avoid the same problems.
In case anyone is interested, Iāve posted some info about my MFE Fighter 4+1 build in this thread. I find these very long threads a bit awkward to navigate and I didnāt want to dilute the excellent information in the main MFE Fighter 4+1 thread so I started a new thread to post my updates and ask questions. Iāll need to figure out where Iāll document my MFE Freeman build. This (excellent) thread is also so long itās hard to scroll quickly through the thread.
The main difference between a normal servo and a ārobotā servo is a robot servo includes a pivot point opposite of the servo horn. A robot servo is designed to be a joint in a limb rather than pulling and pushing a push rod.
Normal servos can be used as robot servos but this usually requires a pivot point be added to the bottom of the servo. My first attempt at making a robotic hexapod used normal 9g hobby servos (and Popsicle sticks). I added Lego turntable pieces to the bottom of the servos in order to make the servos behave better as limb joints.
Iāll pretend like building robots is somehow related to this topic so I have an excuse to share this video. This is one of many land based robots Iād like to figure out how to control using ArduRover.
Some robot servos use a serial protocol for communication. Dynamixel makes a bunch of different high power robot servos (called Robotis Actuators). You canāt use a normal servo pulse to control Robotis Actuators. These servos are controlled with a serial protocol. Iāve seen mention of these servos in the ArduPilot Wiki so using these more advanced robot servos is an option in ArduPilot projects.
Really good explanation and very cool hexapod there! Have been on my have-to-do-list-ā¦-later for many years.
We went for the DS-servo RDS3115MG 15kg 180 degrees biaxial servos to the Freeman 2300.
The VTOL is complete and the next step is the firmware. This thread is 460+ messages longā¦ Instead of reading the hole thread are there a faster way to find out what firmware to choose and if there are any latest parameter-file? 
Using the Hex ProfiCNC Pixhawk 2.1 and Here+ GNSS RTK, Mauch-stuff for power, front motors T-Motor AT3520 50E 550KV, rear motors T-Motor MN4019-9 400KV and so on. Total weight with LiPo and no camera = 5,9 kg. Camera is around 400 grams.
