Add buffer output
IngoKaiser opened this issue · comments
Its already implemented in our node-red module. Please add method ("SetBufferSize"?!) to set amount of data to be buffered before send to start callback - e.g. 48k would sent buffered data array every second. If defined number is smaller than received chunk - it would be ignored.
Added SetBurstSize API call according to requirements
PR: #51
Not tested, need environment to test
Tested on RPi with hardware
Failed to build the driver on Debian-9 with default settings because of errors during compilation (too old compiler?)
Going to build it on latest Ubuntu...
@iluxa what happens when no burstSize is set?
Expected behavior would be 48k samples per second
what happens when no burstSize is set?
if SetBurstSize not called, it is default behavior - call ReadCallback as soon as possible
yes, the easiest way to build the driver - from docker,
instructions are in driver/Readme.md
I've tested Data Logging example: it gave 4x12000 samples in a timespan less than a second (normally 0.2sec, but sometimes up to 0.7 sec).
I found some minor issues in the example itself (not in the driver) in my opinion:
- if config.json is missing the application is terminated with a JSON exception
- the application is always finished with "a terminate called without an active exception"
(doesn't wait for threads are finished?)
I think it would be good to install some debugging enviroment on TimeswipeOS to start driver's debugging section remotly like it is done for SAM... (gdbserver and so on).
Then the driver could be futher inspected with a debugger.
- if config.json is missing the application is terminated with a JSON exception
- the application is always finished with "a terminate called without an active exception"
(doesn't wait for threads are finished?)
#56 created