2015-06-04 00:32 FDCX_ has quit [Ping timeout: 240 seconds] 2015-06-04 00:45 ccnnjj has joined #qi-hardware 2015-06-04 01:11 archang has joined #qi-hardware 2015-06-04 01:35 arossdotme has quit [Ping timeout: 245 seconds] 2015-06-04 01:35 atommann has joined #qi-hardware 2015-06-04 01:48 arossdotme has joined #qi-hardware 2015-06-04 02:11 atommann has quit [Ping timeout: 265 seconds] 2015-06-04 02:23 wej has quit [Ping timeout: 248 seconds] 2015-06-04 02:27 atommann has joined #qi-hardware 2015-06-04 02:28 wej has joined #qi-hardware 2015-06-04 02:34 infobot has quit [Read error: Connection reset by peer] 2015-06-04 02:35 infobot has joined #qi-hardware 2015-06-04 02:40 xiangfu has joined #qi-hardware 2015-06-04 02:45 fengling has joined #qi-hardware 2015-06-04 02:49 nicksydney has joined #qi-hardware 2015-06-04 03:13 nicksydney has quit [Ping timeout: 244 seconds] 2015-06-04 03:14 nicksydney has joined #qi-hardware 2015-06-04 03:34 nicksydney has quit [Ping timeout: 244 seconds] 2015-06-04 03:37 nicksydney has joined #qi-hardware 2015-06-04 03:39 nicksydney has quit [Read error: Connection reset by peer] 2015-06-04 03:42 nicksydney has joined #qi-hardware 2015-06-04 03:47 nicksydney_ has joined #qi-hardware 2015-06-04 03:47 nicksydney_ has quit [Read error: Connection reset by peer] 2015-06-04 03:48 nicksydney has quit [Ping timeout: 272 seconds] 2015-06-04 04:45 rjeffries has joined #qi-hardware 2015-06-04 05:22 jekhor has joined #qi-hardware 2015-06-04 06:14 jekhor has quit [Ping timeout: 265 seconds] 2015-06-04 07:05 fengling has quit [Ping timeout: 265 seconds] 2015-06-04 07:13 fengling has joined #qi-hardware 2015-06-04 07:24 fengling has quit [Ping timeout: 265 seconds] 2015-06-04 07:25 wej has quit [Ping timeout: 246 seconds] 2015-06-04 07:25 fengling has joined #qi-hardware 2015-06-04 07:29 arhuaco has quit [Read error: Connection reset by peer] 2015-06-04 07:30 arhuaco has joined #qi-hardware 2015-06-04 07:31 fengling has quit [Quit: WeeChat 1.1.1] 2015-06-04 07:32 wej has joined #qi-hardware 2015-06-04 07:44 atommann has quit [Ping timeout: 246 seconds] 2015-06-04 08:22 jekhor has joined #qi-hardware 2015-06-04 08:32 atommann has joined #qi-hardware 2015-06-04 08:58 mirko has joined #qi-hardware 2015-06-04 08:58 mirko has quit [Client Quit] 2015-06-04 08:58 mirko has joined #qi-hardware 2015-06-04 09:08 zcrc has joined #qi-hardware 2015-06-04 09:13 fengling has joined #qi-hardware 2015-06-04 09:56 atommann has quit [Quit: Leaving] 2015-06-04 10:24 wej has quit [Ping timeout: 248 seconds] 2015-06-04 10:29 wej has joined #qi-hardware 2015-06-04 11:05 zcrc has quit [Quit: AtomicIRC: The nuclear option.] 2015-06-04 13:00 wej has quit [Ping timeout: 246 seconds] 2015-06-04 13:08 wej has joined #qi-hardware 2015-06-04 13:42 pcercuei has joined #qi-hardware 2015-06-04 16:10 $2M USD raised against $50K USD goal. C.H.I.P. will happen. (Uses lower end Allwinner ARM based SoC) 2015-06-04 16:10 https://www.kickstarter.com/projects/1598272670/chip-the-worlds-first-9-computer/ 2015-06-04 16:15 super cool, yet another closed source cpu based hardware o/ 2015-06-04 16:19 composite video output? Get real 2015-06-04 16:24 hehe. great reactions ;-)) 2015-06-04 16:27 i wonder if this simple adjustable regulator could actually work: https://neo900.org/stuff/werner/tmp/cmpreg.pdf 2015-06-04 16:28 the theory is that the comparator opens the p-FET until Vout ~ Vin (~ = approximately equal). then it closes. when the load discharges the silo capacitor, Vout drops and the comparator opens again 2015-06-04 16:28 so far the theory. the question is whether this would actually work or whether i'd get mad oscillations, etc. 2015-06-04 16:30 overshoot should be around td * Imax / C where td = propagation delay of the comparator, Imax = maximum current through the FET, and C = the capacitance of the capacitor 2015-06-04 16:33 xiangfu has quit [Remote host closed the connection] 2015-06-04 16:35 so even if we assume an extreme worst case of Vout = 0, with Ron = 1 Ohm, C = 100 uF, and td = 1 us, that would be 1 us * 3.3 A / 100 uF = 33 mV 2015-06-04 16:39 what puzzles me is that nobody seems to use this sort of regulator circuit. seems pretty ideal if you need a programmable reg, already have DAC and comparator (common in many MCUs), and don't need huge currents 2015-06-04 17:56 wpwrak: oh well, I can say what would be wrong in my view 2015-06-04 17:56 (though it's pretty much EE 101 so I would be surprised if you haven't considered that still?) 2015-06-04 17:57 your "equivalent circuit" for the FET relies on an invalid assumption. that is, that the turn-on/turn-off time of the FET is insignificant 2015-06-04 17:58 you miss a resistor right after the comparator, which will be required to bring the current through the pin in line to absolute maximimum ratings of the MCU 2015-06-04 17:58 which will limit the charge/discharge rate of the gate. 2015-06-04 17:59 thus, you will operate the FET in the region where it's least efficient pretty much all the time 2015-06-04 17:59 jekhor has quit [Ping timeout: 246 seconds] 2015-06-04 18:00 in the best case you will get, well, a linear regulator, not entirely unlike lm317 2015-06-04 18:00 wpwrak: https://cds.linear.com/image/7413.png 2015-06-04 18:00 looks familiar, isn't it? 2015-06-04 18:09 wpwrak: oh, for that matter, tl431 is pretty much that too, except also with a BJT 2015-06-04 18:09 I'm guessing a p-FET is too inefficient in this case, and an n-FET would require a dedicated gate drive 2015-06-04 18:12 wpwrak: http://www.ti.com/lit/ds/symlink/lp2975.pdf does exactly what you describe 2015-06-04 18:13 they seem to have needed a more complicated control circuit for ripple rejection 2015-06-04 18:14 ah, no, nope, the second opamp is for overcurrent protection 2015-06-04 18:24 (turn on/off time) naw, it should only not be excessively slow. the comparator also has delays in the tens if not hundreds of nanoseconds. so you can just add any FET delay to the comparator's td 2015-06-04 18:25 but that's not about FET delays. 2015-06-04 18:25 (resistor) FETs don't need that, only BJT ;-) 2015-06-04 18:25 but of course they do 2015-06-04 18:26 not unless ~1 uA is a problem :) 2015-06-04 18:26 I am not talking about steady state 2015-06-04 18:27 ah, i see. naw, even then it should be fine. you get a few MHz, tops. that should be pretty negligible. 2015-06-04 18:27 the first is the turn-on transient 2015-06-04 18:27 which /can/ kill an MCU's output cascade 2015-06-04 18:27 like, i have myself killed a few MCU pins before i figured that out 2015-06-04 18:27 it's pretty reliable. 2015-06-04 18:27 you need at least an ohm there or something. 2015-06-04 18:28 the second is the average dissipated power at your "few MHz", which is actually a ton 2015-06-04 18:28 let's calculate 2015-06-04 18:29 e.g., the DMG1013T has a "total gate charge" of 580 pC 2015-06-04 18:30 and its threshold voltage? 2015-06-04 18:30 [0.5, 1] V 2015-06-04 18:30 900mΩ at -2.5V 2015-06-04 18:30 or well 2015-06-04 18:30 yes 2015-06-04 18:30 really, what your MCU runs on? 2015-06-04 18:30 3.3 probably 2015-06-04 18:31 yes, 3.3 V 2015-06-04 18:32 (LP2975) neat ! :) 2015-06-04 18:32 hrm 2015-06-04 18:33 0.58mA 2015-06-04 18:33 negligible :) 2015-06-04 18:33 seems you're right 2015-06-04 18:33 maybe you get this sort of trouble with larger FETs 2015-06-04 18:33 this one is pretty much as small as it gets 2015-06-04 18:34 (for that kind of form factor) 2015-06-04 18:34 yeah, that's where my guess was coming from 2015-06-04 18:34 I still think you won't be able to get it to switch that fast and it will work as a linear reg 2015-06-04 18:35 but that's just another guess 2015-06-04 18:35 try it 2015-06-04 18:35 I wonder what the effective resistance of the MCU pin driver is? 2015-06-04 18:36 200 Ohm 2015-06-04 18:38 8 MHz 2015-06-04 18:38 I dunno. 2015-06-04 18:38 now I'm interested. 2015-06-04 18:39 build it already 2015-06-04 18:40 ;-)) 2015-06-04 18:41 i guess something like 10 uF may even be enough there 2015-06-04 18:44 let's be generous, 22 uF 2015-06-04 19:24 hi 2015-06-04 19:50 pcercuei has quit [Ping timeout: 250 seconds] 2015-06-04 20:12 pcercuei has joined #qi-hardware 2015-06-04 20:14 did anybody ever see that two GPIO pins are connected together, in firmware one as output the other as input. And then they making some handshake algorithmn to confirm that the firmware running on the right board? :-/ 2015-06-04 20:15 makes no sense for me 2015-06-04 20:15 could be for identifying board variants, with different boards having different such connections 2015-06-04 20:47 wej has quit [Ping timeout: 246 seconds] 2015-06-04 20:56 wej has joined #qi-hardware 2015-06-04 21:32 mhh 2015-06-04 21:51 wej has quit [Ping timeout: 248 seconds] 2015-06-04 21:58 Jay7 has joined #qi-hardware 2015-06-04 22:06 wej has joined #qi-hardware 2015-06-04 22:29 arhuaco has quit [Ping timeout: 245 seconds] 2015-06-04 22:33 roh has quit [Ping timeout: 245 seconds] 2015-06-04 22:34 roh has joined #qi-hardware 2015-06-04 22:35 Luke-Jr has quit [Excess Flood] 2015-06-04 22:35 Luke-Jr has joined #qi-hardware 2015-06-04 22:39 arhuaco has joined #qi-hardware 2015-06-04 22:41 uwe_mobile__ has quit [Ping timeout: 245 seconds] 2015-06-04 22:41 uwe_mobile has joined #qi-hardware 2015-06-04 23:03 whitequark: 1 V into 100 Ohm: http://downloads.qi-hardware.com/people/werner/cmpreg/static/ 2015-06-04 23:04 (fast mode, minimum hysteresis) 2015-06-04 23:06 the over/undershoot look more like measurement effects than anything else. lemme check if the probe compensation is still good ... 2015-06-04 23:22 hmm. that was not a good idea. now it's much worse :-( 2015-06-04 23:33 pro tip: the DMG1013T acts erratically after being shorted and emitting smoke