- this ensures that the MAV_TYPE parameter is always updated
- previously it could happen that the simulator module was using a wrong
MAV_TYPE value because it only read the parameter value at initialisation
Signed-off-by: Roman <bapstroman@gmail.com>
A hardfault was happening on:
fmu stop
fmu mode_pwm
pwm info
The _mixer was null and being dereferenced to access the trim
setting that were moved to the mixer from the fmu.
This commit fixes that but making the getter issue a warning
and the setter fail.
The code was forcing the CV reload, but not resettting the count
this would cause short and long blinks during breathing.
this change allows the CV to update at 50Hz (20 ms) asynchronously.
So the LED update rate of 40Hz (25) will take effect on the next
FTM counter change, end of the prescaler counting, after CnV register
was written.update.
a b c d
LED PWM ___-___-___-___-___-___-___-___-___-___
LED Data ____-____-____-____-____-____-____-____-
a b c d
This will disable the fxos8701cq internal mag on
the NXPHlite. There are random noise spikes on the
HIGHRES_IMU.[x|y|x]mag. Even with all other SPI
devices shut down, the noise is still present.
It seems that the oneline to find the process ID of any running jMAVSim
instance was not working correctly.
1. On Linux, the name of the process does not contain Simulator but
jmavsim_run.jar. Also, it triggers incorrectly, if you have opened
Simulator.java using the command line :).
2. The cutting to get the PID at the end does not work as intenteded and
gives the username instead of PID, at least on Arch Linux. Using awk
should fix this.
Starting with cmake version 3.12 the cmake -E copy_directory
command fails if the source directory does not exist. This results
in a build failure. This fix creates the source directory before
the copy which does not harm if the source directory exists.
Closes: #10368
Beat Küng
Roman
David Sidrane
Daniel Agar
Julian Oes
Hamish Willee
mcsauder
PX4 Build Bot
fredowski