| Anonymous | Login | Signup for a new account | 2019-06-25 14:14 UTC |  |
| Main | My View | View Issues | Roadmap | Repositories |
| View Issue Details [ Jump to Notes ] | [ Print ] | ||||||||||
| ID | Project | Category | View Status | Date Submitted | Last Update | ||||||
| 0000279 | Firmware | Serial Comms | public | 2011-09-26 18:05 | 2011-12-06 00:13 | ||||||
| Reporter | Fred | ||||||||||
| Assigned To | Fred | ||||||||||
| Priority | normal | Severity | feature | Reproducibility | N/A | ||||||
| Status | assigned | Resolution | open | ||||||||
| Platform | OS | OS Version | |||||||||
| Product Version | 0.2.0-SNAPSHOT | ||||||||||
| Target Version | Future | Fixed in Version | |||||||||
| Summary | 0000279: Add Mechanism To Periodically Send Comms Error Summaries | ||||||||||
| Description | Currently you need custom logging to dig into a comms issue. The firmware should be proactive about this. One option would be to send a copy every 1 second to 10 minutes or so, if non-zero sum of bytes. Another would be to send a copy every 1 second to 10 seconds IF the previous checksum was different. Perhaps a combination of both. Possibly later apply this technique to other internal error types. Add lib test packet for retrieving same data too, therefore this depends upon issue 0000128 | ||||||||||
| Tags | No tags attached. | ||||||||||
| FirmwareVersion | |||||||||||
| Issue Type | New Feature | ||||||||||
| Risk of Breakage | low | ||||||||||
| Attached Files | |||||||||||
 Relationships |
|
 Relationships |
|
Notes |
|
| There are no notes attached to this issue. |
|
Notes |
| Copyright © 2000 - 2011 MantisBT Group |
 |