IRC log for #neo900 on 20180615

00:02.27*** join/#neo900 louisdk (~louisdk@static-5-103-138-205.ip.fibianet.dk)
00:19.25*** join/#neo900 infobot (ibot@208.53.50.136)
00:19.25*** topic/#neo900 is http://neo900.org | CCCAMP15 lightning talks at http://neo900.org/stuff/cccamp15/ - major: http://neo900.org/stuff/cccamp15/ccc2015talk/neo900-wpwrak_CCC2015.webm | conversations are logged to http://infobot.rikers.org/%23neo900/ and http://irclog.whitequark.org/neo900 | Latest news: http://neo900.org/news/joerg-pia-2018-03-01
00:19.25*** mode/#neo900 [+v infobot] by ChanServ
03:07.19*** join/#neo900 knttl (~knttl@p54B7E259.dip0.t-ipconnect.de)
03:50.27*** join/#neo900 pagurus (~user@i59F7CA86.versanet.de)
03:59.22*** join/#neo900 himcesjf_ (~cesjf@unaffiliated/himcesjf)
04:04.33*** join/#neo900 knttl (~knttl@p54A53D9F.dip0.t-ipconnect.de)
04:07.49*** join/#neo900 ravelo (uid244116@neo900/community/supporter/ravelo)
04:11.09raveloJoerg-Neo900: thanks for explaining
04:11.16raveloRead it now
04:18.48*** join/#neo900 ArturShaik (~artur-sha@212.112.100.88)
04:30.29*** join/#neo900 him-cesjf (~cesjf@unaffiliated/himcesjf)
04:32.59*** join/#neo900 jonsger (~Thunderbi@i59F77F16.versanet.de)
08:05.55Joerg-Neo900juts for correctness: there _are_ situations where you simply can't route stuff - when you need to connect 3 chips of 3*3cm each with traces none longer than 6mm - we don't have any such situation on Neo900
08:06.53Joerg-Neo900at least not in proto_v2
08:21.31*** join/#neo900 ArturShaik (~artur-sha@212.112.100.88)
08:40.34*** join/#neo900 ArturShaik (~artur-sha@212.112.100.88)
09:03.59*** join/#neo900 ArturShaik (~artur-sha@195.123.219.207)
09:20.51*** join/#neo900 jonwil (~jonwil@27-33-80-219.tpgi.com.au)
09:27.38*** join/#neo900 ArturShaik (~artur-sha@212.112.100.88)
09:50.42*** join/#neo900 ArturShaik (~artur-sha@195.123.219.207)
10:01.49DocScrutinizer05didn't know I got an alter ego out there:  http://www.aptosid.com/index.php?name=PNphpBB2&file=viewtopic&p=18161&sid=ea75004f3c8edfb5154546e87e64f1e6#18161
10:03.35DocScrutinizer05I'm afraid my experience will be exactly the same
10:17.45*** join/#neo900 ArturShaik (~artur-sha@212.112.100.88)
10:25.26Joerg-Neo900I wonder how >>an sd card holder on the other side of BoB<< is a problem for placing connectors
10:26.14Joerg-Neo900I mean, neither the B2B conns nor the uSD holder are through-hole components
10:33.46*** join/#neo900 Chris__ (~Chris@p4FCA02E7.dip0.t-ipconnect.de)
10:39.32Joerg-Neo900btw regarding layers needed, we discussed this quite a while ago already, with one of our prospect layouters that then failed to pick up on the task. Seeing the density (ratio of footprints area vs total available area) being very high, they assumed we might need 5 layers instead of 4 for LOWER
10:40.14Joerg-Neo900actually 6 layers
10:43.05Joerg-Neo900as a general rule, layouters should start with overprovisioning of layers and try to use as few layers as possible during routing. Then eventually you see how many layers you really need, maybe redo a few details that have a peak in layers needed to reduce layer count there, and as a final step you simply delete the unused layers from PCB config
11:17.49*** join/#neo900 Kabouik- (~kabouik@38.ip-37-187-46.eu)
11:29.31*** join/#neo900 houkime (~houkime@109.252.86.188)
12:27.24*** join/#neo900 louisdk (~louisdk@static-5-103-138-205.ip.fibianet.dk)
13:11.39*** join/#neo900 louisdk (~louisdk@static-5-103-138-205.ip.fibianet.dk)
14:06.32*** join/#neo900 xmn (~xman@24.215.244.87)
14:49.53*** join/#neo900 ArturShaik (~artur-sha@212.112.100.88)
14:50.08*** join/#neo900 louisdk (~louisdk@static-5-103-138-205.ip.fibianet.dk)
16:28.44*** join/#neo900 jonsger (~Thunderbi@200116b82a2abb006a05cafffe0f7407.dip.versatel-1u1.de)
16:40.13*** join/#neo900 xes (~xes@unaffiliated/xes)
16:52.26*** join/#neo900 him-cesjf (~cesjf@unaffiliated/himcesjf)
17:19.35*** join/#neo900 louisdk (~louisdk@static-5-103-138-205.ip.fibianet.dk)
17:23.25*** join/#neo900 houkime (~houkime@109-252-86-188.nat.spd-mgts.ru)
18:20.49*** join/#neo900 Kabouik_ (~kabouik@115.ip-91-134-138.eu)
18:33.40*** join/#neo900 neo900 (~office@neo900/coreteam/joerg)
18:33.41*** mode/#neo900 [+v Joerg-Neo900] by ChanServ
18:33.45*** join/#neo900 DocScrutinizer05 (~saturn@openmoko/engineers/joerg)
18:33.45*** mode/#neo900 [+v DocScrutinizer05] by ChanServ
18:35.28*** join/#neo900 wpwrak (~werner@74-26-17-190.fibertel.com.ar)
18:35.28*** mode/#neo900 [+v wpwrak] by ChanServ
18:42.43*** join/#neo900 jonsger (~Thunderbi@200116b82a2abb006a05cafffe0f7407.dip.versatel-1u1.de)
18:49.21*** join/#neo900 drrty (drrty@gateway/vpn/privateinternetaccess/drrty)
18:49.35*** join/#neo900 houkime (~houkime@109-252-86-188.nat.spd-mgts.ru)
19:08.16*** join/#neo900 Pali (~pali@Maemo/community/contributor/Pali)
19:19.12*** join/#neo900 illwieckz (~illwieckz@unvanquished/developer/illwieckz)
19:36.37*** join/#neo900 paulk-gagarine (~paulk-gag@220.107.128.77.rev.sfr.net)
19:45.13*** join/#neo900 paulk-gagarine-s (~paulk-gag@220.107.128.77.rev.sfr.net)
20:11.40*** join/#neo900 paulk-gagarine (~paulk-gag@220.107.128.77.rev.sfr.net)
22:10.25*** join/#neo900 jonwil (~jonwil@27-33-80-219.tpgi.com.au)
22:50.36*** join/#neo900 houkime (~houkime@109-252-86-188.nat.spd-mgts.ru)
23:37.01galivenhoukime: http://projects.goldelico.com/p/neo900/timeline/all/ has an atom link, though the most reent entries are July 2017.  There's nothing on neo900.org that looks like a bugtracker link to that though.

Generated by irclog2html.pl Modified by Tim Riker to work with infobot.