abb_libegm: EgmClock message does not represent UNIX time
The definition of EgmClock in proto/egm.proto is
message EgmClock // Time in seconds and microseconds since 1 Jan 1970
{
required uint64 sec = 1;
required uint64 usec = 2;
}
Below are headers of EGM messages sent from RobotStudio on my system:
header {
seqno: 352216
tm: 28397221
mtype: MSGTYPE_DATA
}
feedBack {
joints {
joints: 0.00025089801056310534
joints: -0.010418600402772427
joints: 0.03861050307750702
joints: -0.0001342049945378676
joints: 45.01199722290039
joints: -0.0667094737291336
}
cartesian {
pos {
x: 1216.9378662109375
y: 0.0046911695972085
z: 1187.1817626953125
}
orient {
u0: 0.3823593258857727
u1: -0.0005403859540820122
u2: 0.9240135550498962
u3: -0.00022283525322563946
}
euler {
x: -179.93319209849528
y: 44.95977143802771
z: -179.90533858705996
}
}
time {
sec: 28397
usec: 216500
}
}
...
The time data sec: 28397 does not look like “time in seconds and microseconds since 1 Jan 1970”.
About this issue
- Original URL
- State: closed
- Created 6 years ago
- Comments: 27 (15 by maintainers)
The issue seems to be fixed in RobotStudio 21.2.9526.0 – the timestamps look like UNIX time now.
So just to be clear: this repository is not where ABB maintains its EGM implementation.
This is an OSS library which implements an interface to EGM running on an ABB (robot) controller.
Issues with EGM itself – as it seems yours is – should be either reported to your local ABB branch office (which will then escalate them if/when appropriate) or posted on one of the official ABB fora.
From your description, I don’t have the impression the issue you are reporting is specific to this library.
If you agree, please close the issue.
If you post on the RobotStudio forum fi, it would be appreciated if you could post a final comment here with a link to your post there, so we can keep things connected.