Iris+ drone. May need older profiles like AC32+ or AC33+ if there was one (help)

#### Issue details

Iris+ acting weird when calibrations withtout props. Not as when it was flying OK . ... but seems to pass all pre-arm and say it is in good shape. I suspect a profile problem.

My supposition : Probably need old Mission Planner Iris+ profiles AC32+ and AC33+ but unable to find them. The section is grayed in old versions of MP I downloaded so I can't at all select a profile.

I asked 3DR informations on it and they told me the last functionnal version of arducopter firmware for my version of Iris+ was 3.3.3 . I installed it and all my beep sounds returned like when my Iris+ was functionnal ( AC34 profile was making it acting very strange on the throttle ) . I was enthousiast but , the problem is the following :

I can't find the old profile in the presets for parameters. They only offer me the " AC34+ only " version but I run 3.3.3. Passed this version my drone is acting really anormally without props and all the ESC sounds and other are strange. With the 3.3.3 version , calibrations sounds of my Pixhawk (px4) are back to normal , calibration shows good ... but the throttle still feel not the same as factory even if it's a little smoother. I'm pretty sure it's a PROFILE SETTINGS matter cause I'm forced using AC34+ profile on AC3.3.3 ( my last functionnal version for first edition of Iris+ ) . You see where I'm going ?

I tried as a solution to just install older versions of mission planner but when I do , the PROFILE area normally clickable is grayed like the server is no longer connected . ... so I'm totally unable to run " like new " my drone. The only solution I see is someone give me the configuration profile files ( not the firmware) Iris+AC32 and Iris+AC33 if there was one . I presume the writers of the code kept a backup for cases like mine .

Feel like if I don't test in optimal ( factory ) settings , I may loose it with props. Some are telling loiter mode is normally very bizarre acting without props but my Iris+ was graduating it smoothly in the past without props . Is it due to a change in the code of the profiles ?

So I need the profile Iris+ AC31 and AC32 and (or) AC33 if there is one. In stabilize mode , my drone seems to graduate normally the speed with the throttle but ... when I try LTR without props like I was doing when the drone was new , it changed it's way of acting. Motors spin all at the same time like ESC is doing good .My ESC calibration completes without errors and graduates super smoothly when in calib mode. Then I put the drone in LTR mode and ... it graduates very strangely... like I got the impression it would fly away with props .... even if my green light is there ( GPS locked ) .

It seems 3DR has made 2 versions of the Iris+ , not just simple IRIS and then Iris+ so I'm pretty sure the AC34+ profile doesn't seem to work correctly on the throttle with my old 2014 Iris+ for this kind of reason. The motors were not the same and I think the 2015 version of Iris+ had an ESC by motor and not an all in one ESC board. Some say it had smaller props too. It may be the source of the total attitude change of my drone since a firmware update. Maybe the profile was modified to fit last versions of my drone and then I don't have access to the old profiles.

I'm an autistic very good multimedia producer but I don't have a lot of money so bring back to functionnal state this drone is a priority for me.

#### Version

All versions gives strange attitude of the drone when I test throttle without props but the calibrations sounds are normal on the 3.3.3 version. Passed this , I got a lot of bizarre different noises from my drone and it acts pretty crazy even after all calib I'm used to do . Seems like I try to run on the AC34+ profile on the last goof firmware for me .... the 3.3.3 . If I could get back the setup I had ( I lost my backup files ) , it would allow me to double check I'm really ready to fly. It passes all calib test including barometer and accellerometer or ESC on the 3.3.3 firmware. It just lacks a AC33+ or AC32+ profile so I can test with original values.

#### Platform
Px4 ( pixhawk 2.6 )
Original firmware Arducopter 3.2.1

#### Airframe type
Quad , V shape

#### Hardware type
Px4

#### Logs
had problems reading my Logs for the moment but may come back with it soon

Start by reviewing Mission Planner's parameter profile or preset handling for Iris+ and compare the available AC34+ profile with the reported ArduCopter 3.3.3 setup on Pixhawk. Reproduce the calibration and throttle or loiter behavior if possible, then determine whether the requested AC31, AC32, or AC33 profiles exist and what evidence would confirm the correct factory settings.

Written by the indexing model from the issue text.