You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
MC may need know the information about the AGV mechanism in the "state" topic, such as the lifting mechanism of a lift vehicle, the fork of a forklift truck, or any other movable mechanism of the AGV,I notice the "load" field, but I think it doesn't feel right,it more likely to describe the information about the load.
What i need may be like this:
we prefer the second option,maybe the parameter names need to be changed a bit, but that's about it,this allows us to reduce customization,and we think it's best if the protocol has some defaults for common vehicles
MC may need know the information about the AGV mechanism in the "state" topic, such as the lifting mechanism of a lift vehicle, the fork of a forklift truck, or any other movable mechanism of the AGV,I notice the "load" field, but I think it doesn't feel right,it more likely to describe the information about the load.
What i need may be like this:
The physicalStates should be able to extend.
What's next step for vda5050?Will the vda5050 have some standard device attributes built in?
The text was updated successfully, but these errors were encountered: