IEEE 1451 Manual
IEEE 1451 Manual
IEEE 1451 Manual
item whatsoever,
whether express, implied, or statutory, including, but not limited to, any warranty of merchantability or fitness for a
particular purpose or any warranty that the contents of the item will be error-free.
NCAP
The NCAP is multi-port or multi-functional. The ports are:
RS232 (Dot 2)
USB (in future)
Wi-Fi (Dot 5)
One 8-pin connector with SPI interface
o See Dot 2 standard for description
However, only one port is active at a time, in part to simplify the software, which is a goal
for the reference design. Note that Dot5 is a local Ad hoc Wi-Fi network, not connected directly
to the Internet except through the NCAP. The Internet protocol is the IEEE 145.0 (Dot 0)
HTTP is provided in the NCAP.
The NCAP is available in a case for purchase from Esensors.
TIM
The types of TIMs provided in this kit are:
Dot 2 -- RS232
With various I/Os and sensor including Dot 4 sensor
Wi-Fi (Dot 5)
With various I/Os and sensors (3 types) including Dot 4 sensor
Detailed Description
Multiport NCAP Hardware
The NCAP consists of two boards each with a microcontroller (Fig.2). The main board
handles the local network or ports while the second handles the Ethernet/Internet interface.
The two boards are stacked one over the other and connected via SPI bus. The
connection to the Internet is via Ethernet (not Wi-Fi). Power is provided via 9-12v DC adapter
A photo of the boards is shown in Fig. 3. The circuit is described further in Appendix C.
Signal
Analog In #2
Analog In #1
Analog In #4
Analog In #3
Analog Out#2
Analog Out#1
Digital In - 1
Digital In - 0
Pin
9
10
11
12
13
14
15
16
Signal
Digital In - 3
Digital In - 2
Digital In - 5
Digital In - 4
Digital In - 7
Digital In - 6
Digital Out - 1
Digital Out - 0
Pin
17
18
19
20
21
22
23
24
Signal
Digital Out - 3
Digital Out - 2
Digital Out - 5
Digital Out - 4
Digital Out - 7
Digital Out - 6
Pin
25
26
27
28
29
30
Signal
nc
Relay NO
Ground
+5v out
nc
nc
Relay Com
Relay NC
Table 2.
Dot 2 TIM Data Channel Assignments
Channel Signal name In/Out
Data Type Note
1
ANx1
-5.0V to 5.0 V
ANx2
-5.0V to 5.0 V
Temperature Input
FP (32)
Humidity
Input
FP (32)
0 to 100%, 0.5%
DI_0
Digital Input #0
UINT8
1: high, 0: low
DO_0
1: high, 0: low
Relay
Digital Output
UIN8
1: close, 0: open
D2A_1
Analog Output
FP (32)
0V to 5.0 V
LCD
Output
10
J7, D1
Dot4 Analog In
FP (32)
11
Dot4 TEDS
Input
UINT8
A Dot 4 type sensor is an analog output sensor with a small EEPROM on a 1-wire bus
as the TEDS. There are two types of interfaces, one with separate lines for the TEDS and data
and another which has the analog and digital on the same wire (2 wires including ground). For
the combined analog/digital interface, the analog signal is modulated on a current source for
positive voltages (IEPE) and the digital (TEDS) is connected for negative voltages (see
Appendix F). This TIM has these ports:
Class 1 with IEPE (two of these)
Connector is HD-BNC
Class 2 with 4-20 mA signal input
Connector (J5) is 5-pin header with 0.1 spacing
Class 2 with 0 to 5v signal input
Connector (J6) is 5-pin header with 0.1 spacing
Signal #1 (J7)
IEPE (coax)
Pin
1
Signal # 2 (J8)
IEPE (coax)
Pin
1
2
3
4
5
Signal #3 (J5)
TEDS
+Vs
LP+
LPGnd
Pin
1
2
3
4
5
Signal #4 (J6)
TEDS
+Vss
In+
InGnd
The TIM will have a temperature and humidity sensor (SHT11) also. The channel assignments
are given in Table 2.
These WTIMs can be battery operated (rechargeable battery) with line operated option
(via 5v supply from USB connector or RS-232 connector which also acts as the charger.
The I/O lines are the same for the Serial (Dot 2) TIM (Table 1), except that there is no
relay (to conserve battery power), specifically:
Four analog inputs, -5 to +5v
With 10-bit a/d
Two analog outputs (0 to +5v)
Two 8-bit digital ports (selectable configuration via switch)
One 8-bit input and one 8-bit output
Temperature/Humidity sensor
LCD (16x2 line)
The channel assignments are given in Table 2. Please note Dot4 sensor can be
connected to J8 connector on any TIM board(Dot 2 or Dot 5).
TEDS
The Transducer Electronic Data Sheet (TEDS) is stored in the TIM, here as read-only
files (mostly binary). The following TEDS are present:
META-TEDS
TransducerChannel TEDS (several)
Users Transducer Name TEDS (ASCII)
PHY TEDS
The data in the TEDS is stored with the least significant byte at the highest address (big
Endian) following the Dot 0 specification. For example decimal 1000 (hexadecimal 03 E8, two
bytes) is stored as 03 E8 which is the human readable format (English). Many computers
reverse the order (little endian) and it is the responsibility of the TIM designer to assure that the
TEDS data, especially binary, is transmitted in the proper order.
As a development tool, this system provides the way to query, read and write/add raw
TEDS via web interface.
The response of query TEDS is to provide information like TEDS attributes,
status, current size, checksum and maximum size.
The reply of read TEDS is the raw TEDS stored in TIMs non volatile memory
output in Hex format.
User can change or add raw TEDS (in Hex format). TIM device will do sanity
checking with the input raw TEDS before storing it to non volatile memory, which
includes general format checking (length, checksum), size and if the TEDS type
in the raw TEDS match with the input TEDS type. If the specified raw TEDS
already exist, according to input Channel Id and TEDS type, TIM will update the
old TEDS with the new one after sanity checking, otherwise, it will create a new
TEDS.
1451.X
Comm Layer
1451.0
Control Logic
Analog/
Digital
Conversion
Signal
Processing
Sensor
TEDS
LAN
Message
Abstraction,
TCP/IP, Web
Server
Embedded
Application
1451.0 Routing,
signal
processing,
TEDS mgt
1451.X
Comm Layer
Remote Computer
the NCAP. When a TIM is asked for a reading, it will acquire the data and generally return it in
fundamental A/D counts. The NCAP will then apply the correction data found in the TEDS and
convert it to calibrated SI data. The data is then transferred over the external network using http
protocol and XML. The reason for this method of transferring from the TIM and processing in
the NCAP allows the calibration data to be associated with the sensor itself, but offloads the
complex processing to the NCAP. This allows the TIM to be implemented with small
microprocessors.
An alternate reference model is shown in Fig. A2.
Fig. A2 IEEE 1451 Reference Model showing relation of Dot 0 and PHY sections.
The benefits of this technology are myriad and varied, depending on the configuration chosen.
The first, and most apparent, benefit is the open nature of this standard that allows different
manufacturers to produce products with the assurance that they will self configures and
seamlessly operates with products from other manufacturers (plug and play feature). All 1451
systems benefit from the use of common codes and formats. This means that TIMs can be
configured into systems and be recognized and configured by NCAPs without previous
knowledge of that TIM. Sensors and actuators can easily be added to or removed from a
system. If a wireless sensor is used, no action needs to be taken other than placing the sensor
and ensuring that an appropriate wireless NCAP is within range. This capability allows sensors
to be placed during testing phases or when a specific testing need is discovered and then easily
removed during normal deployment.
A 1451 based system also returns sensor data in calibrated, SI units. This places the correction
routines in the sensor where they belong and also reduces the chances for errors to be
introduced by unit mismatch. In addition, all operating parameters are queryable, thus allowing
the application to certify units, calibration and operating data.
9
The quality of the measurement can be improved because analog to digital conversion occurs
near the signal being measured. This, in turn, eliminates long runs of analog wiring that can
introduce noise and crosstalk, as well as eliminating large bundles of wiring. In addition to the
noise problem, wire bundles are heavy, prone to failure, and difficult to diagnose and repair.
The status of the different parts of the standard are as follows:
Dot 0 -- General Format --- approved 2007
Dot 1 -- NCAP Protocol (optional) approved 1998, being revised.
Dot 2 -- Serial, point-to-point revision done, final approval pending
Dot 3 -- Multi-drop & timestamp -- approved 2003, but obsolete (no hardware)
Dot 4 -- Analog & TEDS (approved 2004, TEDS only)
Dot 5 -- Wireless (Bluetooth, WiFi, maybe Zigbee) -- approved 2007
Dot 7 --- RFID with sensors -- approved 2010
The basic functions of Dot 0 are to handle the following commands:
TEDS/Status requests
Triggering and configuration
Sensor read commands and data return
Actuator write commands and data sending
TEDS
The transducer electronic data sheets required are:
MetaTEDS
Channel TEDS
Calibration TEDS (unless SI units)
Xdr-name TEDS
Phy TEDS
These are in specific, compact binary formats. There are many additional, optional TEDS.
10
Appendix B. References
1.
11
12
The pinouts for the connector J2 are shown in Table E1 (same as Table 1).
13
Signal
Analog In #2
Analog In #1
Analog In #4
Analog In #3
Analog Out#2
Analog Out#1
Digital In - 1
Digital In - 0
Pin
9
10
11
12
13
14
15
16
Signal
Digital In - 3
Digital In - 2
Digital In - 5
Digital In - 4
Digital In - 7
Digital In - 6
Digital Out - 1
Digital Out - 0
Pin
17
18
19
20
21
22
23
24
Signal
Digital Out - 3
Digital Out - 2
Digital Out - 5
Digital Out - 4
Digital Out - 7
Digital Out - 6
Pin
25
26
27
28
29
30
Signal
nc
Relay NO
Ground
+5v out
nc
nc
Relay Com
Relay NC
# pins
4
2
16
2
6?
2
1
N/A
N/A
N/A
Option
All
All
Opt A
All
Opt B
Opt B
Opt B
All
All
All
In/Out
In
Out
8in & 8out
In
Out
Out
Out
In
In
1in, 1out
Notes
A/d
D/a
Two digital ports
Factory reset and updating firmware
2x16 Display
In addition to power & Communication
14
b
Fig. F1 IEEE 1451.4 Interfaces (a) Class 1 and (b) Class 2
Block Diagram
A block diagram of the Dot4 TIM is shown in Fig. F2.
15
Class 1 Interface
Analog Section
The class 1 interface combines an analog line and a 1-wire digital line with a TEDS (Fig. F3a).
The analog part utilizes a Integrated Electronic Piezo Electric Interface (IEPE) developed
originally by accelerometer (and other) manufacturers ( http://www.mmf.de/iepe_standard.htm
which is ref [4]). See Fig. F3. It is also known under other brand-names (e.g. ICP).
If no sensor is present, the voltage at the connector will go to saturation (about +22 v). This
condition is detected by a comparator. When the sensor comes back on line, the TEDS is read
again. If the UUID is different, a change in sensor is recorded.
Digital (TEDS interface) Section
For the Class 1 interface, the TEDS is accessed when the voltage on the wire is negative.
Diodes on the sensor side separate the digital (negative) from the analog (positive) signals. The
reason for using a 1-wire cable (coax) is that it is much easier to install, especially for small
sensors (such as accelerometers), than multi-wire cables. The TEDS is a special EEPROM with
a 1-wire interface. Data is transmitted in both directions, depending on timing. The data pin on
the EEPROM shifts between input and output (also provides chip power). The EEPROM is
standard CMOS but is connected backward at the sensor end (+Vcc to ground). Timing is
critical and is best implemented with a special interface 1-wire master. Converting the bidirectional signal from negative to positive requires a special MMI (mixed mode interface) driver
(see www.maxim-ic.com/app-notes/index.mvp/id/4491) which uses a mosfet pair (and analog
switch). This is shown in Fig. F5.
a microcomputer via a SPI line. The combination of the two analog switches on inputs #1 and
#2 plus the digital mux (#3 and #4) selects one of the four TEDS.
Class 2 Interface
The class 2 interface simply provides a separate pin for the 1-wire EEPROM (TEDS). It is
connected directly to the 1-wire master (no additional interface needed). We have selected two
representative inputs (another possibility is a strain sensor). A HD-BNC is the chosen coax
connector.
4-20 mA Current Loop
Many industrial sensors have a 4-20 mA current loop (transmitter) as the output. There are two
general types: (1) loop powered and (2) sensor excitation voltage external to the sensor. Input #
3 is of this type. The +24 volt supply on pin 5 is used for loop powered devices (pins 3 & 4
connected, pins 1 and 2 connected), see Fig. F6
If the input is open (over 10k) , the light pullup resistor brings the input to over +5 v.
D/A Output
The two analog outputs are the same as for the Dot 2 interface except that the voltage is 0-3
volts because of the battery operation.
Power Supply
Power (+5v) is supplied by the USB port (J4). A battery charger is present, although this is not
needed for the Dot 4 TIM. Separate 3.3 v regulators are used for the two microcontrollers. A
boost switching power supply (U7) generates the +25v (see Fig. F2). A DC/DC supply (U9)
provides the -5v.
The power and signals go between boards through redundant connectors J3 and J4.
Signal List
Table F1. Signal List for Sensor Microcontroller (U12)
Signal
Analog inputs
1-Wire master (I2C)
LCD
Status LEDs
# pins
4
2
4
3
In/Out
In
Both
Out
Out
Notes
Class 1 and Class 2
For 1-Wire (Dot 4 TEDS)
16x2 alphanumeric (SPI)
TEDS Reading
The reading of the TEDS, which has several sections, is done on power-up and occasionally
thereafter, at least if a sensor is removed and replaced. The TEDS data is transferred to a
cache TEDS (C-TEDS) on the TIM where it is more easily available. Each TEDS has a unique
ID (UUID, 48-bit + a chip family # of 8-bits) which aids in detection of change of sensor. This is
in addition to the basic TEDS (64-bits) and a sensor specific section.
The Dot 4 TEDS must be translated to a Dot 0 (Dot 2 TIM) style TEDS which is required by the
NCAP. This Dot 0 TEDS is also stored in the cache TEDS and is the TEDS data sent to the
NCAP upon request.
The full schematics (pdf format) are provided in a separate file available for download from this
site : http://www.eesensors.com/media/wysiwyg/pdf/NCAP-Main-Schematic.pdf
19
20
21
Network Configuration
The network configuration page is password protected. The default username and password for
the device is admin & password. The NETWORK CONFIGURATION page enables the user to
set up the device IP & host name using the web interface. When the NETWORK
CONFIGURATION link is clicked the NETWORK CONFIGURATION page appears; see Figure
G6.
From the NETWORK CONFIGURATION screen it is possible to change the various network
settings involved in any IP addressable device, port number for the webpage, DNS, gateway,
admin ID and password. The device requires an internet connection if you want to set the
device time automatically. The device uses TAI time to timestamp sensor data. In case of power
loss the device automatically corrects the time upon the Internet connection is available. Once
changes are made it is necessary to left click on the Save Config button to have the changes
take effect.
When you change the IP address though the webpage interface, the next page displayed is the
Reboot in Progress page depicted in Figure G7.
Note: If you get the message Error: Connection to NCAP device was lost then the browser still points to
the former IP address. When the new IP address is entered into the address bar the screen will correctly
display the NCAP MAIN (Home) Page.
22
23
Esensors Inc.
Development Kit
24
Esensors Inc.
Development Kit
Data Type
ANx1
FP(32)
Analog Input
#1
ANx2
Analog Input
#1
Temperature Input
Humidity
Input
FP(32)
DI_0
UINT8
DO_0
Relay
Digital Input
#0
Digital
Output #0
Digital
Output
D2A_1
FP(32)
LCD
Analog
Output
Output
10
J7, D1
FP (32)
11
Dot4 TEDS
Dot4 Analog
In
Input
FP(32)
FP(32)
UINT8
UINT8
J2
Connector
Pin2
Note
-5.0V to
5.0V
Pin1
-5.0V to
5.0V
-40 to 123.8
C, 0.1C
0 to 100%,
0.5%
Pin8
1: high, 0:
low
Pin16
1: high, 0:
low
Pin23(COM), 1: close, 0:
24(NC),
open
26(NO)
Pin6
0V to 5.0 V
Character
UINT8
Array for 32
characters
32 octets, in
Hex format
25
Esensors Inc.
Development Kit
26
Esensors Inc.
Development Kit
27
Esensors Inc.
Development Kit
Go back to "Read Raw TEDS" page and read the read XdcrName TEDS from channel 4,
we can see the TEDS has been added to the TIM, Fig. H6
Fig. H7 TEDS type Input must match with TEDS access code in raw TEDS
28
Esensors Inc.
Development Kit
5. Transducer Discovery
To report the available channel from TIM, NCAP reads TIM's MetaTEDS first since
MetaTEDS has MaxChan field indicating number of implemented transducer channels , then
NCAP reads the each XdcrName TEDS from TIM.
Example: we just add Read XdcrName TEDS for channel 4 in above example, we need
to modify the MetaTEDS's MaxChan field from 3 to 4. Otherwise, "Transducer Discovery" will
report 3 channels instead of 4, Fig. H8
29
Esensors Inc.
Development Kit
The MaxChan TLV in this raw TEDS is " 0D, 02, 00, 03", change it to " 0D, 02, 00, 04".
We don't need to change TEDS length field since no octet had been add or removed. Put the
new raw TED in "Write Raw TEDS" page's Raw TEDS(Hex) input field, recalculate the
checksum by clicking Calculate Checksum button then click Write Raw Teds button, Fig. H10.
30
Esensors Inc.
Development Kit
6. WTIM Discovery
NCAP device is capable to communicate with 253 WTIM devices (TIM IDs from 2 to
254), See Fig. H12. NCAP maintains a WTIM connection list internally. One can ask NCAP to
scan the Wi-Fi network to generate the WTIM list, NCAP will query MetaTEDS for each WTIM Id,
mark it as "connected" when it gets a response or "disconnected" when there is no response
within 250ms. The scan operation is based on timeout, so it takes up to 70 seconds to scan TIM
Id from 2 to 254. The scan time can be reduced by narrowing down the scan range. Whenever
NCAP is requested to communicate with WTIM device, NCAP always updates the connection
status for the specified WTIM device.
One can also ask NCAP to display (report) WTIM list, save list to non-volatile memory
(EEPROM) or erase (clear) list. Please note that for "Report", "Save" and "Clear" operations,
NCAP does not communicate with any WTIM device, the operation is for WTIM list cached in
the NCAP device.
Esensors Inc.
Development Kit
32
Esensors Inc.
Development Kit
33
Esensors Inc.
Development Kit
Bootloader LED
D10
D9
D9
USB Connector
J3
J4
J4
Type
Mini-B
Micro-AB
Mini-B
34
Esensors Inc.
Development Kit
Click "Load Hex File" button to locate the firmware file on the PC. For easy identification,
the firmware file name is named after the board name (NCAP-ETH, NCAP-MAIN or
TIM-COM) and extension is "hex". Fig. I4
The factory default state for NCAP and TIM boards are:
Board
IP Address
Host Name
Wi-Fi SSID
Name
NCAP-ETH
NACPMAIN
TIM-COM
Wi-Fi
Network
Type
Security
Type
192.168.254.102 NCAP_BASE_ETH
192.168.254.102 NCAP_BASE_WF
NCAP_WF_Setup
Ad hoc
None
192.168.254.102 TIM_COM_WF
TIM_WiFi_Setup
Ad hoc
None
35
Esensors Inc.
Development Kit
36
Esensors Inc.
Development Kit
37
Esensors Inc.
Development Kit
38
Esensors Inc.
Development Kit
39
Esensors Inc.
Development Kit
time errors in this mode. The network configurations like gateway and DNS must be properly set
for this feature since device need Internet access.
Another way is to set the device's clock manually. This can be done by clicking the "Set
Device Clock" button in Network Configuration webpage. Device does not need Internet access
in this mode. The disadvantages are: the clock needs to be set whenever device is re-powered
since it cannot save time when power is lost. The time may also have accumulated error from
longer run times.
Whenever the clock on NCAP-ETH board is updated, it will automatically set the clock
on NCAP-MAIN board. NCAP device will put the timestamp for sensor data when it is received
from the TIM board. The timestamp format is based on IEEE 1451.0-2007 (Clause 4.9 Time
Representation), 32-bits TAI seconds and 32-bits nanoseconds.
40