Date
1 - 3 of 3
Design Rules, track and pad sizes (Was: Trace thicknesses)
|
John Johnson <johnatl@...>
On Mon, 14 Aug 2006 23:04:10 -0400, <kbmarsha@...> wrote:
Actually, I may have it working...Glad things are doing well! I saw your note that you might have this working. I thought this further clarification might be handy to someone in the future. From the board editor, click the DRC (Design Rules Check) button. Look on the Restring tab. http://tinyurl.com/j6woz Min and max pad size can be changed there. Also look on the Shapes tab. http://tinyurl.com/jal3e The Elongation % for the two different types of pads (hole in the center, and hole at the end) can be changed there. All the settings in the DRC can be tweaked to improve board layout, trace/pad size, etc. The pcb-gcode.dru is a good starting point. This file is shipped with pcb-gcode and is also available in the Files section of the Yahoo! group. It is loaded in the DRC. From the Board Editor, either click the DRC button, or go to the Edit | Design rules... menu item. In the DRC editor, you will see the File tab. http://tinyurl.com/zef7d There are Load... and Save as... buttons there. Use these to load the pcb-gcode.dru file, or to save your own .dru file when you have customized it. The size of the traces can be controlled from the Edit | Net classes... menu item. http://tinyurl.com/fzksz Regards, JJ -- Using Opera's revolutionary e-mail client: http://www.opera.com/mail/ |
|
|
|
kbmarsha@...
JJ,
toggle quoted message
Show quoted text
When PCB Gcode runs, there's a rendering of the tools paths that is made for each machining routine. Are those saved anywhere I could see them? Kent On Mon, 14 Aug 2006 23:04:10 -0400, <kbmarsha@...> wrote:Actually, I may have it working...Glad things are doing well! |
|
|
|
John Johnson <johnatl@...>
Kent,
toggle quoted message
Show quoted text
Sorry I missed this question back in August. Substitute this code in pcb-gcode.ulp beginning about line 478. Some of the lines are the same so you can tell where it goes. The code will create files named e.g. board_bot_06_03.png (where 03 is the pass number) for each pass. Regards, JJ if (m_isolate >= ISO_MAX || task == TASK_FILL) { output_file_postamble(m_phase, which_side); printf(RAPID_MOVE_Z, TOOL_Z_UP); device_end(); } m_cmd = m_cmd + "display "; int states[]; B.layers(L) { states[L.number] = L.visible; if (L.number != g_layer) { m_cmd = m_cmd + "-" + int_to_string(L.number) + " "; } } m_cmd = m_cmd + ";\n"; sprintf(cmd_temp, "export image %s_%s_%02d_%02d.png 300;\n", g_file_name, (which_side == TOP) ? "top" : "bot", m_phase, m_pass_num); m_cmd = m_cmd + cmd_temp; m_cmd = m_cmd + "display "; B.layers(L) { if (states[L.number] == 1) { m_cmd = m_cmd + " " + int_to_string(L.number) + " "; } } m_cmd = m_cmd + ";\n"; sprintf(cmd_temp, "delete (%f %f) (%f %f);\n", units(x1), units(y1), units(x2), units(y2) ); m_cmd = m_cmd + cmd_temp; dlgMessageBox(m_cmd); //dlgMessageBox(m_cmd); } // polygons } // if(S.name == OUTLINES_SIGNAL_NAME) } // signals } // output } // board } // write_outlines On 15-Aug-2006, at 14:56, kbmarsha@... wrote:
JJ, |
|
|