Configuring a Hamilton Entry/Exit Lane

The Hamilton Parking Entry/Exit Terminal (PEET) is the primary device in a self park installation. The purpose of this device is to allow your customers to enter your lot by pulling a ticket or by scanning a credential. A credential can be an employee badge, a loyalty card, a reservation or a parking pass. Before you begin setting up your PEET device, you’ll need to have a few things:

1. Lane number – This is defined within netPark on the Self Park screen and is typically setup by netPark
2. Facility Code – If using RFID Prox reference the facility code on the cards from your provider
3. NIM IP – Provided by the IT team at your location to netPark. Once we have configured and shipped the NIM we can provide this IP upon request.
4. Router/Gateway IP – Provided by the IT team at your location
5. Subnet mask – Provided by the IT team at your location
6. Controller IP – Provided by the IT team at your location (should be unique for each device)

Please note: The NIM IP, Gateway IP, Subnet Mask and Controller IP should all be provided by your IT team. netPark does not run or manage networks and cannot provide these details.

Setup device in netPark

The first step in configuring a PEET device is to get setup all devices in netPark. This allows us to clearly id each device and makes it easier to manage the lot. To begin, navigate to the Self Park screen in netPark and click the “Add New” button. A window will popup with some questions about the device you are configuring. With this being a PEET device you’ll want to select “Hamilton Entry PEET-S” or “Hamilton Validator PEET-V”. Provide a clear description of the device (e.g. Cashier Booth Left Entry). Note: The Lane Number specified here is what we will use when configuring the PEET. The lane number is the first digit of any ticket pulled from a PEET device. For example, if your lane number is “3”, tickets from the Hamilton device will be 3,000,000-3,999,999.

Configuring the PEET

Configuring a PEET is pretty straight-forward. To begin, you’ll need to connect your Hamilton Programming Device to the controller inside the PEET. Once you have connected your programming device, hit the “ESC” key to bring up the main menu.

Configuring Network Settings

Via the Main Menu, press F1 to access the NETWORK section and follow the below steps:

1. Navigate to LAN
   1. DHCP* – Set to “Disabled”
   2. Controller IP Addr – Set IP Address of PEET device
   3. Edit Gateway Addr – Set Gateway IP Address
   4. Edit DNS Addr – Set DNS Address (if needed)
   5. Edit Network Mask – Set Subnet Mask IP Address (typically 255.255.255.0)
2. Navigate to NIM IP and set to NIM’s IP Address

Configuring Device Settings

Via the Main Menu, press F2 to access the CONFIGURE section and follow the below steps:

1. Navigate to Kiosk
   1. Lane Number – Set Lane Number (should match lane number in netPark)
   2. Ticket Number – For a new device, set this to 0. If you are reconfiguring an existing device this should be set to the last issued ticket number for this lane
   3. Date & Time – Set the “Timezone” option to the timezone of the location
2. Navigate to H/W Options
   1. Barcode – Enable to accept barcodes
   2. Keycard
      1. Set Keycard – Set to enabled if using RFID cards
      2. HID Configuration
         1. Set Facility Code – Set to the facility ID on the prox cards, if you do not know or are using multiple types of cards, set to 0
   3. Button – Set to enabled to issue tickets
3. Navigate to Loop Options
   1. Set Loop Mode – Set the loop mode of the device to one of the following:
      • 1-Loop Presence – Event is complete when the device loop turns on and off
      • 1-Loop Safety – Event is complete when the gate loop turns on and off
      • 2-Loops Far – Event is complete when the device and gate loops turn on and off with a small delay between each
      • 2-Loops Close – Event is complete when the device and gate loops turn on and off with no delay between each (DEFAULT)

* We recommend disabling DHCP to make it easier to troubleshoot devices. A static IP address is not necessary.

Finalizing Configuration

In all configuration cases, a reboot of the PEET device is recommended.