Anonymous | Login | Signup for a new account | 2021-01-26 15:46 UTC | ![]() |
Main | My View | View Issues | Roadmap | Repositories |
View Issue Details [ Jump to Notes ] | [ Print ] | ||||||||||
ID | Project | Category | View Status | Date Submitted | Last Update | ||||||
0000558 | Firmware | Serial Comms | public | 2012-04-04 17:46 | 2012-04-05 00:25 | ||||||
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 | 0.2.X | Fixed in Version | |||||||||
Summary | 0000558: Add Live-Only Control Structure + Related Simple Features | ||||||||||
Description | Add a block in memory with settable variables and a control variable with settable flags that is forgotten on each reset. Use this to allow live control of things that shouldn't be set permanently such as fixed timing and value overrides on some sensor inputs and code outputs, etc. This will avoid the situation that has seen some people with destroyed engines after forgetting to go back to normal running mode post performing some testing by fixing some value or other. | ||||||||||
Tags | No tags attached. | ||||||||||
FirmwareVersion | |||||||||||
Issue Type | New Feature | ||||||||||
Risk of Breakage | medium | ||||||||||
Attached Files | |||||||||||
![]() |
|||||||||||
|
![]() |
|
![]() Fred (administrator) 2012-04-04 17:48 |
The chances are that this will end up in 0.2.0 to allow fixed timing setting while configuring the engine. |
Copyright © 2000 - 2011 MantisBT Group |