cliansang / uwb-tracking-ros Goto Github PK

I am trying to run this on ros-melodic with python 2.7 but I keep getting

AttributeError: module 'enum' has no attribute 'IntFlag' error

I see that it has only been tested on ROS-Noetic, so does this mean there is a dependency where it can only runon python 3.x or can it be run on python 2.x too?

First time to get this location info into ROS! However, only three nodes show up, when network has 4 anchors, 1 tag, and 1 listener. Does this program require the Android tablet be left running, or is it just for setting up the uwb network? Sometimes the tracking is very slow, and at other times it zips along. I don't know what is affecting this or causing this! Have you found the same thing, with unreliable speed response?

From the documentation and Decawave forum, I see that "stationary detection" may be turned off for the Tag, and this will cause the 10 Hz update rate to continue, and the Tag will not switch to the "energy conserving" 0.1 Hz update rate. This can be done under Tag settings on the Android App. I will try this next. It seems to have the "energy conservation" settings much too aggressive by default. That causes it to often run much too slowly. Updating position every 10 seconds would never work for a rover robot! Or for a flying robot, for that matter.

Thank you for the answer, yes, this made a great difference! Testing was much more successful.

However, sometimes the Tag shows in the ROS output, and at other times it isn't there. I see just two devices reporting through the ROS topics. What we need most of all is to be able to plug the USB into the active Tag and get it's location. This will be on the robot and assisting with location awareness. To listen to a passive device and then send that data to the robot will only slow down the process.

And I didn't see any output on the Rviz grid. It stays blank.

Thank you @cliansang for setting up this repository! I'm planning on using the same device, and your work is a helpful start to understand the serial interface required.

I'm currently having some challenges getting the listener recognized by the PC. Previously I was able to get one of the anchors to pop up in the dev/ directory as the expected ACM0, but I have had trouble reproducing that, and the listener beacon does not appear anywhere visible in the directory.

From your experience, is there a specific configuration needed to allow the UART communication? I haven't seen the documentation say that specifically. Additionally, will the communication only occur when there is a valid network setup for the tag to publish information about, or should the single unit bench test work to configure the serial communication.

Thanks again