Message containing the accumulated distance travelled by a wheel located at an odometry reference point defined by the user. The offset for the odometry reference point and the definition and origin of the user frame are defined through the device settings interface. The source of this message is identified by the source field, which is an integer ranging from 0 to 255. The timestamp associated with this message should represent the time when the accumulated tick count reached the value given by the contents of this message as accurately as possible. If using "local CPU time" time tags, the receiving end will also expect either `MSG_GNSS_TIME_OFFSET` or `MSG_PPS_TIME` to sync incoming wheeltick data to GNSS time., Local CPU time shall roll over to zero after one week.
{
"copyright": [
"Copyright (C) 2019-2021 Swift Navigation Inc.",
"Contact: https://support.swiftnav.com",
"",
"This source is subject to the license found in the file 'LICENSE' which must",
"be distributed together with this source. All other rights reserved.",
"",
"THIS CODE AND INFORMATION IS PROVIDED 'AS IS' WITHOUT WARRANTY OF ANY KIND,",
"EITHER EXPRESSED OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE IMPLIED",
"WARRANTIES OF MERCHANTABILITY AND/OR FITNESS FOR A PARTICULAR PURPOSE."
],
"$schema": "http://json-schema.org/draft-06/schema#",
"$id": "#MsgWheeltick",
"title":"MsgWheeltick",
"description":"Message containing the accumulated distance travelled by a wheel located at an odometry reference point defined by the user. The offset for the odometry reference point and the definition and origin of the user frame are defined through the device settings interface. The source of this message is identified by the source field, which is an integer ranging from 0 to 255. The timestamp associated with this message should represent the time when the accumulated tick count reached the value given by the contents of this message as accurately as possible. If using \"local CPU time\" time tags, the receiving end will also expect either `MSG_GNSS_TIME_OFFSET` or `MSG_PPS_TIME` to sync incoming wheeltick data to GNSS time.,\nLocal CPU time shall roll over to zero after one week.\n",
"type": "object",
"properties": {
"time": {"type": "integer"},
"flags": {"type": "integer"},
"source": {"type": "integer"},
"ticks": {"type": "integer"}
},
"required": [
"time",
"flags",
"source",
"ticks"
]
}