maintenance/troubleshooting - · pdf filemaintenance/troubleshooting • no network...

1

1) HB – (Diagnostics “Heart Beat”)If Green device is communicating and sending HB data. If Red device is notcommunicating.

2) MAC’s – (Bluetooth detection)If Green device is receiving MACdetection data. If Red device is notreporting MAC detections to database.

3) Lag – (Device latency)If Green device is in-sync with server. IfRed device clock is out of sync with server and other devices.

Maintenance/Troubleshooting

1





Hardware TrainingBlueTOAD

1





Why are we here?

• Provide enviroment to educate and discuss BlueTOAD

• Share inside experience

• Open forum discussion

1





What are our Goals

• Propertestingproceduresbeforefield install

• Field installation & check list beforeyou leave

• Field troubleshooting

• Website setup

• Website troubleshooting

1





• PuTTyTerminal Emulator application used forBlueTOADconsoleconfiguration

• POEPower over Ethernet

• GSMGlobal System for Mobile

• ETOADEthernet based device

• GTOADCellular based device

• National ServerTrafficCastHostedBluetoadServer

• SASStand Alone Local BlueToad Server

• DeviceBlueTOAD sensor

• HBHeartBeat

• MacMedia Access Control Address

• Latency/Lagdiscrepancy between device and server

• PairsRelation between two devices to derrive travel time & speeds

• NTPNational Time Protocol

• RoutesA complilation of pairs

• ESDElectro-Static Discharge

• RSSIRecieved Signal Strength

• GSM BERGlobal System for Mobile Bit Error Rate

• StatusHBcountsenselastreboot

Nomenclature list

1





ETOAD - Getting StartedPreparingClient’sNetworkMUSTHAVES

Outbound ports must be open:

• Port 8010 - Comm to BT Server

• Port69-Firmwareverification

• Port 123 - Comm to NTP timing

1





ETOAD - Getting StartedProgramming ETOAD Devices, what you need from client:

• IP Address

• Gateway

• Netmask

• NTP Server

• DNS

1





ETOAD - Getting StartedProperworkenviromentfortestingbeforefielddeployment

• Clean & secured/mounted

• Grounded

• Can you access clients network

• Can you get a list from client ofconfiguration

• Connect to a network & test/verifyETOAD is able to connect to abluetoad server (National &/or SAS)

1





• No network connectionrequired, but physical con-nection to board required

• Can change betweenCellular/Ethernet

• Can change manysettings that are onlyavialable through theconsoleconfigurationmenu.

• Device must have anetwork connection (to net-work or local machine)

• No physical connectionrequired to board

• Can only change networksettings (IP, Gate, DNS,Mask, NTP)

• Can connect remotely onthe same network

ETOAD - Getting StartedTwo ways to program BlueTOAD devices

Console vs Web Config

1





• The more you prepare, the easier the install

• Pick your locations - Google Earth Pro is FREE

• Pre-program device settings to match location settings

• BONUS: Setup your devices/pairs on the site beforeyou install

GTOAD:

• Scout for solar placement

ETOAD - Getting StartedPreparingforthefield-Doyourhomework!

1





• Device Not Turning On-Check for green light on PoE Injector Power Supply-Check for green light on PoE Splitter-Test ethernet cables with cable tester

• No Connection to Server-Does device have power-Verifyconnectionsettingsviaconsoleorwebconfig-RunTestPorttoolfromTrafficCastwhilepluggedinto cabnet

• Not Detecting MAC Addresses-Is the bluetooth antenna connected?-IstheS1lightflashingslowly1x/3sec?-Doyouseethebluelightflashingoccasionallyonthe bluetoad PCB?-IsthereenoughtrafficwithinrangetodetectMACs?

ETOAD - Getting StartedTroubleshootingdeviceinthefield

1





Using the Console Port

Connecting through the console port provides a lot of help and vital information when troubleshooting the BlueTOAD devices. Connect using a serial DB9 Female Cable with your port set to 115,200, 8, N, 1, N. Power cycle the BlueTOAD once you are connected serially and hit any key to enter the configuration mode.

**Each BlueTOAD comes with a small install manual which details how to gain access through the web interface and serially. In addition it details all the CLI commands but you can always type ? to see the complete list on-board the BlueTOAD

Type ‘showconfig’ and verify all the device settings

1





Once everything is verified for the BlueTOAD type ‘boot’ and monitor the text as the BlueTOAD goes through itsboot and operation process

Monitor the BlueTOAD operating Text and make sure the BlueTOAD is able to connect to the BlueTOAD server onport 8010. After about 3-4 minutes of running you should begin to see the BlueTOAD connect to the server andtransmit MAC data without seeing any errors.

**Important Note – Make sure the BlueTOAD is connected into the switch while it is booting. If the BlueTOAD doesnot detect an Auto Negotiating Ethernet connection it will not complete the startup boot and continue recycling.

1





BlueTOAD is not displaying data on the Server

The BlueTOAD devices require 4 separate communication paths on the Network for 100% operation:

NTP Server communication, DNS Server communication, BlueTOAD Server Communication, and

Network Gateway communication

If any one of these network items are not setup or working properly, the device will either not report accurate data to the server or be unable to connect at all.If you are receiving this data (Bad-News-Dude, 143.100.231.249 refuses the connection) from the BlueTOAD

please proceed with verifying each connection using the following steps

1





ObjectiveLet’s get your BlueTOAD connected, communicating, and collecting data fast!

OverviewTo provide a complete set of resources and tools that will allow a user the ability to verify, troubleshoot, and diagnose any issues on a BlueTOAD network.

Check List

Installation

BlueTOAD POE device is powered on and plugged in to a protected power source (non GFI outlet)

POE is properly grounded and the BlueTOAD is plugged into the Power + Data port of the injector

BlueTOAD is mounted 10-14’ above road level and facing lanes of detection

BlueTOAD board is showing LED status of power and network connection

BlueTOAD is plugged in to the designated and specified Field Switch port

Proper cable is used from cabinet POE to BlueTOAD – shielded CAT5e with shielded connectors

CAT5e cable and terminations are tested and verified after installation

Communication

LED status on field switch shows activity and local area connection

Factory made CAT5e jumper is used to connect from POE splitter to Field Switch

Web Interface from the switch into the BlueTOAD and screen shot the settings (default address below): http://IP:8080/cgi-bin/admin.cgi username = admin PW = 77admin77

Verify the Device ID is correct for that location according to the master spread sheet

Verify the BlueTOAD NTP Server Status and BlueTOAD Server Status are both Green (Take Screen Shot)

1





Troubleshooting

Unable to Web Interface into the BlueTOAD

Verify what the BlueTOAD IP, Subnet, and Mask should be at the location from the master device spreadsheet

Verify that your PC is set within the IP, Mask, and GW range allowed for this location

If you are plugged into the Field Switch, remove your connection and plug directly into the Data port of the BlueTOAD (some agencies have VLANs and other things blocking ports on the field switch)

**Special Note – The BlueTOAD device can take up to 5 minutes after power cycle or rebooting to allow access on the Web Interface….Be Patient!

Send a Ping to the device IP address and verify you are receiving a response back. If you are not, either you or the device is not set with the appropriate IP info.

1





Troubleshooting

Unable to Web Interface into the BlueTOAD

Verify what the BlueTOAD IP, Subnet, and Mask should be at the location from the master device spreadsheet

Verify that your PC is set within the IP, Mask, and GW range allowed for this location

If you are plugged into the Field Switch, remove your connection and plug directly into the Data port of the BlueTOAD (some agencies have VLANs and other things blocking ports on the field switch)

**Special Note – The BlueTOAD device can take up to 5 minutes after power cycle or rebooting to allow access on the Web Interface….Be Patient!

Send a Ping to the device IP address and verify you are receiving a response back. If you are not, either you or the device is not set with the appropriate IP info.

Set your laptop to the Exact IP, Mask, GW, and DNS as the BlueTOAD is

Plug in to the same port of the Field Switch as the BlueTOAD is currently connected

Send Ping tests to the local switch address and verify you receive a response back. If no response is returned then go back and check network settings on the BlueTOAD, Switch, or VLAN config of the local agency

1





Send Ping tests to the defined Gateway on this subnet. If no response check with network administrator on the network settings for this subnet. If successful, please proceed with the following steps.

Send Ping tests to the BlueTOAD Server and DNS address and verify you receive response back. If no response back, the network may be blocking access to the BLueTOAD server address and please contact the network administrator

BlueTOAD Device shows up on the Server but no MACs are being recorded

**Special note – If the BlueTOAD cannot see the NTP Server or has limited connection the timestamps for MAC hit will be corrupt and the BlueTOAD server will refuse the connection.

What are we looking for?If you notice you have an issue with a device verify the following:

1) Does the device have power?No brainer, if device does not have power, get it power.

2) Does the device have communication?If device does not have comms a field visit will be necessary.

3) Does the device have latency?If you made it this far device is communicating but with latency, time to sync the clock.

4) Check device/pair settings, not a device issue1) Check device settings, make sure device is active and date range is valid.

2) Check pair distances and speeds


Page 10

GTOAD - Getting StartedProperworkenviromentfortestingbeforefielddeployment

• Clean & secured/mounted

• Inside ok if you can get a signal

• Can you connect to Cellular network

• Can you connect to GPS

• Move device outside if unable to get connection inside.

• If unsure about connection status call techsupportforverification

GTOAD - Getting StartedField Installation

• 8 - 14 Feet

• Clear line of sight to South

• Avoidplacingsolarneartraffic,ifonlyoption mount high to avoid OSOW vehicles

• If unsure about connection status call techsupportforverification

What are we looking for?If you notice you have an issue with a device verify the following:

1) Does the device have power?No brainer, if device does not have power, get it power.

2) Does the device have communication?If device does not have comms a field visit will be necessary.

3) Does the device have latency?If you made it this far device is communicating but with latency, time to sync the clock.

4) Check device/pair settings, not a device issue1) Check device settings, make sure device is active and date range is valid.

2) Check pair distances and speeds


Page 10

1

1) HB – (Diagnostics “Heart Beat”) If Green device is communicating and sending HB data. If Red device is not communicating.

2) MAC’s – (Bluetooth detection)If Green device is receiving MAC detection data. If Red device is not reporting MAC detections to database.

3) Lag – (Device latency)If Green device is in-sync with server. If Red device clock is out of sync with server and other devices.


Page 11


2) MAC’s – (Bluetooth detection)If Green device is reporting MAC detection data. If Red device is not reporting MAC detections to database.


2


Page 12

3


2) MAC’s – (Bluetooth detection)If Green device is receiving MAC detection data. If Red device is not reporting MAC detections to database.



Page 13

1) Select Device

2) Date Range

3) Output type (CSV recommended unless looking at most recent data)

1


Page 14

1) Device

2) Set Date Range


Special Note: We don’t know the last time this unit 1303 was operational, so we will start with the beginning of the year, and work back until we find a date with operational data.

2


Page 15

1) Device

2) Date Range


3


Page 16

TimeMost recent communication with device.

Special Note: In this report we can see that last readings were 8/18/2015 19:02. (Current date is 8/25/15) so device has been offline for 7 days.

It is important to note, when many devices are down on a network, compare their times with each other. If all went down at the same time, obvious network issue.

- This device was working fine then suddenly nothing, would need to visit in field.

Field visit check list(assuming device worked at some point):

Device on upon arrival? Can device power on?

Reboot, did it help (S1 slow flash)?

Yes No

Confirm IP/Gateway/Netmask with IT; issue resolved?


Page 17

LatencyThe device time is compared to the server time if a discrepancy(+/-) the amount of error will be displayed.

Special Note: If device is communicating use the remote web config tool to access device settings, and even reboot without a field visit. “Submit changes” will reboot the unit.

Never change the IP or Gateway unless certain, otherwise if setting incorrect a field visit will be needed.


Page 18

StatusFor every sequential HB +1 to Status. If Device resets, Status also resets to 0.

Special Note: When diagnosing a device, look for data around a 0 reset, it may tell you something about the device before it reset, such as a device latency increase where previously there was no latency.

VoltsTracks the input power, very helpful for tracking GTOAD Solar/Battery consumption.


Page 19

Latitude/Longitude GPS Data is used for syncing clocks on devices

Special Note: GTOADS have on board batteries which are used to sync the clocks when GPS data is lost. A device only needs to sync with GPS 1/year to keep clocks insync.

SatsHow many GPS satellites are triangling the device.


Page 20

RSSI (Received Signal Strength Indicator)

Special Note: If high interference and jumping between GSM Channels device may need an external antenna to help boost a signal to the best channel available.

GSM BER (Bit Error Rate)Between 0 & -5 OKIf lower than -5.1 increased interference until finally a drop-off, if does not recover.

GSM ChannelCan inform you if device is jumping recievers.


Page 21

This is how we calculate solar panel and battery sizing:

## Amp Hour Consumption ##:GTOAD is 1.8Watts

1.8watts / 12volts * 24 hours a day = a total of 3.6 amp hours in a 24hr period.

## PV Amp Hours Required ##:3.6 / 3 sun peak hours(in chicago - midwest) = 1.2 array amps.

20 watt is 1.19 array amps, 30 watt is 1.79 array amps, 50 watt is ~2.7 array amps.

## Sun Peak Hours ##:-- This is what is required from the solar panel to restore the energy

consumed by the load with ~3 avg peak sun hours, which covers the majority of the US.-- use a different Sun Peak Hour number for a different region if required.

## Battery Consumption ##for the battery @ 25C:

36 ahr battery / 3.6 ahr a day = 10 days down to 0% capacity.44 ahr battery / 3.6 ahr a day = 12 days down to 0% capacity.

Note: @0C the battery capacity is reduced by 50%

maintenance/troubleshooting - · pdf filemaintenance/troubleshooting • no network...

Documents