rosrun rosserial_python serial_node.py incorrect time.

edit

Hi all.

I've recently deployed ::ROS noetic to my Ubuntu 20.04 VMWare installation and I'm noticing an issue with the timestamp. When I run the following command:

rosrun rosserial_python serial_node.py _port:=/dev/ttyACM0

I get the following:

[INFO] [1616078565.714165, 0.000000]: ROS Serial Python Node
[INFO] [1616078565.718151, 0.000000]: Connecting to /dev/ttyACM0 at 115200 baud

The time I receive from my embedded device shows:

data: 
  secs: 1616078001
  nsecs: 235177963
---
data: 
  secs: 1616078001
  nsecs: 236177963

I'm a beginner to the ::ROS ecosystem so this issue maybe be something silly. Now, as I'm deploying the roserial API to my embedded plaform, is there sometime I'm missing on this side (such as a publishing a dedicating topic for clock syncing?). I don't think is the case, as the very first request sent to my embedded platform does indeed show the seconds is incorrect. Scratching my head a little.

I don't this is to do with running the ::ROS framework within a VM either.

Thanks

Thank