Activity for Alex Lawrow
-
Alex Lawrow committed [r661] on Code
Differentiate between placed and floating SOIC
-
The top part of the aliases dialog in the "Valid Import Strings" lists the valid import strings. It is up to you to choose an appropriate import string for each part. You have to type them in. Then hit Re-Import button on the dialog. See screenshot
-
See section 17.2 of the Tutorials. All that matters is the .net file. The other files s are not read or used. The problem is that you have not set up part aliases for mapping the footprint names in KiCAD to valid footprint names in VeroRoute. When you do File->Import Netlist->OrcadPCB2 and select the Prova_1.net file you will get a pop-up window titled "Error Importing Netlist" and it will say "Part: Name = Q1, Value = 2N3905, Type = Package_TO_SOT_THT:T0-92_Inline Error: Unknown part type". In other...
-
A few comments. For diodes, use the type "DIODE_IPC" rather than "DIODE" or it will end up with the wrong polarity for the diode (KiCAD and VeroRoute have different pin numbering conventions for diodes). For the 2 pin connector,s I entered PADS2. Note that for a component with "n" pins, if you enter the type PADSn then it will simply provide you with "n" different pads for the component that you can place anywhere on the board.
-
The top part of the parts dialog in the "Valid Import Strings" lists the valid import strings. It is up to you to choose an appropriate import string for each part. You have to type them in. Then hit Re-Import button on the dialog. See screenshot
-
The top part of the parts dialog in the "Valid Import Strings" lists the valid import strings. It is up to you to choose an appropriate import string for each part. Then hit Re-Import button on the dialog. See screenshot
-
See section 17.2 of the4 Tutorials. All that matters is the .net file. The other files s are not read or used. The problem is that you have not set up part aliases for mapping the footprint names in KiCAD to valid footprint names in VeroRoute. When you do File->Import Netlist->OrcadPCB2 and select the Prova_1.net file you will get a pop-up window titled "Error Importing Netlist" and it will say "Part: Name = Q1, Value = 2N3905, Type = Package_TO_SOT_THT:T0-92_Inline Error: Unknown part type". In...
-
See section 17.2 of the4 Tutorials. All that matters is the .net file. The other files s are not read or used. The problem is that you have not set up part aliases for mapping the footprint names in KiCAD to valid footprint names in VeroRoute. When you do File->Import Netlist->OrcadPCB2 and select the Prova_1.net file you will get a pop-up window titled "Error Importing Netlist" and it will say "Part: Name = Q1, Value = 2N3905, Type = Package_TO_SOT_THT:T0-92_Inline Error: Unknown part type". In...
-
You need to export the netlist in OrcadPCB2 format. If you can do that and post the file here i can take a look.
-
Thanks for sharing this Tanveer.
-
No
-
No
-
There are 2 Android builds (apk files) on the page . . . https://sourceforge.net/projects/veroroute/files/ Maybe you used the one with "phone" in the name, as that version has smaller text and icons. If so, try install the other apk without "phone" in the name instead . . . https://sourceforge.net/projects/veroroute/files/veroroute-2.39.apk/download
-
If you want to make a new component in the component editor then just change the footprint width or height while in the component editor. It should wipe everything that is currently "remembered" in the component editor and just give you a blank rectangular footprint with no pins. Setting the footprint height/width should be the first step in defining a component anyway (since it wipes everything). Remember if you accidentally change the footprint height or width, you can still use the Undo button...
-
I take it the two number "1" pins in your diagram would end up on adjacent holes in the board. I would number the pins for your two holders "1 2 3 4". Then when you come to use the part, you would "paint" pins 1 and 2 with the same netlist value, and pins 3 and 4 with the same netlist value. This is no different to having a DIP package where some adjacent pins end having the same netlist value.
-
Mainly a bunch of minor bug fixes with this release, Bug fix: Mono mode with colored tracks showed grey track colors when Fill level was not zero. Fill level should have been ignored in Mono mode. Bug fix: Shapes of zero size should never be rendered (so their PDF export works like Gerber export). Previously PDF export would render a dot for a zero size shape. Bug fix: Component Name/Value text size was wrong when doing PDF export in Mono mode. Bug fix: Vero labels should use same font as components...
-
V2.39 Mark up
-
Ibanez Tube Screamer TS808 This is suitable for a true bypass build (i.e. none of the JFET switching circuitry is included). Just export to Gerber files. Then zip them and mail to your PCB maker. I use JLCPCB. The board mounted pots will have their bodies under the board. Note that although net 1 is listed as "broken" it is not broken in practice, since all points for that net are connected through the ground pours on both layers.
-
ZVEX Woolly Mammoth Fuzz Just export to Gerber files. Then zip them and mail to your PCB maker. I use JLCPCB. The board mounted pots will have their bodies under the board.
-
Ibanez Tube Screamer TS808 This is suitable for a true bypass build (i.e. none of the JFET switching circuitry is included). Just export to Gerber files. Then zip them and mail to your PCB maker. I use JLCPCB. The board mounted pots will have their bodies under the board. Note that although net 1 is listed as "broken" it is not broken in practice, since all points for that net are connected through the ground pours on both layers.
-
Ibanez Tubescreamer TS808 This is suitable for a true bypass build (i.e. none of the JFET switching circuitry is included). Just export to Gerber files. Then zip them and mail to your PCB maker. I use JLCPCB. The board mounted pots will have their bodies under the board. Note that although net 1 is listed as "broken" it is not broken in practice, since all points for that net are connected through the ground pours on both layers.
-
Ibanez Tubescreamer TS808 This is suitable for a true bypass build (i.e. none of the JFET switching circuitry is included). Just export to Gerber files. Then zip them and mail to your PCB maker. I use JLCPCB. The board mounted pots will have their bodies under the board. Note that although net 1 is listed as "broken" it is not broken in practice, since all points for that net are connected through the ground pours on both layers.
-
The circuit above has three 500pF capacitors that may be hard to source. So here is an alternative PCB layout that constructs these 500pF values using a pair of 1nF capacitors in series.
-
The circuit above has three 500pF capacitors that may be hard to source. So here is an alternative PCB layout that constructs these 500pF values using a pair of 1nF capacitors in series.
-
EHX Big Muff Pi (Civil War / Tall Font Green Russian) Just export to Gerber files. Then zip them and mail to your PCB maker. I use JLCPCB. The board mounted pots will have their bodies under the board. Link to circuit information: http://www.bigmuffpage.com/Big_Muff_Pi_versions_schematics_part3.html
-
EHX Big Muff Pi (Civil War / Tall Font Green Russian) Just export to Gerber files. Then zip them and mail to your PCB maker. I use JLCPCB. The board mounted pots will have their bodies under the board. Link to circuit information: http://www.bigmuffpage.com/Big_Muff_Pi_versions_schematics_part3.html
-
This is an excellent compressor designed by ValveWizard (aka Merlin). Just export to Gerber files. Then zip them and mail to your PCB maker. I use JLCPCB. The board mounted pots will have their bodies under the board. After loading the VRT file, see circuit notes in the Info window (Windows->Info).
-
This is an excellent compressor designed by ValveWizard (aka Merlin). Just export to Gerber files. Then zip them and mail to your PCB maker. I use JLCPCB. The board mounted pots will have their bodies under the board. After loading the VRT file, see circuit notes in the Info window (Windows->Info).
-
This is an excellent compressor designed by ValveWizard (aka Merlin). Just export to Gerber files. Then zip them and mail to your PCB maker. I use JLCPCB. The board mounted pots will have their bodies under the board. After loading the VRT file, see circuit notes in the Info window (Windows->Info).
-
This is an excellent compressor designed by ValveWizard (aka Merlin). Just export to Gerber files. Then zip them and mail to your PCB maker. I use JLCPCB. The board mounted pots will have their bodies under the board. After loading the VRT file, see circuit notes in the Info window (Windows->Info).
-
Just export to Gerber files. Then zip them and mail to your PCB maker. I use JLCPCB. The board mounted pots will have their bodies under the board.
-
Just export to Gerber files. Then zip them and mail to your PCB maker. I use JLCPCB. The board mounted pots will have their bodies under the board.
-
Just export to Gerber files. Then zip them and mail to your PCB maker. I use JLCPCB. The board mounted pots will have their bodies under the board.
-
Just export to Gerber files. Then zip them and mail to your PCB maker. I use JLCPCB. The board mounted pots will have their bodies under the board. After loading the VRT file, see circuit notes in the Info window (Windows->Info).
-
This is an excellent compressor designed by ValveWizard (aka Merlin). Just export to Gerber files. Then zip them and mail to your PCB maker. I use JLCPCB. The board mounted pots will have their bodies under the board. After loading the VRT file, see circuit notes in the Info window (Windows->Info).
-
Just export to Gerber files. Then zip them and mail to your PCB maker. I use JLCPCB. The board mounted pots will have their bodies under the board. After loading the VRT file, see circuit notes in the Info window (Windows->Info).
-
This is an excellent compressor designed by ValveWizard (aka Merlin). Just export to Gerber files. Then zip them and mail to your PCB maker. I use JLCPCB. The board mounted pots will have their bodies under the board. After loading the VRT file, see circuit notes in the Info window (Windows->Info).
-
Just export to Gerber files. Then zip them and mail to your PCB maker. I use JLCPCB. The board mounted pots will have their bodies under the board. After loading the VRT file, see circuit notes in the Info window (Windows->Info).
-
Just export to Gerber files. Then zip them and mail to your PCB maker. I use JLCPCB. The board mounted pots will have their bodies under the board.
-
New feature: Allow tracks to be displayed in color when in Mono mode. There is a new menu "View->Enable Track Colors in Mono mode". It works with both normal/inverse Mono mode. I added this option because the existing Color mode for displaying tracks does not handle the display of ground-fills (unlike the Mono and PCB modes). This new option bridges that gap. The ground fill is still shown in black or white (depending on whether you have Inverse Mono mode disabled/enabled) but the tracks can now...
-
V2.38 Mark up
-
Allow colored tracks in Mono mode
-
Cosmetic change: Draw components using PCB style when in Mono mode. Bug fix: In PCB mode, the GUI could select and move text boxes, even though they are not displayed in that mode. Improvement: No longer double-click to modify pin layer preference for 2-layer PCBs. Double-clicking was a tedious way of handling that functionality and was especially messy on an Android tablet. Instead, there is a new toolbar button that can be selected in PCB mode, that allows pin layer preferences to be changed using...
-
V2.37 Mark up
-
Make order of toggling pin layer preferences depend on displayed layer. Added algorithm to auto-set pin layer preferences. Updated Tutorial 21
-
Fixes to previous check-ins. Move/resize of text boxes must be disabled while in PCB mode.
-
Draw components using PCB style when in Mono mode
-
No longer double click to change pin layer preference. Instead have a toolbar button that allows pin layer preference to toggle with a single click. Updated Tutorial 21.
-
The routing algorithm will not overwrite any thing that you manually paint. So if you want to stop any sort of routing to those drilled out squares, just manually paint them with an unused netlist value. i.e. First double-click on blank area so that no tracks are highlighted in grey. Then hold down SPACE bar and paint those drilled out squares. They will be given a unique netlist ID (different to all the pins).
-
Moved painter.save() location to earlier point when drawing text boxes
-
I don't have a problem with that VRT on my Linux build of VeroRoute. See the attached image, showing that I have the PDF and the application showing same text with same relative size to the track. However, if I load that VRT on an Android version of VeroRoute the application draws the text smaller size than the PDF. In other words, the PDFs produced by Linux version of VeroRoute and Android version of VeroRoute both agree with each other, and they both agree with the screen image on the Linux VeroRoute...
-
Actually I cannot reproduce the problem. Can you send me a VRT file that demonstrates the problem ?
-
Looks like a bug in the Qt library that produces PDF.
-
Run through tutorial 14
-
The coding is not at all straightforward as there's custom to code for routing, hole sharing, track rendering, and outline rendering. You can search the whole code base for "SOIC" and you'll see it scattered all over the place. Basically this is something I would have to code. It's not just the footprint pattern that matters. It's all the details needed to make sure routing and interaction with other parts works properly. What footprint do you think would be of most use. 0805 ?
-
Could look into it but I dont have time for VeroRoute development at the moment. Problem is that each part needs be hard-coded. So i would prioritise parts that are going to be useful. 7805 resistors would end up taking the same amount of space as a regular resistor though due to the need to run tracks to virtual pins that lie on grid squares. So not sure how much use that is.
-
I'll look into it if I have time, but will probably not be changing anything soon. I always export BOM info to tab separated text file, and then import that into Excel, or OpenOffice Calc.
-
No. You dont get any choice of how flying wires are drawn (except to hide them). It simply daisy-chains all flying wire pads with the same netlist ID.
-
Regarding the example in the LargePads.vrt. Something that you might consider it so to offset the pads. You can only do this when the part is placed. If you press and hold down the left mouse button for 1 second on any grid-point that has a pad, then when you release the button it will launch a small dialog where you can apply offsets (up to 1/2 a grid square) to that pad. If you offset all pads on a component by the exact same amount, then the whole compnent (outline as well) gets offset by that...
-
Regarding the example in the LargePads.vrt. Something that you might consider it so to offset the pads. You can only do this when the part is placed. If you press and hold down the left mouse button for 1 second on any grid-point that has a pad, then it will launch a small dialog where you can apply offsets (up to 1/2 a grid square) to that pad. If you offset all pads on a component by the exact same amount, then the whole compnent (outline as well) gets offset by that amount. This is something that...
-
Regarding the example in the LargePads.vrt. Something that you might consider it so to offset the pads. You can only do this when the part is placed. If you press and hold down the left mouse button for 1 second on any grid-point that has a pad, then it will launch a small dialog where you can apply offsets (up to 1/2 a grid square) to that pad. If you offset all pads on a component by the exact same amount, then the whole compnent (outline as well) gets offset by that amount.
-
Regarding the example in the LargePads.vrt. Something that you might consider it so to offset the pads. You can only do this when the part is placed. If you press and hold down the left mouse button for 1 second on any grid-point that has a pad, then it will launch a small dialog where you can apply offsets (up to 1/2 a grid square) to that pad. If you offset all pads on a component by the exact same amount, then the whole compnent (outline as well) gets offset by that amount.
-
All pads on a component have to be the same size. To set a custom pad size for the component in the component editor, tick the Custom box and it will show controls for the pad and hole size.
-
Not possible I'm afraid. The routing algorithm is a simple grid router and cannot account for track or pad sizes. It relies on having a 0.1 inch grid with all pads/tracks restricted to lie within a grid square. (i.e maximum pad size of 100mil diameter). If you are going to use pads that are larger than a grid square (100mil diameter) them you need to manually route things in the area near those pads.
-
Improvement: Automatically force text-box text to black (or white) when in Mono mode, with consideration to how ground-fill/inverse-mono is being used
-
Removed bad 'bug fix'. Original behavior was correct. Text boxes in Mono mode should be mirrored only on the bottom layer.
-
V2.36 Mark up
-
Bug fix: Text-box text should be mirrored in Mono mode on all layers (not bottom-layer only)
-
Improvement: Automatically force text box text to black (or white) when in Mono mode, with consideration to how ground-fill/inverse-mono is being used
-
Actually it is not a bug, though existing functionality could be improved or documented better. When you edit the text, you get to choose its color (there is RGB button) in the text editor dialog. The chosen colour is not turned into black or white in Mono in mode. For example, see what happens when you choose to have text in red color. So if you want text to appear in mono mode when you are using ground fill, choose white text colour if you are using normal mono mode, and choose black text colour...
-
Actually the text box text appears in Mono mode if you have no ground fill enabled. Conversely, it works in inverse mono mode if you have ground fill enabled. May be a bug introduced by recent changes to allow inverse mono. Note that text in Mono mode is deliberately mirrored as the assumption is you are using that mode for etching. Alex.
-
Text boxes used to work in Mono mode, so you found a bug. I'll fix it next release. For PCB mode (Gerber's) see this ... https://sourceforge.net/p/veroroute/discussion/partshares/thread/1ed3fd4967/
-
New feature: Added View menu item to toggle between Inverse/Normal Mono mode. New feature: Added Ground Fill Perimeter parameter to PCB parameters. See Tutorial 22. Made the Board Edge Margin (PCB parameter) apply to all view types, and account for it when drawing to screen. Bug fix: Writing to PDF was not centering the page correctly. Bug fix: Metric Gerber files were not as compressed as they could be. Improvement: If closing via X-button or windows toolbar, ask for confirmation if layout has been...
-
V2.35 Mark up (again). Added ground fill perimeter. Fixed metric Gerber file compression bug.
-
Change default board edge margin from 20 mil to 0 mil
-
Bug fix: Brightness level was not working in Inverse Mono mode. Updated most tutorials to have 0 board edge margin.
-
If closing via X-button or windows toolbar, ask for confirmation if the layout has been modified.
-
Will be fixed in next release.
-
I'll have to see how Qt handles that. The X button gets handled in different ways depending on the OS. Sometimes there is no X button (i.e. in Android).
-
Typo in comment
-
Use board edge margin when rendering to screen
-
OK. I will put option to toggle between Normal Mono and Inverse Mono under the View menu, with that menu item only changeable in Mono mode. I have managed to fix a small error in how things were centered on the page when writing to PDF. I also spotted another bug (or rather code that I wrote but never quite finished). There is currently no way to clearly see the Board Edge Margin on the screen (the PCB parameter that determines the bounding rectangle in the Gerber GKO file). So what I am going to...
-
Bug fix: Correction to centering when writing to PDF
-
If I hack the code so things are centered better I get the following. Two test connectors with 83 pins and 117 pins correspond well to A4 page size.
-
Hi Max, I don't have a printer to test with at the moment, but when I last did a test it was OK. The PDF writer code in VeroRoute sets paper size to A4 and resolution to 1200 dpi. If I look at the resulting PDF on screen the scale looks correct. For example, A4 is 210mm x 297mm (8.3 inches x 11.7 inches). If I make a test file containing a single connector that is 117 pins long (i.e. 11.7 inches) it should fit the page. When I look at the resulting PDF on screen, I see that the scale looks correct....
-
Version 2.35 Mark up. Added option to View menu to choose Inverse Mono/Normal Mono.
-
Hi Max, I have uploaded the file V234_InvertedMono_beta.zip here... https://sourceforge.net/projects/veroroute/files/ Unzip it and replace your existing V2.34 executable. I just made a few changes made to the drawing code. Mono mode has black/white swapped compared to what your had before. Let me know if it works OK. Alex
-
Hi Max, What platform are you running on (Windows/Linux) ? If you don't mind beta testing, I can upload a custom build of V2.34 for you with the Mono mode inverted. If it all looks OK I'll then provide it as a configurable option in the next release. Alex
-
Major bug fix: Component editor was not storing pin info correctly., so pins of placed part were not protected by regular track painting. Improvement: Added "Yes To All" option for overwriting library parts when adding to library from VRT/layout.
-
I'll fix this in V2.34 which I aim to release in an hour so. The invert PDF feature will take longer. I will see if I can get you a prototype build to test for that feature before I add it properly.
-
V2.34 Mark up
-
Bug fix: Component definer not calling SetupOccupanciesTH() when building part for library
-
Thanks. I'll look into it.
-
Ok, understood. It shouldn't be too hard to do. Will get it into next release.
-
Add "Yes To All" option for overwrite when adding library parts.
-
"Yes to All" option on import is a good idea. I'll add it next release. Just to be clear about the inversion, do you mean the whole page should be inverted, (i.e. whole page has black background, all tracks are drawn in white, all drill holes and gaps between tracks are drawn in black)? See attachment (which I did by inverting colors in a pdf viewer) Or do you mean the whole page should have a white background as it does at the moment, but you want tracks drawn in white, and drill holes and gaps...
-
New feature: Added support for some SOICs (8,14,16,20,24,28 pin). See Tutorial 26. Improvement: Allow non-custom library parts (e.g. T092) to be overwritten if the Import string has not changed but the Prefix string has. Improvement: Allow editing of a library part without placing it, by selecting it in the Parts Library then switching to Component Editor mode. Bug fix: Label offsets were not persisted by the Component Editor. Bug fix: If not forcing X-thermals, the code for producing additional...
-
Fix Linux Mint 19.3 compiler warning
1 >
Gen AI apps are built with MongoDB Atlas
Atlas offers built-in vector search and global availability across 125+ regions. Start building AI apps faster, all in one place.
Try Free →