-
Notifications
You must be signed in to change notification settings - Fork 163
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Initial code changes are a bit of a mess, but working OK currently. Will require reconfiguration of all network nodes. Main Changes: 1. Changed addressing to use a better default mask (CCCCCCCCCC) as the manufacturer recommends against the previous mask (F0) since it has only 1 transition, and modified the addressing function. 2. Also changed default address translation: Uses 0xc3,0x3c,0x33,0xce,0x3e,0xe3 to represent the octal numbers 0 through 5 in the address format and pipe numbers. ie: base address (pipe 0) 00 = CC:CC:CC:CC:C3 address 01 = CC:CC:CC:3C:C3 011 = CC:CC:CC:3C:3C:C3 3. New routing protocol using Dynamic Radio ACKs & Network ACK payloads: The old functionality would allow an auto-radio ACK from a routing node, but after that it was unknown whether the payload was delivered. New: Payloads between direct child and parent nodes will continue to use the radio chip built-in retry methods. Routed payloads will follow the following protocol: a: A payload is transmitted from node 011 to node 00. Node 01 must route the payload on behalf of 011. b: Node 011 sends the payload with the NoACK flag set to 01. c: If received, node 01 will forward the payload to 00 and request a radio auto-ACK. d: If the payload was delivered, 01 will forward a manual Network ACK back to 011. e: Node 011 can retry transmission as required if failed, or send another if OK. The above greatly reduces traffic for routed messages, and provides a true indication of success or failure. Testing seems to confirm benefits from the addressing changes, and the multicast routing seems to potentially increase both throughput and potential reliability as well.
- Loading branch information
Showing
6 changed files
with
324 additions
and
133 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.