VeroRoute Activity
Qt based Veroboard, Perfboard, and PCB layout and routing application
Brought to you by:
dralx
Activity for VeroRoute
-
Joe posted a comment on discussion General Discussion
Thank you Alex, I try it and I can import the net file.
-
Alex Lawrow modified a comment on discussion General Discussion
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...
-
Hello Alex, I post the schematic and net files. I don't know what I do wrong. Thank you
-
You need to export the netlist in OrcadPCB2 format. If you can do that and post the file here i can take a look.
-
Hello, how can I import the netlist to Veroroute from Kicad? I have tried to change the footprint of the symbols in Kicad but I have not succeeded. How can I do it? How should the footprint be changed? Thanks
-
Thanks for sharing this Tanveer.
-
Tee Zee posted a comment on discussion General Discussion
VeroRoute for macOS VeroRoute 2.39 is now available for macOS (tested only on Apple Silicon) Problem it solves: Mac users were locked out - VeroRoute was Windows/Linux only Complex routing by hand - Auto-routing saves hours of manual work Pre-built Binary (Recommended): No compilation needed - Just download and run Native .app bundle - Drag to Applications folder like any Mac app Universal binary - Optimized for both M1/M2 and Intel Macs All resources included - Tutorials and examples bundled inside...
-
T James posted a comment on discussion General Discussion
Okay, thanks.
-
No
-
No
-
Sorry if this has been covered somewhere, but i couldn't find it. Is there a way to create or edit parts and have them resizable in the same way that some of the inbuilt parts are? I.e. the length adjustable for number of pins, or length of a resistor etc.
-
Sorry if this has been covered somewhere, but i couldn't find it. Is there a way to create or edit parts and have them resizable in the same way that some of the inbuilt parts are? I.e. the lenth adjustable for number of pins, or length of a resistor etc.
-
Oh no, that's exactly what I did! Oops! Thanks so much for clearing that up for me.
-
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
-
The app looks very promising, however the UI is quite small on my Android tablet making it not very legible and difficult to use (i.e. hitting up/down arrows to change values etc.) Any chance of an updated version some time? Thanks for providing the software anyway!!
-
Chris Wood posted a comment on discussion General Discussion
Thanks. I had realised that changing the footprint would reset the component, I'd just not considered doing it deliberately!
-
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...
-
The component editor seems unable to "forget" the last component. Even if nothing is selected in the circuit layout, the editor still remembers the last component it was editing. In order to create a new component from scratch, I have to save the circuit, exit the program and start again. Is this correct? Can you give some guidance about specifying Type and Value? I want to create components for SD and RTC modules. These are physically similar in footprint (size and pin layout) but clearly logically...
-
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.
-
Michael Postmann modified a comment on discussion General Discussion
I want to add a fuse-holder to my board. It consists of two identical parts, but as they always need to be at the same distance, I think it's best to design the holder as one part with the length of the fuse. What I can't figure out though, is how to design the pins. As you can see on the picture I've attached, there are two pins on each side, which are electrically connected with 100 mil gap in between. Intuitively I would design it like this: ------------ |1 1 2 2| ------------ But duplicating...
-
I want to add a fuse-holder to my board. It consists of two identical parts, but as they always need to be at the same distance, I think it's best to design the holder as one part with the length of the fuse. What I can't figure out though, is how to design the pins. As you can see on the picture I've attached, there are two pins on each side, which are electrically connected. Intuitively I would design it like this: ------------- | 1 1 2 2| ------------- But duplicating pins is not allowed. Of course...
-
VeroRoute released /veroroute-2.39-phone.apk
-
-
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).
-
boardmaker posted a comment on discussion General Discussion
Pending track cuts are highlighted by changes in color of track with a white space between the colors. Fair enough. Now I looking for a way to mark the cut as being done ... and a dead end to the autorouter. DIPs always need track cuts which I do with a 5/32 drill bit. I don't cut between the holes. BTW, there is much to like in VeroRouter. Two thumbs up!
-
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...
-
Harshana Ranmuthu modified a comment on discussion Reporting Bugs/Crashes
Attaching a test file.
-
Attaching a test file. Here the problem is not so prominent. But it is there.
-
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.
-
What we see on Mono mode is different from the PDF export. Using version v2.36. Please see the comparison on the attached jpg. Text alignment and text size is different.
-
Jon McLin modified a comment on discussion General Discussion
Somehow I missed that tutorial. Thanks. And look at the bright side: I learned to do it by discovery! :)
-
Somehow I missed that tutorial. Thanks. And look at the bright side: I learned out to do it by discovery! :)
-
I must have scrolled right past that tutorial. Thanks.
-
Figured it out. For future reference: - netlists are created/edited solely using mouse and keyboard. There is no associated menu or dialog box. - See the "key/mouse" actions under the help menu for the specific keys/buttons combinations. - "P" will paint/unpaint a pin (on a device/wire) for the currently-selected net. If no net is selected, it will create a new one. - <space> will paint/unpaint a track (or track segment) - if a net is selected, pins and any track will be black. - non-selected nets...
-
Run through tutorial 14
-
I found an additional outside forum post (from 2018) describing entering the netlist with slightly more detail. And I've actually been able to start a (single) net. However, every additional pin or trace I paint attaches to that first net, so I've not been able to create additional nets. I did go through the tutorial again. The ability to edit nets is described in Tutorials 9 and 10, but only in the context of changing existing nets, not creating them. I don't see any reference to nets prior to tutorial...
-
I came across VeroRoute on another forum, and it looks to be extremely useful for prototyping. The posts in the other forum stated that in addition to importing netlists, they could be created within VeroRoute graphically. I created small multivibrator layout to test it, but I have not been able to figure out how to tie the components together. I've not found mention of this feature anywhere other than that forum. Does such a capability actually exist?
1 >
