While looking at the documentation it mentions that after the identification and before the data fields there is a timestamp in the XCP message frame.
Is there a method inside the master that could achieve this? Or would we have to retrieve the raw data to access this value? This would be for DAQ and polling
I noticed that in the base transport layer, there is a timestamp, but is this the same one that I am referring to?
Well, there's a more or less confusing hierarchy of timestamps:
timestamps as depicted above only apply to DAQ/STIM packets and are generated by your ECU or simulator; extraction is currently left to the user (maybe there will be an API).
pyxcp generates its own timestamps on every frame received, accessible to the user.
But the story continues, hardware interfaces may also generate timestamps (these clock-sources are currently NOT provided by pyxcp), for example
While looking at the documentation it mentions that after the identification and before the data fields there is a timestamp in the XCP message frame.
Is there a method inside the master that could achieve this? Or would we have to retrieve the raw data to access this value? This would be for DAQ and polling
I noticed that in the base transport layer, there is a timestamp, but is this the same one that I am referring to?