MOT_PWM_MIN, MOT_PWM_MAX are reset to default values automatically about ardupilot HOT 7 CLOSED

This is probably mostly a support request and if so belongs on the support forums here. https://discuss.ardupilot.org/c/arducopter/copter-45/174

I suspect the motors are setup to use DShot which enforces the 1000 ~ 2000 range. I don't think regular PWM outputs enforce a particular range. If there's a log file we could check although it should also be clear from looking at the messages (aka "the ribbon") output soon after startup (and whenever parmeters are downloaded)

Copter doesn't support reversible motors though. The most similar frame that supports reversible motors would be the heliquad frame using the TradHeli software.

from ardupilot.

The work around would be to not set Dshot in MOT_PWM_TYPE and use the SERVO_BLH_ params instead.

from ardupilot.

@rmackay9 HeliQuad is much further from my drone than a Quad. I doubt moving in that direction would be productive.
The ESCs are DShot indeed. BLHeli are all configurable in their range, including reversible, so enforcing a fixed value doesn't look right. I have a business reason to use reversible motors - when the drone is not in flight the motors can do other things; it would still fly like a quad.

I posted this here, because the customer expectation is to see things that work - if a particular setting doesn't do anything it should either be made to do its thing or be removed. Showing things that don't work is a bug.

@IamPete1 Can you please clarify your suggestion? What should I set MOT_PWM_TYPE to and which SERVO_BLH_ properties set to what values? In my setup MOT_PWM_TYPE is Dshot150 and below is a screenshot of my SERVO_BLH_ properties, including two of them than mention reversing

from ardupilot.

MOT_PWM_TYPE should be 0. Sounds like you want 3D not reversed.

from ardupilot.

@IamPete1 What I ultimately need to achieve is the ability to move any set of motors in either direction while the drone is on the ground, via a Lua script. It would suffice if the servo range settings are actually used instead of hard-coded 1000-2000.

Setting MOT_PWM_TYPE to 0 doesn't change anything, the normal motor servo range still gets reset to 1000-2000 and the remote's throttle still maps to the whole range. Are there other settings you're suggesting I should change?

Side note: limiting the throttle range on the remote itself doesn't work because the motor outputs can exceed the throttle PWM value when the drone is trying to stabilize itself

from ardupilot.

I don't think this is a bug, it sounds like the @StenPetrov is trying to do something outside of what copter was designed for.

from ardupilot.

@IamPete1 Fair - Then the bug is to remove the settings whenever they don't apply, so others like me don't waste their time - and yours - trying to figure out how to coax their copter into doing new things, or at the very least explain in the description boxes how it works - it's still a bug

from ardupilot.