# Another BatchPCB DRC Failed

**URL:** <https://community.sparkfun.com/t/another-batchpcb-drc-failed/3502>\
**Category:** BatchPCB\
**Created:** [January 16, 2007, 2:56am UTC](https://community.sparkfun.com/t/another-batchpcb-drc-failed/3502 "2007-01-16T02:56:45Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![madcitysw](https://avatars.discourse-cdn.com/v4/letter/m/e480ec/32.png) [@madcitysw](https://community.sparkfun.com/u/madcitysw)\
**Post date:** [January 16, 2007, 2:56am UTC](https://community.sparkfun.com/t/another-batchpcb-drc-failed/3502/1 "2007-01-16T02:56:45Z")

</div>

Now that I had my other PCB passed everything, how I sending another PCB for testing and now it reporting a error again. After reading the logs, I see this

DRC Error - trace to narrow in the top\_drc.log, but when I check all of the traces in eagle, they all are in 8mil and don’t seem to find any that is smaller than 8mil. Eagle’s DRC passes the board. I however noticed that the pictures that I got back from BatchPCB is smaller than the one I sented off.

Here are the files: [http://www.vipermodz.com/chaser/errors/](http://www.vipermodz.com/chaser/errors/)

---

<div class="post-metadata">

**Author:** ![busonerd](https://avatars.discourse-cdn.com/v4/letter/b/958977/32.png) [@busonerd](https://community.sparkfun.com/u/busonerd)\
**Post date:** [January 16, 2007, 8:31pm UTC](https://community.sparkfun.com/t/another-batchpcb-drc-failed/3502/2 "2007-01-16T20:31:57Z")

</div>

Your server gives a timeout, but I’ll check the DRC bot log files.

Cheers,

–David Carne

---

<div class="post-metadata">

**Author:** ![madcitysw](https://avatars.discourse-cdn.com/v4/letter/m/e480ec/32.png) [@madcitysw](https://community.sparkfun.com/u/madcitysw)\
**Post date:** [January 17, 2007, 1:09am UTC](https://community.sparkfun.com/t/another-batchpcb-drc-failed/3502/3 "2007-01-17T01:09:51Z")

</div>

Um… I didn’t have any problems accessing my server, maybe it working fine now. What did you find so far?

---

<div class="post-metadata">

**Author:** ![busonerd](https://avatars.discourse-cdn.com/v4/letter/b/958977/32.png) [@busonerd](https://community.sparkfun.com/u/busonerd)\
**Post date:** [January 17, 2007, 1:25am UTC](https://community.sparkfun.com/t/another-batchpcb-drc-failed/3502/4 "2007-01-17T01:25:35Z")

</div>

Your server works fine now.

The issue is that you have a tiny “dot” on the copper side of the board - near the 2 pin connector on the left.

If you look closely in top.png you can see it.

Cheers,

–David Carne

---

<div class="post-metadata">

**Author:** ![reklipz](https://avatars.discourse-cdn.com/v4/letter/r/51bf81/32.png) [@reklipz](https://community.sparkfun.com/u/reklipz)\
**Post date:** [January 17, 2007, 1:47am UTC](https://community.sparkfun.com/t/another-batchpcb-drc-failed/3502/5 "2007-01-17T01:47:14Z")

</div>

I see it too, right above the center of the two pads on the left.

nice find, i couldnt see it at first when the image was scaled.

---

<div class="post-metadata">

**Author:** ![madcitysw](https://avatars.discourse-cdn.com/v4/letter/m/e480ec/32.png) [@madcitysw](https://community.sparkfun.com/u/madcitysw)\
**Post date:** [January 17, 2007, 11:18am UTC](https://community.sparkfun.com/t/another-batchpcb-drc-failed/3502/6 "2007-01-17T11:18:52Z")

</div>

Um… Are we talking about that little tiny red dot? I have no idea how that got there and you telling me it stopped because of that? LOL

---

<div class="post-metadata">

**Author:** ![busonerd](https://avatars.discourse-cdn.com/v4/letter/b/958977/32.png) [@busonerd](https://community.sparkfun.com/u/busonerd)\
**Post date:** [January 17, 2007, 6:20pm UTC](https://community.sparkfun.com/t/another-batchpcb-drc-failed/3502/7 "2007-01-17T18:20:16Z")

</div>

Yup.

That dot is to be drawn into the copper layer, and our FAB cannot draw it.

Ergo, the bot rejects it.

Cheers,

–David Carne