Professional Documents
Culture Documents
7003055E - eRAM
7003055E - eRAM
Operating Instructions
About the eRAM
The eRAM (Remote Area Manager) hardware is a new addition to the RAMM and BLP family of products. eRAM has
been designed for small to large enterprise applications. eRAM features a Linux based platform running the ApeXX
access control software. eRAM also features it’s own SQLite database enhancing the eRAM performance.
The eRAM provides similar functionality of the RAMM. It is an area controller that allows up to 10 BLP’s for a total of 20
readers. BLPs require a prom update for proper operation with eRAM. eRAM is designed with it’s own SQL database
which manages the connected BLP door panels. AXxess 4.1 or later software communicates to the eRAM for
programming and management.
eRAM currently does not support BLP-200’s. It is designed to be used with BLP-206 Wiegand processors.
Tamper , AC Fail
and Bat Fail sensor
inputs not used.
NOTE: Inputs labeled ”Not Used” may be implemented in future releases of eRAM firmware.
RS485 Port 1 – Data bus connection to BLP door panels. Daisy chain connection. 9600 Baud
RS485 Port 2 – Data bus connection to BLP door panels. Daisy chain connection. 9600 Baud
NOTE: Either or both RS485 ports may be used for connecting to BLP’s and Input Modules. The eRAM features
an internal multiplexer. Do not exceed a total of 10 units between both ports. One BLP equals one unit, four
Input Modules equal one unit.
RS485 Data bus must be terminated using 120 ohm resistors (included with eRAM) at both ends of the data line
for each port used. On board termination may be applied using the jumpers on the lower left of the eRAM board.
See label.
TCP/IP Ethernet – Used for Ethernet communications to the eRAM from the MultiPort computer.
Port 1 EOL Resistor – Used to terminate Port 1 RS485 data bus.
Port 2 EOL Resistor – Used to terminate Port 2 RS485 data bus.
WARNING - Do not power eRAM with an unregulated transformer as it can cause damage to the eRAM.
LED’s
Power – Solid Red LED if power is present. Flashes Red when there is network activity.
Comm – Blinks twice and pauses. The first blink indicates MultiRAMM communication status. The second blink
indicates panel communication status. A pause between blinks indicates end of blink sequence.
The ARP command below is performed from the Command window. Click Start, Run, enter CMD and click OK.
The ARP command is as follows:
NOTE: The ping must be performed within 2 minutes of powering up the eRAM.
Once the temporary IP Address has been assigned proceed to the section below Programming the
Network Address settings for the eRAM.
eRAM Introduction and Installation guide.doc Page 5 of 20 8/20/2012 1:03:00 PM
Mounting the unit in the DIN track.
Using the included hardware, assemble the mounting brackets to the unit. The brackets can be mounted on either edge
and in various positions to optimize the layout in the enclosure.
TCP/IP Ethernet
IP Address 192.168.6.12
Netmask 255.255.255.0
Broadcast 192.168.6.255
Gateway Not specified
About Gateways
Note that a default gateway is not specified. If you need to set a gateway for your network, you must specify it.
About Broadcast IP
It is necessary that the broadcast IP is set correctly. Failure to do so may cause unpredictable results. It must be
set to the subnet of the IP address plus 255. See examples below for a Class C, B and A subnet respectively.
if the IP address is 192.168.9.10 and the sub net mask is 255.255.255.0, then the IP subnet is 192.168.9. The
Broadcast IP would then be 192.168.9.255.
If the IP address is 192.168.9.10 and the sub net mask is 255.255.0.0, then the IP subnet is 192.168. The
Broadcast IP would then be 192.168.255.255.
If the IP address is 192.168.9.10 and the sub net mask is 255.0.0.0, then the IP subnet is 192. The Broadcast IP
would then be 192.255.255.255.
NOTE: The Calc button may be used to configure the Broadcast IP.
There are two options for programming the network settings, using the eRAM Setup utility or using the ARP
command. Maxxess recommends using the eRAM Utility which can be started from the Windows Start,
Programs, AXxess, Accessories, eRAM Setup menu.
NOTE: If more than one new eRAM is to be configured at a time, the following command may need to be
sent between each eRAM. Otherwise it may take approximately 5 minutes from the time the one eRAM is
disconnected before the next one will be recognized.
arp –d 192.168.6.12
1. Install the eRAM on the network using the TCP/IP Ethernet connection for the network. Apply power to the
eRAM. NOTE: You must be able to ping the eRAM at 192.168.6.12 before the utility will work.
2. Execute the eRAM Setup utility from the Windows Start, Programs, AXxess, Accessories, eRAM Setup menu.
NOTE: It is recommended that the eRAM database is backed up before performing a firmware update.
The firmware update is performed using the Maxxess eRAM Setup Utility which is accessed from the Windows
Start, Programs, AXxess, Accessories, eRAM Setup menu. The firmware file is located in the root AXxess 200
folder. The file name is eRAM_firmware_XX_XXX.bin.
3. Type the User and password. Default User is root and the password is pass.
4. Type the IP address of the eRAM to update.
5. Create a backup by entering a path or browsing to a folder location. Click the Backup button to execute.
6. Update the firmware by browsing to the AXxess 200 Server Installation folder and selecting the appropriate
eRAM_Firmware_XX_XXX.bin file. Click the Update button to execute.
7. Once updated, click the Reboot eRAM button.
8. Verify that the AXxess software is communicating with the eRAM and re-initialize from the Desktop or
MultiPort.
9. Once the “Initialization Sequence 1” message is received on the MultiPort, perform an eRAM status from the
MultiPort application to confirm the revision of the eRAM.
The eRAM Setup Utility may be used to change the eRAM telnet password from the default of pass to any
password up to 8 characters. If the password is lost, the unit must be returned to Maxxess in order to be
restored. The password is case sensitive.
NOTE: For security reasons, it is recommended that the password be changed by the user.
The password may be changed from either the Network Settings or Firmware Update sections of the eRAM Setup
utility.
1. Execute the eRAM Setup Utility from the Windows Start, Programs, AXxess, Accessories, eRAM Setup
menu.
2. Select the Network Settings or Firmware Update option in the tree.
3. Click on the Change Password… button.
The content of the file may be copied to the clipboard by clicking on the Copy to Clipboard button.
To access the interface, start a telnet client and point it to port 10001 on the eRAM.
Using Windows, go to Start, Run and type telnet iii.iii.iii.iii 10001 and press enter. Where iii is the IP
address of the eRAM to troubleshoot.
The following window will appear. Press enter to receive the prompt.
At the prompt, login to the unit using username login and password pass.
Type login pass and hit enter. The following will appear.
0 – ERROR
1 – WARN
2 – INFO
3 – DEBUG 1
4 – DEBUG 2
…..
9 – DEBUG 7
Confirm password>Maxxess
Password changed!
show badge #
Example, show info for badge number ‘9816529’
Badge: 9816529
PIN: -1
Count: 255
Activation: Wed Oct 1 16:00:00 2003
Expiration: Sun Oct 30 15:59:00 2005
Last seen at door: 0.0
Schedule 3:
Start Stop Status
----- ----- ------
00600 01200 INACTIVE
10600 11200 INACTIVE
20600 21200 INACTIVE
30600 31200 ACTIVE
40600 41200 INACTIVE
80600 81200 INACTIVE
Schedule: normal 0
1. Wait until the eRAM is relatively quiet, ie. little or no badge reads, sensor activity, etc. in progress.
2. Using any ftp client software, ftp to the eRAM and log in.
Unless it was changed, the default user is ‘root’ and default password is ‘pass’
4. Get all database files (*.db), any journal files (*journal*), all log files (*.log), and any config files (*.cfg)
mget *.db
mget *journal*
mget *.log
mget *.cfg
or, you can just get everything from ‘/mnt/flash’, including the ramm executable,
mget *
6. Copy all files into a Zip file and upload the file to the secure Maxxess Support web site.
The database (*.db), log (*.log) and system log (‘/var/log/messages’) files are most important.