Commit Graph

578 Commits

Author SHA1 Message Date
EspoTek 440cbed9a7 Added files for Android deployment. Added references to PCB on layer "Dwgs.User"
Former-commit-id: a9e38c8115
2017-02-18 13:38:18 +11:00
EspoTek 78454dc96d Fixed little PCB glitch
Pre-compiled stuff all changed due to move from Qt 5.7.0 to Qt 5.7.1


Former-commit-id: 3ddc37a4b5
2017-02-18 11:43:29 +11:00
EspoTek d98e82f99a Removed black magic. Always a bad idea.
Former-commit-id: 67000bc7de
2017-02-12 15:35:27 +11:00
EspoTek 0b08acb312 Changed Framerate to 30FPS; fixed autogain bug; removed QCP2 crashes
30FPS gives 2% CPU usage on a 2600k@4.8; ~10% of one core.
QCPP2 is not enabled since performance is kak on Qt 5.7.


Former-commit-id: bfb2935812
2017-02-09 15:33:50 +11:00
EspoTek 3a4f5de038 Starting up driver doesn't block GUI execution (Windows only).
Bonus: "Device Disconnected" prompt works again!

Former-commit-id: f8d3ae9bc5
2017-02-09 13:24:30 +11:00
EspoTek 07255f1e8c Added skeleton for QCustomPlot 2
Former-commit-id: 97f8768c5e
2017-02-08 14:04:27 +11:00
EspoTek 68f5751d2b Moved to unix. Tested on Mac, anyway. Also fixed bug on Windows + CR/LF issues.
Former-commit-id: e1f0ced8b4
2017-02-08 13:30:05 +11:00
EspoTek b6f8209b12 About to start work on Unix port.
Former-commit-id: fa59da633e
2017-02-08 10:52:24 +11:00
EspoTek b28bad3bb7 Quick PCB finalisationsion, lowered priority of tiny_dma_set_mode_x; looks like it's stopped the problem of "too much switching drops packet
Former-commit-id: c5e94e6812
2017-02-07 10:10:36 +11:00
EspoTek f49013dd66 Removed delays from winUsbDriver's Iso stack - other half of software bug fixed?
No longer seems to show that "every packet is corrupt" error.  I suspect
it was caused by the "filling the transfer contents" loop in
usbIsoInit() taking place during two 1ms periods.  This would, in
theory, cause it to skip over 1ms of data every ISO_PACKETS_PER_CTX *
NUM_FUTURE_CTX frames.


Former-commit-id: 66a8b96e10
2017-02-05 12:05:03 +11:00
EspoTek cdf9da1562 Merged trying-calibration into master
Very, very hackily...


Former-commit-id: f929191825
2017-02-03 17:34:54 +11:00
EspoTek afaf8ba16d Commit before revert
dead end


Former-commit-id: 9e2ea03c6c
2017-01-05 09:04:44 +11:00
EspoTek 7789a3cf62 there are still files??
Former-commit-id: 667452acb4
2016-12-28 10:18:45 +11:00
EspoTek d4a90aa24a i was playing around and just want to commit
Former-commit-id: d46528726e
2016-12-28 10:17:46 +11:00
EspoTek 4dd657a164 CH2 no longer drifting
But is corrupting.


Former-commit-id: b60b82fb6c
2016-12-22 15:23:45 +11:00
EspoTek 45d6b89c0a Fixed Logic Analyzer CH2
Former-commit-id: 46d113259a
2016-12-20 10:52:21 +11:00
EspoTek fefba14eb1 And mode 7 up
Bugs found recently:
- Trigger doesn't work on negative voltages (at least in MM mode).
- Double Sample Rate button won't de-trigger when CH1 scope is disabled.


Former-commit-id: 56f329a016
2016-12-18 15:15:57 +11:00
EspoTek 33f052ccf7 Mode 6 Up
The error where every packet can become corrupt when you get a "bad
launch" seems more pronounced here.  But it still succeeds enough times
to show that correct synchronisation could fix it.


Former-commit-id: 85b86af1ff
2016-12-18 14:56:54 +11:00
EspoTek bf2697d80d Mode 4 Up
Although Logic Analyzer CH2 is faulty.  Looks like it's been in the code
for months, though.  Add that to the list of things to fix.


Former-commit-id: f76e8eb3a7
2016-12-18 14:44:57 +11:00
EspoTek c01b24e661 Mode 3 Up
And found the bug from before; or at least the trigger.  It seems to
only occur when the rear PCI USB port is used.  Front hub or rear USB2
ports don't show issues at all.


Former-commit-id: 653891ca63
2016-12-18 13:57:52 +11:00
EspoTek 25a2ab2a41 Committ before revert
Former-commit-id: 7fd9074207
2016-12-16 17:19:33 +11:00
EspoTek 282a9a394d Mode 2 Up.
And it looks like the old glitch has crept back in?  Was it not fixed
all along?


Former-commit-id: 536ba0ea4c
2016-12-16 15:56:53 +11:00
EspoTek 275394fc36 GUI responsive when device disconnected
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
2016-12-16 15:11:47 +11:00
EspoTek 9db4972573 Mode 1 Up
Mode 1 moved to the new system.  Same notes as mode 0.


Former-commit-id: 3d5c2b0b0a
2016-12-16 14:23:06 +11:00
EspoTek 02d4ba10da One packet per sample glitch gone!!!
From the looks of things, anyway.
This fix came with a cost:
- All modes apart from 0 are broken.
- Randomly, the DMA write and USB read may access the same half of
isoBuf.  This is determined on boot, and doesn't seem to desynchronise
and resynchronise over time.

The good news is that both of these have a fix.  Give it another day of
coding...


Former-commit-id: 23741ceecb
2016-12-15 13:52:44 +11:00
EspoTek 68453fe220 Triple endpoints working in SW now
Added triple endpoint support for the Desktop interface.
Should be possible to fix the one-packet-per-sample glitch easily, now.
Even if it isn't, the device now only needs to reserve 768 bytes/frame,
not 1023!!!!


Former-commit-id: 5769288a11
2016-12-15 09:52:43 +11:00
EspoTek b5ff947309 3 Iso Endpoints
Have moved from one big (1023 byte) iso endpoint to 3x 256 byte ones.
This will fix the error where Labrador is picky about which port it's
connected to, and *should* fix the one-sample-per-packet error.


Former-commit-id: 880303ed09
2016-12-13 10:46:13 +11:00
EspoTek dbc2865396 3 lines changed
Just to make debugging easier on the one-packet-per-frame-dropped error.


Former-commit-id: 88ddd41c8d
2016-12-08 10:44:42 +11:00
EspoTek f272a1f2bd Merge remote-tracking branch 'origin/master'
# Conflicts:
#	Desktop Interface/Labrador.pro.user


Former-commit-id: 0b1d5c5ec2
2016-12-08 08:40:29 +11:00
EspoTek 86d74f5dc2 Sped up serial decode dramatically
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
2016-12-08 08:39:22 +11:00
EspoTek 7b959d6fdb Changed default search directory
functionGenControl and espoComboBox now use QCoreApplication::
applicationDirPath().  This is to fix deploys on Mac.  It’s possible
but unlikely that it broke Windows/Linux.


Former-commit-id: 3bcf78e4c4
2016-11-30 10:58:34 +11:00
EspoTek 9179073975 Code cleanup
Added comments and a folder structure.  No functional changes.


Former-commit-id: 644359d1a2
2016-11-29 09:56:21 +11:00
EspoTek adaaa63eb7 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.


Former-commit-id: b32392b525
2016-11-28 10:38:14 +11:00
EspoTek e1c451ebb2 Plotted and done
Made up the silkscreen layers, put down the stabiliser pin and it's all
ready to be sent off now!


Former-commit-id: 1c6201a7f3
2016-11-23 12:16:40 +11:00
EspoTek 2069cf2e16 FInished the board.
Just need to position balange pins.  Design seems tight, with really low
power supply distances.


Former-commit-id: 0964cc7e6a
2016-11-22 21:06:41 +11:00
EspoTek 9879262085 Redoing the board
Signal gen and PSU wired in.  Very happy!


Former-commit-id: b521416f48
2016-11-22 14:01:56 +11:00
EspoTek 09b492bfd0 Swapped all components to SMD
Board too dense.  Going to start again.


Former-commit-id: edf9c8904b
2016-11-22 10:03:11 +11:00
EspoTek 542daed722 More board work.
It's a bit dense; some would say unnecessarily so.  Might see what I can
do with it in the morning but there's a reasonable chance it'll become
unworkable.


Former-commit-id: a1e508cc1a
2016-11-20 21:17:47 +11:00
EspoTek f758213761 PSU in place
First attempt, anyway.  Far shorter grounding than last rev!  Very
happy!


Former-commit-id: f0fa88c473
2016-11-20 18:39:26 +11:00
EspoTek 8b8a748a5d Named headers
Also there's now an empty kicad_pcb file.


Former-commit-id: 59c472fedb
2016-11-20 17:35:25 +11:00
EspoTek b55a66a0f2 Error fix from last eschema
Accidentally set 2x4 headers rather than 1x4.  This has been fixed.


Former-commit-id: c5408e5c1b
2016-11-20 17:31:44 +11:00
EspoTek fedc1f8892 Another Eschema Update
Have changed pinout of scope.
Still haven't added SMD pads for inductor/diode since the Element14 is
not playing ball.


Former-commit-id: 3dde628793
2016-11-20 17:29:05 +11:00
EspoTek 2318c94755 New Eschema
- Reverted the dual transistor IC back to a single transistor (TSM
thingo)
- Added PSU indicator LED
- Added PSU control/expansion header.

Note that this is only in eschema, not pcbnew!


Former-commit-id: 059d5cbe65
2016-11-20 15:52:25 +11:00
EspoTek 95c5a4b95d Undid PCB revert
I don't want to deal with KiCAD's library management again.  The first
time was bad enough.


Former-commit-id: 2696688130
2016-11-19 18:20:44 +11:00
EspoTek 44bf2d39c4 Reverted PCB files to initial upload
Going to have a final attempt now!


Former-commit-id: bf98f0796f
2016-11-19 17:42:15 +11:00
EspoTek 6a008946d1 Slight change to terminology
Changed things like "Aplitude" to "Amplitude (peak-peak)".
Just to make things a bit less confusing for the user.


Former-commit-id: c9c98b0295
2016-11-19 17:29:41 +11:00
EspoTek ec339d1a76 Update README.md
Former-commit-id: 2f4d8f928b
2016-11-17 11:40:13 +11:00
EspoTek 21832f4d55 Added a single #define
That's it.  Literally a single #define that determines how many
milliseconds the OS waits before reconnecting.  Fixed an error with
Windows not reading it on new mobo, hopefully fixes it under OS X as
well.


Former-commit-id: d69bbf8e68
2016-11-10 17:39:40 +11:00
EspoTek 4c25a50696 Pushing Windows
Going to revert and compare.


Former-commit-id: 8d0f6dbeeb
2016-11-10 15:50:34 +11:00
EspoTek 663cf71cfe Mac OS X build running
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
2016-11-09 16:21:00 +11:00