
ANPR ACCESS | INSTALLATION GUIDE
Configuration
24/36
number plate number, date and time) or the JPEG image
of the vehicle: %IMAGE_BW. The data is sent on the
network using a message header that includes the overall
number of data contained in the message.
Jpeg Quality:
Jpeg image quality. The value may range from 1 to 100
where 1 is the maximum compression level (lowest
quality) and 100 is the minimum compression level
(highest image quality). Suggested values from 50 to 90.
Server IP:
IP address of the server.
Server Port:
Server listening port.
Reuse Connection:
NO: the socket connection is opened and closed upon
every message.
YES: the socket connection is opened upon sending the
first message and is kept active. The connection is shut
down if unused for 15 minutes.
Regardless of mode configuration, the TCP connection will
close and open a new TCP connection when problems
occurred while sending data. This means the receiver
should be steadily ready to accept new TCP connections.
Buffering on SD:
In case of network failure and Buffering on SD is enabled,
the camera will save all data regarding the actions. When
the network connection is restored, the ANPR will manage
automatically all data stored, freeing the memory. The
saving is based over a circular buffer. In case of full
memory the ANPR will overwrite oldest data.
Standard message format - Network data packet format
Value
Length (in bytes) Description
24
4
Header size in bytes. Always set to 24
(=0x00000018).
<CMD>
4
Command code. Always set to 40000
(=0x00009C40).
0
4
Not used
0
4
Not used
<ERR>
4
Error code ( 0=no error).
<LEN>
4
Data size in bytes. 32-bit aligned. Header not
included.
<DATA>
<LEN>
Packet data. Containing the tag defined in the
Message field above.
The packet data contains the tags defined in the Message field. Every tag is defined
by a tag-identifier and a tag-size indicator. The packet may contain any number of
tag-fields. Tag-fields are arranged depending on the ANPR firmware. This may as well
change when using a different firmware version. For this reason, when searching for
tag-fields in a received packet, the server should scan all tag-fields regardless of
their position inside the received message. This programming method allows for
software compatibility with future firmware versions.