Abstract: Techniques for engaging and disengaging a vehicle from an autonomous operation mode are described. The techniques include receiving a request to engage or disengage the autonomous mode at a teleoperations system. The request is validated at the teleoperations system using a first set of conditions describing trust in the request and validity of the request. The request is then sent, if valid, to the vehicle where a second validation is performed using a second set of conditions describing the conditions or states of the vehicle. If the second conditions are valid then the request is performed and the vehicle engages or disengages from autonomous mode.

Abstract: Techniques for engaging and disengaging a vehicle from an autonomous operation mode are described. The techniques include receiving a request to engage or disengage the autonomous mode at a teleoperations system. The request is validated at the teleoperations system using a first set of conditions describing trust in the request and validity of the request. The request is then sent, if valid, to the vehicle where a second validation is performed using a second set of conditions describing the conditions or states of the vehicle. If the second conditions are valid then the request is performed and the vehicle engages or disengages from autonomous mode.

Abstract: One variation of a method includes, during a first time period: detecting a direction of motion of a trailer; detecting a first force applied to a kingpin; detecting an incline angle of the trailer; calculating a first target preload force opposite the direction of motion and inversely proportional to the incline angle; and in response to the first force falling below the first target preload force, triggering a motor to increase torque output opposite the direction of motion. The method further includes, during a second time period: detecting a second force applied to the kingpin; detecting a decline angle of the trailer; calculating a second target preload force opposite the direction of motion and inversely proportional to the decline angle; and in response to the second force falling below the second target preload force, triggering the motor to increase torque output opposite the direction of motion.

Abstract: One variation of a method includes, during a first time period: detecting a direction of motion of a trailer; detecting a first force applied to a kingpin; detecting an incline angle of the trailer; calculating a first target preload force opposite the direction of motion and inversely proportional to the incline angle; and in response to the first force falling below the first target preload force, triggering a motor to increase torque output opposite the direction of motion. The method further includes, during a second time period: detecting a second force applied to the kingpin; detecting a decline angle of the trailer; calculating a second target preload force opposite the direction of motion and inversely proportional to the decline angle; and in response to the second force falling below the second target preload force, triggering the motor to increase torque output opposite the direction of motion.

Abstract: One variation of a system includes a bogie including: a chassis; a first set of latches configured to transiently engage a first subset of engagement features, in a first array of engagement features on a left rail and in a second array of engagement features on a right rail of the trailer, to retain the bogie below a floor of the trailer; a driven axle suspended from the chassis; and a motor coupled to the driven axle and configured to output torque to the driven axle and regeneratively brake the driven axle. The system further includes a battery assembly: including a second set of latches configured to transiently engage a second subset of engagement features, in the first array of engagement features and in the second array of engagement features, to retain the battery assembly adjacent the bogie; and configured to receive electrical energy from the motor.

Abstract: One variation of a system for power distribution of a trailer includes: a trailer chassis; a driven axle suspended from the trailer chassis; and a motor coupled to the driven axle. The system further includes a battery assembly coupled to the trailer chassis and configured to supply electrical energy to the motor to drive the driven axle and source electrical energy from the motor to slow motion of the driven axle. The system also includes a charging panel coupled to the trailer chassis and configured to couple to an external charging element. The system further includes a panel actuator configured to advance the charging panel from the trailer chassis to an open position to form a target gap between the external charging element and the charging panel and to retract the charging panel to a closed position to decouple the charging panel from the external charging element.

Abstract: One variation of a system includes a kingpin including: a head; a base coupled to a proximal end of the trailer; a shank interposed between the head and the base; a first sensor configured to output signals representing lateral forces applied to the kingpin; and a second sensor configured to output signals representing longitudinal forces applied to the kingpin. The system further includes a controller configured to: access a first signal from the first sensor representing a lateral force applied to the kingpin; access a second signal from the second sensor representing a longitudinal force applied to the kingpin; calculate a direction and a magnitude of a force applied to the kingpin based on the first and second signals; and trigger a motor arranged on a distal end of the trailer to output a torque in the direction of the force and proportional to the magnitude of the force.

Abstract: One variation of a system includes a kingpin: arranged on a proximal end of the trailer; includes a sensor configured to output a signal representing lateral forces and longitudinal forces applied to the kingpin; and configured to couple to a tow vehicle. The system further includes an interface including a joystick and a kingpin interface configured to transfer forces, applied to the joystick, into the kingpin. The system also includes a controller configured to: access the signal from the sensor; based on the signal, calculate a magnitude of a force applied to the kingpin; calculate a first target speed of a first wheel of the trailer proportional to the magnitude; calculate a second target speed of a second wheel of the trailer proportional to the magnitude; and serve the first target speed and the second target speed to a drive system arranged on a distal end of the trailer.

Abstract: The present disclosure is directed to performing one or more validity checks on potential trajectories for a device, such as an autonomous vehicle, to navigate. In some examples, a potential trajectory may be validated based on whether it is consistent with a current trajectory the vehicle is navigating such that the potential and current trajectories are not too different, whether the vehicle can feasibly or kinematically navigate to the potential trajectory from a current state, whether the potential trajectory was punctual or received within a time period of a prior trajectory, and/or whether the potential trajectory passes a staleness check, such that it was created within a certain time period. In some examples, determining whether a potential trajectory is feasibly may include updating a set of feasibility limits based on one or more operational characteristics of statuses of subsystems of the vehicle.

Abstract: Techniques for determining whether to limit an operation of a vehicle while operating in a manually assisted mode of operation are described herein. A vehicle computing system can monitor components of the vehicle and identify a fault associated with a component. The vehicle computing system can determine whether the fault is associated with a manual operation of the vehicle. Based on a determination that the fault is not associated with the manual operation of the vehicle (e.g., fault associated with an autonomous control component), the vehicle computing system can override the fault and enable continued operation of the vehicle in the manually assisted mode of operation. Based on a determination that the fault is associated with the manual operation of the vehicle, the vehicle computing system can cause the vehicle to cease operating.

Abstract: Techniques for identifying a constraint to apply to an operation of a vehicle are described herein. A vehicle computing system receives diagnostics and constraints associated with components of the vehicle. The vehicle computing system identifies constraints to apply to vehicular operation based on the received diagnostics and constraints. The vehicle computing system may determine whether a received constraint is valid, based on associated diagnostics. Based on a determination that the constraint is valid, the vehicle computing system may include the constraint in vehicle control considerations. Based on a determination that the constraint is invalid, the vehicle computing system may withhold the constraint from vehicle control considerations.

Abstract: Testing autonomous vehicle control systems in the real world can be difficult, because creating and re-creating physical scenarios for repeated testing may be impractical. In some implementations, detailed map data and data acquired through driving in a region can be used to identify similar segments of a drivable surface. Simulation scenarios used to test one of the similar segments may be used to test other of the similar segments. The driving data may also be used to generate and/or validate the simulation scenarios, e.g., by re-creating scenarios encountered while driving in a first segment in a simulation scenario for use in the second segment and comparing simulated driving behavior with the driving data.

Abstract: Performance anomalies in autonomous vehicle can be difficult to identify, and the impact of such anomalies on systems within the autonomous vehicle may be difficult to understand. In examples, systems of the autonomous vehicle are modeled as nodes in a probabilistic graphical network. Probabilities of data generated at each of the nodes is determined. The probabilities are used to determine capabilities associated with higher level functions of the autonomous vehicle.

Abstract: A vehicle may include a primary system for generating data to control the vehicle and a secondary system that validates the data and/or other data to avoid collisions. For example, the primary system may localize the vehicle, detect an object around the vehicle, predict an object trajectory, and generate a trajectory for the vehicle. The secondary system may localize the vehicle, detect an object around the vehicle, predict an object trajectory, and determine a likelihood of a collision of the vehicle with the object. A simulation system may generate simulation scenarios that test aspects of the primary system and the secondary system. Simulation scenarios may include simulated vehicle control data that causes the primary system to generate a driving trajectory and simulated object data that causes the secondary system to determine a collision.

Abstract: The described techniques relate to coordinating and managing faults of systems of a vehicle, such as an autonomous vehicle, to enable the vehicle to respond safely and appropriately to the faults. In examples, a centralized fault monitor system receives faults from different vehicle systems, maps the received faults to associated fault constraints, prioritizes different and shared parameters between the fault constraints, and communicates the constraint parameters to appropriate vehicle systems accordingly.

Abstract: Performance anomalies in autonomous vehicle can be difficult to identify, and the impact of such anomalies on systems within the autonomous vehicle may be difficult to understand. In examples, systems of the autonomous vehicle are modeled as nodes in a probabilistic graphical network. Probabilities of data generated at each of the nodes is determined. The probabilities are used to determine capabilities associated with higher level functions of the autonomous vehicle.

Abstract: Systems and methods are described for performing one or more validity checks on potential trajectories for a device, such as an autonomous vehicle, to navigate. In some examples, a potential trajectory may be validated based on whether it is consistent with a current trajectory the vehicle is navigating such that the potential and current trajectories are not too different, whether the vehicle can feasibly or kinematically navigate to the potential trajectory from a current state, whether the potential trajectory was punctual or received within a time period of a prior trajectory, and/or whether the potential trajectory passes a staleness check, such that it was created within a certain time period. In some examples, determining whether a potential trajectory is feasibly may include updating a set of feasibility limits based on one or more operational characteristics of statuses of subsystems of the vehicle.

Abstract: The present disclosure is directed to performing one or more validity checks on potential trajectories for a device, such as an autonomous vehicle, to navigate. In some examples, a potential trajectory may be validated based on whether it is consistent with a current trajectory the vehicle is navigating such that the potential and current trajectories are not too different, whether the vehicle can feasibly or kinematically navigate to the potential trajectory from a current state, whether the potential trajectory was punctual or received within a time period of a prior trajectory, and/or whether the potential trajectory passes a staleness check, such that it was created within a certain time period. In some examples, determining whether a potential trajectory is feasibly may include updating a set of feasibility limits based on one or more operational characteristics of statuses of subsystems of the vehicle.

Abstract: The present disclosure is directed to performing one or more validity checks on potential trajectories for a device, such as an autonomous vehicle, to navigate. In some examples, a potential trajectory may be validated based on whether it is consistent with a current trajectory the vehicle is navigating such that the potential and current trajectories are not too different, whether the vehicle can feasibly or kinematically navigate to the potential trajectory from a current state, whether the potential trajectory was punctual or received within a time period of a prior trajectory, and/or whether the potential trajectory passes a staleness check, such that it was created within a certain time period. In some examples, determining whether a potential trajectory is feasibly may include updating a set of feasibility limits based on one or more operational characteristics of statuses of subsystems of the vehicle.

Abstract: A method and apparatus for selecting among a plurality of trajectories comprises receiving at least a first and second trajectory, each having an associated level in a trajectory hierarchy, determining whether the first trajectory is viable, determining a present level limit for trajectory selection, and if the first trajectory is viable and its level does not exceed the present level limit, executing the first trajectory. If the first trajectory is not viable or the associated level of the first trajectory exceeds the present level limit, the second trajectory is executed if it is viable and its associated level does not exceed the present level limit. A state variable is set such that when a trajectory lower in a trajectory hierarchy is executed, a trajectory selector waits for a message from a monitor or an operator before returning to the use of higher level trajectories.