Stalker Stationary Speed Sensor II Technical Manual

Stalker Stationary Speed Sensor II
Technical Manual
011-0131-00
Applied Concepts, Inc.

2609 Technology Drive
Plano, Texas 75074
9723983780
Rev. H
Stalker Stationary Speed Sensor II Technical Manual

Regulatory Statement
Note: This equipment has been tested and found to comply with the limits for a Class A digital
device, pursuant to part 15 of the FCC Rules. These limits are designed to provide reasonable
protection against harmful interference when the equipment is operated in a commercial
environment. This equipment generates, uses, and can radiate radio frequency energy and, if not
installed and used in accordance with the instruction manual, may cause harmful interference to
radio communications. Operation of this equipment in a residential area is likely to cause harmful
interference in which case the user will be required to correct the interference at his own
expense.
Changes or modifications not expressly approved by Applied Concepts, Inc. could void the
user's authority to operate the equipment.
Not intended or approved for Law Enforcement use in the United States.
Stalker/Applied Concepts
2609 Technology Drive Plano, TX 75074 USA
1-800-STALKER
(972) 398-3750 Sales / (972) 398-3751 Fax
www.stalkerradar.com


Table of Contents
1
2
3
Overview ..................................................................................................................... 5
Specification ................................................................................................................ 6
Physical characteristics................................................................................................ 7
3.1
Package dimensions ............................................................................................. 7
3.2
Electrical connections .......................................................................................... 8
4 Connecting the Stationary Speed Sensor ...................................................................... 9
4.1
Connecting to the COM Ports ................................................................................ 9
4.1.1 COM B RS232 Full Duplex Port...................................................................... 9
4.1.2 COM A and COM C RS485 Ports ................................................................... 10
4.1.2.1 COM A RS485 Full Duplex Port ............................................................ 11
4.1.2.2 COM A and COM C RS485 Half Duplex Ports ......................................... 11
4.2
Auxiliary Relay Connections ............................................................................... 12
5 Custom Applications to Control the Stationary Speed Sensor II ................................... 12
6 Streaming Speed Data Protocols ................................................................................ 13
6.1
A Format Single Visual Speed Only .................................................................. 14
6.2
B Format All Visual Speeds + Status ................................................................. 15
6.3
D0 Format Strong Visual Speed Only, Optional Direction Byte .......................... 16
6.4
D1 Format Strong Visual Speed Only, Optional Direction Byte, Checksum ......... 16
6.5
D2 Format Strong Visual Speed Only, Optional Direction Byte, Tenths .............. 17
6.6
D3 Format Strong Visual Speed Only, Optional Direction Byte, Relative
Amplitude, Tenths......................................................................................................... 18
6.7
D4 Format Strong Visual Speed Only................................................................ 18
6.8
Enhanced Output Format Hex All Visual Speeds, Status .................................... 19
6.9
S Format ASCII Visual Speeds + Status ............................................................. 21
6.10 BT Format ASCII Timestamp from the units internal realtime clock ............... 22
6.11 DT Format ASCII Date/Time stamp from the units internal realtime clock...... 23
6.12 DBG1 Format ASCII information for all tracked statistics targets ...................... 24
6.13 LOG Message ASCII information for statistics targets as they are lost ............... 25
7 Handshake Speed Data Protocols ............................................................................... 26
7.1
EE Polling .......................................................................................................... 26
7.1.1 EE Format Request (from Controller to Stationary Speed Sensor II) ................ 27
7.1.2 EE Format Response (from Stationary Speed Sensor II to Controller) .............. 27
7.2
EA Polling .......................................................................................................... 27
7.2.1 EA Polling Request (from Controller to Stationary Speed Sensor II) ................ 27
7.3
Polled Mode for D0D4 Formats ......................................................................... 28
8 Configuration Setting Descriptions ............................................................................. 28
Basic Configuration ............................................................................................ 28
8.1
8.2
COM Ports ......................................................................................................... 30
8.3
Target Recognition ............................................................................................ 34
8.4
Target Filtering .................................................................................................. 35
8.5
Speed Presentation ............................................................................................ 36
8.6
Locking Targets ................................................................................................. 37
8.7
Realtime Clock .................................................................................................. 38
8.8
Aux Pin Usage .................................................................................................... 39
8.9
Traffic Statistics (stats unit only) ........................................................................ 39
3

8.10 System ............................................................................................................... 42
9 Configuration Settings Table ...................................................................................... 43
10 Configuration Protocol ........................................................................................... 48
11 Sensor variations.................................................................................................... 50
11.1 200088052,53 ................................................................................................. 50
11.1.1
Summary ................................................................................................ 50
11.1.2
Mechanical Description ........................................................................... 50
11.1.3
Electrical Connection .............................................................................. 51
11.1.4
Operation ............................................................................................... 51
11.2 200088054,55 ................................................................................................. 52
11.2.1
Summary ................................................................................................ 52
11.2.2
Mechanical description ........................................................................... 52
11.2.3
Electrical connections ............................................................................. 52
11.2.4
Operation ............................................................................................... 52
11.3 200100400 ..................................................................................................... 53
11.3.1
Summary ................................................................................................ 53
11.3.2
11.3.3
Electrical Connections ............................................................................. 55
11.3.4
Operation ............................................................................................... 55
11.4 200088056 ..................................................................................................... 56
11.4.1
Summary ................................................................................................ 56
11.4.2
11.4.3
Electrical Connection .............................................................................. 57
11.4.4
Operation ............................................................................................... 57
11.5 200103300,01 ................................................................................................. 58
11.5.1
Summary ................................................................................................ 58
11.5.2
11.5.3
11.5.4
Operation ............................................................................................... 60
11.6 200103310,11 ................................................................................................. 61
11.6.1
Summary ................................................................................................ 61
11.6.2
11.6.3
11.6.4
Operation ............................................................................................... 63
12 FCC Requirements .................................................................................................. 64
Appendix A
OEM 6 x 26 Stationary Speed Sensor II for Lane Discrimination .......... A-1

1 Overview

The S Stationary Speed Sensor II is a complete Doppler Radar in a small, rugged
housing. Its direction sensing capabilities and its featurerich configuration settings allow it
to filter out undesired targets and focus on your targets of interest.

The Stationary Speed Sensor II connects to the serial port on a PC or other controller via an
RS232, an RS485, or a USB link. This interface is used to configure the unit and to monitor
the speed data it sends out. The Stationary Speed Sensor can be configured to report the
speeds of targets it acquires in many formats from short ASCII character strings to larger
data packets with speed and status information.

The RS232 or USB port can stream speed data and monitor for commands from the
controller at the same time. When configured for a fourwire connection, an RS485 port
can also send and receive data at the same time. When configured for a twowire
connection however, RS485 ports only communicate one way at a time; they never stream
data as a slave on the link. They only respond to commands and speed requests from the
controller. RS485 links have the benefit of operating over longer cable distances from the
controller, and also multiple RS485 units can be installed in a pointtomultipoint
configuration and controlled from a single serial port on a controller.

The compact, waterproof unit can be mounted almost anywhere. Just supply 1045 VDC
power, and the Stationary Speed Sensor produces serial speed data configured for your
application.

2 Specification
GENERAL SPECIFICATIONS
Product Type
Processor
Operating Temperatures
Storage Temperatures
Stationary Doppler Radar Speed Sensor

Digital Signal Processor
-30C to +70C (-22F to +158F), 90% relative humidity
-40C to +85C (-40F to +185F)
MICROWAVE SPECIFICATIONS
Operating Frequency
Frequency Stability
Antenna Type
3 db Beam Width
Power Output
24.125 GHz (K-band)

50 MHz
Planar array
30 by 32
18 dBm EIRP
ELECTRICAL SPECIFICATIONS
Supply Voltage
Current (at 12 VDC
nominal)
10 - 45 VDC
12 - 35 VAC
Transmitter On: 85 mA
Transmitter Off: 40 mA
PHYSICAL SPECIFICATIONS
Weight
Size (LxWxH)
Case Material
13 oz (0.35 kg)
4.4 x 3.9 x 1.6 inches
11.2 x 9.9 x 4 cm
Aluminum die cast
PERFORMANCE SPECIFICATIONS
Stationary Speed Range
Accuracy
Max target speed: 200 MPH (322 km/h, 174 knots, 89 meters/sec, 293
feet/sec)
.5 MPH 0.3%, (.8 KPH .3%)
In ones resolution, speeds are rounded to nearest integer.
In tenths resolution, speeds are rounded to nearest tenth.
3 Physical characteristics
3.1 Package dimensions

3.2 Electrical connections
Use the table below to identify the electrical connections in the external connector.
Pin
Number
Wire Color
Primary Function
Secondary Function
1
2
Brown
Red
USB D+
USB D-
Orange
Yellow
5
6
7
Dark Green
Blue
Violet
Gray
Black
10
White
11
12
Pink
Light Green
AC Power (factory only option)

AC Power (factory only option)
COM B, RS-232 RX (From
Computer)
COM A, RS-485 RX-, Full Duplex
(From Computer)
DC POWER
AUX Relay
AUX Relay
COM A, RS-485 TX+, Full Duplex
(To Computer)
COM A, RS-485 TX-, Full Duplex
(To Computer)
COM A, RS-485 RX+, Full Duplex
(From Computer)
COM B, RS-232 TX (To Computer)
GROUND
COM C, RS-485 T/R-, Half Duplex
USB V
COM A, RS-485 T/R+, Half Duplex
COM A, RS-485 T/R-, Half Duplex
COM C, RS-485 T/R+, Half Duplex
The diagrams below shows the pin out of the cable and sensor connectors as mated.
The columns in the table below show pins used for different connection options.
Pin
Number
1
2
3
4
5
6
7
8
9
10
11
12
Wire Color
Brown
Red
Orange
Yellow
Dark Green
Blue
Violet
Gray
Black
White
Pink
Light Green
RS-485 Full
Duplex
RS-485 Half
Duplex
RS-232
COM B, RX (from computer)

COM A, RXDC Power
Relay (optional)
Relay (optional)
COM A, TX+
COM A, TXCOM A, RX+
COM C, T/RDC Power

Relay (optional)
Relay (optional)
COM A, T/R+
COM A, T/RCOM C, T/R+
Ground
Ground
8
DC Power
Relay (optional)
Relay (optional)
COM B, TX (to computer)

Ground
4 Connecting the Stationary Speed Sensor

4.1 Connecting to the COM Ports
There are four standard COM ports on the Stationary Speed Sensor II. Not all ports are
available on all sensor models. COM A is an RS485 port which can be either 4wire full
duplex or 2wire halfduplex. COM B is a 2wire fullduplex RS232 port. COM C is a 2wire
halfduplex RS485 port. COM D is a fullduplex USB port which can have flow control
enabled. Depending on the units configuration one, two, three or four COM ports may be
used at the same time. The factory default configuration has COM A as a 4wire fullduplex
RS485 port, COM B as a 2wire fullduplex RS232 port, COM C as disabled, and COM D as a
USB port. This default configuration allows COM A, COM B, and COM D to be used
simultaneously.

All Stationary Speed Sensor II COM ports are configured for 10 bit asynchronous serial
communications with 1 start bit, 8 data bits, 1 stop bit and no parity (8N1). This is standard
for PC serial ports, but a custom controller may need to be modified to match these settings.
COM A and COM C, the RS485 ports, have interdependencies, so COM B is discussed first
below.
4.1.1 COM B RS232 Full Duplex Port

COM B is the simplest port to connect and configure. It provides a standard RS232 port
with Transmit Data (TX) and Receive Data (RX) signals relative to its ground (GND) as
shown in the diagram below.
I
n 11 RS-232 TX
t
e 3 RS-232 RX
r
f 12 GROUND
a
c
e
TX
COM B
RS-232
Full Duplex
RX
GND

The sensor transmits data by changing the voltage level on the TX wire relative to GND. The
TX wire should be connected to the receive signal on the PC/controller, and the GND should
be connected to the controllers GND signal. The controller receives the data on its end by
sensing the voltage changes relative to GND.

In a like manner, the controllers TX signal is connected to the sensors RX, and the sensor
receives controller data by sensing the voltage changes on that wire relative to the same
ground. Because there are the two separate signals (TX and RX), the link is defined as full
duplex meaning that the data signals can flow in both directions at the same time without
corrupting each other.

A limitation on RS232 links is distance. The sensor and controller can communicate over
cables but only so far. Since received data is sensed as a voltage relative to the links
ground signal, as the cable gets longer, the received voltage changes get lower and noisier
9

and become harder to detect reliably resulting in degraded communications. This distance
can be affected by wire size in the cable, crosstalk between wires in the cable as well as
routing the cable through noisy environments.

Most newer PCs are not configured with the older 9pin D serial ports and have USB ports
instead. In these cases, acquire a USB to serial port adapter to perform the necessary
conversion. These products vary and may or may not work well. In some cases they
provide undesirable buffering and delay, and a different brand should be used.
4.1.2 COM A and COM C RS485 Ports

RS485 ports differ from RS232 in that RS485 uses a pair of wires with no ground for each
direction of transmission instead of the RS232 method of using one wire for each direction
relative to a shared ground. Instead of generating or sensing a voltage level relative to
ground like RS232, RS485 transmits data by changing the direction of current flow in the
loop created by its two wires. Although still affected by noisy environments, RS485 links
can operate over longer distances than RS232 because the receivers are not trying to
measure smaller and smaller voltages relative to a noisier and noisier ground as the
distances increase. They just have to measure the direction of the current flow on a closed
loop.

RS485 links can be implemented in a 4wire or a 2wire implementation. With four wires,
the link is fullduplex because one pair of wires can be used to send data one way, and the
other pair can be used to send data the other way permitting twoway simultaneous
communication.

With only two wires, the two ends of the link must coordinate their sending of data so that
only one end transmits at a time. On this halfduplex link, if both ends try to transmit at
the same time, the communications will be garbled and neither end will be able to receive a
clean signal.

To prevent messages in the two directions from colliding, the RS485 halfduplex protocol
requires that there be a master on one end of the link and a slave on the other. A Stationary
Speed Sensor II always acts as the slave device, and the controller is always the master. On
a halfduplex link the Stationary Speed Sensor II only answers commands or requests for
speeds from the controller. It never sends any data without receiving a request first, and it
never streams speed data.

The Stationary Speed Sensor II has two RS485 ports: COM A and COM C. COM A can be
configured to be 4wire fullduplex or 2wire halfduplex. COM C is always a 2wire half
duplex port. They share internal connections to only four pins on the main connector, so
either COM A can be 4wire while COM C is disabled, or they can both be 2wire ports.
10

4.1.2.1COM A RS485 Full Duplex Port
The default configuration for the COM A port is 4wire as shown below. The two wires for
the transmit data are TX+ and TX, and the two wires for the receive data are RX+ and RX.
Notice that since there is a pair of wires for each direction, both the sensor and the
controller can transmit and receive at the same time creating a fullduplex link. In this
configuration, COM C cannot be used and is disabled.
TX+
I
n
t
e
r
f
a
c
e
TXCOM A
RS-485
Full Duplex
RX+
RX-
COM C
RS-485
Disabled
8 COM A, RS-485 TX+

9
COM A, RS-485 TX-
10 COM A, RS-485 RX+

4
COM A, RS-485 RX-
unused

4.1.2.2COM A and COM C RS485 Half Duplex Ports

The 2wire halfduplex implementation on COM A is shown below. In this configuration,
there is only one pair of wires COM A+ and COM A which is used for both directions of
communication. Since the second pair of signals on COM A is unused, COM C may be
enabled and connects to the other two pins on the connector as a second, independent half
duplex port.
COM A+
I
n
t
e
r
f
a
c
e
COM ACOM A
RS-485
Half Duplex
unused
COM A, RS-485 T/R+
COM A, RS-485 T/R-
10 COM C, RS-485 T/R+

4
COM C, RS-485 T/R-
COM C+
COM C
RS-485
Half Duplex
COM C
11

4.2 Auxiliary Relay Connections
The AUX Relay Contacts, pins 6 and 7 of the interface connector, provide a contact closure
interface. The sensor can internally short these pins together or leave them in their normal
state of an open circuit. On some models, pin 6 is used for other purposes, so in those cases,
pint 7 is shorted internally to ground. This interface is used by the Stationary Speed Sensor
II to implement an external status signal which is described in more detail in the Aux Pin
Usage section of Section 8.

5 Custom Applications to Control the

Stationary Speed Sensor II

This chapter discusses in detail the protocol used to communicate with the Stationary
Speed Sensor IIs. It is the protocol used by S demo applications such as Dashboard
and can be used by designers to develop custom applications to control Stationary Speed
Sensor IIs. A basic knowledge of hexadecimal math is required, but the protocol fields are
basically fill in the blank.

Using the configuration protocol described in Section 10, a designer can get the current
value of a setting from the unit, set the setting to a new value or change (increment) the
value. When a PC or other controller sends a configuration command packet to the
Stationary Speed Sensor II, the Stationary Speed Sensor II responds immediately with a
packet in the same format. The only values changed in the returned packet are the
Destination ID, Source ID, Configuration Value and the Checksum bytes. The Payload
Length may also change depending on the length of the returned Configuration Value.

The PC/controller is always defined to be the master (ID = 0x01) so commands from the
controller will always have 0x01 as the Source ID, and responses from Stationary Speed
Sensor IIs will always have 0x01 as the Destination ID.

The default Unit ID for Stationary Speed Sensor IIs is 0x02 and need not be changed on
pointtopoint links between a sensor and a PC/controller whether on an RS232 or RS
485 port.

Multiple units using RS485 ports can work simultaneously on a single link to the controller
in a pointtomultipoint configuration. The ID of each one must be unique and in the range
of 2254 (0x02 0xFE). ID 0 is undefined and should not be used. ID 255 (0xFF) is the
broadcast address. Every unit on the link acts on commands sent to ID 255, so a controller
can, for example, turn all the radar transmitters on or off with a single command. Be aware
that each unit also sends a response packet to a broadcast command, and that the responses
are likely to be garbled on the shared link. For this reason, always disregard responses to
broadcast commands unless there is only one Stationary Speed Sensor II on the link. If the
response from a single unit on a multipoint link is desired, always address that unit in the
command.

Another good use for a broadcast command is to find out the ID of a Stationary Speed
Sensor II that may not be responding to its expected address. Make sure the unit is the only
one on the link, and send the Get Stationary Speed Sensor II Address command (1/116) to
12

the broadcast Destination ID 255 (0xFF). As long as the baud rate is correct, the unit will
respond back using its ID as the Source ID in the response packet.

All of the configuration methods (get, change and set) use the same packet format defined in
Section 10. The differences are in the use of the Command ID and the Configuration Value
fields.
The change command and the get command are similar in that the Command ID
field is set equal to the Setting ID (in hex) from the list of settings in Section 9.
o For a change command, the Configuration Value is set to 1 to instruct the
Stationary Speed Sensor II to increment the value by 1 and return the
resulting value: change(1). If the incremented value exceeds the legal range
for the setting, the value rolls around to the lowest value in the range.
o For a get command, the Configuration Value is set to 0 basically instructing
the Stationary Speed Sensor II not to increment the current value but to
simply return it. This is essentially a change(0) command.
For a set command, the Command ID field is set equal to 0x80 plus the Setting ID
value (in hex) from the list in Section 9 (essentially turning on the highorder bit).
The Configuration Value field is set to the new desired value.

In the response packet, the Stationary Speed Sensor II inserts the value of the requested
setting in the Configuration Value field. Once the Destination and Source IDs and the
Configuration Value are correct, the sensor calculates a new checksum and inserts it into
the packet before sending off the response.

6 Streaming Speed Data Protocols

When a streaming protocol is selected on a fullduplex port, the Stationary Speed Sensor II
sends continuous speed updates in the selected output format at a specified message
period. When one of these protocols is selected on a halfduplex port, the unit sends only a
single message in the selected output format in response to each EA Poll from the
controller. Refer to the COM Ports section in Section 8 for settings that affect the content
and timing of these messages.

The following streaming protocol message formats are supported.

A ASCII single visual speed only
B ASCII all visual speeds + status
D0 ASCII strong visual speed only, optional direction byte
D1 ASCII strong visual speed only, optional direction byte, checksum
D2 ASCII strong visual speed only, optional direction byte, tenths
D3 ASCII strong visual speed only, optional direction byte, relative amplitude, tenths
D4 HEX strong visual speed only
Enhanced Output Hex all visual speeds + status
S ASCII visual speeds + status
BT ASCII Timestamp from the units internal realtime clock
DT ASCII Date and Timestamp from the units internal realtime clock
DBG1 ASCII information for all tracked statistics targets (stats unit only)
LOG ASCII information for statistics targets as they are lost (stats unit only)
13

6.1
A Format Single Visual Speed Only
Byte #
1
2
3
4

Description
Speed hundreds digit (ASCII)
Speed tens digit (ASCII)
Speed ones digit (ASCII)
Carriage Return
Value
0x0D
A Format messages are 4 bytes in length. The baud rate setting must be 1200 or greater to ensure
that a complete message is sent before the radar processes a new message to send.

Use the Format A Speed setting for the desired port to select the Strong visual target or the Fast
visual target to be sent in this message.
When the Unit Resolution (Setting 1/21) is set for tenths, the speed reported is multiplied by ten:
58.5 MPH is reported as 585. The decimal point is assumed. An A Format message can carry a
maximum speed in tenths of 99.9.

14

6.2
B Format All Visual Speeds + Status
Byte #
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
Description
Message Type
Status 1
Status 2
unused
unused
unused
Locked speed hundreds digit (ASCII)
Locked speed tens digit (ASCII)
Locked speed ones digit (ASCII)
Fast speed hundreds digit (ASCII)
Fast speed tens digit (ASCII)
Fast speed ones digit (ASCII)
Target speed hundreds digit (ASCII)
Target speed tens digit (ASCII)
Target speed ones digit (ASCII)
Carriage Return
Value
0x81
(see detail below)
(see detail below)
0x20 (space) or 0x30 (ASCII 0)
0x0D

Status 1 byte
Bit 76:
Bit 5:
Bit 4:
Bit 3:
Bit 2:
Bit 1:
Bit 0:

Status 2 byte
Bit 76:
Bit 54:
Bit 3:
Bit 2:
Bit 1:
Bit 0:
always = 01 (to force displayable ASCII characters)

lock status (0=no speed locked, 1=speed locked)
zone (0=closing, 1=away/both)
always = 0
always = 0
always = 1
transmitter status (0=off, 1=on)
always = 00
fast lock status (0=no fast speed locked, 1=fast speed locked)
fast status (0=faster disabled, 1=faster enabled)
always = 0
always = 0

B Format messages are 16 bytes in length. The baud rate setting must be 4800 or greater to ensure

When the Unit Resolution (Setting 1/21) is set for tenths, the speeds reported are multiplied by ten:
58.5 MPH is reported as 585. The decimal point is assumed. A B Format message can carry a

15

6.3
D0 Format Strong Visual Speed Only, Optional Direction Byte
Byte #
1
2
3
4
5

Description
Optional direction byte
Carriage Return
Value
0x0D
D0 Format messages are up to 5 bytes in length. The baud rate setting must be 1200 or greater to
ensure that a complete message is sent before the radar processes a new message to send.

If the direction byte is not enabled for the desired port, it is not sent, and the message will be a 4 byte
message. When enabled, the direction byte is + for approaching, for receding, and ? for
unknown.

58.5 MPH is reported as 585. The decimal point is assumed. A D0 Format message can carry a

6.4
D1 Format Strong Visual Speed Only, Optional Direction Byte, Checksum
Byte #
1
2
3
4
5
6

Description
S
Carriage Return
Checksum
Value
The letter S (0x53)
0x0D

message. When enabled, the direction byte is + for approaching, for receding, and ? for
unknown.

The checksum is the sum of the preceding bytes truncated to the low order 7 bits.
When the Unit Resolution (Setting 1/21) is set for tenths, the speed reported is multiplied by ten: 8.2
MPH is reported as 82. The decimal point is assumed. A D1 Format message can carry a maximum
speed in tenths of 9.9. Due to this limited speed range, the tenths setting is not recommended for this
format.

16

6.5
D2 Format Strong Visual Speed Only, Optional Direction Byte, Tenths
Byte #
1
2
3
4
5
6
7

Description
Decimal Point
Target Speed tenths digit (ASCII)
Carriage Return
Value
0x2E
0x0D

message. If enabled, the direction byte is + for approaching, for receding, and ? for unknown.

The Unit Resolution (Setting 1/21) should be set to tenths for this format to report speeds properly.

17

6.6
D3 Format Strong Visual Speed Only, Optional Direction Byte, Relative

Amplitude, Tenths
Byte #
1
2
3
4
5
6
7
8
9
10
11
12

Description
*
Decimal Point
Target Speed tenths digit (ASCII)
,
Relative Amplitude hundreds digit (ASCII)
Relative Amplitude tens digit (ASCII)
Relative Amplitude ones digit (ASCII)
Carriage Return
Value
Asterisk (0x2A)
0x2E
Comma (0x2C)
0x0D

If the direction byte is not enabled for the desired port, it is not sent, and the message will be an 11
byte message. If enabled, the direction byte is + for approaching, for receding, and ? for
unknown.

Amplitude values are relative and in the range 0160.

The Unit Resolution (Setting 1/21) should be set to tenths for this format to report speeds properly.

6.7
D4 Format Strong Visual Speed Only
Byte #
1
2
3
4
5
6
7

Description
0x02 (HEX)
0x84 (HEX)
0x01 (HEX)
Target Speed (HEX)
0x01 (HEX)
0xAA (HEX)
0x03 (HEX)
The bytes are sent just as above, in HEX format. The only variable is speed, which is the strong target
speed expressed in HEX format, e.g. 30 MPH would be sent as 0x1E. The maximum speed that can be
reported in this format is 255

D4 Format messages are 7 bytes in length. The baud rate setting must be 2400 or greater to ensure
25.5 MPH is reported as 255. The decimal point is assumed. A D4 Format message can carry a
maximum speed in tenths of 25.5
18

6.8
Enhanced Output Format Hex All Visual Speeds, Status
Byte #
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
Description
Start ID
Destination ID
Source ID
Packet Type
Payload Length (LSB)
Payload Length (MSB)
Command ID
Antenna Number
Target Speed (LSB)
Target Speed (MSB)
Faster Speed (LSB)
Faster Speed (MSB)
Locked Speed (LSB)
Locked Speed (MSB)
unused
unused
Direction
Status
Configuration
Checksum (LSB)
21

Checksum (MSB)
Value
0xEF
0xFF (broadcast address)
0x02
0x01
0x0D
0x00 (length = 0x000D = 13 bytes) (bytes 719)
0x00
0x01
Speed of strongest target is 16bit number
(see above)
Speed of faster target is 16bit number
(see above)
Locked speed (strong or fast) is 16bit number
(see above)
0x00
0x00
(see detail below)
(see detail below)
(see detail below)
The checksum should equal the 16bit sum of pairs
of bytes in LSB, MSB order starting with byte #1 as
the first LSB through and including the last byte
before the Checksum (in this case, byte #19). In
the case of an odd number of bytes, 0x00 is used as
the last MSB value. (See example packet below.)
(see above)
Direction byte
Bits 76:
always = 00
Bits 54:
locked speed direction (0=unknown, 1=closing, 3(1)=away)
Bits 32:
fast speed direction (0=unknown, 1=closing, 3(1)=away)
Bits 10:
target speed direction (0=unknown, 1=closing, 3(1)=away)

Status byte
Bit 7:
always = 0
Bit 6:
always = 0
Bits 53:
units (000=MPH, 001=km/h, 010 = knots, 011 = meters/sec, 100 = ft/sec)
Bit 2:
Bit 1:
strong lock (1=locked speed is strongest target)
Bit 0:
fast lock (1=locked speed is faster target)

Configuration byte
Bits 73:
always = 00000
Bits 21:
zone (00=away, 01=closing,10=both closing and away)
Bit 0:
always = 0

19

Enhanced Output Format messages are 21 bytes in length. The baud rate setting must be 4800 or
greater to ensure that a complete message is sent before the radar processes a new message to send.
When the Unit Resolution (Setting 1/21) is set for tenths, the speeds reported are multiplied by ten:
58.5 MPH is reported as 585. The decimal point is assumed. Since the speeds are sent as hex values,
an Enhanced Output Format message can easily carry the highest measurable speed of 321 km/h (or
3210 in tenths).

EXAMPLE PACKET (Enhanced Output Format)

Byte # Description
Example Values
1
Start ID
0xEF
2
Destination ID
0xFF
3
Source ID
0x02
4
Packet Type
0x01
5
0x0D
6
0x00
7
Command ID
0x00
8
Antenna Number
0x01
9
Target Speed (LSB)
0x37 (55 MPH)
10
Target Speed (MSB)
0x00
11
Fast Speed (LSB)
0x4B (75 MPH)
12
Fast Speed (MSB)
0x00
13
Locked Speed (LSB)
0x37 (55 MPH)
14
Locked Speed (MSB)
0x00
15
unused
0x00
16
unused
0x00
17
Direction
0x1D
18
Status
0x06
19
Configuration
0x00
20
Checksum (LSB)
0xD4
21
Checksum (MSB)
0x08
Checksum = 0x08D4 (truncated to the low order 2 bytes) = 0xFFEF + 0x0102 + 0x000D +
0x0100 + 0x0037 + 0x004B + 0x0037 + 0x0000 + 0x061D + 0x00

20

6.9
S Format ASCII Visual Speeds + Status
Byte #
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
Description
Message type
Faster target direction
Faster target speed
(same)
(same)
(same)
Strongest target direction
Strongest target speed
(same)
(same)
(same)
Strongest target strength
(same)
(same)
Channel signal strength ratio
(same)
(same)
Status
Carriage return
Value
0x83
A = away, C = closing
Hundreds (100)
0 9 (ASCII)
Tens (10)
0 9 (ASCII)
Ones (1)
0 9 (ASCII)
Tenths (0.1)
0 9 (ASCII)
A = away, C = closing
Hundreds (100)
0 9 (ASCII)
Tens (10)
0 9 (ASCII)
Ones (1)
0 9 (ASCII)
Tenths (0.1)
0 9 (ASCII)
Hundreds (100)
0 9 (ASCII)
Tens (10)
0 9 (ASCII)
Ones (1)
0 9 (ASCII)
Hundreds (100)
0 9 (ASCII)
Tens (10)
0 9 (ASCII)
Ones (1)
0 9 (ASCII)
0x40 (see detail below)
0x0D
Status byte
Bit 76:
Bit 5:
Bit 4:
Bits 30:

always = 0
always = 0
always = 0

S Format messages are 19 bytes in length. The baud rate setting must be 4800 or greater to ensure

Strongest target strength values are relative and in the range 132.

Channel signal strength ratio is a measure of the directionality of the target. A higher number is
more directional.

21

6.10 BT Format ASCII Timestamp from the units internal realtime clock
Byte #
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
Description
Message Type
Status 1
unused
ASCII space
Fractional second tens digit (ASCII)
Fractional second ones digit (ASCII)
ASCII space
Second tens digit (ASCII)
Second ones digit (ASCII)
ASCII space
Minute tens digit (ASCII)
Minute ones digit (ASCII)
ASCII space
Hour tens digit (ASCII)
Hour ones digit (ASCII)
Carriage Return
Value
0x81
(see detail below)
0x40
0x20
0x20
0x20
0x20
0x0D

Status 1 byte
Bit 76:
Bit 5:
always = 0
Bit 4:
always = 0
Bit 3:
always = 0
Bit 2:
always = 0
Bit 1:
always = 1
Bit 0:

The BT Format has the same basic format as the B Format except speeds are replaced with times. If a
sensor is configured for this format and connected to a PC running the demo app, the units internal
realtime clocks time is displayed in the apps four windows: hh mm ss fs.

BT Format messages are 16 bytes in length. The baud rate setting must be 4800 or greater to ensure

22

6.11 DT Format ASCII Date/Time stamp from the units internal realtime clock
Byte #
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
Description
Year thousands digit (ASCII)
Year hundreds digit (ASCII)
Year tens digit (ASCII)
Year ones digit (ASCII)
ASCII slash (/)
Month tens digit (ASCII)
Month ones digit (ASCII)
ASCII slash (/)
Date tens digit (ASCII)
Date ones digit (ASCII)
ASCII space
ASCII colon (:)
ASCII colon (:)
ASCII decimal point (.)
Fractional second tens digit (ASCII)
Fractional second ones digit (ASCII)
Carriage Return
Value
0x2F
0x2F
0x20
0x3A
0x3A
0x2E
0x0D

The DT Format message is an ASCII string showing the units internal realtime clocks date and time
as follows: 2000/12/31 23:59:59.99<cr>.

DT Format messages are 23 bytes in length. The baud rate setting must be 9600 or greater to ensure

23

6.12 DBG1 Format ASCII information for all tracked statistics targets
This format is only used in the stats unit.
Byte #
1
2
3
4
5
6
7
8
9
10
Description
ASCII T
Target number tens digit
Target number ones digit
ASCII space
Target ID thousands digit
Target ID hundreds digit
Target ID tens digit
Target ID ones digit
ASCII space
Target direction ASCII C for closing,
A for away, ? for unknown
Last target speed hundreds digit
Last target speed tens digit
Last target speed ones digit
ASCII space
Peak speed direction C, A or ?
Peak speed hundreds digit
Peak speed tens digit
Peak speed ones digit
ASCII space
Average speed direction C, A or ?
Average speed hundreds digit
Average speed tens digit
Average speed ones digit
ASCII space
Target Strength tens digit
Target Strength ones digit
ASCII space
Target duration thousands digit
Target duration hundreds digit
Target duration tens digit
Target duration ones digit
ASCII space
Carriage Return
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
Value
0x54
0x20
0x20
0x20
0x20
0x20
0x20
0x20
0x0D

When the DBG1 Format is selected, the unit streams a 33byte ASCII message as defined above (e.g.
T00 0018 A040 A041 A040 18 0006 <cr>) for each of the targets being tracked. If the unit is
configured for tenths resolution, a decimal point and tenths digit is added to each speed value (e.g.
T00 0018 A040.1 A041.3 A040.4 18 0006 <cr>) and the message length is 39 bytes.

Since the unit can track up to 15 targets, the baud rate setting must be set at 115200 to ensure that a
complete message for each target is sent before the radar processes new target information.

24

6.13 LOG Message ASCII information for statistics targets as they are lost
This format is only used in the stats unit.
Byte #
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
Description
ASCII L
ASCII O
ASCII G
ASCII space
Target ID thousands digit
Target ID hundreds digit
Target ID tens digit
Target ID ones digit
ASCII space
Year thousands digit (ASCII)
Year hundreds digit (ASCII)
Year tens digit (ASCII)
Year ones digit (ASCII)
ASCII slash (/)
Month tens digit (ASCII)
Month ones digit (ASCII)
ASCII slash (/)
Date tens digit (ASCII)
Date ones digit (ASCII)
ASCII space
ASCII colon (:)
ASCII colon (:)
ASCII space
Direction first character (ASCII)
Direction second character (ASCII)
Direction third character (ASCII)
Direction fourth character (ASCII)
ASCII space
ASCII L
Last target speed hundreds digit
Last target speed tens digit
Last target speed ones digit
ASCII space
ASCII P
Peak target speed hundreds digit
Peak target speed tens digit
Peak target speed ones digit
ASCII space
ASCII A
25
Value
0x4C
0x4F
0x47
0x20
0x20
0x2F
0x2F
0x20
0x3A
0x3A
0x20
A or C
W or L
A or O
Y or S
0x20
0x4C
0x20
0x50
0x20
0x41

46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
Average target speed hundreds digit

Average target speed tens digit
Average target speed ones digit
ASCII space
Target Strength tens digit
Target Strength ones digit
ASCII space
Target classification
ASCII space
Target duration thousands digit
Target duration hundreds digit
Target duration tens digit
Target duration ones digit
ASCII space
Carriage Return
0x20
0x20
0x20
0x20
0x0D

When LOG messages are enabled with the Enable Stats LOG Messages setting on a port, the unit
generates a 60byte ASCII message as defined above
(e.g. LOG 0015 2000/12/31 23:59:59 CLOS L040 P041 A040 19 2 0077 <cr>) for each of the targets
lost in the last radar measuring period. It appends these LOG message(s) to the end of the selected
standard streaming format messages. If the unit is configured for tenths resolution, a decimal point
and tenths digit is added to each speed value
(e.g. LOG 0015 2000/12/31 23:59:59 CLOS L040.1 P041.3 A040.4 19 2 0077 <cr>) and each LOG
message is 66 bytes long.

Due to the length of these messages and the variable number of them, the baud rate setting should be
set at 115200 to ensure that all generated messages are sent before the radar processes new target
information.

7 Handshake Speed Data Protocols

When a handshake (polling) protocol is selected, the Stationary Speed Sensor II sends only
one speed message for each speed data request (poll) it receives from the controller.

7.1 EE Polling

The simple EE Format Request is a two byte message as shown below. The response from
the Stationary Speed Sensor II is a four byte message carrying fields for live visual speed (in
hexadecimal) and direction. Since there is no addressing in the request message, it is
assumed that it is directed to a unit with a Stationary Speed Sensor II ID of 2; and only a unit
with ID=2 responds to it.

The EE Format only reports one speed the strongest visual speed is reported.

26

Refer to Users Manual for instructions on configuring the demo application to poll for EE
Format responses.

7.1.1 EE Format Request (from Controller to Stationary Speed Sensor II)

Byte #
1
2

Description
Start ID
Check byte
Value
0xEE
0x12 (0xEE + 0x12 = 0 (mod 256))
7.1.2 EE Format Response (from Stationary Speed Sensor II to

Controller)
Byte #
1
23
Description
Start ID
Speed
Check byte
Value
0xEE
Bit 15 valid bit (1=valid speed)
Bit 1413 direction (11=away,
00=unknown,
01=closing
Bit 12 unused
Bit 110 speed in selected units and unit resolution
Bytes 14 sum to 0 (mod 256)
7.2 EA Polling

EA Polling Request messages are like those for EE, but they contain Destination and Source
IDs as shown below. The source ID is always 1 for the controller. The destination ID can be
any value in the range from 2 through 254, and only a Stationary Speed Sensor II with that
address will respond. Its response to the EA poll is to send a single speed message in the
streaming format selected by the Output Format setting for that port. Only those ports
configured as halfduplex respond to EA polling. Fullduplex ports stream speed messages
continuously.

The demo PC application does not support EA polling.

7.2.1 EA Polling Request (from Controller to Stationary Speed Sensor II)

#
1
2
3
4

Description
Start ID
Destination ID
Source ID
Check byte
Value
0xEA
0x02 0xFE (2254)
0x01
Bytes 14 sum to 0 (mod 256)
27

7.3 Polled Mode for D0D4 Formats

The D0D4 Formats described in Section 6 may also be used in polled mode. If polled mode
is selected on the desired port, sending a 3 byte poll string of *P<cr>, (0x2A 0x50 0x0D)
causes a return of the current target speed in the selected D0D4 format. Used in
conjunction with the Format D Polled Mode setting, only use the *P poll on fullduplex,
streaming ports to reduce the quantity of streamed messages. On halfduplex ports, use EA
polling as described in Section 7.2.

The demo PC application does not support polling in the D0D4 formats.
8 Configuration Setting Descriptions

All the control and configuration settings available for the Stationary Speed Sensor IIs are
described in this Section. Here, they are arranged in the following groups of related
function.

1. Basic Configuration
2. COM Ports
3. Target Recognition
4. Target Filtering
5. Speed Presentation
6. Locking Targets
7. Realtime Clock
8. Aux Pin Usage
9. Traffic Statistics (stats unit only)
10. System

The tables at the beginning of each of the sections below list the settings included in each
group. The Setting column shows the setting names. The ID column shows the Packet Type
and ID number to be used for each setting when building a Configuration Protocol message
or command (Refer to Section 10 for the protocol format).

The Default column contains the factory default values for each setting.
in this column means that the setting is not used to configure a setting. It is used to
request an action or status from the Stationary Speed Sensor II. And the Available Values
column shows the possible values for each setting.

The table in Section 9 lists all the available settings in order of ID number for ease of
reference.

8.1 Basic Configuration

Setting
Transmitter Control
ID
Default
1/42
28
Available Values
0 = Hold
1 = Transmit
2 = Automatic (stats unit only)

Mode
1/1
0 = Stationary
0 = Both
Target Direction
1/2
0
1 = Closing
2 = Away
0 = MPH
1 = km/h
Units
1/20
0
2 = knots
3 = meters/sec
4 = feet/sec
0 = ones
Unit Resolution
1/21
0
1 = tenths
OSD Date Time (CCTV unit
0 = Disabled
1/40
0
only)
1 = Enabled
OSD NTSC/PAL (CCTV unit
0 = NTSC
1/56
0
only)
1 = PAL
OSD On Screen Alarm Display
0 = Disabled
2/6
1
(CCTV unit only)
1 = Enabled
OSD Alarm Type (CCTV unit
0 = Over
1/57
0
only)
1 = Under
The X/Y notation for IDs in the table above means to use X for the Packet Type field in a
Configuration Protocol command and to use Y for the Setting ID value. Refer to Section 10
for a description of the Configuration Protocol format.

The Transmitter Control setting (1/42) turns the radar transmitter on or off. The
transmitter must be on for the radar to register speeds. The Automatic value is used in
conjunction with statistics gathering. When a survey is loaded into the unit, it includes
calendar settings to allow the unit to run statistics during certain time periods on certain
days. When the Transmitter Control is set for Automatic, the statistics function controls the
state of the transmitter by turning it off if no statistics are being gathered. This results in
lower power draw and the ability run an interrupted survey for more days.

The Mode setting (1/1) is fixed in stationary mode (value = 0) and can be read but not
changed.

The Target Direction setting (1/2) tells the radar to look for targets moving in certain
direction(s) relative to the unit. The Target Direction values are Away to monitor receding
targets only, Closing to monitor approaching targets only and Both to monitor targets
moving in either direction.

The Units setting (1/20) selects the units of speed measurement. The available options are
MPH, km/h, knots, meters/sec and feet/sec.
The Unit Resolution setting (1/21) can be set to report speeds in whole units, as 25, or
tenths of units, as 25.4.

The OSD (On Screen Display) settings are for the Speed CCTV Sensor model only. OSD Date
Time enables the date and time to be overlaid on the video. OSD NTSC/PAL selects the
video format. OSD On Screen Alarm Display enables an onscreen indication when the
sensor detects a vehicle speed outside its alarm setting. And the OSD Alarm Type selects
29

whether the alarm indication occurs when a target is over or under the alarm speed
threshold.

8.2 COM Ports

COM A
ID
COM B
ID
COM C
ID
2/16
2/48
Baud Rate
2/17
2/33
2/49
Output Format
2/18
2/34
2/50
Message Period
Leading Zero
Character
2/19
2/35
2/51
2/20
2/36
2/52
Format A Speed
2/21
2/37
2/53
Zeros After Target

Loss
2/22
2/38
2/54
2/23
2/39
2/55
2/24
2/40
2/56
2/25
2/41
2/57
Setting
COM A Link
Configuration
COM C Link
Configuration
COM D Link
Configuration
Format D Direction
Character
Format D Update On
Change Only
Format D Zero
30
COM D
Default Available Values
ID
0 = 485 2W Half Duplex

1
1 = 485 4W Full Duplex
0 = Disabled

0
1 = 485 2W Half Duplex
0 = USB No Flow Control
2/64
0
1 = USB w/ Flow Control
5 = 9600 baud
6 = 19200 baud
7 = 38400 baud
8 = 57600 baud
2/65
9
9 = 115200 baud
10 = 230400 baud
11 = 460800 baud
12 = 921600 baud
0 = None (no serial output)
1 = A
2 = B
3 = D0
2 for all 4 = D1
but
5 = D2
COM C 6 = D3
2/66

7 = D4
0 for
8 = EE
COM C 9 = Enhanced Output
10 = S
11 = DBG1 (stats unit only)
12 = BT
13 = DT
2/67
0
0 10000 ms (10 sec)
0 = ASCII Space (0x20)
2/68
1
1 = ASCII Zero (0x30)
0 = Strong Visual Target
2/69
0
1 = Fast Visual Target
0 = No Zeros
2/70
2
1 = One Zero
2 = Stream Zeros
0 = Disabled
2/71
0
1 = Enabled
0 = Disabled
2/72
0
1 = Enabled
2/73
0
0 = Disabled

Report
1 = Enabled
Format D Polled
0 = Disabled
2/26
2/42
2/58
2/74
0
Mode
1 = Enabled
Statistics LOG
0 = Disabled
Messages (stats unit
2/27
2/43
2/59
2/75
0
1 = Enabled
only)
Statistics Record
0 = Disabled
Messages (stats unit
2/28
2/44
2/60
2/76
0
1 = Enabled
only)

Use the settings in this section to configure the serial ports and the messages they transmit.

The Link Configuration settings (2/16, 2/48 and 2/64) have different values and
meanings for the different COM ports. Refer to the Connecting to the COM Ports section for
more detail on the link configurations and their interdependencies.
COM A is an RS485 port and can be configured as a 4wire fullduplex port or as a 2wire
halfduplex port. If COM C is enabled, COM A cannot be configured as a 4wire fullduplex
port.
COM C is always a 2wire halfduplex port. By default it is disabled, but it can be enabled if
COM A is set up for 2wire halfduplex operation.
COM D is a USB port and can be configured with or without flow control.
After a Link Configuration setting is changed, it will immediately report its new value to the
controller, but the setting does not take effect to actually change the link type until the
Process Baud/Link Update command is sent. This is so that the link type does not change
while communicating over the link. The new setting will also take effect after a power cycle
in this case it is unnecessary to send the Process Baud/Link Update command. Refer to
the System subsection in this section for more details on the Process Baud/Link Update
command.

Each COM port has its own Baud Rate setting (2/17, 2/33, 2/49, 2/65) which can be set in
the range from 9600 to 921600. 115200 is the default. Regardless of the baud rate, the
serial port is always configured for 10 bit asynchronous data with 1 start bit, 8 data bits, 1
stop bit and no parity (8N1).
After a Baud Rate setting is changed, it will immediately report its new value to the
controller, but the setting does not take effect to actually change the baud rate until the
Process Baud/Link Update command is sent. This is so that the baud rate does not change
while communicating over the link. The new setting will also take effect after a power cycle
in this case it is unnecessary to send the Process Baud/Link Update command. Refer to
the System subsection in this section for more details on the Process Baud/Link Update
command.

The Stationary Speed Sensor II can transmit speed and status messages out the serial port
in different formats for different applications. The Output Format setting (2/18, 2/34,
2/50 and 2/66 for the four COM ports) selects the format for transmitted messages. Refer
to Appendices A and B for more details on the message contents for different formats.
A halfduplex RS485 port cannot be configured to stream out continuous speed data
because it would never be able to receive a command from the controller over the same pair
31

of wires. For this reason, halfduplex ports are limited to the EE and EA handshaking
protocols described in Section 7 and only send out a speed message when requested (or
polled) by the controller.
A fullduplex port (RS232 or RS485) continuously streams out messages in any format
described in Section 6. It can also respond to EE and D0D4 polling described in Section 7
but not EA polling.

When configured for a streaming message format, the Stationary Speed Sensor II sends a
message each time the radar generates new internal speed measurements about 21 times
per second or every 48 milliseconds. This is the default (and fastest) rate for streaming
messages. If that rate is too fast for a users application, it can be slowed down using the
Message Period setting (2/19, 2/35, 2/51 and 2/67 for the four ports). With a range of 0
to 10,000 milliseconds, a delay of up to 10 seconds can be configured for the time between
the beginning of one message and the next. This feature is only applicable for fullduplex
ports which can stream data.
It is important to note that the sensor only has an opportunity to send a new message at its
internal operating rate of once per 48 ms. That means any value for this setting between 0
and 48 results in a 48 ms period. Any value between 49 and 96 results in a 96 ms period.
Generalizing, whatever actual value is selected for this setting results in messages sent out
at a rate of the next higher multiple of 48 ms.

The Leading Zero Character setting (2/20, 2/36, 2/52 and 2/68 for the four ports) defines
the character used for leading zeros on speeds in ASCII visual speed message formats (A, B,
D0D3 and S). It can be set = 0 for a space character (ASCII 0x20) or = 1 for a zero character
(ASCII 0x30). Examples below show how different numbers would appear on a speed sign
or printout.
Space ASCII spaces are used for leading zero characters
500
50
5

Zero ASCII zeros are used for leading zero characters
500
050
005
000

The Format A Speed setting (2/21, 2/37, 2/53 and 2/69 for the four ports) determines
what speed will be reported in the A Format messages: either the Strong visual target or the
Fast visual target. It only applies when the Output Format setting is for the A Format.

Use the Zeros After Target Loss setting (2/22, 2/38, 2/54 and 2/70 for the four ports) to
configure what, if any, streaming messages are sent when no target is present. After a
target is lost and when no valid speeds are detected, the Stationary Speed Sensor II by
default streams messages with speed values set to zero. As an option, a port can be
configured to stop streaming messages completely after the last valid message until a new
target is acquired. A third option sends one zero speed message after the last valid
message before halting the message stream. This single message might be used to clear a
speed board after the last speed was displayed.
32

Beware of changing the Zeros After Target Loss setting from the default streaming value.
When no target is present and the Stationary Speed Sensor II is not transmitting any serial
data, the link can appear broken or dead.

The D0, D1, D2 and D3 formats have a field for an ASCII direction character. It indicates +
for an approaching target, for a receding target or ? if the direction cannot be
determined. Enable or disable this byte in the message using the Format D Direction
Character setting (2/23, 2/39, 2/55 and 2/71 for the four ports).

When streaming in any of the D0D4 formats, another way to reduce speed message traffic
on the link is to send a message only when the new speed reading is different from the last.
Enable or disable this feature with the Format D Update On Change Only setting (2/24,
2/40, 2/56 and 2/72 for the four ports). When it is enabled and there are no targets, the
Stationary Speed Sensor II does not send out any speed messages, and the link may appear
dead.
To turn on a keepalive signal from the unit, enable the Format D Zero Report setting
(2/25, 2/41, 2/57 and 2/73 for the four ports) to configure it to send a zerospeed message
every 2 seconds when no target is present. These two settings are limited to a port
configured for the D0, D1, D2, D3 or D4 Format.

One last feature that the D0D4 Formats share is that they can operate in polled mode like
the EE Format. When the Format D Polled Mode setting (2/26, 2/42, 2/58 and 2/74 for
the four ports) is enabled, a speed message is only transmitted after the Stationary Speed
Sensor II receives a poll message from the controller. The poll is *P followed by a carriage
return (in hex: 0x2A, 0x50, 0x0D). No messages are automatically streamed out when this
setting is enabled.
Enable this setting only on fullduplex ports. It is only intended as a way to reduce
streamed messages. To poll for a D0D4 format message on a halfduplex port, use EA
polling as described in Section 7.2.

When the stats sensor unit is tracking targets and gathering statistics, enabling the
Statistics LOG Messages setting (2/27, 2/43, 2/59 and 2/75 for the four ports) configures
the sensor to append ASCII strings to the end of standard streaming messages. These
strings identify targets that were lost from tracking in the last radar measurement period
this is the point at which a target is included in the statistics counts.
This feature is especially effective when used in conjunction with the DBG1 streaming
format. The DBG1 format streams out strings of data after each 48 ms processing period for
each target being tracked. Monitoring this data can tell a user how many targets are being
tracked; what their latest, fastest and average speeds are; and how long they have been
tracked. In the streamed data for the period following the loss of one or more targets, LOG
messages will be appended to show the final data for each lost target as it is saved in the
statistics gathering function.
In order to receive all LOG messages, ensure that the Message Period setting = 0 so that the
sensor sends out messages for each 48ms period. If the message period is longer, speed
messages are not sent out each period; LOG messages for skipped periods are not saved
they are lost. In addition, always use a fullduplex, streaming port to monitor LOG
messages. As above, they are not saved up for whenever the controller may poll for a speed
message.

33

Use the Statistics Record Messages setting (2/28, 2/44, 2/60 and 2/76 for the four ports)
on the stats unit to enable raw statistics records to be streamed out a port when they are
generated normally on a 1, 2, 5, 10, 30 or 60 minute period. These messages are only
generated if the survey is configured for External data. Refer to the Traffic Statistics section
for more detail on tracking, gathering and storing statistics data.

8.3 Target Recognition

Setting
Faster Target Tracking
ID
Default
1/13
Available Values
0 = Disabled
1 = Enabled
0 (min) 16 (max)
0 100%
1 650 ms
0 100%
1 650 ms
1 (min) 99 (max)
Sensitivity
1/4
16
Target Acquisition Density
1/55
70
Target Acquisition Span
1/122
500
Target Loss Density
1/62
0
Target Loss Span
1/123
500
Visual Target Strength Sensitivity
1/85
99
Stats Target Strength Sensitivity
1/120
50
1 (min) 99 (max)
(stats unit only)

Before covering the settings used to adjust the target recognition features of the Stationary
Speed Sensor II, a more detailed definition of target is needed. The base sensor unit has
only one type of targets: Visual Targets. The sensor unit with stats identifies two different
types of targets: Visual Targets and Stats Targets.
Visual Targets are the targets that might display on a Your Speed Is sign on the side of the
road. The speed of a target far from the radar/sign and at the distant edge of the radars
range may flicker on the display until it gets close enough to the radar for solid recognition.
Basically, the radar reports what it actually detects in real time for Visual Targets. Strong
targets, fast targets and locked targets reported in speed messages are of the Visual Target
type.
When the sensor with stats is counting targets for statistics, it should count each target only
once. After the radar sees a Stats Target for the first time, it needs to hold on to it until it
completely disappears from the radars view without the target dropping out and
reappearing. For this and other reasons, Stats targets are treated differently in the radar
processing. Last speed, peak speed and average speed reported in statistics messages are of
the Stats Target type.

The Faster Target Tracking setting (1/13) allows acquisition and tracking of a faster
visual target when a slower target has already been acquired as the strong visual target. An
example of a time when this capability is helpful is when a small car is passing a large truck.
The truck is reported as the main target because of its larger size. The car is then reported
as the fast target.

34

Sensitivity (1/4) is the main setting used by the radar affecting target recognition. With a
higher sensitivity, the Stationary Speed Sensor II looks as far away as possible for targets
and gives the unit its highest performance. It is also able to see smaller targets. Use lower
sensitivity for targets closer to the unit and when you want to restrict it from seeing smaller
objects or objects farther out in the background. The value of this setting affects recognition
of both visual targets and stats targets.
The range of values for this setting is 0 through 16. Use 16 for maximum sensitivity and 1
for minimum sensitivity. A sensitivity setting of 0 allows no target acquisition at all.

Standard radar operation reports a target speed when analysis of its most recent data
results in a target meeting the sensitivity requirements outlined above. Once a target is
acquired, it is tracked until it no longer meets those requirements.
The Target Acquisition and Loss settings give more control over the criteria used to acquire
and then lose a target. They affect recognition of both visual and stats targets.
The Target Acquisition Density and Target Acquisition Span settings (1/55 and 1/122)
are used as a pair to affect when the radar acquires a target. The Density value specifies a
percentage (0100), and the Span value specifies a length of time (1650 ms). As an
example, using values of 70% and 500 ms configure a sensor to acquire a target only after it
sees it 70% of the time over any halfsecond period.

The Target Loss Density and Target Loss Span settings (1/62 and 1/123) are used in a
similar way to tell the radar when it should lose a target. For example, values of 0% and
500 ms tell it to hold on to a target until it doesnt see it at all (0% of the time) for a full half
second.

Whereas the Sensitivity setting described above compares the target strength to the
ambient noise from other radar reflections (signal to noise ratio) to declare recognition of a
target, the Target Strength Sensitivity settings can be used to recognize or suppress targets
depending purely on the targets strength. A higher value allows smaller, lower strength
targets to be acquired. A lower value requires the target to be larger/closer before it is
acquired.
The Visual Target Strength Sensitivity setting (1/85) only affects recognition of visual
targets, and the Stats Target Strength Sensitivity setting (1/120) only affects recognition
of stats targets.

8.4 Target Filtering

Setting
ID
Low Speed Threshold
1/7
0
0 322
High Speed Threshold
1/11
200
0 322

Several settings can be used to filter out undesired targets. The first step is to ignore targets
that are not moving in the desired direction. This is accomplished with the Target
35

Direction setting (1/2) as described in the first subsection of this section, Basic
Configuration.

Slow target speeds can be filtered out using the Low Speed Threshold setting (1/7). The
range of values for this setting is 0 through 322. Any targets with a speed slower than this
threshold are ignored. This feature can be helpful when monitoring traffic around slow
moving objects like pedestrians or trees blowing in the wind.
In a like manner, fast target speeds can be filtered out using the High Speed Threshold
setting (1/11) which also has a range of 0322. Targets with speeds higher than this
threshold are also ignored. It is important to set the High Speed Threshold higher than the
Low Speed Threshold or else all targets will be ignored.

8.5 Speed Presentation

Setting
Cosine Angle 1
Cosine Angle 2
ID Default
1/18
0
1/19
0
Available Values
045 degrees (1 increments)
045 degrees (1 increments)
0 10 = 0 10 seconds
Holdover Time
1/88
2
11 = Forever

The internal measurements made by the radar are corrected and/or held after target loss
depending on the settings in this section.

Stationary Speed Sensor IIs measure the most accurate speeds when targets are moving
directly toward or away from them. Unfortunately, it is usually not advisable to mount one
directly in the path of traffic. As with any radar, aiming at an angle results in lower speeds.
At slight angles the error is very small; however at larger angles the error can become
substantial.

36

These low speeds can be automatically corrected by the sensor using the Cosine Angle
settings (1/18 and 1/19). Two settings are provided so two corrections can be made
simultaneously. The two settings are independent and interchangeable. Either one can be
used by itself or with the other as a pair. One cosine angle setting might be used for the
horizontal besidetheroad angle shown in the diagram above. The other might be set for
the vertical overtheroad angle if the Stationary Speed Sensor II is mounted on a pole.
When the aim of the radar is aligned with the targets path, both angles should be set for 0
degrees, and no correction takes place. The range of these settings is 045 degrees.

The Holdover Time setting (1/88) is used to smooth the speed readings during
intermittent dropouts. It only affects visual targets (not stats targets). When the unit is
configured for a streaming message format, a message is transmitted out the COM port for
each radar measurement period every 48ms. The radar returns a speed of zero if it is
unable to determine a valid speed for any given measurement time. When conditions are
noisy or when the target is very small and almost out of range, these missed measurements
(or dropouts) can make the series of speed reports appear erratic or jumpy.
Rather than interjecting dropouts in the series for invalid speeds, the last valid reading can
be repeated (or held over) to provide continuity for noisy, intermittent targets. The
Holdover Time setting can be set for 010 seconds in 1 second increments, or it can be set to
Forever to hold the last speed the radar saw until a new one is acquired.

8.6 Locking Targets

Setting
ID
Default
Available Values
0 = Disabled
Strong Lock Enable
1/15
1
1 = Enabled
0 = Disabled
Fast Lock Enable
1/14
1
1 = Enabled
0 = Release
Strong Lock
1/43
0
1 = Lock
0 = Release
Fast Lock
1/44
0
1 = Lock

While monitoring a targets visual speed, the sensor can lockin the speed at any point in
time while still tracking the changing speed of the target (trackthrough lock). Either the
speed of the strong visual target or the fast visual target can be locked but not both at the
same time. Stats targets cannot be locked. To monitor locked targets, use the B or
Enhanced Output Format which have fields to report the locked speed.

The Strong Lock Enable setting (1/15) disables or enables the locking feature for strong
visual targets. If locking of fast visual targets is desired, in addition to enabling Faster
Target Tracking as described in the Target Recognition subsection of this section, the Fast
Lock Enable setting (1/14) must also be enabled.
37

Lock and release speeds using the Strong Lock (1/43) and Fast Lock (1/44) commands.
The current locked speed, strong or fast, must be released before any other speed can be
locked.

8.7 Realtime Clock

Setting
ID
RTC Calibration Factor
1/106
0x80
0x80 0xC8
RTC Year
1/107
none
2000 2399
RTC Month
1/108
none
1 12
RTC Date
1/109
none
1 31
RTC Hour
1/110
none
00 23
RTC Minute
1/111
none
00 59
RTC Second
1/112
none
00 59
RTC Fractional Second
1/113
none
0 99
RTC Weekday
1/124
none
1 (Monday) 7 (Sunday)

The realtime clock in the sensor has an internal battery and keeps the current time and
date whether the unit is powered up or not. The following settings can be changed or read
to set or get the current time and date:
The RTC Calibration Factor setting (1/106) accepts values between 128 (0x80) and 200
(0xC8). A higher value will speed up the clock and a lower value will slow it down.
The RTC Year setting (1/107) holds a value between 2000 and 2399.
The RTC Month setting (1/108) holds a value between 1 and 12.
The RTC Date setting (1/109) holds the day of month value between 1 and 31.
The RTC Hour setting (1/110) holds a 24 hour clock value between 0 and 23.
The RTC Minute setting (1/111) holds a value between 0 and 59.
The RTC Second setting (1/112) holds a value between 0 and 59.
The RTC Fractional Second setting (1/113) holds a value between 0 and 99 representing 0
to 0.99 seconds.
The RTC Weekday setting (1/124) holds the day of week value between 1 and 7 where
1=Monday and 7=Sunday.

38

8.8 Aux Pin Usage

Setting
Aux Pin Configuration
ID
Default
1/16
Available Values
0 = Disabled
1 = Speed Alarm
2 = Stats Status (stats
unit only)
0 322
Alarm Speed Threshold

1/12
322
Alarm Type (appears under
0 = Over
Basic Configuration for CCTV 1/57
0
1 = Under
sensor)

The Stationary Speed Sensor II can provide an external signal for notification of a condition
or status. Refer to the Connecting the Stationary Speed Sensor II/Auxiliary Relay
Connections section for details on the physical connection of the AUX contacts used.

Use the Aux Pin Configuration setting (1/16) to enable either a speed alarm or a stats
status notification. When configured for Speed Alarm, the AUX relay activates when a visual
strong target is traveling faster or slower than a preset alarm threshold.
When configured for Stats Status (on stats sensors only), the AUX signal can be connected to
an LED to provide a readiness indicator from the unit. As long as the radar transmitter is
off, the AUX contacts are open. When the transmitters is on, the contacts close for 0.5
seconds and open for 4.5 seconds for a slow blink signaling that the unit is monitoring
traffic for stats. As each target is logged the unit performs a quicker sequence of 0.25
seconds closed and 0.25 seconds open.

When the Speed Alarm feature is enabled, use the Alarm Speed Threshold setting (1/12)
to set up the target speed where the speed alarm activates. The range of values for this
setting is 0322. When a strong visual target is traveling faster (or slower) than this
threshold, the state of the AUX contacts changes from an open circuit to a contact closure.
When the target slows down (or speeds up) out of the alarm range, the contact closure
opens again.

Use the Alarm Type setting (1/57) to determine whether the alarm condition is triggered
by a target traveling over or under the alarm speed threshold.

8.9 Traffic Statistics (stats unit only)

Setting
ID
Default
Statistics Monitor
1/9
Minimum Tracking Distance
2/4
200
39
Available Values
0 = Disabled
1 = Enabled
0 500 feet

0 = Disabled
1 = Enabled
0 = Incomplete
Training Status
2/97
0
1 = Complete
1 = Request current
Get Training Data
2/98

status of training data
(read only)
Away Class 1 Threshold
2/99
84
0 99
2/100
68
0 99
2/101
53
0 99
2/102
37
0 99
2/103
0
0 99
Closing Class 1 Threshold
2/104
84
0 99
2/105
68
0 99
2/106
53
0 99
2/107
37
0 99
2/108
0
0 99

The Stationary Speed Sensor II model with stats can count vehicles and store statistics on
their speeds and classifications over time. Most of the user interface for the statistics
functions is provided in the StalkerSTATS PC application, but some functions can be
handled with these settings.

The Statistics Monitor setting (1/9) turns on or off the basic statistics gathering functions.
It must be enabled for statistics to be counted.

The Minimum Tracking Distance setting (2/4) can be used to filter out some shortlived
targets during a survey. An ideal survey location would not have intersecting streets or
driveways along the path of the surveyed vehicles, but sometimes this cannot be avoided.
To keep from counting vehicles that only travel a portion of the survey path by turning onto
or off of the roadway, set the Minimum Tracking Distance for a distance (in feet) that a
target needs to travel to be counted in the survey. The range of settings is 0500 feet with a
default of 200 feet.

One of the qualities of stats targets is their classification: Class 1 (larger targets) through
Class 5 (smaller targets). The sensor determines a targets class based on the amount of
initial transmitted radar energy that bounces off the target and is returned to the sensor.
This returned energy depends not only on the physical size of the target but also the targets
shape, surface topography and physical bearing to the radar. In some cases, a large target
may return less energy than a smaller target. So while target classes may not correlate
exactly to different types of vehicles, Class 1 targets appear relatively larger to the radar
than Class 2 and so on.

The sensor calculates the intensity, in the range 199, of the returned radar signal for each
target it tracks. It then assigns a Class depending on where that intensity falls in the range
of Class Thresholds. The ten thresholds are split into five for Away Class n Threshold
Classification Training
2/96
40

settings (2/99 2/103) and five for Closing Class n Threshold settings (2/104 2/108).
There are separate sets of thresholds for closing vs. away targets because the radar may be
set up on one side of a roadway, and closing targets look different to it than away targets
which travel at more of an angle to the radar. Other installation locations provide similar
differences.

There are default settings for the thresholds, but they may be set to any level by the user, or
the unit may train itself for the range of targets it sees in a particular installation. This is
accomplished by setting up the radar on a survey site and turning on the Classification
Training setting (2/96). The radar will then monitor the next 100 targets it sees, calculate
the intensity range of those targets, and then automatically set the thresholds evenly spaced
within that range. This training gives reasonable assurance that the statistics survey will
provide results with targets spread throughout the class range. Note that if the unit is
configured for only one direction of traffic, Away or Closing, it only tracks 100 targets
moving in that direction. If it is set up for Both directions, it tracks 100 away targets to
determine the Away Thresholds and 100 closing targets for the Closing Thresholds.

As soon as the Classification Training is enabled, the Training Status setting (2/97) is
automatically set to Incomplete. After the training is complete, the Classification Training
setting is automatically disabled, the Training Status is automatically set to Complete, and
the Class Threshold settings are updated with the newly calculated thresholds.

While training is in progress, it is possible to monitor how many of the 100 targets have
been registered and their intensities. After receiving the Get Training Data command
(2/98), the unit responds by sending out an ASCII stream of data: an A followed by the
intensities of the 100 Away targets and then a C followed by the 100 Closing intensities.
The intensities are initially reported as 0 and are then replaced by the intensities of actual
targets as they are tracked.

The training settings are remembered through power cycles, so it is possible to configure
the unit to train and power it down before going out to the survey site. Then, onsite, simply
aim the unit and power it up. It will then automatically start to train as it sees targets. After
completion of training, it then automatically starts to gather statistics based on the trained
classification thresholds. The targets monitored during the training period are not included
in the statistics counts.

41

8.10 System

Setting
Reset Unit
ID
1/84
1 = Request a reset of the unit

0 = No Action
Force Product Defaults
1/74
0
1 = Force Settings
0 = No Update
Process Baud/Link Update 2/3
0
1 = Update
1 = Request the Product ID (read
Get Product ID
1/37

only)
1 = Request the Product Type (read
Get Product Type
1/79

only)
1 = Request the Software Version
Get Software Version
1/81

(read only)
1 = Request the Hardware ID (read
Get Hardware ID
1/82

only)

The Get settings (or commands) in this section are used to query the Stationary Speed
Sensor II for information about itself. The values cannot be changed by the user; they are
constant and depend on the model of the unit and version of software loaded into it.

To reset a unit, send the Reset Unit command (1/84) with a value of 1. This causes the unit
to reset itself after a ten second delay. No settings are changed, but the unit is restarted.

Use the Force Product Defaults command (1/74) to return a unit to a known state. All
settings are reset to the default values as shown in this section.

The Process Baud/Link Update command (2/3) is used after the Link Configuration and
Baud Rate commands as described in the COM Ports subsection in this section. Since both
of those commands change basic link properties, if the sensor acted on them immediately
after receiving them, its response would be in a different baud rate or the link type would
change before the response goes out. The consequences could be worse if a controller tries
to change multiple settings (as happens with the Dashboard demo PC app) with a baud rate
or link type change in the middle of the sequence of commands: the first commands would
go through successfully, but any commands after the baud rate or link type changed would
not.
Once any baud rate or link configuration settings have been changed without actually
affecting the communications link, sending the Process Baud/Link Update command with a
value of 1 makes those changes take effect. On receiving the command, the unit will
immediately reconfigure the port (or ports if more than one COM port is changed) and send
its response in the new baud rate and/or over the new link type. After sending the
command, the PC/controller should expect these changes and reconfigure its own
configuration on its side of the link.
If the user has access to the sensors power and can turn it on and off, use of the Process
Baud/Link Update command is not necessary. After any baud rate or link type settings have
been changed, simply turning the unit off and back on will make the new settings take effect.
42

A Stationary Speed Sensor II responds to a Get Product ID command (1/37) with an ASCII
string containing the product model name and the version of software loaded into it. An
example is Stationary II Ver: 1.1.0.

The response to a Get Product Type command (1/79) is a three byte hexadecimal value
associated with the model of the Stationary Speed Sensor II. The values are:

0x52A200
Stationary II Speed Sensor

0xFEDB0B
Traffic Statistics Sensor

0xDF1AEE
Speed CCTV Sensor

The Get Software Version command (1/81) returns an ASCII string with the loaded
softwares version. e.g. 1.0.0.0

The Get Hardware ID command (1/82) returns a 32byte ASCII string with the internal
Hardware ID unique to each sensor.

9 Configuration Settings Table

All of the settings available for the Stationary Speed Sensor II are listed below in numerical
order of the Setting IDs which are shown in decimal and hexadecimal format.

The Setting Description column shows the setting names. It also has references to the
subsection in Section 8 where the setting is described in detail.

Setting ID
Packet
Setting Description
Type
Dec
Hex
1
1
0x01 Mode
1 Basic Configuration
0x02
Target Direction
0x04
Sensitivity
0x07
Low Speed Threshold
0x09
Statistics Monitor (stats

unit only)
1
1
7
9
3 Target Recognition
4 Target Filtering
9 Traffic Statistics
11
0x0B
High Speed Threshold
12
0x0C
Alarm Speed Threshold
0x0D
Faster Target Tracking
0x0E
Fast Lock Enable
1
1
13
14
4 Target Filtering
8 Aux Pin Usage
6 Locking Targets
43

1
15
0x0F
Strong Lock Enable

6 Locking Targets
16
0x10
Aux Pin Configuration
18
0x12
Cosine Angle 1
0x13
Cosine Angle 2
0x14
Units
0x15
Unit Resolution
0x25
Get Product ID
0x28
OSD Date Time (CCTV unit

only)
0x2A
Transmitter Control
0x2B
Strong Lock
0x2C
Fast Lock
0x37
Target Acquisition Density
0x38
OSD NTSC/PAL (CCTV unit

only)
0x39
Alarm Type
0x3E
Target Loss Density
0x4A
Force Product Defaults
0x4F
Get Product Type
0x51
Get Software Version
0x52
Get Hardware ID
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
19
20
21
37
40
42
43
44
55
56
57
62
74
79
81
82
8 Aux Pin Usage
5 Speed Presentation
10 System
6 Locking Targets
6 Locking Targets
8 Aux Pin Usage
10 System
10 System
10 System
10 System
84
0x54
Reset Unit
85
0x55
Visual Target Strength

Sensitivity
0x58
Holdover Time
0x6A
RTC Calibration Factor
10 System
1
1
88
106
7 Realtime Clock
107
0x6B
RTC Year
108
0x6C
RTC Month
0x6D
RTC Date
109
7 Realtime Clock
7 Realtime Clock
7 Realtime Clock
44

1
110
0x6E
RTC Hour
7 Realtime Clock
111
0x6F
RTC Minute
112
0x70
RTC Second
0x71
RTC Fractional Second
0x78
Stats Target Strength

Sensitivity (stats unit only)
1
1
113
120
7 Realtime Clock
7 Realtime Clock
7 Realtime Clock
122
0x7A
Target Acquisition Span
123
0x7B
Target Loss Span
0x7C
RTC Weekday
0x03
Process Baud/Link Update
0x04
Minimum Tracking Distance

(stats unit only)
0x06
OSD On Screen Alarm

Display (CCTV unit only)
124
7 Realtime Clock
10 System
16
0x10
COM A Link Configuration
17
0x11
COM A Baud Rate
0x12
COM A Output Format
18
2 COM Ports
2 COM Ports
2 COM Ports
19
0x13
COM A Message Period
20
0x14
COM A Leading Zero

Character
2 COM Ports
2 COM Ports
2
2
21
22
0x15
COM A Format A Speed
0x16
COM A Zeros After Target

Loss
0x17
COM A Format D Direction

Character
0x18
COM A Format D Update On

Change Only
0x19
COM A Format D Zero

Report
0x1A
COM A Format D Polled

Mode
2 COM Ports
2 COM Ports
23
2 COM Ports
24
2 COM Ports
25
2 COM Ports
26
2 COM Ports
45

2
27
0x1B
COM A Statistics LOG

Messages (stats unit only)
0x1C
COM A Statistics Record

0x21
COM B Baud Rate
0x22
COM B Output Format
0x23
COM B Message Period
0x24
COM B Leading Zero

Character
0x25
COM B Format A Speed
0x26
COM B Zeros After Target

Loss
2 COM Ports
28
2 COM Ports
2
2
2
2
33
34
35
36
2 COM Ports
2 COM Ports
2 COM Ports
2 COM Ports
2
2
37
38
2 COM Ports
2 COM Ports
39
0x27
COM B Format D Direction

Character
2 COM Ports
40
0x28
COM B Format D Update On

Change Only
2 COM Ports
41
0x29
COM B Format D Zero

Report
0x2A
COM B Format D Polled

Mode
0x2B
COM B Statistics LOG

0x2C
COM B Statistics Record

0x30
COM C Link Configuration
2 COM Ports
42
2 COM Ports
43
2 COM Ports
44
2 COM Ports
48
2 COM Ports
49
0x31
COM C Baud Rate
50
0x32
COM C Output Format
0x33
COM C Message Period
0x34
COM C Leading Zero

Character
2
2
51
52
2 COM Ports
2 COM Ports
2 COM Ports
2 COM Ports
53
0x35
COM C Format A Speed
54
0x36
COM C Zeros After Target

Loss
2 COM Ports
2 COM Ports
46

2
55
0x37
COM C Format D Direction

Character
0x38
COM C Format D Update On

Change Only
0x39
COM C Format D Zero

Report
0x3A
COM C Format D Polled

Mode
0x3B
COM C Statistics LOG

0x3C
COM C Statistics Record

0x40
COM D Link Configuration
0x41
COM D Baud Rate
0x42
COM D Output Format
2 COM Ports
56
2 COM Ports
57
2 COM Ports
58
2 COM Ports
59
2 COM Ports
60
2 COM Ports
2
2
2
64
65
66
2 COM Ports
2 COM Ports
2 COM Ports
67
0x43
COM D Message Period
68
0x44
COM D Leading Zero

Character
0x45
COM D Format A Speed
0x46
COM D Zeros After Target

Loss
0x47
COM D Format D Direction

Character
0x48
COM D Format D Update On

Change Only
0x49
COM D Format D Zero

Report
0x4A
COM D Format D Polled

Mode
0x4B
COM D Statistics LOG

2 COM Ports
2 COM Ports
2
2
69
70
2 COM Ports
2 COM Ports
71
2 COM Ports
72
2 COM Ports
73
2 COM Ports
74
2 COM Ports
75
2 COM Ports
76
0x4C
COM D Statistics Record

2 COM Ports
47

2
96
0x60
Classification Training
(stats unit only)
0x61
Training Status (stats unit

only)
0x62
Get Training Data (stats unit

only)
0x63

(stats unit only)
0x64

(stats unit only)
0x65

(stats unit only)
0x66

(stats unit only)
97
98
99
100
101
102
103
0x67

(stats unit only)
104
0x68

(stats unit only)
0x69

(stats unit only)
0x6A

(stats unit only)
0x6B

(stats unit only)
0x6C

(stats unit only)
105
106
107
108
10 Configuration Protocol

Refer to the chapter on Custom Applications to Control Stationary Speed Sensor IIs for
details on using this protocol to control Stationary Speed Sensor IIs.

Configuration packet format

#
1
2
3
4
5
Description
Start ID
Destination ID
Source ID
Packet Type
Value
0xEF
2 254 (0x02 0xFE) For broadcast: 255 (0xFF)
0x01
0x01 or 0x02
The Payload Length is a 2byte word which is the
48

6
7

Command ID/
Setting ID
8
9
Antenna Number
Configuration Value
10 Checksum (LSB)
number of bytes starting with byte #7 through and

including the last byte before the checksum bytes.
(see above)
Get method: Command ID value = Setting ID in hex
(and byte #9 = 0x00): causes the Speed Sensor to return
the current setting
Change method: Command ID value = Setting ID in hex
(and byte #9 = 0x01): causes the Speed Sensor to select
the next possible setting
Set method: Command ID value = Setting ID in hex +
0x80: causes the Speed Sensor to use the value in byte
#9 as the new configuration setting
Reserved (use 0x00 or 0x01)
Get method: Value = 0x00
Change method: Value = 0x01
Set method: Value = new desired value in hex (for
multibyte values, the LSB is first and is followed by the
more significant bytes in low to high order)
The checksum should equal the 16bit sum of pairs of
bytes in LSB, MSB order starting with byte #1 as the
first LSB through and including the last byte before the
Checksum (in this case, byte #9). In the case of an odd
number of bytes, 0x00 is used as the last MSB value.
(See example below.)
(see above)
11 Checksum (MSB)

The following is an example showing a command to set UNITS to km/h.

# Description
Value
1 Start ID
0xEF
2 Destination ID
0x02
3 Source ID
0x01
4 Packet Type
0x00
5 Payload Length (LSB)
0x03 (length = 0x0003 = 3 bytes)
6 Payload Length (MSB)
0x00
7 Command ID
0x94 = 0x14 (Setting 20) + 0x80 (set method)
8 Antenna Number
0x00
9 Configuration Value
0x01 (km/h)
10 Checksum (LSB)
0x88
11 Checksum (MSB)
0x03
Checksum = 0x0388 (truncated to the low order 2 bytes) = 0x02EF + 0x0001 + 0x0003 +
0x0094 + 0x0001

49
11 Sensor variations
11.1 200088052,53
11.1.1
Summary
These sensors include the following changes to the base sensor (200088000,01):
The electrical connector is moved from the side to the rear of the sensor.
A USB communications port is added. The sensor is a USB slave complaint with USB
2.0 requirements. An external (host) 5 volts must be supplied to the sensor to
operate the USB communications port. This is an additional communication port; no
previously available communication ports were removed.
The AC voltage input was removed to allow for the addition of the USB
communications port.
The external AUX relay function was changed from a 2 line switch closure function
to a single grounded line operation. This is a normally open switch on pin 7 which is
connected to sensor ground when the switch is closed.
11.1.2
Mechanical Description
50

11.1.3
Electrical Connection
The electrical connections on the rear port are as shown here.

Note: The USB operation requires the hosts 5 volts be place on the pin 6. All other sensor
functions will operate normally without this connection.
Pin Number
Wire Color
Primary Function
1
2
3
Brown
Red
Orange
4
5
6
7
8
9
10
11
Yellow
Dark Green
Blue
Violet
Gray
Black
White
Pink
Com D, D+(USB)
Com D, D-(USB)
Com B, RS-232 RX
(From Computer)
Com A, RS-485 RX-, Full Duplex
DC POWER
5 volts (USB only)
RELAY
Com A, RS-485 TX+, Full Duplex
Com A, RS-485 TX-, Full Duplex
Com A, RS-485 RX+, Full Duplex
Com B, RS-232 TX
(To Computer)
12

Light Green
11.1.4
Operation
Secondary Function
Com C, RS-485 T/R-, Half Duplex
Com A, RS-485 T/R+, Half Duplex

Com A, RS-485 T/R-, Half Duplex
Com C, RS-485 T/R+, Half Duplex
GROUND
To use the USB option the USB driver needs to be loaded on the computer the sensor will be
attached to. The driver can be found on the Developers Kit CD or downloaded from the
stalkerrader.com web site. After the driver is installed, anytime the sensor is connected it
will show up on the computer as a standard com port device which can be accessed by any
standard PC comport application.

To use the ACIs Dashboard PC application to configure the sensor through the USB com
port be sure to use version 2.8.3 or newer. The version needs to support Com port D in its
configuration set up.

51

11.2 200088054,55
11.2.1
Summary
A USB Comminations Port was added with a USB 2.0 Type miniB jack connector.
The M12 connector was removed, eliminating the RS485, RS232, and external
trigger capabilities.
The sensor runs off the USB supplied power and external power source is not
needed.

11.2.2
Mechanical description
11.2.3
Electrical connections
The sensor uses a standard USB 2.0 Mini type B jack.

11.2.4
Operation

To use the ACIs Dashboard PC application to configure the sensor through the USB com
port be sure to use version 2.8.3 or newer. The version needs to support Com port D in its
configuration set up.

52

11.3 200100400
11.3.1
Summary
These sensors include the following changes to the base sensor (200088000):
1. The housing was removed including the M12 connector. The connector is replaced
with a molex board to cable connector.
2. The real time clock function has been removed.
3. Data collection flash memory has been removed.
11.3.2
53
54

11.3.3
Electrical Connections
Included with your sensor is a cable (Stalker Radar P/N 155-2461-00) that plugs into the
Sensor that can be wired into the OEM system as required for your particular needs. The
wiring diagram for the cable is shown below.
Pin
1
2
3
4
5
6
7
8
9
10
11
12
11.3.4
Signal
RS-485 receive - (to sensor)
Vcc
External trigger
External trigger
RS-485 transmit + (from sensor)
RS-485 transmit - (from sensor)
Ground
RS-485 receive + (to sensor)
RS-232 transmit (from sensor)
AC input
AC input
RS-232 receive (to sensor)
Wire Color
Brown
Red
Orange
Yellow
Violet
Blue
Green
Gray
White
Black
White/Brown stripe
White/Red stripe
Operation
The operation is identical to the 200088000 base sensor with the exceptions noted in
section.11.3.1

If the sensor is to be mounted in an enclosure or behind a protective lens, make sure that
there is space in front of the lens as specified in the Mechanical Description section above.
The material in front of the lens should be a natural, undyed plastic such as polypropylene
or high density polyethylene. Try to stay away from dyed material especially black as
many black dyes use carbon which will block the radar transmission. If the sensor is
operating poorly, remove it from the enclosure or the lens to compare operation with
nothing in front of it.

Also note: In this configuration the sensor is not FCC certified and will need to be certified
by the end customer when integrated into their product.

55

11.4 200088056
11.4.1
Summary
These sensors include the following changes to the base sensor (200088001):
The electrical connector is moved from the side to the rear of the sensor.
A USB flash memory port is added.
The AC voltage input was removed to allow for the addition of the USB memory
port.
The external AUX relay function was changed from a 2 line switch closure function
11.4.2
56

11.4.3
Electrical Connection
The electrical connections on the rear port are as shown here.

Pin Number
Wire Color
Primary Function
1
2
3
Brown
Red
Orange
4
5
6
7
8
9
10
11
Yellow
Dark Green
Blue
Violet
Gray
Black
White
Pink
12

Light Green
USB memory, D+(USB)

USB memory, D-(USB)
Com B, RS-232 RX
(From Computer)
Com A, RS-485 RX-, Full Duplex
DC POWER
5 volts (USB memory drive only)
RELAY
Com A, RS-485 TX+, Full Duplex
Com A, RS-485 TX-, Full Duplex
Com A, RS-485 RX+, Full Duplex
Com B, RS-232 TX
(To Computer)
GROUND
11.4.4
Operation
Secondary Function
Com C, RS-485 T/R-, Half Duplex
Com A, RS-485 T/R+, Half Duplex

Com A, RS-485 T/R-, Half Duplex
Com C, RS-485 T/R+, Half Duplex
The USB memory option is for use when collecting traffic data only. Then it is only used
when the sensor is configured for External Memory by the survey set up in the PC
application. When the USB memory drive is installed the sensor will copy any traffic data it
has stored in its internal memory to the USB memory device and while it is installed the
sensor will save all new traffic data to the USB memory drive.

57

11.5 200103300,01
11.5.1
Summary
1. The housing was removed including the M12 connector. The connector is replaced
with a molex board to cable connector.
2. The standard 30x32 degree antenna is replaced by a 6x26 degree narrow beam
antenna.
3. The AC voltage input was removed to allow for the addition of the USB
communications port.
4. The external AUX relay function was changed from a 2 line switch closure function
11.5.2
58

11.5.3
Included with your sensor is a cable (Stalker Radar P/N 155-2461-00) that plugs into the
Sensor that can be wired into the OEM system as required for your particular needs. The
wiring diagram for the cable is shown below.
Pin
1
2
3
4
5
6
7
8
9
10
11
12
Signal
Vcc
USB V
External trigger
Ground
USB D+
USB DRS-232 receive (to sensor)

59
Wire Color
Brown
Red
Orange
Yellow
Violet
Blue
Green
Gray
White
Black
White/Brown stripe
White/Red stripe

11.5.4
Operation

If the sensor is to be mounted in an enclosure or behind a protective lens, make sure that
there is space in front of the lens as specified in the Mechanical Description section above.
The material in front of the lens should be a natural, undyed plastic such as polypropylene
or high density polyethylene. Try to stay away from dyed material especially black as
many black dyes use carbon which will block the radar transmission. If the sensor is
operating poorly, remove it from the enclosure or the lens to compare operation with
nothing in front of it.

Also note: In this configuration the sensor is not FCC certified and will need to be certified
by the end customer when integrated into their product.
60

11.6 200103310,11
11.6.1
Summary
These sensors include the following changes to the 200103300,01 sensors:

1. An M12 connector with flex cable and bracket is added.

11.6.2

There are many ways to attach the M12 cable and bracket to the sensor. A few possibilities
are shown below with straight and rightangle cables.
61
62
11.6.3
Pin
1
2
3
4
5
6
7
8
9
10
11
12
11.6.4
Signal
USB D+
USB DRS-232 receive (to sensor)
Vcc
USB V
External trigger
Ground
Operation
The operation is identical to the 200103300,01 sensor.
63
12 FCC Requirements
This device is approved as an intentional radiator under FCC Part 15 with FCC identifier
IBQACMI007.
No additional licensing is required to operate this device.
Operation is subject to the following two conditions:
(1) This device may not cause harmful interference, and
(2) This device must accept any interference received, including interference that may
cause undesired operation.

64
Appendix A OEM 6 x 26 Stationary Speed Sensor II for

Lane Discrimination

Applied Concepts makes several types of radar based speed sensors. Due to the narrow
vertical beam width, the OEM 6 x 26 Stationary Speed Sensor II and the OEM 6 x 26
Traffic Statistics Sensor are specifically well suited for lane discrimination applications.

Sensor Installation

There are many aspects of mounting the Speed Sensor, all of which have an impact on the
behavior, and the reliability of the results. This paper presents basic recommendations for
installation and some of the background reasons behind them. From these descriptions, it is
expected that users can determine how their particular environment impacts the
installation and can make the necessary adjustments.

To begin the explanation of the installation we will describe the main factors involved.
These factors are then expressed using more detailed charts towards the end of this section.

The recommended location of the sensor is above and in the center of the lane to be
monitored. The Sensor should be pointed at a downward slope, towards the center of the
lane. Since it has a 6 beam width in the horizontal direction and a 26 beam width in the
vertical direction, it makes a trapezoidal pattern where it hits the roadway as shown below.

By specifying that the beam width is 6 by 26, we mean that the majority of the power in
the transmitted radar beam is within that pattern. Some of the radars power actually
extends in a wider pattern, but it is weaker outside the 6 x 26 boundaries.

Another thing to note about the rectangular beam is that the 6 dimension is aligned with
the long dimension of the antenna and the 26 dimension is aligned with the short
dimension of the antenna. Although it may seem counterintuitive, the larger the antenna is,
the narrower the beam. For lane discrimination installations, the sensor should be mounted
with its long side parallel to the ground.

The diagram below shows the geometry of the sensor installation. In the side view, the
sensor is mounted at the top of a pole of height H and is tilted down at angle C (for center).
The center of the beam hits the road at a distance RDC (Road Distance Center) from the base of
the pole. The near and far edges of the beam hit the road at distances RDN (Road Distance
Near) and RDF (Road Distance Far). The angles N (Near) and F (Far) are defined by the 26
A-1

vertical beam width of the antenna: N = C13 and F = C+13. The road distance values can
be calculated for a given pole height and mounting angle as follows:
RDC = H * tan C RDF = H * tan F
RDN = H * tan N

The Road Pattern view above shows the size of the trapezoidal area where the beam hits the
road surface. The length L of the pattern is the difference from the far edge to the near
edge; L = RDF RDN. The width of the pattern varies and depends on the distance the beam
travels from the radar to intersect the road. As the signal travels away from the sensor, the
width of the 6 beam increases roughly by the following equation.

Width = 0.1 * Distance

The beam distance for the near edge DN = (H2 + RDN2), so the beam width WN = 0.1 * (H2 +
RDN2). In a like manner, the beam width WC at RDC is 0.1 * (H2 + RDC2), and the beam width
WF at the far end of the pattern is 0.1 * (H2 + RDF2)

A-2

A typical lane width is 11 ft. (3.3m) and is the single most important factor in choosing the
distance between the sensor and the target zone to be monitored. To perform lane
discrimination a majority of the radar signal must be confined to the lane of interest, but
some overlap into the adjacent lanes can be tolerated because of the low probability of a
significant amount of reflective surface from a vehicle in the adjacent lane will be in view.
Some of the effects of allowing the adjacent lanes to be exposed will be compensated for
later when setting up the Target Strength Sensitivity of the sensor and will be explained
later in this paper.

The explanation provided so far provides the theory and math for the calculations. The
following tables define the beam pattern for a number of different pole heights and aiming
angles to give a more practical view of the installation options and resulting beam patterns.

Pole Aiming
Road
Height Angle Distance

Near

H
C
RDN
15
15
15
15
15
15
15

15
15
15
15
15
15
15
15
15
15
15
15
15
15
15
15

45
50
55
60
65
70
75

60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
9.37
11.30
13.51
16.09
19.20
23.10
28.21

16.09
16.66
17.26
17.88
18.52
19.20
19.91
20.65
21.42
22.24
23.10
24.01
24.96
25.98
27.06
28.21
Road
Distance
Center

RDC
15.00
17.88
21.42
25.98
32.17
41.21
55.98

25.98
27.06
28.21
29.44
30.75
32.17
33.69
35.34
37.13
39.08
41.21
43.56
46.17
49.06
52.31
55.98
Road
Beam Pattern Pattern Pattern Cosine
Distance Pattern Width Width Width Angle
Far
Length
Center
Far

Near

RDF
L
WC
W F

WN
24.01
29.44
37.13
49.06
70.57
122.17
429.54
14.63
18.14
23.62
32.98
51.37
99.07
401.33
1.77
1.88
2.02
2.20
2.44
2.75
3.20
2.12
2.33
2.62
3.00
3.55
4.39
5.80
49.06
52.31
55.98
60.16
64.97
70.57
77.17
85.07
94.71
106.73
122.17
142.72
171.45
214.51
286.22
429.54
32.98
35.65
38.73
42.29
46.45
51.37
57.26
64.42
73.28
84.49
99.07
118.71
146.49
188.53
259.16
401.33
2.20
2.24
2.29
2.33
2.38
2.44
2.49
2.55
2.62
2.68
2.75
2.83
2.91
3.00
3.09
3.20
3.00
3.09
3.20
3.30
3.42
3.55
3.69
3.84
4.00
4.19
4.39
4.61
4.85
5.13
5.44
5.80
A-3
2.83
3.30
4.00
5.13
7.21
12.31
42.98

5.13
5.44
5.80
6.20
6.67
7.21
7.86
8.64
9.59
10.78
12.31
14.35
17.21
21.50
28.66
42.98
45
40
35
30
25
20
15
30
29
28
27
26
25
24
23
22
21
20
19
18
17
16
15

Pole Aiming
Road

Near

H
C
RDN
20
20
20
20
20
20
20

20
20
20
20
20
20
20
20
20
20
20
20
20
20
20
20

45
50
55
60
65
70
75

60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
12.50
15.07
18.01
21.45
25.60
30.80
37.61

21.45
22.21
23.01
23.84
24.70
25.60
26.54
27.53
28.56
29.65
30.80
32.01
33.29
34.64
36.08
37.61
Road
Distance
Center

RDC
20.00
23.84
28.56
34.64
42.89
54.95
74.64

34.64
36.08
37.61
39.25
41.01
42.89
44.92
47.12
49.50
52.10
54.95
58.08
61.55
65.42
69.75
74.64
Road
Far
Length
Center
Far

Near

RDF
L
WC
W F

WN
32.01
39.25
49.50
65.42
94.09
162.89
572.73
19.51
24.18
31.49
43.97
68.49
132.09
535.11
2.36
2.50
2.69
2.93
3.25
3.67
4.26
2.83
3.11
3.49
4.00
4.73
5.85
7.73
65.42
69.75
74.64
80.22
86.63
94.09
102.89
113.43
126.28
142.31
162.89
190.29
228.60
286.01
381.62
572.73
43.97
47.54
51.63
56.38
61.93
68.49
76.35
85.90
97.71
112.66
132.09
158.28
195.32
251.37
345.54
535.11
2.93
2.99
3.05
3.11
3.18
3.25
3.32
3.40
3.49
3.58
3.67
3.77
3.88
4.00
4.13
4.26
4.00
4.13
4.26
4.41
4.56
4.73
4.92
5.12
5.34
5.58
5.85
6.14
6.47
6.84
7.26
7.73
A-4
3.77
4.41
5.34
6.84
9.62
16.41
57.31

6.84
7.26
7.73
8.27
8.89
9.62
10.48
11.52
12.78
14.37
16.41
19.13
22.95
28.67
38.21
57.31
45
40
35
30
25
20
15
30
29
28
27
26
25
24
23
22
21
20
19
18
17
16
15

Pole Aiming
Road

Near

H
C
RDN
25
25
25
25
25
25
25

25
25
25
25
25
25
25
25
25
25
25
25
25
25
25
25
45
50
55
60
65
70
75

60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
15.62
18.84
22.51
26.81
32.00
38.50
47.02

26.81
27.77
28.76
29.79
30.87
32.00
33.18
34.41
35.70
37.06
38.50
40.01
41.61
43.30
45.10
47.02
Road
Distance
Center

RDC
25.00
29.79
35.70
43.30
53.61
68.69
93.30

43.30
45.10
47.02
49.07
51.26
53.61
56.15
58.90
61.88
65.13
68.69
72.61
76.94
81.77
87.19
93.30
Road
Far
Length
Center
Far

Near

RDF
L
WC
W F

WN
40.01
49.07
61.88
81.77
117.62
203.61
715.91
24.39
30.23
39.37
54.96
85.62
165.11
668.89
2.95
3.13
3.36
3.67
4.06
4.59
5.33
3.54
3.89
4.36
5.00
5.92
7.31
9.66
81.77
87.19
93.30
100.27
108.29
117.62
128.61
141.78
157.84
177.88
203.61
237.86
285.75
357.52
477.03
715.91
54.96
59.42
64.54
70.48
77.41
85.62
95.44
107.37
122.14
140.82
165.11
197.85
244.14
314.22
431.93
668.89
3.67
3.74
3.81
3.89
3.97
4.06
4.15
4.25
4.36
4.47
4.59
4.72
4.85
5.00
5.16
5.33
5.00
5.16
5.33
5.51
5.70
5.92
6.15
6.40
6.67
6.98
7.31
7.68
8.09
8.55
9.07
9.66
4.72
5.51
6.67
8.55
12.02
20.51
71.63

8.55
9.07
9.66
10.33
11.11
12.02
13.10
14.40
15.98
17.96
20.51
23.92
28.68
35.84
47.77
71.63
45
40
35
30
25
20
15
30
29
28
27
26
25
24
23
22
21
20
19
18
17
16
15

There is one more very important point to make in considering the antenna location. The
antenna should be mounted so that there are no obstacles between the radar and the lane to
be monitored. Even though the beam width is only 6 degrees, some of the radar signal will
exit in much wider beam angles from the antenna. The closer an object is to the antenna the
stronger the signal will be that will be reflected back to the antenna. A very close object,
even outside the 6 degree beam width, can reflect enough energy back to the antenna to
overload the antenna and reduce its sensitivity. When installing the antenna, make sure
there are no obstacles near the front of the antenna.

A-5

Sensor Configuration

There are four configuration registers that are used to customize the Speed Sensor for lane
discrimination. They are the Target Direction, Cosine Angle 1, Target Strength Sensitivity,
and the Holdover Time registers.

Target Direction (configuration ID 1/02)
The available values for the Target Direction setting are Away to monitor receding targets
only, Closing to monitor approaching targets only and Both to monitor targets moving in
either direction. Select the direction of traffic relative to the sensor for the lane to be
monitored. The Both selection should not be used since lanes typically only have one
direction of travel and using the Both setting may add unwanted reporting.

Cosine Angle 1 (configuration ID 1/18)
Radars measure the most accurate speeds when targets are moving directly toward or away
from them. As with any radar, aiming at an angle results in lower readings than the actual
speeds. At slight angles the error is very small; however at larger angles the error can
become substantial.

These low speeds can be corrected using the Cosine Angle settings. The range of values for
the two Cosine Angle settings is 0 45 degrees, in one degree increments.

In the Lane discrimination applications the Cosine Angle ( in the charts above) is the
complementary angle to the aiming angle of the sensor (C in the charts above). For example,
if the sensor is pointing out at a 70 degree angle relative to a vertical pole, then the
complement, or the cosine angle for the sensor is 20 degrees (90 70 = 20).

Target Strength Sensitivity (configuration ID 1/85 or 1/120)
Targets can be suppressed or acquired depending on their signal strength. A higher value
for the Target Strength Sensitivity allows smaller, weaker targets to be acquired. A lower
value requires the target to be larger/stronger before it is acquired. The range of values is
199. For lane discrimination applications we suggest a starting value of 50 for Target
Strength Sensitivity.

The OEM 6 x 26 Stationary Sensor II has just one target strength sensitivity setting, the
Visual Target Strength Sensitivity (ID 1/85). The OEM 6 x 26 Traffic Statistics Sensor has
two: the Visual Target Strength Sensitivity as above and also the Stats Target Strength
Sensitivity (ID 1/120). If the Traffic Statistics Sensor is being used to collect statistics, use
this second setting.

Holdover Time (Configuration ID 1/88)
The Holdover Time sets a time for the last speed measurement to continue to be displayed
after the signal has been lost. This is primarily for applications where the speed is to be
visually displayed and the holdover aids in eliminating display flicker. In lane
discrimination applications the output generally does not go to a visual display and so is not
needed. The Holdover Time is settable from 0 to 10 seconds. For lane discrimination
applications set this register to 0.

A-6

Fine Tuning the Set Up

Every installation should be treated as a unique set up. There are several sources of
variability that may require an installation to be finetuned. These sources of variability
range from differences in the sensitivity and transmit power from one sensor to the next, to
lane width and road gradients of the installation site.

The primary tool for adjusting the performance of the sensor once it is installed is its Target
Strength Sensitivity setting. The larger the sensitivity value stored in the configuration
register, the wider the effective beam width. This will cause the target zone to increase,
moving the near end closer to the sensor and the far end further away from the sensor; the
drawback is the sensor will pick up more traffic in adjacent lanes. If your lanes are wide,
then you can increase your sensitivity a little and have a longer target zone. Conversely, if
the sensor is picking up too much traffic in adjacent lanes then you need to lower the
sensitivity setting; this will also cause the length of the effective target zone to decrease.

A-7

Stalker Stationary Speed Sensor II Technical Manual

Uploaded by

Copyright:

Available Formats

Stalker Stationary Speed Sensor II Technical Manual

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Stalker Stationary Speed Sensor II Technical Manual

Uploaded by

Copyright:

Available Formats

Stalker Stationary Speed Sensor II

Applied Concepts, Inc.