Back
[01:00:34] <feurig> Casper: yeah. I just dont want to read their source code to figure out what they foobard with.
[04:04:50] <earthshine> Morning
[04:42:41] <inflex> evening
[04:59:10] <CapnKernel> wotcha
[05:01:17] * inflex prays for various deliveries tomorrow
[05:01:27] <ziph> Sheesh, none today?
[05:01:39] <inflex> need some 1206 resistors for my CC power board... andI need a motherboard for my LOM... and I need a bunch of JST RCY parts
[05:02:03] <ziph> You need to mount the heads of a few late deliverymen on pikes on your driveway.
[05:02:10] <inflex> ziph: I did actually - got my LOM power boards, a Soanarplus catalogue and... ermm... oh yes, my LCDs
[05:02:30] <ziph> Oh, you ended up with two boards?
[05:02:56] <inflex> for the LOM? Yes, split the boards about 3 revisions ago
[05:05:16] <inflex> latest motherboard, which I'm waiting on, has room for 4 x 1206 or 1 x 1206 + 2 x 2512 resistors, or of course the ultimate solution, a single TO220
[05:05:19] <ziph> inflex: Ever considered doing RF telemetry for RC's?
[05:05:28] <ziph> Heh.
[05:05:40] <ziph> I did that with heatsink mounts on a board recently.
[05:06:03] <ziph> With all the different holes it looked like the board had been around a mob hit.
[05:06:27] <inflex> ziph: gets that way doesn't it - you get so sick of revising boards because parts go out of availability or just don't quite work as you wanted
[05:06:36] <inflex> oh RF telemetry, the R/C market already has that sewn up
[05:06:42] <inflex> most modern 2.4GHz systems have it
[05:07:07] <ziph> They do control over 2.4 Now?
[05:07:21] <inflex> yep - everything is 2.4GHz now
[05:07:25] <karlp> how much range do they get though?
[05:07:29] <inflex> and yep, it's 2 way
[05:07:39] <inflex> still good range, out to 500m~1km
[05:07:46] <inflex> remember, it's line of sight through air
[05:07:51] <karlp> yeah,
[05:08:06] <karlp> what data rate do you get at that range?
[05:08:23] <inflex> depends on the system - but the data /back/ can range from 9600 to 115200
[05:08:31] <inflex> not sure on the frame-rates going _to_ the plane though
[05:08:33] <karlp> 500m to 1k doesn't really sound like much, not for those fly by video camera planes I've seen
[05:08:58] <inflex> but it's at least higher than 50 updates/sec, so probably at least 19200bps or more
[05:09:13] <inflex> karlp: sure, for those people are using some impressive gear
[05:09:17] <inflex> mostly illegal :D
[05:09:33] <ziph> And not flying legally either.
[05:09:33] <inflex> someone recently did a 45km flight I think.
[05:09:45] <inflex> ziph: ja, then they get all pissy when you tell them that
[05:09:58] <inflex> "I'm not hurting anyone - I'm just having fun - it's my RIGHT!"
[05:10:15] <inflex> You should see some of the STUPID stuff a fellow called "Trappy" does
[05:10:20] <ziph> Well, if you do it out the back of butt fudge nowhere then no one will care.
[05:10:28] <inflex> really, it makes you wonder why the govt hasn't just put us on the terror list
[05:10:35] <ziph> But the video I've seen is over suburban areas and VHF flight paths.
[05:10:52] <ziph> Err, VFR flight paths.
[05:11:32] <ziph> And if you're flying in summer there's a high risk of starting massive fires...
[05:11:48] <inflex> http://www.youtube.com/watch?v=M9cSxEqKQ78
[05:11:49] <ziph> So even the back of nowhere isn't such a great place to do it.
[05:14:11] <ziph> Flying over/around cars is about the worst thing you can do.
[05:15:56] <inflex> ja, people go "What the hell was *CRASH*"
[05:16:14] <ziph> inflex: There's one on YouTube of flying 1000ft + over the Perth foreshore and CBD.
[05:16:59] <inflex> don't forget the one that came waaay too close to the Virgin plane during landing
[05:17:53] <ziph> That probably wouldn't do much.
[05:18:10] <ziph> Assuming it wasn't one of those massive RC jets. ;)
[05:27:33] <inflex> wonder if it's plausible to log to 1GB of data?
[05:27:50] <inflex> with an AVR
[05:27:58] <ziph> Why wouldn't it be? :)
[05:28:14] <inflex> shrug...wonderwhat the cost of 1GB of memory would be? wouldn't need to use VFAT
[05:28:44] <ziph> Use an SPI SD card...
[05:28:59] <ziph> And use raw sectors.
[05:29:32] <inflex> nice idea
[05:29:56] <inflex> mmmm... time to google
[05:29:56] <ziph> In Windows you just open the device file the same way you'd open a normal file and read the blocks in.
[05:30:19] <inflex> okay, so Win would see it as a file, as opposed to a file-system
[05:30:25] <inflex> (which is fine, because it would just be one big long file
[05:30:40] <ziph> You can always open a volume device, even if it does have a file system on it.
[05:30:56] <inflex> ja on linux I'd have no problem - but yes, Windows was what I was thinking
[05:31:18] <ziph> Yeah, it's the same as in Linux except that the device handles aren't normally visible in the file system.
[05:31:18] <karlp> fatfs is realllly easy to use
[05:31:47] <karlp> you can use a spi sd card and write files to it. with avr-libc you just open it as a file, write, close, done.
[05:31:57] <karlp> take teh card out of the avr device, stick it in a card reader.
[05:32:18] <inflex> karlp: yeah true... given that I wrote a decoder for MS's OLE format, I figure I could do FAT too (for 1 file)
[05:32:19] <ziph> You're going to need special software to read the telemetry anyhow.
[05:32:31] <inflex> ziph: O_o no... there's no telemetry
[05:32:46] <ziph> What's the data?
[05:33:02] <karlp> no, I mean, don't write it yourself.
[05:33:08] <karlp> bah! what happened to elm-chan.org?
[05:33:11] <ziph> inflex: By the way, they took SPI out of the SD card standard in the newest versions.
[05:33:13] <karlp> it's busted and going to yahoo.com!
[05:33:20] <inflex> volts, amps, temp - I'll have the logging device _on_ the battery
[05:33:34] <inflex> ziph: hmmm.. curious, trying to stop people doing it
[05:34:06] <karlp> inflex: probably because some of thew newer ones want to use two or more channels don't they?
[05:34:07] <ziph> inflex: Probably more to do with simplifying implementations since SPI speeds are now far slower than the speeds the cards will now do.
[05:34:20] <karlp> and yeah, it's getting too fast
[05:34:38] <karlp> ok, it's back:
http://elm-chan.org/fsw/ff/00index_e.html
[05:34:54] <karlp> that's really simple for working with spi cards and fat file systems
[05:37:14] <inflex> woah, nearly 900kbytes/sec O_o
[05:37:45] <inflex> oh, compact-flash
[05:38:02] <ziph> inflex: The ones that don't support SPI are the smaller form factor ones I think.
[05:38:23] <inflex> like microSD?
[05:38:29] <karlp> no, microsd still works on spi
[05:38:30] <ziph> Yeah.
[05:38:35] <karlp> at least the ones we're using
[05:38:40] <inflex> oh okay, what new size arethey dropping to?
[05:39:06] <karlp> ziph: isn't it on the regular sized ones, but in the xdhc what'sit spec?
[05:39:40] <ziph> Hmm, something didn't support SPI any more. :)
[05:41:13] <inflex> how much powr do microSD cards need?
[05:41:35] <karlp> depends on the card and your write patterns iirc
[05:41:52] <inflex> hrmm... that could be a killer in my plans
[05:41:53] <karlp> more than that, I'd have to research
[05:42:04] <ziph> You can dig up datasheets for most of them.
[05:42:18] <inflex> since obviously one doesn't want to kill the battery - if it's anything more than about 0.1mA it's almost dead in the water
[05:42:32] <inflex> unless I store up the data in the AVR's memory, then dump larger blocks
[05:42:36] <ziph> inflex: Log to SRAM and then turn it on occasionally.
[05:43:00] <inflex> ziph: ja... likewise thinking :)
[05:43:30] <inflex> sad thing is, I was thinking of going with something insane like a T25 for this
[05:44:29] <inflex> and 128 bytes won't last me long... but maybe long enough
[05:45:08] <inflex> is there a mechanical diff betwen microSD and microSDTM ?
[05:45:26] * inflex thinks maybe he'll just go with 'standard' SD cards.... since a lot of fat-thumbed people will be using these
[05:49:00] <karlp> inflex: it's going to be way more than 0.1mA to log to external flash
[05:49:33] <inflex> if I can make it -average- that, then I'll be okay
[05:50:06] <ziph> What about compressing the fields a bit too?
[05:53:15] <inflex> I could pack multiple 10 bit ADC fields together
[05:53:23] <inflex> eg, 8 of them into 10 bytes
[05:53:38] <ziph> Don't they tend to be similar to their last readings too?
[05:53:51] <inflex> not always during flight
[05:53:59] <inflex> so you could run out of delta-range
[05:54:36] <ziph> That only costs you an extra bit worst case though.
[05:54:39] <inflex> I suppose you could use 9 bits for delta, and then if b10 is set you know it's the 'real' value
[05:55:30] <ziph> You could also do (for example) 4 bits for a small delta and 9 for a large delta.
[05:55:38] <ziph> Or just huffman the distribution of deltas.
[05:56:03] <inflex> mmmm
[05:56:08] <inflex> plenty of options
[05:56:35] <ziph> I managed to get 3 second GPS tracking reports (send in UDP packets every minute) to under 2 megabyte for an entire months tracking.
[05:56:35] <karlp> moah data!
[05:56:45] <inflex> for sure thoughyou're right, during non-flying (which is almost all the time) the battery would remain effectively constant
[05:56:47] <ziph> sent in UDP...
[05:57:11] <inflex> ziph: so you could have a case where you just don't update until the next change occurs and then you record the new timestamp
[05:57:54] <inflex> then during the "holy crap, everything's happening" times you can go full on
[05:58:38] <inflex> which sortof solves the mA consumption problem too
[05:58:45] <inflex> because during flight time, you don't really care
[05:58:51] <inflex> but during the storage/idle time, you do
[06:01:58] <ziph> inflex: Yeah, I've done it before where in the stream you have "Set default timestamp interval" and then you either have a single bit to indicate if a time delta follows or if it just uses the default time delta.
[06:10:21] <inflex> Now, the real trick for me is to make this thing as cheap as possible
[06:10:23] <inflex> I mean REALLY cheap
[06:10:42] <inflex> if it's going to work, it has to be acceptably cheap to the point where you just get one for every device/pack
[06:10:58] <inflex> hence why I was hoping to go for a T25 or better yet, a T10 :p
[06:10:59] <ziph> How do you feel about moving to China? ;)
[06:11:05] <ziph> What about a PIC?
[06:11:12] <ziph> Or an MSP430?
[06:11:12] <inflex> no thanks
[06:11:30] <inflex> the AVRs are cheap enough - I guess what I mean is, minimal glue components
[06:11:47] <inflex> so, you have the AVR, microSD holder... then not much else, but the timeclock is the issue now
[06:12:20] <ziph> Drift? Or running it while the AVR is sleeping?
[06:12:22] <inflex> RTC is way too expensive
[06:12:45] <ziph> The MSP430 can run timers off of the watch crystal oscillator. :)
[06:12:47] <inflex> AVR with xtal would be okay... so long as the xtal/resonator wasn't too power hugry
[06:13:05] <inflex> ja, the AVR can too - but then how fast doesone have to be to talk to the SD card?
[06:13:25] <ziph> Switch to the internal oscillator for that.
[06:15:25] <inflex> can't change clock source son the fly afaik ?
[06:16:15] <ziph> MSP430 can.
[06:20:34] <inflex> mmmm... no, it'd be stupid for me to retool at this point
[06:20:51] <inflex> I know what I can do - I just need to change the divider on the fly
[06:21:48] <inflex> 1MHz in, run the divider at 256 - then I'm down to a nice slow 4kHz :D
[06:21:56] <ziph> The MSPGCC works, and ships with the programmingtools.
[06:22:15] <inflex> ja,but there's so many other things that I'll have to work out - really, it'd be a major nightmare at this point
[06:22:38] <ziph> Yeah.
[06:22:41] <inflex> if I run off a 8MHz resonator or similar, hit it with the 256 divider, it'll be fine
[06:22:53] <ziph> Plus you might not want to go back to AVR's afterwards. ;)
[06:22:57] * inflex has done on-the-fly divider changing before with other projects
[06:23:16] <inflex> hahah, not sure, you can't get MSP430 in SOT23-6 or MLF10
[06:23:28] <ziph> Nup.
[06:23:34] <ziph> You can get PIC's down to that though. :)
[06:24:01] <inflex> yes well, PIC _would_ be a step backwards
[06:25:42] <inflex> I thikn this can be done.... T25 (so I can use external resonator/xtal), ADC, bitbashed SPI
[06:26:00] <inflex> only about $2 for the microSD holder
[06:26:14] <ziph> If you're going to bitbash it might be simpler just to do the native SD protocol.
[06:26:38] <inflex> think you can do that in 2K?
[06:26:44] <inflex> I suppose if I have to, I can go 4K
[06:26:56] <ziph> Dunno, but you can't do FAT in 2K. :)
[06:27:08] <inflex> well, you can do write-only FAT in 2K
[06:27:18] <inflex> write-only-with-one-file
[06:27:50] <ziph> The simpler the FS code is the less power a burst uses.
[06:28:26] <inflex> urrrrugh, farq... damn, doing the footprints for these microSD holders is no fun
[06:28:27] <ziph> If you're having to navigate a 500MB FAT cluster chain you'll be sitting there for ages.
[06:29:44] <inflex> will just stick to raw data dump for now I think :)
[06:32:46] <karlp> you can get it pretty small....
http://elm-chan.org/fsw/ff/00index_p.html is the "even smaller version"
[06:33:15] <karlp> I'ved used it to do a bootloader from microsd card
[06:33:20] <ziph> How do you append to the end of a 500Mb file in less than several minutes of continuous reading? :)
[06:35:17] <inflex> you cheat and keep the 'last used sector' in memory
[06:35:31] <inflex> remember, this thing never turns off - it's just perpetually on and perpetually appending
[06:36:08] <ziph> You'd still want to handle reboots though.
[06:37:29] <ziph> And without any SRAM to load FA blocks into a fragmented card would require a huge number of reads.
[06:39:50] <ziph> Oh, and even if you have the last written block you also then have to search for free clusters.
[06:46:21] <inflex> interestringly, the microSD holder is about the same size as my current servo logger board
[06:46:33] <inflex> (which uses a m48 + SPI EEPROM
[06:46:56] <ziph> If you use normal size though some PC's come with readers.
[06:47:02] <ziph> Like most Mac's. ;)
[06:49:44] <inflex> ja, got quite a few around here too
[06:49:53] <inflex> most netbooks come with SD readers
[08:44:38] <manoulaw> Hello there. I want to use a 3-pin rotary encoder to adjust the PWM duty cycle on ATtiny13. I have connected pin C to gnd. I connected pin A on a falling edge interrupt and pin B on another input. Both inputs have enabled pull up resistors. When a falling edge interrupt is occurred i have a delay of 2ms to check if the value of pin A is still low (so it wasn't some noise). Then i check the value of pinB. if it is low it means the rotary
[08:44:39] <manoulaw> turned ccw (left) else cw (right). Also i have put 2x100n capacitors on pins A & B for noise reduction. Well the above doesn't work. It seems it looses lot of turns.
[09:55:33] <grummund> manoulaw: could be your noise filtering is causing the missed steps
[10:25:48] * manoulaw is away: auto-away
[10:32:02] * manoulaw is back (gone 00:06:14)
[10:33:22] <LoRez> manoulaw: turn that off in here
[10:33:39] <manoulaw> sry!
[11:11:57] <moe3> hi
[11:12:37] <moe3> do you know what samplingfrequency for ADC the most standard avr could do ?
[11:18:09] <devilsadvocate> moe3: iirc about 37 clocks per sample
[11:53:14] <Casper> moe3: ain't that 125ksps for 10 bits and 250ksps for 8?
[12:05:40] <tomatto_> hello
[12:06:10] <Casper> hell low
[12:06:23] <tomatto_> :D
[12:06:25] <Casper> that's what I ate today: tomatto sanwitch
[12:06:34] <Casper> so, be affraid, very affraid! :D
[12:07:05] <tomatto_> great choose
[12:08:17] <Steffanx> Affraid is the new afraid or … Casper ?
[12:08:26] <tomatto_> please, do you have some tips to regulate brightness of fluorescent lamp with or without avr ?
[12:08:40] <tomatto_> how
[12:08:47] <Casper> nope
[12:09:05] <Casper> unless you are actually making your own ballast...
[12:09:11] <_Shurik_> tomatto: how about mechanical solution?
[12:10:35] <tomatto_> _Shurik_: mechanical solution, what do you mean?
[12:11:31] <_Shurik_> don't even consider it :)
[12:11:55] <tomatto_> i don't understand you
[12:12:17] <_Shurik_> Now, why would you need to regulate brightness of a fluorescent light?
[12:16:04] <tomatto_> _Shurik_: it's needed by customer. set it in the room, in some situations is not needed to set it to max
[12:17:14] <_Shurik_> Is it one of those energy efficient ones, or literally a day-light tube?
[12:17:48] <tomatto_> both of them
[12:18:10] <_Shurik_> Yeah, good question. I know PWM doesn't work on those :)
[12:18:48] <Casper> mechanical... like motorised blinds
[12:18:57] <Casper> block part of it...
[12:19:05] <Casper> bad way, but probably the easiest...
[12:19:13] <Casper> fluorescent ain'T to be dimmed...
[12:19:50] <_Shurik_> Just don't tell that my idea actually is good one. I'll be too extatic
[12:23:07] <tomatto_> i saw situations where fluorescent light are dimmable, but how they do it...
[12:23:22] <Casper> specialised ballast
[12:23:30] <Casper> that I searched online but couln't find
[12:28:27] <tomatto_> so am i
[12:28:47] <tomatto_> unfortunately
[12:29:20] <tomatto_> :(
[12:29:24] <Casper> I found a small inductor calculator that just made me realise one of my mistake
[12:30:14] <Casper> the inductor will charge and discharge at different rate due to the voltage... which is why I partially failed
[12:43:56] <tomatto_> what are you doing?
[12:59:41] <Tom_itx> Casper are you making a regulator?
[12:59:58] <Tom_itx> you can go to several websites and calculate the parts you need
[13:03:09] <Casper> Tom_itx: yeah but the problem is that I have problem to get the right parts, which does cause issues
[13:03:14] <Casper> but wish me good luck
[13:03:23] <Casper> I need to try to return some bolts that got installed
[13:03:30] <Tom_itx> you can find similar ones
[13:03:33] <Casper> the stupid guy at canadian tire gave me the wrong one
[13:03:51] <Tom_itx> well when you go back ask for the smart one
[13:04:36] <_abc_> Interesting, my yahoo mailbox can be opened in ffox but I can't open any messages. This is new (~3 days)
[13:04:47] <_abc_> Same thing in Opera. Very nice.
[13:58:21] <RikusW> anyone have a working -U lock:..... command handy ? or e/h/lfuse will help too
[13:59:12] <RikusW> for avrdude...
[13:59:47] <Tom_itx> http://tom-itx.dyndns.org:81/~webpage/how_to/atmega168/using_avrdude_index.php
[13:59:51] <Tom_itx> there's probably one there
[14:00:03] <RikusW> thanks
[14:00:15] <Tom_itx> or close enough you can figure it out
[14:00:31] <moe3> sorry for that stupid question but a sampling frequency of 15kHz means 15kSPS ?
[14:00:34] <RikusW> I just need to see the format h
[14:00:41] <RikusW> and how exactly to type it
[14:00:48] <Tom_itx> i figured
[14:00:55] <RikusW> there should be examples in the manpage...
[14:01:19] <Tom_itx> i'd address it like the other fuse bits
[14:02:08] <RikusW> -U lfuse:w:0x62:m -u
[14:02:10] <RikusW> thanks
[14:02:29] <RikusW> just needed to know how to use m
[14:02:40] <RikusW> don't want to take chances...
[14:03:32] * RikusW got some angry customers today, they didn't appreciate the hose moving operation and wanted to kill me....
[14:03:39] <RikusW> about 20000 of them...
[14:03:43] <RikusW> or moer...
[14:03:44] <RikusW> more
[14:05:26] <Tom_itx> hose?
[14:05:43] <Tom_itx> why did you hose em?
[14:06:06] <RikusW> bees....
[14:06:15] <RikusW> needed to remove them from a roof...
[14:06:29] <RikusW> got only 5 stings...
[14:06:35] <RikusW> the got into my hat :S
[14:06:42] <Tom_itx> oh
[14:06:44] <moe3> 15kHz = 15kSPS ?
[14:06:50] <Tom_itx> smoke em
[14:06:59] <RikusW> I did
[14:07:06] <RikusW> but it wore off a bit later
[14:07:10] <Tom_itx> are they the 'anrgy' type?
[14:07:15] <RikusW> yes
[14:07:19] <RikusW> not at the start
[14:07:21] <Tom_itx> the 'africanized' bees
[14:07:33] <Tom_itx> they are invading the US too
[14:07:37] <Tom_itx> agressive
[14:07:39] <Steffanx> Better than those american killerbees
[14:07:41] <RikusW> but the ones coming in from the field werent full of honey...
[14:07:59] <RikusW> Tom_itx: so you've worked with bees ?
[14:08:13] <RikusW> or only noticed the african types ?
[14:08:41] <moe3> nobody here who can help me please
[14:08:54] <Tom_itx> RikusW, no but i've heard storries
[14:09:31] <RikusW> Some bees over here are worse than others, and some are just plain crazily aggressive
[14:09:45] <RikusW> others are easy to work with
[14:10:25] <RikusW> moe3: 15kHz = 15kSPS Samples per second ?
[14:10:28] <RikusW> then yes
[14:31:23] <RikusW> Seems ravrprog flash writing is buggy, dont work, crashes the app :(
[14:31:26] <RikusW> and the avr...
[14:34:39] <Steffanx> poor you
[14:37:09] <RikusW> will fix it
[14:37:26] <RikusW> just writes some junk to the avr and at the wrong place too...
[14:53:56] <moe3> @RikusW: Thanks !!
[14:54:52] <moe3> so a at128 can only do max. 15000Hz sampling frequency?
[14:55:05] <RikusW> on the ADC ?
[15:28:39] <tomatto_> can bluetooth server mode with X clients?
[15:32:08] <vectory> come again?
[15:34:08] <RikusW> X clients like x windows ? ! :-P
[15:34:46] <vectory> i would guess, bluetooth can transmitt X sessions, if you tell it to
[15:38:55] <_Shurik_> O.o
[15:39:17] <Casper> you can do data transfert on bluetooth, so I guess you could make it pass tcp data somehow
[15:39:42] <vectory> if that was even the question
[15:39:52] <_Shurik_> PAN or DUN profiles
[17:49:07] <glguy> Is there a way to directly manipulate the "Z" (r30,r31) register via C, or are there simply no guarantees that C would leave the register alone after you manipulated it and inline assembly is the way to go?
[17:49:45] <RA2lover> That sounds more like a #arduino question than an #avr
[17:49:53] <glguy> :(
[17:51:02] <Tom_itx> arduino don't know about asm
[17:51:13] <Tom_itx> they can barely tie their own shoes
[17:52:12] <Tom_itx> i doubt you can with c
[17:52:34] <Tom_itx> but i haven't tried it
[17:55:57] <glguy> I can do this now [asm volatile (""::"z" (address));], and it happens that gcc doesn't need [z] for anything else, so it works; but that just feels a bit fragile :)
[18:26:39] <abcminiuser> glguy, no guarantees
[18:26:53] <abcminiuser> Plus you'd break the C code, it will use the index registers for indirect struct accesses and the like
[21:20:12] <rue_house> if you want an inline chunk of assembler, do the whole process in assembler
[21:20:15] <rue_house> as a function
[21:22:12] <Tom_itx> ok it works
[21:27:36] <karlp> were you talking to another channel tom? ...
[21:28:21] <Tom_itx> never
[21:28:30] <Tom_itx> it keeps ppl guessing
[21:33:10] <Kevin`> inline assembler has a clobber parameter for situations like this, no?
[21:55:52] <abcminiuser> Nearly hit 100 pages in my thesis :P
[21:56:05] <abcminiuser> Three more subsections to go and I'm done, I think
[21:57:06] <Casper> then you'll reread then realise that you forgot 25 pages
[21:58:20] <abcminiuser> Blarg
[21:59:53] <Tom_itx> FINALLY
[21:59:58] <Tom_itx> got the arm toolchain built
[22:34:36] <Valen> abcminiuser: whens it due?
[22:35:05] <Landon> abcminiuser: impressive, that's about the grand sum of pages I've written the past 4.5 years
[22:35:19] <abcminiuser> Valen, Monday
[22:35:24] <abcminiuser> Landon, there's a lot of pics :P
[22:35:26] * Landon notes they were much less interesting topics than a thesis paper should ideally be though
[22:35:31] <abcminiuser> It's only about 70 pages text
[22:35:48] <Landon> "only" :P
[22:35:55] * Valen wrote a 30 page manual in an hour
[22:36:01] <Valen> but its 80% pictures ;->
[22:37:44] <Valen> it does contain firefighting instructions though
[22:37:52] <Valen> its always fun putting those in ;->
[22:37:54] <abcminiuser> Valen, ?
[22:38:01] <Valen> lipoly batteries
[22:38:14] <Valen> instructions are to let it burn and extinguish things around it
[22:38:27] <Landon> I hope those instructions had pcitures
[22:38:32] <Valen> damn!
[22:38:36] <Valen> should have done that
[22:38:45] <Valen> irritates me that phones and laptops lack them
[22:38:58] <Landon> http://www.youtube.com/watch?v=LnjSWPxJxNs I imagine they would have looked something like this
[22:39:15] <Landon> (fast forward to 1:10ish)
[22:39:39] <Valen> this one was funny
[22:40:03] <abcminiuser> Valen, "throw flaming product onto non-flammable surface. Run like hell."
[22:40:15] <Valen> words to that effect
[22:40:32] <abcminiuser> Also who has time to read the manual when the thing's burning a hole in your table?
[22:40:38] <Landon> Moss
[22:40:56] <abcminiuser> "HOLY CRAP. Wait, let me get the manual. Let's see, fire, fire, fi...ah, here it is. RUN!"
[22:41:03] <abcminiuser> Hehe
[22:41:12] <Valen> <- [o;pt
[22:41:19] <abcminiuser> 0118 815 81192 715 3
[22:41:22] <abcminiuser> Or something like that
[22:41:23] <Valen> Cassandra Dunning <damonster@vapourforge.com>
[22:41:28] <Landon> http://www.youtube.com/watch?v=1EBfxjSFAxQ if anyone wants to relive it
[22:41:35] <Valen> wtf
[22:41:51] <Valen> weird shit be goin on with my clipboard
[22:42:02] <Valen> http://www.youtube.com/watch?feature=player_detailpage&v=B-AoAYrEy-o#t=147s
[22:42:13] <Valen> thats a link to a good lipo fire
[22:42:26] <Valen> and i was going to say
[22:42:42] <Landon> that's a good deal more impressive than I thought
[22:42:51] <Valen> I'm a pilot the correct response to any incident is a) fly the plane b) consult the manual
[22:43:24] <Valen> unfortunately most people seem to forget that part A takes precedence over solving the problem
[22:44:05] <Valen> landon lipoly cells are friggin scary ;->
[22:44:19] <Valen> though burning them like that is uncommon
[22:44:39] <abcminiuser> 0118 999 88192 715 3
[22:44:43] <abcminiuser> Getting closer, I think
[22:44:48] <Valen> abcminiuser: ?
[22:45:02] <abcminiuser> Valen, number for the emergency services in IT Crowd
[22:45:30] <Valen> that the weird british one?
[22:45:34] <abcminiuser> At the start of the episode there's an ad on TV that says they changed the emergency number to that long-ass number, which is why Moss can't call them when the table catches fire
[22:45:41] <Valen> lol
[22:45:45] <abcminiuser> Yeah, the american IT crowd was god-awful
[22:46:03] <Valen> i saw a few parts of eps on youtube of the british one
[22:46:04] <Valen> liked it
[22:46:09] <Valen> anyway better make a phone call
[22:46:12] <abcminiuser> Yeah it's really good
[22:46:17] <Valen> the box with the internet in it ;->
[22:46:35] <Landon> only one more special left and it's done :(
[22:46:38] <Landon> if wikipedia is to be believed
[22:51:22] <abcminiuser> Last section last section!
[22:51:31] <abcminiuser> Then I have to go and add in all my references :(
[22:51:51] <Landon> no reference management?
[22:52:30] <abcminiuser> I know what I used, just have to add them to the bibliography, then city them all over the place :S
[22:52:50] <Landon> ah, that method is a pain
[22:54:36] <abcminiuser> Indeed
[23:21:02] <abcminiuser> Achievement unlocked: Thesis draft complete (minux references)
[23:29:18] <geckosenator> anyone used any of the 6 pin avrs?
[23:30:56] <Casper> I think inflex did
[23:31:06] <Casper> you can't use ISP to flash them
[23:31:38] <geckosenator> oh, need to use debug wire?
[23:32:12] <Casper> no idea
[23:32:41] <geckosenator> parallel probably doesnt work
[23:32:44] <geckosenator> not enough pins
[23:32:57] <geckosenator> maybe someday they will make a 1-pin avr
[23:34:31] <Casper> I think abcminiuser or inflex touched them
[23:34:51] <abcminiuser> Casper, that's a damned lie, I didn't touch anybod...oh
[23:35:04] <abcminiuser> Yes, I did have a play with a TINY10
[23:35:37] <geckosenator> how was it?
[23:37:42] <geckosenator> how did you program it?
[23:37:52] <geckosenator> and did gcc work or just asm?
[23:45:43] <Landon> geckosenator: I'm holding out for a wireless avr
[23:46:48] <geckosenator> they had ones with xbee didnt they?
[23:46:57] <geckosenator> but you mean ones with no pins
[23:47:04] <geckosenator> so they receive power wirelessly as well
[23:47:22] <Landon> indeed
[23:47:45] <Landon> bonus points if the programmer comes in a magic wand form factor
[23:48:37] <geckosenator> maybe just have a light sensor on top to receive power and data