Re: gEDA-user: Water proof panel connectors
Looking at connectors for this in the past has lead me to circular connectors. A search on digikey brings up a selection matrix including ingress protection. If your going to be connecting and disconnecting this alot, look into push pull circular connectors. Lemo makes really nice ones. www.lemo.com As for ratings. http://en.m.wikipedia.org/wiki/IP_Code IP65 should be enough even IP54 And you might want to take your wheelchair and make it into a scuba submersible too! Then you might wand really good underwater connectors. :-) Steve On Jun 8, 2011, at 1:58 PM, Rob Butts wrote: > I have a water proof box with two volage sources inside. I need a > power connector to be water proof that I can in the box and be water > proof. It doesn't have to be submersible because it will be on the > back of my wheelchair but the more water proof the better. > > > > Can anyone recommend one? > > > > Thanks > > > ___ > geda-user mailing list > geda-user@moria.seul.org > http://www.seul.org/cgi-bin/mailman/listinfo/geda-user ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
gEDA-user: Water proof panel connectors
I have a water proof box with two volage sources inside. I need a power connector to be water proof that I can in the box and be water proof. It doesn't have to be submersible because it will be on the back of my wheelchair but the more water proof the better. Can anyone recommend one? Thanks ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
Re: gEDA-user: PCB head fails with ***MEMORY-ERROR***
On Sat, 2011-06-04 at 10:51 -0700, Andrew Poelstra wrote: > Another leak can be seen when zooming in and out. Typing > Zz on the board takes another 12Mb. It is only a leak if repeated cycles continue to cause this extra memory to be allocated. It is quite possible that hitting different zoom levels causes the rendering code to evaluate and cache polygon geometry which wasn't displayed at the previous zoom level. PS.. Many thanks for fixing that other leak I introduced. I completely forgot the possibility of breaking out of the loops via other means. That commit was a quick (but intrusive) change required to fix drawing whilst auto-routing, and has caused a couple of teething problems so far. I still think it is the right way to go (moving other types of memory allocation over to it in the future), but we do need to be careful about iterating over lists we might modify. I think the macro loops should ideally be used for read-only access to the data-structures only. I thought I was being clever (and more robust against problems) by adding the g_list_copy (), but obviously I had not taken care of the clean-up correctly. Best wishes, -- Peter Clifton Electrical Engineering Division, Engineering Department, University of Cambridge, 9, JJ Thomson Avenue, Cambridge CB3 0FA Tel: +44 (0)7729 980173 - (No signal in the lab!) Tel: +44 (0)1223 748328 - (Shared lab phone, ask for me) signature.asc Description: This is a digitally signed message part ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
Re: gEDA-user: Blog post: Porting gEDA to Guile 2.0, and future plans
On Sun, 2011-06-05 at 21:53 -0400, Dan McMahill wrote: > has anyone tried to compile against gtk3? Yes - and the answer is we cannot ;) I can revive my attempt at some point, and propose we proceed as follows: Identify widgets / UI elements which use deprecated APIs or direct structure access forbidden in GTK 3.0. For each identified area, do a brief code and UI design review to see whether the quality of the existing code and user interface is worth spending effort on, or needs to be redesigned. If the UI and basic code is solid, fix up the GTK 2.0 / 3.0 incompatibilities as directly as possible. (No need to re-write these as fully developed widgets with data access via GObject properties and notification via signals if they aren't already so). If the UI is bad, redesign a replacement (coding in line with best practice GTK 3.0 styles), basically from scratch. If the UI is ok but depends on completely deprecated widgets or is generally hateful - write it again from scratch. The aim should not really be to hack hack hack until we "just" compile with GTK 3.0, but to do a complete UI review - focusing on the most legacy code first. -- Peter Clifton Electrical Engineering Division, Engineering Department, University of Cambridge, 9, JJ Thomson Avenue, Cambridge CB3 0FA Tel: +44 (0)7729 980173 - (No signal in the lab!) Tel: +44 (0)1223 748328 - (Shared lab phone, ask for me) signature.asc Description: This is a digitally signed message part ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
Re: gEDA-user: trcing with pcb design
On Tue, 2011-06-07 at 12:56 -0400, DJ Delorie wrote: > Yes, you need to specify a background PPM image. > http://www.delorie.com/pcb/bg-image.html It should load PNG fine as well... (certainly the GTK HID can), and probably other formats supported by gdkpixbuf, such as JPEG. -- Peter Clifton Electrical Engineering Division, Engineering Department, University of Cambridge, 9, JJ Thomson Avenue, Cambridge CB3 0FA Tel: +44 (0)7729 980173 - (No signal in the lab!) Tel: +44 (0)1223 748328 - (Shared lab phone, ask for me) signature.asc Description: This is a digitally signed message part ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
Re: gEDA-user: import schematics with local footprints
> > For gsch2cb the path to the footprint lib is set by the parameter > > --elements-dir on the command line, or in a project file. > > (Why isn't it "--footprint-dir"?) > > Because the PCB file format calls them elements? PCB calls them footprints *before* they're put on the board, and elements *after*. --footprint-dir would be more appropriate. ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
Re: gEDA-user: multiple attributes with the same value
Kai-Martin Knaak writes: > Do attributes have to be unique within a symbol? Currently, > gschem/gnetlist is a bit indifferent. This has been discussed before: http://thread.gmane.org/gmane.comp.cad.geda.user/34557/focus=34677 Upshot: current behaviour is inconsistent. They don't have to be unique (apart from where they do), but there's a strong argument that they should be. Peter -- Peter Brett Remote Sensing Research Group Surrey Space Centre pgpV9vOl3C0Tb.pgp Description: PGP signature ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
Re: gEDA-user: import schematics with local footprints
Kai-Martin Knaak writes: > Ethan Swint wrote: > >> I've got the line >> (component-library-search "/../../footprints") >> in my gafrc file. Does that set a priority? > > I just double checked. This setting does not seem to affect the > choice of footprints in any way. Correct. > The term components in the context of gafrc exclusively refers to > symbols. (Why is the parameter not called "symbol-search-path"?) I don't know the reason, but let's make one up: because the entries in the file format are called "component entries" and begin with the letter "C". It's not like it can be changed now anyway. > For gsch2cb the path to the footprint lib is set by the parameter > --elements-dir on the command line, or in a project file. > (Why isn't it "--footprint-dir"?) Because the PCB file format calls them elements? Peter -- Peter Brett Remote Sensing Research Group Surrey Space Centre pgpxpTFSnAQC5.pgp Description: PGP signature ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user