Whitefield provides a simulation environment for sensor networks by combining realistic PHY/MAC layer simulation with the native mode use of popular IoT stacks/OSes such as Contiki/RIOT/OpenThread/Zephyr/FreeRTOS/OT-RTOS. Thus one can use existing stack implementation as is and test it on top of realistic RF simulation.
Whitefield uses PHY/MAC layer provided by popular simulators (such as NS3-lrwpan/PLC) and loosely couples it with the constrained network stacks supported by popular IoT OSes, thus providing the best of both worlds. It provides common visualization and OAM tools (logs, pcap, shell) which simplifies monitoring and troubleshooting.
Typical use-cases of Whitefield:
Terminology:
Airline: Airline refers to PHY/MAC/RDC implementation provided by third-party simulators such as NS3/Castalia-Omnet++. Provides configuration management and OAM tools which works across any third-party simulators. It interfaces with Commline to send/recv messages to/from Stackline.
Commline: Message queue and corresponding interfaces which decouples Airline and Stackline. All the messages, be it the network payloads or OAM messages are transported using Commline.
Stackline: 6lowpan/Network layer and above protocol stack provided by third-party IoT OSes such as Contiki/RIOT. A new platform is added in such OSes to interface with Whitefield. The protocol stack with application will be used as-is from these OSes.
Execute Instructions:
$ cd whitefield
#Start Whitefield
$ ./invoke_whitefield.sh config/wf.cfg
#Monitor whitefield status
$ ./scripts/monitor.sh
#View live network toplogy open http://localhost:8080/ in a browser
$ ./canvas/canvas.py
#Whitefield shell
$ ./scripts/wfshell help
#Stop whitefield
$ ./scripts/wfshell stop_whitefield