meta data for this page
  •  

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
Last revisionBoth sides next revision
doc_urecs:software_interface [2023/12/04 09:39] – [Resources] fundoc_urecs:software_interface [2024/01/08 08:45] – [LoRa Message] fun
Line 194: Line 194:
  
 ^ Attribute ^ Description ^ HTTP method ^ ^ Attribute ^ Description ^ HTTP method ^
-|''/lorawan/uplink'' |Schedules uplink packet to the application endpoint defined in the management interface|POST|+|''/lorawan/uplink/{fport}'' |Schedules uplink packet to the application endpoint for the specified fport|POST|
 |''/lorawan/downlink/{fport}'' |Responds with incoming downlink LoRaWAN messages for the specified fport|GET| |''/lorawan/downlink/{fport}'' |Responds with incoming downlink LoRaWAN messages for the specified fport|GET|
  
 Example HTTP Body on GET request: Example HTTP Body on GET request:
  
-<code xml><lorawan fport="...">+<code xml><lorawan>
   <payload>{custom lorawan payload}</payload>   <payload>{custom lorawan payload}</payload>
   <time>{timestamp}</time>   <time>{timestamp}</time>
Line 206: Line 206:
 Example HTTP Body on POST request: Example HTTP Body on POST request:
  
-<code xml><lorawan fport="...">+<code xml><lorawan>
   <payload>{custom lorawan payload}</payload>   <payload>{custom lorawan payload}</payload>
 </lorawan></code> </lorawan></code>
Line 222: Line 222:
 ==== LoRa Message ==== ==== LoRa Message ====
  
-The u.RECS supports to upstream LoRa messages to [[https://www.thethingsnetwork.org/|The Things Network (TTN)]]. The following table gives the LoRa message meaning of version 0.+The u.RECS supports upstream and downstream LoRa messages to [[https://www.thethingsnetwork.org/|The Things Network (TTN)]]. The following table gives the LoRa message meaning of version 0. 
 + 
 +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   | Command (0x01 = Change Power State for Node) | - | Byte |
 +|2   | RCU ID | - | Byte |
 +|3   | Baseboard ID | - | Byte |
 +|4   | Node ID | - | Byte |
 +|5   | Power State (0=Off, 1=On, 2=Soft-off, 3=Standby, 4=Hibernate) | - | 3 Bits |
 +
 +
 +