Annotated XML Examples

From MTConnect® User's Portal
Jump to: navigation, search

Simplest Device

For the simplest possible device, we are modeling a saw that has only an Availability (the minimal set of DataItem). To retrieve this information, we send the following request to the Agent:

The Agent responds as follows:

1.	<?xml version="1.0" encoding="UTF-8"?>
2.	<MTConnectDevices xmlns:m="" xmlns:xsi="" xmlns="" xsi:schemaLocation=" /schemas/MTConnectDevices.xsd">
3.	<Header sender="" bufferSize="100000" 
      creationTime="2008-07-07T23:07:50-07:00" version="0.9" 

Line 3 provides the instanceId as a unique number for this request. For this example, the Agent does not persist the Samples, Events, and Condition. Therefore, this number will change every time that it is recorded. The bufferSize indicates that this Agent is capable of storing 100,000 DataItem of category Sample, Event, and Condition.

4.	<Devices>
5.	  <Device iso841Class="6" uuid="linux-01" name="LinuxCNC"
               sampleInterval="100.0" id="d">
6.	    <Description manufacturer="NIST" serialNumber="01"/>

The above device description includes the unique id and a sample interval of ten times per second. Since there are no telemetry data being collected, sampling at once per second is typically adequate.

7.	    </Components>
8.	     <DataItems>
9.	        <DataItem type="AVAILABILITY" name="avail" category="EVENT"
10.	      </DataItems>

As was stated previously, the device is only required to have one DataItem and it is of the type AVAILABILITY which MUST report the device’s present ability to communicate. The DataItem on line 9 has an id of “a”. This will allow events responding to this DataItem to be easily associated.

11.	      </Components>
12.	    </Device>
13.	  </Devices>
14.	</MTConnectDevices>

Lines 11 through 14 terminate each element type and close the document.

More Complex Probe Example

The Sample was generated with the following request:

The following is an example of a 3 axis mill simulation. The mill has three linear axes and one rotary axis (spindle):

1.	<?xml version="1.0" encoding="UTF-8"?>
2.	<MTConnectDevices xmlns:m="" xmlns:xsi="" xmlns="" xsi:schemaLocation=" /schemas/MTConnectDevices.xsd">
3.	  <Header sender="" bufferSize="100000" creationTime=
           "2008-07-07T23:07:50-07:00" version="0.9"
4.	   <Devices>
5.	    <Device iso841Class="6" uuid="linux-01" name="LinuxCNC" 
             sampleRate="100.0" id="d1">

Here we provide the top level container Devices and the information on the Device.

6.	   <Description manufacturer="NIST" serialNumber="01"/>
7.	     <DataItems>
8.	           <DataItem type="AVAILABILITY" name="avail" category="EVENT"
9.	       </DataItems>
10.	    <Components>
11.	    <Axes name="Axes" id="3">

On line 11 we introduce the collection of Axes. The Axes component is a special component that acts as an abstract component as well as a collection. The Axes component contains various DataItems that have a global context; they are not associated with any one axis but they go across all axes.

13.	      <Rotary name="C" id="c1">
14.	       <DataItems>
15.	        <DataItem type="ROTARY_VELOCITY" name="Cspeed" category="SAMPLE"
                  id="c2" nativeUnits="REVOLUTION/MINUTE" subType="ACTUAL" 
16.	           <Source>Sspeed</Source>
17.	        </DataItem>   
18.	          <DataItem type=”ROTARY_MODE” name=”Cmode” category=”EVENT”
19.	             <Constraints>
20.	                <Value>SPINDLE</Value>
21.	             </Constraints>
22.	          </DataItem>
23.	        </DataItems>
24.	     </Rotary>

The spindle component (Rotary Axis C) declared on line 13 is the C axis and has spindle specific DataItems.

25.	     <Linear name="X" id="x1">
26.	       <DataItems>
27.	         <DataItem type="POSITION" name="Xact" category="SAMPLE" id="x2"
               nativeUnits="MILLIMETER" subType="ACTUAL" units="MILLIMETER"/>
28.	         <DataItem type="POSITION" name="Xcom" category="SAMPLE" id="x3"
               nativeUnits="MILLIMETER" subType="COMMANDED" 
29.	       </DataItems>
30.	     </Linear>
31.	     <Linear name="Y" id="y1">
32.	       <DataItems>
33.	         <DataItem type="POSITION" name="Yact" category="SAMPLE" id="y2"
                nativeUnits="MILLIMETER" subType="ACTUAL"
34.	         <DataItem type="POSITION" name="Ycom" category="SAMPLE" id="y3"
                nativeUnits="MILLIMETER" subType="COMMANDED"
35.	       </DataItems>
36.	     </Linear>
37.	     <Linear name="Z" id="z1">
38.	      <DataItems>
39.	        <DataItem type="POSITION" name="Zact" category="SAMPLE" id="z2" 
               nativeUnits="MILLIMETER" subType="ACTUAL" units="MILLIMETER"/>
           <DataItem type="POSITION" name="Zcom" 
             category="SAMPLE" id="z3"
               nativeUnits="MILLIMETER" subType="COMMANDED"
41.	      </DataItems>
42.	     </Linear>
43.	  </Components>
44.	  </Axes>

Lines 25, 31, and 37 define the three linear axes X, Y, and Z respectively. In this example device, the Agent is only collecting the actual and commanded positions.

The Controller is capable of providing the program name, block, and the current line being executed:

45.	    <Controller name="Controller" id="cn8">
46.	     <Components>
47.	      <Path id=”pth1” name=”path”>
48.	        <DataItems>
49.	          <DataItem type="LINE" name="line" category="EVENT" id="p1"/>
50.	          <DataItem type="CONTROLLER_MODE" name="mode" category="EVENT"
51.	          <DataItem type="PROGRAM" name="program" category="EVENT"
52.	          <DataItem type="EXECUTION" name="execution" category="EVENT"
53.	          <DataItem type="PATH_FEEDRATE" name="feedrate" 
54.	              category="SAMPLE" id="p5" units=”MILLIMETER/SECOND”
                  nativeUnits=”MILLIMETER/SECOND” />
55.	          <DataItem type="PATH_POSITION" name="position" 
56.	              category="SAMPLE" id="p6" units=”MILLIMETER_3D” 
57.	              nativeUnits=”INCH_3D”/>
58.	        </DataItems>
59.	      </Path>
60.	     </Components>
61.	    </Controller>
62.	   </Components>
63.	</MTConnectDevices>