Expectation is the the ut-control module, will have multiple devices that it supports, and that the rack configuration will be setup to define the devices per module that are controllable.
Messages sent to ut-control are defined by the testing suites
Messages will direct either to the vDevice to be processed, or to the external hardware which will mimic the physical control.
Example message for the HDMICEC Commands:-
User Commands
HdmiCec
ImageViewOn - User Selects by power on, TV should become active.
Active Source - Change the active source, re-assert the active command
Standby - Put a device on the HDMI Network in standby
Hotplug - Unplug a cable from a device
Internal Messages (maybe rejected from the module).
Send a yaml / json file to the ut-control module
If the device is vDevice, then send the message onto a an http port as defined by the configuration
if the device is a real device, then control the module as specified would have to be controlled in a specific way.
Expectation is the the ut-control module, will have multiple devices that it supports, and that the rack configuration will be setup to define the devices per module that are controllable.
Messages sent to ut-control are defined by the testing suites
Messages will direct either to the vDevice to be processed, or to the external hardware which will mimic the physical control.
Example message for the HDMICEC Commands:-
User Commands
HdmiCec
Internal Messages (maybe rejected from the module).