Mirror of EspoTek/Labrador@github.com - Drivers and firmware for the Labrador board
Go to file
EspoTek 1c6201a7f3 Plotted and done
Made up the silkscreen layers, put down the stabiliser pin and it's all
ready to be sent off now!
2016-11-23 12:16:40 +11:00
AVR Code PCB update 2016-10-26 10:31:04 +11:00
Desktop Interface Slight change to terminology 2016-11-19 17:29:41 +11:00
Old Matlab Interface Code dump 2016-09-07 16:36:43 +10:00
PCB Plotted and done 2016-11-23 12:16:40 +11:00
build-Labrador-Desktop_Qt_5_7_0_clang_64bit-Debug Mac OS X build running 2016-11-09 16:21:00 +11:00
build-Labrador-Desktop_Qt_5_7_0_clang_64bit-Release Mac OS X build running 2016-11-09 16:21:00 +11:00
README.md Update README.md 2016-11-17 11:40:13 +11:00

README.md

This is the project page for the EspoTek Labrador.

http://espotek.com/labrador https://www.crowdsupply.com/espotek/labrador

#Licence All software files are licenced under GNU GPL v3. https://www.gnu.org/licenses/gpl.html

All hardware files (schematics, PCB) are licenced under Creative Commons 4.0 (CC BY-NC-SA). https://creativecommons.org/licenses/by-nc-sa/4.0/

The intention is to move to a less restrictive licence in future, where commercial hardware derivatives are allowed but the use of the Labrador name or any branding is not. If anyone knows how to implement such a licence, I'm all ears.

#Known bugs. This software is very much pre-beta. Those of you with sharp eyes will notice that there are some bugs. A few biggies include: ~~ - The software is compatible with Windows (x64) only.~~

  • A sample is discarded every frame while the DMA resynchronises.
  • The serial decoder doesn't actually look at every sample individually.

There are planned fixes for these: ~~ - Port libusbK calls to libusb1.~~

  • Time everything from the ADC's input clock. Send an extra "status" byte in isoBuffer[] and time this to a high-priority DMA interrupt to prevent the desktop interface and MCU code falling out of sync. (The "drop 1 sample per frame" was a hacky solution to a synchronisation problem caused by a double buffer's state variable being stored separately, on both PC and MCU. This should have been stomped out 6 months ago).
  • Change all calculations to be bit-based (not byte) and use a mix of divide and modulo to get exact position.

This is in addition to the dozens of small bugs that will have to be slowly squashed before launch.

#Collaboration Mailing list is here and open to all who wish to collaborate on the project: https://groups.google.com/forum/#!forum/labrador-devel

Thanks to all.

~Chris