rroche
November 22, 2023, 6:01pm
1
Discord is the easiest way to communicate over voice, video, and text. Chat, hang out, and stay close with your friends and communities.
Community Announcement
Community Q&A
General Discussions
Proposal to have a four-week break from community calls from December 18th to January 15th
Specify what you are trying to achieve
Specify what environment / platform you are using
Prepare a Link or Document to help understand if possible
First, ask the question on Discord or create a Github Issue !
If you take over 5 minutes for the question, please continue in Discord or a GitHub Issue.
ADS1115 ADCs on FMUv6X using 12S using PX4 v1.14
Hey everyone!
We’re experiencing the same issue. Our setup includes a 6X and two external ADS1115 ADCs connected to POWER 1 and 2. We’re running on 12s, PX4 1.14 and the ADC_ADS1115_EN parameter enabled. We do have valid voltage and current readings on both channels. During booting we usually (>75%) get the “System Power unavailable” message.
Help would be greatly appreciated.
Kind regards,
Heiko
Console output:
HW arch: PX4_FMU_V6X
HW type: V6X000003
HW version: 0x000
HW revision: 0x003
P…
Answer: Please open an issue on GitHub we will get back to you (@dagar )
opened 10:47AM - 29 Nov 23 UTC
stale
bug-report
### Describe the bug
Hi! I have written a node, which publishes velocity offboa… rd-commands using the uxrce-dds-bridge.
The trajectory_setpoint and offboard_control_mode messages get transmitted and are visible in uorb (see below)
However when i try to switch to offboard mode, i get the following error (see sreenshot below): "Critical: Switching to mode 'Offboard' is currently not possible No offboard signal"
Arming the vehicle via uxrce_dds bridge while in offboard-mode and with skipping of the pre-flight checks causes the vehicle to immediatly go into failsafe with the same error.
Using the px4_ros_com offboard_control node causes the same problem.
The relevant part of my code:
```
VelocityController::VelocityController(void) : Node("px4_offboard_control") {
controll_mode_msg.position = false;
controll_mode_msg.velocity = true;
pub_offboard_control_mode = this->create_publisher<px4_msgs::msg::OffboardControlMode>("/fmu/in/offboard_control_mode", 10);
pub_trajectory_setpoint = this->create_publisher<px4_msgs::msg::TrajectorySetpoint>("/fmu/in/trajectory_setpoint", 10);
...
}
...
void VelocityController::publish_trajectory_setpoint(void){
publish_offboard_control_mode();
timestamp = this->get_clock()->now().nanoseconds() / 1000;
publish(trajectory_msg);
}
...
void VelocityController::publish_offboard_control_mode()
{
controll_mode_msg.timestamp = this->get_clock()->now().nanoseconds() / 1000;
pub_offboard_control_mode->publish(controll_mode_msg);
}
```
### To Reproduce
- Turn on Rover
- On Companion: start uxrce-dds-bridge
- On Companion start either px4_ros_com offboard_control or px4_offboard_control velocity_controller
- Disengage kill switch
- Arm Rover
- Switch to Offboard mode
### Expected behavior
Rover should slowly drive West
### Screenshot / Media
### Flight Log
https://logs.px4.io/plot_app?log=3c4983fe-dae7-4ba4-b823-88a2fa28ce32
### Software Version
https://github.com/PX4/PX4-Autopilot/commit/6a34b63b60251aa15703a66ad9f4479943868f16
HW arch: NXP_MR_CANHUBK3
HW type: MR-CANHUBK3-ADAP
HW version: 0x000
HW revision: 0x000
PX4 git-hash: 6a34b63b60251aa15703a66ad9f4479943868f16
PX4 version: 1.15.0 0 (17760256)
PX4 git-branch: main
OS: NuttX
OS version: Release 11.0.0 (184549631)
OS git-hash: e7da5ac0e660238cb353948b2a9118579727267a
Build datetime: Nov 28 2023 16:44:37
Build uri: localhost
Build variant: fmu
Toolchain: GNU GCC, 9.3.1 20200408 (release)
PX4GUID: 00086702193221071965ffffffffffffffff
MCU: S32K344, rev. 0
### Flight controller
NXP_MR_CANHUBK3
### Vehicle type
Rover
### How are the different components wired up (including port information)
_No response_
### Additional context
_No response_
Eduarto-toptal : Built a simulator in MAVLink with PX4 using Unity. The drone is flying, but there are still some behaviors from unhealthy sensors that appear sometimes, and we would like to nail down what might be the cause.
Question: YAW is not working. How can we debug?Answer: Please post a log and open an issue we can help debug. (@dagar )
Answer: Look at the datasheet and ensure you understand all the data you need from the device. Once you get the basic driver infrastructure, we must define the new data that no other airspeed uses.
https://www.swiss-airdata.com/products/adp55
C_G
November 28, 2023, 5:09pm
2
What time does this start?
rroche
November 29, 2023, 4:21pm
3
Depends on where you are, here’s a link to the calendar
Community Announcement
Community Q&A (No deep technical discussions)
Guideline for asking a Question
General Discussions