Difference between revisions of "WCPS: Wireless Cyber-Physical Simulator"

From Cyber-Physical Systems Laboratory
Jump to navigationJump to search
 
(247 intermediate revisions by 3 users not shown)
Line 1: Line 1:
End-user's Tutorial on using WCPS: The Wireless Cyber-Physical Simulator
+
----
 +
Wireless Cyber-Physical Simulator (WCPS) is an open-source simulation environment for wireless control systems. By integrating Simulink and the TOSSIM wireless sensor simulator in a holistic simulation environment, WCPS accurately captures the dynamics of both the physical systems and the wireless sensor-actuator networks used for control. WCPS has been used for [http://research.engineering.wustl.edu/~boli/papers/iccps13.pdf realistic case studies of wireless structural control systems for civil infrastructure], [http://www.cse.wustl.edu/~lu/papers/iccps16.pdf studying routing and control of cyber physical system], and [http://research.engineering.wustl.edu/~boli/papers/iccps15_final.pdf incorporating emergency alarms in reliable wireless process control]. The broad application of WCPS is to support cyber-physical systems research on large-scale wireless control systems through high-fidelity joint cyber and physical simulations. This site includes the code release, tutorial, and simulation examples for wireless structural control systems.
  
WCPS is design for, but not limited to, realistic Wireless Structural Control simulations. The efficient integration of Simulink and TOSSIM has made WCPS an ideal choice for realistic wireless control simulations. The following tutorial introduces how to install and configure MATLAB, TinyOS, and PYTHON environments, as well as the WCPS framework. The tutorial herein is specifically organized for end-users who do not do much development but instead trying to do wireless control simulations with Simulink and TOSSIM. A more advanced tutorial for developers can be found [here].
+
== What's New ==
 +
* '''[Software Release]''' WCPS-EC is released. [https://github.com/WU-CPSL/WCPS-EC here].
 +
* '''[Software Release]''' WCPS-RT is released. [https://github.com/WU-CPSL/WCPS-RT here].
 +
* '''[Software Release]''' Dockerized [[WCPS v3.0]] for industrial process control is released. [http://wsn.cse.wustl.edu/index.php/WCPS_v3.0 here].
 +
* '''[Software Release]''' [https://nees.org/groups/wireless_control_benchmark Benchmark Problem in Active Structural Control with Wireless Sensor Network].
 +
* '''[Software Release]''' WCPS v2.0 is released.
 +
* '''[Software Update]''' [https://nees.org/groups/wireless_control_benchmark Benchmark Wireless Structural Control Problem], July 29, 2014.
 +
* '''[News]''' [http://spectrum.ieee.org/podcast/at-work/test-and-measurement/smart-bridges Smart Bridges - Interview and Podcast on Cyber-Physical Systems for Resilient Bridges], August 07, 2013.
 +
* '''[News]''' [http://news.medill.northwestern.edu/chicago/news.aspx?id=222339 Washington Bridge Collapse Could Be a Wake-up Call], May 30, 2013.
 +
* '''[News]''' [http://www.indyposted.com/195455/matthew-roblez-structural-engineering-saves-lives/#.UZ7GqGSAAy8 Matthew Roblez: Structural Engineering Saves Lives], May 22, 2013.
 +
* '''[News Release]''' [http://news.wustl.edu/news/Pages/25358.aspx Engineering Professor Working to Help Bridges Survive Natural Disaster], April 26, 2013.
 +
* '''[Paper]''' [http://research.engineering.wustl.edu/~boli/papers/iccps13.pdf Realistic Case Studies of Wireless Structural Control], ACM/IEEE International Conference on Cyber-Physical Systems (ICCPS'13), April 2013.
 +
* '''[Software Update]''' A complete package of Cygwin with TinyOS 2.1.1, MLA, TOSSIM pre-installed was released [http://wsn.cse.wustl.edu/index.php/WCPS:_Wireless_Cyber-Physical_Simulator#Download_WCPS here], April 01, 2013.
 +
* '''[Software Update]''' WCPS v0.1.1 and the four cases studies for the ICCPS'13 paper was released [http://wsn.cse.wustl.edu/index.php/WCPS:_Wireless_Cyber-Physical_Simulator#Download_WCPS here], March 10, 2013.
 +
* '''[Tutorial]''' Wireless structural control examples from a [http://research.engineering.wustl.edu/~boli/downloads/wcps_structural_perspective.pdf structural perspective], March 09, 2013.
  
== Change Log ==
+
== WCPS Architecture ==
 
+
[[File:Wcps_architecture_wcpsv3.png|600px|thumb|right|Figure 1. WCPS Architecture]]  
* Release: March 10, 2013, [http://research.engineering.wustl.edu/~boli/downloads/wcpsv0.1.1.zip WCPS v0.1.1] released.
+
In the Fig.1, WCPS simulates
* Tutorial: March 09, 2013, WSC Examples from a [http://research.engineering.wustl.edu/~boli/downloads/wcps_structural_perspective.pdf structural perspective].
 
 
 
== WCPS Principle ==
 
 
 
[[File:Wcps_framework.png|500px|humb|right|WCPS Architecture]]  
 
 
 
As shown in the architecture illustrated in Fig. 2, WCPS simulates
 
 
the feedback control loop of the control system as follows.
 
the feedback control loop of the control system as follows.
Sensor data is generated from structural models. Through a cross-platform function call from Simulink, sensor data is injected to the
+
Sensor data is generated from plant models such as structures and water tanks. Through a cross-platform function call from Simulink, sensor data is injected to the
 
corresponding wireless sensors in TOSSIM. Following the routes
 
corresponding wireless sensors in TOSSIM. Following the routes
 
and transmission schedule calculated by the network manager module,
 
and transmission schedule calculated by the network manager module,
Line 21: Line 29:
 
then return the packet delay and loss to the Interfacing Block in
 
then return the packet delay and loss to the Interfacing Block in
 
Simulink through the Python interface. The Packet Collector module
 
Simulink through the Python interface. The Packet Collector module
then to extracts packet delivery information(the delay and loss)from the message pool of returned values in Simulink. Sensor
+
extracts packet delivery information(the delay and loss)from the message pool. Sensor
data and their loss and delay are then provided to the Data Block,
+
data and their loss and delay are provided to the Data Block,
which then feed the sensor data to the controller at the right time
+
which can feed the sensor data to the controller at the right time
 
based on the packet delay (if the packet is not lost). WCPS utilizes
 
based on the packet delay (if the packet is not lost). WCPS utilizes
 
basic API (e.g., the dos, UNIX command) of MATLAB to
 
basic API (e.g., the dos, UNIX command) of MATLAB to
 
do cross-platform function calls. In TOSSIM, we re-implement a
 
do cross-platform function calls. In TOSSIM, we re-implement a
printf method in TinyOS to send TOSSIM simulation results to the
+
printf method in TinyOS to send simulation results to the
 
Interfacing Block.
 
Interfacing Block.
  
User inputs to WCPS includes excitation signals to the structure
+
User inputs to WCPS includes reference signals of the plants and wireless traces used
(e.g., acceleration caused by earthquakes) and wireless traces used
+
as input to TOSSIM.  
as input to TOSSIM. Excitation signal of the structure is provided
 
to the structure models in the format of MAT files.
 
 
The scheduler module calculates transmission schedules. Networking
 
The scheduler module calculates transmission schedules. Networking
 
schedule is then deployed into the MAC layer code of
 
schedule is then deployed into the MAC layer code of
 
wireless nodes and becomes effective after a TinyOS compilation.
 
wireless nodes and becomes effective after a TinyOS compilation.
 
The TDMA MAC layer in WCPS is developed based on the MAC
 
The TDMA MAC layer in WCPS is developed based on the MAC
Layer Architecture (MLA) library [17] and further adapted for
+
Layer Architecture (MLA) library and further adapted for
 
TOSSIM under TinyOS 2.1.1. Received Signal Strength Indication(
 
TOSSIM under TinyOS 2.1.1. Received Signal Strength Indication(
 
RSSI) and wireless noises traces are collected from real-world
 
RSSI) and wireless noises traces are collected from real-world
environments and provided to the wireless model [18] used by TOSSIM
+
environments and provided to the wireless model used by TOSSIM
 
for realistic wireless network simulations.
 
for realistic wireless network simulations.
As shown in Fig. 2, the interfaces between the Simulink model
+
The interfaces between the Simulink model
 
and TOSSIM are encapsulated as two MATLAB embedded functions
 
and TOSSIM are encapsulated as two MATLAB embedded functions
in Simulink: the Interfacing Block and the Data Block. The
+
in Simulink: the Interfacing Block and the Data Block, as is shown in Fig.2. The
 
Interfacing Block extracts delay and loss information from TOSSIM
 
Interfacing Block extracts delay and loss information from TOSSIM
 
messages, and the Data Block decides what data will be used for
 
messages, and the Data Block decides what data will be used for
Line 52: Line 58:
 
structural models and implement alternative scheduling-control
 
structural models and implement alternative scheduling-control
 
approaches.
 
approaches.
 +
[[File:simulink.png|600px|thumb|center|Figure 2. Simulink Model]]
  
== WCPS Capability ==
+
==Environment Installation==
 
+
* Install TinyOS
Fig. 13 shows the end-to-end packet delivery ratio of the wireless
 
network. The end-to-end delivery ratio means the fraction of
 
packets from the sensors that are successfully delivered to the controller.
 
As shown in Fig. 13 Sensor 1 has the lowest delivery ratio
 
because it has a 2-hop route to the controller. Recall that OTDC-1
 
does not perform any retransmission, while OTDC-2 and OTDC-3
 
performs retransmit each packet once and twice, respectively. Under
 
OTDC-1 Sensors 1 and 4 have delivery ratios of 70% and over
 
95%, respectively. As expected more retransmissions improve the
 
deliver ratios of all sensors at the cost of longer delays as described
 
earlier.
 
 
 
[[File:Wcps building prr statistics.png|400px|thumb|left|network statistics]]
 
 
 
[[File:Control perf building 1.png|400px|thumb|center|building control performance 1]]
 
 
 
[[File:Control perf building 2.png|400px|thumb|right|building control performance 2]]
 
 
 
Wireless Structural Control (WSC) systems are a representative
 
class of cyber-physical systems that have the promise to protect
 
our civil infrastructure in the event of earthquake and other natural
 
disasters. To develop WSC systems it is critical to capture both
 
the cyber aspects (wireless communication and control) and the
 
physical aspects (structural dynamics) through realistic and holistic
 
simulations. We have developed the Wireless Cyber-Physical
 
Simulator (WCPS) that integrates a high-fidelity wireless simulator
 
(TOSSIM) and a standard control system simulator (Simulink).
 
With WCPS, we performed two case studies on structural control
 
systems. Each case study combines a realistic structural model and
 
wireless simulations driven by traces collected from real-world deployments.
 
Our case studies leads to three important insights. First,
 
there exist complex tradeoffs among data synchronization, sensing
 
delay, and network reliability under realistic wireless structural
 
control settings. Second, a realistic, integrated wireless control
 
simulator like WCPS is critical in exploring the design tradeoffs
 
in wireless control design. Finally, a control-scheduling co-design
 
approach is effective in wireless control design. In both case studies
 
the integration of a contant-delay control design and a scheduling
 
scheme achieving data synchronization lead to substantial improvement
 
in control performance when compared to a traditional
 
control design. Our cyber-physical simulation methodology and
 
scheduling-control co-design approaches presented in this work not
 
only represent a promising step toward smart civil infrastructure,
 
but also provide useful insights and tools that can be generalized
 
to other cyber-physical systems employing wireless control.
 
 
 
== Live Example ==
 
 
 
===Installation===
 
  
==== Install TinyOS ====
 
 
<pre>
 
<pre>
WCPS is implemented and tested on MacOS X (snowleopard), Windows XP, and Windows 7. Current release of WCPS is under  TinyOS 2.1.1, which can be installed following the two methods.
+
WCPS is implemented and tested on MacOS X (snowleopard), Windows XP, and Windows 7.  
 +
Current release of WCPS is under  TinyOS 2.1.1, which can be installed following the two methods.
 
</pre>
 
</pre>
*Follow the TinyOS official tutorial on installation of TinyOS for your specific platform: [http://docs.tinyos.net/tinywiki/index.php/Getting_started#User_Contributed_Methods Link]
+
* Follow the TinyOS official tutorial on installation of TinyOS for your specific platform: [http://docs.tinyos.net/tinywiki/index.php/Getting_started#User_Contributed_Methods Link]
*Directly download the pre-tested TinyOS 2.1.1 image from here: [http://research.engineering.wustl.edu/~boli/downloads/tinyos-2.1.1.dmg TinyOS2.1.1 for SnowLeopard and later versions.] [Cygwin package]
+
* Directly download the pre-tested TinyOS 2.1.1 image from here: [http://research.engineering.wustl.edu/~boli/downloads/tinyos-2.1.1.dmg TinyOS2.1.1 for SnowLeopard(and possibly later versions)] [Cygwin package coming soon.]
  
==== Install Mac Layer Architecture(MLA) ====
+
* Install Mac Layer Architecture(MLA)
 
<pre>
 
<pre>
 
The MAC Layer Architecture (MLA) provides a component-based architecture for MAC protocols in wireless sensor networks. MLA extends the Unified Power  
 
The MAC Layer Architecture (MLA) provides a component-based architecture for MAC protocols in wireless sensor networks. MLA extends the Unified Power  
Line 118: Line 76:
 
reusable components that implement MAC layer logic on top of them. The MLA architecture can be used to develop a large number of platform-independent  
 
reusable components that implement MAC layer logic on top of them. The MLA architecture can be used to develop a large number of platform-independent  
 
MAC implementations, with little or no further effort required to adapt these implementations to new hardware platforms. Our current implementation of MLA
 
MAC implementations, with little or no further effort required to adapt these implementations to new hardware platforms. Our current implementation of MLA
is built on top of TinyOS 2.1.1. It currently supports platforms which use the CC2420 radio stack and has been tested on TelosB motes. In addition to providing
+
is built on top of TinyOS 2.1.1. It currently supports platforms which use the CC2420 radio stack and has been tested on TelosB motes. In addition to providing
interfaces and components for building new MAC layer implementations, MLA includes implementations of five representative MAC layers:
+
interfaces and components for building new MAC layer implementations, MLA includes implementations of five representative MAC layers. Specifically for WCPS, we
 +
adopt and further change the pure-TDMA MAC protocol for centralized data communication.
 
</pre>
 
</pre>
  
 
* Follow the instructions here: [http://wsn.cse.wustl.edu/index.php?title=MAC_Layer_Architecture Install MLA].
 
* Follow the instructions here: [http://wsn.cse.wustl.edu/index.php?title=MAC_Layer_Architecture Install MLA].
  
==== Install MATLAB and Simulink ====
+
* Install MATLAB and Simulink
If you already have MATLAB  MATLAB 7.11.0.584 (2010b) or later version, skip this step. Otherwise, follow the  
+
* If you already have MATLAB  MATLAB 7.11.0.584 (2010b) or later version, skip this step. Otherwise, follow the tutorial here: [http://www.mathworks.com/help/install/index.html install MATLAB]
tutorial here: [http://www.mathworks.com/help/install/index.html install MATLAB]
 
  
==== Install Python ====
+
* Install Python
 
If you already have Python 2.7.2 or later version installed, skip this step. Otherwise, follow the manual here: [http://www.python.org/getit/ install Python]
 
If you already have Python 2.7.2 or later version installed, skip this step. Otherwise, follow the manual here: [http://www.python.org/getit/ install Python]
  
==== Installation Check ====
+
<pre>
To test if TinyOS, Python and WCPS were configured correctly, pleas read ahead and do the following example.
+
Below is the installation guide of WCPS v3.0.
 +
For Mac OSX Users who would like to run WCPS on their own computer, please follow first instruction link below for a detailed installation and test procedures.
 +
For OSX/Linux/UNIX/Windows users, please follow the second instruction link below for ruining Dockerized WCPS in a Docker container.
 +
</pre>
  
=== A Simple Example with WCPS===
+
*Install [[WCPS v3.0]] on Mac. [[Run_WCPS_On_Mac_Guide]]
 +
*Run [[WCPS v3.0]] using Docker Container.  [[Run_WCPS_In_Docker_Container_Guide]]
  
==== Simulate a TDMA wireless network ====
+
== Download WCPS ==
 +
* Dockerized WCPSv3: [https://hub.docker.com/r/yehan/wcpsv3/ Docker image], [https://github.com/WU-CPSL/WCPSv3_docker local Matlab folder].
 +
* [https://github.com/WU-CPSL/WCPSv3 Local WCPSv3 installation folder].
 +
* [http://research.engineering.wustl.edu/~boli/downloads/cygwin.zip A complete package of Cygwin with TinyOS 2.1.1, MLA, TOSSIM pre-installed] with a [http://research.engineering.wustl.edu/~boli/downloads/WCPS_Cygwin_Installation_Usage_Tutorial.txt WCPS Cygwin Installation & Usage Tutorial]
 +
* [http://research.engineering.wustl.edu/~boli/downloads/wcpsv0.1.1.zip WCPS v0.1.1 and four extensive case studies] for [http://research.engineering.wustl.edu/~boli/papers/iccps13.pdf ICCPS'13 paper]
  
*  Makefile
+
== Use WCPS ==
"Makefile" takes advantage of the fact that it's not necessary to recompile all the project files that has not been changed.
 
To have the "Makefile" for our project, copy the code below into a txt file and save as "Makefile" without any suffix.
 
  
* TestNetwork.h
+
Wireless network plays a critical role in close-loop wireless control system. Sitting on top of WCPS, simulating
"TestNetwork.h" defines necessary message structures for the wireless communication. Copy the code below into a txt file and save as "TestNetwork.h".
+
a wireless TDMA network is as easy as collecting these NesC files below:
  
* TestNetworkAppC.nc
+
* "Makefile" takes advantage of the fact that it's not necessary to recompile all the files not changed while specifying all necessary libraries.
"TestNetworkAppC.nc" connects claimed application interfaces to interfaces that are defined in the hardware librare. Copy the code below into a txt file and save as "TestNetworkAppC.nc".
+
* "TestNetwork.h" defines necessary message structures for the wireless communication.
 +
* "TestNetworkAppC.nc" connects claimed application interfaces to interfaces that are defined in the hardware library.
 +
* "TestNetworkC.nc" implements send/receive functionality of a wireless node.
 +
* "tossim-call.py" configures TOSSIM network and does packet injection into the Tossim network.[http://research.engineering.wustl.edu/~boli/downloads/TinyosFiles.zip All above necessary files.].
 +
* Re-implemented TOSSIM libraries for TDMA simulation.[http://research.engineering.wustl.edu/~boli/downloads/pure-tdma.zip TDMA components for TOSSIM.].
 +
* Wireless traces: [http://research.engineering.wustl.edu/~boli/downloads/building_noise_n_rssi.zip Traces for 5-sensor wireless network in a building].
 +
 
 +
Put all the above files into the same folder, prompt a terminal (or a Cygwin window), and in the terminal run
 +
<pre>
 +
Make micaz sim
 +
</pre>
  
* TestNetworkC.nc
+
If TinyOS and python is configured correctly, go ahead and run in the terminal:
"TestNetworkC.nc" Implements send/receive functionality of a wireless node. Copy the code below into a txt file and save as "TestNetworkC.nc".
+
<pre>
 +
./tossim-call.py
 +
</pre>
  
* tossim-call.py
+
Having collected aforementioned TinyOS files, a simplified example that uses key networking Interfacing Block and Data Block of WCPS is shown in Fig. 3.
"tossim-call.py" configures TOSSIM network and does packet injection into the Tossim network. Copy the code below into a txt file and save as "tossim-call.py".
+
[[File:Simple_wcps_example.png|500px|thumb|center|Figure 3. A Simple Example that uses Interfacing and Data Block of WCPS. ]]
  
* Wireless traces
+
This examples shows:
  
* Make
+
* How input data in Simulink is injected to TOSSIM network;
 +
* How TOSSIM Interfacing Block runs as a Matlab Embedded function;
 +
* What type of data is output from the Interfacing Block;
 +
* How data usage strategies are applied to the data in the Data Block.
 +
* What type of data is eventually output from the Data Block and provided for future control use.
  
==== A simple Simulink Model ====
+
Source code for the example can be found [http://research.engineering.wustl.edu/~boli/downloads/simple_example.zip here].
 +
To run this integrated example, simply download, unzip the source code, and run Run_delay_data_func.m in Matlab.
  
 +
== WCPS-RT ==
  
To run the network simulation above, we need wireless RSSI (strength of the wireless communication signal) and wireless Noise for
+
[[File:Wcps_architecture_wcps_RT.png|300px|thumb|right|Figure 4. WCPS-RT Architecture]]
Tossim to build Signal to Noise Ratio (SNR) model. Two options to do are:
+
Given the complexity of wireless communication in physical environments, simulators cannot always capture the real-world behavior of WSANs.  Network-in-the-loop simulations have been developed to address the limitation of wireless simulations by incorporating physical wireless networks.
  
1) Use the provided RSSI and noise [http://research.engineering.wustl.edu/~boli/downloads/building_noise_n_rssi.zip traces] for test purposes.
+
To experiment with wireless control over real-world WSANs, we develop wireless cyber-physical simulator real-time (WCPS-RT). WCPS-RT integrates MATLAB/Simulink Desktop Real-time (SLDRT) and a 3-floor WSAN testbed. It captures realistic wireless dynamics that are hard to simulate accurately, and leverages simulation support for controllers and physical plants.
 +
The architecture of WCPS-RT is shown in Fig. 4.  
  
2) Use the code [rssi.zip] to collect the RSSI values and use code [noise.zip] to collect the wireless noise traces.
+
SLDRT is used to simulate the physical part of the WNCS: physical plants, controllers, state observers, and physical disturbance.
 +
In practice, industrial plants usually operate continuously or at very high rates. However, the wireless communication and controller execute at a relatively low rate because of the communication and computation latencies. Therefore, SLDRT modules are operated at different rates in our design.
  
==== Joint Simulation ====
+
The 3-floor WSAN testbed is deployed on the 3rd to 5th floors of Jolley Hall at Washington University in St. Louis. It consists of 70 TelosB motes.
 +
Each mote is equipped with Chipcon CC2420 radio compliant with the IEEE 802.15.4 standard and a TI MSP430 microcontroller.
 +
40 Raspberry Pis with a backplane network are used for the management of the WSAN.
  
==== Example Test ====
+
The interfaces between SLDRT and WSAN are socket connections between the PCs that run SLDRT and the Pis, and serial connections between the Pis and the end nodes. In this way, the end nodes of the sensing and actuation flows  can be any nodes in the testbed.
And you are ready to go for the wireless network setup.
 
  
 +
== WCPS-EC ==
  
Put all the above files into the same folder, prompt a terminal (or a Cygwin window), and:
+
[[File:Wcps_architecture_wcps_EC.png|350px|thumb|right|Figure 5. WCPS-EC Architecture]]
1. In the terminal, Make micaz sim and hit return
 
2. In the terminal  ./tossim-call.py
 
  
== Get Support ==
+
We built a real-time hybrid simulator, wireless cyber-physical simulator edge-computing (WCPS-EC), which integrates (1) Real controllers running on various computation platforms; (2) Real Wi-Fi network and Ethernet, or simulated network using TOSSIM; (3) Simulink Desktop Real-time (SLDRT), which simulates robotic arm in real-time.
*TinyOS and TOSSIM: Bo Li: boli@seas.wustl.edu
 
*Simulink Models: Zhuoxiong Sun: SUN152@purdue.edu
 
  
==References==
+
The architecture of WCPS-EC is shown in Fig. 5. Compared with WCPS-RT, WCPS-EC includes immigrated controllers running on various computation platforms instead of controllers running in MATLAB/Simulink. In addition, WCPS-EC can reflect the impacts of real communication network and computation platform during run-time.
* B. Li, Z. Sun, K. Mechitov, G. Hackmann, C. Lu, S. Dyke, G. Agha and B. Spencer, "Realistic Case Studies of Wireless Structural Control," ACM/IEEE International Conference on Cyber-Physical Systems (ICCPS'13), April 2013.
 
  
*Z. Sun, B. Li, D. Dyke, and C. Lu. "A novel data utilization and control strategy for wireless structural control systems with tdma network," In Proc. ASCE IWCCE 2013.
+
In WCPS-RT, the worst-case end-to-end latency is below one sampling period. Hence the actuation commands are set to have fixed latency of one sampling period. However, in multi-tier control systems, the end-to-end latency can be longer than one sampling period. In addition, we consider a more realistic control system setup with (1) clock-driven sensors that sample the plant outputs periodically every sampling period; (2) an event-driven controller which calculates the actuation commands as soon as the sensor data arrives; and (3) event-driven actuators, which means actuators can respond to updated actuation commands immediately.
  
*Z. Sun, B. Li, S.J. Dyke and C. Lu, "Evaluation of Performances of Structural Control Benchmark Problem with Time Delays from Wireless Sensor Network," Joint Conference of the Engineering Mechanics Institute and ASCE Joint Specialty Conference on Probabilistic Mechanics and Structural Reliability (EMI/PMC'12), June 2012.
+
== Talks ==
 +
*Y. Ma, C. Lu, B. Sinopoli and S. Zeng, [http://cps.cse.wustl.edu/index.php/File:EMSOFT.pdf Exploring Edge Computing for Multi-Tier Industrial Control], ESWEEK 2020 - ACM International Conference on Embedded Software (EMSOFT), September 2020.
 +
* Yehan Ma, [http://cps.cse.wustl.edu/index.php/File:ICII.pdf Efficient Holistic Control over Industrial Wireless Sensor Actuator Networks] , IEEE International Conference on Industrial Internet (ICII'18), Seattle, October 23, 2018.
 +
* Chenyang Lu, [http://www.cse.wustl.edu/~lu/talks/iccps16.pdf Wireless Routing and Control: a Cyber-Physical Case Study] , ACM/IEEE International Conference on Cyber-Physical Systems (ICCPS'16), Vienna, April 11, 2016.
 +
* Chenyang Lu, [http://spectrum.ieee.org/podcast/at-work/test-and-measurement/smart-bridges Smart Bridges - Interview and Podcast on Cyber-Physical Systems for Resilient Bridges], IEEE Spectrum, August 07, 2013.
 +
* Chenyang Lu, [http://www.cse.wustl.edu/~lu/talks/temple-wcn.pdf Real-Time Wireless Control Networks for Cyber-Physical Systems], Computer Science Colloquium, Temple University, April 12, 2013.
 +
* Bo Li, [http://research.engineering.wustl.edu/~boli/papers/WCPS-iccps13.pdf Realistic Case Studies of Wireless Structural Control], ACM/IEEE International Conference on Cyber-Physical Systems (ICCPS'13), Philadelphia, PA, April 11, 2013.
  
* H. Lee, A. Cerpa, and P. Levis. Improving wireless simulation through noise modeling. In IPSN, 2007.
+
==Publication==
 +
*Y. Ma, C. Lu, B. Sinopoli and S. Zeng, [https://www.cse.wustl.edu/~lu/papers/emsoft20.pdf Exploring Edge Computing for Multi-Tier Industrial Control], IEEE Transactions on Computer-Aided Design of Integrated Circuits and Systems (TCAD), Special Issue on ESWEEK 2020 - Proceedings of ACM International Conference on Embedded Software (EMSOFT), September 2020.
 +
*Y. Ma, C. Lu and Y. Wang, [https://www.cse.wustl.edu/~lu/papers/tcps20.pdf Efficient Holistic Control: Self-Awareness across Controllers and Wireless Networks], ACM Transactions on Cyber-Physical Systems, Special Issue on Self-Awareness in Resource Constrained Cyber-Physical Systems, 4(4), Article 41, June 2020.
 +
*Y. Ma and C. Lu, [https://www.cse.wustl.edu/~lu/papers/icii18-holistic-control.pdf Efficient Holistic Control over Industrial Wireless Sensor-Actuator Networks], IEEE International Conference on Industrial Internet (ICII'18), October 2018.
 +
* Y. Ma, D. Gunatilaka, B. Li, H. Gonzalez and C. Lu, [http://www.cse.wustl.edu/~lu/papers/tcps18.pdf Holistic Cyber-Physical Management for Dependable Wireless Control Systems], ACM Transactions on Cyber-Physical Systems, Special Issue on Dependability in Cyber Physical Systems and Applications, 3(1), Article No. 3, August 2018.
 +
* B. Li, Y. Ma, T. Westenbroek, C. Wu, H. Gonzalez, C. Lu. (2016, April). [http://www.cse.wustl.edu/~lu/papers/iccps16.pdf Wireless Routing and Control: a Cyber-Physical Case Study]. ACM/IEEE 7th International Conference on Cyber-Physical Systems (ICCPS'16), April 2016.
 +
* B. Li, L. Nie, C. Wu, H. Gonzalez, C. Lu.[http://research.engineering.wustl.edu/~boli/papers/iccps15_final.pdf Incorporating Emergency Alarms in Reliable Wireless Process Control]. ACM/IEEE 6th International Conference on Cyber-Physical Systems (ICCPS'15), April 2015.
 +
* B. Li, Z. Sun, K. Mechitov, G. Hackmann, C. Lu, S. Dyke, G. Agha and B. Spencer, "[http://research.engineering.wustl.edu/~boli/papers/iccps13.pdf Realistic Case Studies of Wireless Structural Control]," ACM/IEEE International Conference on Cyber-Physical Systems (ICCPS'13), April 2013.
  
* P. Levis, N. Lee, M. Welsh, and D. Culler. Tossim: Accurate and scalable simulation of entire tinyos applications. In Sensys, 2003.
+
== Get Support ==
 +
*WCPS v3.0: Yehan Ma: yehan.ma@wustl.edu

Latest revision as of 07:59, 23 November 2020


Wireless Cyber-Physical Simulator (WCPS) is an open-source simulation environment for wireless control systems. By integrating Simulink and the TOSSIM wireless sensor simulator in a holistic simulation environment, WCPS accurately captures the dynamics of both the physical systems and the wireless sensor-actuator networks used for control. WCPS has been used for realistic case studies of wireless structural control systems for civil infrastructure, studying routing and control of cyber physical system, and incorporating emergency alarms in reliable wireless process control. The broad application of WCPS is to support cyber-physical systems research on large-scale wireless control systems through high-fidelity joint cyber and physical simulations. This site includes the code release, tutorial, and simulation examples for wireless structural control systems.

What's New

WCPS Architecture

Figure 1. WCPS Architecture

In the Fig.1, WCPS simulates the feedback control loop of the control system as follows. Sensor data is generated from plant models such as structures and water tanks. Through a cross-platform function call from Simulink, sensor data is injected to the corresponding wireless sensors in TOSSIM. Following the routes and transmission schedule calculated by the network manager module, TOSSIM simulates the end-to-end wireless communication of the sensor data packets from the sensors to the base station, and then return the packet delay and loss to the Interfacing Block in Simulink through the Python interface. The Packet Collector module extracts packet delivery information(the delay and loss)from the message pool. Sensor data and their loss and delay are provided to the Data Block, which can feed the sensor data to the controller at the right time based on the packet delay (if the packet is not lost). WCPS utilizes basic API (e.g., the dos, UNIX command) of MATLAB to do cross-platform function calls. In TOSSIM, we re-implement a printf method in TinyOS to send simulation results to the Interfacing Block.

User inputs to WCPS includes reference signals of the plants and wireless traces used as input to TOSSIM. The scheduler module calculates transmission schedules. Networking schedule is then deployed into the MAC layer code of wireless nodes and becomes effective after a TinyOS compilation. The TDMA MAC layer in WCPS is developed based on the MAC Layer Architecture (MLA) library and further adapted for TOSSIM under TinyOS 2.1.1. Received Signal Strength Indication( RSSI) and wireless noises traces are collected from real-world environments and provided to the wireless model used by TOSSIM for realistic wireless network simulations. The interfaces between the Simulink model and TOSSIM are encapsulated as two MATLAB embedded functions in Simulink: the Interfacing Block and the Data Block, as is shown in Fig.2. The Interfacing Block extracts delay and loss information from TOSSIM messages, and the Data Block decides what data will be used for discrete control during each sampling period. The federated architecture of WCPS provides great flexibilities to incorporate different structural models and implement alternative scheduling-control approaches.

Figure 2. Simulink Model

Environment Installation

  • Install TinyOS
WCPS is implemented and tested on MacOS X (snowleopard), Windows XP, and Windows 7. 
Current release of WCPS is under  TinyOS 2.1.1, which can be installed following the two methods.
  • Install Mac Layer Architecture(MLA)
The MAC Layer Architecture (MLA) provides a component-based architecture for MAC protocols in wireless sensor networks. MLA extends the Unified Power 
Management Architecture to provide the hardware-independent interfaces required by timing sensitive MAC protocols, and defines platform-independent 
reusable components that implement MAC layer logic on top of them. The MLA architecture can be used to develop a large number of platform-independent 
MAC implementations, with little or no further effort required to adapt these implementations to new hardware platforms. Our current implementation of MLA
is built on top of TinyOS 2.1.1. It currently supports platforms which use the CC2420 radio stack and has been tested on TelosB motes. In addition to providing
interfaces and components for building new MAC layer implementations, MLA includes implementations of five representative MAC layers. Specifically for WCPS, we 
adopt and further change the pure-TDMA MAC protocol for centralized data communication. 
  • Install MATLAB and Simulink
  • If you already have MATLAB MATLAB 7.11.0.584 (2010b) or later version, skip this step. Otherwise, follow the tutorial here: install MATLAB
  • Install Python

If you already have Python 2.7.2 or later version installed, skip this step. Otherwise, follow the manual here: install Python

Below is the installation guide of WCPS v3.0. 
For Mac OSX Users who would like to run WCPS on their own computer, please follow first instruction link below for a detailed installation and test procedures.
For OSX/Linux/UNIX/Windows users, please follow the second instruction link below for ruining Dockerized WCPS in a Docker container.

Download WCPS

Use WCPS

Wireless network plays a critical role in close-loop wireless control system. Sitting on top of WCPS, simulating a wireless TDMA network is as easy as collecting these NesC files below:

  • "Makefile" takes advantage of the fact that it's not necessary to recompile all the files not changed while specifying all necessary libraries.
  • "TestNetwork.h" defines necessary message structures for the wireless communication.
  • "TestNetworkAppC.nc" connects claimed application interfaces to interfaces that are defined in the hardware library.
  • "TestNetworkC.nc" implements send/receive functionality of a wireless node.
  • "tossim-call.py" configures TOSSIM network and does packet injection into the Tossim network.All above necessary files..
  • Re-implemented TOSSIM libraries for TDMA simulation.TDMA components for TOSSIM..
  • Wireless traces: Traces for 5-sensor wireless network in a building.

Put all the above files into the same folder, prompt a terminal (or a Cygwin window), and in the terminal run

 Make micaz sim

If TinyOS and python is configured correctly, go ahead and run in the terminal:

./tossim-call.py

Having collected aforementioned TinyOS files, a simplified example that uses key networking Interfacing Block and Data Block of WCPS is shown in Fig. 3.

Figure 3. A Simple Example that uses Interfacing and Data Block of WCPS.

This examples shows:

  • How input data in Simulink is injected to TOSSIM network;
  • How TOSSIM Interfacing Block runs as a Matlab Embedded function;
  • What type of data is output from the Interfacing Block;
  • How data usage strategies are applied to the data in the Data Block.
  • What type of data is eventually output from the Data Block and provided for future control use.

Source code for the example can be found here. To run this integrated example, simply download, unzip the source code, and run Run_delay_data_func.m in Matlab.

WCPS-RT

Figure 4. WCPS-RT Architecture

Given the complexity of wireless communication in physical environments, simulators cannot always capture the real-world behavior of WSANs. Network-in-the-loop simulations have been developed to address the limitation of wireless simulations by incorporating physical wireless networks.

To experiment with wireless control over real-world WSANs, we develop wireless cyber-physical simulator real-time (WCPS-RT). WCPS-RT integrates MATLAB/Simulink Desktop Real-time (SLDRT) and a 3-floor WSAN testbed. It captures realistic wireless dynamics that are hard to simulate accurately, and leverages simulation support for controllers and physical plants. The architecture of WCPS-RT is shown in Fig. 4.

SLDRT is used to simulate the physical part of the WNCS: physical plants, controllers, state observers, and physical disturbance. In practice, industrial plants usually operate continuously or at very high rates. However, the wireless communication and controller execute at a relatively low rate because of the communication and computation latencies. Therefore, SLDRT modules are operated at different rates in our design.

The 3-floor WSAN testbed is deployed on the 3rd to 5th floors of Jolley Hall at Washington University in St. Louis. It consists of 70 TelosB motes. Each mote is equipped with Chipcon CC2420 radio compliant with the IEEE 802.15.4 standard and a TI MSP430 microcontroller. 40 Raspberry Pis with a backplane network are used for the management of the WSAN.

The interfaces between SLDRT and WSAN are socket connections between the PCs that run SLDRT and the Pis, and serial connections between the Pis and the end nodes. In this way, the end nodes of the sensing and actuation flows can be any nodes in the testbed.

WCPS-EC

Figure 5. WCPS-EC Architecture

We built a real-time hybrid simulator, wireless cyber-physical simulator edge-computing (WCPS-EC), which integrates (1) Real controllers running on various computation platforms; (2) Real Wi-Fi network and Ethernet, or simulated network using TOSSIM; (3) Simulink Desktop Real-time (SLDRT), which simulates robotic arm in real-time.

The architecture of WCPS-EC is shown in Fig. 5. Compared with WCPS-RT, WCPS-EC includes immigrated controllers running on various computation platforms instead of controllers running in MATLAB/Simulink. In addition, WCPS-EC can reflect the impacts of real communication network and computation platform during run-time.

In WCPS-RT, the worst-case end-to-end latency is below one sampling period. Hence the actuation commands are set to have fixed latency of one sampling period. However, in multi-tier control systems, the end-to-end latency can be longer than one sampling period. In addition, we consider a more realistic control system setup with (1) clock-driven sensors that sample the plant outputs periodically every sampling period; (2) an event-driven controller which calculates the actuation commands as soon as the sensor data arrives; and (3) event-driven actuators, which means actuators can respond to updated actuation commands immediately.

Talks

Publication

Get Support

  • WCPS v3.0: Yehan Ma: yehan.ma@wustl.edu