Alarm Board Development - Closeout Tasks

[Aeasala]

• It would be useful to include a PCF8575 footprint beneath the IO expander. This would allow users to choose between installing a standalone chip, or an off-the-shelf plug-in assembly.
• Determine if decoupling caps are necessary. Preliminary results from prototyping are dictating that they are not.
• Change 470o/2.2nF filter to 1k/1nF. This removes one unique component from the bill-of-materials, replacing it with an already used 1kohm resistor. Nearly the same time constant.
• Attach or include mouser/digikey link to purchase entire set of board components. This would be a great convenience.
• Perform once-over check of component parameters, to ensure that their definitions and fields are consistent amongst others.
• Create a local library for custom footprints -- one which is tracked in version control.
• Tie silkscreen print of version, board name to values in the lower-right corner of the schematic. Minimizes possibility of being forgotten between revisions.

Finally, signature should also be edited, 1.5mmx1.5mm size, bold & italic, in the format of: ASPlab [DSKY] Alarm Board Rev. x.y.z

[Aeasala]

To research for future modification:

• 3 (or 2) LEDs/lamp, distributing same (or more) current between them per lamp.

[Aeasala]

in its current state, the PCF8575 footprint addition causes a discontinuity in the ground plane. creativity needed

[Pablo-Ortiz-Lopez]

in its current state, the PCF8575 footprint addition causes a discontinuity in the ground plane. creativity needed

I think the downsides outweigh the advantages of having the chip footprint directly on board, I think I'd rather not add this complexity