readable x0x schematics

[guest]

perhaps not useful for everyone
but im constantly getting confused by what resistors go where
especially up in the switch and led section
so i cleaned up the schematics for the x0x
ive put them up on the openmusiclabs wiki
http://wiki.openmusiclabs.com/wiki/x0xb0x
feel free to grab them and host them as needed

[Luap]

That is indeed much more clear. Thanks for doing that

Presumably the readability factor is the only change, and the circuit is otherwise 100% identical?

For whatever reason, I didn't have the IO/powerboard before either, so this is all very useful.

[guest]

from a visual perspective its 99% the same
i added a few details where needed
but didnt take anything out

i cant guarantee that it will produce the same netlist
eagle is extremely finicky about connecting things
and i didnt verify that every connection was made
or that things werent connected if they were supposed to be unconnected
so it would be best to use the old schematics
for any pcb layout changes

if someone has a good suggestion on how to verify the netlist
i can try to do that

[westfw]

Very nice.

suggestion on how to verify the netlist

Copy the old .brd files to match the filenames of the new schematics, and check for brd/sch consistency errors. I see 27 for the mainboard, most of which seem to be renamed (redrawn) nets. However, this might be a multi-pass process (once you fix the named nets, there may be new errors that show up...)

I wonder if it is worthwhile for someone with a "pro" version of EAGLE to move the pieces around to different "sheets." The free version of EAGLE can still be used to look at the schematic, but changes/additions would become more difficult.

[guest]

ill give that a try
and perhaps there is a text file that contains the netlist
so i can do a diff and make sure its 100%

[westfw]

I believe the schematic editor has an "export netlist" capability, but I don't know whether that results in output that is usefully comparable to see if two schematics are different or not.

I played with it some last night. Note that a renamed net will result in a ERC "consistency error" for each pin connected to the net, so the actual number of errors was smaller than they list.
I found one actual "error" near S7, where both pins on one side of the switch are connected instead of just one. (not a REAL error, but an actual difference in the schematics.)

[guest]

ok ill give it a look

[guest]

i did a diff on the netlists and corrected all differences
with the exception of a few part names errors and juncture warnings
they give the exact same erc errors

[textile]

Cool!
I have a reference map that I did, I am just making sure all coordinates are right, then I'll share

Hey Westfw have you tried Design Spark? You can transfer the data from Eagle , it gives you unlimited board size - its free!! Whooo! (PC only, Mac version soon - I hope)
Other than that you can just delete the sections you don't want (on Eagle) then you are left with the parts and placement for that section, I have done it before for parts layout.

[guest]

the reference map is incredibly useful
if its possible to note the state of the machine
that helps as well
ive seen some people get confused because the note latch
wasnt in the exact same position for example

[IFadeToGrey]

Hey Westfw have you tried Design Spark? You can transfer the data from Eagle , it gives you unlimited board size - its free!! Whooo! (PC only, Mac version soon - I hope)
Other than that you can just delete the sections you don't want (on Eagle) then you are left with the parts and placement for that section, I have done it before for parts layout.

Design Spark is awesome. I've been using it to mod the mainboard over the last couple of days, and love it. What's really nice is that you can easily open up multiple schematics and PCBs and copy and paste between them... which normally would have taken more time than it's worth on Eagle.

I will say that autorouting seems a little better in Eagle though. Design Spark seems to have trouble getting all the way through some routes that Eagle would handle with no problem.