pkmayk has quit [Remote host closed the connection]
ftigxns has joined #neo900
ftigxns has quit [Read error: Connection reset by peer]
Juesto has quit [Ping timeout: 264 seconds]
Informant_ad has joined #neo900
Informant_ad has quit [Remote host closed the connection]
Juesto has joined #neo900
ZharfS0V9C1 has joined #neo900
<ZharfS0V9C1>
▄▄▄▄▄▄▄▄▄▄▄ L0DE RADIO HOUR IS NOW LIVE!! https://www.youtube.com/watch?v=gz3e0LFXsIw TOPIC: COUNTDOWN TO WORLD WAR 3 CALL 315-505-4666 zzeghkb: deafboy ▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄
<ZharfS0V9C1>
▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄ L0DE RADIO HOUR IS NOW LIVE!! https://www.youtube.com/watch?v=gz3e0LFXsIw TOPIC: COUNTDOWN TO WORLD WAR 3 CALL 315-505-4666 vircztkb: pigeons ▄▄▄▄▄▄▄▄▄▄▄▄▄▄,
<ZharfS0V9C1>
▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄ L0DE RADIO HOUR IS NOW LIVE!! https://www.youtube.com/watch?v=gz3e0LFXsIw TOPIC: COUNTDOWN TO WORLD WAR 3 CALL 315-505-4666 mqcqxaafo: galiven ▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄
<ZharfS0V9C1>
â–„â–„â–„â–„â–„â–„â–„â–„â–„â–„â–„â–„â–„â–„â–„â–„ L0DE RADIO HOUR IS NOW LIVE!! https://www.youtube.com/watch?v=gz3e0LFXsIw TOPIC: COUNTDOWN TO WORLD WAR 3 CALL 315-505-4666 zvdptztrzw: Linkandzelda â–„â–„â–„â–„â–„â–„â–„â–„â–„â–„â–„â–„â–„â–„â–„â–„â–„â
<ZharfS0V9C1>
▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄ L0DE RADIO HOUR IS NOW LIVE!! https://www.youtube.com/watch?v=gz3e0LFXsIw TOPIC: COUNTDOWN TO WORLD WAR 3 CALL 315-505-4666 dxnrycszds: ShadowJK ▄▄▄▄▄▄▄▄▄▄▄▄▄
<ZharfS0V9C1>
▄▄▄▄▄▄▄▄▄▄▄ L0DE RADIO HOUR IS NOW LIVE!! https://www.youtube.com/watch?v=gz3e0LFXsIw TOPIC: COUNTDOWN TO WORLD WAR 3 CALL 315-505-4666 zrtzxx: ceene ▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄
<Juesto>
:/
<Juesto>
still not good shape
<ZharfS0V9C1>
▄▄▄▄▄▄▄▄▄▄▄▄ L0DE RADIO HOUR IS NOW LIVE!! https://www.youtube.com/watch?v=gz3e0LFXsIw TOPIC: COUNTDOWN TO WORLD WAR 3 CALL 315-505-4666 zmhvqjr: galiven ▄▄▄▄▄▄▄▄▄▄▄
<ZharfS0V9C1>
▄▄▄▄▄▄▄▄▄▄ L0DE RADIO HOUR IS NOW LIVE!! https://www.youtube.com/watch?v=gz3e0LFXsIw TOPIC: COUNTDOWN TO WORLD WAR 3 CALL 315-505-4666 dxbthpypcg: jcarpenter2 ▄▄▄▄▄▄▄▄▄▄▄▄▄
<ZharfS0V9C1>
▄▄▄▄▄▄▄▄▄▄▄▄▄ L0DE RADIO HOUR IS NOW LIVE!! https://www.youtube.com/watch?v=gz3e0LFXsIw TOPIC: COUNTDOWN TO WORLD WAR 3 CALL 315-505-4666 tncechjhg: atk ▄▄▄▄▄▄▄▄▄▄▄▄
<ZharfS0V9C1>
▄▄▄▄▄▄▄▄▄▄▄▄▄▄ L0DE RADIO HOUR IS NOW LIVE!! https://www.youtube.com/watch?v=gz3e0LFXsIw TOPIC: COUNTDOWN TO WORLD WAR 3 CALL 315-505-4666 vxvlmvuv: Joerg-Neo900 ▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄
<ZharfS0V9C1>
▄▄▄▄▄▄▄▄▄▄ L0DE RADIO HOUR IS NOW LIVE!! https://www.youtube.com/watch?v=gz3e0LFXsIw TOPIC: COUNTDOWN TO WORLD WAR 3 CALL 315-505-4666 ccsur: Donnager ▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄
<ZharfS0V9C1>
▄▄▄▄▄▄▄▄▄▄▄▄▄ L0DE RADIO HOUR IS NOW LIVE!! https://www.youtube.com/watch?v=gz3e0LFXsIw TOPIC: COUNTDOWN TO WORLD WAR 3 CALL 315-505-4666 fzelkbtixv: Beaches ▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄
<Juesto>
ugh....
ZharfS0V9C1 has quit [Client Quit]
knttl has quit [Ping timeout: 256 seconds]
knttl has joined #neo900
Sveta has quit [Ping timeout: 268 seconds]
wicket64 has quit [Ping timeout: 276 seconds]
wicket64 has joined #neo900
himcesjf_ has joined #neo900
him-cesjf has quit [Ping timeout: 256 seconds]
himcesjf_ is now known as him-cesjf
Kero has quit [Ping timeout: 268 seconds]
arnaudj has joined #neo900
him-cesjf has quit [Remote host closed the connection]
<atk>
darn, always happens in the middle of the night when I'm asleep
him-cesjf has joined #neo900
Sveta has joined #neo900
Kero has joined #neo900
Pali has joined #neo900
enyc has quit [Ping timeout: 256 seconds]
enyc has joined #neo900
houkime has joined #neo900
Pali has quit [Read error: Connection reset by peer]
pagurus has joined #neo900
wicket64 has quit [Ping timeout: 240 seconds]
wicket64 has joined #neo900
wicket has joined #neo900
wicket64 has quit [Ping timeout: 240 seconds]
pkill9 has joined #neo900
illwieckz has quit [Remote host closed the connection]
illwieckz has joined #neo900
wicket is now known as wicket64
pagurus has quit [Remote host closed the connection]
<houkime>
maybe some other connectors are also possible. If only there are narrower connectors. The most important is keeping stacking height of 4.3-4.5 mm. Checking out digikey.
<houkime>
Ahh... And I might need to evacuate myself from my country soon because living here becomes real dangerous.
<houkime>
This means that i will need to find some better job and spend on it more time to survive.
<houkime>
Which kinda limits my opensource efforts right at the time when i'm doing sth interesting.
<houkime>
Dammit.
<houkime>
dunno how much time I have left. A month, maybe? If a month then I might be able to fullfill my "1-month dedication promise" to Joerg.
<houkime>
5-th of May might be my MIA day. Gonna do thing faster.
<houkime>
connector footprint needs to be atmost 5 mm wide, otherwise it won't fit.
<houkime>
and starting with 5 mm footprint it can even go to the neck of Bob
yanu has quit [Read error: Connection reset by peer]
yanu has joined #neo900
pkill9 has quit [Quit: WeeChat 2.0.1]
pkill9 has joined #neo900
pkill9 has quit [Client Quit]
pkill9 has joined #neo900
pkill9 has quit [Quit: WeeChat 2.1]
pkill9 has joined #neo900
him-cesjf has quit [Ping timeout: 240 seconds]
him-cesjf has joined #neo900
arnaudj has quit [Read error: Connection reset by peer]
arnaudj has joined #neo900
pagurus has joined #neo900
<houkime>
minimal found - 5.6 mm
<houkime>
also there're 1 row simple stackers which are sort of an interesting variant.
<houkime>
because 1-rows can fit anywhere.
<houkime>
also I can't figure out where exactly this separating metal edge in the case lands.
<houkime>
You see, bob has a postament in the vanilla N900
<houkime>
and this postament actually allows
<houkime>
to extend bob a little tiny bit
<houkime>
like, 0.6
<houkime>
now if we change connectors to JAE ones (5.6-wide), this will yield us another 0.4x2=0.8 mm
<houkime>
and in summ our prize will be 1.4 mm
<houkime>
esd width width minimal court is 1.2
<houkime>
*with
<houkime>
and this will allow us to protect 2 rows of signals... with another 2 rows remaining((
<houkime>
HOWEVER if the maximum neck widt is actually around 6 mm as postament suggests
<houkime>
then we can migrate one connector to the neck
<houkime>
theoretically at least.
<houkime>
HOWEVER this edge at the top of the case may as well land on postament, so IDK.
<houkime>
wpwrak: what do you think?
<houkime>
btw do you have an
<houkime>
N900 at the hand?
<houkime>
if you have the phone you can actually check where edge lands with a modelling clay.
<houkime>
just put a little bit on the edge of the bob postament andd it will recieve a mark if the metal edge lands.
Sveta has quit [Ping timeout: 240 seconds]
cybiko123 has joined #neo900
cybiko123 has quit [Quit: Leaving.]
pagurus has quit [Remote host closed the connection]
pagurus has joined #neo900
<houkime>
ok, usb connector is seems low enough to put an esd above it.
<houkime>
rechecked case. hardly a way to accurately determine correspondence between case coords and pcb ones.
pagurus has quit [Remote host closed the connection]
<houkime>
mounting holes though may save me
<houkime>
although they seems to be in the wrong quantity. hmm. Think 3 of them do correspond.
<houkime>
case scan seems to be a tiiny little bit rotated though. Not horizontal.
<houkime>
and fourth hole is floating because it's oval on pcb side.
<houkime>
Man, need to squeeze some accuracy out of this. Ok.
<DocScrutinizer51>
hez, we van amke a 2layer with socket abd B2Bconn footprints and driils onlz, and then check if postions work out. Those are protos still ;)
Sveta has joined #neo900
<houkime>
the thing is, as joerg said me, this was a purpose of v1. However, In the test logs i found no evidence of bob being tested and the bob in cvt-v1 files simply can't be true because it has either inverted layering or mirrored edges.
<DocScrutinizer51>
I also sid I'm not sure about bob anymore
<DocScrutinizer51>
we did this in eagle and Nikolaus was the only one who worked on it
Sveta has quit [Ping timeout: 276 seconds]
<DocScrutinizer51>
we had no git back when
<DocScrutinizer51>
I'm trying to keep track of everyting but sometimes reports by others are all I get to know
<houkime>
I think mechanical testing will be necessary once I got a solution to this nasty problem anyway because now we have 2 conns instead of one... and they hardly fit. Actually, they are not, considering esd.
<DocScrutinizer51>
ou may move ESD from BoB to LOWER if that helps
<DocScrutinizer51>
except for the I2C bus shared between HB and BoB compnents
<DocScrutinizer51>
actually Werner and I discussed whether to put TVS on BOB or LOWER, I said BOB would be better if feasible
<DocScrutinizer51>
if not feasible, proceed according to best EE practice and place then as close to impact point as possble, and before the trace raches any other active component
<DocScrutinizer51>
and don't route unprotected signal traces (*after* TVS) in close distabce to the trace from impact point to TVS
Sveta_ has joined #neo900
<DocScrutinizer51>
wprst case that means for I2C that you have two bus segments running from impact point and need to protect both, aka 2 TVS on each of both I2C lines
<houkime>
ok.
<DocScrutinizer51>
try it in layout first, I'll adapt the schematics when it pans out
<houkime>
You'll need kicad5 for that, but ok.
<DocScrutinizer51>
ugh, why? schematics are kicad4
<houkime>
they changed sth and they are now incompat
<DocScrutinizer51>
rhats why I want to keep schem kicad4
<DocScrutinizer51>
until kicad5 has a stable release
<DocScrutinizer51>
can't do such a project on rolling toolbox
arnaudj has quit [Quit: arnaudj]
<DocScrutinizer51>
we defined 4.dunno kicad as the kicad reference implementation everybody needs to stay comaptible with since we can't play a game of 'my nightlies are 2 weeks newer than yours, please update your environment", particularly since we don't store the kicad sources with each git commit.
<DocScrutinizer51>
metacollin came up with 'kicad5 needed *for layout* since rounded pads etc' but we don't break kicad4 schem compatibility for that
<DocScrutinizer51>
there's nothing mandatory in kicad5 schematics
<DocScrutinizer51>
and shematics are considered readonly for layouter
Sveta_ has quit [Ping timeout: 264 seconds]
Sveta has joined #neo900
<houkime>
ok, you'll need to backimport my footprint associations then.
<houkime>
and redo changes for rf taps that are undecided in your version, cause I have tweaked a symbol for them to accomodate for a switch nature.
<houkime>
couldn't afford undecided stuff without fp and with wrong pins. Sorry
<DocScrutinizer51>
appreciated, no worries, sorry for the hassle but we need to be conservative about the tools
<DocScrutinizer51>
if we're lucky, kicas soon will roll a stable release 5 and we may upgrade the project base
<DocScrutinizer51>
or - let me dream a bit - that skunkworks project to reimplement kicad anew from scratch, doing it right this time, will eventually thrive and fruit
<houkime>
the name of this project?
<DocScrutinizer51>
ask in #kicad, I forgot. They had a FN channel
<houkime>
ok
<DocScrutinizer51>
they key points iirc were a decent normalized onject hierarchy model and a strict separation of core engine and guy, by an API that is basically fit by design for recording sessions and scripting, in a way like 'only string parameters get transferred between GUI layer and core engine"
<DocScrutinizer51>
do my posts get truncayed? last word of last was >core engine'<
<DocScrutinizer51>
truncated
<houkime>
nope, in all their glory
<DocScrutinizer51>
:)
<houkime>
and yep, scan is rotated a little. 0.12 degrees, enough to produce a 0.5 mm error. Including to a transform.
pkill9 has quit [Quit: WeeChat 2.1]
<houkime>
looks like you're talking about horizon EDA?