-
Notifications
You must be signed in to change notification settings - Fork 195
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
开启风插件失败 #79
Comments
|
文档说是加这个libWindPlugin.so,但是我根本没找到这个动态库 |
你好,正如教程里面提及的,"libWindPlugin.so"为Gazebo9自带动态共享库,而不是PX4生成的,一般该文件就在环境变量GAZEBO_PLUGIN_PATH的路径中。 如果你想要找寻该文件,可以在根目录下搜索该文件名进行查找。以我的环境为例子,这个动态库处于/usr/lib/x86_64-linux-gnu/gazebo-11/plugins下。(注:我使用的是gazebo11,但是gazebo9是类似的,这并不影响) |
你好,我成功加入了风插件,但是好像没用产生作用。无人机飞行没有受到影响 |
也没有找到和风相关的话题 |
你可以尝试在launch文件中将gazebo config下的verbose标签打开以查看更多信息。可能会有一条关于风插件的err信息提示你是否需要设置一些参数 |
注意,当您修改之后,建议可以采用QGC令飞机旋停的方式来检测场景中是否有风,检测无人机旋停的姿态即可 |
您好,我打开了verbose这是终端的信息,我并没有看到和风插件相关的 |
你可能弄混了一点:风速信息是以gazebo内部的topic类型发布的,而非ROS的消息发布,用rostopic是无法找到的。 首先,你可以通过(比如)在QGC中令无人机起飞并旋停,通过观察无人机的旋停姿态来确认当前场景内部有没有风; |
您好,这是悬停时候的姿态,应该是没有风的。 /gazebo/default/atmosphere 然后这是我的world文件的前面部分,·我还是没找到哪里出了问题:
|
请问你的PX4用的是什么版本? |
您好,是1.11版本的 |
直接使用windy.world也是没有风的状态吗 |
我的电脑上没有找到windy.world这个文件 |
默认环境下,世界文件都应该处于路径 |
我在indoor1.world中加入了下面这个
base_link
1 0 0
0 1 0
4.0
0 0 0
0
0
0
world_wind
然后gazebo就报错了
[INFO] [1681302260.387756, 0.000000]: Calling service /gazebo/spawn_sdf_model
[ INFO] [1681302260.393789246]: waitForService: Service [/gazebo/set_physics_properties] is now available.
gzserver: /usr/include/boost/smart_ptr/shared_ptr.hpp:734: typename boost::detail::sp_member_access::type boost::shared_ptr::operator->() const [with T = gazebo::event::Connection; typename boost::detail::sp_member_access::type = gazebo::event::Connection*]: Assertion `px != 0' failed.
Service call failed: transport error completing service call: unable to receive data from sender, check sender's logs for details
[ERROR] [1681302261.614085, 0.000000]: Spawn service failed. Exiting.
Aborted (core dumped)
[gazebo-1] process has died [pid 102629, exit code 134, cmd /home/luochen/catkin_ws/src/gazebo_ros_pkgs/gazebo_ros/scripts/gzserver -e ode /home/luochen/PX4_Firmware/Tools/sitl_gazebo/worlds/indoor1.world __name:=gazebo __log:=/home/luochen/.ros/log/45318b32-d92b-11ed-bcdd-d5d4b190bca3/gazebo-1.log].
log file: /home/luochen/.ros/log/45318b32-d92b-11ed-bcdd-d5d4b190bca3/gazebo-1*.log
[iris_0/iris_0_spawn-4] process has died [pid 102657, exit code 1, cmd /home/luochen/catkin_ws/devel/lib/gazebo_ros/spawn_model -sdf -param model_description -model iris_0 -x 0 -y -4.5 -z 1 -R 0 -P 0 -Y 1.570796 __name:=iris_0_spawn __log:=/home/luochen/.ros/log/45318b32-d92b-11ed-bcdd-d5d4b190bca3/iris_0-iris_0_spawn-4.log].
log file: /home/luochen/.ros/log/45318b32-d92b-11ed-bcdd-d5d4b190bca3/iris_0-iris_0_spawn-4*.log
The text was updated successfully, but these errors were encountered: