A high level software interface
DINGO-IoT provides you with a high level open platform to develop your own IoT APPs or other software.
Only a lack of imagination can stop you. And if it does, we are here to help!
A high level software interface
DINGO-IoT provides you with a high level open platform to develop your own IoT APPs or other software.
Only a lack of imagination can stop you. And if it does, we are here to help!
The GO-IoT software stack is intended to give developers high-level programming power for their IoT applications. There's no need to bother with programming bits and bytes at sensor/device level. We've already done it for them by implementing the DINGO Peripheral Manager and BACnet/IoT.
Please read about the DINGO software stack here..., before continuing.
The DINGO software stack is all developed in C++ and POCO. Full support is included for the KDevelop RAD environment. We chose this environment to get the smallest footprint and fastest code possible, without losing development-speed.
However developers may choose any other programming environment they want. This is because DINGO software stack is provided with a REST web-service interface (based on BACnet/WS rules), giving the developer total freedom to use whichever dev. environment best suits them.
The BACnet IoT server and client software stack was open-sourced in 2017.
The DINGO software stack provides full Restful Web Services based on BACnet/WS rules, not only for the BACnet part, but also for the APP-manager, Peripheral Manager and other modules of the software stack.
Key features are:
DINGO software stack has a powerful environment to manage APPs. APP parameters can be fully detailed in the DINGO SQLite database. By defining the parameters correctly, those can be viewed and set in DINGO MANAGER or "your manager".
How and when APPs are executed is also configurable via BACnet Scheduling objects.
In addition APPs can be accessed from BACnet via BACnet Program objects. Allowing other BACnet devices from any vendor to communicate easily with the APP.
Additionally APPs can be configured to be a 'source' to BACnet objects. For example an APP that retrieves weather forcast data from the Internet, can be a source to Analog Input Temperature and Analog Input Rain BACnet objects.
We chose BACnet as we couldn't find any other standard that's as well and fully defined in terms of device-to-device communication, both at the Application-layer AND the Network-layer. Furthermore BACnet is an ongoing definition and is widely accepted by the industry.
DINGO BACnet/IOT is a brand new implementation of the BACnet standard. The BACnet standard is huge. Our implementation today only uses a small part of it. However we continue to add BACnet objects and services by definition as needed. To speed up the process, we've decided to open source our BACnet/IoT so third parties can contribute to the development or add their own proprietary objects and services.
A community is being built around this development.
Read more about BACnet/IoT here...