- Jelina overview
- EMS Builder
- Reference manual
Device Coordination Configuration
This page configures sharing using the current model in which the local device sends to a target device. Prepare two mutually reachable Edge-EMS Builder devices. Sender A and receiver B below denote generic roles.
1. Maintain device information
Section titled “1. Maintain device information”Maintain unique deviceCode, deviceIp, and local flags in the corresponding device lists. Each Edge-EMS Builder identifies only one local device. Update device information when network addresses change while keeping device codes stable.
2. Select what to send
Section titled “2. Select what to send”On A, create a sharing configuration with a unique shareConfigCode, name, sharing CRON schedule, and local point list. Create multiple configurations by purpose and set their intervals separately.
Names, aliases, and units are synchronized with shared data. Points must exist first. UDE templates can generate sharing configurations as counts of similar devices change.
3. Create a target and bind configurations
Section titled “3. Create a target and bind configurations”On A, create a shared target with targetDeviceCode set to B, then bind one or more sharing configurations. The current model has no slave-device list and does not require adding the local device to a shared space.
Each target corresponds to one receiver. To also send to C, add a target pointing to C. For B to send to A, configure a reverse target on B.
4. Verify at the receiver
Section titled “4. Verify at the receiver”Inspect shared data on B. Confirm that the source device code is A, dataKey is correct, names and units are complete, and values keep updating. Check connection and communication status rather than merely whether a value was ever received.
Common APIs
Section titled “Common APIs”| Operation | API |
|---|---|
| Device list | GET /device-info/list |
| Sharing configuration list | GET /share-config/list |
| Shared target list / details | GET /share-target/list, /detail |
| Create target | POST /share-target/add |
| Add configuration binding | POST /share-target/add/config |
| Replace all bindings | POST /share-target/update/configs |
| Delete one binding | POST /share-target/delete/config |
Full replacement removes old bindings absent from the new list. Read back the complete configuration before execution. Modify template-managed bindings through UDE templates and reconcile them.
See the shared target reference for target fields and Device coordination for shared calculations and control.