SharpOS 13.6 Sharp Portal - Extension page - SharpV | SharpOS 13.6

To navigate to the Extension page, click Configuration > Connectivity > Extension.

The following information is displayed:

Extension type: None

None

Plate reads are stored locally on the SharpV and can only be retrieved using the Reads API which is an external application.

Extension type: FTP

Sends ALPR data to an FTP server. Configure the following:

Server

Enter the server name and location of the FTP server.

Username

Enter the username for the server.

Password

Enter the password for the username.

Content Template

ALPR data is sent in XML format, using the template shown. You can change certain elements if you choose.

Set default template

Reverts to the default template values.

Export context images

Export the context image (in JPEG format).

Export ALPR images

Export the plate image (in JPEG format).

Retain data when the connection is lost

Select this option for plate reads to be saved locally in the SharpV database if the connection with the server is lost. The system attempts to reconnect with the server every 30 seconds. Stored reads are pushed to the server when the connection is reestablished.

IMPORTANT: If there are any plate reads in the SharpV database, clearing this check box and saving the configuration deletes the plate reads.

Send sample

Verifies that the system can connect to the server and send a sample read file using the configured settings.

HTTP / HTTPS

Server

Enter the server name and location of the third party receiving HTTP server.

Format

Select the format you want to send the ALPR data in. You can select either JSON or XML format.

Username

Enter the username for the server.

Password

Enter the password for the username.

Anonymize ALPR data

The camera hashes the license plate using the SHA-1 algorithm. When you add an alphanumeric salt (cryptography) to the license plate number, it increases the security of the hashed output. Adding the same salt on all of the cameras in a network means that the same license plate produces an identical hash on all cameras. This allows the external system to recognize the identical hashes as a the same vehicle while still maintaining privacy.

IMPORTANT: If the salt is changed after it is set, it must also be changed on all other cameras. Changing the salt breaks the link between old reads and new reads.

Ignore certificate errors

Select this option when sending ALPR data to an HTTPS server that does not have a trusted certificate. The SharpV does not send the ALPR data to an HTTPS server that does not have a trusted certificate unless you select this option.

Export context images

Export the context image (in JPEG format).

Export ALPR images

Export the plate image (in JPEG format).

Retain data when the connection is lost

Select this option for plate reads to be saved locally in the SharpV database if the connection with the server is lost. The system attempts to reconnect with the server every 30 seconds. Stored reads are pushed to the server when the connection is reestablished.

IMPORTANT: If there are any plate reads in the SharpV database, clearing this check box and saving the configuration deletes the plate reads.

Security Center (LPM protocol)

Security Center (LPM protocol)

By default, LPM protocol is not an available extension. When a SharpV (SharpOS 12.7 and later) is manually added to the ALPR Manager (Security Center 5.8 and later), the LPM protocol is automatically selected as the unit’s extension type.

NOTE: When a SharpV is upgraded to SharpOS 12.7 or later, you must still upgrade the unit to use the LPM protocol before you connect to Security Center.

Security Center (Legacy)

Security Center (Legacy)

Use this option to send ALPR data to the ALPR Manager if connecting to Security Center 5.7 or earlier.

NOTE: If the unit connects to Security Center using the LPM protocol, this option is replaced by Security Center (LPM protocol).

This unit manages the connection to Security Center

Use this only if the autodiscovery of the connected SharpV does not work (see SharpV camera connections to Security Center) or if you cannot manually add the SharpV to the ALPR Manager. You must enter the Server address and Port of the server running the ALPR Manager role. For example, if a SharpV is connected to a WiFi router, and the camera’s IP address is then changed, the ALPR Manager cannot detect the change automatically, so you can use this to reconnect to the Security Center computer.

IMPORTANT:

• When using this option, no failover is available if the server connection is lost.
• Avoid the following configuration situations. Correcting these situations requires either assistance from AutoVu™ Support or the deletion and recreation of the ALPR Manager role:
  • Establishing a connection using This unit manages the connection to Security Center, then clearing the check box and saving again.
  • Adding the unit from Config Tool, establishing a connection, and then selecting This unit manages the connection to Security Center, and saving.

Discovery port

Port on which the SharpV listens for discovery requests. This port number must match the discovery port entered on the ALPR Manager Properties page.

NOTE: When setting the discovery port, do not use port 5050 as it is reserved for the logger service.

Control port

Used in Security Center Config Tool when creating a new ALPR unit (SharpV) manually.