* DocScrutinizer05
rather should use name=`basename $0`;
<wpwrak>
and don't forget the rm -rf /$DIRECOTRY/ :)
<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
<DocScrutinizer05>
>>name=`basename $0`;<< is fine, you can use $name later on in script like "$name: wrong parameter". However >>name=basename $0;<< does what ? ;-)
Haswell has joined #qi-hardware
Haswell has quit [Changing host]
Haswell has joined #qi-hardware
<DocScrutinizer05>
it's a rarely ever used ancient way to provide parameters for a executable ($0), as environment vars
<wpwrak>
rarely used ? i use it quite often :)
<DocScrutinizer05>
it probably predates the parameter appending to the command name
* DocScrutinizer05
also uses it often
<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.
sb0 has quit [Read error: Connection reset by peer]
xiangfu has joined #qi-hardware
sb0 has joined #qi-hardware
pcercuei has joined #qi-hardware
<wpwrak>
xiangfu: (soldering) great ! it's best to start with the MCU and the surrounding capacitors, then try to see if SWD works
<wpwrak>
a bit tricky if you don't have your UBB board yet, though :)
<xiangfu>
the cable ordered from taobao.com was arrived. :)
<xiangfu>
but we are not receive the kl26...
viric has quit [Ping timeout: 240 seconds]
<wpwrak>
ah, without the kl26 that step will be a bit difficult, yes :)
viric has joined #qi-hardware
<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.
<xiangfu>
Yes.
<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 :)
<xiangfu>
I didn't get it yet. :)
<xiangfu>
it was at the hardware people place.
<xiangfu>
the usb connect is interesting.
<xiangfu>
wpwrak: I am thinking how to make some of those cases.
viric has quit [Read error: Connection reset by peer]
<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
<arhuaco>
So, that's how 2 broken batts look like :-/
<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
<wpwrak>
(start) nice ! and yes, 2 TB should be sufficient for now :)
<wpwrak>
seems to be nicely optimized
<wpwrak>
and the license is very friendly. excellent.
<xiangfu>
and looks it still active.
<wpwrak>
released as zip. very old-skool ;-)
<wpwrak>
for making a case, you basically have three choices:
<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.
<wpwrak>
2) FreeCAD -> STL -> HeeksCAD/HeeksCAM -> CNC. this should work but it's a bit messy
<wpwrak>
3) is my process. cameo outputs "gnuplot" output which i then convert to RML-1, the strange language my mill speaks
<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.
<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
<xiangfu>
hmm... sounds not easy for me. :)
* xiangfu
write down to my memo.
<wpwrak>
it's a bit complicated, yes. i screw up often enough, too :)
<wpwrak>
but CNC-machining is fun :)
<wpwrak>
archang mentioned that you were thinking of getting a cnc mill. whitequark may have some suggestions for this
<rjeffries>
it seems (to me) to be in the spirit of #qi-hardware
<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"
<whitequark>
that's idiotic
<whitequark>
yay BIOS-level rootkits
<whitequark>
what you do is provide a way to change secure boot trust root by, say, flipping a physical switch
<whitequark>
what you do NOT do is remove trust root entirely and claim this somehow "respects user privacy"
<rjeffries>
so you're saying (I think) no (modern) Intel CPU can be in a free and open hardware system.
<whitequark>
chromebook gives you such a system
<whitequark>
no need for some kickstarter fraud
<whitequark>
and chromebook does it *right*
<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.
<rjeffries>
are you saying this purism project is fraudulent? Really?
<rjeffries>
btw I am writing this on an early Samsung C303 Chromebook. Not a bad little machine.
<whitequark>
most crowdsourced projects overpromise and under/never deliver
<whitequark>
and an entire laptop is a very complex project
<whitequark>
what's worse is their claims
<rjeffries>
this lappie looks doable to me. not impossible. it is expensive, yes
<wpwrak>
if all else fails, there's still novena ;-)
<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
<arossdotme>
or you could use the same funds you would have spent on a librem to help the project move faster :D
<arossdotme>
hehe
<arossdotme>
i guess within a few years if not already embedded stuff will have the same specs as the librem but without the fan :)
<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
<arossdotme>
laptop desisners can focus of making a great laptop in stead of a good but faster laptop for the next product cycle
<DocScrutinizer05>
wpwrak: what do you say about my bash USB DMM readout script? Contrary to what you encountered, it's 100% reliable too
<DocScrutinizer05>
and actually I take quite some pride in the timestamp/scheduling function
<DocScrutinizer05>
100% frequency stable, skew ~20ms avg, max jitter ~ -10/+100ms
<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
wolfspraul has quit [Ping timeout: 244 seconds]
<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,
<DocScrutinizer05>
then throw error?
kilae has quit [Quit: ChatZilla 0.9.91.1 [Firefox 35.0/20150108202552]]
pcercuei has quit [Ping timeout: 245 seconds]
Nik05 has quit [Remote host closed the connection]
<wpwrak>
DocScrutinizer05: yeah, i would have expected you to run into painful problems by now :)
<wpwrak>
at least things like the meter sometimes not responding or such, which then would then require some tricky timeout and recovery mechanism.
<DocScrutinizer05>
which is already implemented in that script
<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.)
<DocScrutinizer05>
ooh, it does: *0 .. *7
<DocScrutinizer05>
when turning the turn dial
<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
<DocScrutinizer05>
wouldn't know why and what to cancel though