Difference between revisions of "Data monitor"
From DIDEAS Wiki
m (Created page with "=purpose= The purpose of the 'data monitor' is to the permit the reading and modification of 'global variables' on an active platform with minimum overhead to the system. =pro...") |
(No difference)
|
Revision as of 15:38, 6 November 2010
purpose
The purpose of the 'data monitor' is to the permit the reading and modification of 'global variables' on an active platform with minimum overhead to the system.
proposal
- Create a data structure 'monitored_locations' that contain a list of addresses, and object sizes
- Create a empty telemetery message packet large enough to store data from 'monitored_locations'
- A function runs over entries in 'monitored_locations'. and copies the referenced data into a telemetry message packet.
issues
- The proposed system does not lock data structures. Depending on the application layer implementation, data in a state of transition may be read/written.
- Reads of data structures could accrue at the end of the statemachine.
- Writes to data structures would be queued, and implemented before the statemachine.
- Header files on the PC could be inconsistant with the memory map on the robot
