[Bug] test flight from controller deployed on simulink

[luca0montecchio]

Describe the bug

Hello everybody,

is there the possibility to perform a test flight from a controller I deployed in matlab/simulink?
I am currently trying but after I do the build, deploy and start in matlab and check that everything is as it should I cannot procede with my objective.

To Reproduce

The passages I follow are:

1. Set HITL mode on QGC with the HITL airframe
2. Go to matlab to do the hardware setup of the UAV Toolbox Support Package for PX4 Autopilots that in the new verion requires to use PX4-Autopilots v1.14.0
3. Perform monitor and tune on jmavsim and QGC through mavlink
4. Perform build, deploy and start in order to write the code in C++ inside the px4_simulink_app folder that is created after the monitor and tune from PX4-Autopilots/src/modules
5. I run the command make px4_fmu-v3_default upload in order to upload the firmware with the code on the board (the board is a cube-black that runs v3)
6. Head back to QGC in order to change the mode into HITL and SIL disabled and the airframe into a quadcopter

Expected behavior

After the above passages and once all the sensors calibrations are completed it should be enough to bring the drone outside and make it fly following the trajectory I set in simulink and that I saw it following in the simulation.
When I attach the battery what I experience is nothing at all, the drone doesn't move and doesn't arm anymore not even witht the RC.

Screenshot / Media

No response

Flight Log

I cannot provide log file since it does not move.

Software Version

v1.14.0

Flight controller

PID

Vehicle type

None

How are the different components wired up (including port information)

No response

Additional context

No response

[FilBk]

Unfortunately i'm not giving any proper solution. iI would ask if from Qgc>Vehicle setup>actuators you can spin engines since it works by a different flow of as far as is in my understanding.

Moreover are you able to run the hitl simulation properly? I'm struggling with this too, and i may be wrong, but i'm suspecting some bug in the simulink app module within px4 1.14