<wpwrak_>
wolfspraul, kristianpaul: (community news) the 150 MHz scope - is it the only one the university has ? if not or uncertain, maybe write "to a 150 MHz scope"
<wpwrak_>
wolfspraul: (mm1) how about mentioning that the case parts were laser-cut ?
<wpwrak_>
wolfspraul: (xue) maybe add more emphasis on xue looking for reviewers ? right now, it sounds a bit like something that'll happen anyway, without any reader needing to get involved. e.g., something like "Andr\'es Calder\'on has issued a call for reviewers."
<wolfspraul>
ha :-)
<wpwrak_>
wolfspraul: in fact, maybe put the CMOS sensor and the call for review as two items. the CMOS sensor also has the "choice" element, right ? or has this been covered before ? So "The Xue project has chosen the .... . In a leap of faith, ... a firm order of 30 sensors."
<wpwrak_>
hmm, too bad that jlime didn't make it into this news batch
<wolfspraul>
don't know what exactly the news is there, someone just needs to write it up
<wpwrak_>
(jlime) i think it's "almost done", but with a few loose ends. not sure about rafa's schedule (or anyone else's for that matter)
<wpwrak_>
ah ... maybe "upcoming events": the MM1 workshop at CCC !
<wpwrak_>
now. the moment of truth. yesterday, after the thunderstorm, my antenna tests all of a sudden started to change. could be something in the test setup or could be just bad luck with all the antennas i tested at the end (three of them) having the same flaw causing an unusual profile.
<wpwrak_>
intersting ... power-cycle all devices, reconnect antenna. voila, signal is some 15 dB stronger than before. WFT ?!? :-(
<wpwrak_>
it does look a lot "cleaner", though. i wonder what happened before.
<qi-bot>
[commit] Mirko Vogt: disable fbterm and lynx, since they do not compile... latter one should be easy to fix (missing iconv.h) http://qi-hw.com/p/openwrt-xburst/d170cb7
<kristianpaul>
wpwrak_: (scope) no, i also used some multimeters, PSU
<kristianpaul>
wpwrak_: they also had an spectrumanalizer but i dint used at last
<kyak>
mirko: they DO compile
<kyak>
they require locale to be enabled
<kyak>
therefore patch for fbterm was removed
<kyak>
you might be missing one of the commits to openwrt-xburst
<kyak>
1b577b72608d4cd16de089a5d8eee419cf9ab4b2 this one, to be specific
<kristianpaul>
wpwrak_: (ants) weird changed indeed, your finding could be interesting for nokia ;)
<mirko>
kyak: hmm, did i miss to update the qi-packages repo first? (thinking...)
<kristianpaul>
actually it looks like more the oposite signal
<kristianpaul>
"oposite" or english equivalent
<kyak>
mirko: well, if both openwrt-packages and openwrt-xburst are updated to the latest master, they compile
<mirko>
it is
<mirko>
updated and started the full build yesterday
<mirko>
updated both repos to latest HEAD, re-enabled them and will test again
<kyak>
and your feeds.conf are using the latest version of qi-packages?
<mirko>
yes
<kyak>
ok then.. pretty strange though because xiangfu also didn't complain
<kyak>
mirko: are you building from scratch?
<mirko>
yes
<wpwrak_>
kristianpaul: (nokia) hmm, i think they know RF a lot better than in could every hope to ;-)
<qi-bot>
[commit] Werner Almesberger: atusb: use 0402 as the preferred component size and replace bad TVS http://qi-hw.com/p/ben-wpan/23c3726
<qi-bot>
[commit] Werner Almesberger: usrp/README: change threshold to avoid making section reference look like a typo http://qi-hw.com/p/ben-wpan/fea4ee5
<qi-bot>
[commit] Werner Almesberger: usrp: try to bring back sanity to pre- and post-processing of FFT data http://qi-hw.com/p/ben-wpan/40d1234
<wpwrak_>
wolfspraul: you did it ! congratulations !!
<wolfspraul>
the news? yeah
<wolfspraul>
done
<wolfspraul>
I could have mentioned the Milkymist One RC2 production, forgot... but also no tangible enough results yet
<wpwrak_>
(mm1) you could have mentioned the upcoming workshop
<wpwrak_>
(i wrote this before. not sure if you saw it.)
<wolfspraul>
I don't like 'upcoming' stuff
<wolfspraul>
so I don't add it :-) it's a wiki...
<wolfspraul>
a few times I thought about adding a whole section at the bottom (or other place), called 'announcements', or 'plans', or 'upcoming' or whatever
<wolfspraul>
but then I can never convince myself to actually write something there
<wpwrak_>
yeah, but people many still want to know about the workshop :)
<wpwrak_>
unlike the typical roadmap item, it's something with a pretty definite schedule :)
<wolfspraul>
yes I understand, my total refusal to talk about upcoming things is also not good
<wolfspraul>
otherwise you always find out about things too late
<wolfspraul>
good point
<wolfspraul>
maybe if it's a fixed date, it should be mentioned
<wpwrak_>
more importantly, if you don't know it before, you'll miss it
<wolfspraul>
sure
<wolfspraul>
I'm not a news person, in general I am very reluctant about 'upcoming' stuff but of course we should have better criteria than that for what is 'good' upcoming stuff and what not.
<wolfspraul>
maybe if it has a fixed date in the calendar, that's a very good indicator it should be mentioned
<wpwrak_>
with a product announcement, it's okay if you learn about it after the fact. well, unless you plan on spending the night before the launch waiting in the line outside the shop :)
<wolfspraul>
and if nobody is willing to put a date next to whatever is announced or upcoming, then maybe it shouldn't be in
<wpwrak_>
hehe :)
<wolfspraul>
yes I definitely understand the power of announcements, but that's why I am reluctant
<wolfspraul>
it adds an extra burden
<wolfspraul>
anyway, I like the 'fixed date' criteria
<wolfspraul>
I'll keep it in mind... thanks!
<wpwrak_>
i think there aren't that many events that need announcing. stuff like public talks and such.
<wpwrak_>
hmm, let's make it "fixed date" plus "you have to know about it before to make the most out of it"
<wpwrak_>
then you don't have to worry about more-or-less-fixed product launch dates and such (well, unless you want to :)
<wpwrak_>
or perhaps two levels: the ones with a fixed expiration date, should always go in, the ones with a date that can be missed are optional
<wpwrak_>
regarding the news, if you intend this as a channel also to keep the press updated, particularly events like the workshop are important. otherwise, they may miss it, and then it doesn't get covered in the probably widely read report on the CCC event.
<wpwrak_>
hmm. seems that i need to power cycle the usrp every now and then, or it starts measuring junk :-(
<kristianpaul>
hmm?
<wpwrak_>
wow ! it's the bloody ground vias !
<kristianpaul>
good, how do you find it?
<wpwrak_>
kristianpaul: looked for texts on f-antennas to see if i had any flaws in my logic. then i found one where they said the vias had to be 50 mil apart. mine are 200 mil. reworked one of the antennas, measured it. lo and behold ...
<wpwrak_>
now .. rework of the other nine boards ... i'll skip the three with a negative size change. they were just the control group.
<viric>
Hep
<viric>
hummm qucs does not build with gcc 4.5.1
<viric>
spfile.cpp:405:21: error: call of overloaded 'conj(nr_complex_t)' is ambiguous
<viric>
annoying
<kristianpaul>
be carefull lekernel could heard you ;)
<viric>
would that help? :)
<kristianpaul>
no actually
<kristianpaul>
try askign #gcc
<viric>
kristianpaul: I imagine it's a qucs bug, not a gcc bug :)
<kristianpaul>
ahh i tought
<kristianpaul>
nv then
<wpwrak_>
that sort of thing is actually quite common with c++. the language seems to have an incredibly fast bit-rot.
<kristianpaul>
btw in the meant time kexec can replace uboot, how hard is get a silent uboot boot, i wonder if all those prints are also tooo infomartives and delay some  bootime..
<kristianpaul>
i a tought
<kristianpaul>
is just*
<wpwrak_>
uboot is fairly silent. are you sure you don't mean kernel messages ?
<wpwrak_>
if i remember right, you can suppress them with the boot parameter "quiet"
<kristianpaul>
ahh
<kristianpaul>
no
<kristianpaul>
before load kernel
<kristianpaul>
when it is looking for /boot/uImage
<wpwrak_>
ah, uSD. haven't tried that yet :)
<kristianpaul>
no no
<kristianpaul>
even from flash
<kristianpaul>
is same tought
<wpwrak_>
wolfspraul: btw, you once mentioned that you got some breakout cables made as a "street job". did this actually happen or was it just an idea that's still awaiting implementation ?
<kristianpaul>
well long dat i'm off bed
<kristianpaul>
bye
<kristianpaul>
s/dat/day
<wolfspraul>
kristianpaul: what is the source url for moc?
<wolfspraul>
[cables] yes sure I made 10
<wolfspraul>
will give them away here and there when there is an opportunity
<wolfspraul>
fuse is there, inductor forgotten :-)