Back
[03:42:23] <inflex> woooo
[03:42:24] <inflex> new product
[03:42:38] <inflex> http://dxp.me/i/SFUSE1.jpg ... just a simple little thing
[05:05:07] <karlp> inflex: what is that? a capictor with plug leads dipped in plastic?
[05:09:08] <inflex> what? erm... oh, right, it's hotglue on the wires, then all shrunk in heatshrink of course
[05:11:14] <karlp> SFUSE?
[05:11:21] <karlp> no, I mean, what do you do with it?
[05:11:38] <inflex> ooooh, it's for servo leads on R/C planes
[05:11:51] <inflex> it has multiple tasks -
[05:12:20] <inflex> boosts the servo signal (there's a 1-ch buffer on there), has a fuse on the other side, also has a blown-fuse LED, and of couse the cap adds decoupling
[05:12:35] <inflex> some ppl will want a blow fuse, others will want a polyfuse
[05:13:59] <karlp> why would anyone not want a polyfuse?
[05:15:02] <inflex> because people sometimes want to know that something went wrong "up there"
[05:15:56] <inflex> it depends on what camp you fall in to regarding the damage scenario
[05:15:58] <karlp> the crashing plane doesn't tell them that?
[05:16:16] <inflex> if you lose an aileron, rudder, gear or throttle servo, you can likely make it back
[05:16:26] <inflex> only if you lose the elevator are you pretty much fscked
[05:16:29] <karlp> actually, yeah, never mind, all serious hobby groups seem to get into their own worlds :)
[05:17:20] <inflex> the "theory" is, if the servo blew the fuse, then it was likely something that'd have bought the plane down irrespective - at least by blowing it you have a chance for the rest of the system to continue
[05:17:41] <inflex> (by pulling all the flight gear down from the short-circuit)
[06:26:13] <Tom_itx> inflex, make one so that 'if something happens up there' it explodes
[06:26:22] <inflex> hehehe, easy enough to do
[06:50:17] <inflex> Tom_itx: ordered my tiny OLED displays today
[06:50:43] <inflex> Tom_itx: 96x16 pixels in a tiny 21 x 3.5mm window
[07:42:27] <Valen> product idea for inflex
[07:42:37] <Valen> laser tag system that turns smoke on when hit
[07:43:39] <theBear> what kinda smoke ? it'll need a lotta refills or a stupid big battery
[07:45:29] <Valen> i figured it'd probably only work on "gas" planes
[07:45:47] <Valen> make FPV dogfights way cooler ;->
[07:46:32] <inflex> Valen: yeah, would do
[07:46:40] <inflex> for FUGS SAKE
[07:46:50] <inflex> this little inductor burns my finger too
[07:47:06] * Valen was looking for some beefy inductors
[07:47:17] <Valen> found some in some slim packages good for a few A
[07:47:26] <Valen> though with 60C temp rise
[07:47:34] <Valen> probably too big for you though lol
[07:47:42] <Valen> 8mmx8mmx4mm
[07:47:58] <inflex> ugh, yeah, I only need 1.5~2A
[07:50:42] <inflex> gharr... the others are 12x12mm
[07:52:41] <inflex> ag, this is obscene... fugging inductors
[07:52:41] <Valen> how much you need?
[07:52:43] <inflex> I need shielded
[07:53:13] <inflex> specs I need, two sorts.... 1.8uH, 6.8uH, max sizeI can handle is 6x6mm, I need 1.5~2A capable, up to 1.6MHz switching
[07:53:19] <inflex> the ones I have are ~100kHz :(
[07:54:06] <jacekowski> at 1.6Mhz you have skin effect that has to be taken into account
[07:54:19] <jacekowski> not very strong
[07:54:32] <jacekowski> but you have to start thinking about it
[07:56:10] <Valen> 1.6mhz might start to be an issue
[07:56:18] <Valen> might be better off with a few smaller ones
[07:58:11] <karlp> what are you switching?
[07:58:24] <inflex> http://au.element14.com/bourns/srr0604-100ml/inductor-power-10uh-20-1-3a/dp/1929700 <=- I could _just_ squeeze one of these on... a little bit of an overhang
[07:58:30] <inflex> (well, that family)
[07:58:41] <inflex> it's for a SMPS, boosting single cell lipo to 5V
[07:58:55] <karlp> and it needs to be 1.6 Mhz?
[07:59:14] <inflex> no, that's what the TS1935 controller runs at ---- or I can use the LT1935 which runs at 1.2MHz
[07:59:38] <karlp> or, look for another one, that runs a lot slower.....?
[07:59:49] <inflex> http://au.element14.com/bourns/srr0604-6r8ml/inductor-smd-power-6-8uh-2-05a/dp/1612714 <=- this looks like it'll do the job
[08:00:27] <inflex> karlp: the board is only designed to cope with either of those two controllers
[08:00:33] <inflex> http://dxp.me/i/BACALL.jpg
[08:00:59] <karlp> you built the board before you found an inductor?
[08:01:40] <inflex> I had found an inductor - but it wasn't the right spec as I've since found out tonight
[08:02:28] <inflex> these are proto boards anyhow - I can just widen the board another 1mm to fit the 6.5x6.5 size one
[08:05:22] <inflex> cheaper for me to just spin another $14 for a new batch
[09:08:06] <inflex> grr
[09:09:31] <CapnKernel> inflex: What's up?
[09:11:45] <inflex> oh, I thought it was actually my internet down - but it seems it's just no one was talking in here :D
[09:12:02] * inflex looks at his next project... logger... can't build it today alas... no SPI EEPROM :(
[09:12:21] <CapnKernel> inflex: I missed the part where you were talking about the need for a respin.
[09:13:02] <inflex> CapnKernel: oh, right - just that to make it fit the inductor I should have used - my board accepted up to 5x5mm, but I need to take 6.5x6.5
[09:13:27] <inflex> (can't find any shielded 5x5mm 6u8H 1~2MHz inductors @ 1.5~2A)
[09:14:03] <CapnKernel> Do you already have the boards and inductors? Or is this a design-phase problem?
[09:14:30] <inflex> proto #1 -
http://dxp.me/i/BACALL.jpg
[09:14:56] <inflex> everything else works great
[09:28:30] <CapnKernel> Are you reflowing that board?
[09:28:33] <inflex> yes
[09:28:40] <CapnKernel> Neat!
[09:29:05] <inflex> obviously the pin-headers and electrolyte are added after, but the rest is in the reflow, including the buzzer
[09:42:02] <inflex> Still paining though over the cost of the LT1935's... obscenely expensive
[09:42:28] <inflex> $8+ at E14 compared to $1.50 for the TS1935 (Taiwan clone)
[15:09:05] <rukuartic> Oy. :< Any chance I could get some help on some tiny44 code?
[15:09:14] <rukuartic> http://pastebin.com/raw.php?i=FsMGVCmY For some odd reason, the second loop is never executing.
[15:10:57] <TwisteR> rukuartic: uint8_t can not handle the value of 256, it overflows into 0
[15:11:04] <TwisteR> you should use 255 instead
[15:11:36] <rukuartic> it never gets to 256
[15:11:42] <rukuartic> ...ooooh.
[15:11:47] <rukuartic> ahurrrr. <____<;
[15:12:04] <madsy> You need moar bits
[15:12:07] <madsy> :-)
[15:12:19] <rukuartic> I was *just* running into this in my FPGA course.
[15:13:10] <TwisteR> one byte = [0..255] = total of 256 values
[15:13:18] * rukuartic face desks
[15:13:23] <TwisteR> :D
[15:53:22] <rukuartic> TwisteR: You're my hero. Thaaaank yoooou ;~;
[15:55:49] <jacekowski> TwisteR: just change it to for(i = 0; i <= 255; i++) {
[16:12:50] <TwisteR> jacekowski: thanks, but that was not my question :-)
[16:32:46] <grummund> rukuartic: add -Wall -Wextra to your compile options and it won't happen again
[16:35:02] <grummund> also the 2nd loop fails because uint8_t will never be negative (which is also caught by -Wextra)
