<xiangfu>
how to test CONNECTTIME_OUT?, just give a wrong gateway ?
<kristianpaul>
ping google?
<lekernel>
aw, everything ok with the gerber?
<aw>
lekernel, so far now is okay though
<lekernel>
so I can publish the one you sent yesterday?
<aw>
about 20 minutes later, I'll send to list and you can check.
<aw>
no
<aw>
wait for me about 20 minutes though
<aw>
I'll send to list for final design & gerber . :-)
<GitHub99>
flickernoise: master Sebastien Bourdeauducq * 83b6c8f (1 files in 1 dirs): Update: display different explanation in rescue mode - http://bit.ly/mS6Lhu
<aw>
lekernel, just sent.
<lekernel>
cool, thanks.
<lekernel>
how long does NH take to make the pcbs, btw?
<aw_>
usually 1~2 days to confirm files they receive and verify well, 7 days for making though; not include weekend.
<aw_>
the smt date is the mostly that i can't control though. :-)
<lekernel>
ok, so I'd guess those things can go through assembly around June 21?
<aw_>
every year before Septermber, the smt date is typically to book since our qty is still not so such big scale. but it's okay..the smt vendor is nice to us just need to check though.
<aw_>
not sure now
<Guest42148>
lekernel: It'll be mid-July until everything is settled, I think.
<Guest42148>
oops, guest account :-) wolfgang here...
<lekernel>
including box, case assembly, etc.?
<wolfspraul>
yes exactly
<wolfspraul>
and also Adam will need some more time, defining this as June 21st now is not a good idea
<lekernel>
more time for what?
<wolfspraul>
for work
<lekernel>
mh, sure, but what kind of work? now that the pcb's are sent, what else needs to be done?
<wolfspraul>
they are not sent yet
<wolfspraul>
there are always surprises, always details. I don't need unrealistic plans that I then have to adjust many times along the way.
<wolfspraul>
you know this manager rule when dealing with estimates - "whatever the engineer says times two"
<wolfspraul>
I don't see any major blockers anymore though, we have so many things in place.
<wolfspraul>
it should be unstoppable now :-)
<wolfspraul>
lekernel: if you have time you can think about the Milkymist logo on the top acrylic. I heard all sorts of ideas with sanding etc.
<wolfspraul>
it will be good for the brand
<wolfspraul>
I'm not pursuing that though, so I'm moving forward without this right now.
<wolfspraul>
we can always do this later
<lekernel>
yeah, I should see roh, but it seems it's difficult to meet him atm ... :(
<lekernel>
so many things are so painfully slow...
<wolfspraul>
maybe they just appear so, you need a little more faith into the team :-)
<wolfspraul>
I am working on m1 every day
<wolfspraul>
and only on m1
<lekernel>
aw_, the slot holes of the DC power supply jack look funny in Altium
<lekernel>
they have a very small circular hole in the middle...
<aw_>
yes, no problem on them which rc1 &Â Â rc2 didn't have, but it's okay that you can see the gerber's drill hole is okay.
<aw_>
so rc2 is 39.37 mil * 125.98 mil , now rc3 is 31.5 * 125.59 mil
<lekernel>
ok, ok :)
<lekernel>
so you edit the drill file manually after Altium generates it?
<aw_>
not me, by house, yes, it's did by manually
<aw_>
in design file it's setting with "round" type,
<lekernel>
why do it like that? it sounds painful and a source of human errors
<aw_>
so when they generated drills, they noticed surely it's a type of round. :-)
<aw_>
well...if it's said that, of course, you can check rc2, it's round with "0" size drill mm.  in design file. :-)
<aw_>
but in drill file, it was not.
<aw_>
so this time in rc3, i added them with 31.5mm round.
<aw_>
have you done on DRC there?
<aw_>
should be only 18 warnings. :-) which is okay.
<lekernel>
ah, so you fixed many undue DRC warnings which were there in rc2?
<lekernel>
good
<aw_>
last time rc2, it seemed that had 40 warnings.
<aw_>
if all followed Altium internal s/w rules, i'll go crazy. :(Â Â well...surely if all warnings are gone like build in C. it's perfect.
<aw_>
which tool you usually view gerber in windows laptop?
<aw_>
or you view it in linux laptop?
<lekernel>
I use gerbv in Linux
<aw_>
ok, that gerbv does not easily change layers to view compared to CAMtastic! 2000
<lekernel>
you mean change the order of layers?
<aw_>
yes
<lekernel>
it does, click on the top/down arrows in the bottom left
<lekernel>
this moves the selected layer up and down
<aw_>
yeah...so not easy to view though.
<aw_>
btw, have you seen Y2's Keep-Out layer?
<lekernel>
no, why?
<aw_>
my patched in rc2 i soldered Y2 at bottom side, I hope the placement now with Y2 doesn't influence those parallel lines connected to fpga
<aw_>
wpwrak, wow...those images done by smart way. i didn't know then. :-)
<wpwrak>
aw_: project eda-tools, fab/prettygerbv
<aw_>
wpwrak, when view the new parts added, I usually use close s/w gerber viewer to click "check" of each layer, so for examples that i can know if the through hole pins with good drill without touching other layers
<wpwrak>
aw_: you'll need to change the file names and such, but the things is quite straightforward and probably not too hard to adapt to non-kicad systems
<aw_>
wpwrak, hup? already existed there, maybe i can try that in JTAG run2 to see.
<wpwrak>
aw_: if you have the drill data also as gebers, you can also include it. otherwise, you'd have to convert it to gerber. i've written a script that does that for kicad's excellon files (fab/drl2gerber), but that probably won't work with drill files from other sources
<wpwrak>
aw_: (click through layers) yes, that's how i often go through them, too, when looking for details. the overview images are more for a quick impression of the whole thing. sometimes, you can overlook the big mistake hidden in all the small details ;-)
<aw_>
wpwrak, yeah...caused i heard few cases that even design files are correct, then the generated gerber files are not same as design ones. indeed felt badly a bit, so when i view gerber,  i use that close tool which is really better than gerbv.
<aw_>
wpwrak, so i admire people can write scripts to overcome own cares. phew...i still don't know script language though.
<wpwrak>
aw_: the difficult part was finding a set of colors that works (gerbv's color mixing algorithm is a bit difficult to predict). then front(), back(), etc. provide the file names. that's pretty much all.
<wpwrak>
let's see what MM1 would look like ...
<aw_>
wpwrak, :-), are you going to try your scripts on rc3 gerbers? :-)
<wpwrak>
does altium always use the same numbers for the file names or is that project-dependent ? e.g., would the top solder paste always be called sm0626.pho ?
<wpwrak>
err, i mean smd0129
<aw_>
wpwrak, i am not sure, but you can define them firstly. :-)
<aw_>
wpwrak, can you import sm0626.pho?
<wpwrak>
yeah, i can read everything. also the drill file converts
<wpwrak>
converts, but wrongly. but that's thanks to the quirks of those stone-age formats ... let's see how they do their decimal points ...
<aw_>
wpwrak, he :-) time to go, you can reply my email if a smart tool applies it with beautiful works/images later. :-)
<wpwrak>
heh, drill file and layers don't use the same origin :)
<wpwrak>
i'm beginning to realize why the fabs are so obsessed with fiducials ;)
<wpwrak>
oh sweet. numbers are left-padded. and i thought hannibal lector was a wicked man.
<wpwrak>
lectEr
<wpwrak>
well, "padded" is the wrong word. aligned. e.g., what sane humans would call 1, 10, and 100, would be something like 001, 01, 1
<wpwrak>
probably useful to get the maximum accuracy out of each number before your relays overheat processing it ...
<wpwrak>
cute. the drill file expresses slotting operations as tools with an insane spindle speed. i guess just using a G command would have lacked coolness
<wpwrak>
(insane = 794'000 rpm. well, or maybe stuxnet now also infects altium ;-)
<wpwrak>
hmm no. the heuristics must be different. *scratch,scratch*
<xiangfu>
change the IR test image to wait button '1' ~ '9' then '0', some remote controller don't have Volumeup or Standby makeby. but most of them have '0' ~ '9' :)
<GitHub147>
autotest-m1: master Xiangfu Liu * 55852b2 (1 files in 1 dirs): tests_ir: change the test buttons to 1 ~ 9, 0 - http://bit.ly/kZaqT0
<lekernel>
wpwrak, nice gerber pics :)
<wpwrak>
thanks ! :) now, the real challenge is in the connectivity view ... in addition to the inherent complexity of having multiple layers, gerbv's color-merging algorithm also produces very counter-intuitive results
<wpwrak>
btw, i'm not sure to what extent the lack of drill vs. mill indications in the drill file could be an issue for the pcb fab. right now, it looks as if they'd have to add this information manually, which bears a risk of human error
<GitHub102>
milkymist: master Xiangfu Liu * f4d446a (1 files in 1 dirs): rc5.v: fixed the timing problem thanks Jack ... - http://bit.ly/j41bUH
<GitHub81>
mtk: master Sebastien Bourdeauducq * 8aeb1a0 (5 files in 2 dirs): Basic translation support - http://bit.ly/kmSzld
<GitHub191>
flickernoise: master Sebastien Bourdeauducq * 570172b (5 files in 1 dirs): Basic translation support - http://bit.ly/lPG3HA
<GitHub198>
flickernoise: master Sebastien Bourdeauducq * b3285e5 (1 files in 1 dirs): More French translations - http://bit.ly/je36xU