#qi-hardware IRC log for Thursday, 2014-03-27

whitequarkhaha00:00
DocScrutinizer05I'm afraid I'd suffer from a ever recurring nightmare about Suckerberg00:03
DocScrutinizer05"#Suckerburg #bought #freenode #and #enforces #funny #silly #hashtags #before #every #word"00:36
DocScrutinizer05I bet you don't want to hear about my next nightmare variation00:37
wpwraklet it all out00:38
wpwrakzrafa: (adding USB to your board) ah, forgot that you'll also need a crystal. or at least freescale say so. haven't tried yet to see if one can make USB work without.01:22
DocScrutinizer05hardly01:46
whitequarkwpwrak: idea for a "hacker's CAD"02:30
whitequarkso traditionally, you'd draw some polygons in a CAD, then put them in a CAM and that'll generate you machining operations02:31
whitequarkhow about we merge them, then invert them and make them parametric?02:31
whitequarki.e. you simultaneously define your model and machining operations to create it02:32
whitequarkpossibly on top of openscad or something02:32
whitequarki.e. you can apply boolean operations to solids, and every boolean operation also has parameters explaining how it is done02:33
whitequarke.g. "start with a l=1 cube at (0,0,0)" "subtract l=0.5 cube at (0.5,0.5,0.5), use pocketing with 1.0mm endmill"02:34
whitequarkor even "subtract (difference between l=1 cube at (0,0,0.5) and d=0.5 l=1 cylinder at (0.5,0.5,0.5)), use pocketing with 1.0mm endmill"02:35
whitequarkwhich would make you a box with a cylindrical bump on top02:35
whitequarkessentially attach gcode parameters to every toplevel subtraction02:36
whitequarkdoes that even make sense?02:36
whitequark /cc DocScrutinizer05 02:36
kristianpaulwpwrak: you love this thingy https://www.kickstarter.com/projects/1516846343/microview-chip-sized-arduino-with-built-in-oled-di02:38
kristianpaulyou'll*02:40
whitequarkyes, we've already... discussed02:41
kristianpaulugh02:43
Action: kristianpaul hides02:43
Action: kristianpaul reads archive02:50
Action: kristianpaul thinks werner will look stare at me02:53
whitequarkah, I thought you used "love" in a sarcastic way02:54
kristianpaulDude, i could but is too late now02:55
kristianpaulwow havent looked at the improvements on anelok case02:57
wpwrakwhitequark: well, not quite ... it's true that many other parameters may enter your design, such as tool/mill/material properties, but you'd definitely not want to have a forced 1:1 relationship04:14
wpwrakkristianpaul: hah, gotcha ! now you'll burn in hell :)04:15
whitequarkwpwrak: why not?04:17
wpwrakbecause mixing high-level geometry with detailed low-level instructions will be non-portable. many designs should work with different mill/printer technologies, so you need some abstraction04:20
wpwrakwhitequark: like using assembler in your C programs. you can if you have to, but you normally try not to make a habit out of it. and compilers are usually "good enough" for the extra bit of machine efficiency you could squeeze out not to justify the human effort.12:52
wpwrakthis one is cool: http://cheezburger.com/580078003212:55
wpwraklove what they did with the date ;-)12:55
zrafawpwrak: no sure if we can manage usb to our little project :)13:00
zrafawpwrak: maybe more like : - talk with mcu, turn on a led, make something else no too complicated :)13:00
wpwrakwell, i was thinking more like "add USB hw" and "flash werner's USB stack with DFU" :)13:01
wpwrakso you need the ben only once, to add the boot loader13:02
wpwrakyou'll have to tweak the software a bit, of course, since my boot loader talks to components you don't have. but the basic structure is the same. in fact, yours will be simpler13:04
wpwrakin any case, you can at least leave room for USB connector and crystal in the design. then you can decide to populate them later.13:04
DocScrutinizer05wpwrak: (graph) niiiiiice :-P15:02
DocScrutinizer05((least leave room for USB connector and crystal)) hell, I forced that even into wikireader (original design)15:04
whitequarkoh god this: http://hackaday.com/2014/03/27/hackaday-68k-so-you-want-a-kit16:04
whitequarkguy never heard of NOR flash, says "logical solution is throw a big FPGA for translating A/D/control busses to SPI flash"16:04
whitequarkWhat ever16:05
whitequarkbest part: he highlights that the "big FPGA solution" is "cheap"16:10
larsccheaper than a ASIC16:12
viricha, you say that because you read the comments about the NOR flash16:18
whitequarkviric: now look at the author of that comment16:19
viricone at 6:23 am mentions NOR flash :)16:19
larscnot only did you steal the comment but his name as well?16:19
whitequarkhm?16:20
viricall stolen16:20
whitequarkoh, I missed that one. here's mine: http://hackaday.com/2014/03/27/hackaday-68k-so-you-want-a-kit/#comment-130677516:20
whitequarkI only looked at toplevel ones before posting...16:21
viric:)16:21
viriccd ..16:22
viricoops16:22
wpwrak(clothes-peg adapter) most of the time, you can conveniently get away with just a footprint and gently pushing the chip on the pads16:26
wpwrakhow an MCU would eat more board space than an FPGA eludes me, though16:29
zrafawpwrak: yes, we need the ben at least once17:15
wpwrakzrafa: you could also make a board that does DFU to SWD, similar to how i do DFU to the CC2543 debug protocol in the y-box17:28
wpwrakzrafa: but ... libswd isn't too stable yet, so it would fail very often17:28
wpwrakzrafa: but yes, you'll need *something* to do the very first flashing (and possibly any later updates/fixes to the boot loader). and the ben is of course perfect for that :)21:49
--- Fri Mar 28 201400:00

Generated by irclog2html.py 2.9.2 by Marius Gedminas - find it at mg.pov.lt!