We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
after revising custom print in ControlAllocator.cpp like this:
if (_actuator_effectiveness != nullptr) { PX4_INFO("Effectiveness Source: %s", _actuator_effectiveness->name()); } // Print current effectiveness matrix for (int i = 0; i < _num_control_allocation; ++i) { const ActuatorEffectiveness::EffectivenessMatrix &effectiveness = _control_allocation[i]->getEffectivenessMatrix(); if (_num_control_allocation > 1) { PX4_INFO("Instance: %i", i); } PX4_INFO(" custom print test."); PX4_INFO(" Effectiveness.T ="); effectiveness.T().print(); PX4_INFO(" minimum ="); _control_allocation[i]->getActuatorMin().T().print(); PX4_INFO(" maximum ="); _control_allocation[i]->getActuatorMax().T().print(); PX4_INFO(" actuator_trim ="); _control_allocation[i]->getActuatorTrim().T().print(); PX4_INFO(" control_trim ="); _control_allocation[i]->getControlTrim().T().print(); PX4_INFO(" Configured actuators: %i", _control_allocation[i]->numConfiguredActuators()); }
and defining functions in ControlAllocation.hpp:
const matrix::Vector<float, NUM_ACTUATORS> &getActuatorTrim() const { return _actuator_trim; } const matrix::Vector<float, NUM_AXES> &getControlTrim() const { return _control_trim; }
then,
make clean
make px4_sitl gazebo
<arg name="vehicle" default="iris_ctrlalloc"/>
and run roslaunch px4 mavros_posix_sitl.launch
roslaunch px4 mavros_posix_sitl.launch
then in the px4 terminal, run commander takeoff and control_allocator status
commander takeoff
control_allocator status
will got no new added message printed, even the string.
at least the added:
PX4_INFO(" custom print test.");
should be printed
No response
PX4 Release/1.13
px4 sitl gazebo
Multicopter
if u think this should not be a [bug] issue, welcome to discuss in the forum and close this issue, thanks a lot!
The text was updated successfully, but these errors were encountered:
The code isn't getting recompiled. Try deleting the build directory
make clean && rm -rf build
make sure you're running the same code that you're building, that you don't accidentally have two px4 repositories downloaded.
Sorry, something went wrong.
@dakejahl Thanks for that! I double checked that I have only one PX4 repo, and run
the whole build folder is removed, and the next make px4_sitl gazbeo took longer time, but it still failed, without any custom message printed.
make px4_sitl gazbeo
then your changes must not be getting saved, check git status
git status
@dakejahl thanks again, but weird, it do has modificaiton
it works only in
make px4_sitl gazebo_iris_ctrlalloc
if using
roslaunch px4 mavros_poxis_sitl.launch
all custom messages will not be printed.
No branches or pull requests
Describe the bug
after revising custom print in ControlAllocator.cpp like this:
and defining functions in ControlAllocation.hpp:
then,
make clean
make px4_sitl gazebo
and run
roslaunch px4 mavros_posix_sitl.launch
then in the px4 terminal, run
commander takeoff
andcontrol_allocator status
will got no new added message printed, even the string.
To Reproduce
Expected behavior
at least the added:
should be printed
Screenshot / Media
Flight Log
No response
Software Version
PX4 Release/1.13
Flight controller
px4 sitl gazebo
Vehicle type
Multicopter
How are the different components wired up (including port information)
No response
Additional context
if u think this should not be a [bug] issue, welcome to discuss in the forum and close this issue, thanks a lot!
The text was updated successfully, but these errors were encountered: