| 00:21.35 | DocScrutinizer05 | lol! |
| 00:22.00 | DocScrutinizer05 | name=basename $0; |
| 00:22.54 | DocScrutinizer05 | rather should use name=`basename $0`; |
| 02:09.49 | wpwrak | and don't forget the rm -rf /$DIRECOTRY/ :) |
| 02:16.12 | DocScrutinizer05 | well, that's simple. But the missing `` make a nice forkbomb from a silly convenience thing for stderror output like "foo: wrong parameter" where foo is the basename of the script |
| 02:17.50 | DocScrutinizer05 | >>name=`basename $0`;<< is fine, you can use $name later on in script like "$name: wrong parameter". However >>name=basename $0;<< does what ? ;-) |
| 02:18.51 | *** join/#qi-hardware Haswell (~Haswell@142.83-213-161.dynamic.clientes.euskaltel.es) |
| 02:18.52 | *** join/#qi-hardware Haswell (~Haswell@unaffiliated/haswell) |
| 02:19.40 | DocScrutinizer05 | it's a rarely ever used ancient way to provide parameters for a executable ($0), as environment vars |
| 02:20.07 | wpwrak | rarely used ? i use it quite often :) |
| 02:20.14 | DocScrutinizer05 | it probably predates the parameter appending to the command name |
| 02:20.25 | DocScrutinizer05 | also uses it often |
| 02:20.56 | wpwrak | and the "fork" bomb isn't so bad. it should build up a lot of processes, hit an error, but then clean up after itself. |
| 02:21.18 | wpwrak | err, "fork bomb" |
| 02:25.31 | DocScrutinizer05 | related: |
| 02:25.34 | DocScrutinizer05 | : ${debug='false'} ;#valid: true | false [| <any cmd>]. |
| 02:25.36 | DocScrutinizer05 | # You may run `debug=true <this-file>`, or`debug='echo "!!!! "' <this-file>` |
| 02:27.46 | DocScrutinizer05 | (lot of processes) err, yep. nevertheless it almost got my box to aa grinding halt before it reached that error |
| 02:28.24 | DocScrutinizer05 | since the error reason been "process table full" or "out of memory (incl swap)" |
| 02:29.06 | wpwrak | yeah there's a reason why i wrote "it should", for i didn't care to verify it by experiment ;-) |
| 02:29.15 | DocScrutinizer05 | haha |
| 02:29.18 | DocScrutinizer05 | ;-P |
| 02:33.39 | DocScrutinizer05 | wtf? where went that colon? : ${debug:='false'} of course |
| 02:34.40 | DocScrutinizer05 | and I missed to quote the third line in that block: ${debug} && set -vx && exec 2>&4 |
| 02:39.27 | DocScrutinizer05 | I guess the last one only makes sense when knowing the previous line too: |
| 02:39.31 | DocScrutinizer05 | # get rid of shell errormsgs - yeah i know... |
| 02:39.32 | DocScrutinizer05 | exec 4>&2 2>/dev/null |
| 02:48.37 | DocScrutinizer05 | gosh, I wrote some funny code 8 years ago ;-) http://paste.opensuse.org/89182449 |
| 05:00.46 | *** join/#qi-hardware xiangfu (~xiangfu@123.125.212.79) |
| 05:34.44 | *** join/#qi-hardware xiangfu (~xiangfu@123.125.212.79) |
| 07:11.02 | *** join/#qi-hardware sb0 (~sb0@123202036015.ctinets.com) |
| 08:02.03 | *** join/#qi-hardware wolfspraul (~wolfsprau@x2f75b47.dyn.telefonica.de) |
| 09:05.59 | *** join/#qi-hardware arhuaco (~arhuaco__@181.61.62.24) |
| 09:17.57 | *** join/#qi-hardware jekhor (~jek@nat-minsk-pool-46-53-200-14.telecom.by) |
| 09:21.40 | DocScrutinizer05 | http://paste.opensuse.org/54475437 |
| 09:24.50 | larsc | on a modern and good operating system it should ;) |
| 09:26.48 | DocScrutinizer05 | http://paste.opensuse.org/43134690 |
| 09:31.10 | DocScrutinizer05 | http://paste.opensuse.org/19035620 GRRR |
| 09:37.37 | DocScrutinizer05 | http://paste.opensuse.org/99448347 |
| 10:30.43 | *** join/#qi-hardware xiangfu (~xiangfu@123.125.212.79) |
| 10:35.42 | *** join/#qi-hardware sb0 (~sb0@123202036015.ctinets.com) |
| 10:38.08 | *** join/#qi-hardware pcercuei (~pcercuei@2a02:810d:1b40:1118::5) |
| 10:38.52 | wpwrak | xiangfu: (soldering) great ! it's best to start with the MCU and the surrounding capacitors, then try to see if SWD works |
| 10:41.13 | wpwrak | a bit tricky if you don't have your UBB board yet, though :) |
| 11:23.02 | xiangfu | the cable ordered from taobao.com was arrived. :) |
| 11:23.28 | xiangfu | but we are not receive the kl26... |
| 11:32.27 | wpwrak | ah, without the kl26 that step will be a bit difficult, yes :) |
| 11:33.24 | *** join/#qi-hardware viric (~viric@unaffiliated/viric) |
| 11:33.35 | wpwrak | i guess it's best to wait until you have the kl26. this is the most difficult part to solder and you don't want the board full of other components at that time. |
| 11:34.04 | xiangfu | Yes. |
| 11:35.25 | wpwrak | maybe you want to post pictures of the PCBs ? that would be the first industrially-made ones, so far we only have my ugly kitchen jobs :) |
| 11:40.44 | xiangfu | I didn't get it yet. :) |
| 11:41.03 | xiangfu | it was at the hardware people place. |
| 11:43.28 | xiangfu | the usb connect is interesting. |
| 11:44.57 | xiangfu | wpwrak: I am thinking how to make some of those cases. |
| 11:51.50 | arhuaco | I am had not used LiPo batteries before. I discharged them too much. A working batt like this one should charge above 8v and last more than 5 minutes with the load I was using (a motor). http://arhuaco.org/tmp/batt.png |
| 11:52.06 | arhuaco | So, that's how 2 broken batts look like :-/ |
| 11:52.52 | arhuaco | s/am// |
| 11:52.55 | *** join/#qi-hardware viric (~viric@unaffiliated/viric) |
| 11:55.19 | xiangfu | wpwrak: http://downloads.qi-hardware.com/people/xiangfu/anelok/pcb/ <--- Just asked them post some pics to me. it taked by mobile phone. |
| 12:13.54 | *** join/#qi-hardware pcercuei (~pcercuei@2a02:810d:1b40:1118:1af4:6aff:fec5:1c8f) |
| 12:17.23 | xiangfu | wpwrak: looks like there are something wrong with my Ubuntu + Freecad (http://downloads.qi-hardware.com/people/xiangfu/anelok/tmp/freecad-anelok-case-0.png) |
| 12:26.48 | wpwrak | (pcb pics) thanks ! the fab was a bit sloppy with the bottom silk screen, but that's not a problem for manual soldering |
| 12:27.22 | wpwrak | (freecad) oh, that looks interesting ;-) |
| 12:28.01 | xiangfu | PCB: there is no silk screen on PCB. |
| 12:28.08 | wpwrak | maybe graphics driver. what video card do you use ? |
| 12:28.43 | xiangfu | yes. there are two video card in my laptop. the Macbook pro retina laptop. |
| 12:28.52 | xiangfu | I think the ubuntu use only one. |
| 12:29.21 | wpwrak | (silk) the white stuff. at the bottom, it's visibly misaligned. and it even seems to overlap a little with pads. |
| 12:29.41 | xiangfu | wpwrak: any advice on fatfs coding work? |
| 12:30.16 | xiangfu | reading this http://elm-chan.org/fsw/ff/00index_e.html |
| 12:30.18 | wpwrak | (macbook) hmm, dunno about these. are you using the open source drivers or the proprietary ones ? |
| 12:31.02 | xiangfu | I am using the open source driver. |
| 12:31.23 | xiangfu | (pcb) I will post some bigger picture tomorrow. |
| 12:32.48 | wpwrak | (fatfs) looks nice. what's important is that we need fat32 support, for those large usd cards |
| 12:33.38 | wpwrak | Perit FAT looks even nicer, but may be a bit too limited |
| 12:34.22 | wpwrak | ah yes, too many limitations. pity. |
| 12:35.06 | xiangfu | which one? |
| 12:36.27 | wpwrak | Petit FAT. FatFs seems to have everything we need. |
| 12:36.34 | xiangfu | Yes. |
| 12:37.13 | xiangfu | I even didn't notice there is 'Petit FatFs' at the first paragraphã |
| 12:37.32 | wpwrak | (video) freecad on ubuntu 14.04 works fine here on nvidia and ati, both with the open source driver |
| 12:37.53 | xiangfu | it have a nice start doc: http://elm-chan.org/fsw/ff/en/appnote.html |
| 12:38.00 | wpwrak | i built freecad from git, but that probably doesn't make a difference. i had used the ubuntu version before and it also worked fine |
| 12:38.58 | wpwrak | (start) nice ! and yes, 2 TB should be sufficient for now :) |
| 12:40.47 | wpwrak | seems to be nicely optimized |
| 12:41.46 | wpwrak | and the license is very friendly. excellent. |
| 12:41.48 | xiangfu | and looks it still active. |
| 12:57.10 | wpwrak | released as zip. very old-skool ;-) |
| 13:20.16 | wpwrak | for making a case, you basically have three choices: |
| 13:21.20 | wpwrak | 1) freecad -> cnc. the problem: this path doesn't officially exist yet and what i've seen of the development work in the are doesn't look as if it could be sufficient for this kind of case. |
| 13:22.06 | wpwrak | 2) FreeCAD -> STL -> HeeksCAD/HeeksCAM -> CNC. this should work but it's a bit messy |
| 13:22.44 | wpwrak | 3) FreeCAD -> STL -> slicer.py + cameo -> g-code |
| 13:23.20 | wpwrak | 3) is my process. cameo outputs "gnuplot" output which i then convert to RML-1, the strange language my mill speaks |
| 13:23.57 | wpwrak | almost everything else uses g-code, but i don't have a converter for that. it shouldn't be overly difficult to write one if you have a mill to test it on. |
| 13:24.37 | wpwrak | this is my gnuplot to rml converter: http://projects.qi-hardware.com/index.php/p/cae-tools/source/tree/master/gp2rml/gp2rml.c |
| 13:28.14 | wpwrak | my freecad-to-rml process seems to work pretty well now. there is one remaining problem: sometimes cameo fails to do the "area fill". this must be some problem with rounding errors since it depends on the position of the piece. so far, i've been able to always avoid the failure (an assertion violation) by moving the addition of an xy offset (i.e., the placement of the piece) either before or after the other operations in cam.sh |
| 13:30.07 | xiangfu | hmm... sounds not easy for me. :) |
| 13:30.16 | xiangfu | write down to my memo. |
| 13:30.56 | wpwrak | it's a bit complicated, yes. i screw up often enough, too :) |
| 13:31.18 | wpwrak | but CNC-machining is fun :) |
| 13:34.13 | wpwrak | archang mentioned that you were thinking of getting a cnc mill. whitequark may have some suggestions for this |
| 13:34.25 | whitequark | http://bit.ly/whitequarks-cnc |
| 13:34.41 | wpwrak | i guess you may also want to they a more-or-less dedicated pc for the mill |
| 13:34.49 | whitequark | yes with an LPT port |
| 13:35.12 | whitequark | alternatively people have been using cubieboard to drive LPT port controllers |
| 13:35.14 | wpwrak | man they're cheap ! |
| 13:35.25 | whitequark | by this point they're quite hard to find actually |
| 13:35.41 | whitequark | anyway, that machine will require some "improvement" |
| 13:35.46 | whitequark | thankfully i documented it all :] |
| 13:36.07 | wpwrak | (hard to find) excessive demand, or did they stop making it ? |
| 13:36.47 | whitequark | they stopped making it a decade ago |
| 13:37.20 | whitequark | and by now people have mostly thrown this hw out, here |
| 13:37.33 | xiangfu | write down to my memo. |
| 13:37.34 | whitequark | ISA multicards, if you remember what they are, go for four digits in dollars |
| 13:38.00 | whitequark | (to some poor souls who have SCADA on 1995 tech) |
| 13:38.34 | whitequark | this reminds me of some nuclear power plant company which doesn't plan to phase out pdp-11 until at least 2040 |
| 13:38.46 | wpwrak | prices here .. for a 3040, about USD 3000-4000 depending on how you count. okay, that one has a 4th axis, but still |
| 13:39.09 | whitequark | wpwrak: holy shit, that's ridiculous |
| 13:39.18 | whitequark | 3040 is at most $600, without delivery |
| 13:39.23 | wpwrak | (stopped a decade ago) wow ! |
| 13:39.47 | wpwrak | whitequark: you're in a free market, not behind some iron curtain :) |
| 13:40.04 | whitequark | ... I'm really not |
| 13:40.08 | whitequark | well |
| 13:40.15 | whitequark | I suppose it's not as bad as what you have, not nearly |
| 13:40.26 | wpwrak | this is what you get here for ~USD 400-500: http://articulo.mercadolibre.com.ar/MLA-537517817-router-cnc-_JM |
| 13:40.46 | wpwrak | good strong MDF |
| 13:40.50 | whitequark | MDF... ugh |
| 13:41.00 | whitequark | and crappy spindle |
| 13:41.34 | whitequark | my mill is fairly bad but now I understand why people like to buy these |
| 13:41.58 | wpwrak | ah, and that's without motors and electronics ;-) |
| 13:42.34 | whitequark | ... |
| 13:42.41 | wpwrak | (3020) someone should start to make them again :_ |
| 13:42.50 | whitequark | nonono, you don't get it |
| 13:42.54 | whitequark | 3020s are actively manufactured |
| 13:43.01 | whitequark | the motherboards with LPT ports are not |
| 13:43.46 | wpwrak | ah, and there are also some used MDX-15. more expensive than mine was new. the miracle of a restricted market :) |
| 13:43.55 | wpwrak | aah, i see |
| 15:55.53 | *** join/#qi-hardware kilae (~chatzilla@catv-162-034.tbwil.ch) |
| 16:07.26 | *** join/#qi-hardware mithro (sid24875@gateway/web/irccloud.com/x-gpehysxgynnkmgrg) |
| 16:53.51 | *** join/#qi-hardware rjeffries (~rjeffries@pool-108-40-199-126.snloca.fios.verizon.net) |
| 16:55.35 | rjeffries | any thoughts on the project to creata what would appear to be a reasonably open laptop? (missing bit is BIOS I guess) |
| 16:55.50 | whitequark | chromebook has FOSS BIOS |
| 16:56.02 | whitequark | except graphics bits, to some degree |
| 16:57.31 | rjeffries | this is one I saw recently: https://www.crowdsupply.com/purism/librem-laptop |
| 16:58.18 | rjeffries | it seems (to me) to be in the spirit of #qi-hardware |
| 16:59.19 | whitequark | "While the BIOS is not yet free, the Librem 15 will be the first laptop ever manufactured to ship a modern Intel CPU fused to run unsigned BIOS code" |
| 16:59.22 | whitequark | that's idiotic |
| 16:59.26 | whitequark | yay BIOS-level rootkits |
| 17:01.50 | whitequark | what you do is provide a way to change secure boot trust root by, say, flipping a physical switch |
| 17:02.10 | whitequark | what you do NOT do is remove trust root entirely and claim this somehow "respects user privacy" |
| 17:02.23 | rjeffries | so you're saying (I think) no (modern) Intel CPU can be in a free and open hardware system. |
| 17:02.55 | whitequark | chromebook gives you such a system |
| 17:03.08 | whitequark | no need for some kickstarter fraud |
| 17:04.36 | whitequark | and chromebook does it *right* |
| 17:04.46 | whitequark | Both things will be nessary, if you want to flash your own version of Coreboot onto your Chromebook (in-system). It is nessary to close a circuit on the motherboard via either a switch, jumper or srew to disable the write-protection of the spi chip. |
| 17:05.54 | rjeffries | are you saying this purism project is fraudulent? Really? |
| 17:06.28 | rjeffries | btw I am writing this on an early Samsung C303 Chromebook. Not a bad little machine. |
| 17:06.35 | whitequark | most crowdsourced projects overpromise and under/never deliver |
| 17:06.49 | whitequark | and an entire laptop is a very complex project |
| 17:06.55 | whitequark | what's worse is their claims |
| 17:07.03 | rjeffries | this lappie looks doable to me. not impossible. it is expensive, yes |
| 17:14.52 | wpwrak | if all else fails, there's still novena ;-) |
| 19:27.07 | *** join/#qi-hardware jekhor (~jek@134.17.175.5) |
| 19:33.31 | arossdotme | rjeffries: i'd say your best bet is http://rhombus-tech.net |
| 19:35.02 | arossdotme | with librem your putting a lot of funds in to a one off laptop that will quickly become an antique or you could use less funds to invest into a new future of computer design |
| 19:35.43 | arossdotme | or you could use the same funds you would have spent on a librem to help the project move faster :D |
| 19:35.52 | arossdotme | hehe |
| 19:36.58 | arossdotme | i guess within a few years if not already embedded stuff will have the same specs as the librem but without the fan :) |
| 19:38.42 | arossdotme | it's a lot lot easier to chun out a new computer card instead of a hole new laptop and faster/newer/diff cpu/ram/gpu and better for the environment |
| 19:39.36 | arossdotme | laptop desisners can focus of making a great laptop in stead of a good but faster laptop for the next product cycle |
| 20:38.52 | DocScrutinizer05 | wpwrak: what do you say about my bash USB DMM readout script? Contrary to what you encountered, it's 100% reliable too |
| 20:40.03 | DocScrutinizer05 | and actually I take quite some pride in the timestamp/scheduling function |
| 20:42.08 | DocScrutinizer05 | 100% frequency stable, skew ~20ms avg, max jitter ~ -10/+100ms |
| 20:44.52 | DocScrutinizer05 | the max sample rate of 1Hz is only by the integer arithmetic of bash $(( )), I could tune that to maybe 20Hz if I'd use milliseconds instead of seconds for interval |
| 20:53.07 | DocScrutinizer05 | there are two cases that are not yet handled correctly: a tiny flaw and "unbearable" 5 lines of error codes when the /dev/ttyUSB* is not readable by user due to file permissions, and no handling of disconnecting or switching off the DMM while command takes a series of samples - mostly due to my lack of ideas how it actually should react on such event. Abort? Error to stderr? Error to stdout? No sample taken at all? Retry a N times, |
| 20:53.09 | DocScrutinizer05 | then throw error? |
| 23:14.29 | nicksydney | wpwrak: http://benjaminkerensa.com/2015/01/23/get-a-free-u2f-yubikey-to-test-on-firefox-nightly |
| 23:16.08 | *** join/#qi-hardware Nik05 (~Nik05@unaffiliated/nik05) |
| 23:17.12 | *** join/#qi-hardware Luke-Jr (~luke-jr@unaffiliated/luke-jr) |
| 23:52.19 | wpwrak | DocScrutinizer05: yeah, i would have expected you to run into painful problems by now :) |
| 23:53.19 | wpwrak | at least things like the meter sometimes not responding or such, which then would then require some tricky timeout and recovery mechanism. |
| 23:53.40 | DocScrutinizer05 | which is already implemented in that script |
| 23:54.17 | wpwrak | luckily, it doesn't even support fancier things where such problems are almost unavoidable, e.g., meter-triggered data transfer (with issues of how to cancel things, etc.) |
| 23:57.00 | DocScrutinizer05 | ooh, it does: *0 .. *7 |
| 23:57.16 | DocScrutinizer05 | when turning the turn dial |
| 23:58.36 | DocScrutinizer05 | and yeah, this *might* spoil one response reading, but then any response would be bogus anyway when fetching data while actually the range/type of test changed |
| 23:59.24 | DocScrutinizer05 | wouldn't know why and what to cancel though |
){kind=link}