If you encounter a bug in the program, please send details of the problem along with the Crash Report to
Set of gerber files (a subset even better) allowing me to repeat the problem is substantially helpful. The files will be kept secret.
Bug List / To Do / deferred:
Space Navigator revision - features update.
GerberX2 "%TF.FileFunction" for autoload.
There is unnatural transparency gradient, close to the board edges, when observed from some angles. Best fix would be "per pixel fog". I am slowly allowing myself to think about this more GPU power demanding method.
Sometimes board outline is routed via the drill file. This could be detected and possibly used instead of the board outline drawing Gerber file.
Single layer board auto file to stackup assignment have top/bottom problems.
Peel layers mode really hides the peeled off layers.
Spaces in STEP export filename are not handled properly.
Slight numerical inaccuracy in a big arc shape was not accepted, causing the STEP export module crash.
Netlist browsing dialog boxes have a netlist name mask entry now.
If BOM file is processed, components not included in the BOM are initially "Hidden".
Sometimes, either by automatic modeling or by the user mistake, parameters of primitives, like the (polar)cube below, are creating "negative" surfaces.
Here, two fillets adds to have more height then the height of the complete primitive.
This is just creating a visual artifact, but it is not crashing the program. It is not that simple in the STEP export, however.
Workaround: if you see an exporter crash, check the last rendered part. Try to fix the dimensions in the Body Builder.
Faces rendered to null objects, caused communication error in STEP export.
Enlarged memory access ability from 2G to 4G.
Netlist selection vertex buffer corruption, visible in big projects.
More exact hit counting on automatic assigning files to layers, to cover Protel v.s. KiCad - Protel Compatible file sets.
Test points on the same location crash - e.g. power transistor radiator pad made out of grid of small pads.
The program does not crash now, but the pads are not "rejoined" in the detection process yet.
Adding 'T','B','M' modifiers on the drill mask description, in the CAM_Load_Rules.txt file. The modifiers allows for using numbers to define internal
layers, starting with internal-1 and words for top and bottom. See CAM_Load_Rules.txt file, section KiCad.
Non-monotone triangulation glitch on the cross-cut, the J-SMD pin.
Section CIRCAD added to CAM_Load_Rules.txt file, Also, a tool to export IPC-356 out of the pcb CirCAD file, solving missing pins problem,
available on the FAQ page.
Board Outline, declared in stackup, but rendering to no "loop", i.e. no surface, can cause a crash. A simple bug fix it is not
enough, as the resulting PCB will be simply empty - that is confusing
Grouping tracks/pads/etc... into groups of overlapping objects. Creating the copper netlist and separating objects for geometry calculation.
In case of 2 outlines (polygons) touch test, one of the segments of one of the polygons was spiked, in most of the cases. It was a kind of
"how was it working at all?" error. One victim, as far as I know.
Inability to detect the footprint features will no longer result in an exception (crash), but just an undetected component type.
Crash when saving .zofzproj file containing a sparse BOM table.
Fixed problem witch the IPC-356 parser option: "Long ID/Pin name correction". The option allows to read an non compliant file,
where component id and pin name text are longer then assigned space in the IPC-356 specification. The option is enabled by default.
Lines containing a "M" marker are not read, also from the compliant files, if this option was enabled.
The shape recognition algorithm was unable to find pin "1" in case there were only non-plated holes in a component.
Such condition could be caused by above bug. Uninitialized value was used as index, causing a crash somewhere later in
the execution, because of a memory corruption.
In some rare cases, rendered PCB, saved as a ".zofzproj" file, was corrupted.
Component geometry detector crash on some complicated BGAs.
A lot of new component classes are added to the internal library.
Menu system for selecting component types and adjusting component parameters.
Mathematical operations for aperture macro definition: unary "-" and "+" and parentheses "(", ")" are added, as defined in GerberX2.
Some file names are longer then dialog box - implemented horizontal scroll bar.
Option to sort files by date/time.
Lighting - simple ambient and difuse light dialog.
CAM_Load_Rules - added sections OrCAD (Alexiej) and Cadence Allegro (Benjamin).
CAM_Load_Rules - must be more visible - added edit button in the autoload dialog.
Aperture Macro rotation center adjusted to the new clear Gerber definition.
Aperture Macro rotation for circle added as option - defined by GerberX2.
Save/Restore of the program window position and size may permanently prevent the program from starting, if minimized or otherwise inactive window position is saved. The Direct3D can initialize only in visible window - program was exiting with Direct3D device error.
There was a hot-fix for old PCAD inserting space characters in Gerber files. The hot-fix was also removing spaces in G04 (comment). That was making problems when the comment string was starting with digits. eg. G0433...)
Excellon routing offset matching to Gerber was not working. Slots could disapear or be miss-placed.
The macro definition was not flattened before it's use. Negative drawing was preserved and was destroying parts of drawing outside the macro.
Very short arcs were replaced by a full circle. This condition detection is now set to trigger on equal points only.
Irregular pinout (via IPC-356) could hang the program.
Adding step and repeat have been changing ".zofzproj" format. This should have been accompanied with the .zofzproj version being incremented.
I missed this. Unfortunately ".zofzproj" files which are saved by version 0.5.0015, are unreadable by any other version.
Reading of the BOM file. Component info is displayed on the right plane.
Tabelarized Component Library, autodetection. In case a component is not identified, the former "extruded" form is displayed. The component tables are stil under development.
Currently, implemented are: L-lead (QFP, SO, SOT, DPACK), J-lead, DIP, chip capacitors (resistors).
GUI bug - folder selection crash. I could not see it for a long time, but it seems I have fixed it with your help.
Cross-Section of the PCB and components. Use "DEL" key, also measurement maker(s).
Hole diameter display (was forgotten while in the implementation).
Wheel zoom movement time constant setting in "Navigate" menu. Plus shift-key speed modifier. Ctrl and shift works also for keyboard controlled movements.
Possibility to switch off auto-offset matching for drills and IPC-356. Priority for zero offset if matching, in this case, is detected.
PCB Outline processing, finding the correct outline, in case of multiple "T" connections, can explode in time or memory usage - possibly leading to crash. This often hapends if some tracks are misinterpreted as outline (in wrongly set meta drawing) or when mutlipe lines are not finised to exactly the same point.
IPC-356 autodetection of rotation angle units, when radians are used. Why to use radians anyway if there are only 3 digits of precision assigned for rotation?! 90deg=>157=>89.954deg
Netlist related operations could crash if there were no components on a bottom side, in some cases.
Removal of board outline of rendered board caused crasch.
But report tool can handle "portable version" stored log file.
More layer types can be used in the CAM_Load_Rules.txt - autoload script. Layers can be defined in each section.
When particular section is used as a rule for filenames, associated layers are added to the program.
Alternatively, layer types previously defined in the Stackup / More Layer Types can be used. See the description inside CAM_Load_Rules.txt
If last object in an object list flattens to nothing, some other objects may be removed.
Board outline containing sequentially equal points may cause crash.
Board outline path selection could create empty loops by going back and forth the seme lines, in some cases.
IPC-356: if the 317-Through-Hole line entry was used to describe a SMD feature, it was read incorrectly, causing the Component-Mesh-Modeler to crash.
IPC-356: unnamed nodes are assumed to be not-connected. The node name is automatically generated in form: " N/C_nnnnn". The same should be done to nodes named "N/C".
IPC-356 does not contain information about THT component placement side (top/bottom). It is now possible to swap those components to the bottom side. Use right mouse button click on selected component.
It is possible to hide unwanted components individually. Use right mouse button click on selected component.
State of component hide and swap is saved together with the PCB stackup and rendered board files.
Possibility to add more layer types. Acces via Menu: Stackup / More Layer Types.
The extra types are saved together with stackup (.camset) and with rendered project (.zofzproj).
Loading stackup file, adds to current set of layer types. Loading rendered project overwrites the types set.
Layer types alone, are saved and loaded together with the Color Presets.
All colors preset is saved and restored by stackup and rendered board files.
Beside above, rendered board save/restore contains: state of layer enable checkboxes, the Component checkbox, the Hollow checkbox and saved camera positions (0..9)
Semitransparent Solder Mask was drawn twice in the Hollow mode, possibly reducing the frame rate.
Semitransparent Solder Mask transparency (alpha) value was reversed in the Hollow mode.
Portable version cannot access its init file. Parameters are not saved for the next time the program is open. The path to the file is changed, by error, to the c:\windows directory and therefore not accessible without administrative privileges.
Sometimes, when routing and drills are on separate files, auto-fit drills to Gerbers fails. One of the drill files is shifted or not visible.
Overlapped, but not continuous routing on the drill "plate" may lose some of its components.
CPN, C, for crosscheck versus measurement selection
Ctrl */ rotate to the nearest rectangular rotation
Home rotates to the nearest rectangular position
Ctrl-Home, rotates to zero angle - as Home before
Screenshot directory and use-project-directory check box
Dialogs are not 'transparent' for the mouse click or drag
Component Display Feature.
At the moment, the only information about component is taken from IPC-356 file.
Components are represented by set of basic shapes: cube, pin/cylinder, rect-chip-filling.
The actual component shape selection is guessed, based on e.g. component designators. (see IEEE 315 or Wikipedia).
Also the THT component layer is always assumed to be TOP.
Therefore, urgently, more features must be added:
AutoLoad suggests the path and name for saving the .camset file.
Camera FOV (Field Of View) setting and orthogonal projection setting.
Objects clearly outside of the Board Outline are removed.
Introducing a new features in the netlist-browsing, I have managed to block the old one.
ESC-key is not stopping the autopilot, but it is expected to.
New version check function contact the website via wrong port (443 instead of 80). Till now that was working. Due to some kind of update, my provider has removed this redirection. I will make a notice about the new version release via the website and the social media.
Above problem also disables the bug report tool.
Auto-Load fail when simplified algorithm - could not decide gerber or excelon, after 20 first lines.
If two outlines follow directly each other in the Gerber file and first point of the second is equal to the last point of the first then those two outlines will be connected. If the outlines overlap, XOR will be then applied instead of ADD.
"Netlist/Nodes (PCB)" and "Netlist/Nodes (IPC-356)" board browsing. The difference between those two methods plays role in case of discrepancies between PCB-detected netlist and IPC-356 netlist.
Reading the board outline from copper layers in addition to former method, that is using a separate layer. Meta image is distinguished from the layer image by using "impossible" thin tracks. The "meta-way" is now officially accepted by the Gerber Specification.
Auto-Load works from a command line parameter if you specify just the folder path. If you specify a file of ".zofzproj" or ".camset" type, it is also loaded, as it was before.
Automatic adding of core/prepreg in between copper layers, when [Set Equal Spacing] in BoardOutline / Thickness is pressed.
Drill routing of more complicated shape, a multi-segment path, does not store mesh reference. Trying to highlight some nets (jump net, error, pin) can cause program crash.
Drill routing of more complicated shape, a multi-segment path likely causes false positive detection of short circuit.
False warning about unsaved work on program exit.
Aperture Macro Comment not implemented. When encountered, causes syntax error: "Macro Primitive Type ?"
Gerber Image Polarity "Force Negative" and "Force Positive" setting in addition to existing "Default Negative" and "Default Positive" settings.
Auto-file-detection checks file content to be Gerber for layers and Gerber or Exelon for drills. This modification solves ambiguous sections, e.g. Protel99se v.s. Kicad "drl" and "txt" - Protel creates "drl" files in a rare binary format,
whose could be taken as Kicad excellon drill files. This functionality is a stub for GerberX2 "%TF.FileFunction" - based autoload.
Some Gerber export modules can generate longer numbers (more digits) than format declared in the same Gerber file header. Workaround is possible in case of trailing zeros removal mode.
Beside signed installation package, there is a companion version, running directly from a folder, without installation and associated privileges. It keeps all settings and examples in the same directory, whenever you place it.
Two more color presets from Christian Weidner, including OSHPark purple.
Ultra High resolution screenshots. x1 (current resolution) to.. x10 19200x10500.
Gerber parser allows for Gerber X2 codes: %TF %TA %TD codes, but ignores its content. You can read Gerber X2, but ZofzPCB makes no use of the new additional information at the moment.
Still not correctly interpreting board outline drawing when using single line as a board cut-out. this can happen in panelisation. Example: two rectangles, one inside the other, form a frame shape. This may be not intended.
Additional syntax in CAM_Load_Rules.txt autoload script:
Plated/Non-Plated option (Drill_PTH/Drill_NPTH).
drills from-to assignment.
Added section "Mentor" and section "Proteus" to the CAM_Load_Rules.txt autoload script.
Added Mentor specific Excellon drill size definition.
ver 0.4.0000 ()
I need some pleasure too. Feature-freeze dissolves. I have decided to add correct thickness for tracks and other layers. It is possible to switch it off in the view menu. This could be required if those additional triangles overheats your GPU, causing too low frame rate.
This is now an official release.
I have arranged for code certificate. That is securing the install package transfer.
I have 3 reports about error in the triangulation, it seems to be the same bug - transparency fade-out band extraction (used for preparing the hollow effect).
It is related to creating band (or ribbon) inside big surfaces, in case of bumpy track drawing e.g. horizontal tracks only. I am still searching the solution faster then n^2.
Some old software does not generate Gerber image polarity parameter %IPPOS*% or %IPNEG*%. Therefore I have added "Def. Negative" checkbox.
The checkbox defines image polarity in case the Gerber file does not declare it (default polarity). Now I found that there are some Gerber files simply declaring wrong image polarity.
This is driving me crazy. What to do?
Extremely long "flattering" time. Detailed description:
for the "flattering" I am still using bounding rectangles to limit the edges crossing algorithm.
It works for local and short tracks. But when it is not efficiently working, I have n^2 operations, and this can grow huge.
The second stage (triangulation) I have already n*log(n) – scan line sweep algorithm successfully implemented.
And I am planning to apply this to the first phase too. (edges are circles – that is the difficult point).
So, n*log(n) is much faster then n*n, I have already seen this. (n is a big number.)
Additionally, since I am using double precision and(especially for circles) I am using 3 value logic: (yes – no – do not know), there is a possibility that I need to solve binary equation system to meaningfully decide what edges are staying and what are removed. Sometimes it takes a very big matrices to solve (n^3 for the Gaussian back-substitution algorithm)!
Solution for this is a double-double arithmetic package – a very cool approach, using pair of double numbers to have almost quadruple precision. This should minimize the ‘do-not-know’ state, as it did in triangulation.
Spaces (character 32) in the Gerber files are forbidden by format definition. But somehow, there are Gerber files containing spaces, as I have seen, in the aperture definitions.
Gerber file read, statements like: $1=$2+$3 - there is a chance of exception.
Lack of pads or IPC-356 test-points on one side and simultaneous lack of THT pads-test-poins causes auto-scale and auto-offset calculations for IPC-356 fail, placing components and test-points almost at infinity.
IPC-356 Load errors were not displayed.
Multiple IPC-356 netlist test-points definitions on a single place could cause problems by error browsing.
Only first type of IPC-356 errors were displayed correctly. Next sections listings interpretations were shifted.
PEI-Genesis is a global leader in the design and assembly of custom engineered connectors and cable solutions for harsh environments.
PEI partners with customers to design engineered solutions that meet specific application requirements and then delivers with speed,
service and consistent quality that is unmatched in the industry. PEI-Genesis