Closed kanbouchou closed 3 months ago
@kanbouchou Isn't that what ElectricMotorActuatorInfo::model_type
is for?
@kanbouchou Isn't that what
ElectricMotorActuatorInfo::model_type
is for?
nm, i see the comment for robotControllerAxisProductCode
. In that case, i would add a little more to the comment to robotControllerAxisManufacturerCode
to explain why it is different from product code.
Thanks,
@kanbouchou Isn't that what
ElectricMotorActuatorInfo::model_type
is for?nm, i see the comment for
robotControllerAxisProductCode
. In that case, i would add a little more to the comment torobotControllerAxisManufacturerCode
to explain why it is different from product code. Thanks,
I've added a bit more comment. Basically, product code by itself is not guaranteed to be globally unique because different manufacturers can happen to have same product code. That's why we need manufacturer code in addition to product code to handle devices from different manufacturers by a single device driver.
thanks~
Overview
robotControllerAxisManufacturerCode
to joint class to support servos from different manufacturers in a daisy chain._vmimic
indefinitely growing inPyJointInfo::_Update
Detail
robotControllerAxisProductCode
field in joint class already, and we could encode manufacturer name in there as well, but need to introduce a rule (separator) which I wanted to avoid. Also,AttachedSensorInfo
has_sensorMaker
so using same pattern here as well.