Duty cycle limits

[faragher]

I've been going through the datasheets recently, and a thought occurs to me: I have a vague recollection of the US limiting duty cycle on data transmission over certain bands. As a practical matter, this doesn't make much difference at the scales most of use use these on, and I don't remember the exact bands and modes affected.

However, I think a duty cycle option is useful. More research is required to figure out the specifics, but I think if we have a duty cycle as a fraction (defaults to one) with a window (default to, say, 60 seconds) and a computed length of message or simple timer, we can leave the actual configuration and compliance up to the end user. I would propose it be part of the Reticulum stack instead of the RNodes, as it is application specific. Alternatively, this could be handled by each system, such as Nomadnet or Sideband, but it's a feature that would be required for widespread compliance and acceptance.

Is this something you think should be implemented?

[markqvist]

It's been on my todo list for way too long. As you say, the amount of traffic is so low with the current functionalities that it is more or less self-enforcing. That being said, I think it should be an option, and I'm going to add it at some point, when I have a bit of time for it ;)