View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0000039 | Software | Connection | public | 2007-08-19 17:31 | 2007-08-19 23:32 |
| Reporter | Peter | Assigned To | Peter | ||
| Priority | normal | Severity | minor | Reproducibility | sometimes |
| Status | closed | Resolution | fixed | ||
| Product Version | 1.3.3 | ||||
| Fixed in Version | 1.3.3 | ||||
| Summary | 0000039: Put option in for data flush wait time (this might help people with problems with sensors not showing up). | ||||
| Description | the time that ecutalk waits after issuing a stop command can sometimes be too short/long depending on laptop/pocket pc etc. being able to change this option can mean laptops and similar can set to a lower value (and hence have quicker startup times) and people having issues with sensors not showing up can try higher values. also look into when and how often flush is used. maybe this has something to do with it | ||||
| Tags | No tags attached. | ||||
|
|
now an option so user can change flush wait time. this is time after "stop streaming data" command sent to ecu before it checks for reply. if it checks too early, then the response might not have been received (and therefore missed). if it checks too late, im not sure if this matters, but it will make everything slower (especially startup detection of gauges). default is 100ms (same as beta3) |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2007-08-19 17:31 | Peter | New Issue | |
| 2007-08-19 17:31 | Peter | Status | new => assigned |
| 2007-08-19 17:31 | Peter | Assigned To | => Peter |
| 2007-08-19 23:32 | Peter | Note Added: 0000019 | |
| 2007-08-19 23:32 | Peter | Status | assigned => closed |
| 2007-08-19 23:32 | Peter | Resolution | open => fixed |
| 2007-08-19 23:32 | Peter | Fixed in Version | => 1.3.3 |
