mirrors
/
Labrador
mirror of https://github.com/EspoTek/Labrador.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
Mirror of EspoTek/Labrador@github.com - Drivers and firmware for the Labrador board
46 Commits 8 Branches 9 Tags 309 MiB
C++ 57.6%
C 32.7%
Makefile 4.5%
Fortran 4.1%
QMake 0.3%
Other 0.8%
Go to file
EspoTek b32392b525 Added more #defines to code 
These #defines are located in desktop_settings.h and allow you to edit
how many samples are discarded per packet.  The idea was to use this to
test the MCU-side code and ensure that it doesn't corrupt a packet per
frame, but this seems to have magically disappeared (???).

I remember queueing USB transfers a long time ago, but can't remember
this having any success.  It's more likely to just be a random clock
skew issue that only appears on some boards - and it's only "fixed" on
the one particular test board I have in hand now.  I think.
 		2016-11-28 10:38:14 +11:00
AVR Code PCB update 2016-10-26 10:31:04 +11:00
Desktop Interface Added more #defines to code 2016-11-28 10:38:14 +11:00
Old Matlab Interface
…
PCB Added more #defines to code 2016-11-28 10:38:14 +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