"Exception thrown while processing service call: timeout” error #272
Comments
|
|
Thank you for your response. I've previously updates crazyflies but not the radio. By updating radio, I'm able to get battery values. I have two other issues now.
I'm able to run all the codes but I was just wondering why is it not able to checkout that specific sub-module. All the other sub-modules are updated.
... logging to /home/ottelab/.ros/log/03bada0c-25da-11eb-8272-9cefd5fcd5b4/roslaunch-ottelab-Precision-Tower-3620-24472.log started roslaunch server http://ottelab-Precision-Tower-3620:43053/ SUMMARY PARAMETERS
NODES auto-starting new master setting /run_id to 03bada0c-25da-11eb-8272-9cefd5fcd5b4 Actually, one time, I could run without any errors and when I hit the start button in joystick, it did takeoff. But I'm not able to do that again. I end up with above output. I do kill the crazyswarn_server and all other nodes before every run. My crazyflies.yaml is as follows
allCrazyflies.yaml is as follows:
hower_swarm.launch is as follows: My crazyflie name in vicon is cf1 and tracking is enabled in vicon. Because I'm using 'motionCapture', I believe I need not set the markers position or anything in this mode. Please let me know why I'm facing the Eigen Assertion error mentioned above. As I was able to fly once and I can see cf1 parameters being loaded, I'm assuming the communication between vicon and my ROS system is established. |
|
|
I had this submodule error too under Crazyswarm, but I couldn't reproduce it in a standalone clone of bitcraze/crazyflie-firmware. I don't know what is going on. |
|
@whoenig I am using Ubuntu 16.04 with ROS kinetic. I am getting the eigen value error sometimes, but not always. Now, the crazyflie takes off but doesn't hover, instead it's just crashing. What can be the possible issues for this behaviour? Also, you mentioned previously, that I can navigate using waypoints. Can you please let me know how to do that? It would help even if you can point me towards an existing tutorial for this. Thanks a lot for the help! |
|
Crashes are mostly related to tracking issues. Make sure all firmwares (radio + NRF + STM) were updated. Make sure the coordinate system is correct by moving the drone manually and looking and the Perhaps https://drive.google.com/file/d/15favAyrLLpC_O6nrAp-eIbZijFUMLgwV/view helps? There is an example on slide 9 for a simple script. The function you are looking for is called |
|
Thank you that helps! I'm trying to do it first in simulation but I have two errors. If I do |
|
We have now added mixed python 2/3 support so you must specify the environment variable: |
|
Thanks for he help! I observe the crazyflie crashing with both motionCapture and libobjecttracker modes. With motioncapture, after the crazyflie takes off, I get a warning saying that "No pose updated" and with libobjecttracker, it says "ICP did not converge" and "[pcl::IterativeClosestPoint::computeTransformation] Not enough correspondences found. Relax your threshold parameters." I have seen in one of the forums that "libobjecttrcaker" is preferred. If so, can you address the error mentioned above. If not, can you give some suggestions on how to fix the motioncapture error? I have ensured that NRF+STM+radio are all updated. The coordinate system matches with the VICON. And I also updated the marker positions in crazyflieTypes.yaml for libobjecttracker mode. Tracking is enabled for motioncapture and disabled for libobjecttracker. |
TL;DR We could reproduce the same problem on Ubuntu 16.04 but not on Ubuntu 18.04. Turns out that it is an issue related to the Git version. Ubuntu 16.04 ships with Git 2.7 while Ubuntu 18.04 has Git 2.17. As far as I understand the behavior of @jpreiss If you can confirm this it might be worth adding a note to the documentation or pinning an issue so people find it easily. Also, sorry for being slightly off-topic here. |
|
@MauroPfister Thanks for the fix! Yes, adding that to the documentation might help many other people who are using the Crazyswarm on 16.04. @manikamakam The errors you mention indicate that the tracking didn't work. Usually the key question is if the tracking issues occur before or after the crash. One thing to note is that if you operate right at the limit of your mocap (e.g., markers too small, cameras far away etc.) tracking can be very difficult. The best solution in that case is to use single-marker-mode (with libobjecttracker) and put a single, larger marker on top. Make sure that whatever marker you use, that the marker appears at least as 3 pixels on each relevant motion capture camera. Also can you confirm that you verified the tracking and communication by logging |
|
Dear @whoenig, I am trying to run a python script to control 4 crazyflies. When I `roslaunch crazyflie_demo a_multi_position1119.launch‘, I encountered the same problem: ’Exception thrown while processing service call: timeout |
|
@ZimingR Please open a new discussion topic for your problem. When you do, make sure you include your crazyflies.yaml, as well as the URI (rate, address, channel) of your Crazyflies. |
|
Thanks a lot！ |
|
@ZimingR Have you solved the problem that the service throws exception "time out" when launch the razyflie_demo multi_teleop_xbox360.launch file |
|
Sorry, not yet.
hit-JB ***@***.***>于2021年12月6日 周一下午8:48写道：
… @ZimingR <https://github.com/ZimingR> Have you solved the problem that
the service throws exception "time out" when launch the razyflie_demo
multi_teleop_xbox360.launch file
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#272 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AVFE3U4DYHUOVXRMAXRFQ4LUPSWKHANCNFSM4TOVXTPA>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
|
Hello,
I am trying to use the crazyswarm repo to fly two crazyflies (for now) using VICON system. I have gotten to a place where our ROS system recognizes the existence of crazyflies. I verified this with the provided chooser.py script.
First issue: If I click reboot, I can observe the crazyflies switching off and turning back on, thus proving that the connection is established. However, if I click on battery, I see 0.00V for both of them though their batteries are charged. I'm not sure why reboot is working but not the battery option.
Second issue: I've selected only one crazyflie from the chooser.py. Before going to VICON, I want to fly the crazyflie with joystick. When I run
roslaunch crazyflie_demo teleop_xbox360.launch uri:=radio://0/100/2M, it throws an error saying “Exception thrown while processing service call: timeout”. No values were found in the IMU topic and we can’t see the crazyflie on the RViz display. The uri is correct as I cross-verified by runningrosrun crazyflie_tools scan -v. I think the connection is established as the reboot is working in chooser.py script. But I'm unsure on why I'm facing this error.Any suggestions to solve these issues would be greatly appreciated. Thank you.
The text was updated successfully, but these errors were encountered: