obsolete part in BOM list (mouser)

Tried the BOM generator and mouser import today, its quite impressing.

First I tried the comm controller card, no problem.

Next it was the stepper motor controller...

Found this component to be obsoleted, never done mouser before so I couldn't quite figure out what to do, maybe there is a susbstitute item?

I can otherwise be quite creative when substituting connectors when I want to :-E

538-39880-0102 (buy) 2 pin .200" connector

The link led me to this page on Molex.com, I don't even recognize this bugger,
what is it?

[www.molex.com]

that sure is a bummer. i found an identical part, that is in stock:

[www.mouser.com]

also, the BOM generator has been updated.

thanks for the heads up!

More like a crash-test-dummy than a heads-up ;-)

Although the BOM generator has been updated, I got the same obsolete part:

538-39880-0102 (buy) 2 pin .200" connector

from the BOM entry for the Universal Controller v1.2. Does the system recognize the same part regardless of which board it is in? If not, it might be nice to treat those subsitutions automagically, so that when a change is made on one board, it can propogate through the system.

what site are you using? make sure its parts.reprap.org

there is only one entry for each unique part, and then the lists for the collections of parts point to them.

here is the page for the 2 pin .200" connector: [parts.reprap.org]

its showing the correct, new number. make sure you're on parts.reprap.org. also, try shift + reload on the page as well.

~Zach

Uh oh. I appear to have been using the old sandbox page [bom-dev.reprap.org] instead of the current [parts.reprap.org] page. Given that I just ordered a big bunch of parts from Mouser based on the parts listing from that site, I wonder what surprises are in wait for me now! The listing you linked to is perfectly correct.

Edited 1 time(s). Last edit at 09/10/2007 11:13PM by rmadams.

oops! well luckily it was pretty current... the electronics portion of the BOM has been stable for a while. the only one that was off was probably the .200" terminal.

i've re-imported the cuttent data for the development site just in case others are using it (bad idea...)

Thanks, Zach. How about flagging the develment site with a watermark or big red text warning of the fact that it is a testing sandbox, with a link to the current production site? I am sure there are (at least some) other people who are as stupid as I am...

thats a good idea. i'll add that in.