user:kluong:feature_idea_-_two_way_communication

Differences

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

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
user:kluong:feature_idea_-_two_way_communication [2021/03/25 17:37]
kluong
user:kluong:feature_idea_-_two_way_communication [2021/09/19 21:59] (current)
Line 1: Line 1:
 ====== Feature Idea - Two way communication ====== ====== Feature Idea - Two way communication ======
 +
 +One thing that might be useful is two way communication between the coordinator and end devices. In a serial console on the server or a command line program, you should be able to send a command to and end device and get a response. Here's how it could work:
 +
 +<​code>​
 +python weatherbox-console.py
 +
 +Enter your command here: ACKREQ 8888
 +...
 +Reply from node 8888: 
 +OK
 +
 +Enter your command here: ACKREQ 9999
 +...
 +Reply from node 9999 timeout.
 +
 +Enter your command here:
 +
 +</​code>​
 +
 +Note this is a communication layer that exists on top of the zigbee/xbee layer. ​
  
 **why it might be useful** **why it might be useful**
  
-One thing that might be useful is two way communication between the coordinator and end devices. ​It might be useful for a couple of things like:+It might be useful for a couple of things like:
  
   * Checking that the firmware is in a good state (if it responds to a request from the coordinator,​ it's probably okay)   * Checking that the firmware is in a good state (if it responds to a request from the coordinator,​ it's probably okay)
  • user/kluong/feature_idea_-_two_way_communication.1616693855.txt.gz
  • Last modified: 2021/09/19 21:59
  • (external edit)