Lines Matching refs:from

25   // Explicitly prevents 0 from being used as a valid message type.
26   // Doing so protects from obscure bugs caused by default-initialized values.
29   // Detector configuration related message start from 100.
49   // Position Detection related message start from 200.
57   // Explicitly prevents 0 from being used as a valid notification type.
58   // Doing so protects from obscure bugs caused by default-initialized values.
67   // Notification of request update from the carried position detector.
70   // Notification of force update from the carried position detector.
85   // Explicitly prevents 0 from being used as a valid carried position type.
86   // Doing so protects from obscure bugs caused by default-initialized values.
110   // Explicitly prevents 0 from being used as a valid type.
111   // Doing so protects from obscure bugs caused by default-initialized values.
128     // transition from the in motion state to the stationary state.