Answers are available.
All you have to do is ask.

Customer Support: (510) 898-2269
Tech Support: (877) 836-8988
International Support: +(39) 3467320800

Contact Us

Order


Area of Interest (please choose at least one)

















RMA Inquiry Type

How many products do you need to return? (required)




If the serial number is not known, the product must be returned to determine its warranty status.
Description of the problem experienced, any troubleshooting attempted and the results of troubleshooting.

Please include Product Model Name, Serial Number and Issue Description for each product submitted for return. Note: If the serial number is not known, the product must be returned to determine its warranty status.

Area of Interest (please choose at least one)

















Technical support

Technical Seminars

Area of Interest (please choose at least one)

















Troubleshooting

TrafficDOT

Connects to APCC
No active sensors.
  • Verify that Master Mode is enabled for SPP(s) (SPP 0 and SPP1).
  • Verify SPP connection is on (SPP text displays black for active connection, red for not connected).
  • Identify configured SPP radios and RF channels.
  • Confirm the proper height and orientation of SPPs and RPs.
  • Confirm sensors are within range of SPP or RP.

If SPP 0/1 link light is off.

  • Check cable between SPP and Isolator.
  • Check cable between APCC and Isolator.
  • Check that Isolator power and link lights are on.
Some active sensors missing.
  • Confirm RF channels.
  • Scan all SPP, RP RF channels for missing sensors (may need to wait at least 2 minutes per channel).
  • Confirm SPP or RP is within range, proper height, and orientation.
  • Reset Keep RF command.
  • Perform hard reset (sets sensors back to factory-default RF channel 0).
  • Confirm that battery is connected to RP.
  • Check if equipment is damaged or missing.
Some or all active RPs missing.
  • Confirm RF channels.
  • Scan all RF channels for missing RPs (may need to wait at least 2 minutes per channel).
  • Reset Keep RF command.
  • Perform hard reset (sets RPs back to factory-default RF channels 0 -> 1).
  • Confirm that SPP or RP is within range, proper height, and orientation..
  • Confirm that battery is connected to RP.

Confirm that battery has sufficient charge.

  • Sufficiently charged battery – LEDs flash red and green when initially powered, then flash red about every 3 seconds.
  • Insufficiently charged battery – LEDs flash red and green consistently or not flash at all.
  • Check if equipment is damaged or missing.
Active sensors are yellow or red (not green)

Confirm RF settings (RSSI, LQI, and Timeslot) are within specs.

  • If RSSI value is low, try changing geometry of SPP or RP.
  • If LQI value is low, select a different (available) RF channel.
  • If Timeslot is red, click the Auto-Assign Timeslots button.
One or more sensors show stuck high (icon color: black)

Check if active sensor is stuck high.

  • If sensor stuck high, recalibrate sensor.
  • Check for magnetic noise source.
  • Check the recalibrate timeout values (under the AP's Detection tab). Five minutes is default.
Missing CC/EX card

Check cable between APCC card and EX card(s).

Confirm proper SW1 and SW2 settings.

  • Confirm each card has a unique address (shelf ID and slot ID configuration).

Check communication with EX card(s).

  • Verify that cable is connected to the 'In' port of the EX card from the 'Out' port of the previous card.

Check for damaged EX card (Swap cards if necessary).

  • Check if Fault Indicator light is on (indicates damage).
  • Visually inspect circuit board for damage (such as black marks).
  • Press reset button to see if all lights display.
  • Check for proper input voltage (.5 amps at 12v is nominal for TS2 and .2 amps at 24v is nominal for TS1).
Constant Call on APCC/EX card(s) input channel
  • Verify that there is nothing in the adjacent slot (if using 4-channel mode).
  • If 2070/TS2 type controller, verify that APCC/EX card TS-mode DIP switch is set to TS2 (SW1 position 3 should be OFF).
  • Check for proper BIU operation.
  • Check for stuck sensor.
  • Confirm sensor zone assignment.
Constant Call on Controller
  • Verify proper input backplane assignment.
  • Verify that there is nothing in the adjacent slot (if using 4-channel mode).
  • If 2070/TS2 type controller, verify that CC/EX card TS-mode DIP switch is set to TS2 (SW1 position 3 should be OFF).
  • Check for proper BIU operation.
False Call on APCC/EX card(s)
  • Check that detection zones are assigned properly.
  • Check that no detection occurs when no vehicle is present (magnetic noise).
  • Check if sensor is detecting adjacent lane traffic.
  • Check the Checksum failure count (under Controller Card>Info tab). (Too many can cause a false call or cause the card to reboot.)
  • Check failsafe mode (default is OFF).
Missed Call on APCC/EX card(s)

Sensor(s) missing vehicle detections.

  • Check if sensor is installed too deep.
  • Check if RSSI value is too high (<-90 dBm) when no vehicles are present.
  • Verify that the Delay setting is set properly.
  • Check connectivity and verify that all sensors are assigned to proper card address.
  • Verify that there are no timeslot conflicts.

Check the detection default settings

  • For F-model sensors, check the detect Z threshold (Default value is 12. Lowering the value increases sensitivity.)
  • For T-model sensors, check the Stop Bar mode (Default value is Stop Bar mode 5. Lowering the value increases sensitivity.)
Cannot apply APCC settings
  • Confirm valid sensor zone name and position for each assigned sensor.
Connects to AP240
No active sensors.
  • Verify that Master Mode is enabled.
  • Confirm RF channel.
  • Confirm AP or RP is within range, proper height, and orientation.
Some active sensors missing
  • Confirm RF channel.
  • Confirm AP or RP is within range, proper height, and orientation.
  • Reset Keep RF command.
  • Perform hard reset (sets sensors back to factory-default RF channels 0).
  • Confirm that battery is connected to RP.
  • Check if equipment is damaged or missing.
Some or all active RPs missing
  • Confirm RF channels.
  • Scan all RF channels for missing RPs (may need to wait at least 2 minutes per channel).
  • Reset Keep RF command.
  • Perform hard reset (sets RPs back to factory-default RF channels 0 -> 1).
  • Confirm that AP or RP is within range, proper height, and orientation.
  • Confirm that battery is connected to RP.

Confirm that battery has sufficient charge.

  • Sufficiently charged battery - LEDs flash red and green when initially powered, then flash red about every 3 seconds.
  • Insufficiently charged battery - LEDs flash red and green consistently or not flash at all.
  • Check if equipment is damaged or missing.
Active sensors are yellow or red (not green)

Confirm RF settings (RSSI, LQI, and Timeslot) are within specs.

  • If RSSI value is weak, try changing geometry of AP or RP.
  • If LQI value is low, select a different (available) RF channel.
  • If Timeslot is red, click the Auto-Assign Timeslots button.
One or more Sensors show stuck high

Check if active sensor is stuck on.

  • If sensor stuck high, recalibrate sensor.
  • Check for magnetic noise source.
  • Check the recalibrate timeout values (under the AP's Detection tab). Five minutes is default.
Missing CC/EX card
  • Check cable between CC card and EX card(s).

Confirm proper SW1 and SW2 settings.

  • Confirm each card has a unique address (shelf ID and slot ID configuration).

Check communication with EX card(s).

  • Verify that cable is connected to the 'In' port of the EX card from the 'Out' port of the previous card.

Check for damaged CC/EX card (Swap cards if necessary).

  • Check if Fault Indicator light is on (indicates damage).
  • Visually inspect circuit board for damage (such as black marks).
  • Press reset button to see if all lights display.
  • Check for proper input voltage (.5 amps at 12v is nominal for TS2 and .2 amps at 24v is nominal for TS1).
False Call on CC/EX card(s)
  • Check that detection zones are assigned properly.
  • Check that no detection occurs when no vehicle is present (magnetic noise).
  • Check if sensor is detecting adjacent lane traffic.
  • Check the Checksum failure count (under Controller Card>Info tab). (Too many can cause a false call or cause the card to reboot.)
  • Check failsafe mode (default is OFF).
Missed Call on CC/EX cards(s)

Sensor(s) missing vehicle detections.

  • Check if sensor is installed too deep.
  • Check if RSSI value is too high (<-90 dBm) when no vehicles are present.
  • Verify that the Delay setting is set properly.
  • Check connectivity and verify that all sensors are assigned to valid card address.
  • Verify that there are no timeslot conflicts.

Check the detection default settings

  • For F-model sensors, check the detect Z threshold (Default value is 12. Lowering the value increases sensitivity.)
  • For T-model sensors, check the Stop Bar mode. (Default value is Stop Bar mode 5. Lowering the value increases sensitivity.)
Constant Call on Controller
  • Verify proper input backplane assignment.
  • Verify that there is nothing in the adjacent slot (if using 4-channel mode).
  • If 2070/TS2 type controller, verify that CC/EX card TS-mode DIP switch is set to TS2 (SW1 position 3 should be OFF).
  • Check for proper BIU operation.
Cannot Connect to APCC
Check laptop network configuration.
  • Set correct IP settings (address, mask, gateway), default AP IP address is 192.168.2.100, subnet mask is 255.255.255.0, set laptop static IP address 192.168.2.200 (May require administrator rights.)
  • Ensure that laptop firewall is disabled. (May require administrator rights.)
  • Ensure that the laptop's local network adapter is enabled.
  • Verify the link light adapter on the laptop is on.
  • Check that laptop's alternative IP configuration is not in use. (May require administrator rights.)
Verify that green link light on the Ethernet port of the APCC is on.
  • Ensure proper physical connections.
  • Inspect ports for visible damage.

Test cable for correct PIN out assignment (T-568B).

  • If cable is damaged, re-terminate the connectors or replace the cable (as needed).
Check for damaged Sensys Networks equipment.
  • If damaged, contact Sensys Networks for replacement of APCC.
Cannot Connect to AP240
Check laptop network configuration.
  • Set correct IP settings (address, mask, gateway), default AP IP address is 192.168.2.100, subnet mask is 255.255.255.0, set laptop static IP address 192.168.2.200. (May require administrator rights.)
  • Ensure that laptop firewall is disabled. (May require administrator rights.)
  • Ensure that the laptop's local network adapter is enabled.
  • Verify the link light adapter on the laptop is on.
  • Check that laptop's alternative IP configuration is not in use. (May require administrator rights.)
For S and ES model APs, verify that both power light on the AccessBox and the green link light on the 'In' port of the CC card are on. (A dim power light on AccessBox indicates a short.)
  • Ensure valid physical connections.
  • Inspect ports for visible damage. (If damaged, contact Sensys Networks for replacement of AccessBox.)
  • If connections are correct, contact Sensys Networks for replacement of AccessBox.

Test cable for valid PIN out (T-568B). (Use cable tester.)

  • If cable is damaged, re-terminate the connectors or replace the cable (as needed).
  • Verify that the backplane voltage from the rack to the CC card is sufficient. (~11-24 VDC is required)
  • Verify that BIU is powered and functioning properly (if applicable).
  • Check for damaged Sensys Networks equipment; if damaged contact Sensys Networks for equipment replacement.
For E model AP, verify that green power light on POE is on.
  • Ensure valid physical connections in proper ports. (“RJ45” connects to the AP, “switch hub” connects to laptop)
  • If power light on the POE is dim there is a short between the POE and AP.
  • Crossover cable may be required for connection to some laptop Ethernet adapters.
  • If green power light on POE is off, check for power.

SNAPS

Cannot log onto SNAPS
SNAPS splash screen does not display
  • Verify that correct URL has been entered.
  • Check that SNAPS IP address and DNS name are valid.
  • Ping the SNAPS server.
  • Check that browser is online (supported browser).
  • If SNAPS splash screen displays, but you are unable to log onto SNAPS, have the SNAPS administrator validate your SNAPS login ID and password.
Cannot add, update, or delete an AP240/APCC, user, or AP Group in SNAPS
  • Check for missing information (required fields not completed).
  • Check for duplicate labels.
  • Check that only allowable characters are used.
  • Check that AP/APCC naming conventions are followed. (SNAPS 2.6.1 validates names automatically)
  • Confirm that user account has sufficient rights.
AP240/APCC is not communicating with SNAPS

If you can successfully ping the AP from the SNAPS console, check the AP entries in SNAPS.

Check the AP configuration entries in SNAPS

  • IP address or DNS name
  • HTTP port
  • TCP port
  • VPN name and password
  • If the AP configuration entries in SNAPS are correct, verify that all of the necessary ports are open on the firewall.

If you cannot successfully ping the AP from SNAPS, try to ping the router from SNAPS console.

If you cannot successfully ping the router from SNAPS console, contact your IT department for further assistance.

If you can successfully ping the router from SNAPS console, get someone to go onsite and have them ping their local router from APCC.

  • If you cannot ping local router from APCC, contact IT department.
  • If a cellular modem is used, confirm that equipment and service has been activated.

Verify VPN configuration on SNAPS and TrafficDOT.

  • If the VPN user name and password match those on the AP, check the AP modem page.
AP time is not synchronized with the SNAPS server

Verify that the NTPD service is running.

Check the IP address(es) or host name(s) of the NTP servers designated on the systems configuration network tab in TrafficDOT.

  • If the information is not correct, make correct entries and then restart the AP.
  • If the information is correct, ping the NTP server from the AP.
  • If you are unable to successfully ping the NTP server, contact your IT department for assistance.

Check if NTP ports are blocked (firewall).

  • If the NTP ports are blocked, have your IT department unblock them.
  • If the NTP ports are not blocked, contact Sensys Networks for assistance.

The NTPD service is not running.

  • Start NTPD service or ask your IT department to do so.
  • After NTPD service is started, check the date on the AP.
  • If the date on the AP is still not set, contact Sensys Networks.
Reports generate no data
  • Verify that none of the AP/APCC logging Statuses are red. Check connection and configuration.
  • Verify that there is data for date which the report is being run.

Confirm that none of the AP/APCC processes are red.

  • Receiving Data?
  • TimeSync?
  • DotTable in sync?
Reports generate incorrect data
  • Verify that AP/APCC's current sensor positions are synchronized in DotTable.
  • Verify that AP/APCC's IP configuration is correct.
  • Verify that multiple AP/APCC's are not assigned to the same IP address.
  • Verify that report is running for intended AP/APCC's.
  • Verify that the Dot tables contain accurate and relevant sensor information.
  • If any configuration changes are made, reboot the AP/APCC (to immediately resynchronize AP with SNAPS server).
Reports generate without graphics
  • Verify that you are using a supported browser.
  • Verify that you have selected Plots as the display format.
Reports generated, but not received by recipient
  • Verify that recipient is a valid user..
  • Verify that the SNAPS user configuration is using valid email address.
  • Verify that report was run and not just saved.
  • If report was sent as a scheduled report, verify that delivery date and time have passed and that SNAPS server reflects the proper date and time.
  • Verify that email account/server for the SNAPS have been set up. (Check with Sensys Networks.)
  • Verify that your email server is up and running. (Check with IT department.)

Travel Time

Map does not display
  • Verify Internet access.
  • Verify that correct URL has been entered.
  • Check that SNAPS IP address and DNS name is valid.
  • Ping the SNAPS server.
  • Check that browser is online (supported browser).
  • Check the map settings elements (including accurate latitude and longitude coordinates).
Segments do not display on map
  • Check configuration settings for complete and correct information.
  • Check the segments and links.
Segments (on map) display in black
  • Check the health of your APs in SNAPS.
  • Check the health of your Sensors by running a Device Diagnostics report.
  • Verify that there is sufficient traffic.
Information bubbles (on map) do not populate with data
  • Check the health of your APs in SNAPS.
  • Check the health of your Sensors by running a Device Diagnostics report.
  • Verify that there is sufficient traffic.
Information bubbles (on map) contain old data
  • Check the health of your APs in SNAPS.
  • Check the health of your Sensors by running a Device Diagnostics report.
  • Verify that there is sufficient traffic.
Segments are not listed on report or wrong segments are listed
  • Verify that the proper Travel Time AP Group was selected.
  • Check configuration settings for complete and correct segment/link information.
Data shown on report is out of range
  • Check the historic health of the equipment by running a Device Diagnostics report.
Chart doesn't display properly
  • Verify that the browser being used is supported.
Cannot find Travel Time group in the configuration
  • Check AP Group (in SNAPS) for Travel Time inclusion.