You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am currently facing a problem with my feedback control system: the feedback sensor data is obtained through subscribing to topics and is assigned to the hardware interface. When I launch the control, there is a slight delay between the actual control computation start and the sensor timestamp (the control frequency is 500 Hz, which means the control computation may start 0-2ms later than the sensor timestamp). Here is the topic timestamp and control start timestamp.
Have you ever encountered a similar problem? If so, how did you solve it? Looking forward to your reply!
The text was updated successfully, but these errors were encountered:
Can you give more details about the signal paths? You have written a custom hardware component, which is subscribing to topics and publishing them again?
Thank you for your reply. Indeed, I assigned values to the hardware component by subscribing to the motors information. These signals are for displaying the information of the three groups of sensors I subscribed to and the timestamp at the start of control (the blue straight line). I can't specify that the control starts to be executed immediately after the three topics are actually received, it is executed after an uncertain period of delay.
I am currently facing a problem with my feedback control system: the feedback sensor data is obtained through subscribing to topics and is assigned to the hardware interface. When I launch the control, there is a slight delay between the actual control computation start and the sensor timestamp (the control frequency is 500 Hz, which means the control computation may start 0-2ms later than the sensor timestamp). Here is the topic timestamp and control start timestamp.
Have you ever encountered a similar problem? If so, how did you solve it? Looking forward to your reply!
The text was updated successfully, but these errors were encountered: