2014-06-06 00:18 nicksydney has joined #qi-hardware
2014-06-06 00:48 DocScrutinizer51 has quit [Read error: No route to host]
2014-06-06 00:48 DocScrutinizer51 has joined #qi-hardware
2014-06-06 01:01 lykw has quit [Quit: Leaving]
2014-06-06 01:53 <nicksydney> My C is rusty...refreshing pointer is really painful :(
2014-06-06 02:07 porchao has joined #qi-hardware
2014-06-06 02:58 michael_lee has joined #qi-hardware
2014-06-06 03:42 <kyak> just wait for whitequark, he'll point ya :)
2014-06-06 04:00 rz2k has joined #qi-hardware
2014-06-06 04:54 <wpwrak> nicksydney: soo .. no new troubles were found ? that's almost disappointing - i must have screwed up somewhere :)
2014-06-06 04:58 <wpwrak> most hated X11 message: "Maximum number of clients reached"
2014-06-06 05:06 <nicksydney> wpwrak: not that i can see but going to review it again just to make sure later :)
2014-06-06 05:15 freespac1 has joined #qi-hardware
2014-06-06 05:15 kyak has quit [*.net *.split]
2014-06-06 05:15 BerryHalsak has quit [*.net *.split]
2014-06-06 05:15 Codora has quit [*.net *.split]
2014-06-06 05:15 michael_lee has quit [*.net *.split]
2014-06-06 05:15 kristianpaul has quit [*.net *.split]
2014-06-06 05:15 FDCX has quit [*.net *.split]
2014-06-06 05:15 woakas has quit [*.net *.split]
2014-06-06 05:15 freespace has quit [*.net *.split]
2014-06-06 05:15 ChanServ has quit [*.net *.split]
2014-06-06 05:15 mth has quit [*.net *.split]
2014-06-06 05:15 Jay7 has quit [*.net *.split]
2014-06-06 05:15 mirko has quit [*.net *.split]
2014-06-06 05:15 DocScrutinizer05 has quit [*.net *.split]
2014-06-06 05:15 roh has quit [*.net *.split]
2014-06-06 05:15 larsc has quit [*.net *.split]
2014-06-06 05:15 uwe_mobile__ has quit [*.net *.split]
2014-06-06 05:15 dos1 has quit [*.net *.split]
2014-06-06 05:15 qi-bot has quit [*.net *.split]
2014-06-06 05:15 tumdedum has quit [*.net *.split]
2014-06-06 05:15 panda|z has quit [*.net *.split]
2014-06-06 05:15 Ornotermes has quit [*.net *.split]
2014-06-06 05:15 bartbes has quit [*.net *.split]
2014-06-06 05:15 valhalla has quit [*.net *.split]
2014-06-06 05:15 kanzure has quit [*.net *.split]
2014-06-06 05:15 rz2k has quit [*.net *.split]
2014-06-06 05:15 porchao has quit [*.net *.split]
2014-06-06 05:15 Luke-Jr has quit [*.net *.split]
2014-06-06 05:15 zear has quit [*.net *.split]
2014-06-06 05:15 jow_laptop has quit [*.net *.split]
2014-06-06 05:15 DocScrutinizer51 has quit [*.net *.split]
2014-06-06 05:15 zrafa_ has quit [*.net *.split]
2014-06-06 05:15 wpwrak has quit [*.net *.split]
2014-06-06 05:15 eintopf has quit [*.net *.split]
2014-06-06 05:27 DocScrutinizer51 has joined #qi-hardware
2014-06-06 05:27 Luke-Jr has joined #qi-hardware
2014-06-06 05:27 porchao has joined #qi-hardware
2014-06-06 05:27 kyak has joined #qi-hardware
2014-06-06 05:27 bartbes has joined #qi-hardware
2014-06-06 05:27 rz2k has joined #qi-hardware
2014-06-06 05:27 BerryHalsak has joined #qi-hardware
2014-06-06 05:27 valhalla has joined #qi-hardware
2014-06-06 05:27 Codora has joined #qi-hardware
2014-06-06 05:27 woakas has joined #qi-hardware
2014-06-06 05:27 uwe_mobile__ has joined #qi-hardware
2014-06-06 05:27 kristianpaul has joined #qi-hardware
2014-06-06 05:27 wpwrak has joined #qi-hardware
2014-06-06 05:27 ChanServ has joined #qi-hardware
2014-06-06 05:27 tumdedum has joined #qi-hardware
2014-06-06 05:27 DocScrutinizer05 has joined #qi-hardware
2014-06-06 05:27 Jay7 has joined #qi-hardware
2014-06-06 05:27 larsc has joined #qi-hardware
2014-06-06 05:27 eintopf has joined #qi-hardware
2014-06-06 05:27 mirko has joined #qi-hardware
2014-06-06 05:27 Ornotermes has joined #qi-hardware
2014-06-06 05:27 panda|z has joined #qi-hardware
2014-06-06 05:27 zear has joined #qi-hardware
2014-06-06 05:27 dos1 has joined #qi-hardware
2014-06-06 05:27 roh has joined #qi-hardware
2014-06-06 05:27 jow_laptop has joined #qi-hardware
2014-06-06 05:27 kanzure has joined #qi-hardware
2014-06-06 05:27 mth has joined #qi-hardware
2014-06-06 05:27 FDCX has joined #qi-hardware
2014-06-06 05:27 zrafa_ has joined #qi-hardware
2014-06-06 05:27 qi-bot has joined #qi-hardware
2014-06-06 05:28 kyak has quit [*.net *.split]
2014-06-06 05:28 BerryHalsak has quit [*.net *.split]
2014-06-06 05:28 Codora has quit [*.net *.split]
2014-06-06 05:28 FDCX has quit [*.net *.split]
2014-06-06 05:28 kristianpaul has quit [*.net *.split]
2014-06-06 05:28 woakas has quit [*.net *.split]
2014-06-06 05:28 ChanServ has quit [*.net *.split]
2014-06-06 05:28 mth has quit [*.net *.split]
2014-06-06 05:28 Jay7 has quit [*.net *.split]
2014-06-06 05:28 mirko has quit [*.net *.split]
2014-06-06 05:28 DocScrutinizer05 has quit [*.net *.split]
2014-06-06 05:28 roh has quit [*.net *.split]
2014-06-06 05:28 larsc has quit [*.net *.split]
2014-06-06 05:28 uwe_mobile__ has quit [*.net *.split]
2014-06-06 05:28 dos1 has quit [*.net *.split]
2014-06-06 05:28 qi-bot has quit [*.net *.split]
2014-06-06 05:28 tumdedum has quit [*.net *.split]
2014-06-06 05:28 Ornotermes has quit [*.net *.split]
2014-06-06 05:28 panda|z has quit [*.net *.split]
2014-06-06 05:28 bartbes has quit [*.net *.split]
2014-06-06 05:28 valhalla has quit [*.net *.split]
2014-06-06 05:28 kanzure has quit [*.net *.split]
2014-06-06 05:28 rz2k has quit [*.net *.split]
2014-06-06 05:28 porchao has quit [*.net *.split]
2014-06-06 05:28 Luke-Jr has quit [*.net *.split]
2014-06-06 05:28 zear has quit [*.net *.split]
2014-06-06 05:28 jow_laptop has quit [*.net *.split]
2014-06-06 05:28 DocScrutinizer51 has quit [*.net *.split]
2014-06-06 05:28 zrafa_ has quit [*.net *.split]
2014-06-06 05:28 wpwrak has quit [*.net *.split]
2014-06-06 05:28 eintopf has quit [*.net *.split]
2014-06-06 05:33 zrafa_ has joined #qi-hardware
2014-06-06 05:33 zear has joined #qi-hardware
2014-06-06 05:33 wpwrak has joined #qi-hardware
2014-06-06 05:33 valhalla has joined #qi-hardware
2014-06-06 05:33 kristianpaul has joined #qi-hardware
2014-06-06 05:33 dos1 has joined #qi-hardware
2014-06-06 05:33 Jay7 has joined #qi-hardware
2014-06-06 05:33 qi-bot has joined #qi-hardware
2014-06-06 05:33 kanzure has joined #qi-hardware
2014-06-06 05:33 tumdedum has joined #qi-hardware
2014-06-06 05:33 BerryHalsak has joined #qi-hardware
2014-06-06 05:33 jow_laptop has joined #qi-hardware
2014-06-06 05:33 Ornotermes has joined #qi-hardware
2014-06-06 05:33 mirko has joined #qi-hardware
2014-06-06 05:33 rz2k has joined #qi-hardware
2014-06-06 05:33 Codora has joined #qi-hardware
2014-06-06 05:33 DocScrutinizer51 has joined #qi-hardware
2014-06-06 05:33 larsc has joined #qi-hardware
2014-06-06 05:33 ChanServ has joined #qi-hardware
2014-06-06 05:33 porchao has joined #qi-hardware
2014-06-06 05:33 bartbes has joined #qi-hardware
2014-06-06 05:33 panda|z has joined #qi-hardware
2014-06-06 05:33 woakas has joined #qi-hardware
2014-06-06 05:33 mth has joined #qi-hardware
2014-06-06 05:33 Luke-Jr has joined #qi-hardware
2014-06-06 05:33 kyak has joined #qi-hardware
2014-06-06 05:33 eintopf has joined #qi-hardware
2014-06-06 05:33 uwe_mobile__ has joined #qi-hardware
2014-06-06 05:33 DocScrutinizer05 has joined #qi-hardware
2014-06-06 05:33 roh has joined #qi-hardware
2014-06-06 05:33 FDCX has joined #qi-hardware
2014-06-06 05:45 <nicksydney> how to find the code for klogctl .. looking inside glibc can't find it :(
2014-06-06 05:45 <nicksydney> any idea ?
2014-06-06 05:45 <nicksydney> WHY is it have to be soooo hard to find a frinkin' code
2014-06-06 05:48 xiangfu has joined #qi-hardware
2014-06-06 05:59 wolfspraul has joined #qi-hardware
2014-06-06 06:06 freespac1 has quit [Ping timeout: 255 seconds]
2014-06-06 06:32 michael_lee has joined #qi-hardware
2014-06-06 06:54 jekhor has joined #qi-hardware
2014-06-06 07:53 BerryHalsak has quit [Quit: Leaving]
2014-06-06 08:00 michael_lee has quit [Quit: Ex-Chat]
2014-06-06 08:18 xiangfu has quit [Remote host closed the connection]
2014-06-06 08:39 lamrz has joined #qi-hardware
2014-06-06 08:55 sb0 has joined #qi-hardware
2014-06-06 10:47 lamrz has quit [Quit: Leaving]
2014-06-06 11:11 <wpwrak> hmm, more heartbleed. time to update the packages. soon a daily cron job will make sense ..
2014-06-06 11:16 <larsc> just disable ssl
2014-06-06 11:18 <wpwrak> return to telnet :)
2014-06-06 11:18 <wpwrak> (and the protocols of that era)
2014-06-06 11:25 <larsc> now is your chance to invent the facebook of gopher
2014-06-06 11:38 <wpwrak> privatebook - not using insecure SSL :)
2014-06-06 11:40 <wpwrak> oh, overlooked two posts on the list ..
2014-06-06 11:40 <sb0> https://web.archive.org/web/20140325191339/http://www.thimbl.net/
2014-06-06 11:41 <sb0> the twitter of finger
2014-06-06 11:44 jekhor has quit [Ping timeout: 252 seconds]
2014-06-06 12:06 <larsc> using the way back machine makes this sound as if it was 10 years ago
2014-06-06 12:15 <wpwrak> fingerbook - transient bookmarks ?
2014-06-06 12:16 <wpwrak> twitter and finger are harder to mix in common language, though
2014-06-06 12:19 <nicksydney> can anelok sing with this http://www.ebay.com/itm/New-XS3868-Bluetooth-Stereo-Audio-Module-OVC3860-Supports-A2DP-AVRCP-/161314794017?pt=LH_DefaultDomain_0&hash=item258f1c6a21  :)
2014-06-06 12:20 <ysionneau> not sure anelok will implement A2DP or AVRCP profiles ;)
2014-06-06 12:21 <ysionneau> oh and btw A2DP or AVRCP are not part of BLE
2014-06-06 12:21 <ysionneau> BLE is just for very low power low throughput stuff
2014-06-06 12:21 <ysionneau> so no media streaming
2014-06-06 12:22 <ysionneau> you need bluetooth 2.1 or 3 or 4 for these profiles
2014-06-06 12:22 <nicksydney> oh no ... so will never hear Anelok sing ever ! :(
2014-06-06 12:22 <ysionneau> sorry :/
2014-06-06 12:22 <nicksydney> neat idea https://www.kickstarter.com/projects/1842571016/piconsole-anywhere-console-for-raspberry-pi :)
2014-06-06 12:23 <larsc> nicksydney: you really need to get a twitter (or a thimbl)
2014-06-06 12:23 <nicksydney> larsc: nah too old fashion twitter...should get twitIRC :)
2014-06-06 12:24 <ysionneau> twitnet
2014-06-06 12:24 <ysionneau> telter
2014-06-06 12:24 <ysionneau> over COM over BLE
2014-06-06 12:28 <wpwrak> and no audio peripherals in anelok :)
2014-06-06 12:29 <wpwrak> (COM, etc.) 110 bps teletype
2014-06-06 12:31 freespace has joined #qi-hardware
2014-06-06 12:36 xiangfu has joined #qi-hardware
2014-06-06 12:57 <nicksydney> i don't understand why people are so excited when they can do programming in a microcontroller such as Cortex-M series using Javascript or .Net ?
2014-06-06 13:01 <wpwrak> because they won't have to live with the confusing fact that some C on a cortex runs faster than their junk on the PC that's supposed to be 1-2 orders of magnitude more powerful ...
2014-06-06 13:03 <nicksydney> hmm....still not convincing to write in JS though
2014-06-06 13:07 <ysionneau> well, for some use cases you prefer python rather than C, right?
2014-06-06 13:07 <ysionneau> some people are very much more productive in python or JS than in C
2014-06-06 13:07 <ysionneau> for string manipulations for instance
2014-06-06 13:08 <ysionneau> so I can understand some people would like to be able to write code for uC in python or JS or some language like that
2014-06-06 13:08 <ysionneau> which is "easy" to write
2014-06-06 13:08 <ysionneau> and moreover it's cool to be able to play with the interpreter interactively
2014-06-06 13:09 <sb0> because C is a pain?
2014-06-06 13:10 <sb0> even the problem of concatening strings doesn't have a proper solution with that crap language
2014-06-06 13:10 <whitequark> because C is a truly terrible language
2014-06-06 13:10 <whitequark> Rust is as powerful (for wpwrak: performant) as C, it's not shit, and "Ruby hipsters" are somehow pretty fine with it
2014-06-06 13:11 <ysionneau> is Ruby still a hipster language ?
2014-06-06 13:11 <ysionneau> I would imagine that hipsters would be on to something new and shiny now :)
2014-06-06 13:11 <sb0> define: "hipster language"
2014-06-06 13:11 <ysionneau> a language which attracts hipsters?
2014-06-06 13:12 <whitequark> meh, doesn't matter. what I mean is, the fact that C is hard to use and the fact that its compiler can produce tiny/fast binaries are orthogonal
2014-06-06 13:12 <sb0> well, anything can attract hipsters...
2014-06-06 13:12 <ysionneau> true
2014-06-06 13:12 <ysionneau> especially when it's "new"
2014-06-06 13:12 <ysionneau> and has nice features for rapid development like scaffholding
2014-06-06 13:13 <ysionneau> even if it's usually more a demo stuff than anything else
2014-06-06 13:17 <sb0> I wonder how much a hardware memory manager (malloc/gc) would make sense
2014-06-06 13:18 <sb0> with safe pointers
2014-06-06 13:18 <whitequark> sb0: but you don't *need* hardware to hold your hand there...
2014-06-06 13:19 <sb0> yes, you can have a VM of course, but it's slow
2014-06-06 13:19 <sb0> I know JIT makes it faster
2014-06-06 13:19 <whitequark> VM?
2014-06-06 13:20 <whitequark> have you seen how Rust solves the problem?
2014-06-06 13:20 <whitequark> you don't need a VM to get memory safety
2014-06-06 13:23 nicksydney has quit [Remote host closed the connection]
2014-06-06 13:30 nicksydney has joined #qi-hardware
2014-06-06 13:38 lamrz has joined #qi-hardware
2014-06-06 13:41 <wpwrak> ysionneau: for string-heavy stuff, i use perl. better syntax :)
2014-06-06 13:42 <whitequark> so if you want to have systems software that intensely manipulates strings--say, any old-days protocol, like SMTP or IMAP, ever--you're fucked
2014-06-06 13:44 <wpwrak> well, in this case i have to make a little extra effort. like write a string lib for C. or reuse one i've already written. depends on the task. didn't need heavy string-processing for a while.
2014-06-06 13:44 <whitequark> you should review one day the history of remotely exploitable vulnerabilities for FTP servers, mail servers, DNS servers (especially BIND), ...
2014-06-06 13:45 <wpwrak> most of my programs are the batch type: read all inputs, process, spit out results.
2014-06-06 13:45 <whitequark> every single one RCE in them could not exist if it was written in a memory-safe language
2014-06-06 13:45 <whitequark> tell me again how C is a good systems language
2014-06-06 13:45 <wpwrak> oh, i grew up with ftp exploits ;-)
2014-06-06 13:46 <wpwrak> if you need to do things with strings that make you uncomfortable, encapsulate the tricky functions. just like your critter does somewhere, too.
2014-06-06 13:47 <wpwrak> if you don't feel up to the task of making your own abstractions, look for some library that does it for you and learn that library
2014-06-06 13:47 <whitequark> no amount of encapsulation will save you from use-after-free (for example)
2014-06-06 13:47 <wpwrak> i find it more convenient to just adapt to the situation, exploit the sweet spots
2014-06-06 13:48 <whitequark> or in other words, accidental incorrect usage of the API of that library which the compiler won't find
2014-06-06 13:48 <whitequark> besides, your advice is irrelevant. I certainly admit it is *possible* to write secure code in C
2014-06-06 13:48 <wpwrak> if you're terminally afraid of free, then don't use it in your code. encapsulate it and add run-time checks as needed
2014-06-06 13:48 <whitequark> but in practice this mostly doesn't happen
2014-06-06 13:48 <ysionneau> 15:41 < wpwrak> ysionneau: for string-heavy stuff, i use perl. better syntax :) < *chockes*
2014-06-06 13:49 <whitequark> no amount of encapsulation or runtime checks or even code reviews saved openssl from being a piece of shit
2014-06-06 13:49 <whitequark> it did everything you said
2014-06-06 13:49 <wpwrak> perhaps the main problem of C is that it encouraged unwarranted confidence
2014-06-06 13:49 <whitequark> you could describe it like that, yes.
2014-06-06 13:50 <wpwrak> and no, openssl still exposed too many low-level things. if you want such abstraction, you have to be consistent
2014-06-06 13:50 <whitequark> hardly changes the consequences, which are: if you want to exploit a Linux system, you can
2014-06-06 13:50 <whitequark> remotely, locally, pick whatever you like
2014-06-06 13:50 <wpwrak> (too many) in relation to the quality of the review process and coding standards
2014-06-06 13:51 <wpwrak> there are many ways to make your code secure, but you have to be consistent
2014-06-06 13:52 <wpwrak> btw, the "new heartbleed" is also from the same author. i guess his commits will come under very close scrutiny now
2014-06-06 13:52 <ysionneau> latest changelog showed how many security issues? 6?
2014-06-06 13:53 <ysionneau> crazy :o
2014-06-06 13:53 nicksydney has quit [Remote host closed the connection]
2014-06-06 13:53 <whitequark> you'll also find that he isn't a particularly bad coder (or much less an NSA agent)
2014-06-06 13:53 <wpwrak> which means that he's either losing a job, or he'll learn a lot about himself ;-)
2014-06-06 13:53 <whitequark> just a regular C guy
2014-06-06 13:53 <whitequark> oh oh
2014-06-06 13:53 <wpwrak> let's see what they find
2014-06-06 13:54 <whitequark> wpwrak: http://pastebin.com/uFF9LsFg
2014-06-06 13:54 <whitequark> ugh, paste removed
2014-06-06 13:54 <wpwrak> there are certain very fundamental coding practices that can help you a lot. like making small functions that do one thing and do it correctly
2014-06-06 13:55 <wpwrak> so the heartbleed copying should have been one such function. it would have stuck out immediately.
2014-06-06 13:55 <whitequark> there is also a very fundamental coding practice that eliminates *all* memory-safety bugs, which is strictly better than what you suggest...
2014-06-06 13:55 <wpwrak> the tendency to write long functions doing a ton of things is either laziness, ignorance, or some bad habits learned from C++
2014-06-06 13:56 nicksydney has joined #qi-hardware
2014-06-06 13:56 <wpwrak> C++ being a much inferior language to C
2014-06-06 13:56 <whitequark> it's also hilarious that you crap on C++ while it helps quite a bit with encapsulation that you like so much
2014-06-06 13:56 <whitequark> and factoring common code out
2014-06-06 13:57 <whitequark> if you omit about 99% of C++, you can write good code in it :p
2014-06-06 13:57 <ysionneau> to me C++ code is very hard to follow, but I don't have much experience with it so it might be the reason
2014-06-06 13:57 <wpwrak> nothing wrong with OO techniques. but you don't need new languages for that, C handles them just fine as well
2014-06-06 13:57 <whitequark> actually, there's a lot of things wrong with OO techniques. the advantages of using C++ lie elsewhere
2014-06-06 13:57 <ysionneau> Good old friday troll is coming :) I feel it
2014-06-06 13:59 <wpwrak> C++ encourages poor style. first, it's very hard to determine what your classes really contain. second, you can't break down methods like you break down functions, leading to monster methods.
2014-06-06 13:59 <whitequark> s,C++,OO,
2014-06-06 13:59 <sb0> (new heartbleed) http://underhanded.xcott.com/?page_id=2 ? :)
2014-06-06 14:00 <wpwrak> OO should be used sparingly, where it makes sense. in C++, you feel obliged to use it for everything. hence bad code.
2014-06-06 14:00 <wpwrak> sb0: i see a lifetime achievement award ;-)
2014-06-06 14:09 <whitequark> wpwrak: since you're so good at C, can you find a bug here, which makes the KDF nearly useless? http://pastebin.com/gYMLpVSe
2014-06-06 14:20 <wpwrak> looks correct, C-wise, though not fully defined. there's also an unfortunate mixing of sizes as constants and open-coded numbers
2014-06-06 14:21 <wpwrak> btw, if you want proper type safety for arrays, put them in a struct
2014-06-06 14:23 xiangfu has quit [Remote host closed the connection]
2014-06-06 15:06 xiangfu has joined #qi-hardware
2014-06-06 15:27 FDCX has quit [Ping timeout: 265 seconds]
2014-06-06 15:35 FDCX has joined #qi-hardware
2014-06-06 15:44 <wpwrak> it's of course not strictly portable, but i don't think there are any real platforms with pointers > 128 bits yet. you may want to add an assert, though.
2014-06-06 15:45 <whitequark> wpwrak: it's not correct
2014-06-06 15:45 <whitequark> it's critically wrong, and any code using it would be terribly insecure
2014-06-06 15:45 <wpwrak> as long as your pointers are short enough, it will run fine
2014-06-06 15:46 <whitequark> there's no undefined behavior there, true
2014-06-06 15:46 <wpwrak> and yes, it's obviously not very secure. especially not on machines with small word sizes
2014-06-06 15:46 <whitequark> but it is not correct and you only have to know C to determine why
2014-06-06 15:46 <whitequark> small word sizes, hm?
2014-06-06 15:47 <whitequark> what about them?
2014-06-06 15:47 <wpwrak> because of sizeof(pointer)
2014-06-06 15:47 <whitequark> yeah, that's the bug
2014-06-06 15:47 <whitequark> should've used AES128_KEY_LEN there
2014-06-06 15:49 <wpwrak> or a struct, as i suggested :)
2014-06-06 15:49 <wpwrak> arrays as arguments are generally not a good idea
2014-06-06 16:08 <wpwrak> hmm, is it really necessary to have two chokes on the earpiece ?
2014-06-06 16:09 <whitequark> eh?
2014-06-06 16:10 xiangfu has quit [Remote host closed the connection]
2014-06-06 16:10 <wpwrak> or sorry, wrong channel :)
2014-06-06 16:10 <wpwrak> (trying to decode the n900 design)
2014-06-06 16:27 <eintopf> :)
2014-06-06 16:38 <whitequark> hmm, for my pump I bought a 3A adjustable SMPS for ~$25
2014-06-06 16:38 <whitequark> decided it's more economically efficient to not make one myself
2014-06-06 16:38 <whitequark> based on some Linear thingy... let me look at it
2014-06-06 17:49 <whitequark> http://www.reddit.com/r/AskEngineers/comments/27gfhq/how_do_i_wet_lay_carbon_fiber_kevlar_on_to_my/
2014-06-06 17:49 <whitequark> hmmm, apparently nothing bonds to HDPE, fascinating
2014-06-06 17:51 FrankBlues has joined #qi-hardware
2014-06-06 18:05 sb0 has quit [Ping timeout: 240 seconds]
2014-06-06 18:13 sb0 has joined #qi-hardware
2014-06-06 18:52 lamrz has quit [Quit: Leaving]
2014-06-06 18:53 lamrz has joined #qi-hardware
2014-06-06 19:03 <whitequark> ahahaha, "SMPS" that gets hot at 300mA@6V
2014-06-06 19:04 <whitequark> 50°C in TO-220 (except with 5 legs) at 1.8W input power
2014-06-06 19:04 <whitequark> oh
2014-06-06 19:04 <whitequark> oh wait, it's 300mA@27V, that explains things
2014-06-06 19:31 * whitequark is having fun with the camera: http://i.imgur.com/O4ZTENX.jpg
2014-06-06 19:34 lamrz has quit [Ping timeout: 245 seconds]
2014-06-06 19:34 Jay7 has quit [Ping timeout: 276 seconds]
2014-06-06 19:51 <kyak> thanks god, it's not mirror :)
2014-06-06 19:52 rz2k has quit [Read error: Connection reset by peer]
2014-06-06 19:53 <larsc> were you expecting selfies with sepia filters?
2014-06-06 19:55 * whitequark is offended
2014-06-06 19:56 <kyak> whitequark: i'm just kidding --)
2014-06-06 19:57 <whitequark> (I'm not really offended)
2014-06-06 19:57 lamrz has joined #qi-hardware
2014-06-06 19:58 lamrz has quit [Read error: Connection reset by peer]
2014-06-06 20:01 lamrz has joined #qi-hardware
2014-06-06 20:01 lamrz is now known as 1JTAAC5F6
2014-06-06 20:01 1JTAAC5F6 has quit [Client Quit]
2014-06-06 20:01 <DocScrutinizer05> nasty choke
2014-06-06 20:02 lamrz has joined #qi-hardware
2014-06-06 20:02 <whitequark> what about it?
2014-06-06 20:02 <DocScrutinizer05> well, it's "open"
2014-06-06 20:02 Jay7 has joined #qi-hardware
2014-06-06 20:02 <whitequark> EMF?
2014-06-06 20:02 <DocScrutinizer05> kinda, yes
2014-06-06 20:02 <whitequark> EMI, rather
2014-06-06 20:03 <DocScrutinizer05> it's prolly for "DC", right?
2014-06-06 20:03 <whitequark> it's DC-DC
2014-06-06 20:03 <whitequark> 0~40 to 0~37
2014-06-06 20:03 <DocScrutinizer05> yeah, so you can conveniently check for current with a analog Hall-sensor ;-P
2014-06-06 20:04 <whitequark> hehe
2014-06-06 20:04 <whitequark> hm, noticed I have nothing to gate its input with... damn
2014-06-06 20:04 <whitequark> need a tiny SSR there
2014-06-06 20:04 <DocScrutinizer05> and with a secondary coil nearby you can check for noice and hum on the DC
2014-06-06 20:04 <whitequark> or not even SSR actually, any relay would work.
2014-06-06 20:05 <whitequark> althoooough not actually, no, a regular relay will get its terminals fused shut
2014-06-06 20:06 <whitequark> while disconnecting 1A flowing through a massive inductor
2014-06-06 20:06 <whitequark> (the motor)
2014-06-06 20:07 <whitequark> O_O fuck, SSRs are expensive
2014-06-06 20:15 <DocScrutinizer05> yep, with a proper mosfet you're better off
2014-06-06 20:16 <whitequark> cheapest relay I can find is... $5
2014-06-06 20:17 <whitequark> well. hm.
2014-06-06 20:20 <whitequark> and any inductive loads are conspicuously absent from relay datasheet
2014-06-06 20:20 <whitequark> I bet the contacts *will* get fused
2014-06-06 20:21 <whitequark> contact material claimed AgNi 90/10
2014-06-06 20:21 <whitequark> hm, that should work ok
2014-06-06 20:24 FrankBlues has quit [Quit: Leaving]
2014-06-06 20:43 wolfspraul has quit [Quit: leaving]
2014-06-06 20:44 <DocScrutinizer05> you shouldn't switch inductive loads with a relay, unless you use a clamp diaode
2014-06-06 20:44 <DocScrutinizer05> diode
2014-06-06 20:45 <DocScrutinizer05> or alternatively an RC spark extinguisher
2014-06-06 20:46 <DocScrutinizer05> you said it's DC. Great for R-C
2014-06-06 20:49 <DocScrutinizer05> R rated for not exceeding relay's max I on contact-close, C dimensioned to not exceed charging to voltages > say 100V during the time the contact needs to open, on nominal load of your motor or whatever
2014-06-06 20:50 <DocScrutinizer05> I.E when you have 1A and the contacts need 50mS to completely open, then your C shouldn't charge to >100V in 50ms with 1A current
2014-06-06 20:51 <DocScrutinizer05> R needs to limit current to < say 2A (max current according to datasheet of your relay), at 40V
2014-06-06 21:21 jekhor has joined #qi-hardware
2014-06-06 23:02 sb0 has quit [Quit: Leaving]
2014-06-06 23:20 jekhor has quit [Ping timeout: 245 seconds]