Getting Error with dwm_loc_ekf_multi_hover.launch with ros

Discussions about all things Bitcraze
Post Reply
anchekuri
Beginner
Posts: 2
Joined: Wed Oct 11, 2017 2:50 am

Getting Error with dwm_loc_ekf_multi_hover.launch with ros

Post by anchekuri » Wed Oct 11, 2017 3:06 am

I am using ubuntu 16.04 and using kinetic ros for the multiple crazyflie hovering. I changed the addresses of the crazyflie with radio://0/100/1M/E7E7E7E701 and radio://0/50/1M/E7E7E7E702 and made launch command for the multi cf launch as

roslaunch bitcraze_lps_estimator dwm_loc_ekf_multi_hover.launch uri0:=radio://0/100/1M/E7E7E7E701 uri1:=radio://0/50/1M/E7E7E7E702

And Changed in the launch with the current radio addresses. After running the current launch file I am having a run time errors that says process has died

[INFO] [1507689729.225590]: Setting anchor position ...
[INFO] [1507689729.232034]: Anchor 0 at [0, 0, 1.85]
[ INFO] [1507689729.274640597]: Update parameters
[INFO] [1507689729.275781]: Anchor 4 at [1.3, 1, 1.85]
terminate called after throwing an instance of 'std::runtime_error'
what(): Could not find acc.x in log toc!
Traceback (most recent call last):
Traceback (most recent call last):
File "/root/catkin_ws/src/lps-ros/scripts/lps_ekf_bridge.py", line 77, in <module>
File "/root/catkin_ws/src/lps-ros/scripts/lps_ekf_bridge.py", line 77, in <module>
update_params([name + 'x', name + 'y', name + 'z'])
update_params([name + 'x', name + 'y', name + 'z'])
File "/opt/ros/kinetic/lib/python2.7/dist-packages/rospy/impl/tcpros_service.py", line 435, in __call__
File "/opt/ros/kinetic/lib/python2.7/dist-packages/rospy/impl/tcpros_service.py", line 435, in __call__
return self.call(*args, **kwds)
return self.call(*args, **kwds)
File "/opt/ros/kinetic/lib/python2.7/dist-packages/rospy/impl/tcpros_service.py", line 525, in call
File "/opt/ros/kinetic/lib/python2.7/dist-packages/rospy/impl/tcpros_service.py", line 525, in call
raise ServiceException("transport error completing service call: %s"%(str(e)))
raise ServiceException("transport error completing service call: %s"%(str(e)))
rospy.servicerospy.service..ServiceExceptionServiceException: : transport error completing service call: unable to receive data from sender, check sender's logs for detailstransport error completing service call: unable to receive data from sender, check sender's logs for details

[crazyflie_server-18] process has died [pid 1294, exit code -6, cmd /root/catkin_ws/devel/lib/crazyflie_driver/crazyflie_server __name:=crazyflie_server __log:=/root/.ros/log/c409e06e-ae2d-11e7-ba7c-b88a60e5eba6/crazyflie_server-18.log].
log file: /root/.ros/log/c409e06e-ae2d-11e7-ba7c-b88a60e5eba6/crazyflie_server-18*.log
[crazyflie0/lps_efk_bridge-8] process has died [pid 1209, exit code 1, cmd /root/catkin_ws/src/lps-ros/scripts/lps_ekf_bridge.py __name:=lps_efk_bridge __log:=/root/.ros/log/c409e06e-ae2d-11e7-ba7c-b88a60e5eba6/crazyflie0-lps_efk_bridge-8.log].
log file: /root/.ros/log/c409e06e-ae2d-11e7-ba7c-b88a60e5eba6/crazyflie0-lps_efk_bridge-8*.log
[crazyflie1/lps_efk_bridge-15] process has died [pid 1268, exit code 1, cmd /root/catkin_ws/src/lps-ros/scripts/lps_ekf_bridge.py __name:=lps_efk_bridge __log:=/root/.ros/log/c409e06e-ae2d-11e7-ba7c-b88a60e5eba6/crazyflie1-lps_efk_bridge-15.log].
log file: /root/.ros/log/c409e06e-ae2d-11e7-ba7c-b88a60e5eba6/crazyflie1-lps_efk_bridge-15*.log

^C[link1_broadcaster-17] killing on exit

I have removed everything and tried to reinstall it again but it was the same error . I was not sure what the error was But I tried to check the path of the file given in the error but found. but not sure about the error .


And in the Rviz the robot model it is showing status:error

Any help will be appreciated . Thank you,

Appala Chekuri

arnaud
Bitcraze
Posts: 1281
Joined: Tue Feb 06, 2007 12:36 pm

Re: Getting Error with dwm_loc_ekf_multi_hover.launch with ros

Post by arnaud » Mon Oct 16, 2017 12:49 pm

Hi,
What version of the firmware are you using? It looks like the ros nodes cannot find all the log variables they need and this could be because you are using an old firmware or a firmware without Kalman filter enabled.

Post Reply