During a Self Park installation, the devices being installed need to be configured and tested. This checklist is for testing the devices after each one has been configured. This list should be done for each device that is configured to verify that the device is working as expected and up-to the expectations the lot owner has for it.
When testing it is possible to use metal to trigger the loops. HOWEVER, we highly recommend using an actual vehicle. If the self park device is configured for 2-loops Close mode, using metal will not trigger both of the loops in the way the device expects which will make testing difficult or prone to issues.
Device Type: ______________ (Entry/Exit/Camera)
All Device Types:
- Device shows as active in netPark with updating every 12 to 45 seconds
- Device model, function, description, rate, zone, user are set as necessary
- Presence Loop is wired and detectable in netPark
- Safety Loop is wired and detectable in netPark
- Loops mode has been configured on device (2-loops close, 2-loops far, etc)
- Open gate command in netPark opens the gate
- Gate shows as up on netPark Self Park Page
- Close gate command in netPark closes the gate
- Note: Not all installers are comfortable wiring this, but most lot owners expect it to be available. If you are installing a device, please discuss this with the lot owner. If this is not wired to the Device, the gate will still close automatically by the gate controller when the safety loop is driven over.
- Test barcode functionality
- Note: This does not need to be a valid barcode in the system, we just need to get a response from the device. It should change the screen or play an audio prompt confirming that the barcode was invalid. If it does not respond then the barcode reader isn’t active or being used. This event should be viewable in netPark.
- Test RFID functionality
- Note: This does not need to be a valid RFID in the system, we just need to get a response from the device. It should change the screen or play an audio prompt confirming that the RFID was invalid. If it does not respond then the RFID reader isn’t active or being used. This event should be viewable in netPark.
- Note: If using a long range reader, test for cross-lane reads. Turn down read strength and adjust reader angle as needed.
- No device errors or warning are showing on Self Park screen
- Verify tickets are loaded into the device correctly
- Test pulling 10 tickets by driving through different cars (small, mid-sized, truck, etc)
- Note: Tickets should be created in the system after driving through gate. Tickets should not have a backout discount applied.
- Note: It’s important to try several tickets. If tickets are inserted incorrectly or ticket mechanism is not fully closed, 2-4 tickets may be issued without problems, but eventually a jam will occur.
- Note: It’s important to test different vehicle sizes to verify loops are detecting as expected. Smart cars or motorcycles may be too short to trigger both loops. Consider 2-loops far setting if needed.
- Train owner and staff on how to replace tickets (and verify the results by pulling several tickets)
- Verify EMV reader is wired and that a credit card transaction works
- Verify receipt paper is loaded into the device correctly
- Pay for a ticket and collect a receipt
- Train owner and staff on how to replace receipt paper (and verify the results by running a transaction)
- Before fully installing camera, verify that the position and angle work via the browser interface
- Note: Camera needs to be configured on the network prior to this point.
- Add camera to appropriate self park device in correct position
- If camera is used for LPR, mark as LPR camera
- Mark self park device to take picture upon scan or loop event
- Test picture process by taking ticket, scanning or driving through device. Resulting ticket should have camera pictures.