#Free viewer for cam350 database 32 bit#
#Free viewer for cam350 database software#
#Free viewer for cam350 database code#

#Free viewer for cam350 database code#

REMOVE COINCIDING POINTS Sample Code Package RECALCULATE DELTA ANGLE WHEN ARC VERTEX COUNT EXCEEDS INTERNAL LIMIT INCLUDE PRECISION OF FIRST SURFACE POINT FOR CIRCULAR DATA SEGMENTS. Output round pad with arc width if the angle between start and end is less than 0.01 degrees.Р”Р„rc with width are segmented when output as boundaries. Use extra precision when handling small arcs. The module that performs Gerber validation has been updated to the most recent version.Р”Р„dded limited support for multi stroke ODB++ fonts. The Boolean library used in odb2gbr has been updated to Artwork's most recent version.

A unit scale of inch to mm would cause data to overflow and not appear at all. Text fonts that were missing the and A characters caused text strokes to be moved to nearly MAX_INT values or not to appear at all. This applies only for the command line argument.Р”В«UG FIX: Text in Fonts Missing AND 'A' characters The optional unit specifier,, can be one of the following : Chord Error includes Unit SpecifierР”Р„dded Unit specifier for chord error: -arcsag:

They can be exported as Gerber, DXF or GDSII or as a 3D 'layer.' depending on what output the user has selected. This means that these layers now have information indicating : thickness, material, color, and electrical properties. Solder Paste Layer SupportР”Р„dded Solderpaste support for NJB output.

#Free viewer for cam350 database software#

We are no longer building or support this software with the MS VS 2008 development system. The programs, libraries and supporting modules have been recompiled using Microsoft's Visual Studio 2015.

#Free viewer for cam350 database 32 bit#

V3.18 () 32 bit Version Built Using MS VS 2015 Updated Boolean ModulesР”В«oolean library modules used by ODB2GBR have been updated to sync with the latest version of Artwork's Boolean. This was addressed by ignoring the precision coming from the Feature file and using a much higher precision. Very small arcs were being converted to a single point when the angle precision was set too low in the ODB Feature file. The problem was addressed by using a higher value of data precision when evaluating these arcs so that the arc endpoints did not co-incide. This resulted in Gerber output that was difficult to correctly interpret. When processing very small arcs where the precision of the coordinates in the ODB Feature file was set too low, the arc's start and end point would snap to the same coordinate. In all cases, use of this class of text strings will generate warnings in the log file. In the case of pre v3.17 these output will also be non-conforming and the strokes in question will be the wrong size, but not stretched. The v3.17 behavior can be turned on with -multiweight command line option. With this version, the support for ODB font files with multi-weight text strokes as described above is disabled by default and the output will revert to pre v3.17 output. the parts of text that contain non-nominal weights will appear stretched.Р”Р‡or example, if a stroke has a weight of twice the nominal, the stroke is realized by two shortened parallel strokes of the nominal dcode offset by the dcode diameter. This was done by making use of multiple strokes of the nominal dcode to realize thicker text strokes when the weight of a line in the ODB font file definition is 'heavier' than the nominal.Р”В«ecause text is handled by first compiling the ODB font file before any translations begins, text strings that more often than not are inserted with different X and Y scaling will not appear as they are rendered in a true ODB++ viewer, i.e. Limited support for ODB font files that contain multi-weight strokes was introduced in v3.17. Odb2gbr is limited to making use of a single dcode when stroking out ODB text in Gerber format.

The underlying Boolean library used by this program has been updated to use the most recent version. This version: if the attribute value is blank, the dynamic text resolves to the next available attribute value pair using the following order: layer step miscellaneous job scope. This has now been fixed with memory being assigned dynamically.Р”В®arlier versions: A text feature with dynamic text of an attribute that is referenced by its feature attribute value pair for which the value is blank would not convert/render this dynamic text. Attribute names or attribute text strings exceeding that limit caused a memory crash. The size for each of these two lists was statically set to 16384. V3.18c () Fixed Feature attribute text string and name issue See -odbtree argument in odb_scan.bat file contained in EXAMPLES folder for more information. ODBSCAN library job tree display has been enhanced in this release. This was due to data precision limitation. This has now been fixed.Р”Р„ bad shape was created during ODB surface feature unionization. This page contains the summary of odb2gbr release dates, versions and changes/fixes made for that release.Р”Р„ memory crash in boolean component caused the program to stop during the conversion.