Yes, the in-memory representation is fixed length (as it the radio packet length). But depending on the uplink command, it might use fewer of those bytes.
An example would be changing some configuration bytes in the Radioduino EEPROM. You can send up to 16 bytes in one packet, but you might only want to change three bytes. The datalength says how many bytes to change, the offset is the address in the EEPROM.
As i said, the packet format (and therefore also the scheduler data structure) is going to change in the future to make it more flexible. But i originally designed this a few years back as my first real Arduino project and my first time using nRF24 radio links. And now half of my home automation is also based on this format, and i have to design and plan an incompatible upgrade to the whole shebang.
In reply to Re^2: Compiling and uploading a crontab to my Radioduino
by cavac
in thread Compiling and uploading a crontab to my Radioduino
by cavac
For: | Use: | ||
& | & | ||
< | < | ||
> | > | ||
[ | [ | ||
] | ] |