Wrong timestamps when running with noetic

[bedaberner]

Environment
Please complete the following information.
ROS distribution: noetic
Operating system: 20.04
Python version: 3.8

natnet_ros version
Try the latest commit in the dev branch in case your issue is already fixed.
natnet_ros branch: dev

Describe the bug
When running the driver with ros noetic under python 3.8, the timestamps are not in the expected time reference.

As is described in the python_natnet package, the time source used for the timestamps is timeit.default_timer.
The source for timeit.default_timer seems to change between python2.7 (where it is time since last epoch) and python 3.8 (where it seems to be since boot time of the system).
This means, that in noetic which uses python 3.8, the timestamps don't match and are not usable for tf transforms etc.

[mje-nz]

Thanks for the report :)

I don't have time to work on this at the moment, but I would certainly accept a PR.

[aarsht7]

Hey @bedaberner I am trying to connect to the Motive 2.2.0 using ros noetic but I am facing some issues. Do you mind helping a bit? Thanks.
Steps I followed,

• I cloned repo and make it in the ros workspace
• I run rosrun natnet_ros client _server:=192.168.0.100 Where I my PC with ROS master is connected to the network with the wifi of the same router
• I get this output [INFO] [1651068734.595030]: Connecting to 192.168.0.100

But it never gets connected to the server.

My configuration in the Motive app is as follows.

• Broadcast Frame Data : On
• Local Interface : 192.168.0.100
• Labeled Markers : On
• Unlabeled Markers : On
• Asset Markers : On
• Rigid Bodies : On
• Up Axis : Z Up
• Remote Trigger : Off
• Transmission Type : Multicast

In the advanced settings its the same as default.

Let me know if you need any other inputs.
Thanks!

[aarsht7]

Anyway I found it. It was windows firewall. Stupid thing 😓