Logo Search packages:      
Sourcecode: pcb2gcode version File versions  Download package

Public Member Functions | Private Member Functions | Private Attributes

ExcellonProcessor Class Reference

Reads Excellon drill files and directly creates RS274-NGC gcode output. More...

#include <drill.hpp>

Collaboration diagram for ExcellonProcessor:
Collaboration graph

List of all members.

Public Member Functions

void add_header (string)
 ExcellonProcessor (const string drillfile, const ivalue_t board_width)
void export_ngc (const string of_name, shared_ptr< Driller > target, bool mirrored, bool mirror_absolute)
void export_ngc (const string of_name, shared_ptr< Cutter > target, bool mirrored, bool mirror_absolute)
shared_ptr< const map< int,
drillbit > > 
get_bits ()
shared_ptr< const map< int,
icoords > > 
get_holes ()
void set_postamble (string)
void set_preamble (string)

Private Member Functions

void millhole (std::ofstream &of, float x, float y, shared_ptr< Cutter > cutter, float holediameter)
void parse_bits ()
void parse_holes ()

Private Attributes

shared_ptr< map< int, drillbit > > bits
const ivalue_t board_width
vector< string > header
shared_ptr< map< int, icoords > > holes
string postamble
string preamble
gerbv_project_t * project

Detailed Description

Reads Excellon drill files and directly creates RS274-NGC gcode output.

While we could easily add different input and output formats for the layerfiles to pcb2gcode, i've decided to ditch the importer/exporter scheme here. We'll very likely not encounter any drill files that gerbv can't read, and still rather likely never export to anything other than a ngc g-code file. Also, i'm lazy, and if I turn out to be wrong splitting the code won't be much effort anyway.

Definition at line 66 of file drill.hpp.

The documentation for this class was generated from the following files:

Generated by  Doxygen 1.6.0   Back to index