SAS 2008 – IEEE Sensors Applications Symposium

IMPLEMENTATION OF IEEE 1451.1 CONFORMANCE/FUNCTIONALITYCONFORMANCE/FUNCTIONALITY

TESTING USING LABVIEW

Richard Franzl1Jonathan Morris2Jonathan Morris2

Deniz Gurkan1

University of Houston, Department of Engineering Technology1

Stennis Space Center – NASA2

MotivationTraditional sensor nodesSensor

Desired plug-&-play, similar to computer networksN l & l

SensorSensor Sensor Sensor

No plug-&-play availableSensor

Networked nodes based on IEEE 1451.1TEDS 1451.4Plug-&-play available

Presentation Outline

Overview of IEEE 1451.1 StandardComponents of an IEEE 1451.1 sensor nodeNCAP-to-NCAP network communication

Program Design Specification g g pNCAP Tester Suite and NCAP ServerTest system hardwareSoftware architectureSoftware architecturePublish/Subscribe communication via UDP multicastClient/Server and Server/Client communication via TCP

TestingTestingMessage conformance testing exampleFunctionality testing example (test case)

C l i /F t kConclusions/Future work

Components of a IEEE 1451 Sensor NodeIEEE 1451 Sensor Node

Network Capable Application Processor pp(NCAP) Manages STIM(s)

Converts Data from STIM to network readable dataTransmits data to network data layer

Smart Transducer Interface Module (STIM)Interface Module (STIM)

Acquires the signal from sensor and performs signal conditioningHolds calibrationHolds calibration constants and operating parameters in Transducer Electronic Datasheets (TEDS)

TEDS Examples(Transducer Electronic Data Sheet)( a sduce ect o c ata S eet)

IEEE 1451.1 Operational Object BlocksOperational Object BlocksNCAP Block

used for PublisherFunction Block

used for NCAP dataused for Publisher Subscriber, client-server, server-client NCAP to NCAP communication

used for NCAP data transfer functionality

Transducer Blockused for STIM operationsC co u cat o

NCAP owning block for NCAP block operations

used for STIM operations and functionality

NCAP – NCAPNetwork CommunicationNetwork Communication

Three main types of packet formats

Format defined by: Stennis Space Centerpacket formats

Publish-SubscribeClient to serverServer to client

Stennis Space Center Interface Control Document v.2.1Stennis Space Center

NCAP Client NCAP Server

Server to clientOn-the-wire format v.04

NCAP BlockNCAP Bl k NCAP BlockObject ID S-1

Function BlockObject ID S-2

NCAP BlockObject ID C-1

Function BlockObject ID C-2

UDP Publish/Subscribe

TCP Client/Server Transducer BlockObject ID S-3

Transducer BlockObject ID C-3

TCP Client/Server

NCAP Tester SuiteNCAP Client Tester

UDP publish/subscribe message marshalling and fdemarshalling of messages

TCP client/server and server/client marshalling and demarshalling of messages F ll t t d fi d i th T t it f IEEEFollows a test sequence defined in the Test suite for IEEE 1451, performs functional testing as well as conformance testing on messages received from a NUT Marshalling and demarshalling of packets follows IEEEMarshalling and demarshalling of packets follows IEEE 1451.1 class structure and data typesGUI allows

performing the test cases, definitions of each test case,performing the test cases, definitions of each test case, reporting of test results

NCAP message generatorGUI provides a manual interface to allow several IEEEGUI provides a manual interface to allow several IEEE 1451.1 and SSC ICD v2.1 messages to be sent to another NCAP in the network

NCAP Test Suite Main Screen

Test Conformance Values GUI

Test Case Performing GUI

Test Case Results Report

Test Case Descriptions GUI

NCAP Message Generator

NCAP Server

Performs and functions as an IEEE 1451.1 NCAP by providing Publisher/Subscribe andby providing Publisher/Subscribe and Server/Client and Client/Server Communication to another NCAP in the networkD h lli f i d li t/Demarshalling of received client/server messages from another NCAP and marshalling of server/client messages to another NCAP in the

knetworkExpandable plug-and-play sensor data acquisition using IEEE 1451 Smart SensorsgMarshalling and demarshalling of packets follows IEEE 1451.1 class structure and data types

NCAP Server Program GUI

Hardware Architecture2 Dell ComputersNI PXI DAQ CardSCC 2350 C iSCC 2350 CarrierSCC Thermocouple moduleWeed Instruments J-Type Thermocouple Smart Sensor with IEEE 1451 4 TEDS capabilitieswith IEEE 1451.4 TEDS capabilities

Software Architecture

Subscriber

`

Root Stream MessageArgument

Entity

Subscriber Port

Publication Message Directed Message

Client Port Properties String

Object Properties Object Properties Array

U-Integer8 U Integer8 Array

Client Server MessageServer Client MessageString

Octet Octet Array Bit Sequence Class ID Object ID Publication Topic

Object Properties Array Integer8 Integer8 Array Integer16 Integer16 Array Integer32 Integer32 Array

U-Integer8 Array U-Integer16 U-Integer16 Array U-Integer32 U-Integer32 Array Boolean Boolean Array

Server Client Message

pSubscription Qualifier Object Tag Object Dispatch Address Publisher Information Publication Sub Domain Time Interval

g yInteger64 Integer64 Array Units Units Array Time Representation Uncertainty

yFloat32 Float32 Array Float64 Float64 ArrayArgument Array

All application software is developed in the LabView 8.2 Programming Language on Windows XP Operating System.Program data types and classes follow IEEE 1451 1Program data types and classes follow IEEE 1451.1 standard

Publish/SubscribeOperationsOperationsPublisher Port Object Attributes

Publication Domain – distribution scope for publicationop o pub a oPublication Key – application-independent syntax and semantics of publication from Publisher’s point of viewPublication Topic – application-specific syntax and semantics for publication’s contents

Subscriber Port Object AttributesjSubscription Domain – domain identified by a subscriber for a specific publicationSubscription Key – subscriber Subsc pt o ey subsc bedefined analog of Publication Key used for selection of received publications Subscription Qualifier – defines

l f d blselection of received publications on basis of Publication Topic

The header format conforms to Stennis Space Center, SSC-1451.1 On-the-wire v0.4 document.

Client/Server OperationsClient Object Attributes

ObjectID of the object j jblock OperationID of the function operationClientPortBlockCookie for authentication purposesReturnArgumentCount for e pected et nexpected return arguments if any

The header format conforms to Stennis Space Center, SSC-1451.1 On-the-wire v0.4 document.

Server/Client Operations

Server Object AttributesS Obj tObj tID fServerObjectObjectID of the object block OperationID of the function operationfunction operationClientServerReturnCode which is used with the rule base for functionalityyServerPortBlockCookie for authentication purposesReturnArguments which are the expected return arguments if any

The header format conforms to Stennis Space Center, SSC-1451.1 On-the-wire v0.4 document.

NCAP TestingConformance testing

NCAP Tester Program will demarshall received messages g gand report each element of the message packet and will compare the elements received to known element values

Functionality testingy gNCAP Tester Program follows test sequences to check the functionality of an NCAPNCAP and its blocks undergo various states changes during the communication process. The expected behavior of the NCAP is used as a premise to compare the output of the communication between the tester node (TN) and NCAP under test (NUT)node (TN) and NCAP under test (NUT)Test cases developed to create scenarios to observe any unauthorized or unexpected behavior from the NUTWhenever packets are exchanged between the TN andWhenever packets are exchanged between the TN and NUT, the next step of the communication process is observed and matched with the expected result

Conformance testing

Functionality testing

NCAP under test (NUT)Current State

Tester Node (TN)

TN listening and NUT joins the network:TN checks for messages from NUT for ΔT

NUT has no dynamic i

PSK_REQUEST_NCAPBLOCK_ANNOUNCEMENT

NUT has no dynamic announcement

PSK NCAPBLOCK ANNOUNCEMENT

PUBLISHING_ENABLED

TimeoutCASE A

PSK_NCAPBLOCK_ANNOUNCEMENT

NUT identification is achievedCASE B

TN listening and NUT joins the network:TN checks for messages from NUT for ΔT

NUT is not configured to announce

TimeoutCASE C

Future workDeploying the NCAP Server Program onto portable single board computers to use in a smart sensor g ptest bedNCAP Tester Program does one-to-one testing; future work includes upgrading the tester programfuture work includes upgrading the tester program to do one-to-many testing to test all the nodes in the network at onceNCAP to NCAP communication is now availableNCAP-to-NCAP communication is now available through the programs implemented, possible QoS scenarios and applications can possibly be added on top of IEEE 1451 communication to allow smarton top of IEEE 1451 communication to allow smart sensor networks the capability for network health monitoring and network management

References[1] IEEE 1451.1 Standard [2] Wall, R., Huska, A., “Design Platform for Plug&Play IEEE 1451 Traffic

Signal”, University of Idaho, Moscow, Id, 2005 IEEESignal , University of Idaho, Moscow, Id, 2005 IEEE[3] Schneeman, R., “Implementing a Standards-based Distributed

Measurement and Control Application on the Internet”, Sensor Integration Group, NIST, June 1999

[4] Schmalzel, J., Figueroa, F., Morris, J., Mandayam, S., Polikar, R., “An [ ] , , g , , , , y , , , ,Architecture for Intelligent Systems Based on Smart Sensors”, IEEE Transactions on Instrumentation and Measurement, Vol 54, No. 4, August 2005

[5] Lee, K., Kim, M., Lee S., Lee, H., “IEEE 1451 Based Smart module for In-Vehicle Networking Systems of Intelligent Vehicles” IEEEIn-Vehicle Networking Systems of Intelligent Vehicles , IEEE Transactions On Industrial Electronics, Vol. 51, No. 6, Dec. 2004.

[6] García-Hernández, C. Ibargüengoytia-González, P., García-Hernández, J. Pérez-Díaz, C., Wireless Sensor Networks and Applications: a Survey, Electric Research Institute (IIE), ITESM, Cuernavaca Campus, Mexico( ), , p ,

[7] IEEE 1451.1 Interface Control Document V2.1, Stennis Space Center[8] IEEE 1451.1 On-the-Wire Format V0.4_SSC, Stennis Space Center[9] IEEE 1451.1 Test Case Suite, Gurkan, D., Singla, A., Ma, H., Franzl, R.,

University of Houston Department of Engineering Technology, y p g g gy,December 2007