Hello,
my drone has a Pixhawk 2.4.8 controler –>I want make telemetry with a TEMPERATURE_SENSOR_MLX90614 (on the right side)
then I need a firmware update
–> I have 3 questions:
which board to select here: ArduPilot firmware : /Copter/stable-4.6.3 ?
I suppose the .apj is the file to download?
In the Feature.txt file, what does means the ! at the beginning of the line?
thanks a lot
Vincent
Pixhawk1-bdshot if you want bdshot functionality. The -1M version if you only have 1 MB but I guess the 2.4.8 all have 2MB.
Go here and see if the default version of firmware includes the sensor you want to use. It does not, so enable it, create the custom version and flash that: Custom Firmware Builder
seams the pixhawk 2.4.8 is a 2MO
Then you can use the Pixhawk1 or the Pixhawk1-bdshot for bdshot support (recommended). But I see that you need support for that particular sensor so as Dave said, you need to build a custom firmware yourself. You can base this firmware upon the Pixhawk1-bdshot version and then enable that sensor.
Thanks Evans, I will do it
what means bdshot support?
Bi-directional dshot. This enables you to obtain esc rpm and any other data sent by ESCs to the FC if you use a BlHeli or Blujay flashed (recommended) ESC so that you can do ESC RPM based harmonic notch filtering.
Thanks a lot Evans & Dave, I can continue my project (copter with temperature + vibration sensors)
we solve the issue for temperature sensor: MLX90614 MLX90614ESF-BAA-000-TU Melexis Technologies NV | Capteurs, transducteurs | DigiKey
I need now to do the same study for vibration sensor VIB01 Analog vibration sensor | Joy-IT (maybe in a new post)
I will connect the temperature sensor on I2C–>does I2C is configured/enabled here?
No, that is for displays. You just need to enable that sensor under Sensors → Enable Temp Sensor - MLX90614
good…( will do the test tomorrow)
on the Copter/pixhawk, I have already this firmware: fmuv2 (all calibration done and copter already flight)
if I upload the new firmware, seems previous parameters will not be lost (I will save it before anyway)
That is correct, at least if you do not switch the FW type. If you do… then it might work as well.
That is the safest way, but do not upload them unless you are sure that the parameters on the FC are wrong.
If I am correct some read only params like tcal cannot be written from a savefile in Mission Planner. But I recently discovered that you can manually change the read-only params from QGC if you like.
Never understood the functional difference between fmuv* and Pixhawk1*. I think fmuv2 is 1MB while fmuv3 is almost same as Pixhawk1
if you do not switch the FW type?
means?
What you just did. You switched the FW type from fmuv2 to pixhawk1.
Hi Evans, pixhawk1 firmware uploaded with custo for temperature sensor :
all configured in MP Setup (see image below)
Now, I try to read the temperature in MP/Data/State but I can’t find it…
I have this temp parameters but not moving:
the same for
no I2C parameters
an idea?
Does the sensor show up in the HW ID tab?
Also, just ensure the i2c bus and the address is correct
-HW ID tab? you mean in MP:
—>I even don’t know the name of the parameter!-for I2C Bus, I tried Temp1_addr=90 (as written in Temperature Sensors — Copter documentation)
-I tried also TEMP1_BUS=0 or 1
-it seems there is an IEC terminal to check the address but I don’t know how to use it
–>I2C Bus Peripherals | PX4 Guide (main)
Modules Reference: Command | PX4 Guide (main)
FYI, here is Mavlink inspector…where i can find the temperature measured?
Yes in MP. HW ID is under the Setup → Mandatory tab. The tuning parameters you enabled are IMU temperatures - not what you want since you are using an external temperature. I think it will be present under a mavlink message but I don’t know the name. Someone else may pitch in and help with this. Also I didn’t check the links you shared but they seem to be PX4’s, and not ArduPilot’s.
You might have to set TEMP_LOG to enable logging.
But before that I see that you have temp data from IMU2. Do you really have a second IMU?
Temp parameters described here: Temperature Sensors — Copter documentation:
(I don’t clearly understand the last folder “Logging/OSD¶”
I will try anyway TEMP_LOG=1
IMU…I don’t know what it is
OK for PX4
