# MAVROS에서 PX4로 사용자 정의 메시지 전송
WARNING
이 문서는 다음 환경에서 테스트하였습니다.
- Ubuntu: 20.04
- ROS: Noetic
- PX4 Firmware: v1.12.3
그러나 이러한 단계는 상당히 일반적이므로 수정이 거의 없이 다른 배포판/버전에서 작동합니다.
# MAVROS 설치
mavlink/mavros (opens new window)의 소스 설치 지침에 따라 "ROS Kinetic"을 설치합니다.
# MAVROS
아래 코드를 사용하여 이 예에서 keyboard_command.cpp(workspace/src/mavros/mavros_extras/src/plugins에 있음)라는 이름의 새 MAVROS 플러그인을 생성합니다.
이 코드는 ROS 주제
/mavros/keyboard_command/keyboard_sub
의 'char' 메시지를 구독하고 MAVLink 메시지로 전송합니다.#include <mavros/mavros_plugin.h> #include <pluginlib/class_list_macros.h> #include <iostream> #include <std_msgs/Char.h> namespace mavros { namespace extra_plugins{ class KeyboardCommandPlugin : public plugin::PluginBase { public: KeyboardCommandPlugin() : PluginBase(), nh("~keyboard_command") { }; void initialize(UAS &uas_) { PluginBase::initialize(uas_); keyboard_sub = nh.subscribe("keyboard_sub", 10, &KeyboardCommandPlugin::keyboard_cb, this); }; Subscriptions get_subscriptions() { return {/* RX disabled */ }; } private: ros::NodeHandle nh; ros::Subscriber keyboard_sub; void keyboard_cb(const std_msgs::Char::ConstPtr &req) { std::cout << "Got Char : " << req->data << std::endl; mavlink::common::msg::KEY_COMMAND kc {}; kc.command = req->data; UAS_FCU(m_uas)->send_message_ignore_drop(kc); } }; } // namespace extra_plugins } // namespace mavros PLUGINLIB_EXPORT_CLASS(mavros::extra_plugins::KeyboardCommandPlugin, mavros::plugin::PluginBase)
mavros_plugins.xml(workspace/src/mavros/mavros_extras)을 편집하고 다음 줄을 추가합니다.
<class name="keyboard_command" type="mavros::extra_plugins::KeyboardCommandPlugin" base_class_type="mavros::plugin::PluginBase"> <description>Accepts keyboard command.</description> </class>
CMakeLists.txt(workspace/src/mavros/mavros_extras)를 편집하고
add_library
에 다음 줄을 추가합니다.add_library( ... src/plugins/keyboard_command.cpp )
(workspace/src/mavlink/message_definitions/v1.0)의 common.xml 내부에서 다음 줄을 복사하여 MAVLink 메시지를 추가합니다.
... <message id="229" name="KEY_COMMAND"> <description>Keyboard char command.</description> <field type="char" name="command"> </field> </message> ...
# PX4 수정사항
- Inside common.xml (in PX4-Autopilot/src/modules/mavlink/mavlink/message_definitions/v1.0), add your MAVLink message as following (same procedure as for MAVROS section above):
... <message id="229" name="KEY_COMMAND"> <description>Keyboard char command.</description> <field type="char" name="command"> </field> </message> ...
WARNING
Make sure that the common.xml files in the following directories are exactly the same:
PX4-Autopilot/src/modules/mavlink/mavlink/message_definitions/v1.0
workspace/src/mavlink/message_definitions/v1.0
are exactly the same.
(PX4-Autopilot/msg)에서 자신만의 uORB 메시지 파일 key_command.msg를 만듭니다. 이 예에서 "key_command.msg"에는 다음 코드만 있습니다.
uint64 timestamp # time since system start (microseconds) char cmd
Then, in CMakeLists.txt (in PX4-Autopilot/msg), include:
set( ... key_command.msg )
mavlink_receiver.h를 편집합니다. (PX4-Autopilot/src/modules/mavlink)
... #include <uORB/topics/key_command.h> ... class MavlinkReceiver { ... private: void handle_message_key_command(mavlink_message_t *msg); ... orb_advert_t _key_command_pub{nullptr}; }
mavlink_receiver.cpp를 수정합니다(PX4-Autopilot/src/modules/mavlink). 여기에서 PX4는 ROS에서 보낸 MAVLink 메시지를 수신하고, 이를 uORB 주제로 게시합니다.
... void MavlinkReceiver::handle_message(mavlink_message_t *msg) { ... case MAVLINK_MSG_ID_KEY_COMMAND: handle_message_key_command(msg); break; ... } ... void MavlinkReceiver::handle_message_key_command(mavlink_message_t *msg) { mavlink_key_command_t man; mavlink_msg_key_command_decode(msg, &man); struct key_command_s key = {}; key.timestamp = hrt_absolute_time(); key.cmd = man.command; if (_key_command_pub == nullptr) { _key_command_pub = orb_advertise(ORB_ID(key_command), &key); } else { orb_publish(ORB_ID(key_command), _key_command_pub, &key); } }
예제 구독자 모듈처럼 자신만의 uORB 주제 구독자를 생성합니다. 이 예에서는 (/PX4-Autopilot/src/modules/key_receiver)에서 모델을 생성할 수 있습니다. In this directory, create three files CMakeLists.txt, key_receiver.cpp, Kconfig Each one looks like the following.
-CMakeLists.txt
px4_add_module( MODULE modules__key_receiver MAIN key_receiver STACK_MAIN 2500 STACK_MAX 4000 SRCS key_receiver.cpp DEPENDS )
-key_receiver.cpp
#include <px4_platform_common/px4_config.h> #include <px4_platform_common/tasks.h> #include <px4_platform_common/posix.h> #include <unistd.h> #include <stdio.h> #include <poll.h> #include <string.h> #include <math.h> #include <uORB/uORB.h> #include <uORB/topics/key_command.h> extern "C" __EXPORT int key_receiver_main(int argc, char **argv); int key_receiver_main(int argc, char **argv) { int key_sub_fd = orb_subscribe(ORB_ID(key_command)); orb_set_interval(key_sub_fd, 200); // limit the update rate to 200ms px4_pollfd_struct_t fds[] = { { .fd = keyboard_sub_fd, .events = POLLIN }, }; int error_counter = 0; for (int i = 0; i < 10; i++) { int poll_ret = px4_poll(fds, 1, 1000); if (poll_ret == 0) { PX4_ERR("Got no data within a second"); } else if (poll_ret < 0) { if (error_counter < 10 || error_counter % 50 == 0) { PX4_ERR("ERROR return value from poll(): %d", poll_ret); } error_counter++; } else { if (fds[0].revents & POLLIN) { struct key_command_s input; orb_copy(ORB_ID(key_command), key_sub_fd, &input); PX4_INFO("Received Char : %c", input.cmd); } } } return 0; }
-Kconfig
menuconfig MODULES_KEY_RECEIVER bool "key_receiver" default n ---help--- Enable support for key_receiver
자세한 설명은 첫 번째 지원서 작성 항목을 참고하십시오.
Lastly, add your module in the default.px4board file correspondent to your board in PX4-Autopilot/boards/. For example: -for the Pixhawk 4, add the following code in PX4-Autopilot/boards/px4/fmu-v5/default.px4board: -for the SITL, add the following code in PX4-Autopilot/boards/px4/sitl/default.px4board
CONFIG_MODULES_KEY_RECEIVER=y
MODULES ...
# Building
# Build for ROS
In your workspace enter:
catkin build
.Beforehand, you have to set your "px4.launch" in (/workspace/src/mavros/mavros/launch). Edit "px4.launch" as below. If you are using USB to connect your computer with Pixhawk, you have to set "fcu_url" as shown below. But, if you are using CP2102 to connect your computer with Pixhawk, you have to replace "ttyACM0" with "ttyUSB0". And if you are using the SITL to connect to your terminal, you have to replace "/dev/ttyACM0:57600" with "udp://:14540@127.0.0.1:14557". Modifying "gcs_url" is to connect your Pixhawk with UDP, because serial communication cannot accept MAVROS, and your nutshell connection simultaneously.
Write your IP address at "xxx.xx.xxx.xxx"
... <arg name="fcu_url" default="/dev/ttyACM0:57600" /> <arg name="gcs_url" default="udp://:14550@xxx.xx.xxx.xxx:14557" /> ...
# ROS 빌드
Clean the previously built PX4-Autopilot directory. In the root of PX4-Autopilot directory:
make clean
Build PX4-Autopilot and upload in the normal way.
For example:
- to build for Pixhawk 4/FMUv5 execute the following command in the root of the PX4-Autopilot directory:
make px4_fmu-v5_default upload
- to build for SITL execute the following command in the root of the PX4-Autopilot directory (using jmavsim simulation):
make px4_sitl jmavsim
# 빌드
이제 작업을 빌드할 준비가 되었습니다!
# PX4 빌드
- In a terminal enter
roslaunch mavros px4.launch
- In a second terminal run:This means, publish 97 ('a' in ASCII) to ROS topic "/mavros/keyboard_command/keyboard_sub" in message type "std_msgs/Char". "-r 10" means to publish continuously in "10Hz".
rostopic pub -r 10 /mavros/keyboard_command/keyboard_sub std_msgs/Char 97
# ROS 실행
Enter the Pixhawk nutshell through UDP. Replace xxx.xx.xxx.xxx with your IP.
roslaunch mavros px4.launch
After few seconds, press Enter a couple of times. You should see a prompt in the terminal as below:
rostopic pub -r 10 /mavros/keyboard_command/keyboard_sub std_msgs/Char 97
Type "key_receiver", to run your subscriber module.
nsh> key_receiver
MAVROS 메시지가 PX4로 전송되는 지 테스트합니다.