JHinkle wrote:The board design I'm doing now is too big for my Eagle limitations.
Joe
Joe, how short are you in making it fit?
timon wrote:Joe, how short are you in making it fit?
Well over an inch in both directions.
Joe
dmcole wrote:I have created one board with DipTrace and to say it was a failure is an understatement. I brought the schematic across to the PCB module and couldn't make heads-nor-tails of the result. I redrew the PCB from scratch (bad idea) and left out a handful of connections.
CaptKirk wrote:I would love to see "the failure" that was generated by Diptrace (like a board PDF?) just to see what that looks like!
I thought this was a valid request and yesterday I went back through the project files. Of course, I didn't have the first cut of the PCB module, so I found the schematic I was using at the time and imported it into the PCB module.
After seeing what I got there, I now understand my ill-fated decision to redraw from scratch:
It was less about how the application splattered (still don't think that part was right) the components across the workspace and more about the fact there were a bunch of connections that didn't make their way across from the schematic to the PCB.
Now, you might say: "Hey, DMC -- why didn't you investigate the problem about the missing connections rather than start drawing the board from scratch?"
I don't have a good answer to that question. I should have gone back to the schematic module and found out why those problems were there and fixed them correctly.
So I think in this instance it would be more accurate to find fault with the user than with the application. Anyone who might not try DipTrace based on my inability to properly think through the problem -- rather than any deficiency in the software -- should not be dissuaded.
\dmc
