From ec2f39481afe99b7df2c61eb017375bd1d20e751 Mon Sep 17 00:00:00 2001 From: Darryl Mocek Date: Mon, 6 Nov 2023 16:32:27 -0800 Subject: [PATCH] feat: Protocol Info In Device Signed-off-by: Darryl Mocek --- docs_src/design/ucr/Protocol-Info-In-Device.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs_src/design/ucr/Protocol-Info-In-Device.md b/docs_src/design/ucr/Protocol-Info-In-Device.md index 5aadcb3bda..dd58202ad7 100644 --- a/docs_src/design/ucr/Protocol-Info-In-Device.md +++ b/docs_src/design/ucr/Protocol-Info-In-Device.md @@ -16,9 +16,9 @@ The Device Profile describes the device. There are many different manufacturers Any users that create Device Profiles and Devices that have protocol-specific attribute values. ## Description -The Device Profile **describes** the device and its attributes, it's type. Different manufacturers can build the same type of device using different protocols and the same device using the same protocol but different configuration (e.g. different Modbus HoldingRegister). For example, two different manufacturers may build an HVAC using ModBus, and another may build an HVAC using SNMP. In the case of two Modbus devices, there will need to be two different Device Profiles, even though the devices are the same and have the same attributes, because the protocol configurations (e.g. HoldingRegister) will conflict. Device Profile +The Device Profile **describes** the device and its attributes, it's type. Different manufacturers can build the same type of device using different protocols and the same device using the same protocol but different configuration (e.g. different Modbus HoldingRegister's). For example, two different manufacturers may build an HVAC using ModBus, and another may build an HVAC using SNMP. In the case of two Modbus devices, there will need to be two different Device Profiles, even though the devices are the same and have the same attributes, because the protocol configurations (e.g. HoldingRegister) will conflict. -If the protocol information resides in the Device, which describes a specific (instance of a) device only a single Device Profile is needed as all devices of the same type can use the same Device Profile. This becomes more important as you have more devices, potentially increasing the number and management of Device Profiles when one will do. +If the protocol information resides in the Device, which describes a specific (instance of a) device, only a single Device Profile is needed as all devices of the same type can use the same Device Profile. This becomes more important as you have more devices, potentially increasing the number and management of Device Profiles when a single one will do. ## Existing solutions