IRC log for #neo900 on 20180403

00:00.46Joerg-Neo900I'm not sure, but it doesn't matter in the end. PCB house gets picked according to what PCB grade we need (precision, resolution, vias etc)
00:02.14Joerg-Neo900you build the PCB as "low tech" as possible (don't use sophiosticated stuff like stacked microvias, microtraces etc if not necessary), then when the layout is clear you find a PCB house that can do what you need
00:04.53houkimeok I guess for material -dependent calculations i will need to deduce a material that doesn't break the work that is already done.
00:07.29houkimeand this time i will make documentation so that stuff never happens again.
00:10.02Joerg-Neo900sounds good. Actual impedance-matched lines are done by the PCB house afaik
00:15.33*** join/#neo900 houkime (~houkime@ppp109-252-49-23.pppoe.spdop.ru)
01:35.16houkimefun things about gemalto. https://theintercept.com/2015/02/19/great-sim-heist/
01:38.04houkime(now I do really want open silicon. Ideally self-made. Gonna sleep)
01:41.46*** join/#neo900 knttl (~knttl@host-091-097-092-006.ewe-ip-backbone.de)
01:41.53Joerg-Neo900February 19 2015
01:43.07*** join/#neo900 pkill9 (~pkill9@unaffiliated/pkill9)
01:43.21Joerg-Neo900iirc what been stolen were the hidden pubkeys used to answer a auth challenge during log in, aka the Ki
01:44.25Joerg-Neo900leaving the SIM cards that were involved vulnerable to cloning
01:55.36*** join/#neo900 houkime (~houkime@ppp109-252-49-23.pppoe.spdop.ru)
01:56.51houkimeActually now that I'm thinking about it, the most realistic solution would be to place a baseband processor on an FPGA.
01:57.54houkimeFPGA should really eliminate all realisitical possibilities of silicon exploits, because no man can predict what you put in there beforehand.
02:01.22houkimeSo all one needs is to help osmocomm guys to hack gsm and then reimplement it as a design to load into FPGA.
02:37.53*** join/#neo900 threebar (~user@unaffiliated/threebar)
02:38.33*** join/#neo900 threebar (~user@pool-71-105-108-82.nycmny.fios.verizon.net)
02:38.33*** join/#neo900 threebar (~user@unaffiliated/threebar)
03:15.33*** join/#neo900 luke-jr (~luke-jr@unaffiliated/luke-jr)
04:42.50*** join/#neo900 ArturShaik (~artur-sha@212.112.100.88)
05:46.29*** join/#neo900 ArturShaik (~artur-sha@212.112.100.88)
05:53.35*** join/#neo900 boq_ (~boq@46.28.202.8)
06:09.05*** join/#neo900 ArturShaik (~artur-sha@212.112.100.88)
06:37.45*** join/#neo900 ArturShaik (~artur-sha@212.112.100.88)
07:46.11*** join/#neo900 pkill9 (~pkill9@unaffiliated/pkill9)
07:49.06*** join/#neo900 Kabouik (~kabouik@158.38.1.70)
07:49.41*** join/#neo900 Kabouik (~kabouik@158.38.1.70)
08:18.09*** join/#neo900 ArturShaik (~artur-sha@212.112.100.88)
08:25.35*** join/#neo900 ArturShaik (~artur-sha@212.112.100.88)
08:26.04*** join/#neo900 boq (~boq@46.28.202.8)
09:10.45*** join/#neo900 xes (~xes@unaffiliated/xes)
09:25.23*** join/#neo900 houkime (~houkime@ppp109-252-49-23.pppoe.spdop.ru)
09:50.25*** join/#neo900 ArturShaik (~artur-sha@212.112.100.88)
09:51.57*** join/#neo900 Kabouik (~kabouik@158.38.1.70)
10:06.24*** join/#neo900 boq (~boq@46.28.202.8)
10:43.53*** join/#neo900 xes (~xes@unaffiliated/xes)
12:33.25*** join/#neo900 Kabouik (~kabouik@158.38.1.70)
12:38.25*** join/#neo900 Kabouik (~kabouik@158.38.1.70)
13:00.53*** join/#neo900 yanu (~yanu@178-116-60-189.access.telenet.be)
14:23.03*** join/#neo900 dos11 (~dos1@neo900/coreteam/dos)
14:23.03*** mode/#neo900 [+v dos11] by ChanServ
14:47.09*** join/#neo900 dos1 (~dos1@neo900/coreteam/dos)
14:47.09*** mode/#neo900 [+v dos1] by ChanServ
14:49.13*** join/#neo900 _whitelogger (~whitelogg@uruz.whitequark.org)
14:49.13*** mode/#neo900 [+v _whitelogger] by ChanServ
15:02.26*** join/#neo900 webmeister (webmeister@unaffiliated/webmeister)
15:16.42*** join/#neo900 illwieckz (~illwieckz@unvanquished/developer/illwieckz)
15:22.36*** join/#neo900 pagurus` (~user@i53874DEA.versanet.de)
15:32.19*** join/#neo900 _Chris_ (~Chris@p4FCA0E81.dip0.t-ipconnect.de)
15:59.43*** join/#neo900 Chris__ (~Chris@p4FCA02B2.dip0.t-ipconnect.de)
16:23.44*** join/#neo900 Pali (~pali@Maemo/community/contributor/Pali)
16:57.42*** join/#neo900 himcesjf_ (~cesjf@unaffiliated/himcesjf)
17:10.03houkimeOk, I investigated situation with rf taps.
17:10.47houkimeAm i right that v2 will use U.FL SMT HIROSE connectors as taps like in v1?
17:12.47houkimeand that i can borrow the footprints for them from tested v1 design?
17:15.56DocScrutinizer51yes, Hirose sounds good and U.FL mifgt be correct
17:15.56DocScrutinizer51teay wre in V1 right
17:15.56DocScrutinizer51they*
17:16.14houkimethe thing is that on v2 schematic there are 2 signal pins (and 2 gnd) for a tap.
17:17.17houkimeso schematics needs to be updated for Hirose usage (correct pin names and such)?
17:18.23houkimeschematics indicate 2 unnamed pins (inout), but hirose uses only one (and 2 GND)
17:18.47houkimev1 schematics is correct in this regard.
17:18.51DocScrutinizer51I guess that's the reason. We need jack with switch (in-out)
17:19.56houkimeok, there's another jack in v1 and it has in-out.
17:19.58DocScrutinizer51prolly nobody found / searched a matching component
17:20.01houkimeit is a murata one
17:20.20houkimebut murata has 4 GND pins
17:21.12houkimeMM8430-2600RA1
17:22.58houkimein v1 there was no jacks with switches on GNSS line, just hirose's but in v2 they should be with switches?
17:23.02DocScrutinizer51do you understand the purpose of the jack? either internal or attached 'antenna'
17:23.02DocScrutinizer51please choose an appropriate component
17:23.02DocScrutinizer51sorry Im on mobile so can't search right now
17:23.14DocScrutinizer51yes
17:23.20DocScrutinizer51some shall
17:24.29houkimecan you please be more specific? on v2 schematics all taps are identical.
17:24.31DocScrutinizer51or even all, cant tell right now
17:24.31DocScrutinizer51sorry I suffer disconnects here
17:24.54houkimeok
17:28.37DocScrutinizer51sorry not now, I don't have access to schematics now
17:28.37DocScrutinizer51use switched everywhere, optimaze later ;)
17:29.33houkimeok, will try
17:29.51DocScrutinizer51ta
17:45.24*** join/#neo900 _Chris_ (~Chris@p4FCA02B2.dip0.t-ipconnect.de)
18:02.23Joerg-Neo900yes, for v2 we decided to sue switched ones everywhere
18:05.44Joerg-Neo900houkime: I can't find MM8430-2600RA1
18:06.03Joerg-Neo900http://www.murata.com/products/catalog/pdf/o33e.pdf
18:07.30Joerg-Neo900found it, 3x3mm
18:08.00Joerg-Neo900wiw, 500 mating cycles
18:08.07Joerg-Neo900wow even
18:08.14Joerg-Neo900but "huuge"
18:09.57Joerg-Neo900how about MM8930-2600  1.7^2mm
18:10.14*** join/#neo900 arnaudj (~Thunderbi@85-171-19-190.rev.numericable.fr)
18:14.50*** join/#neo900 l_bratch (~l_bratch@serenity.bratch.co.uk)
18:19.59atk500 mating cycles, as in it's rated to only be used 500 times?
18:20.09atkthat seems awfully low
18:20.21Joerg-Neo900it's a test jack
18:20.26atkoh I see
18:20.34Joerg-Neo900they are often rated at 50 only
18:20.57atkso they sell the things which don't pass QC for a lower price as "test" grade?
18:21.19Joerg-Neo900it IS test, as in "factory calibration"
18:21.40Joerg-Neo900typically gets used one single time in product lifespan
18:23.21Joerg-Neo900it's a 1.7x1.6mm 6GHz SWR-ratio <1.2 jack, no surprise the electrical properties might wear out after a small number of mating cycles
18:23.46atkOh I see
18:23.48atkI get it
18:24.45Joerg-Neo900it's not a SMA jack
18:24.48Joerg-Neo900;-)
18:25.33Joerg-Neo900you need a 150$ SMA adaper to connect to that thing
18:29.05Joerg-Neo900umm cheaper, only 30 bucks
18:30.01Joerg-Neo900actually no  https://www.digikey.com/product-detail/en/murata-electronics-north-america/MXHQ87PA3000/MXHQ87PA3000-ND/7926544
18:32.17Joerg-Neo900jacks wear out after 50 to 500 mating cycles - which none of them will see during normal product use. Probe lasts "forever" ;-D
18:33.14Joerg-Neo900jack: 0.37USD, probe 136.26USD
18:46.12*** join/#neo900 lukedashjr (~luke-jr@unaffiliated/luke-jr)
18:46.20*** join/#neo900 janus_ (Janus@bnc.animux.de)
18:53.21*** join/#neo900 drrty2 (drrty@gateway/vpn/privateinternetaccess/drrty)
18:53.53*** join/#neo900 pkill9 (~pkill9@unaffiliated/pkill9)
18:54.15*** join/#neo900 M-DzzzzzzR (dzzzzzzrma@gateway/shell/matrix.org/x-ufwjogcnqqzoedhl)
19:06.08houkimeif we choose this we need to update schematics with 4 ground pins and make a footprint (probably based on catalog pdf). ok
19:07.23Joerg-Neo900well, ok. We might need to update schematics, or we simply ignore the different GND pin count ;-)
19:07.42Joerg-Neo900in footprint you can have multiple pads for same pin afaik
19:52.53*** join/#neo900 boq (~boq@46.28.202.8)
21:11.02*** join/#neo900 c4rc4s (~c4rc4s@unaffiliated/c4rc4s)
21:20.35*** join/#neo900 c4rc4s (~c4rc4s@unaffiliated/c4rc4s)
22:05.23*** join/#neo900 jcarpenter2 (rofl@2601:441:8680:4631:103d:dcf4:56ca:ba2a)
22:14.19*** join/#neo900 arnaudj (~Thunderbi@85-171-19-190.rev.numericable.fr)
22:45.42*** join/#neo900 enyc (~enyc@muddle.enyc.org.uk)
23:04.48*** join/#neo900 xmn (~xman@user-0cdft2n.cable.mindspring.com)
23:08.00*** join/#neo900 xmn (~xman@user-0cdft2n.cable.mindspring.com)

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