System information

i.LON SmartServer 2.0 Programmer’s Reference
4-18
For example, consider a scenario where a SOAP application uses the Write function to write to the
value of a data point called “nvoValue”. Assume that the last application to write to the value of
nvoValue used priority level 75 when it updated the data point. In that case, the current application
must use a priority value between 0 and 75 (inclusive) to successfully write a new value to the data
point.
Data point priority levels allow you to give some applications precedence over others when more than
one application might attempt to update the same data point. The following describes a series of
events where various applications write to the value of a single data point. For each event, the priority
level used is listed, as well as a description of whether or not the update was successful, and why. This
should help you understand how you can use data point priority levels to determine which applications
will be given precedence when updating the value of a data point.
Event Priority Level
Assigned
Result of Operation
Power-Up 255 The value of the data point is updated
successfully.
Scheduler Updates Data
Point
240 The value of the data point is updated
successfully, as the priority used by the
Scheduler is greater than that assigned to the data
point during power-up.
Custom Application
Invokes Write Function on
Data Server
75
The value of the data point is updated
successfully, as the priority used in the call to
Write function is greater than that assigned to the
data point by the Scheduler.
Scheduler Updates Data
Point
240 The value of the data point is not updated
successfully, as the priority used by the
Scheduler is less than that used by the last
application to update the data point.
Custom Application Calls
Invoke function to Reset
the Data Point Priority on
Data Server
245 The priority of the data point is not reset to 255,
as the priority level set in the Invoke function
(245) is less than that used by the last application
to update the data point (240).
Custom Application Calls
Invoke function to Reset
the Data Point Priority on
Data Server
75 The custom application calls the Invoke function
and resets the priority level assigned to the data
point to 255, the lowest priority. At this point,
all applications will be able to write to the data
point.
Scheduler Updates Data
Point
240 The Scheduler successfully updates the value of
the data point, as the priority level used here
(240) is greater than current priority assigned to
the data point after being reset by the Invoke
function (255).
4.3.8 Using the Delete Function on the Data Server
You can use the Delete function to delete a data point on the Data Server. To delete a data point, you
provide an <Item> element of a <driver>_Dp_Cfg xsi:type that includes the <UCPTname> property of
the data point to be deleted. If you do not specify the xsi:type, a fault may be returned stating that the