BIC-2300 Overhead Stereo Traffic Sensor Setup Guide 8200

BIC-2300 OVERHEAD STEREO TRAFFIC SENSOR 8200-2689-08, REV. G

SETUP GUIDE 1 of 77

BIC-2300 Overhead Stereo Traffic Sensor

Setup Guide

BIC-2300-25SP, BIC-2300-25RP, BIC-2300-25SN, BIC-2300-25RN, BIC-2300-29SP, BIC-2300-29RP, BIC-2300-29SN, BIC-2300-29RN, BIC-2300-38SP, BIC-2300-38RP, BIC-2300-38SN, BIC-2300-38RN,

BIC-2300-60SP, BIC-2300-60RP, BIC-2300-60SN, BIC-2300-60RN, BIC-2310

© 2019 Sensormatic Electronics, LLC


SETUP GUIDE 2 of 77

Contents

BIC-2300 Overhead Stereo Traffic Sensor ................................................................................................ 1 Contents ..................................................................................................................................................... 2 About the product ....................................................................................................................................... 3

BIC-2310 ............................................................................................................................................... 3 Key features .......................................................................................................................................... 3 EAS enhancement features .................................................................................................................. 3 Data delivery .......................................................................................................................................... 4 Video image ........................................................................................................................................... 4 Tracking ................................................................................................................................................. 5 Reset button .......................................................................................................................................... 6

Safety ......................................................................................................................................................... 8 Installation .................................................................................................................................................. 9

Summary of steps ................................................................................................................................. 9 Step 1: Complete client IP address checklist ...................................................................................... 11 Step 2: Sensor identification ................................................................................................................ 12 Step 3: Date and time setup ................................................................................................................ 13 Step 4: Logger delivery address setup ................................................................................................ 15 Step 5: Sensor calibration ................................................................................................................... 16 Step 6: Reporting zone setup .............................................................................................................. 22 Step 7: Count line setup ...................................................................................................................... 23 Step 8: Proper tracking check ............................................................................................................. 28 Step 9: Filter zone setup ..................................................................................................................... 28 Step 10: Pass and exclude line setup ................................................................................................. 31 Step 11: Data delivery address setup ................................................................................................. 32 Step 12: Sensor validation .................................................................................................................. 33 Step 13 Optional: Device Manager Settings ....................................................................................... 40 Step 14 Optional: Real time data streaming setup .............................................................................. 41 Step 15: Alert Delivery Setup (Optional) ............................................................................................. 42 Step 16: Email Delivery Setup (Optional) ............................................................................................ 44 Step 17: FTP Delivery Setup (Optional) .............................................................................................. 46

Appendix A: Troubleshooting ................................................................................................................... 49 Appendix B: Calibration Features ............................................................................................................ 58 Appendix C: Administration ...................................................................................................................... 60

Importing a Configuration File ............................................................................................................. 60 Exporting a Configuration File ............................................................................................................. 60 Adding Password Protection ............................................................................................................... 60 Server Device Software Upgrade ........................................................................................................ 61 Client Device Software Upload ............................................................................................................ 69

Appendix D: Advanced Features License ................................................................................................ 70 Appendix E: Shopping unit detection ....................................................................................................... 71 Appendix F: Path Linking Feature ............................................................................................................ 73

Using Path Linking .............................................................................................................................. 73 Setting Path Linking ............................................................................................................................ 73 Creating the Master Sensor ................................................................................................................ 74 Adding a Subordinate Smart Device ................................................................................................... 74 Configuring Sensors for Path Linking .................................................................................................. 75 Path Linking Shortcut Menu ................................................................................................................ 77 Notes ................................................................................................................................................... 77


SETUP GUIDE 3 of 77

About the product

The BIC-2300 Overhead Stereo Traffic Sensor uses two cameras and object tracking technology to provide people counts.

BIC-2310

The BIC-2310 is a direct replacement for the BIC-2300, they are identical in form, fit, function and connectivity. You can use a BIC2310 with BIC2300 for stitched scenes, replace a BIC-2300 with a BIC-2310, or replace a BIC-2310 with a BIC-2300. Throughout this guide where you see BIC-2300, you can interchangeably use BIC-2300 or BIC-2310 devices. The Sensormatic part numbers remain unchanged.

Note: The BIC-2310 uses a different firmware version than the BIC-2300. It is not possible to load the incorrect firmware. If you attempt to apply a BIC-2300 firmware file to the BIC-2310 camera, the user interface will recognize the incorrect filename and reject the upgrade request. You must select the proper file for each sensor. Confirm the sensor model by verifying the bottom of the GUI landing page.

CAUTION: Power on the sensor for 15 minutes at the install site before calibrating it. Otherwise, inaccurate people counts may result.

CAUTION: The following is required to run Brickstream 2300 Basic Configuration software.

Microsoft® IE6+ or Mozilla® Firefox® 3+ web browser.

Java Runtime JRE 1.6 update 10 (http://www.java.com) to view live video.

Note: The Path Linking feature has been included in this guide. Please see Appendix F: Path Linking Feature.

Key features

The BIC-2300 Overhead Stereo Traffic Sensor has the following features:

Ability to store metrics at 1, 5, 15, 30, and 60 minute granularities.

Adjusts automatically to environmental changes such as lighting and temperature.

IP addressable, enabling remote management and support, including software upgrades.

No additional in-store devices required for data collection and delivery.

Multiple sensors can be used to widen the coverage, if necessary.

A web-based configurator enables complete configuration and management using standard web browsers, either at the store or remotely over a wide area network (WAN).

Support for oblique views.

Supports scheduled streaming digital video output for remote data validation.

Flash memory stores configuration settings and 80 days of data (one counting zone with one minute granularity) or 20 days of data (six counting zones with one minute granularity).

Real-time data delivery.

Digital I/O and RS-485 interface enables the sensor to integrate with pulse/relay devices and to communicate with a local EAS system.

EAS enhancement features

You can configure the following EAS enhancement features using the Brickstream web-based configurator along with the Sensormatic CE ADS4 Platform Configurator:

Note: For more information on implementing EAS enhancement features, see Overhead Traffic Sensor EAS Enhancement Features Installation Guide, 8200-2689-16 in Install Kit 0352-0542-01.

Directional alarms. This feature eliminates two sources of false alarms:

http://www.java.com/


SETUP GUIDE 4 of 77

Tagged merchandise entering the store from other stores.

People with tagged items walking near the pedestals inside the store.

With this feature the EAS detector must receive a people count from the overhead traffic sensor before it can emit an audio-visual alarm when it detects an EAS tag. You can configure the detector to alarm on tags exiting the store, entering the store, or both.

If the customer requests, you can configure the detector to emit a silent visual alarm, pedestal LEDs flashing, when a tag is nearby, such as on a clothes rack, but a people count is not detected.

Local device manager (LDM). This feature allows LDM functionality using peripheral or client networks so EAS data such as alarm management and system status can be sent to a reporting package such as TrueVUE.

LDM power management. This feature enables the EAS detector to automatically turn on and off to match store operating hours. Power management is scheduled using the overhead traffic sensor.

Traffic-sensor-based power save. This feature enables the EAS detector to turn off if no one approaches its pedestals during a specified amount of time. The overhead traffic sensor will turn the EAS detector on again when it detects a person approaching the pedestals.

Configurator pass-through. This feature allows access to various Sensormatic EAS devices for remote management and diagnostics. The devices it covers include the following:

AMS-9040 EAS Detector Controller



ScanMax Pro EAS Deactivator Controller

AMB-9010-IPS EAS Deactivator Controller

AMK-1000 / AMK-1010 Tag Detacher

IDMK-1000 / IDMK-1010 Tag Detacher

Data delivery

Data collected in real-time from up to six areas of interest (zones) are streamed from the sensor for intra-day reporting and alerting.

Data are simultaneously packaged in XML messages and delivered over the Ethernet to in-store or off-site data center servers over a variety of delivery mechanisms: HTTP/HTTPS, FTP/FTPS, or daily e-mail (SMTP).

XML messages are sent at a configurable time interval of 5, 15, 30, or 60 minutes. The 15-minute time interval selection is illustrated as follows:

Time Data packet sent to remote server

1:15 pm 13:00:00 to 13:14:59 (42 enters, 38 exits)



Delivery packets are stored for up to 10 days on an internal SD card if the sensor is not able to send them to the server.

The stored packets are sent to the server when the connection is re-established.

One off-site server can support many sensors.

Video image

The sensor’s embedded camera creates a video image of the floor with a 4:3 aspect ratio.


SETUP GUIDE 5 of 77

Figure 1. Sensor camera

Tracking

The sensor’s web-based configurator displays a digitized image adjacent to the video image.

Figure 2. Video and digitized images

The digitized image displays the person currently tracked with their foot position located in the center of a colored tracking circle.

For tracking to occur, the height of the sensor must be calibrated, and a person must be in the sensor’s view from head to foot.

Each track is tagged with a unique ID and color so many people can be tracked at once. Tracks are converted to metrics within the sensor.

The sensor can distinguish between desired targets such as adults and undesired targets such as shopping carts, pets, and children.

People tracked will trigger enter and exit counts dependent on their movement and interaction with enter and exit counting lines.


SETUP GUIDE 6 of 77

Figure 3. Tracking area

A Digitized image tracking area

B Center of image

C Feet of person being tracked

Note: Areas outside the tracking area are not recommended for people counting, as false counts can occur.

Reset button

Use the reset button to reset the sensor to the default IP address, reset it to factory defaults, disable the current application, and reset privacy options. The reset function applied depends on how long the button is pressed.

Use a straightened paper clip to press the button.

If you cannot communicate with the sensor, or an unusual LED sequence occurs, or the sensor continuously reboots, complete the following steps:

1. Unplug the sensor.

2. Hold in the reset button, and plug in the sensor.

3. Complete the appropriate reset steps.


SETUP GUIDE 7 of 77

A Reset button access hole

B LED 3

Reset button functions

Reset function Button press duration

Reset sensor IP address to 192.168.1.7 2 seconds until LED 3 turns green. Press again within 10 seconds to confirm selection.

The above plus:

Reset factory defaults

Delete existing zones

Resets license code.

5 seconds until LED 3 turns amber. Press again within 10 seconds to confirm selection.

The above plus:

Disable booting the current application

Sensor will attempt to receive a software update from upgrade.Brickstream. local and 192.168.1.18 via TFTP.

8 seconds until LED 3 turns red. Press again within 10 seconds to confirm selection.

Note: If you upgrade the software accidentally, contact the

manufacturer to have them reactivate the software within the sensor.

Reset privacy options 11 seconds until LED 2 turns amber and LED 3 turns green. Press again within 10 seconds to confirm selection.


SETUP GUIDE 8 of 77

Safety

You must adhere to the following safety instructions:

WARNING: Risk of electric shock. Disconnect all power sources before servicing.

WARNING: Do not install this product in hazardous areas where highly combustible or explosive products are stored or used.

Installation requirements

Intended use: Install this device only as described in this guide.

The installer or contractor must adhere to the following criteria:

Ensure that the electrical work complies with the latest national electrical code, national fire code, and all applicable local codes and ordinances. National or local wiring codes or rules can differ between regions. Adherence to these codes supersedes the instructions in this document.

Coordinate all work with other trades to avoid interference.

Verify the existing site conditions and coordinate with the owner’s representative and appropriate utilities, as required.

Obtain copies of all related plans, specifications, shop drawings, and addenda to schedule and coordinate related work.

Thoroughly review the project to ensure that all work meets or exceeds the aforementioned requirements. Any alleged discrepancies shall be brought to the attention of Sensormatic Electronics.

Cabling

Warning: Risk of electric shock. During the installation, if the device is left unattended, turn off the power or cover high voltage components to prevent unauthorized access to hazardous voltages.

Warning: Risk of electric shock. The AC power can carry 120 VAC or 240 VAC.

Warning: Do not run the power and comm cables in the same conduit or raceway. Building codes require that the power wiring is laid separately from other types of wiring.

Warning: In accordance with the USA National Electric Code and applicable US local codes, a 15 A, or 20 A, two-pole, ganged disconnect device, which also provides short circuit and overload protection, and has a minimum 3-millimeter open circuit clearance, must be installed by a licensed electrician, at a location, readily accessible to the equipment.

For installations in other countries, an electrical outlet, suitable for the voltage and current used in the primary electrical supply input of the equipment, must be already provided or installed by a qualified electrician. At all times, you must follow the National Electric Codes regulations, cable, and fusing requirements applicable for the equipment and type of installation

Caution: The AC power source must be three-wire, and include a ground, 24-hour, un-switched outlet with less than 0.5 VAC between neutral and ground.

Caution: Install pluggable equipment in a position that is near a socket outlet, and easy to access.

Caution: For continued protection against the risk of fire, replace the fuse only with the same fuse type and rating.


SETUP GUIDE 9 of 77

Installation

Summary of steps

This section provides an overview of the installation. Inexperienced users should perform the detailed procedures that follow this overview.

Note: Optional steps are in gray.

Step Description Purpose Details Covered Warnings / Cautions

1 Complete pre-install checklist

Obtain client IP address information

Gather site name, IP address, network mask, default gateway, time sync IP address and port number, data delivery IP address and port number, and AVI capture server IP address

–

2 Sensor identification

Identify installation site and device name

Enter site ID, site name, division ID, and device name

Check middle LED is flashing green

3 Date and time setup

Set time and date Select time zone, time server protocol, and computer port

–

4 Logger delivery address setup

Determine where diagnostic and alert messages are sent

Enter server IP address and computer port, URL, and encryption (if required)

Encryption requires license

5 Sensor calibration

Determines counting accuracy

Enter height, X and Y rotation settings, filtering options, background, and couple counting. Then calibrate and readjust, if necessary.

Inaccurate calibration can decrease count accuracy. Power on the sensor and allow a 15 minute warm up

6 Reporting zone setup

Enables up to six reporting zones to be created

Enter the zone name and external ID for the reporting zone

Must be performed before creating count lines

7 Count line setup

Enables count lines to be drawn

How to draw green enter and blue exit count lines (count lines can be fenced), dots face the traffic direction.

Lines too long or short can cause inaccurate counts, keep away from edge of video image, ensure lines face correctly

8 Proper tracking check

To verify proper tracking How to observe tracks for proper counting

If tracks do not appear on the video image, 3D zoom may have to be increased or decreased

9 Filter zone setup

Helps eliminate false counts from employees, browsing customers, and swinging doors.

Move orange lines to fence sources from which false counts occur. Also, how to delete filter zones.

All tracks must begin and end in the filter zone

10 Pass and exclude line setup

For capturing people passing the store and for excluding certain paths from being counted

How to draw pink pass lines and red exclude lines

–

11 Data delivery address setup

Set data delivery criteria Enter server IP address and computer port, URL, aggregation level, delivery schedule, and encryption (if required)

Encryption requires license

12 Sensor validation

To verify counting accuracy.

Local validation vs. remote validation, AVI setup for remote validation, privacy setup to help prevent unauthorized views

Remote validation requires AVI setup, saved privacy settings can only be removed using the reset button


SETUP GUIDE 10 of 77

Step Description Purpose Details Covered Warnings / Cautions

13 Proxy server setup

Enable remote access to sensor through a firewall

Enter server IP address, computer port, and connection frequency

14 Real time data streaming setup

To receive data in real time at a higher data rate such as once per second

Enter server IP address, computer port, data collection frequency, and delivery protocol

15 Alert delivery setup

Delivers alert messages each time a count line is crossed

Enter server IP address and computer port, URL, inter alert delay time, whether to deliver counts, and delivery protocol

16 Email delivery setup

Enables data to be sent to an email account

Enter recipient, sender, server IP address or hostname, computer port, aggregation level, and delivery time

Test email settings

17 FTP delivery setup

Enables data to be sent to an FTP server

Enter server IP address, computer port, file naming convention, encryption (required), delivery format, delivery schedule, and maximum retries.

Encryption requires license, do not use Microsoft characters and character spacing*

* Do not use spaces and Microsoft reserved characters (/,\,?,&,*,:,|,”,<,>) in file names.



Step 1: Complete client IP address checklist

Note: Before configuring the sensors, complete this checklist.

1. Client IP addresses to be assigned to the sensors:

Site name or number IP address network mask default gateway

2. The time zone for the site is:

3. Site observes daylight savings time (circle one): Yes No

4. Time Synchronization Server IP address is ______.______.______.______

running on port number is ________

5. Data delivery IP address is ______.______.______.______

sending to port number is ________

6. AVI Capture Server IP address is ______.______.______.______



Step 2: Sensor identification

XML metric data includes information about the sensor.

1. Plug the PoE (Power over the Ethernet) injector into the sensor. Allow 25 to 35 seconds for the sensor to boot up.

2. Connect your laptop to the same network as the sensor.

3. In your browser, type the IP address of the sensor into the address bar. Press Enter. The configuration application loads into the browser window.

4. In the sensor’s Web-based configurator, click Basic Settings and then the IP Settings sub-tab. Identification settings appear.

Figure 4. Brickstream 2300 basic configuration

5. Type the Site ID, Site Name, Division ID, Device ID, and Device Name in the appropriate fields. To auto-register the device to a site, the Brickstream Device adapter will attempt to match the Site ID to one in the Operational Database.

6. Click Save to save changes.

Note: If LED 2, the middle LED, is not flashing green when connected to a network, use a cable tester to test the Cat5 cable connecting the sensor to the network. If the cable is functioning and you can connect to the sensor via your laptop, then there is a problem with the configuration of the sensor or the customer’s network.

For troubleshooting, see Appendix A: Troubleshooting.



Step 3: Date and time setup

The sensor can connect to a time synchronization server. This requires a network connection but does not always require Internet access. Time synchronization occurs after a sensor reboot or in 15-minute intervals.

Note: If no access to a time synchronization server, see Manually setting time.

1. In the sensor’s Web-based configurator, click the Basic Settings tab and then the Date and Time Info sub-tab. Date and time settings appear.

Figure 5. Basic configuration date and time

2. Click the Time Zone drop-down menu and select the time zone for the installation site.

3. Click the Time Server Protocol drop-down menu and select the appropriate protocol.

Note: If you do not have “Time Server Protocol” information, contact the customer’s Network Administrator or your Project Manager.

4. In the Time Server field, type the IP address of the server running the Brickstream time server service.

The time server service should be on a server on the same network as the sensor (requires no Internet connection) or on a server that has a public IP address (requires an Internet connection).

The time server service will set the sensor time to UTC time so the time server can run in any time zone.

5. In the Port field, type the port number from which the sensor attempts to get time synchronization.

The time synchronization port and data delivery port can be sent to the same IP address and port if necessary.

The default for SNTP is port 123.

6. Click Sync Now to send a time synchronization request to the IP address and port specified on the Date and Time Info page. A success or failure message displays at the top of the page. Verify that the date and time are correct.

7. Click Save to save changes or Reset to clear the fields.

Note: Refresh refreshes the current time. If you cannot sync to a time server, you can manually enter a time and click Set Time to override current date and time settings.



Manually setting time

If access to a time synchronization server is not possible, complete the following steps to manually set the time:

1. Click the Date and Time Info sub-tab.

2. In the Date field, type the current date.

3. In the Time field, type the current time.

4. Click Set Time to set the time on the sensor to the date and time entered.

5. Click the Time Zone drop-down menu and select the time zone for the installation site.


Note: Refresh refreshes the current time. If you cannot sync to a time server, you can manually enter a time and click Set Time to override current date and time settings.



Step 4: Logger delivery address setup

An application on the server parses the XML log and diagnostic data and writes them to a database or log file. Use the Logging sub-tab to set the IP Address and port to which the XML log and diagnostic data are sent.

1. In the sensor’s Web-based configurator, click the Basic Settings tab and then the Logging sub-tab. Logging settings appear.

Figure 6. Basic configuration logging settings

2. Check the Use Logger Server box.

3. In the IP Address field, type the IP address of the server that will receive data from the sensor.

4. In the Port field, type the port number to which the sensor attempts to deliver XML log and diagnostic data.

5. If you are not directed to change the Enter URL field, leave it set to the default value ‘/’. Otherwise, in this field, type the URL if the device needs to send data to a specific URL in the HTTP POST.

Note: This feature can include a URL in the HTTP POST, thus allowing IT departments to use the same port for multiple devices and filter the traffic by the URL in the HTTP POST.

6. If you have a license to enable encryption, click the Encrypt data drop-down arrow and select Yes. If not, continue.

Note: The SNI Host Name field is not used.

7. Click Test Logger Settings to check settings. Click Save to save changes or Reset to clear the fields.



Step 5: Sensor calibration

To accurately track people, the sensor needs to know its height and tilt with respect to the floor. These parameters are obtained by calibrating the sensor.

CAUTION: Perform calibration correctly. Inaccurate calibration can decrease counting accuracy. See examples in Examples of inaccurate calibration.

CAUTION: Power on the sensor for 15 minutes at the install site before calibrating it. Otherwise, inaccurate people counts may result.

CAUTION: Not removing the protective lens coverings will result in undefined calibration.

1. In the sensor’s Web-based configurator, click the Calibration tab. The Calibration Configuration page appears.

Figure 7. Calibration Configuration

2. Remove the sensor’s protective lens coverings.



3. On the screen under “Calibration”, click the Enable Preview check box. Use the following chart to interpret calibration preview shading.

Color Description

Green Area seen by the sensor as the floor.

Light Blue Area calculated as 10 to 30 cm above the floor.

Blue Area calculated as 30 to 50 cm above the floor.

Yellow Area calculated as 10 to 30 cm below the floor.

Red Area calculated as 30 to 50 cm below the floor.

Pink Area whose height cannot be determined. Do not place the calibration box in this area.

Floor areas within the video image should be shaded primarily green and must be “empty” of objects, especially in the center of the floor.

Numbers in the upper left of the image in step 4 show the percentage of undefined and green pixels.

Shaded areas may change to red or light blue moving out from the center of the image.

Use the following example to assist you in verifying the calibration:

If the color of the floor area is:

Top Bottom Corrective Action

Red Blue Increase X Rotation

Blue Red Decrease X Rotation

Left Right Corrective Action

Blue Red Increase Y Rotation

Red Blue Decrease Y Rotation



On the screen, move the green calibration square over the empty green area to be monitored. The green square must be empty of objects; otherwise, calibration will be inaccurate. Make the square as large and centered as possible. Do not place the green square over pink areas. Pink represents undefined distance, usually on boundaries and walls.

Note: If the green square cannot be moved to an empty area and other sensors are mounted at the same height and tilt that were automatically calibrated, manually input the calibration numbers from these sensors into the Calibration page.

Figure 8. Calibration

A Callibration square

On the Calibration page, look at the height and tilt rotation numbers to make sure that they are reasonable using the following guidelines:

a. Calculated height should be within 20% of actual mounting height.

b. X and Y tilt rotation should be within 10 degrees of visual or actual angle.

4. In the lower-right corner of the screen, click Calculate. After 30 to 60 seconds, the calculated height and X and Y tilt rotation displays. The longer the calculation, the better the calibration.


Note: During calibration, if you need to return to default parameters, click Defaults.

6. Check the sensor calibration. On the screen under Options, do the following:

a. Choose the unit of measure to be displayed, inches or centimeters.

b. Click the Show Height check box.

c. Have a person walk to the center of the calibration square and stand still. The height displayed should be within 5 to 7.5 cm (2 to 3 inches) of a person’s actual height. If the displayed height is not correct, empty the area of people and objects, then move the calibration square to a new area that is not purple (undefined area), Click Calculate to recalibrate the sensor and repeat Steps 6 and 7.



Figure 9. Empty background

7. While the scene is empty of temporary obstructions such as people and ladders, click Empty Background Capture to save the empty background image for reference.

Use empty background only when the sensor powers up; otherwise, the background constantly adapts to the environment.

Note: If auto calibration is unsuccessful, sensor Height can be manually adjusted.

Example: If a 183 cm (72 in.) tall person stands beneath the sensor and the sensor reads 152 cm (60 in.), click Enable Preview and increase the value of the Height setting.

Click the Save button and repeat Step 7 until the measurement is accurate.

8. If calibration is acceptable, click Save to save changes or Reset to clear the fields.

Height and cart filtering

The Calibration tab also contains filtering options that ignore tracks created from shopping carts and

objects below a certain height.

By default, the sensor will count any object that exceeds 120 cm (48 in.) in height. To track shorter objects such as shopping carts, children, and strollers, you can change the Height Filter setting.

Cart filtering

Complete the following steps to configure cart and height filtering:

1. On the screen under Filters, select the Filter Carts check box.

2. Click Save to save changes. The sensor will now filter out all shopping carts.

Height filtering

Complete the following steps to setup height filtering:

1. On the screen under Filters, in the Height Filter field, enter the minimum height that a person must exceed to be counted. Shorter objects may still be tracked but are not counted when they cross count lines.

The default value for this field is 119 cm (47 in.), which means that anything below 120 cm (48 in.) will not be counted.

2. Click Save to save changes. The sensor will now ignore all tracks shorter than the value entered in the Height Filter field.

Additional calibration features

For a complete list of calibration features, see Appendix B: Calibration.

176



Examples of inaccurate calibration

The following scenes occur when calibration was not successful.

Figure 10. Calibration legend

Figure 11. Scene mostly red, increase height of sensor

Figure 12. Scene mostly blue, decrease height of sensor



Figure 13. Scene red to right, blue to left, decrease Y rotation

Figure 14. Scene blue at top, red at bottom, decrease X rotation



Step 6: Reporting zone setup

Before count lines can be drawn, a reporting zone must be created to count for the entrance or exit. If one sensor is to cover multiple entrances and exits, a separate reporting zone must be created for each. One sensor can cover up to six zones before you require an additional software license. To create a reporting zone:

1. In the sensor’s Web-based configurator, click the Counting tab. The Counting Configuration page appears.

Figure 15. Counting configuration

2. Right-click in the white area of the zone list box. A pop-up menu appears. Select New from the pop-up menu. For the zone, type the zone Name (Door) and External ID (Door ID).

Figure 16. Zone list box

Deleting reporting zones

To delete a reporting zone and all count lines and filter zones attached to it, complete the following steps:

1. Click the Counting tab. The Counting Configuration page appears.

2. Verify that the Display All check box is cleared.

3. Right-click on the name of the reporting zone you want to remove. A pop-up menu appears.

4. Select Delete. The reporting zone and all attached lines are deleted.




Step 7: Count line setup

A Blue exit line

B Green enter line

What are count lines?

Count lines are virtual trip wires drawn on the video image where the feet of a person trigger a count.

Green count lines produce enter counts. The green dot shows the direction of travel.

Blue count lines produce exit counts. The blue dot shows the direction of travel.

Count lines cannot be created until assigned to a reporting zone. See Step 6: Reporting zone setup.

When using multiple reporting zones, each zone displays only the count lines assigned to it.

Always point the dots of the count lines away from each other as shown above.

Note: Count lines also display in real-time in the digitized image, although they will look a little different from those seen on the video image.

CAUTION: Count lines cannot be created until assigned to a reporting zone. See Step 6: Reporting zone setup.

CAUTION: When using multiple reporting zones, each zone displays only the count lines assigned to it.

Enter

Exit



Important rules

Where and how you draw count lines on the screen is critical to how well the sensor counts people.

Observe the following rules:

Separate count line configurations are assigned to each reporting zone.

Do not position count lines at the edge of the video image. The sensor requires a person to be visible head-to-toe to track them, and requires enough distance between the person’s feet and the count line to count them.

Keep count lines close together except in small coverage areas.

Position counting lines so that a person is tracked for a minimum of 90 cm (3 ft) before crossing a line.

Fence the count lines together into a U-shape to capture all people entering and exiting. Fencing is highly recommended when no anti-theft pedestals are at the doors.

Figure 17. Fencing

Fencing is not required when anti-theft pedestals are at the door to corral traffic across the count lines.

Always place count lines at the interior and exterior edge of the pedestals.

Try to position the count lines over the pink center circle in the right window, at the center of the tracking area.

Placing the Enter line lower than the Exit line on the screen adds distance between when the person is first tracked by the sensor and when they are counted.

Lines too long can cause under counts. Lines too short can cause over counts.



How to draw count lines

To draw count lines:

1. In the sensor’s web-based configurator, click the Counting tab. The Counting Configuration page appears.

Figure 18. Counting Configuration

2. On the count line toolbar, click the Enter or Exit count line button. Then make sure the Count Once box is selected. See Count once option.

3. On the video image, click and drag to draw the line.

- Drag right to left to draw a line with a downward-pointing dot.

- Drag left to right to draw a line with an upward-pointing dot.

Dots on the count lines must point in the direction of traffic flow for that line.

Note: A slow network may make it hard to draw and move count lines. If this happens, click the Pause button on the Counting screen to stop the video stream before drawing the count lines. Once finished, click Play to restart the live video.

4. Click on a line to select it. Using handles at the ends of the line, you can reverse, move, or delete the line.

Reversing a line: Drag one of the line’s handles to reverse its direction.

Figure 19. Reversing a line



Moving a line: Drag the line, but not by one of its handles.

Figure 20. Moving lines

Deleting enter and exit lines

To delete a count line attached to a reporting zone:


2. Verify that the Display All check box is not selected.

3. Click the reporting zone to which the line is attached. All lines for the selected reporting zone appear.

4. Click the line to be deleted. Square handles appear on each end of the line.

5. Press Delete on your keyboard to remove the line.


Count once option

Right-click on a zone and choose Configure from the pop-up menu. From the Counting Config Parameters window, select the Count Once box to avoid repeatedly counting a person crossing a count line multiple times.

Count Once ON: 0 Enters, 1 Exit Otherwise: 1 Enter, 2 Exits



Count Once ON: 1 Enter, 0 Exits

Otherwise: 2 Enters, 1 Exit

Count Once ON: 1 Exit, 0 Enters Otherwise: 2 Enters, 3 Exits

Shopping unit detection option

Use this option only if directed by the account team or program manager. See Appendix E: Shopping unit detection.

Other features on the count screen

Template button

This button creates three connected enter lines for quick configuration within a count zone. It will also attempt to auto-create matching exit lines, and a filter zone going toward the top or bottom of the screen view, based on the shape the enter lines creates.

Display All check box

If using multiple reporting zones, clicking on each zone name displays only the count lines associated with it. Enabling the Display All check box highlights all zones and displays all count lines associated with them.

The Display All option does not apply to configurations having only a single zone.

Pause button

For diagnostic purposes, use this button to pause the video stream and capture still images of people walking through the monitored area.

Preview button

Click Preview to apply changes to the counting configuration without saving them to memory. The changes take effect until the Reset button is clicked or the sensor reboots, which reverts the configuration to the one last saved.

Save button

Click Save to save changes. The current configuration overwrites the previous one.

Note: If you preview a configuration on one page, navigate to a different page, and save a different parameter, all configurations will be saved to memory, including the one previewed.

For example, if you move a counting line on the Counting Configuration page, click the Preview button, navigate to the AVI Capture page to configure a capture schedule, and click the Save button on the AVI Capture page. This also saves the previewed counting configuration to memory.



Reset button

Click Reset to reset to the last saved configuration.

Zone List box

This box shows the number of reporting zones, with each showing the:

Zone name and External ID (door ID)

Total enters and exits since the sensor was installed

Total enters and exits since the last reboot.

Right-click on a zone for a drop-down menu that has the following selections: New, Delete, Rename, Reset, Configure, and Filter.

Step 8: Proper tracking check

A person is usually tracked when the sensor first detects them from head-to-toe, however sometimes it will start tracking before this.

The right window will be solid white until the sensor tracks a person. Tracks for children shorter than the height filter setting will not be counted.

When a person walks through the video image, a colored tracking circle is displayed in the digitized image. The blob within the circle represents the person’s feet.

Colors are arbitrarily assigned to blobs to differentiate them.

1. In the sensor’s web-based configurator, click the Counting tab. The Counting Configuration page appears.

Figure 21. Counting Configuration

2. Readjust calibration if tracks in the digitized image do not match people observed in the video image, or if no tracking circles appear in the digitized image as people move through the video image.

Step 9: Filter zone setup

A filter zone helps prevent false counts triggered by employees, browsing customers, and doors that swing into the store. Add a filter zone to any reporting zone whenever count lines cannot be positioned next to the door or when anti-theft pedestals are not present to help corral customers. If you are adding a filter zone to a reporting zone, first create count lines.

A filter zone is assigned to a reporting zone and is outlined in orange. Up to six filter zones can be added, one for each reporting zone.

Tracks must start in this zone if they are to be counted as enters.

Tracks must end in this zone if they are to be counted as exits.



Tracks that start outside the zone are not counted, such as when people enter the zone from another part of the store and happen to cross the lines while browsing.

Good filter zone configuration

In the video image below, the filter zone extends from the exit line to the edge of the image to make sure all tracks begin and end in the filter zone.

Figure 22. Good filter zone

A Orange filter zone

Bad filter zone configuration

If the filter zone is too small, tracks entering the store can start outside of the filter zone and tracks leaving the store can end before making it to the filter zone.

Figure 23. Bad filter zone

A Orange filter zone



How to draw a filter zone

To add a filter for an individual zone:

1. In the sensor’s Web-based configurator, click the Counting tab. The Counting Configuration page appears.

2. In the reporting zone field, right-click on the zone name. A pop-up menu appears.

Figure 24. Pop-up menu

3. Select Filter. An orange filter zone appears in the image space.

4. Place the mouse cursor in the middle of the filter zone and click and drag it to cover the area you want.

5. Click the filter zone. Several small orange handles appear.

6. Click and drag each handle to reshape the zone to your specifications.

Note: To move the filter zone one pixel at a time, click the filter zone to select it, and then use the keyboard arrow keys to move it.


Note: A slow network may make it hard to draw and move filter zones. If this happens, click the Pause button on the Counting screen to stop the live video before drawing the count lines. Once finished, click Play to restart the live video.

Deleting filter zones

To delete a filter zone:


2. Verify that the Display All check box is clear.

3. Click the reporting zone to which the filter zone is assigned. All filter zones for the selected reporting zone appear.

4. Click filter zone to be deleted. Square handle appear at the corners of the zone.

5. Press Delete on your keyboard to remove the filter zone.

6. Click Save to save changes or click Reset to clear the fields.



Step 10: Pass and exclude line setup

Pass lines

Use pink pass lines to count people whose direction does not matter. For example, people passing a store front. Do not use pass lines in the same zone with enter or exit lines.

Exclude lines

Use RED exclude lines (C) to prevent certain paths from being counted, such as people exiting the store from an employee only area.

Rule: Once a path crosses an exclude line, the enter or exit line cannot count it.

Rule: One set of exclude lines can be added for each reporting zone.

Figure 25. Red Exclude Line

A Path with exit counted B Path with exit not counted

C Exclude line D Employee door

A. This path’s exit is counted because it doesn’t touch the exclude line before crossing the exit line.

B. This path’s exit is ignored because it crossed the exclude line before crossing the exit line.

Deleting pass and exclude lines

To delete a pass or exclude line attached to a reporting zone:


2. Verify that the Display All box is not checked.

3. Click the reporting zone to which the line is assigned. All lines for the selected reporting zone appear.

4. Click the line to be deleted. Square handles appear on each end of the line.

5. Press Delete on your keyboard to remove the line.


Note: A slow network may make it hard to draw and move pass and exclude lines. If the network is slow, click the Pause button on the Counting screen to stop the live video before drawing the count lines. Once finished, click Play to restart the live video.



Step 11: Data delivery address setup

When setting up a new sensor, first counts can be erroneous. To clear erroneous data before enabling data delivery, type the following into the browser bar:

http://XXX.XXX.XXX.XXX/clearcountdata.cgi XXX is the IP address of the sensor.

The sensor will reboot.

To enable data delivery, complete the following steps:

1. In the sensor’s Web-based configurator, click the Basic Settings tab and then the Data Delivery tab.

Figure 26. Data Delivery

2. Select the Enable Batch Data Streaming check box. The Batch Data Streaming area appears, which allows you to send data to two different servers.

Figure 27. Batch Data Streaming



3. In the IP Address field, type the IP address of the server that will receive data from the sensor.

4. In the Port field, type the port number to which the sensor attempts to deliver data.

5. In the Enter URL field, type /Synchronizer/servlet/BrickstreamServlet. Otherwise leave it

set to the default value ‘/’.

Note: This feature can include a URL in the HTTP POST, thus allowing IT departments to use the same port for multiple devices and filter the traffic by the URL in the HTTP POST. If a Host Name is typed for the SMTP Server field, also enter a valid DNS Server IP address in the IP Settings group on the Network tab.

6. The aggregation level is the period during which data is collected. Click the Aggregation Level list, and select one of the following aggregation levels for the count report: 1, 5, 15, 30, or 60 minute.

7. Click the Delivery Schedule list, and choose when to deliver the data: Immediately, 15 minutes, 30 minutes, or 60 minutes. Metric data are delivered at the aggregation level you select.

8. If you want to encrypt the data and have a license to enable encryption, click the Encrypt data drop-down arrow and select Yes. If not, continue.



Step 12: Sensor validation

Local validation

To ensure a successful validation, walk past count lines in both directions and make sure counts are accurate for approximately 50-100 enters and 50 to 100 exits at varying walking speeds.

The walk-through in high-traffic stores could take as little as 10 minutes or less versus low-traffic stores, where the walk-through could take up to two hours.

Make sure that people completely leave the video image.

For multi-sensor doors, walk through where the count lines join and test for gaps and overlap. See Count Line Issues.

Do not count “near misses”.

Figure 28. Count normal customer behavior

X X

X X X X



Figure 29. Count sneaky customer behavior

Figure 30. Do not count near misses

Remote validation

Remote validation is strongly recommended. Use it to send compressed video .DAT files recorded by the sensor to a remote site for validation.

A team at the remote site does the following:

Carefully reviews the video and manually counts enters and exits.

Compares manual counts to counts generated by the sensor.

This process results in a report that shows the sensor counting accuracy.

AVI capture screen

You can capture a video stream from the sensor to onboard memory using a .DAT file format.

A .DAT file contains one AVI file plus several data files compressed in a proprietary format that only a Brickstream application can extract. Only after the AVI is extracted from the .DAT file can it be opened using a Windows media player, and only certain media players can properly read multiple video streams. For example, the standard Windows Media Player cannot render all of the streams encoded in a validation AVI file.

Once the capture is complete, the sensor can be configured to send the files back to a server via FTP either immediately or during a specified time window.

Once the .DAT file transfers to the server, run it through special software to create the .AVI and .CSV files.

Before you can use AVI capture, an FTP server must be set up on the customer network or the internet to receive the .DAT files.

1. In the sensor’s Web-based configurator, click the AVI Capture tab and then the Schedule sub-tab. The AVI Configuration page appears.

This page enables setup of a predetermined schedule or manual setting that includes AVI file start and end times, AVI settings, and the capture mode.

xx x

xxx x

x



Figure 31. Brickstream 2300 AVI Configuration

Note: To ensure that count lines are properly configured for each sensor, capture AVI files for a one to two hour period. Schedule AVI captures during store open hours, preferably during a medium to high traffic time period.

2. Set the Start Date, Start Time, End Date, and End Time in the Schedule tab.

3. If desired, change Compression and Frequency values.

Compression affects the quality of AVI capture (100=highest, 1=lowest). The higher the compression, the lower the quality.

Frequency affects how often a frame of video is captured (1000 equals 1 frame per second). One frame is desired. Less than that will cause people to be missed.

4. Select the Validation 240x180 option button from the Capture Mode group.


6. You can click the Select Schedule list at the top of the screen to schedule a second and third AVI, if desired. An AVI file can be viewed using any windows media viewer that supports AVI files.

Note: AVI schedule 1, 2, and 3 cannot be set with overlapping time periods.

AVI delivery

To bring up FTP settings:

1. In the sensor’s Web-based configurator, click the AVI Capture tab and then the Delivery sub-tab.



Figure 32. FTP settings

2. Click to select either Timed or Immediate data delivery.

Note: An AVI cannot be captured while the sensor is transmitting another. If back-to-back AVI captures are required, set delivery to “Timed” and chose a distant delivery window to ensure that the sensor does not transfer the first AVI until the second AVI has been captured. Otherwise, the second AVI will not record.

Before scheduling an AVI, verify the sensor is time synchronized or has had the date/time properly set using the manual method. If the date/time is not correct, the AVI will not capture as intended.

Timed: The sensor attempts to transfer all waiting AVI captures created using the Start Time and End Time fields. Use 24-hour time format, 00:00-23:59, for both fields.

In the Start Time field, type the start time for the FTP delivery. In the End Time field, type the end time for the FTP delivery.

Immediate: The sensor attempts to transfer the .AVI captures as soon as the capture period ends.

3. In the FTP Server field, type the IP Address of the computer running the FTP server.

4. In the Port field, type the FTP port, typically 21 by default.

5. In the User Name field, type the user name for the FTP server.

6. In the Password and Confirm Password fields, type the password for the FTP server.



8. Click Test FTP Settings at the bottom of the screen. Doing so will connect to the FTP server and upload a small test file, returning success or failure as appropriate.



Managing and checking the status of AVI .DAT files

1. In the sensor’s Web-based configurator, click the AVI Capture tab and then the Status sub-tab. The AVI

File Status screen appears.

This screen allows you to check the status of the last six AVI captures. It also allows you to abort or resend captures and DAT files currently in progress or waiting to be transferred.

Once a capture is aborted, flash memory can be overwritten by future AVI captures.

The Resend feature allows you to resend DAT files that have already been transferred or aborted.

Figure 33. Brickstream 2300 AVI configuration

2. Click the Select an Action drop-down arrow and select either Resend or Abort.

3. Select a capture from the table captures to resend or abort, then select the check box in the appropriate row to select the DAT files.

4. Click Submit to complete the action.

If you selected Resend, the Upload Status changes to either Ready or In Progress.

If you selected Abort, the Upload Status changes to either Transfer Abort Requested or

Transfer Aborted.

“Streaming” section: The streaming feature streams .DAT files aggregated by the hour to the video console service. If the network goes down, the device stores up to six hours of data and then attempts to send it all back out when the network comes back up.

Privacy options

Privacy options mask live video image streams to prevent unauthorized viewing of AVI captures.

Note: This option requires a license key. See Appendix D: Advanced Features License.

1. In the sensor’s Web-based configurator, click the Privacy tab to access privacy options.

Figure 34. Brickstream 2300 Privacy Settings



2. To disable AVI captures, select No for the Enabled option button in the AVI Capture group.

3. To apply a privacy option to all video streams, select Yes for Enabled? in the Video Overlay area.

4. From the Video Overlay list, select the type of privacy option.

To preview a privacy option without making it permanent complete the following steps:

5. Click Preview to temporarily apply the privacy option. You can preview each option from the Counting tab.

6. Exit Preview by selecting No for Enabled? in the Video Overlay area, then click Save.

To make a privacy option permanent, click Save to save changes or click Reset to clear the fields.

Note: Saved privacy settings can only be removed by using the reset button which will reset the sensor to factory defaults. See Reset button.

Figure 35. Height image overlay

Figure 36. Height image overlay 4-bit



Figure 37. Edge overlay

Figure 38. 4-bit grayscale



Step 13 Optional: Device Manager Settings

The Device Manager Settings option allows remote access to the sensor over networks that provide only out-bound connections, such as those that have a proxy server. The project manager or network administrator should inform you if you need this option.

Complete the following steps to configure the sensor to communicate via a proxy server:

1. In the sensor’s web-based configurator, click the Basic Settings tab, then the Device Manager Settings tab. Device manager settings appear.

Figure 39. Device manager settings

2. Check the Connect to Device Manager for Remote Administration box. The fields become active.

3. In the IP Address field, type the IP Address or hostname of the server running the Brickstream 2300

Proxy Server.

4. In the Port field, type the port number used for the /c: parameter when you started the Brickstream 2300

Proxy Server or use the port number provided to you by your network administrator. The default value is 5000. Sensormatic uses 3040.

5. In the Connect Frequency field, type the number of milliseconds between connection attempts from the sensor to the proxy server. The default value is 10,000.

6. Click Test Device Manager Settings to check settings. Click Save to save changes or click Reset to clear the fields.



Step 14 Optional: Real time data streaming setup

Real time data streaming is used when you desire to receive data in real time at a higher data rate such as once per second.

1. In the sensor’s Web-based configurator, click the Basic Settings tab and then the Data Delivery sub-tab.

2. Click the Real Time Data Streaming button. Real time data streaming settings appear.

Figure 40. Data streaming

3. Check the Enable Real-Time Data Streaming box. The fields become active.

4. In the IP Address field, type the IP address or the hostname of the server.

5. In the Port field, type the port number.

6. In the Frequency field, type the frequency, in milliseconds, with which data is to be updated.

7. Click the Delivery Protocol drop-down menu and select the desired protocol.

Option Description

VLI Sends alert as plain text with a variable length indicator (VLI) at the beginning of the message.

HTTP Post Content Sends a HTTP POST to the URL specified in the Enter URL field.

TCP The TCP data delivery method is compatible with the AXIS camera alert delivery message format.

HTTP Sends an HTTP GET to the URL specified in the Enter URL field. The specific page request is defined on the Counting page.




Step 15 Optional: Alert delivery setup

If you are not using alert delivery, skip this step.

The sensor can be set to deliver individual alert messages when a count line is crossed. This alert is typically used two ways:

To integrate the sensor with counting systems that use a pulse system to aggregate counts from sensors.

To setup tripwire logic in which the sensor sends an alert when count lines are crossed.


5. Click the Alert Delivery Data Streaming button. Alert Delivery Data Streaming settings appear.

Figure 41. Alert Delivery Data Streaming

6. Check the Enable Alert Delivery box.

7. In the IP Address field, type the IP address of the server that will receive alerts from the sensor.

8. In the Port field, type the port number to which the sensor attempts to deliver alerts.

9. If not directed to change the Enter URL field, leave it set to the default value /. Otherwise, in this field,

type the URL if the device needs to send data to a specific URL in the HTTP POST.

Note: This feature can include a URL in the HTTP POST. This allows IT departments to use the same port for multiple devices and filter the traffic by the URL in the HTTP POST.

7. In the Inter Alert Delay Time field, type the number of milliseconds the alert system delays between sending consecutive alerts.

Use this threshold when multiple people cross the count lines simultaneously or close together.

The sensor buffers and sends each alert when the delay time expires. Accepted values are from 0 to 30,000 milliseconds.

8. From the Deliver Counts drop-down menu, select Yes or No for whether the alert message should contain the total enter and/or exit counts since the last reboot. The number is not the daily count total.

9. From the Delivery Protocol list, select the desired protocol.



Option Description

VLI Sends alert as plain text with a variable length indicator (VLI) at the beginning of the message.

HTTP Post Content Sends an HTTP POST to the URL specified in the Enter URL field.

TCP The TCP data delivery method is compatible with the AXIS camera alert delivery message format.

HTTP Sends an HTTP GET to the URL specified in the Enter URL field. The specific page request is defined on the Counting page.


Changing the format and type of alert sent by the sensor

After creating count lines, complete the following steps to configure the alert message sent from the sensor:

1. Click the Counting tab.

2. Right-click the row of the zone for which you want to send alerts and select Configure. The Counting Config Parameters pop-up box appears.

3. In the Alert Delivery area, check the Enter and/or Exit boxes to deliver alerts for enter and/or exit counts.

4. Type the text label to be included in the alert. If you select VLI or TCP streaming, you send enter and exit counts, and you type FrontDoor in the text box, the alert message will include your text label and the enter/exit counts since the last reboot. For example, ‘FrontDoor,30,39’ where 30 is the enter count and 39 is the exit count.

Note: If you select HTTP Post Data as the alert delivery type, the device will perform an HTTP POST when an alert is triggered. The text entered into the text box will be delivered in the content of the HTTP POST.

If you select HTTP as the alert delivery type, the device will perform an HTTP GET when an alert is triggered and the text entered into the text box will be delivered in the content of the HTTP GET.




Step 16 Optional: Email Delivery setup

If you are not using email delivery, skip this step.

This option allows aggregated daily metric data to be sent automatically to an email account.


2. Click the Email Delivery button. Email Delivery settings appear.

Figure 42. Email Delivery

3. Check the Enable Email Delivery box.

4. In the Recipient field, type the recipient’s email address.

5. In the Sender field, type the sender’s email.

Note: Both the Recipient and Sender field must contain a valid email address on the SMTP server.

6. In the SMTP Server field, type the IP Address or Host Name of the SMTP Server.

Note: If you type a Host Name for the SMTP Server field, also enter a valid DNS server IP address in the IP Settings area on the Network tab.



7. In the Port field, type the port number used by the server.

Note: If the SMTP server does not require authentication, skip the next step.

8. If the SMTP server requires an authentication password, check the SMTP Server requires Authentication box. The User Name and Password fields become active.

In the User Name field, type the user name for the SMTP Server.

In the Password field, type the password for your SMTP Server.

9. Click the Aggregation Level drop-down menu and select an aggregation level for the count report email: 1, 5, 15, 30, or 60 minute, or daily. The aggregation level is the period during which data is collected.

Note: The email aggregation level controls how often the data is rolled up into a record. For example, if a 60-minute aggregation level is selected, then there will be 24 records in each daily email which show the data for each hour.

If daily is selected, the email will contain a single enter and exit count for the previous 24-hour period.

10. In the Delivery Time field, type the time in 24-hour notation when the sensor sends the email.

The delivery time specifies when the email is to be sent out to the listed recipient. Multiple addresses are not supported.

The aggregate email contains data from midnight to midnight during the previous calendar day. For example, if the delivery time is 18:00, the sensor sends the count data for the previous day at 6 PM every day.

11. Click Save to save changes or click Reset to clear the fields. If Save was clicked, a confirmation message appears. Click Yes to save your changes. A message appears at the top of the page.

12. Click Test Email Settings to send a test email to the address entered for the recipient. A message appears to inform you that the email was successfully sent.

Note: If you receive an error message, see Appendix A: Troubleshooting.

Note: To test the email configuration, have the FST installer temporarily use their own email address as the recipient.



Step 17 Optional: FTP Delivery setup

If you are not using FTP delivery, skip this step.

The sensor can automatically deliver metric files to an FTP server hourly or daily. When FTP delivery is selected, the sensor first attempts to use passive FTP. If the delivery fails, the device will then attempt to use active FTP.

Note: When using active FTP, the connection attempts to use the IP address of sensor and the full port range to establish a connection unless other options have been selected in the Active FTP area in the FTP Delivery options.


Figure 43. Data Delivery

2. Click the FTP Delivery button. FTP Delivery settings appear.

Figure 44. FTP Delivery settings

In the FTP Delivery group:

1. Check the Enable FTP Delivery box.

2. In the FTP Server field, type the FTP Server address.

3. In the Port field, type the number of the FTP port to be used, typically 21.

4. In the File Naming Convention field, select the naming convention for the data files. Chose several variables from the sensor by typing a # followed by the one letter variable.

Characters not immediately preceded by a # will be included in the file name as normal text.



CAUTION: Spaces and Microsoft Windows reserved characters (/,\,?,&,*,:,|,”,<,>) in file names is prohibited. Their use will corrupt the configuration and reboot the sensor to default settings.

The recommended naming convention for Sensormatic Hosted reporting is:

BRK.PCNT.#S.#D.#T.#M.dat, where:

Variable Definition

#S Inserts the Site Name from the IP Settings sub-tab on the Basic Settings tab.

#I Inserts the Site ID from the IP Settings sub-tab on the Basic Settings tab.

#D Inserts the Date of the data contained in the sent data file formatted YYMMDD.

#T Inserts the Time of the last data bucket included in the sent data file formatted HHMMSS.

#M Inserts the MAC address of the Brickstream device sending the data file formatted XX-XX-XX-XX-XX-XX.

Example configurations: Assume the site name is set to Grocery1 and the site ID is set to 987.

FTP File Naming Convention Field Resulting File Name

#S.PCNT.#I.#D.#T.#M.dat Grocery1.PCNT.987.090226.140000.00-b0-9d-70-01-05.dat

#S_#I_#T Grocery_987_140000

countdata-#S-#I-#D#T.txt countdata-Grocery1-987-090226140000.txt

#T#D_#M.csv 140000090226_00-b0-9d-70-01-05.csv

5. Click the Use FTPS list, and select No. Select YES to encrypt the data. An encryption license is required.


In the Server Authentication group:

1. In the Username field, type the FTP user name that will be used to log into the FTP server.

2. In the Password field, type the password for the username.

3. In the Directory field, type the directory in which the FTP files are to arrive. If this field is left blank, files are delivered to the FTP root directory for the user.

In the FTP Data Application group:

1. Click the Aggregation Level list, and select the level the metric data are to be stored in the files. The sensor can store data in intervals of 5, 15, 30, and 60 minutes.

Note: The recommended aggregation is a 60 minute interval, with a maximum interval of 15 minutes. Use 5 minutes only for testing purposes. In the next step, set the delivery method to Pipe Delimited.

2. Click the Delivery Format list and select the format for the data files sent over FTP. There are two options: Pipe Delimited and XML.

The Pipe Delimited format sends data for each report zone with the relevant information separated by a pipe character, |.

The XML format sends metric data in an XML file similar to the XML packets that are sent out using the Batch Data Streaming option.

3. Click the Delivery Schedule drop-down menu and select the frequency at which the FTP file is delivered. The FTP file can be delivered each hour or delivered once daily at a scheduled time.

4. If Daily was selected in the previous step, type a delivery time in the Delivery Time field. The Delivery Time should be entered in 24 hour notation (00:00-23:59).



5. In the Maximum Retries field, type the maximum number of times that the sensor should attempt to connect to the FTP server to send the files in the case of a failure.

Note: If the Maximum Retries field is set to zero, the sensor will retry indefinitely until it successfully sends the file.

6. In the Retry Interval field, type the amount of time, in seconds, the sensor waits before attempting to reconnect to the FTP server. This value can range from 1 to 599 seconds.

In the Active FTP group:

1. Check the Port Range box if you are using active FTP and you want to limit the port range used for connections.

2. In the Lowest Port and Highest Port fields, type the port range.

3. Check the External IP Override box and type the IP address to pass an IP address that is different t the sensor IP address out to the Firewall and FTP server.

4. Click Test FTP Settings to verify that the sensor can connect to the FTP server.


Troubleshooting FTP Connections

The following errors may be encountered when configuring the FTP delivery options:

Error Cause

Failed to connect:36 Incorrect Server IP Address

Failed to connect 64 Incorrect Port Number

Failed to connect 530 password not accepted Incorrect Username and/or Password



Appendix A: Troubleshooting

This section covers:

Power issues

Calibration issues

Counting issues

Count line issues

Communication issues

Email issues

Power Issues - red power LED not lit

PoE device Make sure the PoE injector is plugged into the sensor and wall outlet. Make sure there is power to the outlet. If there is still no power, replace the sensor.

Cables Make sure the Cat5 cables are properly plugged into each sensor’s in and out ports.

Calibration Issues

Improper calibration Make sure an empty traffic background was captured during calibration. The sensor assumes that all people are walking on either a flat or evenly sloped surface.

Rotation Make sure the sensor’s rotation is properly aligned with the floor. The sensor assumes that people are walking on either a flat or evenly sloped surface.

Counting Issues

Orientation Make sure the sensor’s network ports face the entrance.

Mounting height

Make sure multiple sensors are properly spaced apart and at the correct distance away from the entrance for the desired coverage.

Multiple sensors

Make sure multiple sensors are properly spaced apart and at the correct distance away from the entrance for the desired coverage.

Visual obstacles

- Protective lens coverings. Make sure the protective covering is removed from each lens.

- Translucent material: Make sure the sensor is not tracking through a material such as glass or plastic.

- Lenses: Make sure the sensor’s lenses are not dirty or scratched. A damaged lens could appear as a calibration failure.

- Blocked field-of-view: Make sure the video image is free of obstacles such as signs.

Count line issues

See “Count Line Issues” following.



Count Line Issues

On the Counting Configuration screen, use the Pause Video Stream button when encountering a slow network to make drawing count lines and filter zones easier.

Note: A reporting zone must be created BEFORE a count line or filter zone can be drawn.

Note: The sensor does not count individuals who:

Travel through RED exclude line and then travel through either an “enter” or “exit” line.

Do not meet the Height Filter setting.

If the system under counts:

Count lines too close to the edge of the video image

Position counting lines so that a person is tracked for a minimum of 90cm (3ft) before crossing a line.

Count lines point the correct way

The dot on the GREEN “enter” line must point away from the entrance. The dot on the BLUE “exit” line must point toward the exit.

Count lines are far enough from the entrance for target acquisition

In general, keep count lines away from the edge of the video image.

Apply fencing Fence the count lines if necessary to eliminate coverage gaps.

Count lines join seamlessly If using multiple sensors, make sure count lines join seamlessly with no gaps.

If the system over counts

Count lines too close together

Make sure count lines are not so close that a browsing customer can cross both lines multiple times by only moving across a small area.

Apply a filter zone Use a filter zone to prevent unwanted counting of people, such as employees and browsing shoppers.

Check pass and exclude lines

Make sure pass and exclude count lines are used properly, and that the Count Once option is enabled.



Incorrect Count Line Examples

Incorrectly positioned count lines can affect counting accuracy.

Count lines pointing the same direction: each exit cancels out each enter.

Figure 45. Exit line pointing the wrong way, enter not counted

Figure 46. Exit line pointing the wrong way, exit not counted

Count lines set too close to the door: people are not tracked because their path starts too late.

Figure 47. Count lines too close to the door

xx

System: 1 Enter, 1 ExitActual: 0 Enters, 1 Exit

Same Direction: BAD!

Store Exterior

Store Interior

xx

System: 1 Enter, 1 ExitActual: 0 Enters, 1 Exit


Store Exterior

Store Interior

System: 0 Enters, 0 ExitsActual: 0 Enters, 1 Exit


Store Exterior

Store Interior

System: 0 Enters, 0 ExitsActual: 0 Enters, 1 Exit


Store Exterior

Store Interior



Count lines set too far from the door: people can slip by the count lines.

Figure 48. Count lines too far from the door

Fencing keeps people from slipping past the count lines. See Fencing count lines results in cross-traffic counts.

Wide doorway gap problem

A wide doorway needs two sensors to cover it with their fields-of-view overlapping. The count lines should join seamlessly with no gaps or overlap.

Figure 49. Wide doorway fields

When the count lines are not joined seamlessly, under counts and over counts can occur.

Area of overlap between two sensors

xxxx



Figure 50. Gap and overlap between two sensors

A Entrance path, counted twice due to line overlap

B Area of overlap between two sensors

C Exit path, exit not counted due to a line gap

Note: Use the digitized image in both sensors to avoid gaps and overlap. This provides a common

reference point in both sensors.

Ideally, have someone stand directly in the center of overlap area. Then in the right window, draw the line to the center of their blob. Without them moving, repeat for the second sensor. If doing this yourself, mark the floor with tape to ensure that you are always standing in the same spot.

Figure 51. Sensor views

A Sensor 1 B Sensor 2

C Video view D Floor plan view

When the count lines are properly positioned, clicking the Save button to save changes.

Fencing count lines results in cross-traffic counts

A filter zone eliminates false triggers like in-store traffic, door openers, and greeters. To add a filter to the counting zone, See Step 9: Filter Zone Setup on page 28.

Notes:

All paths must START within the filter zone to be counted as an “enter”.

All paths must END within the filter zone to be counted as an “exit”.



Communication issues

(LED 2 flashing amber when connected to a network)

Cables Check that Cat5 cables are plugged into the correct ports on the sensor. Also test cables for broken wires. Most communication issues are cable related.

Cable distance Make sure cable distance from the sensor to the computer room does not exceed 100m (330ft).

IP address issues - Unique IP address: Make sure a unique IP address was set for each

sensor. It is recommended to use 192.168.1.7 (default) for sensor 1, 192.168.1.8 for sensor 2, and 192.168.1.9 for sensor 3.

- Changing an IP address: If you changed the IP address on a sensor and clicked Save, connection to that sensor will be lost for several

seconds while the sensor sets itself with the new IP Address. Type the new IP address into the address bar of the browser and press Enter to reload the application.

- IP assigned to a new subnet: If the IP was assigned to a new subnet,

connection to the sensor will be lost until the sensor is connected to the assigned subnet or until the PC Network settings are modified to include the new subnet.

“Data Delivery” and “Time Sync” addresses/ ports

Confirm that these addresses/ports are configured correctly.

Email Issues

If the sensor has a problem sending the test email, you will get one of several error messages. This section shows the possible error messages and describes their most common causes and resolutions.

Error Message 1 - Submission Error

Figure 52. Error message 1

Description: This message indicates that the sensor attempted to connect to the mail server but was rejected because it did not have access permission.

Possible Cause: Your SMTP Server requires Authentication (a User Name and Password) in order for the sensor to connect to the mail system.

Resolution:

1. Contact the Mail System Administrator to obtain the SMTP user name and password for the email address listed in the From field.

2. Access the sensor’s Web-based configurator.

3. Click Configure from the application menu. This sets the application to configuration mode.

4. Click the Data Delivery tab. The email data delivery settings appear.

5. Check the My Outgoing SMTP Server requires Authentication box. The User Name and Password fields become active.

6. In the appropriate fields, type the user name and password obtained from the Email Administrator.

7. Click Test Email Settings to send a test email.



8. If the email was successfully sent, click Save to save changes.

Error Message 2 - Invalid User ID or Password


Description: This message indicates that the sensor attempted to connect to the mail server but was rejected because the User ID and/or Password that the sensor attempted to use did not match that stored on the SMTP Server.

Possible Cause: The user name and/or password stored in the sensor is incorrect. This could be a typing error or due to an incorrect User Name and/or Password being supplied by the Mail Administrator.

Resolution:

1. Contact the Mail System Administrator to obtain the SMTP user name and password for the email address listed in the From field.




5. In the appropriate fields in the Logon Information section, type the user name and password obtained from the Email Administrator.



Error Message 3 - Invalid SMTP Server Address


Description: This message indicates that the sensor could not find the SMTP Server address that was entered in the SMTP Server field.

Possible Cause:

The SMTP Server address was incorrectly typed.

The SMTP Server address given to you by the Email Administrator was incorrect.

Resolution:

1. Contact the Mail System Administrator to obtain the SMTP server address or host name.






5. In the SMTP Server field, type the SMTP server address obtained from the Email Administrator.



Error Message 4 - Send (from) email address cannot send from SMTP server


Description: This message indicates that the email address listed in the From field on the Data Delivery tab was either not found, or the account does not have permission to send email messages.

Possible Cause:

The From email address was incorrectly typed.

The email account does not exist on the SMTP Server.

Resolution:

1. Contact the Mail System Administrator to obtain the email address that should be entered into the From field.




5. In the From field, type the sender email address.



Error Message 5 - Sensor cannot connect to the SMTP server


Description: This message indicates that the sensor was unable to connect to the SMTP Server.

Possible Cause: The sensor could not find a valid DNS Server in order to resolve the host name of the SMTP Server.

Resolution:

1. Contact the Network Administrator to obtain the IP address of the DNS server for the network.





4. Click the Network tab. The network settings appear.

5. In the DNS Server field, type the DNS Server IP address.


7. Click Yes to confirm the save.

8. Click Ok to close the verification dialog.

9. Click Data Delivery. The Data Delivery tab appears.


Error Message 6 - Sample error email returned to sender


Description: The system was able to access the SMTP Server but the email address listed in the To field was not a valid email address.

Possible Cause:

The To email address was typed incorrectly in the Data Delivery tab.

The To email address does not exist in the SMTP Server email system.

Resolution:

1. Contact the Mail System Administrator to obtain a valid email address for sending daily sensor count emails.




5. In the To field, type the recipient email address.





Appendix B: Calibration Features

Figure 58. Calibration screen

Calibration screen features

Feature Description

Image Group

Show Height When selected, displays the height of objects as they are tracked through the sensor’s field of view.

Unit Selects centimeters (default) or inches for the height measurement displays. This check box is only enabled when the Show Height check box is selected.

Show height map When selected, changes the view to show tracked objects heights in a color-coded scale. An adjacent legend defines the color scale.

Clear Button Used to clear the view in the Show height map. This button appears when the Show height map check box is selected.

Calibration Group

Enable Preview Enables a color-coded overlay to be displayed over the sensor’s image. This color-coding helps verify that the sensor is accurately calibrated. Numbers in upper left of the screen show the percentage of pixels that are undefined and in good calibration.

Height - Contains the mounting height of the sensor.

Y Rotation - Contains the Y rotation of the sensor.

X Rotation - Contains the X rotation of the sensor.

When Enable Preview is selected the Height, Y Rotation, and X Rotation fields show the values that are currently being previewed on the sensor’s image.

When Enable Preview is not selected, the Height, Y Rotation, and X Rotation fields initially show the currently saved values for the three parameters.

Miscellaneous Group

3D Zoom Sets the scaling for the real-world tracking image displayed on the Counting and Queuing pages. This field is automatically set based on the height and rotation returned by the sensor’s calibration.



Feature Description

Brightness

Disabled. The sensor automatically seeks out the best brightness settings.

Sets brightness of the camera image (auto-exposure). If a scene is too dark, you should increase the brightness setting.

Note: It is possible to make the camera image too bright or too dark and negatively impact the tracking system. In typical shopping and banking environments, this setting should not be above 80 or below 40.

Quality Adjusts the quality settings to be optimized for either indoor or outdoor tracking. If both selections are grayed out and cannot be changed, then the settings have been custom set on the Quality tab of the Brickstream 2300 Tracking page. To enable the radio buttons, access the Tracking page (http://<IP Address>/tracking.html) and change the Quality values back to the default values (Dynamic Range = 20, Noise Threshold = 75, and Undefined Threshold = 50).

Indoor

Sets the values for the Quality tab on the Tracking page to the following values:

Min Dynamic Range = 20

Noise Threshold =75

Undefined Threshold = 50.

Outdoor

Sets the values for the Quality tab on the Tracking page to the following values:

Min Dynamic Range = 20

Noise Threshold =95

Undefined Threshold = 50.

GP Adaptation Used for outdoor mounting only.

Filters Group

Filter Carts Enable this check box to filter out shopping carts.

Height Filter Sets how tall objects must be to be counted by the system. Objects shorter than the height specified here may still be tracked but will not be counted.

Background Group

Counting Enable this check box to set the sensor background adaptation mode for counting. Disable this check box for all other modes, such as queuing, tracking, combined counting and queuing.

Empty Background Capture Click this button to capture a new background. The background should be empty (clear of all people and equipment) when you click the button. A new background should be captured each time you save a new calibration change.

Calculate button Uses the green calibration box to automatically calculate sensor mounting Height, X Rotation, and Y Rotation.

NOTE: Calibration can take up to two minutes. Once calibration completes, new calibration values are displayed in the Calibration group and the Calculate button becomes active again. Click Save to save the calibration to flash memory.

Save button Saves calibration settings to flash memory within the sensor.

Reset Button Restores the last saved sensor configuration (all parameters). This feature is typically used when you are previewing calibration changes and decide to revert back to a previously saved version.

Defaults Button Resets all options to the factory settings.

Couple Counting Group

Default When selected, turns Couple Counting off.

Couples Use where undercounting occurs due to pairs of people walking arm-in-arm or very close together. This option decreases the thresholds that the sensor uses to differentiate between individuals. This allows the sensor to more accurately identify closely spaced persons as two people instead of one.

Custom Only used for customized settings.



Appendix C: Administration

In the sensor’s Web-based configurator, click the Administer tab. The Administration screen appears.

Figure 59. Administration screen

Importing a Configuration File

Importing a configuration/calibration .ini file having predetermined parameters is useful if installing sensors in similar environments.

1. In the Import group, click Browse to find the file.

2. Click Yes or No for import calibration.

3. Click Import to import the file.

Exporting a Configuration File

Your configuration can be exported to a remote site for future use/retrieval. In the Export group, click Export to export the file.

Adding Password Protection

1. In the Password Protection group, check the Enable Password Protection box.

2. In the User Name field, type your user name (1-32 characters),

3. In the Password field, type your password (1-16 alphanumeric characters).

4. In the Confirm Password field, retype your password.




Server Device Software Upgrade

Sensor firmware can be upgraded over an internet connection through the use of a TFTP server.

Note: A simplified process is also provided. See Client Device Software Upload.

Install the Tftpd32 Server

1. To download the server into your laptop, perform an internet search for the tftp32 server.

Figure 60. TFTP32 server location

2. Click the link; the page containing the file opens. Select the tftpd32 file and click Download.

Figure 61. Downloading the tftpd32 file

3. From the versions page select tftpd32 installer.

Figure 62. Versions page



4. In the security warning window, click Run.

5. In the License Agreement window, select I Agree.

6. Select Start Tftpd32 and click Next.

Figure 63. Start Tftpd32 location

7. The Tftpd32 engine installs by default on the C:\ drive. Click Install.

Figure 64. Tftpd32 installation



8. Once the Install is complete the Tftpd32 window opens. Click Close.

Note: If the TFTP server is installed on a machine protected by a firewall, you may have to change the firewall configuration to allow the TFTP to upgrade the firmware.

Upgrade the Firmware

Access the sensor either through the static IP or dynamic IP address. If using static IP, make sure the laptop is configured for it.

1. In the sensor’s Web-based configurator, click the Administer tab, and then scroll down the page to the software upgrade section.

Figure 65. Software upgrade section

2. Point the directory of the Tftpd32 server to the where the update firmware file is in your laptop. The engine will look into the given folder to pull the file and push it into the overhead sensor. This can be done in two ways:

First Method: Click Browse on the Tftpd32 server and point to the where you saved the firmware file on your local drive. Click OK.

Figure 66. Browsing for firmware

Second Method: A. Copy the update .bin file.



Figure 67. Location of .bin file

B. Open the Tftpd32 folder on your C drive.

C. Paste the file into the folder.

Figure 68. Pasting into Tftpd32 folder

3. On your desktop, double click the Tftpd32 icon and keep the window open. Make sure the directory points to the where upgrade firmware file is on your C:\ drive.

Figure 69. Tftpd32 icon



Figure 70. Server interface

Note: The Server interface should be the IP of your laptop. If using Static IP, this should be the IP you had previously configured. If you are on the network, this will be the dynamic IP of your laptop. In this example, the dynamic IP is shown.

4. In the Software Upgrade field of the sensor web interface type the TFTP server address. The TFTP server address is the same as the IP on service interface on the Tftpd32 server.

Figure 71. Software upgrade

In the Upgrade file Name field, enter the .bin file. An easy way to do this is using the Tftpd32 server.

A. Click Show Dir.

Figure 72. Show dir



B. Select the flashbootcount .bin file. This ensures you copied the file into the Tftpd32 folder earlier. Click Copy and close the directory.

Figure 73. Locating the flashbootcount.bin file

C. Paste the file name into the Upgrade file name field in the web interface.

Figure 74. Upgrading the file name

5. Click Upgrade. Make sure the Tftpd32 server is open by the side to observe the download progress.

Figure 75. Upgrading the software



Note: Once the download starts, its progress is visible in a new window. The middle LED on the sensor (LED 2) will change its status indicating that the new software is being downloaded. The upgrade duration depends on the network speed.

CAUTION: Do not disconnect the network connection or power off the device during the software upload, doing so could render the sensor unusable.

Figure 76. Upgrading in process

6. Once the progress bar disappears, confirm the files were sent to the overhead sensor by viewing the Log viewer tab and checking whether the file was sent.

Figure 77. Log viewer tab

7. Scroll down the page, on the upgrade status field you will find the message “uploading file”, although the upload is complete. Wait about 3 minutes and click Refresh.

CAUTION: Do not press F5 on your laptop. The successful upgrade status will display on the web page.



Figure 78. Refresh button

8. If the upgrade was successful, close the Tftpd32 server. This is a very important step.

9. Under the Administer tab of the sensor’s Web-based configurator, click Reboot. The system will ask you to close the browser page.

Figure 79. Reboot button

10. Re-open the sensor’s Web-based configurator. The updated firmware revision should appear at the bottom of the page and on the help page.

Figure 80. Firmware revision



Client Device Software Upload

This is an.html feature that enables firmware uploads without the need for TFTP.

1. Under the Administer tab of the sensor’s Web-based configurator, click Browse to find the file.

2. Click Upload to upload the file.

3. Click Reboot. The system will ask you to close the browser page.

Figure 81. Reboot button

4. Re-open the sensor’s Web-based configurator. The updated firmware revision should appear at the bottom of the page and on the help page.



Appendix D: Advanced Features License

If additional options are needed, an Advanced Features Software License (CBC-40SW-BSAF) is required that includes a special license key.

1. In the sensor’s Web-based configurator, click the License tab. The License Entry screen appears.

Figure 82. License Entry screen

2. In the License Key field, enter the license key provided.

3. Click Submit to display new license information.



Appendix E: Shopping unit detection

Shopping unit detection enables two closely-paired people to be counted as a single shopping unit. For example, a bedding store may want to count couples as a single shopping unit.

Note: Shopping unit detection should typically be used across all stores in a chain as it will affect traffic counts. Use this option only if directed by the account team or program manager.

1. In the sensor’s Web-based configurator, click the Counting tab. The Counting Configuration screen appears.

Figure 83. Counting Configuration screen

2. Right-click on a zone and choose Configure from the pop-up menu. From the Counting Config Parameters window, click Enable in the Shopping Unit pane.

Figure 84. Counting Config Parameters



3. In the Track Max Distance field, enter the maximum distance two people can separate to be counted as one shopping unit when they pass through the field-of-view. Default is 122cm.

4. In the Start Track Max Distance field, enter the maximum distance allowed between the starting points of two tracks for the tracks to be counted as one shopping unit. Default is 122cm.

5. In the Time Difference field, enter the maximum difference in the start time for each track when people fully enter the field-of-view. Default is 5000ms.

6. Click OK.

As people pass through the field-of-view, a green dot is drawn on the person as they are counted. Once shopping unit detection is set, as people pass through the field-of-view, a cyan dot indicates a person is part of a shopping unit and is not counted.



Appendix F: Path Linking Feature

Using Path Linking

By enabling you to link a master sensor to up to two subordinate sensors to create a large virtual floor plan, the Path Linking feature can greatly reduce the configuration time on wide entrances where counting lines of adjacent sensors must be precisely positioned to avoid over counting and under counting.

Path Linking enables you to:

Use the master sensor to create the counting lines and intersections for each subordinate sensor.

Combine the count line data from the subordinate sensors and distribute it, for further analysis as part of the master sensor’s data, to the user designated data warehouses.

Unlink the sensors at any time and then relink them later, or replace the sensors with others.

To enable Path Linking, install a Path Linking license on the sensor you want to be the master. Subordinate sensors do not require this license.

Setting Path Linking

You need to designate a specific port for path linking. This port indicates where the master sensor listens for a request and is the one used by subordinate sensors to determine where to send their data.

1. In the sensor’s Web-based configurator, select the Basic Settings > Data Delivery screen.

2. Click Path Linking to expand the Path Linking section.

Figure 85. Path linking

3. Check the Enable Path Linking box.

4. In the Port field, type the port number (default 80) to which the sensor should attempt to deliver the path linking data.




Creating the Master Sensor

1. On the Path Linking screen, click Enable Path Linking.

This sensor is now the master and an Add Smart Device button will be accessible. Also note that the video image and digitized image of the master sensor also appears.

Figure 86. Add Smart Device Button

Adding a Subordinate Smart Device

Click Add Smart Device to begin setting links to up to two subordinate sensors.

1. Click the Add Smart Device button. The Add Path Linking Smart Device window appears.

Figure 87. Add Path Linking Smart Device window

2. Type the IP address location and port, default 80, of the new subordinate smart device then click OK. The video image and digitized image of the master sensor, red border, and the new subordinate sensor, green border, appears.



Figure 88. New Subordinate Smart Device

3. Repeat Step 1 and Step 2 to add a second subordinate sensor, if desired.


Configuring Sensors for Path Linking

For proper Path Linking operation, the linked sensors must be mapped using markers that must be aligned to compensate for differences in the field of view of adjacent sensors. This allows the sensors to properly hand off targets crossing from one sensor view to another. This is done using markers, or crosshairs.

Note: Use a minimum of two markers per sensor for alignment.

1. To create the first marker, click on a common point of interest in the video image of each sensor. To create the second marker, click on a second common point of interest in the video image of each sensor. These markers show up in the digitized images in the upper part of the screen.

Figure 89. Virtual floor plan showing markers

2. To align the two digitized images:

a. Move the mouse cursor over one of the two images until directional arrows at its center appear. Then click and hold the left mouse button to drag the image to the adjacent one until the markers overlap as close as possible.



Figure 90. Aligning digitized images

b. If the markers are not overlapping close enough, move the cursor away from the center of the image until a circle with a crosshair appears. Click and hold the left mouse button to rotate the image until the markers overlap as close as possible.

Figure 91. Overlapping markers

3. Release the mouse button after aligning the markers. Now when people move through the field of view of two sensors, only one track appears.

4. Configure the count lines once you have finished positioning the sensors.

5. Use the Template button as a shortcut for creating enter/exit/filter zones in just a few clicks.




Path Linking Shortcut Menu

Right-click on a video image to access the Path Linking shortcut menu.

Figure 92. Path Linking shortcut menu

Properties

Choose Properties. The Smart Device Properties screen appears. On this screen, you can manually change the X and Y axis and rotation of the sensor.

Clear Markers

If you’ve created markers on the digitized images, you can use Clear Markers to delete them. Click Save to save changes.

Reset Rotation

If you’ve rotated the digitized image of a sensor, you can use Reset Rotation to reset the rotation. Click Save to save changes.

Unassign

If you’ve assigned a sensor as a master or subordinate, you can use Unassign to delete the assignment. Click Save to save changes.

Notes

When placing sensors for linking, it should be possible to see people’s shoulders in the overlapping field of view. The device coverage spreadsheet should be used to determine device locations.

Count data is generated on the master sensor. If the master is not functioning, all data is lost until the master is back online.

For path linking to accurately work and collect data, all sensors in the group must be up and running.

AVIs need to be captured from the individual devices and validated concurrently. Path-linked AVI capture and validation is not supported at present.

Documents

BIC-2300 Overhead Stereo Traffic Sensor Setup Guide 8200