<DocScrutinizer>
either you 'tune' the circuit, means in-Z == trace-Z == out-Z. Or you feed 'asym' with very low source-Z and proper termination, so the missmatch has no adverse side effects
<DocScrutinizer>
wpwrak: sorry, I'm not cmpetent to answer specific detail questions wrt that
<wpwrak>
hmm, on rx, the differential impedance of the transceiver is 100 Ohm.
<wpwrak>
nothing specific to find about TX.
<DocScrutinizer>
there's programs to calculate such things, and in appnotes the chip manufs clearly signal which parts need to be tuned. This is based on their knowledge about chip fan-out/fan-in or Z properties, and on simply analyzing lab proto boards
<wpwrak>
the docs are a bit fuzzy. and contradict each other :)
<DocScrutinizer>
as a general rule of thumb, you don't care about tuned lines, when the loss caused by mismatch is irrelevant. Then you just make sure you don't run into other truble by line ringing (reflections or standing waves)
<wpwrak>
e.g., ti don't specify anything. they give a balun using transmission lines for inductors in their reference design. if you dig further, they do mention an integrated balun in one web forum. and one rf component maker even has a balun supposedly designed for that chip.
<wpwrak>
(information is similarly confusing with atmel, although with less secrecy)
<DocScrutinizer>
:nod:
<wpwrak>
okay. what would be typical mistakes to avoid when ringing may be an issue ?
<DocScrutinizer>
RF design is black magic - you're supposed to have learnt that lesson :-P
<wpwrak>
yeah yeah :)
<wpwrak>
i don't aim at cooking up a perfect fcc- and etsi-pleasing design that's ready for MP :)
<DocScrutinizer>
wpwrak: typical mistakes: too long traces, too high terimation Z, to high source Z
<DocScrutinizer>
termination*
<wpwrak>
i'll be happy already if i emit more power around the carrier than at the harmonics and get a bit of range :)
<DocScrutinizer>
missing clamp diodes (if digital signal)
<wpwrak>
(z) one end is given by the antenna, 50 R. the other is defined by the balun. feed line is ~10 mm in total.
<DocScrutinizer>
so design it that way. If you want to do a fancy, design 5..10 PCBA with a range of trace geometry, and check which performs best
<wpwrak>
yeha, "try a few things and see what works best" does indeed look like the way to go
<DocScrutinizer>
(in the end of the day that's what industry at large does as well)
<wpwrak>
luckily, i can replace some of the small chips with an integrated balun, so there will be fewer knobs to turn. should also generally perform better.
<DocScrutinizer>
if peak performance is at either end of your range, you should go for another set
<DocScrutinizer>
also, as a catch-oops, usually you see unpopulated Pi-filters at start and end of tuned traces
<wpwrak>
yup. right now, i have suckish reach. barely makes it room to room. interestingly, one direction works much better than the other. (the two boards have some small component variations, that's probably why)
<wpwrak>
(pi) that may be for fcc compliance
<DocScrutinizer>
if after start of first batch of 10k PCB it turns out the mismatch is too severe, you always can throw a bead and 2 C at it
<wpwrak>
i saw this approach in many app notes. first they design and simulate the perfect circuit. then they build it and throw in filters until the unwanted harmonics and stuff are small enough to pass certification.
<DocScrutinizer>
yep. usual SOP
<wpwrak>
well, my board is so small that the unpopulated pi filter would already cover most of the feed line :)
<DocScrutinizer>
the Pi are for SWR / Z matching though
<wpwrak>
there is actually one at the end
<DocScrutinizer>
you see these (usually) unpopulated Pi at every RF design antenna foot point
<DocScrutinizer>
in case antenna impedance changes later on, to what it was during proto tests
<DocScrutinizer>
really *every*
<DocScrutinizer>
each BT or WLAN module, each GSM design
<wpwrak>
so they place a 0R ? or use a transmission line as inductor ?
<DocScrutinizer>
0R
<DocScrutinizer>
and the 2 C are NC
<wpwrak>
i've seen one antenna design recommend a LC termination ("half-T")
<DocScrutinizer>
hmm, you do this if you know in advance your antenna is detuned
<wpwrak>
they do show remarkably better performance with the LC in place ;)
<DocScrutinizer>
sometimes you simply cant get a lambda/4 or whatever
<wpwrak>
ah, and how close can/should the antenna be to the transceiver ? is there a minimum clearance one would normally try to observe ?
<DocScrutinizer>
not to my knowledge
<DocScrutinizer>
usually the closer the better
<wpwrak>
kewl
<DocScrutinizer>
footpoint that is
<DocScrutinizer>
:-)
<DocScrutinizer>
antenna tip should be max free air around in all directions
<wpwrak>
should short feed lines be bracketed by GND ? or is the ground plane underneath sufficient ?
<DocScrutinizer>
should suffice
<wpwrak>
hmm, the definition of "antenna tip" may be a bit tricky in my case :)
<wolfspraul>
it's a bit delayed, first eggdrop only flushes the log file every few minutes I think, and then mostly the cron job only runs every 30 minutes
<DocScrutinizer>
aaah, so the cronjob is introducing the enormous lag
<wpwrak>
oh, i could have repeated them :)
<DocScrutinizer>
I didn't know there were any, wpwrak :-)
<wolfspraul>
I can change the cron to run faster
<wolfspraul>
the next thing I plan to add to qi-bot is an opt-out list of nicknames, so the bot will automatically discard all msgs from people who don't want to be logged
<DocScrutinizer>
yay
<wolfspraul>
but it's not the #1 on my priority list right now, so I'd say it will be a few months until I get to it, unless someone else steps up
<wolfspraul>
well but for discussions like the one between you and wpwrak, I think it's really great to keep them archived :-)
<DocScrutinizer>
wolfspraul: put logbots /ignore list to purpose ;-D
<wolfspraul>
so I hope you won't make use of the opt-out feature once we have it
<wolfspraul>
DocScrutinizer: does freenode already have something that prevents your msgs from going to a particular (logging) nick?
<DocScrutinizer>
now for ti.com
<DocScrutinizer>
wolfspraul: I'm agnostic of the particular ways /ignore is implemented, but wouldn't be surprised it's server side
<DocScrutinizer>
/mode #qi-hardware +i wolfspraul
<wolfspraul>
k I'll look into it one day
<DocScrutinizer>
maybe
<DocScrutinizer>
can't remember right now
<DocScrutinizer>
mompls
<wpwrak>
there's no feature under the sun someone hasn't implemented in irc yet ;-)
<wpwrak>
| i have the left side blocked with the circuit and the feed line goes around. not sure how horrible this is in the general scale of things.
<wpwrak>
| of course, nobody has a useful antenna design that's fed from the short side :-(
<wpwrak>
these were the last three lines
<DocScrutinizer>
what's short side and left side in your world?
<wpwrak>
if you look at my pcb pictures, left is left, etc.
<DocScrutinizer>
on a general note - PCB antenna designs are very sensitive to *any* change of geometry
<wpwrak>
left and right are short, top and bottom are long.
<wpwrak>
i didn't touch the geometry. just the surroundings :)
<DocScrutinizer>
you need to keep the whole design incl feedpoint and adjacent gndplanes
<DocScrutinizer>
e.g you can't add gndplanes to top, right or bottom, and you need to keep the full gndplane (edge, at least) on left side
<DocScrutinizer>
sorry didn't look at your design
<DocScrutinizer>
now I did. Nope that won't pan out
<DocScrutinizer>
the GND plane parallel to the short fat antenna branch is way too close
<wpwrak>
hmm. feed and all that are where they should be. how close can i go with gnd on the left ?
<wpwrak>
and would it help if i put the gnd zone at, say, a 45 deg angle ?
<DocScrutinizer>
max ~1.5 of the general structure detal size, I'd guess from my guts. So about  size of one of the "squares" of meander * 1.5
<wpwrak>
also, does the gnd that's too close affect rx and tx in about the same way or does one suffer a lot more ? (e.g., i would suspect that it hurts tx a lot more)
<wpwrak>
okay, that should be feasible. parallel to the short side or angled ?
<DocScrutinizer>
sorry, please rephrase
<DocScrutinizer>
(affect) both virtually same
<wpwrak>
1) in the current design, with the gnd too close to the antenna, would that gnd distort/weaken emissions and receptions roughly in the same way ?
<DocScrutinizer>
(affect) both virtually same
<wpwrak>
2) we assume the lower left corner of the antenna is at coordinates (0, 0), should the edge if ground plane run parallel to the short side, (-d, 0) to (-d, h) ?
<wpwrak>
d = distance gnd plane to antenna. h = "height" of antenna
<wpwrak>
or would it be better if i make it (-d+h) to (-d, h) ? i.e., at a 45 deg angle, but the closest point of the gnd plane would be closer to the antenna this way
<DocScrutinizer>
parallel
<wpwrak>
kewl. that's easier :)
<wpwrak>
btw, i don't think the crystal in the board on the picture worked :) had to reflow the critter for better alignment. first time i actually had some successful use for my hot air pen :)
<DocScrutinizer>
Small changes of the antenna dimensions may have large impact on the performance. Therefore it is strongly recommended to make an exact copy of the reference design to achieve optimum performance
<wpwrak>
(hmm, need to add a filter for backup files to fpd2pdf)
<wpwrak>
d4 ?
<DocScrutinizer>
also amazing: even while there's (of course) no gndplane under the antenna structure, still they recommend >> It is also recommended to use the same thickness and type of PCB material as used in the reference design. Information about the PCB can be found in a separate readme file included in the reference design. To compensate for a thicker/thinner PCB the antenna could be made slightly shorter/longer.<<
<DocScrutinizer>
your design is missing upper gnd plane
<wpwrak>
ah ... D1 as a dimension
<DocScrutinizer>
page 4, figure 3
<wpwrak>
i keep that clearance. but it's a lot less than what you're suggesting
<wpwrak>
the upper gnd is a bit mysterious
<wolfspraul>
what if the board Werner is designing is integrated into another bigger pcb (the one we currently have behind the lcm)?
<wolfspraul>
if thickness matters - I think the PCB that currently is behind the LCM is rather thin
<wpwrak>
i read figure 3 as not having gnd there. but then, on the picture of their real board, there is a gnd plane
<DocScrutinizer>
>> The size of the ground plane affects the performance of the PCB antenna. Connecting the USB dongle to a computer increases the size of the ground plane and thus the performance is affected. Figure 5 shows how the performance is affected when the USB dongle is...<<
<wpwrak>
wolfspraul: it;s very close to the 0.8 mm i use
<DocScrutinizer>
(lot less than what you're suggesting) yup. Even I can fail
<wpwrak>
DocScrutinizer: (size of gnd plane) yeah. big computer = better. that's why i want to be close to the lcm. it's not much but better than nothing.
<wpwrak>
DocScrutinizer: so you think keeping it that close is acceptable ? ti don't say specifically that it's okay to put something nearby. they just strongly suggest that nothing should be in that area.
<wpwrak>
or, rather, nothing but the pcb dielectric
<DocScrutinizer>
I'd keep it away, though in theory it might be irrelevant, given D1 keeps minimum of 0.50mm
<DocScrutinizer>
in the end that fat trace has a GND via, which I wasn't aware of first instance
<wpwrak>
okay. a few more mm can't hurt anyway.
<DocScrutinizer>
so parasitary capacitance to nearby gndplane might be less of an issue
<wpwrak>
(gnd via) rf is spooky to measure. all things are "shorted" to ground ;-)
<wpwrak>
(to measure with a digital multimeter)
<DocScrutinizer>
yeah X-P
<DocScrutinizer>
put your DMM in your attik as long as dealing with RF
<DocScrutinizer>
useless equipment
<wpwrak>
okay, so we have the transmission line and the upper ground plane. i also need to check their pcb thickness. i have it something in the back of my head that 0.8 mm are okay, but i'm now no longer sure if i took that from ti or just from compatibility with the lcm's pcb.
<wpwrak>
it's still good for testing traces ;-)
<DocScrutinizer>
wpwrak: you can have a short (about 2..3 times trace width) parallel to gndplane 'serife' at long end of antenna (like a L ) and then dremel away successively until antenna is tuned
<DocScrutinizer>
(next to "W2 <->")
<wpwrak>
you mean extending from the end of the antenna towards the right ?
<DocScrutinizer>
yep
<DocScrutinizer>
next to arrow tips of W2 and L1, to the right, length suggested 2 * W2
<DocScrutinizer>
parallel to "<->" ow D3
<DocScrutinizer>
of*
<wpwrak>
and now the big question: how do i tell when my antenna is tuned ? :) that is, with my modest measurement apparatus ?
<DocScrutinizer>
that's the most challenging part, and the reason we got antenna houses doing that for us ;-D
<wpwrak>
grmbl :)
<emeb>
wpwrak: what test equipment do you have?
<DocScrutinizer>
probably measuring exact dBm at a given never changing distance with a good receiver will do
<wpwrak>
i have an usrp that can operate at 2.4 GHz and 5 Ghz. so i should be able to do *something* at carrier and 1st harmonic
<wpwrak>
no calibrated antenna, though
<DocScrutinizer>
1st harmonic - nevermind
<emeb>
that's actually not bad...
<DocScrutinizer>
calib rcv antenna - nvm
<wpwrak>
(1st harm.) gcc and etsi love that one ;)
<DocScrutinizer>
just make sure you got a clearly defined never changing testbed
<wpwrak>
(1st harm) also, the more power i see there, the less i'll have where i want it to be :)
<DocScrutinizer>
wpwrak: (1st harmonic) there's just so much you can do about it anyway
<wpwrak>
that's where your pi filter comes into play :)
<DocScrutinizer>
not exactly
<DocScrutinizer>
Pi filters are Z matchers
<DocScrutinizer>
not filters
<DocScrutinizer>
first approach at least - of course they are also lowpass
<DocScrutinizer>
wpwrak: also note there's antenna detuning even by plastic enclosures, so final antenna tuning has to be done in final product anyway
<wpwrak>
the one i have is used as such. to make up for all the mistakes atmel made in their balun :)
<DocScrutinizer>
humm, I see
<wpwrak>
DocScrutinizer: exactly why i don't see wolfgang avoid rf issues by using modules :)
<DocScrutinizer>
the issue doesn't get much better by using a module. It will see same detuning :-P
<wpwrak>
yup :)
<wpwrak>
and then you're back to tweaking little caps and inductors while staring at your measurement equipment :)
<emeb>
everyone who works RF has to do that...
<wpwrak>
yup. there's no hiding place.
<emeb>
just need to avoid the iPhone 'death grip' :)
<DocScrutinizer>
damn, a nice antenna design: 350MHz bandwidth
<emeb>
how much BW is needed for the wpan? - only a few 100kHz, no?
<wpwrak>
the band is ~100 MHz
<wpwrak>
not quite sure about the chanbnel width
<emeb>
and the chip can tune over the whole band?
<wpwrak>
yup
<emeb>
kewl
<wpwrak>
it's like wifi
<wpwrak>
2405 - 2480 MHz
<wpwrak>
channel spacing is 5 MHz
<emeb>
wow - more than I thought...
<wpwrak>
data rate is 250 kbps
<DocScrutinizer>
muses idly what WPAN might be at all
<emeb>
so there's a lot of dead air between channels.
<wpwrak>
chip rate 2 Mchips/s
<DocScrutinizer>
emeb: for sure not
<emeb>
?? didn't realize it was dsss
<wpwrak>
wireless personal area network. basically a bubble arund you with ~10 m radius
<emeb>
guess I was still thinking the FM stuff that HopeRF was using...
<DocScrutinizer>
what's it worth for?
<wpwrak>
not sure about modulation details yet. that's still on mt reading list
<wpwrak>
emeb: all the sub-ghz stuff is basically unusable for us. way too many regulatory restrictions.
<emeb>
gotcha.
<wpwrak>
emeb: such as duty cycle. 1 s per hour or so, in some of the more extreme cases.
<emeb>
heh - not really useful
<DocScrutinizer>
hrhrhrr
<emeb>
wow - those at86rf230 chips are cheap - $2.27 in 100qty from Digi-key
<wpwrak>
the cc2520 is also not bad. according to ti, as low as $1,95/1000
<wpwrak>
so both are interesting
<DocScrutinizer>
wpwrak: I strongly suggest to also review the documentation of CC2511 reference design, schematics and all. Also to find out about mystery of that "upper GNDplane"
<wpwrak>
ti's has a few more features, such as more buffers. atmel has onlt one, shared between rx/tx/host. kinda like the 3c501 ethernet :)
<emeb>
so are you still undecided which chip to use?
<wpwrak>
yup, good idea. there are also a few mystery components next to the antenna
<DocScrutinizer>
exactly
<wpwrak>
emeb: they both look attractive
<DocScrutinizer>
I'd expect to find some words about "making antenna shorter/longer" in the included readme
<emeb>
hmm - Digi-Key's 100pc price for the CC2511 is $6.10
<emeb>
$4.73 for the CC2520
<wpwrak>
2511 is mcu + usb + rf
<wpwrak>
2520 is just rf, like the at86rf230
<emeb>
atmel datasheet is pretty sparse on RF details
<wpwrak>
emeb: then try to find the impedance in ti's ...
<emeb>
:)
<emeb>
section 9.1 of the cc2520 ds says "high impedance". What more do you want?
<wpwrak>
good luck finding the rest :)
<emeb>
nice chatting - gn
<wpwrak>
DocScrutinizer: any other "red flags" in my design ? the whole mcu side and the crystal will go away when putting all this into the ben
<DocScrutinizer>
wpwrak: I missed the point of WPAN advantages over more established protocols like e.g BT PAN
<DocScrutinizer>
(red flag) I gather the crappy SMT only non-thruhole USB receptacle will go away as well
<wpwrak>
openness. basically everything WLAN or even BT is under NDA. and sometimes you can't even buy the chips/modules. or they're excessively expensive.
<DocScrutinizer>
:-(
<wpwrak>
hey, everybody uses that receptacle ;-) and i soldered it well :)
<DocScrutinizer>
what an epic fail
<wpwrak>
and yes, it'll go away. the idea is to basiclly cut at the two v-shaped dents. and of course remove the crystal. didn't know for sure what to with it when i designed the board
<DocScrutinizer>
(USB) yeah, and N900 returns/repairs/MIAs are legion, due to micro-USB rcptcl coming off
<wpwrak>
so far, _my_ usb receptacles are holding :)
<wpwrak>
but it's nice to hear that not only OM screwed up their usb :)
<DocScrutinizer>
industry should specify drop-tests to be done -mandatory - with cables attached
<wpwrak>
;-)
<DocScrutinizer>
the whole USB receptacle and plugs shit is a botch, at best
<wpwrak>
btw, the receptacle i used in idbg is pretty much indestructible. it's mounted inside the board plane, so there's no lever on the pull/push forces. as long as the pcb holds, that thing stays there.
<DocScrutinizer>
genearlly receptacles must be mounted to solid case, and connected to PCB by flexible  / detachable connection
<DocScrutinizer>
yup, that's another viable way to avoid it breaking on your first sneezing
<wpwrak>
also note the six (!) solder pads. i think nokia wouldn't have much trouble if they had used this one :)
<DocScrutinizer>
forget it! no matter what breaks, whether solder points or clue holding copper traces to base epoxy or the whole PCBA cracks. It's a flimsy design - by design
<DocScrutinizer>
s/clue/glue
<wpwrak>
yeah, pcb cracking is nasty
<wpwrak>
the proble is that you can't produce case-mounted connectors nearly as cheaply as pcb-mounted ones
<DocScrutinizer>
never will stand bending/torque forces >200Ncm
<DocScrutinizer>
err 2Ncm?
<wpwrak>
200 Ncm is a lot :)
<DocScrutinizer>
1Newton == 100g
<DocScrutinizer>
no?
<wpwrak>
yes
<DocScrutinizer>
so make that 2Ncm
<wpwrak>
2 Ncm should be fine
<DocScrutinizer>
i'd have used pcm but that's quite uncommon and ambiguous
<wpwrak>
that's one chocolate suspended from the end of a usb connector
<DocScrutinizer>
exactly
<DocScrutinizer>
and you'll exceed that easily, in a lot of everyday situations
<wpwrak>
agreed
<DocScrutinizer>
like dropping device on connector, or just putting it on sofy and then sitting on it
<DocScrutinizer>
sofa*
<wpwrak>
don't sit on your computers ! :)
<DocScrutinizer>
I bet a lot of less coordinated people will exceed that on mere unplugging
<wpwrak>
maybe a sofa-compatible computer would need a big capacitative sensor, to detect the approaching of the owner's arse ;-)
<DocScrutinizer>
or trip over the wire of charger - bang, dead
<wpwrak>
yes, i think plug/unplug forces can be quite large
<wpwrak>
most things don't break quite so easily
<DocScrutinizer>
USB receptacles do, esp the SMT type
<wpwrak>
hmm, i have stuff fall down, too. nothing broke so far. granted, i don't tie them to my car and drag them across town ...
<DocScrutinizer>
to make matters worse, it seems a lot of micro-USB come with excessive plug forces, by design
<wpwrak>
yup. micro-usb wants a good push
<DocScrutinizer>
honestly, micro-USB rcptcl should have its own mounting PCB, fixed to case, and any sort of wire or spring contacting to main PCB
<wpwrak>
good luck with that proposal :-)
<DocScrutinizer>
look at N810 power connector (2mm barrel) or all the Nxxx series AV/headset connector. Those are nice plastic things with a number of goldplated springs to contact to pads on PCB
<DocScrutinizer>
case has a recession to hold the thing mechanically, a 'bay'
<wpwrak>
ah, they're spring-connected ? nice
<DocScrutinizer>
can't see fundamental obstacles to implement USB that way
<DocScrutinizer>
it's not like those devices are <2% air inside
<wpwrak>
the usb receptacle does look a bit fragile, though
<wpwrak>
only half the pads large, the other(s) already quite small
<DocScrutinizer>
flimsy crap
<DocScrutinizer>
never can work decently
<DocScrutinizer>
I mean, thru hole would give at least a minimum of ruggedness
<DocScrutinizer>
spring load contacts and fixed in a bay would be optimum
<DocScrutinizer>
you literally had to break the case to ruin the receptacle, and even then you can just get a spare case which is supposed to be much cheaper than spare main PCBA
<wpwrak>
i thnk large enough pads should make it work okay for smt too
<wpwrak>
just tiny pads don't work. well, ironically, often it's even the solder than breaks, not the pad
<DocScrutinizer>
yup
<DocScrutinizer>
luckily
<wpwrak>
yes :)
<DocScrutinizer>
it's a botch, and it stays that way
<DocScrutinizer>
could be done better
<DocScrutinizer>
just like most pushbutton designs
<DocScrutinizer>
full load of force to the switching element... no wonder it breaks on first hard push
<DocScrutinizer>
why not have a latch or something where the plastic knob movement is limited hard, and pushing the switch with a "spring" designed into the knob plastic
<DocScrutinizer>
this way you never can break the switch, unless you poke *through* the plastic knob
<wpwrak>
hmm. patent it :)
<DocScrutinizer>
bah
<DocScrutinizer>
I'd rather love to see it *used* than patented
<wpwrak>
you could replace the spring with some silicone
<DocScrutinizer>
sure
<DocScrutinizer>
though this is harder to assemble, one component more
<wpwrak>
give the button four little feet. then you can use an off-the shelf dome.
<DocScrutinizer>
exactly
<wpwrak>
you'd just fill the keycap with the silicone
<wpwrak>
easier to do then placing a spring
<wpwrak>
well, scratch the silicone
<DocScrutinizer>
I thought of making the 'spring' just a thin lever - part of the plastic of knob
<wpwrak>
just a button with feet to terminate the movement will do
<DocScrutinizer>
nope
<DocScrutinizer>
can't manufacture that exact enough
<wpwrak>
the dome also allows for some tolerance
<DocScrutinizer>
headroom from 'click point' to maximum push in of a smt switch is <0.05 mm
<DocScrutinizer>
a dome type spring switch has no such headroom at all
<wpwrak>
hmm. lemme check this ...
<DocScrutinizer>
you need to push it down all the way until the metal dome touches the PCB pad. In that moment contact and limiting of movement are same thing
<DocScrutinizer>
I was thinking of side force operated type smt switches, like in FR
<DocScrutinizer>
though the silicone thing + feet works for dome type as well
<DocScrutinizer>
sure like hell will come off, just needs enough operation force
<wpwrak>
hmm, dome data sheet doesn't say how far it can travel once active. there must be some tolerance.
<DocScrutinizer>
there isn't by design
<DocScrutinizer>
(well axcept for how much you can compress the metal of the dome :-P)
<DocScrutinizer>
or the PCB and pad
<wpwrak>
yup. that's what i was thinking of
<DocScrutinizer>
and that are, incidentally, exactly the two failure patterns you see on dome sheet kbds like the one on N810: puncture the pad by excessive force, so there's no more contact when dome pressed down to the plain epoxy - and deformation of the dome spring, so it loses its properties
<wpwrak>
both should need quite a bit of force ...
<DocScrutinizer>
often less than you might think
<wpwrak>
you also have the dome's base that may be flexible
<wpwrak>
ah, but the metal is inside, so, doesn't help
<DocScrutinizer>
if patenting would help to propagate it into industry, I'd for sure do it. But I'm sure it'd be rather contraproductive
<DocScrutinizer>
anyway, 9'o saturday morning. The time they run their tests on TV how far the idiocy may be pushed on the customers
<DocScrutinizer>
mustn't miss that :-P
<DocScrutinizer>
also *yawn*
<wpwrak>
;-)) yeah, soon 4:30 here. may be a good moment for a nap.
<wpwrak>
thanks a lot for your rf suggestions !
<wpwrak>
that gives me hope the next version will perform a bit less crappy than the current one :)
<DocScrutinizer>
always a please, yw
<DocScrutinizer>
pleasure even
<wpwrak>
i'll try to have more difficult questions the next time :)
<roh>
about connectors and so.. if you want to know how to _really_ do that.. check out a lenovo T60 power plug
<roh>
they put the socket into a 'cave' inside the case which encloses it from all sides, a hole to the back which it cant fall through (rim) and multiple wires (4 in total, 2 for each pin in parallel since its power) go to the board and are connected with a 4 pin minimolex or so
<roh>
means you can a) exchange the power-socket (big barrel type) seperately, and it can 'wobble' a bit. make breaking out of the socket basically impossible, and also breaking it off a mainboard or so.
<roh>
great design.
<roh>
i guess one could mount a usb that way. put it on a pcb which is only 2-3mm wider than the socket, use 4 wires to the main pcb, put the whole thing in a 'recessed' indention in one of the case parts and fixate it by putting the other casing half over it. no more broken pcbs
<kyak>
unclouded: nightsky 20100827 is working fine!
<kyak>
is a great piece of software :)
<kyak>
unclouded: how do you zoom in/out? it's bound to F11/F12
<unclouded>
kyak: it says F11 and F12 but its the volume up and down keys in SDL
<kyak>
unclouded: hm, you mean Vol Up and Down
<kyak>
yeah, works great :) thanks!
<unclouded>
yes.  they turn up as F11 and F12 in SDL.  I should adjust the help text for the NanoNote though
<kyak>
unclouded: do you know how i can see the Sky in specific date/time?
<kyak>
without changin system date/time
<kyak>
unclouded: maybe the F1 help text in source code? Definitely should be patched
<unclouded>
not without editing the source
<kyak>
F11/F12 are bound very conveniently .. i don't know if this is just a conicidence
<kyak>
unclouded: would be better if after pressing F1 it would indicate that zoom in/out keys are VolUp and VolDown
<unclouded>
no coincidence.  it was written for the NanoNote
<kyak>
heh, great
<unclouded>
if you wanted to edit the source to show the sky at different times you want the lines that looks like: model.when_updated = time( NULL); in the update_main() method in main.c
<unclouded>
time(NULL) returns the time now.  using a different value will show the sky at the time represented by that different value
<kyak>
i see.. thanks for the hint
<kyak>
maybe for starters it can read this from config file
<kyak>
reading from user input would be harder
<kyak>
unclouded: i see you've updated version on SF
<unclouded>
the latest version only adds the ability to resize the window and build on Mac OS X, nothing new for the NN
<kyak>
do you plan to put more effort into nightsky? for example, implement possibility to search objects?
<unclouded>
not sure yet
<kyak>
what exists now is already great though :)
<unclouded>
to type stuff in it would have to have a primitive text field: type letters, backspace, delete, cursor, etc. but otherwise searching for an object would be a useful feature
<kyak>
yeah, it would be.. searching for objects and setting arbitrary dates/times
<unclouded>
although out of the 10,000 odd brightest objects, only 230 have common names
<wpwrak>
hmm. needs a hierarchy by topic. cutest on top. there should also be an "install me right now" link :)
<wpwrak>
but yes, screenshots are important. we're very visual animals. that won't go away anytime soon :)
<wpwrak>
ascii art ski jumping. oh dead ;-)
<wpwrak>
deaR even
<viric>
kristianpaul: through that I discovered 'asc'! I go building it
<kristianpaul>
wpwrak: indeed topic lacking
<wpwrak>
grr. git log --follow  follows renames only into the past, not into the future :-(
<wpwrak>
this is going to be messy ...
<rafa__>
are news around?
<rafa__>
hi
<rafa__>
:)
<wpwrak>
rafa__: everybody seems to have a relaxing saturday:)
<viric>
I just discovered ufoai :)
<wolfspraul>
rafa__: you online? where are you?
<wpwrak>
he should still be in barcelona
<viric>
hm I live near Barcelona
<viric>
100km away
<wolfspraul>
wpwrak: nice, so he made it through immigration :-)
<wpwrak>
wolfspraul: yeah. apparently they only had a quick look at the passport. didn't even want to see all the stuff they had prepared.
<wolfspraul>
that's how it should be
<wpwrak>
yes, indeed
<rafa__>
wolfspraul: hey!
<rafa__>
yes, we are in barcelona!
<rafa__>
we also met tuxbrain and we had some nice relaxing afternoonn talking
<wpwrak>
wolfspraul: will be interesting to find out what chip hoperf picked. it has a few unique magic numbers that only appear in their data sheet, according to google
<wpwrak>
things like 0xD99E8621 and 0xFFFFFEF7CF208104082041
<rafa__>
wolfspraul: the airport polices just check my face against passport. and i looks like and good england boy right now.. without beard and with a reallyy short haiir
<rafa__>
and i look like a good..
<rafa__>
:)
<wpwrak>
rafa: ah, you disguised yourself as skinhead ;-)
<rafa__>
let me show you a photo working with tuxbrain
<rafa__>
..
<rafa__>
wpwrak: haha... nono. like a good boy.. skinhead is a little bad boy i guess
<rafa__>
well, i have beard again.. that is fast
<rafa__>
:P
<rafa__>
wpwrak: anyway, i do not rely in the spanish airport police yet.. aaand i feel the same when i need to get in to spain again after jlime meeting
<rafa__>
when i was there.. the police man was so tired he seemed... but i was seeing that other people started to have problems with other polices
<rafa__>
wpwrak: perhaps the strategy is to check which police man is wanting to leave the office :))
<rafa__>
hola gustavo ;)
<wpwrak>
rafa__: so another shave before returning to spain ? :) anyway, you'll return from a EU country. so there shouldn't be much in terms of border controls.
<rafa__>
ah yes? i do not know well the papers there.. if it asks about the "from" country  maybe yes, it should be like you say
<wolfspraul>
rafa__: wow great you are with David?
<wpwrak>
rafa__: maybe keep boarding passes and hotel receipts. that way, you can always prove that you're indeed on an fairly extensive trip.
<wpwrak>
rafa__: i don't quite remember how the airports deal with intra-EU immigration. in theory, there should be no control. but if passengers from EU can be mixed with passengers connecting from non-EU flights, then there would be controls.
<rafa__>
wolfspraul: it was great.. he and victor are really nice guys and very funny guys :D
<rafa__>
i wrote the link manually, let me know if it works :P (i am chating with my hp palmtop)
<wpwrak>
empty beer glasses ?!?
<rafa__>
wpwrak: that was before to leave
<rafa__>
:)
<wolfspraul>
joshcryer: welcome to our copyleft hardware project :-)
<wolfspraul>
I wish one day we have a page like that Milkymist One SMT/DIP flow for a nice little ASIC manufacturing job...
<wolfspraul>
joshcryer: lekernel is the main force behind Milkymist, the channel is #milkymist on freenode
<joshcryer>
wolfspraul, thank you for the warm welcome. :)
<kristianpaul>
joshcryer: why milkymist is not free sofware?
<kristianpaul>
is code as we can see it, sure thee is a synteshis process
<kristianpaul>
sorry ask again i really want read your opinion
<joshcryer>
s/free software/free hardware/
<joshcryer>
uses Spartan-6 FPGA
<joshcryer>
Was not bashing, just thought it was not, exactly, what wolfspraul was talking about.
<joshcryer>
(with regards to freedombox)
<kristianpaul>
yeah sure the fpga is theere but at least we can implement free designs on it
<joshcryer>
Very true.
<kristianpaul>
hardware is not free by default ever
<joshcryer>
It's closer than FreedomBox.
<joshcryer>
Free as in freedom kristianpaul.
<joshcryer>
In English you do not say "Freedom Hardware."
<kristianpaul>
well you here thats good :)
<wolfspraul>
joshcryer: what is closer than FreedomBox?
<wpwrak>
don't "freedom fries" count ? ;-)
<joshcryer>
wolfspraul, Milkymist...
<wolfspraul>
Milkymist the IC design?
<joshcryer>
wolfspraul, yes, it incorporates non-free(dom) hardware.
<joshcryer>
Like FreedomBox does.
<kristianpaul>
is other level
<wolfspraul>
Milkymist is just an IC design, which on top of being entirely copyleft or BSD licensed, does go to great lengths to not build dependencies to proprietary vendor-specific FPGA extensions
<wpwrak>
joshcryer: so are you saying fpgas in general are out ? or just the spartan-6 ?
<kristianpaul>
we cant see hardware as just a big squared box and thats it
<joshcryer>
wpwrak, nah, wolfspraul even wants to move on to ASIC.
<kristianpaul>
there are leves we can achive freedon goals in some of then
<kristianpaul>
joshcryer: Having an ASIC doent mean we're done thereare propietary stuff required to make an ASIC
<kristianpaul>
so level by level...
<joshcryer>
wolfspraul, that's very fair enough. FreedomBox main competition is PlugComputer.
<wpwrak>
joshcryer: yup, but for now we're at fpgas. kinda more affordable :)
<joshcryer>
I did say that it was closer.
<joshcryer>
<joshcryer> It's closer than FreedomBox.
<kristianpaul>
and for what we really need "practical" freedom
<joshcryer>
But this discussion really split when I suggested that wolfspraul make himself an option for FreedomBox.
<joshcryer>
So FreedomBox 1.0 is PlugComputer or SheevaPlug, eventually it can become Milkymist-derived.
<wpwrak>
hmm, the mill has been enjoying more than a day off. time to give it something to do ... let's see ... the topmost plastic looks easy :) kinda useless, but all the rest i've left will be hell to mount.
<wolfspraul>
joshcryer: oh I misunderstood you then. you meant 'closer to freedom' not 'more closed' :-)
<kristianpaul>
joshcryer: so lets call it "free that non-free box"
<kristianpaul>
joshcryer: as we do when run free sofware on out computers
<joshcryer>
wolfspraul, apologies, English is a very difficult language, even for native speakers.
<joshcryer>
wolfspraul, I do sincerely hope you haven't ruled out being a FreedomBox platform some day though, as I think you have the right idea.
<joshcryer>
(I'm maybe a bit more optimistic / naive than most.)
<wolfspraul>
hard to compete with Marvell
<joshcryer>
Shame it's not atheros (packet injection). >:)
<wolfspraul>
they will integrate the CPU and Wi-Fi stuff, price will come down. maybe you will get that thing for 20 USD soon... who knows
<kristianpaul>
oh
<joshcryer>
So what, if you design ASIC and IC and we design PCB and cap/res. components you build the thing at materials cost (very very cheap).
<joshcryer>
wolfspraul, ShivaPlug is $125, V3.0 will likely be in same price range.
<joshcryer>
They should use Fonera but it's very limited (I am IRCing via my Fonera).
<joshcryer>
(And locked.)
<kristianpaul>
wolfspraul: why not Xburst + ethernet lilke a freedom box?
<kristianpaul>
Xburst chips are cheap hopefully can run server apps
<wpwrak>
i think a shivaplug-like device could make a useful platform for bringing MM to the masses. similar to a MM-based ben. basically take a design people are familiar with and totally change one key item.
<wpwrak>
however, a shivaplug-alike would also face regulatory issues. you may find it surprisingly difficult to ship such a thing to a lot of places.
<joshcryer>
Indeed, especially if it ran FreedomBox social networking cloud apps.
<joshcryer>
You destory facebook and fund free hardware designs, in one stroke.
<joshcryer>
>:D
<wpwrak>
well, the shipping will be fine. but then there are customs at the end, watching over local regulations.
<wpwrak>
joshcryer: "world domination, fast and on all fronts at once !" ;-)
<joshcryer>
That's my optimism speaking, btw. :)
<joshcryer>
What started it all was my mentioning my admiration of Moglen and someone posting a FreedomBox link and I'm afraid that wolfspraul thought we were saying it was better, but that was not the intention at all.
<joshcryer>
I quite like Qi-hardware now that I discovered it. :)
<wpwrak>
wolfspraul: btw, you'll notice that my "schematics diffs" often don't pick up a project from its beginning (happens in ben-wpan/atrf and xue). that's because not all the relevant top-level files (i.e., .pro and .sch) were committed from the start. so schhist2web starts looking at things beginning with the first commit but doesn't find anything it can use until later.
<wolfspraul>
wpwrak: well but that sounds like a feature not a bug, right?
<wolfspraul>
my main concern is that the scripts are robust
<wolfspraul>
never hang, never end in loops spamming the server disk space, those things
<wpwrak>
wolfspraul: it's a feature in the sense that the project was indeed not really usable at that point. it's a bug in the sense that there may be a history of changes we're missing. but i'd be a bit afraid of adding heuristics that move up in the history to cherry-pick files that may be missing. maybe add some mechanism for manual fixups in the future.
<wpwrak>
wolfspraul: (robust) time will tell ;-)
<wpwrak>
it would be good to run them in some sort of restricted environment. so that, even if something goes wrong, nothing horrible happens.
<wpwrak>
e.g., there are a few rm -rf in there. would be ugly if their arguments turn into a bare / by some twist of fate and the uid running all this actually can delete something valuable.
<wpwrak>
if someone was looking for a malicious exploit, there will almost certainly be something to find. after all, there are not only the shell scripts (shell being a fragile language when it comes to metacharacter exploits), but also git and eeschema. git has some interesting parsing heuristics that add a whole new set of meta-characters.
<wpwrak>
if we ignore malicious exploits, things should be a bit less rough. but i'd still take precautions.
<wolfspraul>
hmm
<wpwrak>
e.g., if wouldn't feel comfortable creating a new unprivileged user and running an rm -rf / as that user, then you probably don't want such a beast run wild
<wolfspraul>
we can ignore truly malicious exploits, but the 'restricted environment' still needs to be easily setup and maintainable
<wolfspraul>
I'll look into it
<wolfspraul>
wpwrak: would you feel comfortable running the script as an unprivileged user?
<wpwrak>
there are some forms of sandboxes that may be sufficient. package build processes often face the same challenges.
<wpwrak>
if your system is set up in a way that you wouldn't be afraid of your unprivileged user running rm -rf /, then yes
<wpwrak>
also, be warned that it can produce quite a lot of temporary output. e.g., xue has a cache of 3.7 GB
<wpwrak>
ben-wpan/atrf has 357 MB. ben-wpan/cntr only 32 MB (but the latter may get a bit bigger. there's still some bug somewhere hiding some things)
<wpwrak>
the cache is so big because it generates ppm files for all the schematics in all revisions. i can add an optimization for things that don't change later, though.
<wpwrak>
actually .. i could just use links ... let's see ...
<wpwrak>
for the things running crazy, you could just give it a generous cpu limit. maybe combined with a disk quota if you have that kind of stuff enabled.
<wpwrak>
for kicad, it also need some sort of X display. that can of course be some X server variant that doesn't need a head. vnc or such.
<wpwrak>
withvnc, you could also easily check what's wrong in case it hangs at some error dialog.
<wolfspraul>
ok got it
<wpwrak>
oh, and it can run in a pretty isolated environment if you want. no need to be able to write the repository or any other "valuable" data. at the end, you can just copy what it has generated from the output directory.
<wpwrak>
so even a VM that you scrap after use would be fine.
<wpwrak>
the only issue with recycling after use is that, if you lose the cache, it takes a while to process all the old commits. e.g., it needs about one minute for ben-wpan/atrf from a "cold" cache. after that, it's ~5 seconds if nothing has changed.
<wpwrak>
it's worse with xue. xue with a cold cache takes ~12 minutes. 16 seconds from up to date cache.
<wpwrak>
maybe i can make all this a bit faster when eliminating some of the rituals for unchanged files. unfortunately, it's hard to predict when a file may change or not. e.g., if the .sch is the same but a .lib or even the .pro has changed, the output could be different.
<wolfspraul>
don't go crazy, I think I need to move on the server now
<wolfspraul>
for Xue, the #1 thing that stood out last time still were the sheets that had no images at all, just an empty column
<wpwrak>
yup. that's the name tracking problem. it's a bit harder than i thought, because git won't tell me about renames in the past->present direction, only present->past.
<wolfspraul>
xiangfu: the 8 and 16 gb cards still don't boot
<wpwrak>
there's also the problem that xue uses a3 while i expect a4. i need to poke around inside the .sch for this. the .ps generated by eeschema always claims it's a4 :-(
<wolfspraul>
can you send me a u-boot with some more on-screen logging? maybe also just some number at the end (shortly before the error message so it's still visible), so that I know for sure that I am booting with the right u-boot version
<wolfspraul>
or maybe I need to send you my sd cards...
<xiangfu>
wolfspraul: yes. I saw your email. then I fixed the last bug that I know.
<xiangfu>
wolfspraul: it's hard to output log to screen.
<xiangfu>
wolfspraul: send me the sd cards is better.
<wpwrak>
cut out the man in the middle :)
<wolfspraul>
ok
<wolfspraul>
does anybody want to adopt the qihardware twitter and identi.ca accounts? there is also a nanonote group on identi.ca
<wolfspraul>
all pretty badly neglected, so I want to clean up a bit
<wolfspraul>
if nobody wants to use them, I will just delete them
<wolfspraul>
there are maybe 150 or so followers on identi.ca, maybe 300 on twitter. still a while until it catches up with Lady Gaga :-)
<wpwrak>
maybe also kill the forum while you're at it ? ;-)
<wolfspraul>
I knew you would say that Werner :-)
<wolfspraul>
I think the forum is fixable, at least I will try myself.
<wpwrak>
that problem with these "fad" platforms is that the accounts there tend to get orphaned quickly. e.g., just look at all the placed on myspace that wikipedia still often links to. meanwhile, the people have long moved to facebook or such.
<wpwrak>
the forum would be great if it connected to the mailing list
<wpwrak>
but if it's just a parallel universe, it just creates diversion
<wolfspraul>
I have no problem with twitter and identi.ca it's just that I only have so much time, so I think either someone steps up and brings some life into those accounts, or we do everybody a better service by closing them.
<wpwrak>
it's of course easy enough to ignore if you already know that the mailing list is where things are really happening. but it can trap newcomers. also, people who just want to see what's going on in that strange project find a seemingly abandoned site. not good PR.
<wpwrak>
(twitter etc.) they need constant attention to be useful, yes. you could perhaps automate some tweets or so. but i'm not sure if it's worth the trouble.
<wpwrak>
(automate) e.g., tweet is a thread on the list exceeds a certain size/message frequency. or pick commits, maybe even randomly.
<wpwrak>
new project creation could also go there. or maybe after a few commits, so that people don't only see that something will (maybe) happen, but that they come visiting when there's some meat already.
<wolfspraul>
nice ideas. let's see whether someone wants to step up around these accounts, and if not they are deleted :-)
<wpwrak>
if you want to experiment with automated news, you could send them to a list created for that purpose. if the concept works, you could add interfaces list->twitter etc.