| ID: | 2486 |
| From: | ge...@igor2.repo.hu |
| Date: | Mon, 26 Nov 2018 03:18:59 +0100 (CET) |
| Subject: | Re: [pcb-rnd] Re: Subject: Digest of pcb-rnd@list.repo.hu issue 118 |
| in-reply-to: | 2485 from Erich Heinzle <a1...@gmail.com> |
Hi Erich, On Mon, 26 Nov 2018, Erich Heinzle wrote: >This is some "callout" documentation I found, FWIW > >https://www.altium.com/documentation/18.0/display/ADES/Draftsman_Obj-Callout((Callout))_AD > >https://www.reddit.com/r/PrintedCircuitBoard/comments/9vjtg3/what_is_a_callout/ > >https://www.reddit.com/r/PrintedCircuitBoard/comments/7wut22/how_do_i_export_my_slot_files_to_oshparks/ > >https://downstreamtech.com/support/support-blueprint/BluePrintQuickStart-new.pdf Thanks, I found similar links: all "where to click in specific prorpietary software" but no "how does it look like in the exported file". We can't do callouts withot the latter. > >I have a non mission critical board I can send to OSH park as a test >that has some slots, as soon as we figure out their required format. Meanwhile Anthony wrote them a ticket asking about why they don't parse our files correctly and it turned out their import layer breaks on totally valid excellon files, because of white space. I've already added a workaround so it should work now. No callouts included only G85 or G00. Regards, Igor2
Reply subtree:
2486 Re: [pcb-rnd] Re: Subject: Digest of pc...@list.repo.hu issue 118 from ge...@igor2.repo.hu