You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+2Lines changed: 2 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -46,6 +46,8 @@ The blueprint is an entity containing all aspects pertaining to device integrati
46
46
-[`manifest.yml`](https://developers.enapter.com/docs/reference) describes your device interfaces (telemetry it sends, commands it executes, alerts it raises);
47
47
-`firmware.lua` implements these interfaces for the specific piece of hardware using the [Lua](https://www.lua.org) programming language and high-level platform APIs.
48
48
49
+
Blueprints can implement [profiles](https://github.com/Enapter/profiles) β standardized interfaces that define common telemetry, properties, and commands for specific device categories (e.g. battery inverters, PV inverters). When a blueprint declares a profile in its `implements` section, it must provide all telemetry defined by that profile with matching types and enum values.
50
+
49
51
There are two types of hardware that can run your blueprint:
50
52
51
53
- a physical [Enapter UCM](https://handbook.enapter.com/modules/modules.html) that implements communication through [RS-485](https://handbook.enapter.com/modules/ENP-RS485/ENP-RS485.html), [CAN](https://handbook.enapter.com/modules/ENP-CAN/ENP-CAN.html), your own hardware based on [UCM Kit](https://go.enapter.com/ucmkit-enpkit) and other standards,
0 commit comments