Custom
Works, but new line gets added in configs.txt with the same value. Is the last value counted? I have 2 lines with the same variable, 1 line is auto added and 2nd line is with # Custom
From a search of the codebase:
- Here’s the removal code
- The protection word is
custom(but the check is not case sensitive)
That is at least the case for GPIO settings - it’s unclear whether it’s also the case for more general overlays and the like, but that would be quite a common approach to processing a configuration file.
Ok, it was harware issue. We fixed it with a soldering a jumper. Now we have all I2C devices.
Trying to flash arduplane firmware and check all sensors through Mission planner
Do you have a developer guide how to compile production version of BlueOS? @williangalvani github BlueOS
I linked an issue here bug: Is there a build guide available on how to get a raspberry pi image? · Issue #2859 · bluerobotics/BlueOS · GitHub
Ok, I built the new .tar for Raspberry to change address of a megnetometer. Updated it, and now I do not have any boards detected at all. Even though all sensors in I2C show up via terminal. I have magnetometer, barometer, etc available.
We changed address of magnetometer to match ours 0x0D instead of 0x0C in Detector.py
I am stuck on it…
Hi @rosss,
Can you share the log of your system ? Most important is ardupilot manager log.
Be aware that changing the detector is also not enough, the i2c address also should match ardupilot values.
logfile_08-22-2024_10_02_26.log (2.9 MB)
where should I change ardupilot values as well? It won’t even let me install ardupilot firmware first as the board is not detected
Magnetometer is still WIP, will send a video of a flight test on an electric wing and on a gas powered UAV
The Flying Lab
1 Like
Ok, so we are able to configure everything including video, telemetry over LTE (3G/4G). But PWM rail does not work further. The power is fully ok on the PWM rail, but signal does not output anything. We checked with oscilloscope, no “rectangles” are being output. Is in BLUEOS some option to enable PWM signal??
Here is a comparison of CUAV X7 and our copy of Navigator using oscilloscope and PWM signal outputs.
Maybe I need to turn on PWM somehow as the guy refers here? Problems with pwm outputs and other issues - #2 by tony-white
something like Navigator Assistan or toggle PWM enable