The MultiModelTracker contains multiple ModelTrackers - one for each anchor. The ModelTracker can be adressed by the name of their corresponding anchor. This way, one can send a command to a specific ModelTracker (see anchorCommand
). Therefore it is useful to also have a look at the Model Tracker Command Reference. Some commands are implemented in the MultiModelTracker and propagate the command to all anchors. For additional details to MultiModelTracking have a look at Multi Model Tracking (Beta).
The following commands can be executed, if a tracking configuration with a MultiModelTracker pipeline is loaded:
CommandName | Parameter | Result |
---|---|---|
addAnchor | {
"name": string
?"models": array
?"workSpaceDefinitionURI": string
?"workSpaceDefinition": object
?"parameters": {}
}
| None |
The | ||
enableAnchor | {
"anchorName": string
}
| None |
The | ||
disableAnchor | {
"anchorName": string
}
| None |
The | ||
anchorCommand | {
"anchorName": string,
"content": ModelTrackerCommand
}
| CommandResult |
The | ||
setAttributeSeparately | {
"name": string,
"values": AnchorValuePair[]
}
| None |
The {
"anchor": string,
"value": string
}
| ||
getAttributeSeparately | {
"att": string
}
| AnchorValuePair[]
|
The | ||
resetHard | None | None |
The | ||
resetSoft | None | None |
The | ||
setInitPose | ExtrinsicData
| None |
The setInitPose command sets the init pose in all anchors. For details see Model Tracker Command Reference. |
All JsonAndBinary commands of the ModelTracker can also be executed for a specific node. This is done via the anchorCommand
:
CommandName | Parameter | BinaryData | Result |
---|---|---|---|
anchorCommand | {
"anchorName": string,
"content": ModelTrackerCommand
}
| CommandBinaryData | CommandResult |
The addModelData command propagates a ModelTracker jsonAndBinary command to the node specified by the anchorName . The binary data has to be the same as required by the jsonAndBinary command. It also returns the same result. See also Model Tracker Command Reference |