meta data for this page
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
doc_urecs:software_interface [2023/12/04 09:39] – [Resources] fun | doc_urecs:software_interface [2024/01/10 17:18] (current) – [LoRa Message] fun | ||
---|---|---|---|
Line 194: | Line 194: | ||
^ Attribute ^ Description ^ HTTP method ^ | ^ Attribute ^ Description ^ HTTP method ^ | ||
- | |''/ | + | |''/ |
|''/ | |''/ | ||
Example HTTP Body on GET request: | Example HTTP Body on GET request: | ||
- | <code xml>< | + | <code xml>< |
< | < | ||
< | < | ||
Line 206: | Line 206: | ||
Example HTTP Body on POST request: | Example HTTP Body on POST request: | ||
- | <code xml>< | + | <code xml>< |
< | < | ||
</ | </ | ||
Line 222: | Line 222: | ||
==== LoRa Message ==== | ==== LoRa Message ==== | ||
- | The u.RECS supports | + | The u.RECS supports upstream |
+ | |||
+ | All system related management communication (excluding the REST API) uses **FPort 1**. | ||
+ | |||
+ | Upstream message payload layout: | ||
^ Byte(s) ^ Description ^ Unit ^ Data type ^ | ^ Byte(s) ^ Description ^ Unit ^ Data type ^ | ||
Line 242: | Line 246: | ||
|26 | PoE Status Port 1 | - (see below) | Byte | | |26 | PoE Status Port 1 | - (see below) | Byte | | ||
|27 | PoE Status Port 2 | - (see below) | Byte | | |27 | PoE Status Port 2 | - (see below) | Byte | | ||
+ | |||
+ | The u.RECS supports basic control functions over LoRaWAN. | ||
+ | Downstream message payloads: | ||
+ | |||
+ | **Change power state for node:** | ||
+ | ^ Byte(s) ^ Description ^ Unit ^ Data type ^ | ||
+ | |0 | Lora Message-Version | - | Byte | | ||
+ | |1 | Node ID | - | Byte | | ||
+ | |2 | LoRa Command (0x01 = ON, 0x02 = OFF, 0x03 = RESET) | - | Byte | | ||
+ | |||
+ | |||
+ | |||