+ cwrubaja
+ cwrubaja.fuelgauge
+ cwrubaja.fuelgauge.Fuelstate (v0.1) [extent 15.0 bytes] [max length 19.0 bytes]
+ uavcan.time.SynchronizedTimestamp (v1.0) timestamp [extent 7.0 bytes] [max length 7.0 bytes]
Nested data type used for representing a network-wide synchronized timestamp with microsecond resolution. This data type is highly recommended for use both in standard and vendor-specific messages alike.
truncated uint56 microsecond
The number of microseconds that have passed since some arbitrary moment in the past.
The moment of origin (i.e., the time base) is defined per-application. The current time base in use
can be requested from the time synchronization master, see the corresponding service definition.
This value is to never overflow. The value is 56-bit wide because:
- 2^56 microseconds is about 2285 years, which is plenty. A 64-bit microsecond counter would be
unnecessarily wide and its overflow interval of 585 thousand years induces a mild existential crisis.
- Classic-CAN (not FD) transports carry up to 7 bytes of payload per frame.
Time sync messages shall use single-frame transfers, which means that the value can't be wider than 56 bits.
saturated uint56 UNKNOWN = 0
Zero means that the time is not known.
+ uavcan.primitive.scalar.Real32 (v1.0) percent [extent 4.0 bytes] [max length 4.0 bytes]
saturated float32 value
Exactly representable integers: [-16777216, +16777216]
+ cwrubaja.fuelgauge.Fuelvolume (v0.1) [extent 23.0 bytes] [max length 27.0 bytes]
+ uavcan.time.SynchronizedTimestamp (v1.0) timestamp [extent 7.0 bytes] [max length 7.0 bytes]
Nested data type used for representing a network-wide synchronized timestamp with microsecond resolution. This data type is highly recommended for use both in standard and vendor-specific messages alike.
truncated uint56 microsecond
The number of microseconds that have passed since some arbitrary moment in the past.
The moment of origin (i.e., the time base) is defined per-application. The current time base in use
can be requested from the time synchronization master, see the corresponding service definition.
This value is to never overflow. The value is 56-bit wide because:
- 2^56 microseconds is about 2285 years, which is plenty. A 64-bit microsecond counter would be
unnecessarily wide and its overflow interval of 585 thousand years induces a mild existential crisis.
- Classic-CAN (not FD) transports carry up to 7 bytes of payload per frame.
Time sync messages shall use single-frame transfers, which means that the value can't be wider than 56 bits.
saturated uint56 UNKNOWN = 0
Zero means that the time is not known.
+ uavcan.si.unit.volume.Scalar (v1.0) volume [extent 4.0 bytes] [max length 4.0 bytes]
saturated float32 cubic_meter
+ cwrubaja.hallmonitorunit
+ cwrubaja.hallmonitorunit.Rpm (v1.0) [extent 11.0 bytes] [max length 11.0 bytes]
Rotations per minuite. we can stop messing up conversions now
+ uavcan.time.SynchronizedTimestamp (v1.0) timestamp [extent 7.0 bytes] [max length 7.0 bytes]
Nested data type used for representing a network-wide synchronized timestamp with microsecond resolution. This data type is highly recommended for use both in standard and vendor-specific messages alike.
truncated uint56 microsecond
The number of microseconds that have passed since some arbitrary moment in the past.
The moment of origin (i.e., the time base) is defined per-application. The current time base in use
can be requested from the time synchronization master, see the corresponding service definition.
This value is to never overflow. The value is 56-bit wide because:
- 2^56 microseconds is about 2285 years, which is plenty. A 64-bit microsecond counter would be
unnecessarily wide and its overflow interval of 585 thousand years induces a mild existential crisis.
- Classic-CAN (not FD) transports carry up to 7 bytes of payload per frame.
Time sync messages shall use single-frame transfers, which means that the value can't be wider than 56 bits.
saturated uint56 UNKNOWN = 0
Zero means that the time is not known.
saturated float32 rpm
+ cwrubaja.hallmonitorunit.Status (v0.1) [extent 39.0 bytes] [max length 39.0 bytes]
A Status message from HMU
+ uavcan.time.SynchronizedTimestamp (v1.0) timestamp [extent 7.0 bytes] [max length 7.0 bytes]
Nested data type used for representing a network-wide synchronized timestamp with microsecond resolution. This data type is highly recommended for use both in standard and vendor-specific messages alike.
truncated uint56 microsecond
The number of microseconds that have passed since some arbitrary moment in the past.
The moment of origin (i.e., the time base) is defined per-application. The current time base in use
can be requested from the time synchronization master, see the corresponding service definition.
This value is to never overflow. The value is 56-bit wide because:
- 2^56 microseconds is about 2285 years, which is plenty. A 64-bit microsecond counter would be
unnecessarily wide and its overflow interval of 585 thousand years induces a mild existential crisis.
- Classic-CAN (not FD) transports carry up to 7 bytes of payload per frame.
Time sync messages shall use single-frame transfers, which means that the value can't be wider than 56 bits.
saturated uint56 UNKNOWN = 0
Zero means that the time is not known.
+ saturated float32[4] rpm [max length 16.0 bytes]
saturated float32
+ uavcan.si.unit.voltage.Scalar.1.0[4] voltage [max length 16.0 bytes]
+ uavcan.si.unit.voltage.Scalar (v1.0) [extent 4.0 bytes] [max length 4.0 bytes]
saturated float32 volt
+ cwrubaja.hierarchy
+ cwrubaja.hierarchy.Level (v0.1) [extent 1.0 bytes] [max length 1.0 bytes]
Basic datatype that details what algorithmic level the request/message is at
saturated uint4 value
+ cwrubaja.hmi
+ cwrubaja.hmi.notasteeringwheel
+ cwrubaja.hmi.notasteeringwheel.State (v0.1) [extent 16.0 bytes] [max length 16.0 bytes]
+ uavcan.time.SynchronizedTimestamp (v1.0) timestamp [extent 7.0 bytes] [max length 7.0 bytes]
Nested data type used for representing a network-wide synchronized timestamp with microsecond resolution. This data type is highly recommended for use both in standard and vendor-specific messages alike.
truncated uint56 microsecond
The number of microseconds that have passed since some arbitrary moment in the past.
The moment of origin (i.e., the time base) is defined per-application. The current time base in use
can be requested from the time synchronization master, see the corresponding service definition.
This value is to never overflow. The value is 56-bit wide because:
- 2^56 microseconds is about 2285 years, which is plenty. A 64-bit microsecond counter would be
unnecessarily wide and its overflow interval of 585 thousand years induces a mild existential crisis.
- Classic-CAN (not FD) transports carry up to 7 bytes of payload per frame.
Time sync messages shall use single-frame transfers, which means that the value can't be wider than 56 bits.
saturated uint56 UNKNOWN = 0
Zero means that the time is not known.
saturated uint16 rotary0
saturated uint16 rotary1
saturated float32 potentiometer
saturated bool toggle
+ cwrubaja.hmi.steeringwheel
+ cwrubaja.hmi.steeringwheel.Knobs (v0.1) [extent 4.0 bytes] [max length 4.0 bytes]
saturated uint16 left
saturated uint16 right
+ cwrubaja.hmi.steeringwheel.State (v0.1) [extent 8.0 bytes] [max length 8.0 bytes]
+ uavcan.time.SynchronizedTimestamp (v1.0) timestamp [extent 7.0 bytes] [max length 7.0 bytes]
Nested data type used for representing a network-wide synchronized timestamp with microsecond resolution. This data type is highly recommended for use both in standard and vendor-specific messages alike.
truncated uint56 microsecond
The number of microseconds that have passed since some arbitrary moment in the past.
The moment of origin (i.e., the time base) is defined per-application. The current time base in use
can be requested from the time synchronization master, see the corresponding service definition.
This value is to never overflow. The value is 56-bit wide because:
- 2^56 microseconds is about 2285 years, which is plenty. A 64-bit microsecond counter would be
unnecessarily wide and its overflow interval of 585 thousand years induces a mild existential crisis.
- Classic-CAN (not FD) transports carry up to 7 bytes of payload per frame.
Time sync messages shall use single-frame transfers, which means that the value can't be wider than 56 bits.
saturated uint56 UNKNOWN = 0
Zero means that the time is not known.
saturated uint8 value
saturated uint8 NORMAL = 0
saturated uint8 RUH_ROH = 1
saturated uint8 MANUAL = 2
saturated uint8 SEMI_ACTIVE = 3
+ cwrubaja.honeybee
+ cwrubaja.honeybee.Angle (v0.1) [extent 11.0 bytes] [max length 11.0 bytes]
+ uavcan.time.SynchronizedTimestamp (v1.0) timestamp [extent 7.0 bytes] [max length 7.0 bytes]
Nested data type used for representing a network-wide synchronized timestamp with microsecond resolution. This data type is highly recommended for use both in standard and vendor-specific messages alike.
truncated uint56 microsecond
The number of microseconds that have passed since some arbitrary moment in the past.
The moment of origin (i.e., the time base) is defined per-application. The current time base in use
can be requested from the time synchronization master, see the corresponding service definition.
This value is to never overflow. The value is 56-bit wide because:
- 2^56 microseconds is about 2285 years, which is plenty. A 64-bit microsecond counter would be
unnecessarily wide and its overflow interval of 585 thousand years induces a mild existential crisis.
- Classic-CAN (not FD) transports carry up to 7 bytes of payload per frame.
Time sync messages shall use single-frame transfers, which means that the value can't be wider than 56 bits.
saturated uint56 UNKNOWN = 0
Zero means that the time is not known.
saturated float32 degree
+ cwrubaja.midi
+ cwrubaja.midi.Note (v0.1) [extent 3.0 bytes] [max length 3.0 bytes]
saturated bool on
saturated uint8 note
saturated uint8 velocity
+ cwrubaja.navigation
+ cwrubaja.physics
+ cwrubaja.physics.Color (v0.1) [extent 3.0 bytes] [max length 3.0 bytes]
type that encapsulates a 24-bit RGB color
saturated uint8 r
saturated uint8 g
saturated uint8 b
saturated uint8 MAX_RED = 255
saturated uint8 MAX_GREEN = 255
saturated uint8 MAX_BLUE = 255
+ cwrubaja.servocontroller
+ cwrubaja.servocontroller.Manual (v1.0) [extent 8.0 bytes] [max length 8.0 bytes]
Servo Controller Manual Driving datatype Mostly used for debug/exploration of servo & controller behavior Think of it as teleoperation for the entire board (e.g. connect a joystick to Yakut and have control of all actuator axes)
saturated bool pwmEnable
saturated uint32 pwmMicrosecond
saturated bool buckEnable
+ cwrubaja.physics.Color (v0.1) neopixelColor [extent 3.0 bytes] [max length 3.0 bytes]
type that encapsulates a 24-bit RGB color
saturated uint8 r
saturated uint8 g
saturated uint8 b
saturated uint8 MAX_RED = 255
saturated uint8 MAX_GREEN = 255
saturated uint8 MAX_BLUE = 255
+ cwrubaja.servocontroller.State (v0.1) [extent 19.0 bytes] [max length 23.0 bytes]
Servo Controller State datatype Encapsulates the current status of Servo Controller
+ uavcan.time.SynchronizedTimestamp (v1.0) timestamp [extent 7.0 bytes] [max length 7.0 bytes]
Nested data type used for representing a network-wide synchronized timestamp with microsecond resolution. This data type is highly recommended for use both in standard and vendor-specific messages alike.
truncated uint56 microsecond
The number of microseconds that have passed since some arbitrary moment in the past.
The moment of origin (i.e., the time base) is defined per-application. The current time base in use
can be requested from the time synchronization master, see the corresponding service definition.
This value is to never overflow. The value is 56-bit wide because:
- 2^56 microseconds is about 2285 years, which is plenty. A 64-bit microsecond counter would be
unnecessarily wide and its overflow interval of 585 thousand years induces a mild existential crisis.
- Classic-CAN (not FD) transports carry up to 7 bytes of payload per frame.
Time sync messages shall use single-frame transfers, which means that the value can't be wider than 56 bits.
saturated uint56 UNKNOWN = 0
Zero means that the time is not known.
+ uavcan.si.unit.electric_current.Scalar (v1.0) servoCurrent [extent 4.0 bytes] [max length 4.0 bytes]
saturated float32 ampere
saturated bool engaged
saturated uint8 state
saturated uint8 ServoStartup = 1
saturated uint8 ServoDisengaged = 2
saturated uint8 ServoEngaged = 3
saturated uint8 ServoFault = 4
saturated uint8 ServoTrimEngagedMenu = 5
saturated uint8 ServoTrimDisengagedMenu = 6
saturated uint8 ServoLocateInit = 7
saturated uint8 ServoLocateOne = 8
saturated uint8 ServoLocateTwo = 9
saturated uint8 ServoLocateDecide = 10
saturated uint8 ServoAutoTrim = 11
+ cwrubaja.suspension
+ cwrubaja.suspension.vcm
+ cwrubaja.suspension.vcm.Setpoint (v0.2) [extent 7.0 bytes] [max length 11.0 bytes]
A specific Semi-Active Suspension valve setpoint.
saturated uint4 priority
+ uavcan.si.unit.electric_current.Scalar (v1.0) current [extent 4.0 bytes] [max length 4.0 bytes]
saturated float32 ampere
+ cwrubaja.suspension.vcm.Setpoint (v0.1) [extent 7.0 bytes] [max length 11.0 bytes]
A specific Semi-Active Suspension valve setpoint.
+ uavcan.si.unit.electric_current.Scalar (v1.0) current [extent 4.0 bytes] [max length 4.0 bytes]
saturated float32 ampere
+ cwrubaja.suspension.vcm.Status (v0.1) [extent 28.0 bytes] [max length 32.0 bytes]
A status message from VCM
+ uavcan.time.SynchronizedTimestamp (v1.0) timestamp [extent 7.0 bytes] [max length 7.0 bytes]
Nested data type used for representing a network-wide synchronized timestamp with microsecond resolution. This data type is highly recommended for use both in standard and vendor-specific messages alike.
truncated uint56 microsecond
The number of microseconds that have passed since some arbitrary moment in the past.
The moment of origin (i.e., the time base) is defined per-application. The current time base in use
can be requested from the time synchronization master, see the corresponding service definition.
This value is to never overflow. The value is 56-bit wide because:
- 2^56 microseconds is about 2285 years, which is plenty. A 64-bit microsecond counter would be
unnecessarily wide and its overflow interval of 585 thousand years induces a mild existential crisis.
- Classic-CAN (not FD) transports carry up to 7 bytes of payload per frame.
Time sync messages shall use single-frame transfers, which means that the value can't be wider than 56 bits.
saturated uint56 UNKNOWN = 0
Zero means that the time is not known.
+ uavcan.si.unit.temperature.Scalar (v1.0) valve [extent 4.0 bytes] [max length 4.0 bytes]
saturated float32 kelvin
+ uavcan.si.unit.temperature.Scalar (v1.0) module [extent 4.0 bytes] [max length 4.0 bytes]
saturated float32 kelvin
+ uavcan.si.unit.temperature.Scalar (v1.0) mcu [extent 4.0 bytes] [max length 4.0 bytes]
saturated float32 kelvin
+ uavcan.si.unit.electric_current.Scalar (v1.0) current [extent 4.0 bytes] [max length 4.0 bytes]
saturated float32 ampere
+ uavcan.si.unit.voltage.Scalar (v1.0) voltage [extent 4.0 bytes] [max length 4.0 bytes]
saturated float32 volt