Show Posts - esden

This section allows you to view all Messages made by this member. Note that you can only see Messages made in areas you currently have access to.

Messages - esden

General discussion / Re: How do you manage your parts?

February 04, 2012, 04:57:55 am

Hi,

[quote author="bnewbold"]Engineer from octopart here, hope that doesn't step on any toes...

If we can all come up with a good general purpose structured data format, it could be used for interchange between EDA tools, inventory management software, lookup and order placement APIs, etc. One common anti-pattern we see is designers/purchasers blurring the line between part descriptions ("1k 0805 2% resistor"), manufacturer part numbers, and distributor SKUs. Certainly each has their place, and any of these individually or in combination is a valid line item that can be searched for, but not in the same data field please!

[/quote]

As most part definitions have multiple distributors with different naming schemes we are using internally for our projects a type based naming of parts.

The general rule is the following:

[tt:]<type>-<package>[-<pincount>]-<value>[-<additional specs>][/tt:]

Here are some examples:

[tt:]res-0402-1k5
res-0603-44-0.25w
cap-cer-0402-1u
ic-so8-can_transceiver
mcu-tqfp-32-stm32f105
vreg-sot23-5-3v3[/tt:]

We use those ID's to link our PCB designs with part manufacturer selection, project BOM price calculation and final purchasing and assembly, using bom-x in Eagle and a damn big and complicated google docs spreadsheet. :)

It would be nice if we could just drop an ID like [tt:]res-0402-10k[/tt:] into Octopart and get a full list of 0402 10k resistors and find the cheepest source for it. Important to note is that in such a search we would not care about tolerance and wattage.

Things become more complicated with for example capacitors where you may care about which dielectrics you _don't_ want, for example those that start with X and Y. I am not sure how that should be handeled.

I still would love some consolidated standard way of naming electronic parts, so that it is easier to find the right manufacturer and supplier.

Cheers Esden

Bus Blaster JTAG debugger / Re: FTDI 2232 high speed programmer debugger (JTAG/SPI/I2C/UART)

March 30, 2010, 01:01:05 am

Yes that is a problem that I already know about github, I think I should finally report it.

Bus Blaster JTAG debugger / Re: FTDI 2232 high speed programmer debugger (JTAG/SPI/I2C/UART)

March 29, 2010, 04:36:27 pm

I used version 5.7.0. Did you download the eagle files one by one from the interface? If yes then it won't work (I already heard about the problem). Either download the whole source (http://github.com/esden/floss-jtag/zipball/master) or clone the repository: git clone http://github.com/esden/floss-jtag.git

Then you should be able to open the files.

Cheers Esden

Bus Blaster JTAG debugger / Re: FTDI 2232 high speed programmer debugger (JTAG/SPI/I2C/UART)

March 26, 2010, 04:31:43 pm

Hi! I just got pointed to this thread. It really seems that you are trying to do a similar thing I did with Floss-JTAG.

I see that you would like the design to be public domain? I could change the license of Floss-JTAG to PD-0 (http://creativecommons.org/publicdomain/zero/1.0/) but I am not sure that it is really necessary. I think CC-BY-SA is really free (as in freedom) license and I like when people have to release what they do based on open projects to the public, just like GPL does. An example of such usage is the OpenPilot version of Floss-JTAG (http://openpilot.org/Floss-JTAG). Still you can convince me if you want to.

I am currently working on a new version of Floss-JTAG which uses pretty eagle libs (http://github.com/esden/pretty-eagle-libs) to have proper footprint sizes as stated by the standards and a consistent look and feel of them.

Also that version will include an optional eprom. So I think all requirements you stated before should be covered by Floss-JTAG 0.3 version. I have built 10 of Floss-JTAG version 0.2 and several people are using it by now, so I consider it tested and working well.

Cheers Esden

( ! ) Fatal error: Uncaught exception 'Elk_Exception' with message 'Please try again. If you come back to this error screen, report the error to an administrator.' in /var/www/dangerousprototypes/forum/sources/database/Db-mysql.class.php on line 696
( ! ) Elk_Exception: Please try again. If you come back to this error screen, report the error to an administrator. in /var/www/dangerousprototypes/forum/sources/database/Db-mysql.class.php on line 696
Call Stack
#	Time	Memory	Function	Location
1	0.0143	2312296	session_write_close ( )	...(null):0
2	0.0146	2443888	ElkArte\sources\subs\SessionHandler\DatabaseHandler->write( )	...(null):0
3	0.0146	2444664	Database_MySQL->query( )	.../DatabaseHandler.php:119
4	0.0602	2583400	Database_MySQL->error( )	.../Db-mysql.class.php:273