Issues with v2.0: Difference between revisions

From ACCX Products Wiki
Jump to navigation Jump to search
(Created page with "===Open Access Control - Issues with v1.0 and v2.0 hardware=== First off, the v2.x hardware has been very reliable and is installed at a number of locations. The system at [http...")
 
Line 1: Line 1:
===Open Access Control - Issues with v1.0 and v2.0 hardware===
===Open Access Control - Issues with v1.0 and v2.0 hardware===
First off, the v2.x hardware has been very reliable and is installed at a number of locations.
First off, the v2.x hardware has been very reliable and is installed at a number of locations. The system at [http://shop.23b.org 23b Shop] has been in production for over 1 year with no issues. There are some quirks to this system however, especially since it was designed without ever having seen a commercial unit. Here are some things we would like to improve.
 
The system at [http://shop.23b.org 23b Shop] has been in production for over 1 year with no issues.
 
There are some quirks to this system however, especially since it was designed without ever having seen a commercikal unit.


====List of Things to Improve in v3.0 Hardware====
====List of Things to Improve in v3.0 Hardware====
Line 21: Line 17:
* Consider adding an Arduino reset switch footprint
* Consider adding an Arduino reset switch footprint
* Grounded components hard to solder. Consider going to a grid for ground plane
* Grounded components hard to solder. Consider going to a grid for ground plane
* Better regulator footprint or more spacing for heatsink
* Better regulator footprint or more spacing for heat sink
* Need more inputs and outputs for Wiegand reader beeper, LEDs
* Need more inputs and outputs for Wiegand reader beeper, LEDs
* Consider Arduino Mega support
* Consider Arduino Mega support
Line 32: Line 28:
** Replace opto-isoloators with ESD absorbing devices. May also allow bi-directional support.
** Replace opto-isoloators with ESD absorbing devices. May also allow bi-directional support.
* Consider CPU that will handle encryption
* Consider CPU that will handle encryption
* [[Design Requirements]]
* [[Detailed Specification]]

Revision as of 17:41, 30 October 2011

Open Access Control - Issues with v1.0 and v2.0 hardware

First off, the v2.x hardware has been very reliable and is installed at a number of locations. The system at 23b Shop has been in production for over 1 year with no issues. There are some quirks to this system however, especially since it was designed without ever having seen a commercial unit. Here are some things we would like to improve.

List of Things to Improve in v3.0 Hardware

  • Separate power or ground for each sensor input (1 sensors = 2 screw terminals)
  • Consistent labeling (some items start with 0, others with 1)
  • Screw terminals obscure labels of pinouts.
  • Standardize Wiegand and other pin layout and order
  • Removable screw terminals (3.5 or 5mm) desirable for servicing
  • Need to label NO, C, O for relay terminals
  • Increased separation of trace spacing near relays
  • Double ground planes need stitch vias for better immunity
  • Eliminate ground plane around external relay traces
  • Readers with <100uS pulses require external capacitors to work
  • Break out ICSP pins from Arduino
  • Consider adding an Arduino reset switch footprint
  • Grounded components hard to solder. Consider going to a grid for ground plane
  • Better regulator footprint or more spacing for heat sink
  • Need more inputs and outputs for Wiegand reader beeper, LEDs
  • Consider Arduino Mega support
  • Look at RTC crystal and pick best temperature-compensation range
  • Think about on-board Ethernet
  • Option for RS-485
  • Option for SD card for local logging. Consider file system.
  • Control costs (SMT design, cheaper components in some areas
    • Switching PSU circuit
    • Replace opto-isoloators with ESD absorbing devices. May also allow bi-directional support.
  • Consider CPU that will handle encryption