Harsh Deshpande

Sorry for the delay. I will take a look at it today and get back.

@sarguez the main problem here seems to be that the IP address is wrong. Have you made sure the IP address is correctly set in the YAML file? And secondly,...

I am not sure how will re-connection help in this case. Re-connection was meant for cases where the device is unplugged (device is still on) or the device is powered...

https://github.com/PepperlFuchs/ROS_driver/pull/36#issuecomment-736545604

Though time offset is an issue, but the solution is not acceptable. It does not make sense to add a user-defined time offset.

Yes I have seen that and realized that was the basis of this PR. But does not necessarily mean it is a good solution. Also ROS time is completely different...

I might be wrong. The [REP](https://www.ros.org/reps/rep-0138.html) does mention `calibrate_time` and `time_offset`.

Synchronized time or any other time sent by the device is completely different from ROS time. If you want to access the device's timestamp for any reason, I am publishing...

Is it addressed in https://github.com/PepperlFuchs/ROS_driver/pull/26?

You are right. Thanks for pointing out.