View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0000078 | LCD Display | Connecting | public | 2008-08-18 14:19 | 2008-08-27 22:43 |
| Reporter | CoZZm0 | Assigned To | |||
| Priority | normal | Severity | tweak | Reproducibility | always |
| Status | closed | Resolution | not fixable | ||
| Product Version | 2.00 | ||||
| Summary | 0000078: Max Values not updated while viewing | ||||
| Description | While viewing the maximum values menu, they are not updated (or don't seem to be unless its a very long refresh time). This could be "as designed" (i would assume) but would be nice if they were updated once every 5 seconds or so. Especially useful when tacking maximum speed, maximum rpm or max temp on race track while driving without having to toggle to that menu manually. | ||||
| Tags | No tags attached. | ||||
|
|
this is how the display is designed - whenever you are not on the 'main display' page (either trip meter or sensors) then it is not reading from the ECU. so whenever you are in menus etc, trip meter stats, sensors etc arent being read. this is because you have a lot of other accesses to consult (such as error codes, time trials, etc), and its too difficult in the current setup (think single threadded/sequential code execution) to continually process consult data whilst on other 'blocking' code like waiting for a button to be pressed or similar is occuring. not that it would be impossible to do, but likely to generate more issues than the small advantage it would give. if you're interested in knowing in realtime whether a value is being hit or similar, then perhaps audible alerts (when theyre implemented) may help...e.g. if you want to know when you hit 7000rpm or 100C water temp or 110km/h or whatever. these would then also only be monitored whilst on main display |
