Searching \ for '[EE]: Eagle vs. AutoTRAX (derailing to editing par' in subject line. ()
Make payments with PayPal - it's fast, free and secure! Help us get a faster server
FAQ page: techref.massmind.org/techref/pcbs.htm?key=eagle
Search entire site for: 'Eagle vs. AutoTRAX (derailing to editing par'.

Exact match. Not showing close matches.
PICList Thread
'[EE]: Eagle vs. AutoTRAX (derailing to editing par'
2003\03\05@010054 by Nick Veys

flavicon
face
Hmm, granted the editor is somewhat un-user-friendly, but a simple
copy-paste gets parts duplicated and stuff, maybe I dunno what a "tweak"
exactly consists of.

Does anyone have any experience editing parts in AutoTRAX?  Is it
easier, harder, just plain different?

spam_OUTnickTakeThisOuTspamveys.com / http://www.veys.com

{Quote hidden}

--
http://www.piclist.com hint: The PICList is archived three different
ways.  See http://www.piclist.com/#archives for details.

2003\03\05@035542 by erholm (QAC)

flavicon
face
I did a 12F629 in AutoTRAX yesterday (after beeing a "user" of
AutoTRAX for aprox 20 min.) I have done 12F629 in Eagle before
after beeing a user of Eagle for a couple of month.

I don't think I'd been able to make the part in Eagle at all, if not
having a guide I found on the web.

AutpTRAX was, in this respect, much easier to grasp as-is.

*BUT*, right now, I can start AutoTRAX, but when loading my simple
example schematic, I get a memory access error "The memory could
not be "read"" on address 0x0000011c... P-III, 800Mhz, 128Mb, W2K.

Jan-Erik.

{Original Message removed}

2003\03\05@040208 by Paul Kennedy

flavicon
face
----- Original Message -----
From: "Jan-erik Soderholm (QAC)" <.....Jan-erik.SoderholmKILLspamspam@spam@PAC.ERICSSON.SE>
To: <PICLISTspamKILLspamMITVMA.MIT.EDU>
Sent: Wednesday, March 05, 2003 9:55 PM
Subject: Re: [EE]: Eagle vs. AutoTRAX (derailing to editing parts w/each)


{Quote hidden}

If you don't mind me asking Jan, what sort of programmer and software are
you using to program the 12f629?

--
http://www.piclist.com hint: The PICList is archived three different
ways.  See http://www.piclist.com/#archives for details.

2003\03\05@041926 by erholm (QAC)

flavicon
face
Well,  I'm in the middle of the design right now, but I
plan to use my Wisp628 programmer. According to Wouter's
site (http://www.voti.nl/wisp628/index_1.html) it should
support the 12F629/675 chips.

Jan-Erik.

B.t.w, found the problem with the crashing AutoTRAX.
I had saved my schematic as a .PCB file, and when
selecting that file from the "reasent" file list, it
crasched. I could open it by selecting "File->Open->Schematic"
and then changing the file extension from SCH to PCB. After
renamning the file, all is well. Seems as there are some file
format checking lacking from the "open file" code...


Paul Kennedy wrote:
>If you don't mind me asking Jan, what sort of programmer and software are
>you using to program the 12f629?

--
http://www.piclist.com hint: The PICList is archived three different
ways.  See http://www.piclist.com/#archives for details.

2003\03\05@043414 by Wouter van Ooijen

face picon face
> Well,  I'm in the middle of the design right now, but I
> plan to use my Wisp628 programmer. According to Wouter's
> site (http://www.voti.nl/wisp628/index_1.html) it should
> support the 12F629/675 chips.

It does, but two notes:

1. When you want to use the /MCLR as input pin you will need to add some
external components (roughly 1k + TIP120) and use an 7805-based power
for the target, and a separate power for the programmer.

2. The current xwisp PC software does not preserve the osc calibration
and the bandgap bits. (BTW: I know what a bandgap reference *is* but I
still don't know what it is *used for* in a 12F).

Wouter van Ooijen

-- -------------------------------------------
Van Ooijen Technische Informatica: http://www.voti.nl
consultancy, development, PICmicro products

--
http://www.piclist.com hint: The PICList is archived three different
ways.  See http://www.piclist.com/#archives for details.

2003\03\05@121511 by William Chops Westfield

face picon face
   Hmm, granted the editor is somewhat un-user-friendly, but a simple
   copy-paste gets parts duplicated and stuff, maybe I dunno what a "tweak"
   exactly consists of.

Let's say I want to "copy" some existing PIC so as to create the "new"
version that has comparitor capability.  I SHOULD be able to say something
like "copy (from) pic16F84@piclib (to) pic16F628@mylib", rename the pins I
want, and be done.  Instead, the procedure goes something like:

1) in the symbol editor for piclib, copy the symbol.
1.5) switch to mylib.
2) create a new symbol in mylib, and paste the old symbol definition.
3) rename the pins.
3.5) switch files
4) In the package editor for piclib, copy the package
4.5) switch files
5) create new package in mylib.
6) create new "device" in mylib
7) connect pins of device from symbol to package.

Yuk.

BillW

--
http://www.piclist.com hint: The PICList is archived three different
ways.  See http://www.piclist.com/#archives for details.

More... (looser matching)
- Last day of these posts
- In 2003 , 2004 only
- Today
- New search...