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
when device decomposition happens, commands to the device assembly need to have an identifier to be sent to the correct device.
suggestion
since each subdevice needs a unique name anyway and this unique name is used in the config file (if I gather that correctly), the device name could also be used to generate the correct addressing information.
calling subdevice.component_info.name gives the name, which can be fed to the command which needs to be issued to the correct device.
alternative
alternatively, additionally to name, a identifier can be introduced into hardware device and used, if existing, to modify commands
The text was updated successfully, but these errors were encountered:
Problem
when device decomposition happens, commands to the device assembly need to have an identifier to be sent to the correct device.
suggestion
since each subdevice needs a unique name anyway and this unique name is used in the config file (if I gather that correctly), the device name could also be used to generate the correct addressing information.
calling subdevice.component_info.name gives the name, which can be fed to the command which needs to be issued to the correct device.
alternative
alternatively, additionally to name, a identifier can be introduced into hardware device and used, if existing, to modify commands
The text was updated successfully, but these errors were encountered: