Newly Optimized RF24Network Layer v1.0.7
2014-2015 - Optimized RF24 Network Layer for NRF24L01 radios
Header which is sent with each message. More...
|Default constructor. More...|
|RF24NetworkHeader (uint16_t _to, unsigned char _type=0)|
|Send constructor. More...|
|const char *||toString (void) const|
|Create debugging string. More...|
|Logical address where the message was generated. More...|
|Logical address where the message is going. More...|
|Sequential message ID, incremented every time a new frame is constructed. More...|
|Message Types: User message types 1 through 64 will NOT be acknowledged by the network, while message types 65 through 127 will receive a network ACK. More...|
|During fragmentation, it carries the fragment_id, and on the last fragment it carries the header_type. More...|
|static uint16_t||next_id = 1|
|The message ID of the next message to be sent (unused) More...|
Header which is sent with each message.
The frame put over the air consists of this header and a message
Headers are addressed to the appropriate node, and the network forwards them on to their final destination.
Simply constructs a blank header
Fragmentation is enabled by default for all devices except ATTiny
Configure fragmentation and max payload size in RF24Network_config.h
Use this constructor to create a header and then send a message
|_to||The Octal format, logical node address where the message is going|
|_type||The type of message which follows. Only 0-127 are allowed for user messages. Types 1-64 will not receive a network acknowledgement.|
|const char * RF24NetworkHeader::toString||(||void||)||const|
Create debugging string.
Useful for debugging. Dumps all members into a single string, using internal static memory. This memory will get overridden next time you call the method.
Logical address where the message was generated.
Logical address where the message is going.
Sequential message ID, incremented every time a new frame is constructed.
|unsigned char RF24NetworkHeader::type|
Message Types: User message types 1 through 64 will NOT be acknowledged by the network, while message types 65 through 127 will receive a network ACK.
System message types 192 through 255 will NOT be acknowledged by the network. Message types 128 through 192 will receive a network ACK.
Type of the packet. 0-127 are user-defined types, 128-255 are reserved for system
|unsigned char RF24NetworkHeader::reserved|
During fragmentation, it carries the fragment_id, and on the last fragment it carries the header_type.
*Reserved for system use*
The message ID of the next message to be sent (unused)