Whats happening with EagleCad & Cadsoft?

Hello everyone,

Just to add to the cross-platform-ness of Cadsoft, they originally got me onboard because they had a

version of Eagle that was built for OS/2.  Of course they discontinued that line, but given the

direction the OS/2 software market was going, they had no choice.

--

Tony

Am 28.07.2011 00:32, schrieb davem:

HI Andrew,

 

yes there are plenty of MAC users in engineering, ( most of them keep quiet

about it)  and yes Thanks to CADSOFT for having the balls for creating a

Cross platform CAD application. The fact that Eaglecad exists on the mac

help me decide to get into the electronics business, I think thats

important. I have used mac's ( and PC's) since the Apple IIe?? ( Showing my

age now!)

 

>

Thanks

Dave M

The whole discussion about the hardware is childish.

This newsgroup is about eagle. So please everyone take your stupid bla

bla about hardware elsewhere.

--

Mit freundlichen Grüßen / With best regards

Joern Paschedag

Hello everyone,

Just to add to the cross-platform-ness of Cadsoft, they originally got me onboard because they had a

version of Eagle that was built for OS/2.  Of course they discontinued that line, but given the

direction the OS/2 software market was going, they had no choice.

--

Tony

On 7/27/11 7:26 AM, Olin Lathrop wrote:

However, using a

MAC, particularly for engineering, is just silly, and I don't envision

supporting that unless there is a major shift in the market.

Welcome to the shift

After having used both Windows and Linux for several years my main

engineering development workstation is a Mac. By choice. There is BSD

under the hood which is what makes it workable.

Kudos to CadSoft for recognizing this and supporting Mac natively.

Andrew.

Olin,

I have had enough of your arrogance and rudeness, some of the things you

say are outright childish, Please DO NOT Reply to any of my posts again!

I have reported your post(s) to the moderators , enough is enough!

I don't get the same smart *** replies from other HIGHLY SKILLED Eaglecad

user here, only from you. You are not very professional in your attitude to

new users, you need people skills, not just typing skills.

Dave M

--

Web access to CadSoft support forums at www.eaglecentral.ca.  Where the CadSoft EAGLE community meets.

On 07/26/2011 08:54 AM, Olin Lathrop wrote:

davem wrote on Tue, 26 July 2011 05:57

>> So bom's generally consists of the following fields..

>>

>>

>> Line

>> Company Part Number          (optional )

>> Qty

>> Designators                  (grouped together)

>> Description                  (A full description)

>> Revision                     (Optional)

>> Manufacturer's Name          (A list of Approved manufacturers)

>> Manufactures Part Number     (A list of Approved part no's)

>> Vendor ( Supplier )          (A list of Approved vendors)

>>

>> Cost                         (Costs are needed but these are not

>> usually passed on)

I break up your description into three separate fields: general

description, value, and package.  For example, a simple resistor might be

  Description: Resistor, fixed

  Value: 5.1k

  Package: 0805

I break it down even further:

Description

Value

Tolerance

Rating

Material

Polarity

Each of these is an attribute maintained in a table separate from the

part, and linked by a part ID number.  This way, I can have different

attributes for different components.  R's have a rating measured in

watts and sometimes volts.  C's are measured in volts.  L's are measured

in amps.  BJT's are measured in watts.  Material for R's might be 'thick

film', 'thin film', 'silicone',or 'carbon comp'.  Material for C's might

be 'X7R', 'NP0', etc.  Material for L's might be 'air core', 'iron

core'.  IC's probably wouldn't have a material.  Transistors might have

their Polarity set to 'PNP', or 'N-chan'.

It essentially parallels the ATTRIBUTES feature of v 5.0, although my

external DB was established long before 5.0.

These can easily be expanded to include design specific attributes such

as minimum hFE, maximum Rdson, or gate threshold voltage allowing a BOM

program to search for approved parts with those parameters.

One additional note regarding the desire for eagle to NOT have a fixed

BOM system:  By using a BOM system external to eagle, other individuals

can access the BOM without having to install eagle.  This also is able

to integrate to an MRP (Material Resource Planning) system.

Enjoy,

    - Chuck

On 07/26/2011 05:56 PM, davem wrote:

Olin wrote on Tue, 26 July 2011 22:54

>> If you really think this is true, then why not use my BOM system?  It's

>> freely available in my Eagle Tools release at

>> http://www.embedinc.com/pic/dload.htm.

 

Hi Olin,,

 

Because its for PC Only,I use a Mac, If you just have a folder of files to

download instead of an .exe to extract the files, then I could probably

take advantage of your kind offer, I would love to have a look at what you

have done!

 

Thanks

 

Dave M

Dave,

The file install_eagle.exe on Olin's web site is a self-extracting zip

file.  You can unzip it with unzip on linux.  It unzips into the

embedinc/ directory.  It has some Winbloze executables in it along with

some batch files.  There's also a tree of eagle specific files.

If you can't unzip it, let me know and I'll convert it to a .tar.gz for

you.  I believe a Mac can be able to handle that.

Later,

    - CHuck

On 07/26/2011 05:56 PM, davem wrote:

Olin wrote on Tue, 26 July 2011 22:54

>> If you really think this is true, then why not use my BOM system?  It's

>> freely available in my Eagle Tools release at

>> http://www.embedinc.com/pic/dload.htm.

 

Hi Olin,,

 

Because its for PC Only,I use a Mac, If you just have a folder of files to

download instead of an .exe to extract the files, then I could probably

take advantage of your kind offer, I would love to have a look at what you

have done!

 

Thanks

 

Dave M

Dave,

The file install_eagle.exe on Olin's web site is a self-extracting zip

file.  You can unzip it with unzip on linux.  It unzips into the

embedinc/ directory.  It has some Winbloze executables in it along with

some batch files.  There's also a tree of eagle specific files.

If you can't unzip it, let me know and I'll convert it to a .tar.gz for

you.  I believe a Mac can be able to handle that.

Later,

    - CHuck

Olin wrote on Tue, 26 July 2011 22:54

If you really think this is true, then why not use my BOM system?  It's

freely available in my Eagle Tools release at

http://www.embedinc.com/pic/dload.htm.

Hi Olin,,

Because its for PC Only,I use a Mac, If you just have a folder of files to

download instead of an .exe to extract the files, then I could probably

take advantage of your kind offer, I would love to have a look at what you

have done!

Thanks

Dave M

--

Web access to CadSoft support forums at www.eaglecentral.ca.  Where the CadSoft EAGLE community meets.

davem wrote on Tue, 26 July 2011 05:57

So bom's generally consists of the following fields..

 

 

Line

Company Part Number          (optional )

Qty

Designators                  (grouped together)

Description                  (A full description)

Revision                     (Optional)

Manufacturer's Name          (A list of Approved manufacturers)

Manufactures Part Number     (A list of Approved part no's)

Vendor ( Supplier )          (A list of Approved vendors)

 

Cost                         (Costs are needed but these are not

usually passed on)

I break up your description into three separate fields: general

description, value, and package.  For example, a simple resistor might be

  Description: Resistor, fixed

  Value: 5.1k

  Package: 0805Quote:

What I am trying to say that CADSOFT could come up with a BOM SYSTEM

that would suit 99 percent of everyones needs.

There are way too many little wrinkles for that, especially if you already

have a system in place that anything new needs to be compatible with.

If you really think this is true, then why not use my BOM system?  It's

freely available in my Eagle Tools release at

http://www.embedinc.com/pic/dload.htm.  This is a collection of ULPs,

scripts, and external programs that take the information from a schematic

or board ready to import into a spreadsheet.  A set of Eagle attributes are

used that have special meaning to the BOM system.  Most of the parts in the

libraries that are included in the Eagle Tools release already have the

attributes set appropriately.  You can look at the header description of my

BOM.ULP and follow the documentation cookie crumbs from there to understand

the whole BOM system.  The description of the attributes is in the

EAGLE_ATTR documentation file:

This document describes the Embed Inc conventions for using optional

attributes in Eagle, which were first made available in version 5.  In

previous versions a part could only have a few fixed attributes built into

Eagle, such as VALUE and NAME.  In version 5 these fixed attributes still

exist but arbitrary additional attributes can be created by the user.

This document specifies certain attributes that are expected by parts of

the Embed Inc system, mostly to aid in automatic bill of materials (BOM)

generation.  The process of generating a BOM from a eagle board or

schematic is desribed in the CSV_BOM program documentation file.

The Eagle optional attributes that have special meaning within the Embed

Inc

system are:

MANUF

    Manufacturer:partnum; manufacturer:partnum; ...

    The PARTNUM fields and their leading colons may be omitted, but is a

    bad idea unless only a single manufacturer is listed.

PARTNUM

    Generic part number or part number within single manufacturer.

SUPPLIER

    Supplier:partnum; supplier:partnum; ...

    The PARTNUM fields and their leading colons may be omitted, but is a

    bad idea unless only a single supplier is listed.

BOM

    Whether this part should be included on the BOM.  Some "parts" are

    only features on the board, like pogo pin pads for example.  These

    should not be listed on the BOM because they do not need to be bought

    and will not be installed.  Supported values are:

      YES  -  Include this part in the BOM.

      NO  -  Do not include this part in the BOM.

    The default is YES if BOM is empty or does not exist.

VALSTAT

    Indicates how the VALUE attribute is used.  The choices are:

      VAL  -  Normal part value, like the resistance of a resistor.  The

        part value will be listed on the BOM and used to distinguish

        different parts.  For example, a 10K ohm resistor is a different

        part than a 330 ohm resistor.

      PARTNUM  -  The part number.  The value field will be shown in the

        BOM and used to distinguish different parts, like VAL.  However,

        the part number field will be set to VALUE unless the part number

        is otherwise explicitly set.  VALSTAT PARTNUM is for generic

        library devices where the value field is used to show some or all

        of the part number on the schematic.  For example, the library

        might contain a generic 14 pin opamp device, and the value set to

        LM324 to show the type of opamp on the schematic.  In this

        example, VALUE is only set to the generic part number without

        package type, temperature grade, etc.  In this case the PARTNUM

        attribute should be used to specify the exact part number, but

        VALSTAT should still be set to PARTNUM.

      LABEL  -  Label intended for the silkscreen.  The value field will

        not be transferred to the BOM and will not be used to

        differentiate parts.  This might be used, for example, to label a

        LED on the board.  Different LEDs might be labeled "Power" and

        "Error", but they are the same physical part and should be listed

        on the same BOM entry.

SUBST

    Sets the substutions allowed field for the part on the BOM.  Valid

    values are "YES" and "NO".  The default is YES if SUBST does not exist

    or is empty.

DVAL

    Detailed part value.  If present and not empty, this field overrides

    the part value string on the BOM and will be used to differentiate

    parts.  DVAL is always assumed to be the true part value, so is not

    effected by VALSTAT.  The purpose of DVAL is to provide more

    information than reasonable to show on the schematic.  Generally the

    standard VALUE attribute will be shown on the schematic with DVAL

    shown on the BOM.

DESC

    Explicit description string for the BOM.  By default, the BOM

    description is derived from the library name and the device name

    within that library.  If the DESC attribute is present and not empty,

    its contents will override that default.

--

Web access to CadSoft support forums at www.eaglecentral.ca.  Where the CadSoft EAGLE community meets.