Hi,firstly what is your name dont like calling you wicked1 as your so helpfull,so reduce P in alt hold in extended tuning
when i was out alt holding was like pids to kigh jumping about
yea it is a 5 inch quad,and thanks for your help
My last name is Wicke, so thatās why this is my forum name 
Alright, so for Alt_hold tunig, the names of these values have changed, and I donāt have time to figure out their new PSC names. But I think you can still decrease these values on the āextended tuningā screen under their old names.
So, on the extended tuning screen look at āThrottle Accelā and lower them a lot. I had mine all the way down to p=.1 i=.2 d=0. (I was able to increase them to p=.2, i=.4)
The next box over, I think is called āThrottle Rateā, and I put it on 3 (default was 5).
And the next box over is āAltitude Hold Pā, and I have mine on .3 (default was 1).
All these settings have different names now in the āpscā section, but youāll have to figure that out by seeing which values change there when you change these settings. I donāt remember, and canāt look it up right now. I was able to lower the values from the āextended tuningā screen, but not increase them. I had to find their new PSC name to increase them.
2 Likes
Also, you need to cover your barometer w/ foam. I needed a lot. I originally had a small square of foam over the baro, and it wasnāt enough. I had to cover my entire flight controller with foam, and then put tape around the edges of my flight stack to protect it from the wind.
You can watch your altitude in Mission Planner while you hover in stabilize. If the values make sense, then itās ok. If your altitude reading is wrong, you need more barometer protection. Mine was showing me at -10 meters or more, until I added more foam and tape.
1 Like
done every thing can only get the throttle accel P down to 0.5 wont go any lower going away to look for more foam got a bit in there now but will do a proper job lol
Hi wicked1 really happy with the way things are going,its just getting better ,loiter,pos hold,Alt and RTL all performing nice just need more tuning,going to try recalibrating the escās as when put power on fast it really wowbles and yawās to the left.
With out being patroniseing im really so grateful for your help,thank you
Thanks, Iām happy to help. Iām just passing on information Iāve gotten from the developers and other people using Arducopter.
If you get a very good tune, post your settings.
My settings work, and get you a decently working copter. But they arenāt perfect. No where near as good as my little betaflight copter for manual flying. But then betaflight isnāt a robot and canāt do most of what arducopter can.
2 Likes
Hey guys Im having trouble with my Airbot ori 4-in-1 esc. blheli32 only sees 3 escās 1 tru 3 but not 4 Im guessing thats a hardware problem without a fix.Right?
1 Like
Sounds like it. I have one of the ESCās and no problem seeing all 4 in the configurator.
1 Like
Figured that and it has to be the most expensive part on the whole build
1 Like
I donāt think I already mentioned it hereā¦
But they sell the ori32 as a 2s ESC. It is NOT!
It stops working at 7v due to low voltage cutoff in the mosfets they use, and they cannot fix it.
I have 3 of them, and theyāre all useless to me!
In airbotās defense, they apologized and refunded me for the one I purchased directly from them.
GetFPV ignored my rma requestā¦
1 Like
Iām on 4S. Itās too bad all the vendors, including Airbot themselves,still show it as 2S capableā¦
1 Like
Just a we update,firstly went out today,and flying faoirly good,in stabilized its good in Loiter,alt,circle and RTL good its funny in loiter it holds well but in pos hold sometimes but not allways it will have a we drift still better than inav,will play with pos hold a bit im only a week into this so am well impressed nearly as good as a 2.1 cube,great project
1 Like
Finally got to do a few hover tests! Beginning with your settings and tweaking PIDs a little, the build is now pretty solid in Acro and Auto-Level, not as good as Betaflight but thatās to be expected.
Iām wondering if the 3.6 RC8 build for the Omnibus Nano supports:
- OSD
- Voltage sensor
- Current sensor with the Ori32 ESC
Iāll have the opportunity to test outside this afternoon and will report back!
EDIT: grammar
My OSD did not work, but putting the latest daily build on it works.
Voltage sensor did work.
Current sensor (actually ESC telemetry) is not defined in the hardware definition for the nano boardā¦ I donāt know why not.
I might try fixing that some day, but Iām not a programmer, so itās taking me a very long while to get set up for that. I keep dropping hints hoping a real developer tries :). I really think it only needs one short line of code to fix it, but am not sure.
How are you enabling the voltage sensor?
That is defined in the hwdef, and it just worked for meā¦ I enabled it in MP just like a standard voltage monitor.
if youāre having trouble, let me know and Iāll look up what pin itās set to in my config file.
It just occurrd to me what the problem might be. Iām only powering the FC from the Vbatt pin on the motor output connector thru the Ori32 FC on the bench (not flying yet). You have Vbatt connected to the battery pads on the FC. Bet this is it.
Mine is the sameā¦ Only connection is through the ESC port. And I still have the ori32 esc in place as I wait for the new one. Iāll turn on my laptop and look at my config file and get back to you in a few min.
OK,
Batt_Monitor 3
Batt_volt_mult 11 (It reads a little high)
Batt_Volt_Pin 12