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:
Lane number – This is defined within netPark on the Self Park screen and is typically setup by netPark
Facility Code – If using RFID Prox reference the facility code on the cards from your provider
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.
Router/Gateway IP – Provided by the IT team at your location
Subnet mask – Provided by the IT team at your location
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:
Navigate to LAN
DHCP* – Set to “Disabled”
Controller IP Addr – Set IP Address of PEET device
Edit Gateway Addr – Set Gateway IP Address
Edit DNS Addr – Set DNS Address (if needed)
Edit Network Mask – Set Subnet Mask IP Address (typically 255.255.255.0)
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:
Navigate to Kiosk
Lane Number – Set Lane Number (should match lane number in netPark)
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
Date & Time – Set the “Timezone” option to the timezone of the location
Navigate to H/W Options
Barcode – Enable to accept barcodes
Set Keycard – Set to enabled if using RFID cards
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
Button – Set to enabled to issue tickets
Navigate to Loop Options
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.
In all configuration cases, a reboot of the PEET device is recommended.
Reporting in NetPark The Reports and Accounting Screens are used to display all reports within netPark Both screens are identical: The separate naming structure is used strictly for permission purposes. By allowing users to access only specific screens, you can limit the reports they have access to. Click the name of a report below see the breakdown of each report and what they do. Report Screen Company List - List of companies based on defined parameters The Company List allows users to generate a list of companies from within netPark Multiple variables can be set to narrow down the information contained in the report…
netPark Pay Card Readers Learn about the various Credit Card readers that netPark Pay supports and how to set them up and activate them.
BOCA Thermal Ticket Printer The BOCA Lemur is a small form-factor thermal ticket printer used for on-demand ticket printing and UVG printing within the netPark system. About Print Method: direct thermalPrint Speed: 10’’ per sec. maximumResolution: 203 dpi (8 dots/mm); 305 dpi (12 dots/mm); 600 dpi (premium upgrade)Size: 7.7 H x 7.3 W x 8.5 LWeight: 9.5 pounds BOCA Thermal Ticket Printer Installation Driver Installation Please follow the steps below to install the BOCA Printer Driver on your PC: Follow the link to download the Printer Driver Zip file: Boca_Systems.zip On most PCs, the file will be downloaded to the "Downloads" folder on your PC;…
Phone Hours (833) 638-7275 Monday – Friday: 10AM to 6PM EST Emergency Support – 24/7 for business critical functions
Contact Us Please use this form to contact us with any non-emergency comments, problems or inquiries. Be sure to provide details. If this is an emergency or requires immediate assistance, please call netPark Emergency Support.