Uncontrolled altitude in alt_hold and loiter

And when you enter production you will remember why you changed them some months ago?

Do yourself a favor and save some time. Change them NOW.

I got your point, yes you are right from now will certainly put the valid reason change string
Hope you understand my situation I already had that copter perfectly flying but after changing the frame I got stucked and from a long time I am not able to solve it so as its a human nature I want to see that improper takeoff gets resolved
Hope you understand :innocent:

  1. Use the files that I sent you in the configuration
  2. Maximize the parameter file editor window
  3. check the “See only changed parameters” checkbox on the bottom
  4. Start from file 04
  5. Click either “Upload …” or “Skip…” depending if you agree, or not agree with my changes
    Once you reach file 18 do a flight and post the .bin file.

Without the “reason changed” it is very hard and error prone to do a parameter review.

Sure I will do these changes and will get back to you

I did the flight test after uploading the files upto 18th as you said I had to change the notch_filter from ESC Telemetry to Throttle as I don’t have any ESC Telemetry data available and I set takeoff_rpm from 1000 to 0 because I don’t have RPM data

Log of Last Flight: Log

There is something wrong with ESCs firmware configuration or their connection.
DShot600 supports RPM telemetry. That is one of the reasons people use that protocol.

So, Is that issue is because of I don’t have RPM Telemetry
I don’t think so because in the previous version of frame it was working absolutely fine

Hi @amilcarlucas, Did you got any chance to look into the above

You need to fix that issue before you can continue.
Read How to methodically configure and tune any ArduCopter section 1.2 and 2.8

In the past when it flew “correctly” who evaluated that correctness? Probably you, that do not have experience and never flew a properly configured and tuned drone. Or have you?

I will look at the logs once you get ESC telemetry working.
When this is tuned you will get something that you can safely and responsibly sell to other people, it will no longer be a hobby toy.

Ok then I will figure out the ESC Telemetry thing first

You are not configured properly for Bdshot on the main outputs hence no telemetry.
Change these and reboot.
MOT_PWM_TYPE,5 (Dshot600 will not work on the Cube Orange Main outputs)

Then after connecting to Mission Planner look at the Banner message on the messages screen and confirm you have Dshot for the outputs you are using.
Then make a short flight and review the log yourself to determine if ESC RPM is present.

BTW-Your GPS is performing very poorly. You can’t function with 6 satellites and an Hdop >1

1 Like

Let me explain you how exactly I configured

Hardware used:

  1. OrangeCube+ with mini carrier board
  2. DYS Aria 60A 4in1 ESC


MOT_PWM_TYPE,6 (DShot600)

As I know in mission planner esc1_rpm, esc1_volt should show if the is autopilot is receiving esc telemetry

@dkemxr I know my gps is performing poor I did that flight in a not so open area
There are lots of thing that needed to be fixed you guys are my hope for that

What firmware is this ESC using? BLHeli_32, BLHeli_S, something else?

On that picture that is not a CubeOrange, it is a cubePurpule.

You need to connect and configure your 4 DSHOT600 ESCs on to “Aux Out 1 …4” instead of “Main out 1… 4”


But do not change the parameter with Mission Planner, change them with the methodic configurator.

And I now added this section to the documentation:

  • The Reason changed field is extremely important because:
    • if forces you to think, causing rational decisions instead of impulsive ones
    • justifies your decisions on a vehicle certification process required in most countries
    • allows for someone else to see if you know what you are doing
    • allows for someone else (or yourself after a few weeks) to understand your rationale
1 Like

@dkemxr according to his vehicle_components.json file he is using “BLHeli32 Version”: 32.10 connected to serial port6

On the picture above it is connected to serial4.

So the information is incorrect and/or inconsistent.

1 Like

But mine is Cube orange+ mounted on mini carrier board
@amilcarlucas I apologize for the steps taken by me in configuration I am still learning this tech by doing and with your help
After your reply on fixing the esc telemetry issue first I thorougly studied about how to fix that issue I got to know this serial4 thing and telemetry pin in esc
because before that I just connected motor wires and gnd wire

If in fact they are BLHeli_32 ESC’s refer to my previous email and set those parameters. You want ESC RPM from Bdshot not serial telemetry.

1 Like

You should use this firmware version:

The last log he posted shows he is using that firmware. But, with no regard for configuration.

Is that I will get telemetry data from the motor signal pins only, I thought I have to connect the telemetry pin in order to get the esc telemetry Refering to this discussion

Now the very first step I have to do as @amilcarlucas said to connect motor pins to aux pins
and then with RPM data i have to do a flight test then logs

am I missing something?