1. A Cross-Device Testing and Report System for Large-Scale Real-Time Wireless Networks
Tao Gong, Huayi Ji, Tianyu Zhang, Chuancai Gu, Song Han, Xiaobo Shanron Hu, Mark Nixon
University of Connecticut
University of Notre Dame

2. How to analyze a real-time wireless network?
Using a sniffer
Less programming details
Debugging
Only on one node
Node loses sync when debugging
Logging
Good for offline analysis
Online (serial port) can be slow
No sync between nodes
The question starts from here, how to analyze a real-time wireless network.
Of course, first we can use a sniffer to capture the packet over-the-air. However, there will be no programming details in the packet. You can only guess but not knowing what is exactly happening inside the processor.
In order to know the programming details, we can also use traditional debugging tools. However, we can only do one at a time. Also we are dealing with real-time wireless network. A node immediately loses synchronization after we “halt” the CPU to examine the status.
Another way is to do logging, however logging can be slow if we do it over a serial port. And the log can only be analyzed offline.

3. Our approach: Test cases for “Distributed Dynamic Packet Scheduling”
Our approach is like this. First, we have developed a tool to deploy a test case to the testbed. The test cases are from another paper we are going to present tomorrow, the Distributed Dynamic Packet Scheduling. We first deploy the network to the testbed and make it run, which is the 8 CC2538 devices here. Then we use log interfaces to attach to some of the devices and retrieve log in the run time. We use J-Links here. The information is extracted in the runtime and is transparent to the running program, and is way faster than Serial port. The log from multiple devices then send to the analyzer asynchronously, and to be parsed and combined in time series. The correctness of the running status is then get evaluated and a user friendly report is generated to be examined.
Test cases for
“Distributed Dynamic Packet Scheduling”

4. Welcome to our demo and presentation