In trying the Broadcast Manager to send periodic messages with modified data from the 'read the docs', this does not seem very useful. Ref: section 3.6 page 27&27

Rather a thread safe structure / object holding the data (say a python deque) or pointer to the data should be passed with the task creation. The present implementation modifies the data 1x and sends this same data until the task is stopped. Can you setup the implementation to send periodically, but the data is changing constantly, not just on the task instantiation? Suggestions? This limitation does not seem to be the intent of the periodic message task.