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
Recently I used the Ublox and pyUblox to get the time markers.
The Trigger pulse I used was 3 pulse/second. I also publish the tim_tm2 msg as ROS message /Timtm2
However, the problem was that the /Timtm2 was lost every 3 seconds. I also write the Timtm2 information into *.dat file, it seems that the published timtm2 and *.dat file timtm2 were lost.
--------------------------------------The problem above was figured out-------------------------------------
I found that my timtm2 message had some problem shown below:
I do not know how to solve the problem of timtm2 with flags to be 77? Do you think is it the problem from hardware itself?
Thx and I am looking forward to your reply!
Do you know what is the problem of this issue? Thx
The text was updated successfully, but these errors were encountered:
Dear sir/madam:
Recently I used the Ublox and pyUblox to get the time markers.
The Trigger pulse I used was 3 pulse/second. I also publish the tim_tm2 msg as ROS message /Timtm2
However, the problem was that the /Timtm2 was lost every 3 seconds. I also write the Timtm2 information into *.dat file, it seems that the published timtm2 and *.dat file timtm2 were lost.
--------------------------------------The problem above was figured out-------------------------------------
I found that my timtm2 message had some problem shown below:
I do not know how to solve the problem of timtm2 with flags to be 77? Do you think is it the problem from hardware itself?
Thx and I am looking forward to your reply!
Do you know what is the problem of this issue? Thx
The text was updated successfully, but these errors were encountered: