CanFdBusScenario
Robotics scenarios · Implementation: mlsysim/engine/scenario_definitions/robotics/realtime.py.
Construct this scenario with keyword inputs. The fields below show the types and defaults declared by this class.
num_axes servo axes on one CAN FD bus, frames_per_axis frames each per cycle.
Notes
Equation: Result = mlsysim.solvers.CanFdBusModel.solve with the named scenario fields; no extra fitting or postprocessing is applied.
Assumptions: The supplied inputs use the units and validity regime documented by CanFdBusModel.solve; this class binds one reproducible configuration.
Excludes: Any behavior excluded by CanFdBusModel.solve, and measurement or calibration of the supplied inputs.
References
Implementation reference: mlsysim.solvers.CanFdBusModel.solve documents the composed equation and its sources.
Examples
The named registry scenario supplies the stated inputs; this is a modeled calculation, not a new measurement.
>>> from mlsysim import Scenarios
>>> scenario = Scenarios.WarehouseServoCanFdOneBus
>>> round((scenario.result.frame_time).to('μs').magnitude, 6)
56.6Attributes
| Name | Description |
|---|---|
| baud_arbitration | |
| baud_data | |
| cycle | |
| frames_per_axis | |
| num_axes | |
| payload_bytes | |
| result | Return mlsysim.solvers.CanFdBusModel.solve for this scenario; output fields retain the units and feasibility semantics specified by that solver. |
num_axes
Type: int.
Declared default: required.
payload_bytes
Type: int.
Declared default: required.
frames_per_axis
Type: int.
Declared default: required.
baud_arbitration
Type: Quantity.
Declared default: required.
baud_data
Type: Quantity.
Declared default: required.
cycle
Type: Quantity.
Declared default: required.
result
engine.scenario_types.CanFdBusScenario.result
Return mlsysim.solvers.CanFdBusModel.solve for this scenario; output fields retain the units and feasibility semantics specified by that solver.
Equation: mlsysim.solvers.CanFdBusModel.solve (scenario fields).