The MIP SDK has two types of “configuration”.
VideoOS.Platform.Configuration
Historically the older, using this class you get the information a client need, so no information about hardware, driver or similar
VideoOS.Platform.ConfigurationItems
This is the Configuration API exposed as strongly typed classes. The Rest API also exposes this.
Converting from one to the other
This snippet of code should show the relations.
private void FindHardwareInfo(FQID cameraFqid)
{
var camera = new VideoOS.Platform.ConfigurationItems.Camera(cameraFqid);
var hardware = new Hardware(camera.ServerId, camera.ParentItemPath);
var driverSettings = hardware.HardwareDriverSettingsFolder.HardwareDriverSettings.FirstOrDefault();
label1.Text += driverSettings.HardwareDriverSettingsChildItems.FirstOrDefault().Properties.GetValue(“MacAddress”);
}
private void FindHardwareInfo(Item cameraItem)
{
FindHardwareInfo(cameraItem.FQID);
}
private void CameraToItem(Camera camera)
{
var item = Configuration.Instance.GetItem(camera.Guid, Kind.Camera);
label1.Text += "Camera item: " + item.Name + Environment.NewLine;
}
In general the MIP SDK cache the configuration at start up. The StatusViewer sample shows a workaround by subscribing to configuration changes, recently we found that this could be improved, please see this topic: Couldn't get the Event name with StatusViewer Sample - #2 by Bo_Ellegard_Andersen