I have no idea what to do with those links…
In order to save the files, it is necessary to right click the links, and choose "save link as" from the context menu.
You don’t need to supply separate EAGLE libraries,
as the components used in a schematic and board
file are copied automatically.
This is good to know, thanks.
I have two schematics of yours from downloading
the previous link. One has a transistor switch on the
USB 5V pin the other one has a diode to 3.3V - not
sure what that all about?
The one with the transistor switch is the same as the torc-eagle.zip file(schematically, I believe I made a bit more room for the switching circuit, and removed a redundant AC connection).
In the buck converter section there are two 1N4148
diodes - odd for a high frequency converter, are these
supposed to be fast-recovery types?
Indeed you are correct, these should not be 1N4148's. The diodes I have are in fact fast recovery diodes, in the same package as the 1N4148 in the schematic. I should have changed the name in the schematic at least, sorry for the confusion!
Back to the power supply. A diode in series with the
3.3V supply would drop it to about 2.7V is this
intended? Also, the schematic with the transistor
switch would apply 5V to the USB port when (and
only when) the local 12V supply is off. As the 5V
rail is derived from the 12V rail, what does this
switch circuit do?
The 2.7V is fine, as it is an PIC18LF2550 I intend to use (again, probably should have changed the name). As for the switching circuit; The 5V is *not* derived from the 12V rail, it is only supplied when the device is plugged into USB (or when it is being programmed). In order to allow the device to be operable while powered from mains power and while being hooked up to a computer via USB, this switch is needed.
Finally, there’s a bus symbol in EAGLE that would
make your schematic easier to follow. It
replaces the eye-numbing parallel lines with a
single bus and net-named breakouts.
Sorry about that! I knew about this bus feature, and had used it at one point. When I realized I would need a ribbon cable to connect the two boards, I had to do a way with it, and the nets had already been named, thus causing trouble when making two buses. A mistake on my part.
Thank you very much for your input! I’m sorry it has been such a pain to get the files to work properly!
Let me know if there are any other questions.
-Nate