Device Adapter

Typical workflow

The typical development workflow for a device adapter is:

1. Define the Object model — Understand the third-party system and model its objects as AOP EXT Object types with Properties, States, Events, and Operations. Express this in the Module XML.
2. Define the WinGuard mapping — Create the App XML to specify how WinGuard maps Object types to Datapoints and how States and Events correspond to WinGuard alarm states.
3. Choose your SDK — Select C++ or .NET (C#) based on your tech stack. For most teams, the .NET SDK is the fastest path.
4. Set up the Manifest — Define the Module’s identity, version, compatible Skills, and start configuration in the Manifest XML.
5. Implement communication — Connect to the third-party system and synchronize its state into the EXT Object model, using the SDK’s IO framework.
6. Enable Automatic Data Supply — Implement the Object query mechanism so WinGuard can auto-generate Datapoints from the adapter’s Object list.
7. Test in WinGuard — Review how Objects and states appear in WinGuard and iterate.

→ See Module Development, Device Adapter Specification, and SDK overview.