azonenberg changed the topic of #scopehal to: libscopehal, libscopeprotocols, and glscopeclient development and testing | https://github.com/azonenberg/scopehal-cmake, https://github.com/azonenberg/scopehal-apps, https://github.com/azonenberg/scopehal | Logs: https://freenode.irclog.whitequark.org/scopehal
<_whitenotifier-b> [scopehal] tomverbeure opened pull request #171: Initial skeleton Tektronix support - https://git.io/JJIVV
<_whitenotifier-b> [scopehal-apps] tomverbeure opened pull request #128: Add Tektronix oscilloscope. - https://git.io/JJIVr
tverbeure has joined #scopehal
<azonenberg> o/ tverbeure. Been a while, was wondering what you were up to
<azonenberg> busy apparently :p
<_whitenotifier-b> [scopehal-apps] tomverbeure commented on pull request #128: Add Tektronix oscilloscope. - https://git.io/JJIwt
<tverbeure> Busy, but not really on scopehal. I've been trying to hack the TDS420A to get it from 30k samples to 120k samples, learning Ghidra etc in the process.
<azonenberg> Oh, lol
<tverbeure> Turns out: the scope is actually missing RAM on the DSP board. So I have those on order now. :-)
<tverbeure> All of this is completely academic, of course, just to prove a point.
<azonenberg> lol
<azonenberg> I know a guy in another channel who turned ilke a 200 MHz keysight into a 1 GHz
<azonenberg> they had to swap out over a hundred parts in the front end
<azonenberg> but it worked
<miek> i don't think they'll be too cut up about it eating into sales for that series anymore :)
<azonenberg> Lol
<azonenberg> Also, your PR on #128 is unnecessary. All of those scope includes are from before we had the proper dynamic creation table and had a big if/else cascade creating "new foo" for each scope family
<azonenberg> Can you amend the PR to *delete* all of the driver-specific includes from glscopeclient/main.cpp?
<tverbeure> Yeah, that's a different level. I also acquired an HP 54825A scope (essentially for free.) Might be useful to try out some Agilent stuff as well.
<tverbeure> Let me try.
<miek> i was very happy to learn that a lot of HP/Agilent kit has debug symbols included (anything vxworks-based that i've seen so far)
<_whitenotifier-b> [scopehal-apps] tomverbeure synchronize pull request #128: Add Tektronix oscilloscope. - https://git.io/JJIVr
<tverbeure> However, my 54825A scope uses ... Win 95.
<miek> ooh, nice (not the win95 bit :p)
<miek> though, fyi, ghidra includes a script that'll search for the vxworks symbol table in the binary & apply it
<tverbeure> I should have known! I had never used Ghidra before, so these are just beginner's notes.
<miek> yeah, i only found it by accident when i was looking through the script manager
<miek> it needs a large blinking sign that tells you about it when you load a vxworks binary :)
<azonenberg> lol
<azonenberg> yeah i remember getting pretty good at figuring out uC/OS-II thread names etc aftr REing a lot of that for work
<_whitenotifier-b> [scopehal-apps] azonenberg closed pull request #128: Add Tektronix oscilloscope. - https://git.io/JJIVr
<_whitenotifier-b> [scopehal-apps] azonenberg pushed 3 commits to master [+0/-0/±3] https://git.io/JJIrT
<_whitenotifier-b> [scopehal-apps] tomverbeure ad32e8f - Add Tektronix oscilloscope.
<_whitenotifier-b> [scopehal-apps] tomverbeure 19327f4 - Remove explicit list of supported equipment.
<_whitenotifier-b> [scopehal-apps] azonenberg 7da600d - Merge pull request #128 from tomverbeure/tektronix Add Tektronix oscilloscope.
<azonenberg> tverbeure: did you have anything in scopehal-docs for the driver yet?
<tverbeure> No. If anything, it should be: "DON'T USE!". For example, right now, there's a hard-coded number of sample points of 500... I need to clean these kind of things up one by one.
<tverbeure> I shouldn't take too long though to make it functional.
<_whitenotifier-b> [scopehal] azonenberg closed pull request #171: Initial skeleton Tektronix support - https://git.io/JJIVV
<_whitenotifier-b> [scopehal] azonenberg pushed 4 commits to master [+4/-0/±6] https://git.io/JJIrL
<_whitenotifier-b> [scopehal] tomverbeure 381ccfe - Skeleton Tektronix oscilloscope code.
<_whitenotifier-b> [scopehal] tomverbeure 8a75241 - Fix indenting.
<_whitenotifier-b> [scopehal] tomverbeure 764ad41 - Fix tabs.
<_whitenotifier-b> [scopehal] azonenberg 3626e33 - Merge pull request #171 from tomverbeure/tektronix Initial skeleton Tektronix support
<azonenberg> lol ok
juli969 has quit [Quit: Nettalk6 - www.ntalk.de]
<_whitenotifier-b> [starshipraider] azonenberg pushed 3 commits to master [+2/-2/±3] https://git.io/JJIrs
<_whitenotifier-b> [starshipraider] azonenberg 54bd610 - Routed backlight power, remaining pod power, setup for MCU
<_whitenotifier-b> [starshipraider] azonenberg 0729f98 - Removed references to old cylindrical probe shell which doesn't fit the current PCB revision
<_whitenotifier-b> [starshipraider] azonenberg 7cdbbd8 - Final v1.0 probe design for production run
<_whitenotifier-b> [starshipraider] azonenberg pushed 1 commit to master [+0/-0/±1] https://git.io/JJIrl
<_whitenotifier-b> [starshipraider] azonenberg 3dd57fd - Updated probe shell design to provide clearance for second tip ground
Degi has quit [Ping timeout: 256 seconds]
<_whitenotifier-b> [starshipraider] azonenberg pushed 4 commits to master [+0/-0/±4] https://git.io/JJIis
<_whitenotifier-b> [starshipraider] azonenberg 0a4b5ba - Moved input connector hole down. Increased wall thickness from 1 mm to 2 mm. Removed dead space at front side of enclosure.
<_whitenotifier-b> [starshipraider] azonenberg 1a0378a - Increased floor thickness from 1.5 to 2 mm
<_whitenotifier-b> [starshipraider] azonenberg a75db95 - Changed dimensions to match bottom. Increased thickness from 1.5 to 2 mm. Reduced size of LCD cutout.
<_whitenotifier-b> [starshipraider] azonenberg 156797f - Added stiffener ribs to underside of lid
Degi has joined #scopehal
<azonenberg> OK so... the v0.2 MEAD enclosure
<azonenberg> 3D printed black MJF nylon is $32.91 for the bottom and $13.99 for the top, or $46.90, and there's minimal discounts for higher volume
<azonenberg> Expected to ship by the 10th and arrive by the 13th after paying for priority processing - i guess shapeways isn't very busy now?
<azonenberg> along with two of the hopefully final probe PCB shells
<azonenberg> If those look good i'll order the rest of the production run once the prototypes come in
<azonenberg> Meanwhile, for reference, making the MEAD enclosure out of CNC'd 6061 aluminum with black hard-coat anodizing will cost $145.86 for the top @ qty 1 but this drops to $13.40 @ 50 and into the single digits per unit past 100 pieces
<azonenberg> So for the top, 50 units is about the breakeven from 3dp nylon to cnc alu
<azonenberg> For the bottom half, it's $200.85 @ 1, $32.69 @ 25, then cheaper from there. So 25 pieces is the breakeven
<azonenberg> Keeping in mind that a full MAXWELL platform needs 12 MEAD pods, if i end up making even two full MAXWELL systems it will be economical to go with the metal enclosures
<azonenberg> lain, monochroma: see above stats
<monochroma> heh
electronic_eel_ has joined #scopehal
electronic_eel has quit [Ping timeout: 260 seconds]
<_whitenotifier-b> [starshipraider] azonenberg pushed 2 commits to master [+0/-0/±22] https://git.io/JJIyy
<_whitenotifier-b> [starshipraider] azonenberg 889338f - Continued work on MCU area layout
<_whitenotifier-b> [starshipraider] azonenberg 6306f33 - Continued MCU/LCD layout
<azonenberg> coming along nicely but still a ton of work to do
<azonenberg> Got a substantial fraction of the MCU routed today though
<azonenberg> 1826 unrouted
<azonenberg> Roughly speaking the signal layer allocation has big parts and LVDS lanes 0-3 of each input pod on the top layer
<azonenberg> Lanes 4-7 and small passives on the bottom
<azonenberg> then layer 3 is vertical interconnect routing and layer 6 is horizontal
<azonenberg> with pretty much all of the control/status lines forced onto internal layers because everywhere i don't have parts on the front i have LVDS :p
<azonenberg> Still need to finish the rest of the power supply and figure out where to put the spartan7
<_whitenotifier-b> [stm32-cpp] azonenberg pushed 1 commit to master [+4/-0/±3] https://git.io/JJIAT
<_whitenotifier-b> [stm32-cpp] azonenberg 04ad3a7 - Added StringBuffer class, moved printf to CharacterDevice, some other reorganization
<_whitenotifier-b> [starshipraider] azonenberg pushed 2 commits to master [+0/-0/±5] https://git.io/JJIAW
<_whitenotifier-b> [starshipraider] azonenberg e46a18a - AMG240160P: now a character device, added some missing characters to font
<_whitenotifier-b> [starshipraider] azonenberg 23012af - LCD now includes thermal readings for debugging, and includes initial channel name text
juli969 has joined #scopehal
<azonenberg> ok there we go i can printf instead of doing manual char-by-char writes to the framebuffer on the lcd. So much nicer now
<monochroma> hehe
<azonenberg> Need to bring up the DAC still, as well as providing a UART API for setting channel names and thresholds
<azonenberg> My thought is to allow you to specify probe gain and attenuation separately then multiply as needed to get the true Vt
<azonenberg> So for example if you say you've got a 10x probe and have 3.3V logic, you'd set Vt to 1.65V but the hardware would set the DAC to 165 mV
<azonenberg> I'm thinking of how to format my text here... the 9x16 font is just a tiny bit too tall to have 2 lines of text for each channel
<azonenberg> 8x16*
<azonenberg> as of now no actual character is more than 14 pixels high, the top and bottom cells of each character in the font are blank
<azonenberg> So if i were to shrink to 8x15, i'd have worst case 1 pixel instead of 2 pixels of margin between adjacent characters with the same size text
<azonenberg> oh wait
<azonenberg> yeah
<azonenberg> So that would let me have 16 rows of text instead of 15, and save a little bit of flash in the font table
<azonenberg> that would give me 2 full lines per channel
<azonenberg> Production probe PCBs ordered, 15 working day lead time from multech. So I expect to have them around the end of the month
<azonenberg> monochroma: So given that i now have 2 lines of text per probe I'm thinking of having channel name on the first line then some metadata on the second?
<azonenberg> namely, probe attenuation and threshold
<monochroma> sounds good
<azonenberg> I have a signal source connected via a 10x probe to the first channel, working on bringing up the DAC now
juli969 has quit [Quit: Nettalk6 - www.ntalk.de]
bvernoux has joined #scopehal
<azonenberg> ok so the dac isnt cooperating yet
<azonenberg> it's at least somewhat alive, the Vref test point is showing 2.5V
<azonenberg> but i'm not getting it to output anything yet
<azonenberg> And when i attempt to read the ID register i get nothing back. Probe access is annoying because of the LCD ribbon cable and giant alligator clip backlight feeds
<azonenberg> tomorrow i'm gonna try and rig up a more proper bodged-on power source and go from there
tverbeure has quit [Quit: Leaving]
<Degi> Does it make sense to delay and phase match the diff pairs before finalizing their routing?
m4ssi has joined #scopehal
m4ssi has quit [Remote host closed the connection]
<bvernoux> hello
<bvernoux> I have received my KC908 Spectrum Analyzer
<bvernoux> very nice
<Degi> Oh neat!
<azonenberg> Degi: yes
<azonenberg> in fact i'm doing that
<azonenberg> as i start fanning each one out i'm delay matching within the pod
<Degi> Neat
juli969 has joined #scopehal
bvernoux has quit [Read error: Connection reset by peer]
<_whitenotifier-b> [starshipraider] azonenberg pushed 1 commit to master [+0/-0/±3] https://git.io/JJLXb
<_whitenotifier-b> [starshipraider] azonenberg bc97999 - Continued MCU subsystem layout, initial routing of 5V power