Header/@creationTime is written with getCurrentTime(GMT), so it floors to a whole second:
|
addAttribute(writer, "creationTime", getCurrentTime(GMT)); |
deviceModelChangeTime, in the same Header element twenty lines later, uses GMT_UV_SEC:
|
addAttribute(writer, "deviceModelChangeTime", m_modelChangeTime); |
Asset timestamps and observations use it as well, which makes creationTime the coarsest timestamp in the document. I couldn't find a config option that reaches it.
Same in the JSON printer: json_printer.cpp#L67
It matters for clients using creationTime as a remote clock reading, where whole-second resolution caps the measurement at ±0.5 s.
Switching both call sites to GMT_UV_SEC needs no schema change.
Header/@creationTimeis written withgetCurrentTime(GMT), so it floors to a whole second:cppagent/src/mtconnect/printer/xml_printer.cpp
Line 541 in 7a15fbf
deviceModelChangeTime, in the sameHeaderelement twenty lines later, usesGMT_UV_SEC:cppagent/src/mtconnect/printer/xml_printer.cpp
Line 561 in 7a15fbf
Asset timestamps and observations use it as well, which makes
creationTimethe coarsest timestamp in the document. I couldn't find a config option that reaches it.Same in the JSON printer: json_printer.cpp#L67
It matters for clients using
creationTimeas a remote clock reading, where whole-second resolution caps the measurement at ±0.5 s.Switching both call sites to
GMT_UV_SECneeds no schema change.