Installation · Step 3
Components and behaviour
A registered node is ready for its hardware. In this step you tell MIND AIoT what is connected and what it should do — the detail lives in the dashboard, not in a configuration file you have to maintain.
Describe the components
List the components connected to the MIND AIoT Node: sensors, controllers, actuators, relays, modules and any equipment you want to monitor or control. For each one, note how it connects and where its documentation can be found.
Components can connect directly or through a third-party interface, wired or wirelessly — Bluetooth, WiFi, Ethernet, I2C, SPI, USB, analog, Modbus and other digital interfaces supported by Raspberry Pi 5 and embedded Linux.
What it is
Model, manufacturer and what the component measures or does.
How it connects
The interface it uses and any address, channel or mode setting that identifies it.
What it is for
Which room, tank or process it belongs to, and whether it is a control input or an output you switch.
Start with one component. A single sensor is the clearest way to confirm the node, the wiring and the dashboard all work before you add the rest. Add the others one at a time.
A component needs an accessible interface and its documentation. If those exist, agents can add support and verify it on your actual hardware. Physical installation and electrical safety remain your side of the work.
Describe the behaviour
Describe the outcome you want in ordinary language. You do not need to specify the implementation. The platform turns the request into software, tests it and deploys it.
Monitoring
Which readings matter, what counts as normal and what deserves attention.
For example: “Tell me when the rearing room has been more than two degrees above its target for ten minutes.”
Local control
Rules that must hold at the node, close to the equipment.
For example: “Run the exhaust fan when humidity climbs, and stop it when the room is back in range.”
Analytics
Questions you want answered from stored data.
For example: “Compare the production rooms overnight and show which one was outside its range most often.”
Reports
The summary you want, for whom and how often.
For example: “Send a short morning report of anything unusual and the day's power use.”
These are examples of how to phrase a request, not a list of fixed features.
How the work is delivered
Development follows a controlled process on one test node. Nothing is deployed to your operating nodes until you accept it.
Describe the component or feature
Write what should be connected or built in the dashboard. For a component, provide its interface and documentation.
Attach the hardware to one test node
Use one MIND AIoT Node for development, separate from the nodes in production.
Give test permission
Permit the agents to connect, develop, debug and test on that node, and only that node.
Report and review
Agents report the results and the code for your review. A working version is kept so a change can be returned to.
Accept and publish
Accept the result to publish the feature for your system.
Deploy to production
The accepted feature is deployed to the operating nodes, the cloud or both, depending on where it belongs.
After deployment, the feature is deterministic software: it runs the same logic every time. Agents keep monitoring and analysing, but they do not change deployed code in the background.
Custom features follow the discipline of industrial automation: tested changes, dependable local control and a system that is maintained. The minutes promise covers the software integration step, not the physical installation.
Verify the result
- Check the new readings or channel states on the local dashboard at 10.42.0.1. Sensors can take 10–15 minutes to report after a change.
- Confirm the same values appear in the cloud dashboard.
- Test each switched output manually before you leave it in automatic operation. See Dashboards and monitoring.