Ticket #29 (closed development: fixed)
Fix MATLAB's low 15ms-timing accuracy on Windows
|Reported by:||atorf||Owned by:|
On Windows systems, all MATLAB versions up to the current release 2009a show an inaccuracy / poor resolution with timing (functions clock, etime, tic, toc, pause): Histogram tests show that timing is binned to 15ms steps, a finer timing / more accurate resolution is not possible.
Either wait for The MathWorks? to fix this (then this problem is eliminated), or implement a workaround using Windows High Accuracy Timers API (or just use GetTickCount? Kernel-API function). An already implemented MATLAB-function can be found here: http://www.mathworks.com/matlabcentral/fileexchange/16534
Make sure this works on 64bit as well (create mex-file), and replace critical functions inside the COM-layer with this custom function (introduce a new wrapper, which decides between Linux (use etime, clock as usual) and Windows (use HAT)).
This would improve Bluetooth-Performance and be a "nice feature" in general…