But will not respond until device has been connected at least once! On
a side note I found out how silly the saveState/loadState method in
genericUsbDriver was. It was always a better idea to just "poke" the
signals to ensure that it is reset in the same way that would happen
from GUI interactions.
Former-commit-id: 57c841f1d7
Swapped an append to a replace with an ADT designed to return fast
pointers to char[] blocks.
Worked out that the one-corrupt-sample-per-packet bug was definitely not
fixed. I must have been looking at a 1kHz wave before.
Former-commit-id: d3054d9707
May have accidentally broken Linux (untested, I wasn’t being shotgunny
but equally wasn’t being super careful). Seems to randomly fail on
launch. Probably a race condition on the mutex?
Former-commit-id: b7e0035896
.pro file now works with both Windows and Linux. Have fixed up some
header names to have capital letters. Windows doesn't mind, but Linux
cracks the shits. Hop to have it runnning in Ubuntu ASAP.
Former-commit-id: 10a09fdf50
Sadly, it only functions about half a dozen times before failing. I
suspect something isn't being released; perhaps another call needs to be
made to the .dll?
Former-commit-id: fb964d0f71
Some CSV export features implemented - dump everything (in a stream -
750ksps!!) or just dump what's visible in screen. Stream doesn't dump
actual voltage readings but raw sample data.
Board software has been updated to fix DMAnot transmitting the correct
data for signal gen CH1 in modes 4 and 5
Former-commit-id: 7f40f04ef9
Two new ways of changing range:
- Press Z to snap to cursors, or M to open a dialog and enter manually.
- The frequency boxes now scroll in a more sane way - round down to the
nearest multiple of 10, then divide by 10 to find out the increment.
For example, at 2kHz, the next value will be 2.1kHz (2000 + 1000/10)
rather than 2.001Hz (2000 + 1).
Former-commit-id: 80b928cc27
EspoTek