2012-04-23 00:03 xiangfu has joined #qi-hardware
2012-04-23 00:05 <qi-bot> xiangfu: @qihardware @milkymistvj, Very cool documents on "Milkymist One SMT/DIP Process Flow" by @Adam : http://t.co/fdiE33ci ( 194218372148375553@xiangfu - 39s ago via Ping.fm )
2012-04-23 00:24 cladamw has joined #qi-hardware
2012-04-23 00:29 <wolfspra1l> wpwrak: I want to kick the wpan in shape a little
2012-04-23 00:29 <wolfspra1l> first step is to cleanup the patches inside openwrt so that it can work on other routers too
2012-04-23 00:30 <wolfspra1l> do you have any guidance as to what's the best thing to do next there?
2012-04-23 00:30 <wolfspra1l> xiangfu: what are your plans?
2012-04-23 00:30 <wpwrak> hmm, i should finish the new driver then. and see what things have happened on linux-zigbee since. haven't touched any of this in months.
2012-04-23 00:31 <wolfspra1l> wait wait, I don't want to distract  you
2012-04-23 00:31 <wolfspra1l> :-)
2012-04-23 00:31 <wpwrak> (new driver) i.e., make atusb fast enough that it can handle TCP over dirtpan
2012-04-23 00:31 <wolfspra1l> I need boom urgently
2012-04-23 00:31 <wolfspra1l> much more important from my side
2012-04-23 00:31 <wolfspra1l> but I think it's the right thing to move the patches in openwrt such that it can easily work on a router, no?
2012-04-23 00:31 <wolfspra1l> that's an easy thing to do
2012-04-23 00:33 <wpwrak> depends a bit on the state of the rest of 802.15.4 framework
2012-04-23 00:33 <wpwrak> if not much has changed, then it should be relatively easy
2012-04-23 00:33 <xiangfu> I have moved the atUSB patches to target/xburst. 
2012-04-23 00:34 <xiangfu> now needs cleanup and move to linux/generic  for all router that have usb host.
2012-04-23 00:34 <xiangfu> wpwrak, I haven't test atUSB under OpenWrt. but for now. atBen works just fine.
2012-04-23 00:35 <wolfspra1l> xiangfu: yes, sounds great!
2012-04-23 00:35 <wolfspra1l> so we can make it work between a ben and a router
2012-04-23 00:35 <xiangfu> yes.
2012-04-23 00:36 <wolfspra1l> perfect
2012-04-23 00:37 <wpwrak> xiangfu: atusb has the problem that it needs to many (slow) round-trips between host and board to actually send a packet. that causes it to run into problems with TCP very quickly. as long as a higher layer implements what amounts to half-duplex communication, it's fine, though. (just a little slow)
2012-04-23 00:39 <wpwrak> atben, on the other hand, doesn't have USB in the way to slow it down, and doesn't suffer such issues
2012-04-23 00:39 <wpwrak> it can still experience trouble (like stalled connections)
2012-04-23 00:40 <wpwrak> but that has other reasons, not really in the domain of the things i've done
2012-04-23 00:40 <wpwrak> (although one could alleviate them a bit by forking the at86rf23x driver)
2012-04-23 00:40 <wolfspra1l> I don't have a particular use case in mind right now
2012-04-23 00:41 <wolfspra1l> I just want to keep the work in a maintainable state, rather than the patches/drivers falling into coma
2012-04-23 00:41 <wolfspra1l> but yes, I hear you
2012-04-23 00:41 <wolfspra1l> "usb to slow it down"
2012-04-23 00:41 <wolfspra1l> :-)
2012-04-23 00:41 <wpwrak> maybe a good time would be once the driver is updated. then atusb should work quite smoothly. and then we can pimp it more efficiently ;-)
2012-04-23 00:42 <wpwrak> (usb to slow it down) the problem is that the host controller (UHCI, OHCI, etc.) does transfers in 1 ms slots
2012-04-23 00:43 <wpwrak> this means that you only get one round-trip communication in one slot, even if the actual dialog takes only a few usecs
2012-04-23 00:43 cladamw_ has joined #qi-hardware
2012-04-23 00:43 xwalk has joined #qi-hardware
2012-04-23 00:43 <wpwrak> and the atusb driver spend 99.something % of its time patiently waiting for the next slot ...
2012-04-23 00:43 <wolfspra1l> yeah but on the urgency scale, I need boom
2012-04-23 00:44 <wolfspra1l> I want to source m1r4 with boom, or compare sourcing status (what we have already) and what's missing with it, etc.
2012-04-23 00:44 <wpwrak> yup. i agree. boom first :) just explaining what's amiss with wpan
2012-04-23 00:44 <wolfspra1l> yes, perfect
2012-04-23 00:44 <wolfspra1l> xiangfu will start by moving things in a better place in openwrt
2012-04-23 00:44 <wolfspra1l> that's a small practical step to make the work more accessible
2012-04-23 00:45 <kristianpaul> wolfspra1l: had you noticed last dash7 news?
2012-04-23 00:47 <kristianpaul> just filling http://www.dash7.org/index.php?option=com_content&view=article&id=222&Itemid=214
2012-04-23 00:49 <wolfspra1l> no, thanks for posting
2012-04-23 00:49 <kristianpaul> good, i was re-organizing my stuff today and found rfm12b stuff and tought i dash and found this
2012-04-23 00:52 <wpwrak> their lawyers don't seem to believe in the simplicity of "click here to download the PDF" :)
2012-04-23 00:52 <kristianpaul> wpwrak: :)
2012-04-23 01:17 Zhai has joined #qi-hardware
2012-04-23 01:22 <qi-bot> [commit] Adam Wang: changed VDDPLL, VDDRCV, VDDRX to input instead of Power input since a common power network generates local net/lable as usual. (master) http://qi-hw.com/p/kicad-libs/e6d4981
2012-04-23 01:30 <qi-bot> [commit] Adam Wang: changed FLG1/2 pins to output/Line. (master) http://qi-hw.com/p/kicad-libs/be5f5bf
2012-04-23 01:40 wej has joined #qi-hardware
2012-04-23 01:42 rejon has joined #qi-hardware
2012-04-23 01:51 <qi-bot> [commit] Adam Wang: changed HSWAPEN to input which pin controls the internal pull-up resistors on all of the user I/O pins from power-on through completion of configuration. A Low level applied to the pin during configuration enables the internal pull-up resistors, while a High level disables them. (master) http://qi-hw.com/p/kicad-libs/18ae19f
2012-04-23 02:09 <cladamw_> xiangfu, i want to cancel this http://projects.qi-hardware.com/index.php/p/kicad-libs/source/commit/e6d4981d391fef106b88369d1fb85d51e7264b76/  how to use cmd ? like  git checkout e6d4981d391fef106b88369d1fb85d51e7264b76  ? 
2012-04-23 02:11 <xiangfu> cladamw_, git revert e6d4981d391fef106b88369d1fb85d51e7264b76
2012-04-23 02:12 <cladamw_> so this 'revert' will also change my local file back, right ?
2012-04-23 02:16 <xiangfu> cladamw_, yes. 
2012-04-23 02:16 <cladamw_> xiangfu, okay. tks. :)
2012-04-23 02:16 <xiangfu> cladamw_, it will only change the local file. as long as you don't run 'git push'
2012-04-23 02:18 <cladamw_> xiangfu so the git server will still have last commit existed there since I just did 'revert' and i see that commit history still on there, right ?
2012-04-23 02:20 phirsch has joined #qi-hardware
2012-04-23 02:22 <xiangfu> right. git revert it like: commit1(e6d4) --> commit2(be5f) --> commit3(18ae1), it will only revert commit1. keep the commit2 and commit3.
2012-04-23 02:22 <xiangfu> s/it/is
2012-04-23 02:22 <qi-bot> xiangfu meant: "right. gis revert is like: commis1(e6d4) --> commis2(be5f) --> commis3(18ae1), is will only revert commis1. keep the commis2 and commis3."
2012-04-23 02:30 zhai_ has joined #qi-hardware
2012-04-23 02:39 <qi-bot> [commit] Adam Wang: Revert "changed VDDPLL, VDDRCV, VDDRX to input instead of Power input since a common power network generates local net/lable as usual." (master) http://qi-hw.com/p/kicad-libs/6291bf5
2012-04-23 02:39 <qi-bot> [commit] Adam Wang: pwr.lib : added VIDEOIN_A3V3, VIDEOIN_A1V8, ETH_A3V3, ETH_A1V8, ETH_PLL1V8 for application power. (master) http://qi-hw.com/p/kicad-libs/1bff27c
2012-04-23 02:44 xiangfu has joined #qi-hardware
2012-04-23 03:18 xwalk has joined #qi-hardware
2012-04-23 03:24 GeorgeH has joined #qi-hardware
2012-04-23 03:29 xwalk has joined #qi-hardware
2012-04-23 03:45 <qi-bot> [commit] Adam Wang: pwr.lib : added IR_PWR, VAA_3V3 for application power. (master) http://qi-hw.com/p/kicad-libs/e117f71
2012-04-23 03:48 freespace has joined #qi-hardware
2012-04-23 03:48 cxadams has joined #qi-hardware
2012-04-23 03:50 phirsch has joined #qi-hardware
2012-04-23 04:55 xwalk has joined #qi-hardware
2012-04-23 04:58 phirsch has joined #qi-hardware
2012-04-23 05:00 valhalla has joined #qi-hardware
2012-04-23 05:00 rz2k has joined #qi-hardware
2012-04-23 05:00 whitequark has joined #qi-hardware
2012-04-23 05:01 wej has joined #qi-hardware
2012-04-23 05:01 kristianpaul has joined #qi-hardware
2012-04-23 05:01 zear has joined #qi-hardware
2012-04-23 05:04 Textmode has joined #qi-hardware
2012-04-23 05:11 jekhor has joined #qi-hardware
2012-04-23 05:27 xwalk has joined #qi-hardware
2012-04-23 05:28 xwalk has joined #qi-hardware
2012-04-23 05:32 cladamw has joined #qi-hardware
2012-04-23 05:55 cladamw has joined #qi-hardware
2012-04-23 07:06 <qi-bot> [commit] Werner Almesberger: components/EXPAND: added latest application-specific power symbols (master) http://qi-hw.com/p/kicad-libs/dec1eee
2012-04-23 07:15 <qi-bot> [commit] Adam Wang: changed to upper case. (master) http://qi-hw.com/p/kicad-libs/cf35956
2012-04-23 07:15 <qi-bot> [commit] Adam Wang: Merge branch 'master' of projects.qi-hardware.com:kicad-libs (master) http://qi-hw.com/p/kicad-libs/e33b87a
2012-04-23 07:19 DocScrutinizer has joined #qi-hardware
2012-04-23 08:00 LunaVorax has joined #qi-hardware
2012-04-23 08:16 <cladamw> wpwrak, before i do KiCad patch http://projects.qi-hardware.com/index.php/p/eda-tools/source/tree/master/kicad-patches/README, do I need to un-install somethings ?
2012-04-23 08:18 <wpwrak> you may have to uninstall kicad when you reach the point of installing
2012-04-23 08:18 <wpwrak> but you can even test it first
2012-04-23 08:18 <wpwrak> so once you've compiled everything, you can, for example, start the new eeschema with  /your/path/kicad/eeschema/eeschema
2012-04-23 08:18 <wpwrak> then see if it looks right
2012-04-23 08:19 <wpwrak> then, apt-get remove kicad  (or similar, depends on how you installed your present kicad)
2012-04-23 08:19 <wpwrak> then make install
2012-04-23 08:20 <cladamw> i see a file "kicad.bzr" after "bzr checkout -r 3494 lp:kicad kicad.bzr" so keep following your README now i think. :)
2012-04-23 08:20 <wpwrak> then open a new xterm (or do  PATH=$PATH), launch eeschema again, then check that the version is right
2012-04-23 08:20 <cladamw> okay, need to try. :)
2012-04-23 08:20 <wpwrak> very good. make the path above then /your/path/kicad.bzr/eeschema/eeschema   :)
2012-04-23 08:21 <wpwrak> kicad is pretty friendly when it comes to installation. the hard part is getting it to compile at all ;-)
2012-04-23 08:22 <cladamw> alright
2012-04-23 08:24 <cladamw> wpwrak, the current latest m1r4 whole schematic i fixed it now leaves TWO warnings only, I can't figure them out why. 
2012-04-23 08:25 <wpwrak> let's see
2012-04-23 08:25 <cladamw> phew~ from 66 warnings down to todays' last two wanings. :) so I would to use your this latest patches, then check it again hope I install successfully.
2012-04-23 08:25 <wpwrak> two warnings is a good value for such a large design
2012-04-23 08:26 <wpwrak> hah, i get 16 warnings ;-)
2012-04-23 08:27 <cladamw> i haven't uploaded all files( kicad-libs/components, and milkymist/board-m1/r4)
2012-04-23 08:27 <cladamw> so maybe that you just got 16 warnings. :-)
2012-04-23 08:27 <wpwrak> then i misread your "I can't figure them out why" :)
2012-04-23 08:28 <wpwrak> chances are that the new eeschema will find more rather than less. there's a general tendency that warnings get added, hardly ever removed :)
2012-04-23 08:30 <cladamw> wpwrak, ha... well... must be haven some tricky ways to cheat DRC/eeschema to pass them. :-)
2012-04-23 08:31 <cladamw> there's much funny things I re-edited different ways to let free warnings and passed, you will see. funny though !
2012-04-23 08:32 <cladamw> but I can't rely on my older version. so later we know. :)
2012-04-23 08:35 <wpwrak> sometimes there are indeed "invisible" problems. such as a net that looks as if it was connected but isn't.
2012-04-23 08:35 <wpwrak> hmm, all these board-specific power symbols are a bit troubling
2012-04-23 08:36 <wpwrak> alas, kicad more or less forces you to do things that way :-(
2012-04-23 08:36 <wpwrak> since you can't rename a power symbol in the schematics
2012-04-23 08:37 <qi-bot> [commit] Adam Wang: changed ADV7125KSTZ140's pin 13/29/30 to input (master) http://qi-hw.com/p/kicad-libs/f8b3e2d
2012-04-23 08:39 <cladamw> wpwrak, yeah .... about power symbols i got troubles
2012-04-23 08:40 <cladamw> wpwrak, but wait a bit. lemme uploaded all files, then you could check them again to see if same two warnings left. :)
2012-04-23 08:43 <cladamw> wpwrak, done. :) I just committed all my files here. so you may check to do DRC, and if also get two warnings on J17's pin 20 and 21. :)
2012-04-23 08:44 <wpwrak> 11 errors/warnings
2012-04-23 08:44 <cladamw> wpwrak, to me. then i do horrible patches steps myself. :-)
2012-04-23 08:44 <cladamw> wpwrak, man! 11 !
2012-04-23 08:45 <wpwrak> did you change anything in the ERC options ? i'm not sure if they're saved with the project
2012-04-23 08:46 <cladamw> no, i didn't touch KiCad's settings/default .:-)
2012-04-23 08:47 <cladamw> check this: http://dpaste.com/736030/
2012-04-23 08:48 <cladamw> wpwrak, me either, don't know if DRC settings saved in which file. :)
2012-04-23 08:48 <wpwrak> i don't get that one
2012-04-23 08:48 <cladamw> well .... okay, you can try to fix them if have time. but no rush. i should install yours patches work now. :-)
2012-04-23 08:49 <wpwrak> ah wait. once
2012-04-23 08:49 <wpwrak> http://downloads.qi-hardware.com/people/werner/tmp/m1.erc
2012-04-23 08:51 <cladamw> aha.. nice ! I'll go back to see your this result compared to the one after I installed. :)
2012-04-23 08:53 <wpwrak> there are PWR_FLAG symbols in the schematics that come up as ??, so they're not in kicad-libs
2012-04-23 08:55 <wpwrak> that may explain most of the errors/warnings
2012-04-23 08:58 <cladamw> but why in here, i didn't get yours err even I found the PWR_FLG (under KiCad's system power.lib) wasn't inserted m1.pro ?
2012-04-23 08:59 <cladamw> wpwrak, btw, what's this meanings. "ln -s wherever/eda-tools/kicad-patches patches" ?
2012-04-23 08:59 <wpwrak> wherever means there you've placed eda-tools/... (from qi-hw)
2012-04-23 09:00 <wpwrak> this creates a symbolic link from  patches -> eda-tools/kicad-patches/
2012-04-23 09:00 <wpwrak> which in turn quilt uses to find the patches
2012-04-23 09:03 <cladamw> adam@adam-laptop:~/eda-tools/kicad-patches/kicad.bzr$ ln -s ~/eda-tools/kicad-patches patches
2012-04-23 09:03 <cladamw> ln: creating symbolic link `patches': File exists
2012-04-23 09:04 <wpwrak> then you've already done it
2012-04-23 09:04 <wpwrak> if you did it wrong the first time,  rm patches   and try again
2012-04-23 09:05 <wpwrak> hmm, i think we should make our version of "PWR_FLAG" a bit more explicit that the original. lemme try ...
2012-04-23 09:05 <cladamw> there's four 'cmdline-*.patch under adam@adam-laptop:~/eda-tools/kicad-patches$
2012-04-23 09:05 <wpwrak> quilt patch -a
2012-04-23 09:06 <wpwrak> quilt takes care of the rest :)
2012-04-23 09:06 <cladamw> wait:)
2012-04-23 09:06 <wpwrak> (the link is to the directory. so, when in kicad.bzr, ls patches   should also show you the files in eda-tools/kicad-patches/)
2012-04-23 09:07 <cladamw> type "quilt patch -a" under adam@adam-laptop:~/eda-tools/kicad-patches/kicad.bzr$  or ~/eda-tools/kicad-patches/ ?
2012-04-23 09:09 <wpwrak> under kicad.bzr
2012-04-23 09:10 <cladamw> yeah ... i found and now install 'quilt' :(
2012-04-23 09:12 <wpwrak> hah ! :)
2012-04-23 09:14 <cladamw> wpwrak, so like this ? and run each *.patch one-by-one ? adam@adam-laptop:~/eda-tools/kicad-patches/kicad.bzr$ quilt ~/eda-tools/kicad-patches/cmdline-common.patch -a
2012-04-23 09:15 <wpwrak> no
2012-04-23 09:15 <wpwrak> quilt push -a
2012-04-23 09:15 <cladamw> wpwrak, yes, i agreed that making our own version of "PWR_FLG".
2012-04-23 09:16 <wpwrak> just do as the README says :)
2012-04-23 09:16 <cladamw> adam@adam-laptop:~/eda-tools/kicad-patches/kicad.bzr$ quilt push -a
2012-04-23 09:16 <cladamw> No patches in series
2012-04-23 09:16 <wpwrak> then your link has a problem
2012-04-23 09:16 <wpwrak> rm patches
2012-04-23 09:16 <wpwrak> ln -s ~/eda-tools/kicad-patches patches
2012-04-23 09:16 <wpwrak> then try again
2012-04-23 09:17 <cladamw> nice!
2012-04-23 09:18 <cladamw> done ?  http://dpaste.com/736042/  
2012-04-23 09:18 <cladamw> i keep following README. :)
2012-04-23 09:18 <wpwrak> victory is yours ! :)
2012-04-23 09:20 <cladamw> http://dpaste.com/736044/
2012-04-23 09:20 <qi-bot> [commit] Werner Almesberger: components: added powered.lib (POWERED), to replace PWR_FLG (master) http://qi-hw.com/p/kicad-libs/43585b4
2012-04-23 09:21 <cladamw> building seems slow.
2012-04-23 09:22 <wpwrak> hmm, something's not right with "powered" ..
2012-04-23 09:22 <wpwrak> (slow) it's C++ ...
2012-04-23 09:24 <cladamw> wpwrak, i found eechema will everytimes changes *.sch once i used system's PWR_FLG and fixed err, the PWR??? (??? means number ) will always be changed. I don't know how eescheme it works. you can check for a while. :)
2012-04-23 09:25 zedstar has joined #qi-hardware
2012-04-23 09:25 <wpwrak> uh, these numbers may not mean a lot
2012-04-23 09:27 <cladamw> since i've seen they are auto changed. :)
2012-04-23 09:28 <cladamw> maybe sschema manages internal pwr net, etc. :-)
2012-04-23 09:31 <wpwrak> with proper power flag, still 9 errors
2012-04-23 09:33 <cladamw> green or blue ?
2012-04-23 09:33 <wpwrak> uh ?
2012-04-23 09:33 <cladamw> green(warings) blue (err) :)
2012-04-23 09:34 <cladamw> 9 errors includes green and blue ones. :)
2012-04-23 09:34 <wpwrak> didn't look at the markers. it counts 9 errors and 9 warnings
2012-04-23 09:34 <cladamw> wow..okay
2012-04-23 09:35 <cladamw> actually they should be easiler to fix. :)
2012-04-23 09:35 <wpwrak> e.g., FLASH_A0 ... A3 no connected
2012-04-23 09:36 <wpwrak> hmm. you have an A2 sheet in there ? :)
2012-04-23 09:36 <cladamw> yes
2012-04-23 09:37 <cladamw> since FPGA.sch is too large. :) Is it to related ? 
2012-04-23 09:38 <wpwrak> naw. but it's too big. maybe one can still read A3 when printing, but A2 would be tiny
2012-04-23 09:38 <cladamw> we can split it into two A3 sheet if it's not displayed well for you. :)
2012-04-23 09:38 <wpwrak> yes, we should keep sheet sizes reasonable. i'm not even entirely sure about A3 ...
2012-04-23 09:39 <cladamw> hmm...sounds you're right. then we seperate A2 into two-A3 later.
2012-04-23 09:39 <wpwrak> i would also rename some of the sheets. don't name them by component but by function.
2012-04-23 09:40 <wpwrak> e.g., not "ADV7181CBSTZ" but "Video In"
2012-04-23 09:41 <wpwrak> same for micel, micron, xilinx, wolfson, the other analog devices, numonix
2012-04-23 09:41 <cladamw> am i finished ? http://dpaste.com/736056/
2012-04-23 09:42 <wpwrak> ah, s/rename/relabel/. in the overview sheet. the file names look okay
2012-04-23 09:42 <cladamw> wpwrak, sure ... okay. :)
2012-04-23 09:42 <wpwrak> but you hardly see them (the file names) on the big sheet :)
2012-04-23 09:43 <wpwrak> (build_ looks great
2012-04-23 09:43 <cladamw> wpwrak, yeah....needs to think another way to display text bigger for "Video In" "Audio In/Out" etc ...
2012-04-23 09:43 <wpwrak> now launch eeschema and check help / about eeschema
2012-04-23 09:44 <cladamw> i found text can't be placed within in eeschema's hierarchical rectangle. so need to study more. or you know how to. :)
2012-04-23 09:44 <wpwrak> (bigger text) i would just not mention the chips at that point. that's not really useful information there, and when we change a chip, you'll always have to remember to change it in the overview, too.
2012-04-23 09:45 <wpwrak> it can't ? i though it could. checking ..
2012-04-23 09:45 <wpwrak> works fine for me :)
2012-04-23 09:45 <wpwrak> it is hard to do things with it there, though. e.g., you can't easily move it around
2012-04-23 09:46 <cladamw> i tried to place text within that hierarchical rectangle but not. 
2012-04-23 09:46 <cladamw> yeah
2012-04-23 09:46 <cladamw> oah..nice ! yours can do it. :)
2012-04-23 09:46 <wpwrak> yours too :)
2012-04-23 09:46 <wpwrak> did you check the version ? just run  eeschema
2012-04-23 09:46 <cladamw> wait. help me to finish the PATH
2012-04-23 09:48 <wpwrak> you mean   PATH=$PATH          ?
2012-04-23 09:48 <cladamw> i typed "eeschema" under adam@adam-laptop:~/eda-tools/kicad-patches/kicad.bzr$ but it's older one(BRZ 2448), so how to set PATH ?
2012-04-23 09:48 <cladamw> yes
2012-04-23 09:49 <wpwrak> try  which eeschema
2012-04-23 09:49 <cladamw> /usr/local/bin/eeschema
2012-04-23 09:50 <wpwrak> interesting. that's where you've just installed the new version
2012-04-23 09:50 <cladamw> yes. then ... ?
2012-04-23 09:50 <cladamw> :)
2012-04-23 09:50 <wpwrak> okay,   PATH=$PATH
2012-04-23 09:50 <wpwrak> then   eeschema   again
2012-04-23 09:51 <wpwrak> if you still get the old version, try
2012-04-23 09:51 <cladamw> nice ! now 3494 :)
2012-04-23 09:51 <wpwrak> .... not needed :) ...
2012-04-23 09:51 <wpwrak> perfect ! ;-)
2012-04-23 09:51 <cladamw> (2012-0408 ZR 3494)-testing
2012-04-23 09:51 <wpwrak> now you can try to see for yourself what errors are there :)
2012-04-23 09:52 <cladamw> wpwrak, tks for your helps. and the new GUI is amazing though. :)
2012-04-23 09:53 <wpwrak> unfortunately, it also has a few quirks
2012-04-23 09:53 <wpwrak> you'll see. e.g., when dragging. that's now a bit inconvenient and takes a while to get used to
2012-04-23 09:55 <cladamw> wpwrak, INTERESTING! I got still those two warning!
2012-04-23 09:57 <wpwrak> that suggests that you didn't commit all your files :)
2012-04-23 09:58 <cladamw> really? wait. i need to upload my DRC default settings to compare to yours.
2012-04-23 09:59 <qi-bot> [commit] Werner Almesberger: components/powered.lib: reduced pin length (master) http://qi-hw.com/p/kicad-libs/867b8f9
2012-04-23 10:00 <wpwrak> maybe start by deleting the cached components. there should be a file *cache*lib
2012-04-23 10:00 <cladamw> wpwrak, http://downloads.qi-hardware.com/people/adam/kicad/Erc_settins_3494.png
2012-04-23 10:02 <cladamw> (cache) poor adam. okay... go find that lib. :)
2012-04-23 10:03 <wpwrak> ERC settings are the same here
2012-04-23 10:04 <wpwrak> that lib would be in board-m1/r4/
2012-04-23 10:04 <wpwrak> kicak loves its little caches
2012-04-23 10:07 <cladamw> same results after deleted m1-cache.lib and its dcm
2012-04-23 10:07 <cladamw> strange
2012-04-23 10:09 <cladamw> wpwrak, how to check or type which git cmd to know if I have some files i didn't commit ?
2012-04-23 10:10 <wpwrak> here are the .sch files i see: http://pastebin.ca/2139127
2012-04-23 10:10 <cladamw> except those files with timestamps changes I didn't commit, then i always use 'git checkout -- *.lib or *.dcm" after i see there's no differences after typed "git diff filename". :)
2012-04-23 10:11 Ayla has joined #qi-hardware
2012-04-23 10:11 <wpwrak> git diff    tells you which files are known and have changes
2012-04-23 10:12 <wpwrak> there's one more step: if you add files manually with  git add, then they disappear from git diff. you can see them with  git diff --cached
2012-04-23 10:12 <lindi-> "git ls-files -m" lists modified files if you need them in a reusable format
2012-04-23 10:13 <lindi-> and "git ls-files -o" lists files that are not in the repo
2012-04-23 10:13 <cladamw> i sured those 15 *.sch I commited
2012-04-23 10:14 <cladamw> lindi-, hi nice ! http://dpaste.com/736063/
2012-04-23 10:14 <cladamw> lindi-, much thanks a lot!
2012-04-23 10:15 <wpwrak> all files that shouldn't be in git. so this is good.
2012-04-23 10:15 <lindi-> of course if you use emacs then I'd suggest magit
2012-04-23 10:15 <lindi-> :-)
2012-04-23 10:15 <cladamw> maybe i need to delete m1-cache.bak & *.bck ?
2012-04-23 10:15 <wpwrak> and you've deleted the cache library. if you run eeschema now, do the errors still appear ?
2012-04-23 10:16 <wpwrak> i don't think kicad used .bck or .bak automatically
2012-04-23 10:17 <cladamw> wpwrak, no, i still got two warnings only after deleted m1-cache.lib. :(
2012-04-23 10:17 <wpwrak> grmbl
2012-04-23 10:18 <cladamw> wpwrak, wait. you just updated kicad-lib/component ? so i need to sync ?
2012-04-23 10:19 <wpwrak> yeah, why not. it's just the new POWERED symbol
2012-04-23 10:19 <cladamw> or it's not related though. don't  know
2012-04-23 10:19 <wpwrak> lemme update m1-board then, too
2012-04-23 10:20 antoniodariush has joined #qi-hardware
2012-04-23 10:20 <wpwrak> incoming ...
2012-04-23 10:21 <cladamw> okay...lemme do sync and DRC again. :-)
2012-04-23 10:23 <cladamw> phew~ still two.
2012-04-23 10:24 <wpwrak> you should DRC your components ...
2012-04-23 10:24 <cladamw> i saw your new POWERED flg
2012-04-23 10:24 <wpwrak> e.g., 74320-1004 produces a lot of complains in the library editor
2012-04-23 10:26 <wpwrak> http://downloads.qi-hardware.com/people/werner/tmp/trouble.png
2012-04-23 10:27 <wpwrak> seems that some copy & paste went terribly wrong
2012-04-23 10:28 <cladamw> wow..nice the new version in Library Editor has DRC function. :-)
2012-04-23 10:30 <cladamw> wpwrak, ha ... nice. now i can follow DRC window results to fix it. the older version doesn't have DRC version in Library Editor. phew~
2012-04-23 10:30 <wpwrak> ah, really ? i though that has been around for a while. maybe it was hidden, though
2012-04-23 10:30 <cladamw> but still don't know why the DRC results in Schematic editor which are not same as yours ?
2012-04-23 10:31 <cladamw> you said you got 9
2012-04-23 10:31 <xiangfu> do you need me? do this DRC again?
2012-04-23 10:31 <cladamw> i got two only. phew~
2012-04-23 10:31 <cladamw> xiangfu, wpwrak wait no need now. :-)
2012-04-23 10:32 <cladamw> since I need to use this new KiCad version to check components in Library Editor then go back in eeschema to do DRC. :-)
2012-04-23 10:32 <wpwrak> yeah :)
2012-04-23 10:33 <wpwrak> if it's a commit problem, maybe it'll disappear as part of that cleanup
2012-04-23 10:33 <cladamw> but in the parallel , if you both have time, you could do it. but don't do from you both now. 
2012-04-23 10:34 <cladamw> since I need to figure out why my results got two only and yours is 9 ! :-O
2012-04-23 10:34 <wpwrak> i suspect that there's some commit difference. let's see how things look once you're done with the cleanup
2012-04-23 10:35 <cladamw> xiangfu, but maybe you can also do patch for KiCad by http://projects.qi-hardware.com/index.php/p/eda-tools/source/tree/master/kicad-patches/README
2012-04-23 10:35 <wpwrak> this will probably remove the two ERC warnings/errors you got
2012-04-23 10:35 <wpwrak> (this = the cleanup)
2012-04-23 10:36 <wpwrak> if we still diverge afterwards, we'll need to try tarballs ...
2012-04-23 10:36 <cladamw> wpwrak, yeah... since this board-m1 is my  firstly done with frequently git commit, actually i don't know if I did well on git work though. :-)
2012-04-23 10:37 <wpwrak> so far, it looks good. oh, and we should track the changes in schhist
2012-04-23 10:37 <wpwrak> hmm. http://projects.qi-hardware.com/schhist/ -> You don't have permission to access /schhist/ on this server.
2012-04-23 10:37 <wpwrak> :-(
2012-04-23 10:37 <cladamw> wpwrak, be careful on my skill on git work now. :)
2012-04-23 10:38 <cladamw> so don't open permission unless you think that i'm qualified. :-O
2012-04-23 10:38 <wpwrak> schhist is a pretty good detector for commit problems ;-)
2012-04-23 10:39 <wpwrak> (permissions) naw, there's something wrong in the setup on project.qi-hw.com
2012-04-23 10:40 <wolfspra1l> wpwrak: you want to add board-m1 to schhist?
2012-04-23 10:40 <wolfspra1l> I needed to do it anyway...
2012-04-23 10:40 <cladamw> xiangfu, wpwrak i think from now on, who wants to contribute this project, should all sync to the latest tools(KiCad patches) how do you think ?
2012-04-23 10:42 <wpwrak> cladamw: agreed. if versions are too much out of sync you run into too many little problems
2012-04-23 10:42 <cladamw> yeah...
2012-04-23 10:42 <cladamw> xiangfu, so please also use latest KiCad patches. :-)
2012-04-23 10:53 <xiangfu> cladamw, ok.
2012-04-23 11:21 GNUtoo-desktop has joined #qi-hardware
2012-04-23 11:51 Ayla has joined #qi-hardware
2012-04-23 12:02 LunaVorax has joined #qi-hardware
2012-04-23 12:07 cladamw has joined #qi-hardware
2012-04-23 12:23 urandom__ has joined #qi-hardware
2012-04-23 12:27 <qi-bot> [commit] Adam Wang: molex.lib: 74320-1004 -> removed duplicated pins (master) http://qi-hw.com/p/kicad-libs/dc58a6f
2012-04-23 12:30 <cladamw> [m1r4 DRC Zero err] after last commit on J17 duplicated pins, board-m1 now got zero err after DRC from adam site here.
2012-04-23 12:33 <cladamw> now needs to check carefully why mine differs from Werner's. :-)