mcmx/open-access-control

Automatically exported from code.google.com/p/open-access-control

open-access-control's Issues

Instructions for uploading firmware

What steps will reproduce the problem?
1. Press Upload button in Arduino without changing settings
2. Note stk500_getsync error
3. Change Tools>Board menu to "Duemilanove w/ ATMEGA328" and try again
4. Note it now works

What is the expected output? What do you see instead?

Expect instructions in the Arduino sketch, or wiki, on what "board" the 
hardware is detected as.

What version of the product are you using? On what operating system?

OA Standard Rev4, Arduino 1.0, software v4 136

Original issue reported on code.google.com by [email protected] on 13 Feb 2014 at 7:32

Wiki uses /dev/ttyACM0 and /dev/ttyUSB0 interchangably

What steps will reproduce the problem?
1. Via the wiki, type `chown root:dialout /dev/ttyACM0` and notice file not 
found error
2. Use /dev/ttyUSB0 instead, notice success

What is the expected output? What do you see instead?

Expect wiki to reflect how hardware shows up on raspi


What version of the product are you using? On what operating system?

OAC Hardware Rev4

Original issue reported on code.google.com by [email protected] on 13 Feb 2014 at 4:45

Update default in assignments in code to match new hardware design

The new board that is being developed will make use of all of the digital
and analog pins on a standard Arduino. We need to update the pin
assignments as follows:


byte reader1Pins[]={2,3};               // Reader 1 connected to pins 4,5
byte reader2Pins[]= {4,5};              // Reader2 connected to pins 6,7
const byte doorPin[]   = {6,7};         // Door Open pins
const byte alarmstrobePin= 8;           // Pre-alarm output relay pin 
const byte alarmsirenPin = 9;           // Siren/Alarm output relay pin
const byte analogsensorPins[] = 
{0,1,2,3};                             //Alarm Sensors on opto-isolators 

// Analog pins 4,5 are used for I2C support for the real-time clock (RTC)

Original issue reported on code.google.com by [email protected] on 9 Apr 2010 at 8:59

User dump not printing all 400 users

What steps will reproduce the problem?
1. enable at the serial console
2. dump all users (a) 

What is the expected output? What do you see instead?
Craps out around 268 users and skips from 258 to 397, and only shows up to user 
399, but the software thinks that 401 is a valid user.  This could be serial or 
the dump process.  More info and debugging is needed.

Please use labels and text to provide additional information.

Original issue reported on code.google.com by [email protected] on 26 Feb 2013 at 10:47

rc.local documentation

What steps will reproduce the problem?
1. Notice the line in the wiki, `h. Add the following lines to 
/etc/rc.d/rc.local:`
2. Fail to find an /etc/rc.d folder in the NOOB Raspbian image
3. Use /etc/rc.local instead

What is the expected output? What do you see instead?

Expect wiki to provide instructions for latest raspbian

What version of the product are you using? On what operating system?

NOOBS v1.3.3

Original issue reported on code.google.com by [email protected] on 13 Feb 2014 at 5:11

Recommend adding instructions for CLI arduino uploading

Right now the instructions encourage using the `arduino` program to burn images 
to the RPi, but with only two USB ports (and assuming no knowledge of X over 
SSH) this is hard. Might be nice to include instructions on burning the 
firmware via the CLI.

Note, these instructions are not yet verified working:

---
from: 
http://www.linuxcircle.com/2013/05/15/programming-and-uploading-arduino-sketch-w
ithout-ide/

---

arduino-mk package makes it simple to build and upload sketches on a Raspberry 
Pi without the bloated Arduino IDE.

Install the package:

sudo apt-get install arduino-mk
This will install all the required software and files.

Create a library area in your user home directory with a demo sketch in it: 
first, download Open_Access_Control_v4_std_136.zip to your home folder.

mkdir ~/sketchbook
cd ~/sketchbook
ln -s /usr/share/arduino/Arduino.mk
mkdir Open_Access_Control_v4_std
cd Open_Access_Control_v4_std
unzip ~/Open_Access_Control_v4_std_136.zip

Create the Makefile:

sudo nano Makefile

BOARD_TAG = uno
ARDUINO_PORT = /dev/ttyUSB0
ARDUINO_LIBS = Wire EEPROM DS1307 Wiegand26 PCATTACH Adafruit_MCP23017 AT24C
ARDUINO_DIR = /usr/share/arduino
include ../Arduino.mk

make

make upload

It will prepare the c and bit files and burn the memory on your Arduino. Watch 
your LED blinks.

Other commands to perform various tasks:

make – no upload
make upload – compile and upload
make clean – remove all our dependencies
make depends – update dependencies
make reset – reset the Arduino by tickling DTR on the serial port
make raw_upload – upload without first resetting
make show_boards – list all the boards defined in boards.txt

Original issue reported on code.google.com by [email protected] on 13 Feb 2014 at 7:16

Open_Access_Control_v4_std_136 won't compile in Arduino 1.0

What steps will reproduce the problem?
1. Install Arduino 1.0 and copy the library folders from the OAC v4 136 to the 
Arduino libraries folder.
2. Open Arduino and click the Verify button
3. Note that E24C1024.h is not found
4. Change E24C1024.h to AT24C.h and try again
5. Note that now WConstants.h is not found
6. Change in AT24C.h, change WConstants to Arduino.h, try again
7. Note that there are now Wire.send and Wire.receive errors
8. Change all instances of Wire.send to Wire.write and Wire.receive to 
Wire.read in AT24C.cpp
9. Program now compiles

What is the expected output? What do you see instead?

Program compiles in latest version of Arduino that comes standard on my platform

What version of the product are you using? On what operating system?

Arduino 1.0, Ubuntu 12.04, Open_Access_Control_v4_std_136.zip

Original issue reported on code.google.com by [email protected] on 13 Feb 2014 at 7:24

Dynamically update tag list using eeeprom storage

A future release really needs to allow for user management via
keypad/serial/PC and store the values in eeeprom.

Original issue reported on code.google.com by [email protected] on 9 Apr 2010 at 8:52

chmod needs a capital R

What steps will reproduce the problem?
1. type `chmod -r 700 /home/access/scripts` according to wiki
2. notice "chmod: cannot access `700': No such file or directory" erorr
3. type `chmod -R 700 /home/access/scripts` instead

What is the expected output? What do you see instead?

expect wiki to list chmod command with working command (capital R)

Original issue reported on code.google.com by [email protected] on 13 Feb 2014 at 5:52

Documentation and v1.35 Baud Mismatch

What steps will reproduce the problem?
1. Follow instructions here 
https://code.google.com/p/open-access-control/wiki/RaspberryPiSetup 
specifically regarding 57600 baud
2. Use latest Arduino firmware from this page 
https://code.google.com/p/open-access-control/downloads/list
3. Note mismatch between 9600 baud (Arduino) and 57600 baud (wiki)

What is the expected output? What do you see instead?
Expect more-recent version on downloads list (1.36) to be present in downloads 
list (and for Google Code wiki to match most recent version present on Google 
Code)

Original issue reported on code.google.com by [email protected] on 13 Feb 2014 at 4:17

Issues uploading to arduino

Hi John,

All open access files are in the Libraries folder.  get the following errors 
when compiling on Arduino 0023.

Cheers,

Scott.

Wiegand26\WIEGAND26.cpp.o: In function `WIEGAND26':
C:\Program Files 
(x86)\arduino-0023\arduino-0023\libraries\Wiegand26/WIEGAND26.cpp:15: multiple 
definition of `WIEGAND26::WIEGAND26()'
Open_Access_Control\WIEGAND26.cpp.o:C:\Program Files 
(x86)\arduino-0023\arduino-0023\libraries\Open_Access_Control/WIEGAND26.cpp:15: 
first defined here
Wiegand26\WIEGAND26.cpp.o: In function `WIEGAND26':
C:\Program Files 
(x86)\arduino-0023\arduino-0023\libraries\Wiegand26/WIEGAND26.cpp:15: multiple 
definition of `WIEGAND26::WIEGAND26()'
Open_Access_Control\WIEGAND26.cpp.o:C:\Program Files 
(x86)\arduino-0023\arduino-0023\libraries\Open_Access_Control/WIEGAND26.cpp:15: 
first defined here
Wiegand26\WIEGAND26.cpp.o: In function `~WIEGAND26':
C:\Program Files 
(x86)\arduino-0023\arduino-0023\libraries\Wiegand26/WIEGAND26.cpp:18: multiple 
definition of `WIEGAND26::~WIEGAND26()'
Open_Access_Control\WIEGAND26.cpp.o:C:\Program Files 
(x86)\arduino-0023\arduino-0023\libraries\Open_Access_Control/WIEGAND26.cpp:18: 
first defined here
Wiegand26\WIEGAND26.cpp.o: In function `~WIEGAND26':
C:\Program Files 
(x86)\arduino-0023\arduino-0023\libraries\Wiegand26/WIEGAND26.cpp:18: multiple 
definition of `WIEGAND26::~WIEGAND26()'
Open_Access_Control\WIEGAND26.cpp.o:C:\Program Files 
(x86)\arduino-0023\arduino-0023\libraries\Open_Access_Control/WIEGAND26.cpp:18: 
first defined here
Wiegand26\WIEGAND26.cpp.o: In function `WIEGAND26::reader3Zero()':
C:\Program Files 
(x86)\arduino-0023\arduino-0023\libraries\Wiegand26/WIEGAND26.cpp:113: multiple 
definition of `WIEGAND26::reader3Zero()'
Open_Access_Control\WIEGAND26.cpp.o:C:\Program Files 
(x86)\arduino-0023\arduino-0023\libraries\Open_Access_Control/WIEGAND26.cpp:113:
 first defined here
Wiegand26\WIEGAND26.cpp.o: In function `WIEGAND26::reader3One()':
C:\Program Files 
(x86)\arduino-0023\arduino-0023\libraries\Wiegand26/WIEGAND26.cpp:105: multiple 
definition of `WIEGAND26::reader3One()'
Open_Access_Control\WIEGAND26.cpp.o:C:\Program Files 
(x86)\arduino-0023\arduino-0023\libraries\Open_Access_Control/WIEGAND26.cpp:105:
 first defined here
Wiegand26\WIEGAND26.cpp.o: In function `WIEGAND26::reader2Zero()':
C:\Program Files 
(x86)\arduino-0023\arduino-0023\libraries\Wiegand26/WIEGAND26.cpp:83: multiple 
definition of `WIEGAND26::reader2Zero()'
Open_Access_Control\WIEGAND26.cpp.o:C:\Program Files 
(x86)\arduino-0023\arduino-0023\libraries\Open_Access_Control/WIEGAND26.cpp:83: 
first defined here
Wiegand26\WIEGAND26.cpp.o: In function `WIEGAND26::reader2One()':
C:\Program Files 
(x86)\arduino-0023\arduino-0023\libraries\Wiegand26/WIEGAND26.cpp:75: multiple 
definition of `WIEGAND26::reader2One()'
Open_Access_Control\WIEGAND26.cpp.o:C:\Program Files 
(x86)\arduino-0023\arduino-0023\libraries\Open_Access_Control/WIEGAND26.cpp:75: 
first defined here
Wiegand26\WIEGAND26.cpp.o: In function `WIEGAND26::reader1Zero()':
C:\Program Files 
(x86)\arduino-0023\arduino-0023\libraries\Wiegand26/WIEGAND26.cpp:66: multiple 
definition of `WIEGAND26::reader1Zero()'
Open_Access_Control\WIEGAND26.cpp.o:C:\Program Files 
(x86)\arduino-0023\arduino-0023\libraries\Open_Access_Control/WIEGAND26.cpp:66: 
first defined here
Wiegand26\WIEGAND26.cpp.o: In function `WIEGAND26::reader1One()':
C:\Program Files 
(x86)\arduino-0023\arduino-0023\libraries\Wiegand26/WIEGAND26.cpp:58: multiple 
definition of `WIEGAND26::reader1One()'
Open_Access_Control\WIEGAND26.cpp.o:C:\Program Files 
(x86)\arduino-0023\arduino-0023\libraries\Open_Access_Control/WIEGAND26.cpp:58: 
first defined here
Wiegand26\WIEGAND26.cpp.o: In function `WIEGAND26::initReaderThree()':
C:\Program Files 
(x86)\arduino-0023\arduino-0023\libraries\Wiegand26/WIEGAND26.cpp:93: multiple 
definition of `WIEGAND26::initReaderThree()'
Open_Access_Control\WIEGAND26.cpp.o:C:\Program Files 
(x86)\arduino-0023\arduino-0023\libraries\Open_Access_Control/WIEGAND26.cpp:93: 
first defined here
Wiegand26\WIEGAND26.cpp.o: In function `WIEGAND26::initReaderTwo()':
C:\Program Files 
(x86)\arduino-0023\arduino-0023\libraries\Wiegand26/WIEGAND26.cpp:44: multiple 
definition of `WIEGAND26::initReaderTwo()'
Open_Access_Control\WIEGAND26.cpp.o:C:\Program Files 
(x86)\arduino-0023\arduino-0023\libraries\Open_Access_Control/WIEGAND26.cpp:44: 
first defined here
Wiegand26\WIEGAND26.cpp.o: In function `WIEGAND26::initReaderOne()':
C:\Program Files 
(x86)\arduino-0023\arduino-0023\libraries\Wiegand26/WIEGAND26.cpp:30: multiple 
definition of `WIEGAND26::initReaderOne()'
Open_Access_Control\WIEGAND26.cpp.o:C:\Program Files 
(x86)\arduino-0023\arduino-0023\libraries\Open_Access_Control/WIEGAND26.cpp:30: 
first defined here

Original issue reported on code.google.com by [email protected] on 3 Mar 2012 at 7:45

Wiki needs to be more clear about cat / EOF commands

What steps will reproduce the problem?
1. type "cat > start_screen_logging.sh << EOF"
2. realize that the scripts don't work
3. remove those lines from all script files
4. stuff works again!

What is the expected output? What do you see instead?

Expect to have a bit of explanation about what the cat command does and what 
the script files actually need to contain. Indeed, since the default raspi 
install doesn't allow copy-paste from the wiki, maybe remove the cat commands 
entirely.

Original issue reported on code.google.com by [email protected] on 13 Feb 2014 at 3:19

Provide "Unlocked during specific hours" feature

Please provide any additional information below.

This is a feature request.  Please add the ability to allow the door locks to 
unlock during a specific time band during specific days of the week.  Example:
"locked during Sat, Sun"
"unlocked M-F from 8:30am to 5:30pm" 
etc.

If this feature exists, please document the usage of this feature in the wiki.

Thanks!

Original issue reported on code.google.com by [email protected] on 10 Oct 2012 at 3:13

scripts folder should be chown access

What steps will reproduce the problem?
1. follow instructions as root or pi
2. /home/access/scripts ends up owned by root and secured
3. access user can't even read the scripts to run them

What is the expected output? What do you see instead?

expect instructions to ensure scripts folder is accessible by correct user

Original issue reported on code.google.com by [email protected] on 13 Feb 2014 at 6:29

user access needs a password

What steps will reproduce the problem?
1. follow instructions, attempt to login on step (i.)
2. there has been no access password defined, only logging in as pi is supported

Original issue reported on code.google.com by [email protected] on 13 Feb 2014 at 6:28

Implement Ethernet logging

It seems that the Arduino UDP logs may have some issues with syslog. It
might be better to just scrap syslog support and come up with an http
get/post scheme for communicating with a log server.

This is also useful as a gateway to "who's at the space" feeds via
RSS/Twitter/etc.

Original issue reported on code.google.com by [email protected] on 9 Apr 2010 at 8:54

Hardware: Change power supply design

Based on feedback, the following changes need to be made to the power
supply circuit:

1. Update circuit using adjustable voltage regulator and current-limiting
diode. This is apparently how commercial alarm panels work.

2. Add MOVs to the outside-facing power buses.

Original issue reported on code.google.com by [email protected] on 12 Apr 2010 at 5:23