In 2017, Hurricane Maria, a category-5 storm, severely impacted Puerto Rico, demolishing homes and communication infrastructure. To address this issue, the ClusterDuck Protocol (CDP) was developed in 2018. It utilizes battery-powered Internet-of-Things devices to reestablish essential communication during emergencies, allowing civilians to request assistance, share their locations, and receive vital information from local governments and responders.
The ClusterDuck Protocol runs on a variety of IoT hardware, including many ESP32 Arduinos.
Here is a list of hardware we use, though there may be many others that work. We recommend the Heltec LoRa ESP32 and the TTGO T-Beam ESP32.
For a simple network you will want to make at least two Ducks. For bigger networks you will need more.
To start developing, you will need PlatformIO on your computer.
Download or git clone the CDP library from GitHub.
Follow the installation instructions here
Please Note: With the Release of the ClusterDuck Protocol Version 4 we have different instructions. If you are looking for older instructions please go here
Connect your board to platform IO
Follow the these updates instructions for loading up a Duck to get one running.
Use the pre-built examples or develop custom Ducks of your own.
Deploy!
Scenario A: You lost the password but have a backup of the project file
If you encounter issues with the PNOZmulti configurator default password, here are some common problems and solutions:
The PNOZmulti Configurator is a graphic tool for configuring and programming units from the Pilz PNOZmulti modular safety system. It allows engineers to create safety programs for configurable small controllers using an intuitive interface, serving as the central hub for developing the logic that protects machinery and personnel in industrial environments. pnozmulti configurator default password
This is a critically important reminder. Strong passwords and well-configured user management mean little if an attacker can simply open a control cabinet, connect a laptop directly to the PNOZmulti base unit via USB, and attempt to bypass authentication. Physical access to the device must be restricted at all times.
The exact model number of the PNOZmulti base unit (e.g., PNOZ m1p, PNOZ m B0, PNOZ m B1). The serial number of the hardware. Scenario A: You lost the password but have
Give operator-level access (Level 2) for troubleshooting, and developer-level access (Level 1) only to authorized safety engineers.
Password protection in the PNOZmulti Configurator is not merely a recommendation; it is a fundamental aspect of safety management. The system implements that provide graduated access, allowing different personnel to interact with the safety program according to their specific responsibilities: The serial number of the hardware
However, confusion arises because the software allows users to password-protect individual project files ( .pnoz files) and hardware configurations (base units). In older versions of the software or on certain base units, a default setting might have been present, but modern best practices have moved away from this.
Securing programmable safety controllers is a critical aspect of industrial automation. The Pilz PNOZmulti series is an industry standard for configurable safety systems, protecting both human operators and expensive machinery. Managing access permissions via passwords ensures that only authorized personnel can alter safety configurations.