... | ... | @@ -5,33 +5,11 @@ |
|
|
installation to CERN environment (setting up libraries, generating
|
|
|
BOM and assembly documentation).
|
|
|
|
|
|
\* <s>Assembly documentation</s>
|
|
|
We should check with people responsible for assembling boards what kind
|
|
|
of documentation do they expect. Alternatively we can open an EDMS
|
|
|
project and see what files are stored in xxx-assy.zip archives.
|
|
|
This probably would require a converter or an export plugin in KiCad.
|
|
|
KiCad should offer export to one of the formats accepted by CircuitCam.
|
|
|
See also the [DEM documentation
|
|
|
convention](https://edms.cern.ch/ui/#!master/navigator/document?d:1453943006:1453943006:subdocs).
|
|
|
*Update**: For assembly documentation we need:
|
|
|
|
|
|
\- Gerbers (ok)
|
|
|
|
|
|
\- drill files (ok)
|
|
|
|
|
|
\- pick and place machine data (ok, generated with a Python script on
|
|
|
DFS (Applications/KiCad/scripts/fab/mounter.py) or using Maxime's Excel
|
|
|
macros)
|
|
|
|
|
|
\- BOM (ok, Python script on DFS
|
|
|
(Applications/KiCad/scripts/bom/cern\_csv\_bom.py), needs further
|
|
|
processing with Maxime's Excel macros)
|
|
|
now we can go with GenCAD exporter, in the future we may
|
|
|
\- ODB** (for now it is substituted with GenCAD)
|
|
|
|
|
|
- <s>Support for long pad names/pin numbers</s>
|
|
|
Required for Altium library import.
|
|
|
Update: fixed in 76d13653
|
|
|
<!-- end list -->
|
|
|
|
|
|
- ODB** or IPC-2581 export
|
|
|
Currently GenCAD export is sufficient, in the future it would be
|
|
|
better to export layout in one of the two formats.
|
|
|
|
|
|
<!-- end list -->
|
|
|
|
... | ... | @@ -47,24 +25,6 @@ now we can go with GenCAD exporter, in the future we may |
|
|
|
|
|
## Eeschema
|
|
|
|
|
|
- <s>Good quality BOM generator</s>
|
|
|
The current user interface is terrible. It requires to choose a file
|
|
|
that provides an xsltproc plugin (if you know where to look for
|
|
|
one). As far as I know, it can generate only .csv files.
|
|
|
A good candidate to fix the problem is Oliver Walters [component
|
|
|
table
|
|
|
viewer](https://lists.launchpad.net/kicad-developers/msg29057.html).
|
|
|
Drop XSLT, switch to Python plugins? **Be sure they are
|
|
|
automatically detected, so all the user has to do is to pick the
|
|
|
output format and settings.**
|
|
|
**Update:** Eeschema is able to take advantage of Python scripts
|
|
|
when generating BOM. There is a Python script that is good enough
|
|
|
for CERN needs, could be upgraded if needed.
|
|
|
Automatic detection of plugins is still needed to improve the user
|
|
|
experience.
|
|
|
|
|
|
<!-- end list -->
|
|
|
|
|
|
- Default fields for new components
|
|
|
Currently there are a few default fields (name, value, footprint),
|
|
|
so for each new component others have to be added manually (e.g.
|
... | ... | @@ -95,39 +55,41 @@ now we can go with GenCAD exporter, in the future we may |
|
|
|
|
|
<!-- end list -->
|
|
|
|
|
|
- <s>Update component field values</s>
|
|
|
There are cases when symbol libraries fields change (e.g. Obsolete
|
|
|
field), but there is no way to reflect the change in already placed
|
|
|
component.
|
|
|
Update: fixed in e29d77c8
|
|
|
- Custom fields for worksheet templates
|
|
|
The fields might store only basic and predefined information
|
|
|
(author/date/a few lines of comments). One should be able to add
|
|
|
custom fields that could be displayed in a worksheet template (page
|
|
|
layout), using e.g. FieldName format.
|
|
|
|
|
|
<!-- end list -->
|
|
|
|
|
|
- Custom fields for worksheet templates
|
|
|
Now there the fields might store only very basic and predefined
|
|
|
information. Ideally should be able to add own fields that could be
|
|
|
displayed in a worksheet template (page layout).
|
|
|
- Easier BOM exporter configuration in eeschema
|
|
|
Check a few standard locations and try to load export plugins.
|
|
|
|
|
|
<!-- end list -->
|
|
|
|
|
|
- Place custom power symbols
|
|
|
Any symbol placed on a schematic sheet needs to be available in the
|
|
|
symbol library, including power supply symbols. The power symbol
|
|
|
library contains a limited set of voltages and usually is stored in
|
|
|
a read-only file, making it even harded to add custom voltages. The
|
|
|
most convenient solution would be to create a requested voltage
|
|
|
power symbol and place in the schematic. It will be much easier to
|
|
|
implement when the new schematic file format is in place.
|
|
|
|
|
|
## Pcbnew
|
|
|
|
|
|
- STEPs
|
|
|
<s>Import and export. It might be already doable with KiCad, I need
|
|
|
to check. Perhaps it requires a few hackish tricks that could be
|
|
|
replaced with a nice UI.</s>
|
|
|
**Update**: STEPs can be easily assigned to footprints and are
|
|
|
correctly displayed by 3D viewer, given the model path is properly
|
|
|
configured.
|
|
|
Pcbnew has also successfully exported a STEP model for the FMC
|
|
|
nanoFIP board. The only missing part are informative error messages
|
|
|
in case the export
|
|
|
does not work (most often lack of continuity of the board outline).
|
|
|
- STEP export
|
|
|
STEP export fails if the board outline is not continuous, but it is
|
|
|
not clear where the continuity breaks. Add an error message pointing
|
|
|
to the faulty spot.
|
|
|
|
|
|
<!-- end list -->
|
|
|
|
|
|
- Selecting layers when importing DXF files
|
|
|
Right now KiCad imports all DXF layers, which is not always
|
|
|
convenient. Adding a listbox to select layers would significantly
|
|
|
improve the importer functionality.
|
|
|
- Layer mapping when importing DXF files
|
|
|
Right now KiCad imports all DXF layers and places them on a selected
|
|
|
layer, which is not always convenient. A dialog to select and map
|
|
|
imported DXF layers to pcbnew layers would solve the problem.
|
|
|
|
|
|
<!-- end list -->
|
|
|
|
... | ... | @@ -189,7 +151,8 @@ now we can go with GenCAD exporter, in the future we may |
|
|
|
|
|
<!-- end list -->
|
|
|
|
|
|
- Reset grid & auxiliary origin
|
|
|
- Reset grid & auxiliary origin
|
|
|
It might be done via hot keys, but needs a menu entry.
|
|
|
|
|
|
<!-- end list -->
|
|
|
|
... | ... | @@ -201,10 +164,10 @@ now we can go with GenCAD exporter, in the future we may |
|
|
|
|
|
<!-- end list -->
|
|
|
|
|
|
- Enable plotting a selected layer to all output files
|
|
|
- Enable plotting multiple layers to a single file
|
|
|
PCB designs often contain a small frame with additional informations
|
|
|
about the board (e.g. layers) that could be included in all output
|
|
|
files, if it is drawn on a dedicated layer.
|
|
|
about the board (e.g. layers or drill table) that could be included
|
|
|
in all output files, if it is drawn on a dedicated layer.
|
|
|
|
|
|
<!-- end list -->
|
|
|
|
... | ... | @@ -217,12 +180,6 @@ now we can go with GenCAD exporter, in the future we may |
|
|
Could be easily done with a Python script, but the board stack-up
|
|
|
information requires adding such feature to KiCad first (model, UI).
|
|
|
|
|
|
<!-- end list -->
|
|
|
|
|
|
- Free rotation of the module texts
|
|
|
Designators (references) and values are restricted to -90**..90**
|
|
|
rotation angles.
|
|
|
|
|
|
<!-- end list -->
|
|
|
|
|
|
- Improved footprint courtyard recognition
|
... | ... | @@ -231,6 +188,16 @@ now we can go with GenCAD exporter, in the future we may |
|
|
footprint libraries contain crosses that render the courtyard
|
|
|
invalid during DRC.
|
|
|
|
|
|
<!-- end list -->
|
|
|
|
|
|
- Push and Shover router
|
|
|
Add autofinish option.
|
|
|
|
|
|
<!-- end list -->
|
|
|
|
|
|
- Flex PCB support
|
|
|
Different DRC rules for a selected region?
|
|
|
|
|
|
# Bugs (to be confirmed and posted on the bug tracker)
|
|
|
|
|
|
- Create array does not work correctly when lowercase letters are used
|
... | ... | |