stalker stationary speed sensor ii technical manual

AppliedConcepts,Inc.2609TechnologyDrivePlano,Texas75074 972‐398‐3780

Stalker Stationary Speed Sensor II

Technical Manual

011-0131-00 Rev. H

Stalker Stationary Speed Sensor II Technical Manual

2

Regulatory Statement Note: This equipment has been tested and found to comply with the limits for a Class A digital device, pursuant to part 15 of the FCC Rules. These limits are designed to provide reasonable protection against harmful interference when the equipment is operated in a commercial environment. This equipment generates, uses, and can radiate radio frequency energy and, if not installed and used in accordance with the instruction manual, may cause harmful interference to radio communications. Operation of this equipment in a residential area is likely to cause harmful interference in which case the user will be required to correct the interference at his own expense.

Changes or modifications not expressly approved by Applied Concepts, Inc. could void the user's authority to operate the equipment.

Not intended or approved for Law Enforcement use in the United States.

Stalker/Applied Concepts

2609 Technology Drive Plano, TX 75074 USA

1-800-STALKER

(972) 398-3750 Sales / (972) 398-3751 Fax

www.stalkerradar.com


3

TableofContents1 Overview ..................................................................................................................... 5 2 Specification ................................................................................................................ 6 3 Physicalcharacteristics ................................................................................................ 7 3.1 Packagedimensions ............................................................................................. 7 3.2 Electricalconnections .......................................................................................... 8

4 ConnectingtheStationarySpeedSensor ...................................................................... 9 4.1 ConnectingtotheCOMPorts ................................................................................ 9 4.1.1 COMB–RS‐232FullDuplexPort ...................................................................... 9 4.1.2 COMAandCOMC–RS‐485Ports ................................................................... 10 4.1.2.1 COMA–RS‐485FullDuplexPort ............................................................ 11 4.1.2.2 COMAandCOMC–RS‐485HalfDuplexPorts ......................................... 11

4.2 AuxiliaryRelayConnections ............................................................................... 12 5 CustomApplicationstoControltheStationarySpeedSensorII ................................... 12 6 StreamingSpeedDataProtocols ................................................................................ 13 6.1 AFormat–SingleVisualSpeedOnly .................................................................. 14 6.2 BFormat–AllVisualSpeeds+Status ................................................................. 15 6.3 D0Format–StrongVisualSpeedOnly,OptionalDirectionByte .......................... 16 6.4 D1Format–StrongVisualSpeedOnly,OptionalDirectionByte,Checksum ......... 16 6.5 D2Format–StrongVisualSpeedOnly,OptionalDirectionByte,Tenths .............. 17 6.6 D3Format–StrongVisualSpeedOnly,OptionalDirectionByte,RelativeAmplitude,Tenths......................................................................................................... 18 6.7 D4Format–StrongVisualSpeedOnly................................................................ 18 6.8 EnhancedOutputFormat–HexAllVisualSpeeds,Status .................................... 19 6.9 SFormat–ASCIIVisualSpeeds+Status ............................................................. 21 6.10 BTFormat–ASCIITimestampfromtheunit’sinternalreal‐timeclock ............... 22 6.11 DTFormat–ASCIIDate/Timestampfromtheunit’sinternalreal‐timeclock ...... 23 6.12 DBG1Format–ASCIIinformationforalltrackedstatisticstargets ...................... 24 6.13 LOGMessage–ASCIIinformationforstatisticstargetsastheyarelost ............... 25

7 HandshakeSpeedDataProtocols ............................................................................... 26 7.1 EEPolling .......................................................................................................... 26 7.1.1 EEFormatRequest(fromControllertoStationarySpeedSensorII) ................ 27 7.1.2 EEFormatResponse(fromStationarySpeedSensorIItoController) .............. 27

7.2 EAPolling .......................................................................................................... 27 7.2.1 EAPollingRequest(fromControllertoStationarySpeedSensorII) ................ 27

7.3 PolledModeforD0‐D4Formats ......................................................................... 28 8 ConfigurationSettingDescriptions ............................................................................. 28 8.1 BasicConfiguration ............................................................................................ 28 8.2 COMPorts ......................................................................................................... 30 8.3 TargetRecognition ............................................................................................ 34 8.4 TargetFiltering .................................................................................................. 35 8.5 SpeedPresentation ............................................................................................ 36 8.6 LockingTargets ................................................................................................. 37 8.7 Real‐timeClock .................................................................................................. 38 8.8 AuxPinUsage .................................................................................................... 39 8.9 TrafficStatistics(statsunitonly) ........................................................................ 39


4

8.10 System ............................................................................................................... 42 9 ConfigurationSettingsTable ...................................................................................... 43 10 ConfigurationProtocol ........................................................................................... 48 11 Sensorvariations .................................................................................................... 50 11.1 200‐0880‐52,53 ................................................................................................. 50 11.1.1 Summary ................................................................................................ 50 11.1.2 MechanicalDescription ........................................................................... 50 11.1.3 ElectricalConnection .............................................................................. 51 11.1.4 Operation ............................................................................................... 51

11.2 200‐0880‐54,55 ................................................................................................. 52 11.2.1 Summary ................................................................................................ 52 11.2.2 Mechanicaldescription ........................................................................... 52 11.2.3 Electricalconnections ............................................................................. 52 11.2.4 Operation ............................................................................................... 52

11.3 200‐1004‐00 ..................................................................................................... 53 11.3.1 Summary ................................................................................................ 53 11.3.2 MechanicalDescription ........................................................................... 53 11.3.3 ElectricalConnections ............................................................................. 55 11.3.4 Operation ............................................................................................... 55

11.4 200‐0880‐56 ..................................................................................................... 56 11.4.1 Summary ................................................................................................ 56 11.4.2 MechanicalDescription ........................................................................... 56 11.4.3 ElectricalConnection .............................................................................. 57 11.4.4 Operation ............................................................................................... 57

11.5 200‐1033‐00,01 ................................................................................................. 58 11.5.1 Summary ................................................................................................ 58 11.5.2 MechanicalDescription ........................................................................... 58 11.5.3 ElectricalConnections ............................................................................. 59 11.5.4 Operation ............................................................................................... 60

11.6 200‐1033‐10,11 ................................................................................................. 61 11.6.1 Summary ................................................................................................ 61 11.6.2 MechanicalDescription ........................................................................... 61 11.6.3 ElectricalConnections ............................................................................. 63 11.6.4 Operation ............................................................................................... 63

12 FCCRequirements .................................................................................................. 64 AppendixA OEM6°x26°StationarySpeedSensorIIforLaneDiscrimination .......... A-1


5

1 OverviewTheSStationarySpeedSensorIIisacompleteDopplerRadarinasmall,ruggedhousing.Itsdirectionsensingcapabilitiesanditsfeature‐richconfigurationsettingsallowittofilteroutundesiredtargetsandfocusonyourtargetsofinterest.TheStationarySpeedSensorIIconnectstotheserialportonaPCorothercontrollerviaanRS‐232,anRS‐485,oraUSBlink.Thisinterfaceisusedtoconfiguretheunitandtomonitorthespeeddataitsendsout.TheStationarySpeedSensorcanbeconfiguredtoreportthespeedsoftargetsitacquiresinmanyformats–fromshortASCIIcharacterstringstolargerdatapacketswithspeedandstatusinformation.TheRS‐232orUSBportcanstreamspeeddataandmonitorforcommandsfromthecontrolleratthesametime.Whenconfiguredforafour‐wireconnection,anRS‐485portcanalsosendandreceivedataatthesametime.Whenconfiguredforatwo‐wireconnectionhowever,RS‐485portsonlycommunicateonewayatatime;theyneverstreamdataasaslaveonthelink.Theyonlyrespondtocommandsandspeedrequestsfromthecontroller.RS‐485linkshavethebenefitofoperatingoverlongercabledistancesfromthecontroller,andalsomultipleRS‐485unitscanbeinstalledinapoint‐to‐multipointconfigurationandcontrolledfromasingleserialportonacontroller.Thecompact,waterproofunitcanbemountedalmostanywhere.Justsupply10‐45VDCpower,andtheStationarySpeedSensorproducesserialspeeddataconfiguredforyourapplication.


6

2 SpecificationGENERAL SPECIFICATIONS Product Type Stationary Doppler Radar Speed Sensor Processor Digital Signal Processor Operating Temperatures -30°C to +70°C (-22°F to +158°F), 90% relative humidity Storage Temperatures -40°C to +85°C (-40°F to +185°F) MICROWAVE SPECIFICATIONS Operating Frequency 24.125 GHz (K-band) Frequency Stability ±50 MHz Antenna Type Planar array 3 db Beam Width 30 by 32° Power Output 18 dBm EIRP ELECTRICAL SPECIFICATIONS Supply Voltage 10 - 45 VDC

12 - 35 VAC Current (at 12 VDC nominal)

Transmitter On: 85 mA Transmitter Off: 40 mA

PHYSICAL SPECIFICATIONS Weight 13 oz (0.35 kg) Size (LxWxH) 4.4 x 3.9 x 1.6 inches

11.2 x 9.9 x 4 cm Case Material Aluminum die cast PERFORMANCE SPECIFICATIONS Stationary Speed Range Max target speed: 200 MPH (322 km/h, 174 knots, 89 meters/sec, 293

feet/sec) Accuracy ±.5 MPH ±0.3%, (±.8 KPH ±.3%)

In ones resolution, speeds are rounded to nearest integer. In tenths resolution, speeds are rounded to nearest tenth.


7

3 Physicalcharacteristics

3.1 Packagedimensions


8

3.2 ElectricalconnectionsUse the table below to identify the electrical connections in the external connector.

Pin Number

Wire Color Primary Function Secondary Function

1 Brown AC Power (factory only option) USB D+

2 Red AC Power (factory only option) USB D-

3 Orange COM B, RS-232 RX (From

Computer)

4 Yellow COM A, RS-485 RX-, Full Duplex

(From Computer) COM C, RS-485 T/R-, Half Duplex

5 Dark Green DC POWER 6 Blue AUX Relay USB V 7 Violet AUX Relay

8 Gray COM A, RS-485 TX+, Full Duplex

(To Computer) COM A, RS-485 T/R+, Half Duplex

9 Black COM A, RS-485 TX-, Full Duplex

(To Computer) COM A, RS-485 T/R-, Half Duplex

10 White COM A, RS-485 RX+, Full Duplex

(From Computer) COM C, RS-485 T/R+, Half Duplex

11 Pink COM B, RS-232 TX (To Computer) 12 Light Green GROUND

The diagrams below shows the pin out of the cable and sensor connectors as mated.

The columns in the table below show pins used for different connection options.

Pin Number

Wire Color RS-485 Full

Duplex RS-485 Half

Duplex RS-232

1 Brown 2 Red 3 Orange COM B, RX (from computer) 4 Yellow COM A, RX- COM C, T/R- 5 Dark Green DC Power DC Power DC Power 6 Blue Relay (optional) Relay (optional) Relay (optional) 7 Violet Relay (optional) Relay (optional) Relay (optional) 8 Gray COM A, TX+ COM A, T/R+ 9 Black COM A, TX- COM A, T/R-

10 White COM A, RX+ COM C, T/R+ 11 Pink COM B, TX (to computer) 12 Light Green Ground Ground Ground


9

4 ConnectingtheStationarySpeedSensor

4.1 ConnectingtotheCOMPortsTherearefourstandardCOMportsontheStationarySpeedSensorII.Notallportsareavailableonallsensormodels.COMAisanRS‐485portwhichcanbeeither4‐wirefull‐duplexor2‐wirehalf‐duplex.COMBisa2‐wirefull‐duplexRS‐232port.COMCisa2‐wirehalf‐duplexRS‐485port.COMDisafull‐duplexUSBportwhichcanhaveflowcontrolenabled.Dependingontheunit’sconfigurationone,two,threeorfourCOMportsmaybeusedatthesametime.ThefactorydefaultconfigurationhasCOMAasa4‐wirefull‐duplexRS‐485port,COMBasa2‐wirefull‐duplexRS‐232port,COMCasdisabled,andCOMDasaUSBport.ThisdefaultconfigurationallowsCOMA,COMB,andCOMDtobeusedsimultaneously.AllStationarySpeedSensorIICOMportsareconfiguredfor10bitasynchronousserialcommunicationswith1startbit,8databits,1stopbitandnoparity(8N1).ThisisstandardforPCserialports,butacustomcontrollermayneedtobemodifiedtomatchthesesettings.COMAandCOMC,theRS‐485ports,haveinter‐dependencies,soCOMBisdiscussedfirstbelow.

4.1.1 COMB–RS‐232FullDuplexPortCOMBisthesimplestporttoconnectandconfigure.ItprovidesastandardRS‐232portwithTransmitData(TX)andReceiveData(RX)signalsrelativetoitsground(GND)asshowninthediagrambelow.

ThesensortransmitsdatabychangingthevoltagelevelontheTXwirerelativetoGND.TheTXwireshouldbeconnectedtothereceivesignalonthePC/controller,andtheGNDshouldbeconnectedtothecontroller’sGNDsignal.ThecontrollerreceivesthedataonitsendbysensingthevoltagechangesrelativetoGND.Inalikemanner,thecontroller’sTXsignalisconnectedtothesensor’sRX,andthesensorreceivescontrollerdatabysensingthevoltagechangesonthatwirerelativetothesameground.Becausetherearethetwoseparatesignals(TXandRX),thelinkisdefinedasfull‐duplexmeaningthatthedatasignalscanflowinbothdirectionsatthesametimewithoutcorruptingeachother.AlimitationonRS‐232linksisdistance.Thesensorandcontrollercancommunicateovercables–butonlysofar.Sincereceiveddataissensedasavoltagerelativetothelink’sgroundsignal,asthecablegetslonger,thereceivedvoltagechangesgetlowerandnoisier

COM B RS-232

Full Duplex

TX

RX

GND

Interface

11 RS-232 TX

3 RS-232 RX

12 GROUND


10

andbecomehardertodetectreliablyresultingindegradedcommunications.Thisdistancecanbeaffectedbywiresizeinthecable,crosstalkbetweenwiresinthecableaswellasroutingthecablethroughnoisyenvironments.MostnewerPCsarenotconfiguredwiththeolder9‐pinDserialportsandhaveUSBportsinstead.Inthesecases,acquireaUSBtoserialportadaptertoperformthenecessaryconversion.Theseproductsvaryandmayormaynotworkwell.Insomecasestheyprovideundesirablebufferinganddelay,andadifferentbrandshouldbeused.

4.1.2 COMAandCOMC–RS‐485PortsRS‐485portsdifferfromRS‐232inthatRS‐485usesapairofwireswithnogroundforeachdirectionoftransmissioninsteadoftheRS‐232methodofusingonewireforeachdirectionrelativetoasharedground.InsteadofgeneratingorsensingavoltagelevelrelativetogroundlikeRS‐232,RS‐485transmitsdatabychangingthedirectionofcurrentflowintheloopcreatedbyitstwowires.Althoughstillaffectedbynoisyenvironments,RS‐485linkscanoperateoverlongerdistancesthanRS‐232becausethereceiversarenottryingtomeasuresmallerandsmallervoltagesrelativetoanoisierandnoisiergroundasthedistancesincrease.Theyjusthavetomeasurethedirectionofthecurrentflowonaclosedloop.RS‐485linkscanbeimplementedina4‐wireora2‐wireimplementation.Withfourwires,thelinkisfull‐duplexbecauseonepairofwirescanbeusedtosenddataoneway,andtheotherpaircanbeusedtosenddatatheotherwaypermittingtwo‐waysimultaneouscommunication.Withonlytwowires,thetwoendsofthelinkmustcoordinatetheirsendingofdatasothatonlyoneendtransmitsatatime.Onthishalf‐duplexlink,ifbothendstrytotransmitatthesametime,thecommunicationswillbegarbledandneitherendwillbeabletoreceiveacleansignal.Topreventmessagesinthetwodirectionsfromcolliding,theRS‐485half‐duplexprotocolrequiresthattherebeamasterononeendofthelinkandaslaveontheother.AStationarySpeedSensorIIalwaysactsastheslavedevice,andthecontrollerisalwaysthemaster.Onahalf‐duplexlinktheStationarySpeedSensorIIonlyanswerscommandsorrequestsforspeedsfromthecontroller.Itneversendsanydatawithoutreceivingarequestfirst,anditneverstreamsspeeddata. TheStationarySpeedSensorIIhastwoRS‐485ports:COMAandCOMC.COMAcanbeconfiguredtobe4‐wirefull‐duplexor2‐wirehalf‐duplex.COMCisalwaysa2‐wirehalf‐duplexport.Theyshareinternalconnectionstoonlyfourpinsonthemainconnector,soeitherCOMAcanbe4‐wirewhileCOMCisdisabled,ortheycanbothbe2‐wireports.


11

4.1.2.1 COMA–RS‐485FullDuplexPortThedefaultconfigurationfortheCOMAportis4‐wireasshownbelow.ThetwowiresforthetransmitdataareTX+andTX‐,andthetwowiresforthereceivedataareRX+andRX‐.Noticethatsincethereisapairofwiresforeachdirection,boththesensorandthecontrollercantransmitandreceiveatthesametimecreatingafull‐duplexlink.Inthisconfiguration,COMCcannotbeusedandisdisabled.

4.1.2.2 COMAandCOMC–RS‐485HalfDuplexPortsThe2‐wirehalf‐dupleximplementationonCOMAisshownbelow.Inthisconfiguration,thereisonlyonepairofwiresCOMA+andCOMA‐whichisusedforbothdirectionsofcommunication.SincethesecondpairofsignalsonCOMAisunused,COMCmaybeenabledandconnectstotheothertwopinsontheconnectorasasecond,independenthalf‐duplexport.

COM A RS-485

Full Duplex

TX+

TX-

RX+

RX-

COM C RS-485 Disabled

unused

Interface

8 COM A, RS-485 TX+

9 COM A, RS-485 TX-

10 COM A, RS-485 RX+

4 COM A, RS-485 RX-

COM A RS-485

Half Duplex

COM A+

COM A-

unused

COM C RS-485

Half Duplex

COM C+

COM C-

Interface

8 COM A, RS-485 T/R+

9 COM A, RS-485 T/R-

10 COM C, RS-485 T/R+

4 COM C, RS-485 T/R-


12

4.2 AuxiliaryRelayConnectionsTheAUXRelayContacts,pins6and7oftheinterfaceconnector,provideacontactclosureinterface.Thesensorcaninternallyshortthesepinstogetherorleavethemintheirnormalstateofanopencircuit.Onsomemodels,pin6isusedforotherpurposes,sointhosecases,pint7isshortedinternallytoground.ThisinterfaceisusedbytheStationarySpeedSensorIItoimplementanexternalstatussignalwhichisdescribedinmoredetailintheAuxPinUsagesectionofSection8.

5 CustomApplicationstoControltheStationarySpeedSensorII

ThischapterdiscussesindetailtheprotocolusedtocommunicatewiththeStationarySpeedSensorIIs.ItistheprotocolusedbySdemoapplicationssuchasDashboardandcanbeusedbydesignerstodevelopcustomapplicationstocontrolStationarySpeedSensorIIs.Abasicknowledgeofhexadecimalmathisrequired,buttheprotocolfieldsarebasically“fillintheblank”.UsingtheconfigurationprotocoldescribedinSection10,adesignercan“get”thecurrentvalueofasettingfromtheunit,“set”thesettingtoanewvalueor“change”(increment)thevalue.WhenaPCorothercontrollersendsaconfigurationcommandpackettotheStationarySpeedSensorII,theStationarySpeedSensorIIrespondsimmediatelywithapacketinthesameformat.TheonlyvalueschangedinthereturnedpacketaretheDestinationID,SourceID,ConfigurationValueandtheChecksumbytes.ThePayloadLengthmayalsochangedependingonthelengthofthereturnedConfigurationValue.ThePC/controllerisalwaysdefinedtobethemaster(ID=0x01)socommandsfromthecontrollerwillalwayshave0x01astheSourceID,andresponsesfromStationarySpeedSensorIIswillalwayshave0x01astheDestinationID.ThedefaultUnitIDforStationarySpeedSensorIIsis0x02andneednotbechangedonpoint‐to‐pointlinksbetweenasensorandaPC/controller–whetheronanRS‐232orRS‐485port.MultipleunitsusingRS‐485portscanworksimultaneouslyonasinglelinktothecontrollerinapoint‐to‐multipointconfiguration.TheIDofeachonemustbeuniqueandintherangeof2‐254(0x02–0xFE).ID0isundefinedandshouldnotbeused.ID255(0xFF)isthebroadcastaddress.EveryunitonthelinkactsoncommandssenttoID255,soacontrollercan,forexample,turnalltheradartransmittersonoroffwithasinglecommand.Beawarethateachunitalsosendsaresponsepackettoabroadcastcommand,andthattheresponsesarelikelytobegarbledonthesharedlink.Forthisreason,alwaysdisregardresponsestobroadcastcommandsunlessthereisonlyoneStationarySpeedSensorIIonthelink.Iftheresponsefromasingleunitonamultipointlinkisdesired,alwaysaddressthatunitinthecommand.AnothergooduseforabroadcastcommandistofindouttheIDofaStationarySpeedSensorIIthatmaynotberespondingtoitsexpectedaddress.Makesuretheunitistheonlyoneonthelink,andsendtheGetStationarySpeedSensorIIAddresscommand(1/116)to


13

thebroadcastDestinationID255(0xFF).Aslongasthebaudrateiscorrect,theunitwillrespondbackusingitsIDastheSourceIDintheresponsepacket.Alloftheconfigurationmethods(get,changeandset)usethesamepacketformatdefinedinSection10.ThedifferencesareintheuseoftheCommandIDandtheConfigurationValuefields.

The“change”commandandthe“get”commandaresimilarinthattheCommandIDfieldissetequaltotheSettingID(inhex)fromthelistofsettingsinSection9.

o Fora“change”command,theConfigurationValueissetto1toinstructtheStationarySpeedSensorIItoincrementthevalueby1andreturntheresultingvalue:change(1).Iftheincrementedvalueexceedsthelegalrangeforthesetting,thevaluerollsaroundtothelowestvalueintherange.

o Fora“get”command,theConfigurationValueissetto0basicallyinstructingtheStationarySpeedSensorIInottoincrementthecurrentvaluebuttosimplyreturnit.Thisisessentiallyachange(0)command.

Fora“set”command,theCommandIDfieldissetequalto0x80plustheSettingIDvalue(inhex)fromthelistinSection9(essentiallyturningonthehigh‐orderbit).TheConfigurationValuefieldissettothenewdesiredvalue.

Intheresponsepacket,theStationarySpeedSensorIIinsertsthevalueoftherequestedsettingintheConfigurationValuefield.OncetheDestinationandSourceIDsandtheConfigurationValuearecorrect,thesensorcalculatesanewchecksumandinsertsitintothepacketbeforesendingofftheresponse.

6 StreamingSpeedDataProtocolsWhenastreamingprotocolisselectedonafull‐duplexport,theStationarySpeedSensorIIsendscontinuousspeedupdatesintheselectedoutputformatataspecifiedmessageperiod.Whenoneoftheseprotocolsisselectedonahalf‐duplexport,theunitsendsonlyasinglemessageintheselectedoutputformatinresponsetoeachEAPollfromthecontroller.RefertotheCOMPortssectioninSection8forsettingsthataffectthecontentandtimingofthesemessages.Thefollowingstreamingprotocolmessageformatsaresupported.A–ASCIIsinglevisualspeedonlyB–ASCIIallvisualspeeds+statusD0–ASCIIstrongvisualspeedonly,optionaldirectionbyteD1–ASCIIstrongvisualspeedonly,optionaldirectionbyte,checksumD2–ASCIIstrongvisualspeedonly,optionaldirectionbyte,tenthsD3–ASCIIstrongvisualspeedonly,optionaldirectionbyte,relativeamplitude,tenthsD4–HEXstrongvisualspeedonlyEnhancedOutput–Hexallvisualspeeds+statusS–ASCIIvisualspeeds+statusBT–ASCIITimestampfromtheunit’sinternalreal‐timeclockDT–ASCIIDateandTimestampfromtheunit’sinternalreal‐timeclockDBG1–ASCIIinformationforalltrackedstatisticstargets(statsunitonly)LOG–ASCIIinformationforstatisticstargetsastheyarelost(statsunitonly)


14

6.1 AFormat–SingleVisualSpeedOnlyByte# Description Value1 Speedhundredsdigit(ASCII)2 Speedtensdigit(ASCII)3 Speedonesdigit(ASCII)4 CarriageReturn 0x0DAFormatmessagesare4bytesinlength.Thebaudratesettingmustbe1200orgreatertoensurethatacompletemessageissentbeforetheradarprocessesanewmessagetosend.UsetheFormatASpeedsettingforthedesiredporttoselecttheStrongvisualtargetortheFastvisualtargettobesentinthismessage.WhentheUnitResolution(Setting1/21)issetfortenths,thespeedreportedismultipliedbyten:58.5MPHisreportedas585.Thedecimalpointisassumed.AnAFormatmessagecancarryamaximumspeedintenthsof99.9.


15

6.2 BFormat–AllVisualSpeeds+StatusByte# Description Value1 MessageType 0x812 Status1 (seedetailbelow)3 Status2 (seedetailbelow)4 unused 0x20 (space)or0x30(ASCII0)5 unused 0x20(space)or0x30(ASCII0)6 unused 0x20(space)or0x30(ASCII0)7 Lockedspeedhundredsdigit(ASCII)8 Lockedspeedtensdigit(ASCII)9 Lockedspeedonesdigit(ASCII)10 Fastspeedhundredsdigit(ASCII)11 Fastspeedtensdigit(ASCII)12 Fastspeedonesdigit(ASCII)13 Targetspeedhundredsdigit(ASCII)14 Targetspeedtensdigit(ASCII)15 Targetspeedonesdigit(ASCII)16 CarriageReturn 0x0D

Status1byteBit7‐6: always=01(toforcedisplayableASCIIcharacters)Bit5: lockstatus(0=nospeedlocked,1=speedlocked)Bit4: zone(0=closing,1=away/both)Bit3: always=0Bit2: always=0Bit1: always=1Bit0: transmitterstatus(0=off,1=on)Status2byteBit7‐6: always=01(toforcedisplayableASCIIcharacters)Bit5‐4: always=00Bit3: fastlockstatus(0=nofastspeedlocked,1=fastspeedlocked)Bit2: faststatus(0=fasterdisabled,1=fasterenabled)Bit1: always=0Bit0: always=0

BFormatmessagesare16bytesinlength.Thebaudratesettingmustbe4800orgreatertoensurethatacompletemessageissentbeforetheradarprocessesanewmessagetosend.WhentheUnitResolution(Setting1/21)issetfortenths,thespeedsreportedaremultipliedbyten:58.5MPHisreportedas585.Thedecimalpointisassumed.ABFormatmessagecancarryamaximumspeedintenthsof99.9.


16

6.3 D0Format–StrongVisualSpeedOnly,OptionalDirectionByteByte# Description Value1 Optionaldirectionbyte2 Targetspeedhundredsdigit(ASCII)3 Targetspeedtensdigit(ASCII)4 Targetspeedonesdigit(ASCII)5 CarriageReturn 0x0DD0Formatmessagesareupto5bytesinlength.Thebaudratesettingmustbe1200orgreatertoensurethatacompletemessageissentbeforetheradarprocessesanewmessagetosend.Ifthedirectionbyteisnotenabledforthedesiredport,itisnotsent,andthemessagewillbea4bytemessage.Whenenabled,thedirectionbyteis‘+’forapproaching,‘‐‘forreceding,and‘?’forunknown.WhentheUnitResolution(Setting1/21)issetfortenths,thespeedreportedismultipliedbyten:58.5MPHisreportedas585.Thedecimalpointisassumed.AD0Formatmessagecancarryamaximumspeedintenthsof99.9.

6.4 D1Format–StrongVisualSpeedOnly,OptionalDirectionByte,ChecksumByte# Description Value1 Optionaldirectionbyte2 ‘S’ Theletter‘S’(0x53)3 Targetspeedtensdigit(ASCII)4 Targetspeedonesdigit(ASCII)5 CarriageReturn 0x0D6 ChecksumD1Formatmessagesareupto6bytesinlength.Thebaudratesettingmustbe2400orgreatertoensurethatacompletemessageissentbeforetheradarprocessesanewmessagetosend.Ifthedirectionbyteisnotenabledforthedesiredport,itisnotsent,andthemessagewillbea5bytemessage.Whenenabled,thedirectionbyteis‘+’forapproaching,‘‐‘forreceding,and‘?’forunknown.Thechecksumisthesumoftheprecedingbytestruncatedtotheloworder7bits.WhentheUnitResolution(Setting1/21)issetfortenths,thespeedreportedismultipliedbyten:8.2MPHisreportedas82.Thedecimalpointisassumed.AD1Formatmessagecancarryamaximumspeedintenthsof9.9.Duetothislimitedspeedrange,thetenthssettingisnotrecommendedforthisformat.


17

6.5 D2Format–StrongVisualSpeedOnly,OptionalDirectionByte,TenthsByte# Description Value1 Optionaldirectionbyte2 Targetspeedhundredsdigit(ASCII)3 Targetspeedtensdigit(ASCII)4 Targetspeedonesdigit(ASCII)5 DecimalPoint 0x2E6 TargetSpeedtenthsdigit(ASCII)7 CarriageReturn 0x0DD2Formatmessagesareupto7bytesinlength.Thebaudratesettingmustbe2400orgreatertoensurethatacompletemessageissentbeforetheradarprocessesanewmessagetosend.Ifthedirectionbyteisnotenabledforthedesiredport,itisnotsent,andthemessagewillbea6bytemessage.Ifenabled,thedirectionbyteis‘+’forapproaching,‘‐‘forreceding,and‘?’forunknown.TheUnitResolution(Setting1/21)shouldbesettotenthsforthisformattoreportspeedsproperly.


18

6.6 D3Format–StrongVisualSpeedOnly,OptionalDirectionByte,RelativeAmplitude,Tenths

Byte# Description Value1 ‘*’ Asterisk(0x2A)2 Optionaldirectionbyte3 Targetspeedhundredsdigit(ASCII)4 Targetspeedtensdigit(ASCII)5 Targetspeedonesdigit(ASCII)6 DecimalPoint 0x2E7 TargetSpeedtenthsdigit(ASCII)8 ‘,’ Comma(0x2C)9 RelativeAmplitudehundredsdigit(ASCII)10 RelativeAmplitudetensdigit(ASCII)11 RelativeAmplitudeonesdigit(ASCII)12 CarriageReturn 0x0DD3Formatmessagesareupto12bytesinlength.Thebaudratesettingmustbe4800orgreatertoensurethatacompletemessageissentbeforetheradarprocessesanewmessagetosend.Ifthedirectionbyteisnotenabledforthedesiredport,itisnotsent,andthemessagewillbean11bytemessage.Ifenabled,thedirectionbyteis‘+’forapproaching,‘‐‘forreceding,and‘?’forunknown.Amplitudevaluesarerelativeandintherange0‐160.TheUnitResolution(Setting1/21)shouldbesettotenthsforthisformattoreportspeedsproperly.

6.7 D4Format–StrongVisualSpeedOnlyByte# Description1 0x02(HEX)2 0x84(HEX)3 0x01(HEX)4 TargetSpeed(HEX)5 0x01(HEX)6 0xAA(HEX)7 0x03(HEX)Thebytesaresentjustasabove,inHEXformat.Theonlyvariableisspeed,whichisthestrongtargetspeedexpressedinHEXformat,e.g.30MPHwouldbesentas0x1E.Themaximumspeedthatcanbereportedinthisformatis255D4Formatmessagesare7bytesinlength.Thebaudratesettingmustbe2400orgreatertoensurethatacompletemessageissentbeforetheradarprocessesanewmessagetosend.WhentheUnitResolution(Setting1/21)issetfortenths,thespeedreportedismultipliedbyten:25.5MPHisreportedas255.Thedecimalpointisassumed.AD4Formatmessagecancarryamaximumspeedintenthsof25.5


19

6.8 EnhancedOutputFormat–HexAllVisualSpeeds,StatusByte# Description Value1 StartID 0xEF2 DestinationID 0xFF(broadcastaddress)3 SourceID 0x024 PacketType 0x015 PayloadLength(LSB) 0x0D6 PayloadLength(MSB) 0x00(length=0x000D =13bytes)(bytes7‐19)7 CommandID 0x008 AntennaNumber 0x019 TargetSpeed(LSB) Speedofstrongesttargetis16‐bitnumber10 TargetSpeed(MSB) (seeabove)11 FasterSpeed(LSB) Speedoffastertargetis16‐bitnumber12 FasterSpeed(MSB) (seeabove)13 LockedSpeed(LSB) Lockedspeed(strongorfast)is16‐bitnumber14 LockedSpeed(MSB) (seeabove)15 unused 0x0016 unused 0x0017 Direction (seedetailbelow)18 Status (seedetailbelow)19 Configuration (seedetailbelow)20 Checksum(LSB) Thechecksumshouldequalthe16‐bitsumofpairs

ofbytesinLSB,MSBorderstartingwithbyte#1asthefirstLSBthroughandincludingthelastbytebeforetheChecksum(inthiscase,byte#19).Inthecaseofanoddnumberofbytes,0x00isusedasthelastMSBvalue.(Seeexamplepacketbelow.)

21 Checksum(MSB) (seeabove)

DirectionbyteBits7‐6: always=00Bits5‐4: lockedspeeddirection(0=unknown,1=closing,3(‐1)=away)Bits3‐2: fastspeeddirection(0=unknown,1=closing,3(‐1)=away)Bits1‐0: targetspeeddirection(0=unknown,1=closing,3(‐1)=away)StatusbyteBit7: always=0Bit6: always=0Bits5‐3: units(000=MPH,001=km/h,010=knots,011=meters/sec,100=ft/sec)Bit2: transmitterstatus(0=off,1=on)Bit1: stronglock(1=lockedspeedisstrongesttarget)Bit0: fastlock(1=lockedspeedisfastertarget)ConfigurationbyteBits7‐3: always=00000Bits2‐1: zone(00=away,01=closing,10=bothclosingandaway)Bit0: always=0


20

EnhancedOutputFormatmessagesare21bytesinlength.Thebaudratesettingmustbe4800orgreatertoensurethatacompletemessageissentbeforetheradarprocessesanewmessagetosend.

WhentheUnitResolution(Setting1/21)issetfortenths,thespeedsreportedaremultipliedbyten:58.5MPHisreportedas585.Thedecimalpointisassumed.Sincethespeedsaresentashexvalues,anEnhancedOutputFormatmessagecaneasilycarrythehighestmeasurablespeedof321km/h(or3210intenths).

EXAMPLEPACKET(EnhancedOutputFormat)Byte# Description ExampleValues1 StartID 0xEF2 DestinationID 0xFF3 SourceID 0x024 PacketType 0x015 PayloadLength(LSB) 0x0D6 PayloadLength(MSB) 0x007 CommandID 0x008 AntennaNumber 0x019 TargetSpeed(LSB) 0x37(55MPH)10 TargetSpeed(MSB) 0x0011 FastSpeed(LSB) 0x4B(75MPH)12 FastSpeed(MSB) 0x0013 LockedSpeed(LSB) 0x37(55MPH)14 LockedSpeed(MSB) 0x0015 unused 0x0016 unused 0x0017 Direction 0x1D18 Status 0x0619 Configuration 0x0020 Checksum(LSB) 0xD421 Checksum(MSB) 0x08Checksum=0x08D4(truncatedtotheloworder2bytes)=0xFFEF+0x0102+0x000D+0x0100+0x0037+0x004B+0x0037+0x0000+0x061D+0x00


21

6.9 SFormat–ASCIIVisualSpeeds+StatusByte# Description Value1 Messagetype 0x832 Fastertargetdirection ‘A’=“away”,‘C’=“closing”3 Fastertargetspeed Hundreds(100) ‘0’–‘9’(ASCII)4 (same) Tens(10) ‘0’–‘9’(ASCII)5 (same) Ones(1) ‘0’–‘9’(ASCII)6 (same) Tenths(0.1) ‘0’–‘9’(ASCII)7 Strongesttargetdirection ‘A’=“away”,‘C’=“closing”8 Strongesttargetspeed Hundreds(100) ‘0’–‘9’(ASCII)9 (same) Tens(10) ‘0’–‘9’(ASCII)10 (same) Ones(1) ‘0’–‘9’(ASCII)11 (same) Tenths(0.1) ‘0’–‘9’(ASCII)12 Strongesttargetstrength Hundreds(100) ‘0’–‘9’(ASCII)13 (same) Tens(10) ‘0’–‘9’(ASCII)14 (same) Ones(1) ‘0’–‘9’(ASCII)15 Channelsignalstrengthratio Hundreds(100) ‘0’–‘9’(ASCII)16 (same) Tens(10) ‘0’–‘9’(ASCII)17 (same) Ones(1) ‘0’–‘9’(ASCII)18 Status 0x40(seedetailbelow)19 Carriagereturn 0x0D

StatusbyteBit7‐6: always=01(toforcedisplayableASCIIcharacters)Bit5: always=0Bit4: always=0Bits3‐0: always=0

SFormatmessagesare19bytesinlength.Thebaudratesettingmustbe4800orgreatertoensurethatacompletemessageissentbeforetheradarprocessesanewmessagetosend.Strongesttargetstrengthvaluesarerelativeandintherange1‐32.Channelsignalstrengthratioisameasureofthedirectionalityofthetarget.Ahighernumberismoredirectional.


22

6.10 BTFormat–ASCIITimestampfromtheunit’sinternalreal‐timeclockByte# Description Value1 MessageType 0x812 Status1 (seedetailbelow)3 unused 0x404 ASCIIspace 0x205 Fractionalsecondtensdigit(ASCII)6 Fractionalsecondonesdigit(ASCII)7 ASCIIspace 0x208 Secondtensdigit(ASCII)9 Secondonesdigit(ASCII)10 ASCIIspace 0x2011 Minutetensdigit(ASCII)12 Minuteonesdigit(ASCII)13 ASCIIspace 0x2014 Hourtensdigit(ASCII)15 Houronesdigit(ASCII)16 CarriageReturn 0x0D

Status1byteBit7‐6: always=01(toforcedisplayableASCIIcharacters)Bit5: always=0Bit4: always=0Bit3: always=0Bit2: always=0Bit1: always=1Bit0: transmitterstatus(0=off,1=on)

TheBTFormathasthesamebasicformatastheBFormatexceptspeedsarereplacedwithtimes.IfasensorisconfiguredforthisformatandconnectedtoaPCrunningthedemoapp,theunit’sinternalreal‐timeclock’stimeisdisplayedintheapp’sfourwindows:hhmmssfs.BTFormatmessagesare16bytesinlength.Thebaudratesettingmustbe4800orgreatertoensurethatacompletemessageissentbeforetheradarprocessesanewmessagetosend.


23

6.11 DTFormat–ASCIIDate/Timestampfromtheunit’sinternalreal‐timeclockByte# Description Value1 Yearthousandsdigit(ASCII)2 Yearhundredsdigit(ASCII)3 Yeartensdigit(ASCII)4 Yearonesdigit(ASCII)5 ASCIIslash(“/”) 0x2F6 Monthtensdigit(ASCII)7 Monthonesdigit(ASCII)8 ASCIIslash(“/”) 0x2F9 Datetensdigit(ASCII)10 Dateonesdigit(ASCII)11 ASCIIspace 0x2012 Hourtensdigit(ASCII)13 Houronesdigit(ASCII)14 ASCIIcolon(“:”) 0x3A15 Minutetensdigit(ASCII)16 Minuteonesdigit(ASCII)17 ASCIIcolon(“:”) 0x3A18 Secondtensdigit(ASCII)19 Secondonesdigit(ASCII)20 ASCIIdecimalpoint(“.”) 0x2E21 Fractionalsecondtensdigit(ASCII)22 Fractionalsecondonesdigit(ASCII)23 CarriageReturn 0x0D

TheDTFormatmessageisanASCIIstringshowingtheunit’sinternalreal‐timeclock’sdateandtimeasfollows:“2000/12/3123:59:59.99<cr>”.DTFormatmessagesare23bytesinlength.Thebaudratesettingmustbe9600orgreatertoensurethatacompletemessageissentbeforetheradarprocessesanewmessagetosend.


24

6.12 DBG1Format–ASCIIinformationforalltrackedstatisticstargetsThisformatisonlyusedinthestatsunit.Byte# Description Value1 ASCII“T” 0x542 Targetnumbertensdigit3 Targetnumberonesdigit4 ASCIIspace 0x205 TargetIDthousandsdigit6 TargetIDhundredsdigit7 TargetIDtensdigit8 TargetIDonesdigit9 ASCIIspace 0x2010 Targetdirection–ASCII“C”forclosing,

“A”foraway,“?”forunknown11 Lasttargetspeedhundredsdigit12 Lasttargetspeedtensdigit13 Lasttargetspeedonesdigit14 ASCIIspace 0x2015 Peakspeeddirection– “C”,“A”or“?”16 Peakspeedhundredsdigit17 Peakspeedtensdigit18 Peakspeedonesdigit19 ASCIIspace 0x2020 Averagespeeddirection– “C”,“A”or“?”21 Averagespeedhundredsdigit22 Averagespeedtensdigit23 Averagespeedonesdigit24 ASCIIspace 0x2025 TargetStrengthtensdigit26 TargetStrengthonesdigit27 ASCIIspace 0x2028 Targetdurationthousandsdigit29 Targetdurationhundredsdigit30 Targetdurationtensdigit31 Targetdurationonesdigit32 ASCIIspace 0x2033 CarriageReturn 0x0D

WhentheDBG1Formatisselected,theunitstreamsa33‐byteASCIImessageasdefinedabove(e.g.“T000018A040A041A040180006<cr>“)foreachofthetargetsbeingtracked.Iftheunitisconfiguredfortenthsresolution,adecimalpointandtenthsdigitisaddedtoeachspeedvalue(e.g.“T000018A040.1A041.3A040.4180006<cr>”)andthemessagelengthis39bytes.Sincetheunitcantrackupto15targets,thebaudratesettingmustbesetat115200toensurethatacompletemessageforeachtargetissentbeforetheradarprocessesnewtargetinformation.


25

6.13 LOGMessage–ASCIIinformationforstatisticstargetsastheyarelostThisformatisonlyusedinthestatsunit.Byte# Description Value1 ASCII“L” 0x4C2 ASCII“O” 0x4F3 ASCII“G” 0x474 ASCIIspace 0x205 TargetIDthousandsdigit6 TargetIDhundredsdigit7 TargetIDtensdigit8 TargetIDonesdigit9 ASCIIspace 0x2010 Yearthousandsdigit(ASCII)11 Yearhundredsdigit(ASCII)12 Yeartensdigit(ASCII)13 Yearonesdigit(ASCII)14 ASCIIslash(“/”) 0x2F15 Monthtensdigit(ASCII)16 Monthonesdigit(ASCII)17 ASCIIslash(“/”) 0x2F18 Datetensdigit(ASCII)19 Dateonesdigit(ASCII)20 ASCIIspace 0x2021 Hourtensdigit(ASCII)22 Houronesdigit(ASCII)23 ASCIIcolon(“:”) 0x3A24 Minutetensdigit(ASCII)25 Minuteonesdigit(ASCII)26 ASCIIcolon(“:”) 0x3A27 Secondtensdigit(ASCII)28 Secondonesdigit(ASCII)29 ASCIIspace 0x2030 Directionfirstcharacter(ASCII) “A”or“C”31 Directionsecondcharacter(ASCII) “W”or“L”32 Directionthirdcharacter(ASCII) “A”or“O”33 Directionfourthcharacter(ASCII) “Y”or“S”34 ASCIIspace 0x2035 ASCII“L” 0x4C36 Lasttargetspeedhundredsdigit37 Lasttargetspeedtensdigit38 Lasttargetspeedonesdigit39 ASCIIspace 0x2040 ASCII“P” 0x5041 Peaktargetspeedhundredsdigit42 Peaktargetspeedtensdigit43 Peaktargetspeedonesdigit44 ASCIIspace 0x2045 ASCII“A” 0x41


26

46 Averagetargetspeedhundredsdigit47 Averagetargetspeedtensdigit48 Averagetargetspeedonesdigit49 ASCIIspace 0x2050 TargetStrengthtensdigit51 TargetStrengthonesdigit52 ASCIIspace 0x2053 Targetclassification54 ASCIIspace 0x2055 Targetdurationthousandsdigit56 Targetdurationhundredsdigit57 Targetdurationtensdigit58 Targetdurationonesdigit59 ASCIIspace 0x2060 CarriageReturn 0x0D

WhenLOGmessagesareenabledwiththeEnableStatsLOGMessagessettingonaport,theunitgeneratesa60‐byteASCIImessageasdefinedabove(e.g.“LOG00152000/12/3123:59:59CLOSL040P041A0401920077<cr>“)foreachofthetargetslostinthelastradarmeasuringperiod.ItappendstheseLOGmessage(s)totheendoftheselectedstandardstreamingformatmessages.Iftheunitisconfiguredfortenthsresolution,adecimalpointandtenthsdigitisaddedtoeachspeedvalue(e.g.“LOG00152000/12/3123:59:59CLOSL040.1P041.3A040.41920077<cr>”)andeachLOGmessageis66byteslong.Duetothelengthofthesemessagesandthevariablenumberofthem,thebaudratesettingshouldbesetat115200toensurethatallgeneratedmessagesaresentbeforetheradarprocessesnewtargetinformation.

7 HandshakeSpeedDataProtocolsWhenahandshake(polling)protocolisselected,theStationarySpeedSensorIIsendsonlyonespeedmessageforeachspeeddatarequest(poll)itreceivesfromthecontroller.

7.1 EEPollingThesimpleEEFormatRequestisatwobytemessageasshownbelow.TheresponsefromtheStationarySpeedSensorIIisafourbytemessagecarryingfieldsforlivevisualspeed(inhexadecimal)anddirection.Sincethereisnoaddressingintherequestmessage,itisassumedthatitisdirectedtoaunitwithaStationarySpeedSensorIIIDof2;andonlyaunitwithID=2respondstoit.TheEEFormatonlyreportsonespeed‐thestrongestvisualspeedisreported.


27

RefertoUser’sManualforinstructionsonconfiguringthedemoapplicationtopollforEEFormatresponses.

7.1.1 EEFormatRequest(fromControllertoStationarySpeedSensorII)Byte# Description Value1 StartID 0xEE2 Checkbyte 0x12(0xEE+0x12=0(mod256))

7.1.2 EEFormatResponse(fromStationarySpeedSensorIItoController)

Byte# Description Value1 StartID 0xEE2‐3 Speed Bit15– validbit(1=validspeed)

Bit14‐13–direction(11=away,00=unknown,01=closingBit12–unusedBit11‐0–speedinselectedunitsandunitresolution

4 Checkbyte Bytes1‐4sumto0(mod256)

7.2 EAPollingEAPollingRequestmessagesarelikethoseforEE,buttheycontainDestinationandSourceIDsasshownbelow.ThesourceIDisalways1forthecontroller.ThedestinationIDcanbeanyvalueintherangefrom2through254,andonlyaStationarySpeedSensorIIwiththataddresswillrespond.ItsresponsetotheEApollistosendasinglespeedmessageinthestreamingformatselectedbytheOutputFormatsettingforthatport.Onlythoseportsconfiguredashalf‐duplexrespondtoEApolling.Full‐duplexportsstreamspeedmessagescontinuously.ThedemoPCapplicationdoesnotsupportEApolling.

7.2.1 EAPollingRequest(fromControllertoStationarySpeedSensorII)# Description Value1 StartID 0xEA2 DestinationID 0x02– 0xFE(2‐254)3 SourceID 0x014 Checkbyte Bytes1‐4sumto0(mod256)


28

7.3 PolledModeforD0‐D4FormatsTheD0‐D4FormatsdescribedinSection6mayalsobeusedinpolledmode.Ifpolledmodeisselectedonthedesiredport,sendinga3bytepollstringof“*P<cr>”,(0x2A0x500x0D)causesareturnofthecurrenttargetspeedintheselectedD0‐D4format.UsedinconjunctionwiththeFormatDPolledModesetting,onlyusethe*Ppollonfull‐duplex,streamingportstoreducethequantityofstreamedmessages.Onhalf‐duplexports,useEApollingasdescribedinSection7.2.ThedemoPCapplicationdoesnotsupportpollingintheD0‐D4formats.

8 ConfigurationSettingDescriptionsAllthecontrolandconfigurationsettingsavailablefortheStationarySpeedSensorIIsaredescribedinthisSection.Here,theyarearrangedinthefollowinggroupsofrelatedfunction.

1. BasicConfiguration2. COMPorts3. TargetRecognition4. TargetFiltering5. SpeedPresentation6. LockingTargets7. Real‐timeClock8. AuxPinUsage9. TrafficStatistics(statsunitonly)10. System

Thetablesatthebeginningofeachofthesectionsbelowlistthesettingsincludedineachgroup.TheSettingcolumnshowsthesettingnames.TheIDcolumnshowsthePacketTypeandIDnumbertobeusedforeachsettingwhenbuildingaConfigurationProtocolmessageorcommand(RefertoSection10fortheprotocolformat).TheDefaultcolumncontainsthefactorydefaultvaluesforeachsetting.√inthiscolumnmeansthatthesettingisnotusedtoconfigureasetting.ItisusedtorequestanactionorstatusfromtheStationarySpeedSensorII.AndtheAvailableValuescolumnshowsthepossiblevaluesforeachsetting.ThetableinSection9listsalltheavailablesettingsinorderofIDnumberforeaseofreference.

8.1 BasicConfiguration

Setting ID Default AvailableValues

TransmitterControl 1/42 10=Hold1=Transmit2=Automatic(statsunitonly)


29

Mode 1/1 0 0=Stationary

TargetDirection 1/2 00=Both1=Closing2=Away

Units 1/20 0

0=MPH1=km/h2=knots3=meters/sec4=feet/sec

UnitResolution 1/21 0 0=ones1=tenths

OSDDateTime(CCTVunitonly)

1/40 0 0=Disabled1=Enabled

OSDNTSC/PAL(CCTVunitonly) 1/56 0

0=NTSC1=PAL

OSDOnScreenAlarmDisplay(CCTVunitonly) 2/6 1

0=Disabled1=Enabled

OSDAlarmType(CCTVunitonly) 1/57 0 0=Over

1=UnderTheX/YnotationforIDsinthetableabovemeanstouseXforthePacketTypefieldinaConfigurationProtocolcommandandtouseYfortheSettingIDvalue.RefertoSection10foradescriptionoftheConfigurationProtocolformat.TheTransmitterControlsetting(1/42)turnstheradartransmitteronoroff.Thetransmittermustbeonfortheradartoregisterspeeds.TheAutomaticvalueisusedinconjunctionwithstatisticsgathering.Whenasurveyisloadedintotheunit,itincludescalendarsettingstoallowtheunittorunstatisticsduringcertaintimeperiodsoncertaindays.WhentheTransmitterControlissetforAutomatic,thestatisticsfunctioncontrolsthestateofthetransmitterbyturningitoffifnostatisticsarebeinggathered.Thisresultsinlowerpowerdrawandtheabilityrunaninterruptedsurveyformoredays.TheModesetting(1/1)isfixedinstationarymode(value=0)andcanbereadbutnotchanged.TheTargetDirectionsetting(1/2)tellstheradartolookfortargetsmovingincertaindirection(s)relativetotheunit.TheTargetDirectionvaluesareAwaytomonitorrecedingtargetsonly,ClosingtomonitorapproachingtargetsonlyandBothtomonitortargetsmovingineitherdirection.TheUnitssetting(1/20)selectstheunitsofspeedmeasurement.TheavailableoptionsareMPH,km/h,knots,meters/secandfeet/sec.TheUnitResolutionsetting(1/21)canbesettoreportspeedsinwholeunits,as25,ortenthsofunits,as25.4.TheOSD(OnScreenDisplay)settingsarefortheSpeedCCTVSensormodelonly.OSDDateTimeenablesthedateandtimetobeoverlaidonthevideo.OSDNTSC/PALselectsthevideoformat.OSDOnScreenAlarmDisplayenablesanon‐screenindicationwhenthesensordetectsavehiclespeedoutsideitsalarmsetting.AndtheOSDAlarmTypeselects


30

whetherthealarmindicationoccurswhenatargetisoverorunderthealarmspeedthreshold.

8.2 COMPorts

Setting COMAID

COMBID

COMCID

COMDID

Default AvailableValues

COMALinkConfiguration

2/16 ‐‐‐‐‐ ‐‐‐‐‐ ‐‐‐‐‐ 1 0=4852WHalfDuplex1=4854WFullDuplex

COMCLinkConfiguration

‐‐‐‐‐ ‐‐‐‐‐ 2/48 ‐‐‐‐‐ 0 0=Disabled1=4852WHalfDuplex

COMDLinkConfiguration ‐‐‐‐‐ ‐‐‐‐‐ ‐‐‐‐‐ 2/64 0

0=USBNoFlowControl1=USBw/FlowControl

BaudRate 2/17 2/33 2/49 2/65 9

5=9600baud6=19200baud7=38400baud8=57600baud9=115200baud10=230400baud11=460800baud12=921600baud

OutputFormat 2/18 2/34 2/50 2/66

2forallbut

COMC

0forCOMC

0=None(noserialoutput)1=A2=B3=D04=D15=D26=D37=D48=EE9=EnhancedOutput10=S11=DBG1(statsunitonly)12=BT13=DT

MessagePeriod 2/19 2/35 2/51 2/67 0 0–10000ms(10sec)LeadingZeroCharacter

2/20 2/36 2/52 2/68 1 0=ASCIISpace(0x20)1=ASCIIZero(0x30)

FormatASpeed 2/21 2/37 2/53 2/69 00=StrongVisualTarget1=FastVisualTarget

ZerosAfterTargetLoss

2/22 2/38 2/54 2/70 20=NoZeros1=OneZero2=StreamZeros

FormatDDirectionCharacter 2/23 2/39 2/55 2/71 0

0=Disabled1=Enabled

FormatDUpdateOnChangeOnly

2/24 2/40 2/56 2/72 0 0=Disabled1=Enabled

FormatDZero 2/25 2/41 2/57 2/73 0 0=Disabled


31

Report 1=EnabledFormatDPolledMode

2/26 2/42 2/58 2/74 0 0=Disabled1=Enabled

StatisticsLOGMessages(statsunitonly)

2/27 2/43 2/59 2/75 00=Disabled1=Enabled

StatisticsRecordMessages(statsunitonly)

2/28 2/44 2/60 2/76 00=Disabled1=Enabled

TheX/YnotationforIDsinthetableabovemeanstouseXforthePacketTypefieldinaConfigurationProtocolcommandandtouseYfortheSettingIDvalue.RefertoSection10foradescriptionoftheConfigurationProtocolformat.Usethesettingsinthissectiontoconfiguretheserialportsandthemessagestheytransmit.TheLinkConfigurationsettings(2/16,2/48and2/64)havedifferentvaluesandmeaningsforthedifferentCOMports.RefertotheConnectingtotheCOMPortssectionformoredetailonthelinkconfigurationsandtheirinter‐dependencies.COMAisanRS‐485portandcanbeconfiguredasa4‐wirefull‐duplexportorasa2‐wirehalf‐duplexport.IfCOMCisenabled,COMAcannotbeconfiguredasa4‐wirefull‐duplexport.COMCisalwaysa2‐wirehalf‐duplexport.Bydefaultitisdisabled,butitcanbeenabledifCOMAissetupfor2‐wirehalf‐duplexoperation.COMDisaUSBportandcanbeconfiguredwithorwithoutflowcontrol.AfteraLinkConfigurationsettingischanged,itwillimmediatelyreportitsnewvaluetothecontroller,butthesettingdoesnottakeeffecttoactuallychangethelinktypeuntiltheProcessBaud/LinkUpdatecommandissent.Thisissothatthelinktypedoesnotchangewhilecommunicatingoverthelink.Thenewsettingwillalsotakeeffectafterapowercycle–inthiscaseitisunnecessarytosendtheProcessBaud/LinkUpdatecommand.RefertotheSystemsubsectioninthissectionformoredetailsontheProcessBaud/LinkUpdatecommand.EachCOMporthasitsownBaudRatesetting(2/17,2/33,2/49,2/65)whichcanbesetintherangefrom9600to921600.115200isthedefault.Regardlessofthebaudrate,theserialportisalwaysconfiguredfor10bitasynchronousdatawith1startbit,8databits,1stopbitandnoparity(8N1).AfteraBaudRatesettingischanged,itwillimmediatelyreportitsnewvaluetothecontroller,butthesettingdoesnottakeeffecttoactuallychangethebaudrateuntiltheProcessBaud/LinkUpdatecommandissent.Thisissothatthebaudratedoesnotchangewhilecommunicatingoverthelink.Thenewsettingwillalsotakeeffectafterapowercycle–inthiscaseitisunnecessarytosendtheProcessBaud/LinkUpdatecommand.RefertotheSystemsubsectioninthissectionformoredetailsontheProcessBaud/LinkUpdatecommand.TheStationarySpeedSensorIIcantransmitspeedandstatusmessagesouttheserialportindifferentformatsfordifferentapplications.TheOutputFormatsetting(2/18,2/34,2/50and2/66forthefourCOMports)selectstheformatfortransmittedmessages.RefertoAppendicesAandBformoredetailsonthemessagecontentsfordifferentformats.Ahalf‐duplexRS‐485portcannotbeconfiguredtostreamoutcontinuousspeeddatabecauseitwouldneverbeabletoreceiveacommandfromthecontrolleroverthesamepair


32

ofwires.Forthisreason,half‐duplexportsarelimitedtotheEEandEAhandshakingprotocolsdescribedinSection7andonlysendoutaspeedmessagewhenrequested(orpolled)bythecontroller.Afull‐duplexport(RS‐232orRS‐485)continuouslystreamsoutmessagesinanyformatdescribedinSection6.ItcanalsorespondtoEEandD0‐D4pollingdescribedinSection7–butnotEApolling.Whenconfiguredforastreamingmessageformat,theStationarySpeedSensorIIsendsamessageeachtimetheradargeneratesnewinternalspeedmeasurements–about21timespersecondorevery48milliseconds.Thisisthedefault(andfastest)rateforstreamingmessages.Ifthatrateistoofastforauser’sapplication,itcanbesloweddownusingtheMessagePeriodsetting(2/19,2/35,2/51and2/67forthefourports).Witharangeof0to10,000milliseconds,adelayofupto10secondscanbeconfiguredforthetimebetweenthebeginningofonemessageandthenext.Thisfeatureisonlyapplicableforfull‐duplexportswhichcanstreamdata.Itisimportanttonotethatthesensoronlyhasanopportunitytosendanewmessageatitsinternaloperatingrateofonceper48ms.Thatmeansanyvalueforthissettingbetween0and48resultsina48msperiod.Anyvaluebetween49and96resultsina96msperiod.Generalizing,whateveractualvalueisselectedforthissettingresultsinmessagessentoutatarateofthenexthighermultipleof48ms.TheLeadingZeroCharactersetting(2/20,2/36,2/52and2/68forthefourports)definesthecharacterusedforleadingzerosonspeedsinASCIIvisualspeedmessageformats(A,B,D0‐D3andS).Itcanbeset=0foraspacecharacter(ASCII0x20)or=1forazerocharacter(ASCII0x30).Examplesbelowshowhowdifferentnumberswouldappearonaspeedsignorprint‐out.Space–ASCIIspacesareusedforleadingzerocharacters“500”“50”“5”“”Zero–ASCIIzerosareusedforleadingzerocharacters“500”“050”“005”“000”TheFormatASpeedsetting(2/21,2/37,2/53and2/69forthefourports)determineswhatspeedwillbereportedintheAFormatmessages:eithertheStrongvisualtargetortheFastvisualtarget.ItonlyapplieswhentheOutputFormatsettingisfortheAFormat.UsetheZerosAfterTargetLosssetting(2/22,2/38,2/54and2/70forthefourports)toconfigurewhat,ifany,streamingmessagesaresentwhennotargetispresent.Afteratargetislostandwhennovalidspeedsaredetected,theStationarySpeedSensorIIbydefaultstreamsmessageswithspeedvaluessettozero.Asanoption,aportcanbeconfiguredtostopstreamingmessagescompletelyafterthelastvalidmessageuntilanewtargetisacquired.Athirdoptionsendsone“zerospeed”messageafterthelastvalidmessagebeforehaltingthemessagestream.Thissinglemessagemightbeusedtoclearaspeedboardafterthelastspeedwasdisplayed.


33

BewareofchangingtheZerosAfterTargetLosssettingfromthedefault“streaming”value.WhennotargetispresentandtheStationarySpeedSensorIIisnottransmittinganyserialdata,thelinkcanappearbrokenordead.TheD0,D1,D2andD3formatshaveafieldforanASCIIdirectioncharacter.Itindicates“+”foranapproachingtarget,“‐“forarecedingtargetor“?”ifthedirectioncannotbedetermined.EnableordisablethisbyteinthemessageusingtheFormatDDirectionCharactersetting(2/23,2/39,2/55and2/71forthefourports). WhenstreaminginanyoftheD0‐D4formats,anotherwaytoreducespeedmessagetrafficonthelinkistosendamessageonlywhenthenewspeedreadingisdifferentfromthelast.EnableordisablethisfeaturewiththeFormatDUpdateOnChangeOnlysetting(2/24,2/40,2/56and2/72forthefourports).Whenitisenabledandtherearenotargets,theStationarySpeedSensorIIdoesnotsendoutanyspeedmessages,andthelinkmayappeardead.Toturnona“keep‐alive”signalfromtheunit,enabletheFormatDZeroReportsetting(2/25,2/41,2/57and2/73forthefourports)toconfigureittosendazero‐speedmessageevery2secondswhennotargetispresent.ThesetwosettingsarelimitedtoaportconfiguredfortheD0,D1,D2,D3orD4Format.OnelastfeaturethattheD0‐D4FormatsshareisthattheycanoperateinpolledmodeliketheEEFormat.WhentheFormatDPolledModesetting(2/26,2/42,2/58and2/74forthefourports)isenabled,aspeedmessageisonlytransmittedaftertheStationarySpeedSensorIIreceivesapollmessagefromthecontroller.Thepollis“*P”followedbyacarriagereturn(inhex:0x2A,0x50,0x0D).Nomessagesareautomaticallystreamedoutwhenthissettingisenabled.Enablethissettingonlyonfull‐duplexports.Itisonlyintendedasawaytoreducestreamedmessages.TopollforaD0‐D4formatmessageonahalf‐duplexport,useEApollingasdescribedinSection7.2.Whenthestatssensorunitistrackingtargetsandgatheringstatistics,enablingtheStatisticsLOGMessagessetting(2/27,2/43,2/59and2/75forthefourports)configuresthesensortoappendASCIIstringstotheendofstandardstreamingmessages.Thesestringsidentifytargetsthatwerelostfromtrackinginthelastradarmeasurementperiod–thisisthepointatwhichatargetisincludedinthestatisticscounts.ThisfeatureisespeciallyeffectivewhenusedinconjunctionwiththeDBG1streamingformat.TheDBG1formatstreamsoutstringsofdataaftereach48msprocessingperiodforeachtargetbeingtracked.Monitoringthisdatacantellauserhowmanytargetsarebeingtracked;whattheirlatest,fastestandaveragespeedsare;andhowlongtheyhavebeentracked.Inthestreameddatafortheperiodfollowingthelossofoneormoretargets,LOGmessageswillbeappendedtoshowthefinaldataforeachlosttargetasitissavedinthestatisticsgatheringfunction.InordertoreceiveallLOGmessages,ensurethattheMessagePeriodsetting=0sothatthesensorsendsoutmessagesforeach48msperiod.Ifthemessageperiodislonger,speedmessagesarenotsentouteachperiod;LOGmessagesforskippedperiodsarenotsaved–theyarelost.Inaddition,alwaysuseafull‐duplex,streamingporttomonitorLOGmessages.Asabove,theyarenotsavedupforwheneverthecontrollermaypollforaspeedmessage.


34

UsetheStatisticsRecordMessagessetting(2/28,2/44,2/60and2/76forthefourports)onthestatsunittoenablerawstatisticsrecordstobestreamedoutaportwhentheyaregenerated–normallyona1,2,5,10,30or60minuteperiod.ThesemessagesareonlygeneratedifthesurveyisconfiguredforExternaldata.RefertotheTrafficStatisticssectionformoredetailontracking,gatheringandstoringstatisticsdata.

8.3 TargetRecognition


FasterTargetTracking 1/13 1 0=Disabled1=Enabled

Sensitivity 1/4 16 0 (min)– 16(max)TargetAcquisitionDensity 1/55 70 0– 100%TargetAcquisitionSpan 1/122 500 1– 650 msTargetLossDensity 1/62 0 0– 100%TargetLossSpan 1/123 500 1– 650 msVisualTargetStrengthSensitivity 1/85 99 1(min)– 99(max)StatsTargetStrengthSensitivity(statsunitonly) 1/120 50 1(min)–99(max)

TheX/YnotationforIDsinthetableabovemeanstouseXforthePacketTypefieldinaConfigurationProtocolcommandandtouseYfortheSettingIDvalue.RefertoSection10foradescriptionoftheConfigurationProtocolformat.BeforecoveringthesettingsusedtoadjustthetargetrecognitionfeaturesoftheStationarySpeedSensorII,amoredetaileddefinitionof“target”isneeded.Thebasesensorunithasonlyonetypeoftargets:VisualTargets.Thesensorunitwithstatsidentifiestwodifferenttypesoftargets:VisualTargetsandStatsTargets.VisualTargetsarethetargetsthatmightdisplayona“YourSpeedIs”signonthesideoftheroad.Thespeedofatargetfarfromtheradar/signandatthedistantedgeoftheradar’srangemayflickeronthedisplayuntilitgetscloseenoughtotheradarforsolidrecognition.Basically,theradarreportswhatitactuallydetectsinrealtimeforVisualTargets.Strongtargets,fasttargetsandlockedtargetsreportedinspeedmessagesareoftheVisualTargettype.Whenthesensorwithstatsiscountingtargetsforstatistics,itshouldcounteachtargetonlyonce.AftertheradarseesaStatsTargetforthefirsttime,itneedsto“holdontoit”untilitcompletelydisappearsfromtheradar’sview–withoutthetargetdroppingoutandreappearing.Forthisandotherreasons,Statstargetsaretreateddifferentlyintheradarprocessing.Lastspeed,peakspeedandaveragespeedreportedinstatisticsmessagesareoftheStatsTargettype.TheFasterTargetTrackingsetting(1/13)allowsacquisitionandtrackingofafastervisualtargetwhenaslowertargethasalreadybeenacquiredasthestrongvisualtarget.Anexampleofatimewhenthiscapabilityishelpfuliswhenasmallcarispassingalargetruck.Thetruckisreportedasthemaintargetbecauseofitslargersize.Thecaristhenreportedasthefasttarget.


35

Sensitivity(1/4)isthemainsettingusedbytheradaraffectingtargetrecognition.Withahighersensitivity,theStationarySpeedSensorIIlooksasfarawayaspossiblefortargetsandgivestheunititshighestperformance.Itisalsoableto“see”smallertargets.Uselowersensitivityfortargetsclosertotheunitandwhenyouwanttorestrictitfromseeingsmallerobjectsorobjectsfartheroutinthebackground.Thevalueofthissettingaffectsrecognitionofbothvisualtargetsandstatstargets.Therangeofvaluesforthissettingis0through16.Use16formaximumsensitivityand1forminimumsensitivity.Asensitivitysettingof0allowsnotargetacquisitionatall.Standardradaroperationreportsatargetspeedwhenanalysisofitsmostrecentdataresultsinatargetmeetingthesensitivityrequirementsoutlinedabove.Onceatargetisacquired,itistrackeduntilitnolongermeetsthoserequirements.TheTargetAcquisitionandLosssettingsgivemorecontroloverthecriteriausedtoacquireandthenloseatarget.Theyaffectrecognitionofbothvisualandstatstargets.TheTargetAcquisitionDensityandTargetAcquisitionSpansettings(1/55and1/122)areusedasapairtoaffectwhentheradaracquiresatarget.TheDensityvaluespecifiesapercentage(0‐100),andtheSpanvaluespecifiesalengthoftime(1‐650ms).Asanexample,usingvaluesof70%and500msconfigureasensortoacquireatargetonlyafteritseesit70%ofthetimeoveranyhalf‐secondperiod.TheTargetLossDensityandTargetLossSpansettings(1/62and1/123)areusedinasimilarwaytotelltheradarwhenitshouldloseatarget.Forexample,valuesof0%and500mstellittoholdontoatargetuntilitdoesn’tseeitatall(0%ofthetime)forafullhalf‐second.WhereastheSensitivitysettingdescribedabovecomparesthetargetstrengthtotheambientnoisefromotherradarreflections(signaltonoiseratio)todeclarerecognitionofatarget,theTargetStrengthSensitivitysettingscanbeusedtorecognizeorsuppresstargetsdependingpurelyonthetarget’sstrength.Ahighervalueallowssmaller,lowerstrengthtargetstobeacquired.Alowervaluerequiresthetargettobelarger/closerbeforeitisacquired.TheVisualTargetStrengthSensitivitysetting(1/85)onlyaffectsrecognitionofvisualtargets,andtheStatsTargetStrengthSensitivitysetting(1/120)onlyaffectsrecognitionofstatstargets.

8.4 TargetFiltering

Setting ID Default AvailableValuesLowSpeedThreshold 1/7 0 0‐ 322HighSpeedThreshold 1/11 200 0‐ 322

TheX/YnotationforIDsinthetableabovemeanstouseXforthePacketTypefieldinaConfigurationProtocolcommandandtouseYfortheSettingIDvalue.RefertoSection10foradescriptionoftheConfigurationProtocolformat.Severalsettingscanbeusedtofilteroutundesiredtargets.Thefirststepistoignoretargetsthatarenotmovinginthedesireddirection.ThisisaccomplishedwiththeTarget


36

Directionsetting(1/2)asdescribedinthefirstsubsectionofthissection,BasicConfiguration.SlowtargetspeedscanbefilteredoutusingtheLowSpeedThresholdsetting(1/7).Therangeofvaluesforthissettingis0through322.Anytargetswithaspeedslowerthanthisthresholdareignored.Thisfeaturecanbehelpfulwhenmonitoringtrafficaroundslowmovingobjectslikepedestriansortreesblowinginthewind.Inalikemanner,fasttargetspeedscanbefilteredoutusingtheHighSpeedThresholdsetting(1/11)whichalsohasarangeof0‐322.Targetswithspeedshigherthanthisthresholdarealsoignored.ItisimportanttosettheHighSpeedThresholdhigherthantheLowSpeedThresholdorelsealltargetswillbeignored.

8.5 SpeedPresentation

Setting ID Default AvailableValuesCosineAngle1 1/18 0 0‐45degrees(1° increments)CosineAngle2 1/19 0 0‐45degrees(1° increments)

HoldoverTime 1/88 2 0– 10=0– 10seconds11=Forever

TheX/YnotationforIDsinthetableabovemeanstouseXforthePacketTypefieldinaConfigurationProtocolcommandandtouseYfortheSettingIDvalue.RefertoSection10foradescriptionoftheConfigurationProtocolformat.Theinternalmeasurementsmadebytheradararecorrectedand/orheldaftertargetlossdependingonthesettingsinthissection.StationarySpeedSensorIIsmeasurethemostaccuratespeedswhentargetsaremovingdirectlytowardorawayfromthem.Unfortunately,itisusuallynotadvisabletomountonedirectlyinthepathoftraffic.Aswithanyradar,aimingatanangleresultsinlowerspeeds.Atslightanglestheerrorisverysmall;howeveratlargeranglestheerrorcanbecomesubstantial.


37

TheselowspeedscanbeautomaticallycorrectedbythesensorusingtheCosineAnglesettings(1/18and1/19).Twosettingsareprovidedsotwocorrectionscanbemadesimultaneously.Thetwosettingsareindependentandinterchangeable.Eitheronecanbeusedbyitselforwiththeotherasapair.Onecosineanglesettingmightbeusedforthehorizontal“beside‐the‐road”angleshowninthediagramabove.Theothermightbesetforthevertical“over‐the‐road”angleiftheStationarySpeedSensorIIismountedonapole.Whentheaimoftheradarisalignedwiththetarget’spath,bothanglesshouldbesetfor0degrees,andnocorrectiontakesplace.Therangeofthesesettingsis0‐45degrees.TheHoldoverTimesetting(1/88)isusedtosmooththespeedreadingsduringintermittentdropouts.Itonlyaffectsvisualtargets(notstatstargets).Whentheunitisconfiguredforastreamingmessageformat,amessageistransmittedouttheCOMportforeachradarmeasurementperiod–every48ms.Theradarreturnsaspeedofzeroifitisunabletodetermineavalidspeedforanygivenmeasurementtime.Whenconditionsarenoisyorwhenthetargetisverysmallandalmostoutofrange,thesemissedmeasurements(ordropouts)canmaketheseriesofspeedreportsappearerraticorjumpy.Ratherthaninterjectingdropoutsintheseriesforinvalidspeeds,thelastvalidreadingcanberepeated(orheldover)toprovidecontinuityfornoisy,intermittenttargets.TheHoldoverTimesettingcanbesetfor0‐10secondsin1secondincrements,oritcanbesettoForevertoholdthelastspeedtheradarsawuntilanewoneisacquired.

8.6 LockingTargets


StrongLockEnable 1/15 1 0=Disabled1=Enabled

FastLockEnable 1/14 1 0=Disabled1=Enabled

StrongLock 1/43 0 0=Release1=Lock

FastLock 1/44 00=Release1=Lock

TheX/YnotationforIDsinthetableabovemeanstouseXforthePacketTypefieldinaConfigurationProtocolcommandandtouseYfortheSettingIDvalue.RefertoSection10foradescriptionoftheConfigurationProtocolformat.Whilemonitoringatarget’svisualspeed,thesensorcan“lock‐in”thespeedatanypointintimewhilestilltrackingthechangingspeedofthetarget(track‐throughlock).Eitherthespeedofthestrongvisualtargetorthefastvisualtargetcanbelockedbutnotbothatthesametime.Statstargetscannotbelocked.Tomonitorlockedtargets,usetheBorEnhancedOutputFormatwhichhavefieldstoreportthelockedspeed.TheStrongLockEnablesetting(1/15)disablesorenablesthelockingfeatureforstrongvisualtargets.Iflockingoffastvisualtargetsisdesired,inadditiontoenablingFasterTargetTrackingasdescribedintheTargetRecognitionsubsectionofthissection,theFastLockEnablesetting(1/14)mustalsobeenabled.


38

LockandreleasespeedsusingtheStrongLock(1/43)andFastLock(1/44)commands.Thecurrentlockedspeed,strongorfast,mustbereleasedbeforeanyotherspeedcanbelocked.

8.7 Real‐timeClock

Setting ID Default AvailableValuesRTCCalibrationFactor 1/106 0x80 0x80‐ 0xC8RTCYear 1/107 none 2000‐ 2399RTCMonth 1/108 none 1‐ 12RTCDate 1/109 none 1‐ 31RTCHour 1/110 none 00‐ 23RTCMinute 1/111 none 00‐ 59RTCSecond 1/112 none 00‐ 59RTCFractionalSecond 1/113 none 0‐ 99RTCWeekday 1/124 none 1(Monday)– 7(Sunday)

TheX/YnotationforIDsinthetableabovemeanstouseXforthePacketTypefieldinaConfigurationProtocolcommandandtouseYfortheSettingIDvalue.RefertoSection10foradescriptionoftheConfigurationProtocolformat.Thereal‐timeclockinthesensorhasaninternalbatteryandkeepsthecurrenttimeanddatewhethertheunitispoweredupornot.Thefollowingsettingscanbechangedorreadtosetorgetthecurrenttimeanddate:TheRTCCalibrationFactorsetting(1/106)acceptsvaluesbetween128(0x80)and200(0xC8).Ahighervaluewillspeeduptheclockandalowervaluewillslowitdown.TheRTCYearsetting(1/107)holdsavaluebetween2000and2399.TheRTCMonthsetting(1/108)holdsavaluebetween1and12.TheRTCDatesetting(1/109)holdsthedayofmonthvaluebetween1and31.TheRTCHoursetting(1/110)holdsa24hourclockvaluebetween0and23.TheRTCMinutesetting(1/111)holdsavaluebetween0and59.TheRTCSecondsetting(1/112)holdsavaluebetween0and59.TheRTCFractionalSecondsetting(1/113)holdsavaluebetween0and99representing0to0.99seconds.TheRTCWeekdaysetting(1/124)holdsthedayofweekvaluebetween1and7where1=Mondayand7=Sunday.


39

8.8 AuxPinUsage


AuxPinConfiguration 1/16 0

0=Disabled1=SpeedAlarm2=StatsStatus(statsunitonly)

AlarmSpeedThreshold 1/12 322 0‐ 322AlarmType(appearsunderBasicConfigurationforCCTVsensor)

1/57 0 0=Over1=Under

TheX/YnotationforIDsinthetableabovemeanstouseXforthePacketTypefieldinaConfigurationProtocolcommandandtouseYfortheSettingIDvalue.RefertoSection10foradescriptionoftheConfigurationProtocolformat.TheStationarySpeedSensorIIcanprovideanexternalsignalfornotificationofaconditionorstatus.RefertotheConnectingtheStationarySpeedSensorII/AuxiliaryRelayConnectionssectionfordetailsonthephysicalconnectionoftheAUXcontactsused.

UsetheAuxPinConfigurationsetting(1/16)toenableeitheraspeedalarmorastatsstatusnotification.WhenconfiguredforSpeedAlarm,theAUXrelayactivateswhenavisualstrongtargetistravelingfasterorslowerthanapresetalarmthreshold.WhenconfiguredforStatsStatus(onstatssensorsonly),theAUXsignalcanbeconnectedtoanLEDtoprovideareadinessindicatorfromtheunit.Aslongastheradartransmitterisoff,theAUXcontactsareopen.Whenthetransmittersison,thecontactsclosefor0.5secondsandopenfor4.5secondsforaslowblinksignalingthattheunitismonitoringtrafficforstats.Aseachtargetisloggedtheunitperformsaquickersequenceof0.25secondsclosedand0.25secondsopen.WhentheSpeedAlarmfeatureisenabled,usetheAlarmSpeedThresholdsetting(1/12)tosetupthetargetspeedwherethespeedalarmactivates.Therangeofvaluesforthissettingis0‐322.Whenastrongvisualtargetistravelingfaster(orslower)thanthisthreshold,thestateoftheAUXcontactschangesfromanopencircuittoacontactclosure.Whenthetargetslowsdown(orspeedsup)outofthealarmrange,thecontactclosureopensagain.UsetheAlarmTypesetting(1/57)todeterminewhetherthealarmconditionistriggeredbyatargettravelingoverorunderthealarmspeedthreshold.

8.9 TrafficStatistics(statsunitonly)


StatisticsMonitor 1/9 0 0=Disabled1=Enabled

MinimumTrackingDistance 2/4 200 0– 500feet


40

ClassificationTraining 2/96 00=Disabled1=Enabled

TrainingStatus 2/97 0 0=Incomplete1=Complete

GetTrainingData 2/98 √1=Requestcurrentstatusoftrainingdata(readonly)

AwayClass1Threshold 2/99 84 0– 99AwayClass2Threshold 2/100 68 0– 99AwayClass3Threshold 2/101 53 0– 99AwayClass4Threshold 2/102 37 0– 99AwayClass5Threshold 2/103 0 0– 99ClosingClass1Threshold 2/104 84 0– 99ClosingClass2Threshold 2/105 68 0– 99ClosingClass3Threshold 2/106 53 0– 99ClosingClass4Threshold 2/107 37 0 – 99ClosingClass5Threshold 2/108 0 0– 99

TheX/YnotationforIDsinthetableabovemeanstouseXforthePacketTypefieldinaConfigurationProtocolcommandandtouseYfortheSettingIDvalue.RefertoSection10foradescriptionoftheConfigurationProtocolformat.TheStationarySpeedSensorIImodelwithstatscancountvehiclesandstorestatisticsontheirspeedsandclassificationsovertime.MostoftheuserinterfaceforthestatisticsfunctionsisprovidedintheStalkerSTATSPCapplication,butsomefunctionscanbehandledwiththesesettings.TheStatisticsMonitorsetting(1/9)turnsonoroffthebasicstatisticsgatheringfunctions.Itmustbeenabledforstatisticstobecounted.TheMinimumTrackingDistancesetting(2/4)canbeusedtofilteroutsomeshort‐livedtargetsduringasurvey.Anidealsurveylocationwouldnothaveintersectingstreetsordrivewaysalongthepathofthesurveyedvehicles,butsometimesthiscannotbeavoided.Tokeepfromcountingvehiclesthatonlytravelaportionofthesurveypathbyturningontooroffoftheroadway,settheMinimumTrackingDistanceforadistance(infeet)thatatargetneedstotraveltobecountedinthesurvey.Therangeofsettingsis0‐500feetwithadefaultof200feet.Oneofthequalitiesofstatstargetsistheirclassification:Class1(largertargets)throughClass5(smallertargets).Thesensordeterminesatarget’sclassbasedontheamountofinitialtransmittedradarenergythatbouncesoffthetargetandisreturnedtothesensor.Thisreturnedenergydependsnotonlyonthephysicalsizeofthetargetbutalsothetarget’sshape,surfacetopographyandphysicalbearingtotheradar.Insomecases,alargetargetmayreturnlessenergythanasmallertarget.Sowhiletargetclassesmaynotcorrelateexactlytodifferenttypesofvehicles,Class1targetsappearrelativelylargertotheradarthanClass2andsoon.Thesensorcalculatestheintensity,intherange1‐99,ofthereturnedradarsignalforeachtargetittracks.ItthenassignsaClassdependingonwherethatintensityfallsintherangeofClassThresholds.ThetenthresholdsaresplitintofiveforAwayClassnThreshold


41

settings(2/99–2/103)andfiveforClosingClassnThresholdsettings(2/104–2/108).Thereareseparatesetsofthresholdsforclosingvs.awaytargetsbecausetheradarmaybesetupononesideofaroadway,andclosingtargetslookdifferenttoitthanawaytargetswhichtravelatmoreofanangletotheradar.Otherinstallationlocationsprovidesimilardifferences.Therearedefaultsettingsforthethresholds,buttheymaybesettoanylevelbytheuser,ortheunitmaytrainitselffortherangeoftargetsitseesinaparticularinstallation.ThisisaccomplishedbysettinguptheradaronasurveysiteandturningontheClassificationTrainingsetting(2/96).Theradarwillthenmonitorthenext100targetsitsees,calculatetheintensityrangeofthosetargets,andthenautomaticallysetthethresholdsevenlyspacedwithinthatrange.Thistraininggivesreasonableassurancethatthestatisticssurveywillprovideresultswithtargetsspreadthroughouttheclassrange.Notethatiftheunitisconfiguredforonlyonedirectionoftraffic,AwayorClosing,itonlytracks100targetsmovinginthatdirection.IfitissetupforBothdirections,ittracks100awaytargetstodeterminetheAwayThresholdsand100closingtargetsfortheClosingThresholds.AssoonastheClassificationTrainingisenabled,theTrainingStatussetting(2/97)isautomaticallysettoIncomplete.Afterthetrainingiscomplete,theClassificationTrainingsettingisautomaticallydisabled,theTrainingStatusisautomaticallysettoComplete,andtheClassThresholdsettingsareupdatedwiththenewlycalculatedthresholds.Whiletrainingisinprogress,itispossibletomonitorhowmanyofthe100targetshavebeenregisteredandtheirintensities.AfterreceivingtheGetTrainingDatacommand(2/98),theunitrespondsbysendingoutanASCIIstreamofdata:an“A”followedbytheintensitiesofthe100Awaytargetsandthena“C”followedbythe100Closingintensities.Theintensitiesareinitiallyreportedas0andarethenreplacedbytheintensitiesofactualtargetsastheyaretracked.Thetrainingsettingsarerememberedthroughpowercycles,soitispossibletoconfiguretheunittotrainandpoweritdownbeforegoingouttothesurveysite.Then,on‐site,simplyaimtheunitandpoweritup.Itwillthenautomaticallystarttotrainasitseestargets.Aftercompletionoftraining,itthenautomaticallystartstogatherstatisticsbasedonthetrainedclassificationthresholds.Thetargetsmonitoredduringthetrainingperiodarenotincludedinthestatisticscounts.


42

8.10 System

Setting ID Default AvailableValuesResetUnit 1/84 √ 1=Requestaresetoftheunit

ForceProductDefaults 1/74 00=NoAction1=ForceSettings

ProcessBaud/LinkUpdate 2/3 0 0=NoUpdate1=Update

GetProductID 1/37 √ 1=RequesttheProductID(readonly)

GetProductType 1/79 √ 1=RequesttheProductType(readonly)

GetSoftwareVersion 1/81 √1=RequesttheSoftwareVersion(readonly)

GetHardwareID 1/82 √1=RequesttheHardwareID(readonly)

TheX/YnotationforIDsinthetableabovemeanstouseXforthePacketTypefieldinaConfigurationProtocolcommandandtouseYfortheSettingIDvalue.RefertoSection10foradescriptionoftheConfigurationProtocolformat.The“Get”settings(orcommands)inthissectionareusedtoquerytheStationarySpeedSensorIIforinformationaboutitself.Thevaluescannotbechangedbytheuser;theyareconstantanddependonthemodeloftheunitandversionofsoftwareloadedintoit.Toresetaunit,sendtheResetUnitcommand(1/84)withavalueof1.Thiscausestheunittoresetitselfafteratenseconddelay.Nosettingsarechanged,buttheunitisrestarted.UsetheForceProductDefaultscommand(1/74)toreturnaunittoaknownstate.Allsettingsareresettothedefaultvaluesasshowninthissection. TheProcessBaud/LinkUpdatecommand(2/3)isusedaftertheLinkConfigurationandBaudRatecommandsasdescribedintheCOMPortssubsectioninthissection.Sincebothofthosecommandschangebasiclinkproperties,ifthesensoractedonthemimmediatelyafterreceivingthem,itsresponsewouldbeinadifferentbaudrateorthelinktypewouldchangebeforetheresponsegoesout.Theconsequencescouldbeworseifacontrollertriestochangemultiplesettings(ashappenswiththeDashboarddemoPCapp)withabaudrateorlinktypechangeinthemiddleofthesequenceofcommands:thefirstcommandswouldgothroughsuccessfully,butanycommandsafterthebaudrateorlinktypechangedwouldnot.Onceanybaudrateorlinkconfigurationsettingshavebeenchangedwithoutactuallyaffectingthecommunicationslink,sendingtheProcessBaud/LinkUpdatecommandwithavalueof1makesthosechangestakeeffect.Onreceivingthecommand,theunitwillimmediatelyreconfiguretheport(orportsifmorethanoneCOMportischanged)andsenditsresponseinthenewbaudrateand/oroverthenewlinktype.Aftersendingthecommand,thePC/controllershouldexpectthesechangesandreconfigureitsownconfigurationonitssideofthelink.Iftheuserhasaccesstothesensor’spowerandcanturnitonandoff,useoftheProcessBaud/LinkUpdatecommandisnotnecessary.Afteranybaudrateorlinktypesettingshavebeenchanged,simplyturningtheunitoffandbackonwillmakethenewsettingstakeeffect.


43

AStationarySpeedSensorIIrespondstoaGetProductIDcommand(1/37)withanASCIIstringcontainingtheproductmodelnameandtheversionofsoftwareloadedintoit.Anexampleis“StationaryIIVer:1.1.0”.TheresponsetoaGetProductTypecommand(1/79)isathreebytehexadecimalvalueassociatedwiththemodeloftheStationarySpeedSensorII.Thevaluesare: 0x52A200 StationaryIISpeedSensor 0xFEDB0B TrafficStatisticsSensor 0xDF1AEE SpeedCCTVSensorTheGetSoftwareVersioncommand(1/81)returnsanASCIIstringwiththeloadedsoftware’sversion.e.g.“1.0.0.0”TheGetHardwareIDcommand(1/82)returnsa32‐byteASCIIstringwiththeinternalHardwareIDuniquetoeachsensor.

9 ConfigurationSettingsTableAllofthesettingsavailablefortheStationarySpeedSensorIIarelistedbelowinnumericalorderoftheSettingIDswhichareshownindecimalandhexadecimalformat.TheSettingDescriptioncolumnshowsthesettingnames.ItalsohasreferencestothesubsectioninSection8wherethesettingisdescribedindetail.

PacketType

SettingIDSettingDescription

Dec Hex

1 1 0x01 Mode1–BasicConfiguration

1 2 0x02 TargetDirection1–BasicConfiguration

1 4 0x04 Sensitivity3–TargetRecognition

1 7 0x07 LowSpeedThreshold4–TargetFiltering

1 9 0x09StatisticsMonitor (statsunitonly)

9–TrafficStatistics

1 11 0x0B HighSpeedThreshold4–TargetFiltering

1 12 0x0C AlarmSpeedThreshold8–AuxPinUsage

1 13 0x0D FasterTargetTracking3–TargetRecognition

1 14 0x0E FastLock Enable6–LockingTargets


44

1 15 0x0F StrongLockEnable6–LockingTargets

1 16 0x10 AuxPinConfiguration8–AuxPinUsage

1 18 0x12 CosineAngle15–SpeedPresentation

1 19 0x13 CosineAngle25–SpeedPresentation

1 20 0x14 Units1–BasicConfiguration

1 21 0x15 UnitResolution1–BasicConfiguration

1 37 0x25 GetProductID10‐System

1 40 0x28OSDDateTime(CCTVunitonly)

1–BasicConfiguration

1 42 0x2A TransmitterControl1–BasicConfiguration

1 43 0x2B StrongLock6–LockingTargets

1 44 0x2C FastLock6–LockingTargets

1 55 0x37 TargetAcquisitionDensity3–TargetRecognition

1 56 0x38OSDNTSC/PAL(CCTVunitonly)


1 57 0x39 AlarmType8–AuxPinUsage

1 62 0x3E TargetLossDensity3–TargetRecognition

1 74 0x4A ForceProductDefaults10‐System

1 79 0x4F GetProductType10‐System

1 81 0x51 GetSoftwareVersion10‐System

1 82 0x52 GetHardwareID10‐System

1 84 0x54 ResetUnit10‐System

1 85 0x55VisualTargetStrengthSensitivity

3–TargetRecognition

1 88 0x58 HoldoverTime5–SpeedPresentation

1 106 0x6A RTCCalibrationFactor7–Real‐timeClock

1 107 0x6B RTCYear7–Real‐timeClock

1 108 0x6C RTCMonth7–Real‐timeClock

1 109 0x6D RTCDate7–Real‐timeClock


45

1 110 0x6E RTCHour7–Real‐timeClock

1 111 0x6F RTCMinute7–Real‐timeClock

1 112 0x70 RTCSecond7–Real‐timeClock

1 113 0x71 RTCFractionalSecond7–Real‐timeClock

1 120 0x78StatsTargetStrengthSensitivity(statsunitonly)

3–TargetRecognition

1 122 0x7A TargetAcquisitionSpan3–TargetRecognition

1 123 0x7B TargetLossSpan3–TargetRecognition

1 124 0x7C RTCWeekday7–Real‐timeClock

2 3 0x03 ProcessBaud/LinkUpdate10–System

2 4 0x04MinimumTracking Distance(statsunitonly)


2 6 0x06OSDOnScreenAlarmDisplay(CCTVunitonly)


2 16 0x10 COMA LinkConfiguration2–COMPorts

2 17 0x11 COMA BaudRate2–COMPorts

2 18 0x12 COMA OutputFormat2–COMPorts

2 19 0x13 COMA MessagePeriod2–COMPorts

2 20 0x14COMA LeadingZeroCharacter

2–COMPorts

2 21 0x15 COMA FormatASpeed2–COMPorts

2 22 0x16COMA ZerosAfterTargetLoss

2–COMPorts

2 23 0x17COMA FormatDDirectionCharacter

2–COMPorts

2 24 0x18COMA FormatDUpdateOnChangeOnly

2–COMPorts

2 25 0x19COMA FormatDZeroReport

2–COMPorts

2 26 0x1ACOMA FormatDPolledMode

2–COMPorts


46

2 27 0x1BCOMA StatisticsLOGMessages(statsunitonly)

2–COMPorts

2 28 0x1CCOMA StatisticsRecordMessages(statsunitonly)

2–COMPorts

2 33 0x21 COMB BaudRate2–COMPorts

2 34 0x22 COMB OutputFormat2–COMPorts

2 35 0x23 COMB MessagePeriod2–COMPorts

2 36 0x24COMB LeadingZeroCharacter

2–COMPorts

2 37 0x25 COMB FormatASpeed2–COMPorts

2 38 0x26COMB ZerosAfterTargetLoss

2–COMPorts

2 39 0x27COMB FormatDDirectionCharacter

2–COMPorts

2 40 0x28COMB FormatDUpdateOnChangeOnly

2–COMPorts

2 41 0x29COMB FormatDZeroReport

2–COMPorts

2 42 0x2ACOMB FormatDPolledMode

2–COMPorts

2 43 0x2BCOMB StatisticsLOGMessages(statsunitonly)

2–COMPorts

2 44 0x2CCOMB StatisticsRecordMessages(statsunitonly)

2–COMPorts

2 48 0x30 COMC LinkConfiguration2–COMPorts

2 49 0x31 COMC BaudRate2–COMPorts

2 50 0x32 COMC OutputFormat2–COMPorts

2 51 0x33 COMC MessagePeriod2–COMPorts

2 52 0x34COMC LeadingZeroCharacter

2–COMPorts

2 53 0x35 COMC FormatASpeed2–COMPorts

2 54 0x36COMC ZerosAfterTargetLoss

2–COMPorts


47

2 55 0x37COMC FormatDDirectionCharacter

2–COMPorts

2 56 0x38COMC FormatDUpdateOnChangeOnly

2–COMPorts

2 57 0x39COMC FormatDZeroReport

2–COMPorts

2 58 0x3ACOMC FormatDPolledMode

2–COMPorts

2 59 0x3BCOMC StatisticsLOGMessages(statsunitonly)

2–COMPorts

2 60 0x3CCOMC StatisticsRecordMessages(statsunitonly)

2–COMPorts

2 64 0x40 COMD LinkConfiguration2–COMPorts

2 65 0x41 COMD BaudRate2–COMPorts

2 66 0x42 COMD OutputFormat2–COMPorts

2 67 0x43 COMDMessagePeriod2–COMPorts

2 68 0x44COMD LeadingZeroCharacter

2–COMPorts

2 69 0x45 COMD FormatASpeed2–COMPorts

2 70 0x46COMD ZerosAfterTargetLoss

2–COMPorts

2 71 0x47COMD FormatDDirectionCharacter

2–COMPorts

2 72 0x48COMD FormatDUpdateOnChangeOnly

2–COMPorts

2 73 0x49COMD FormatDZeroReport

2–COMPorts

2 74 0x4ACOMD FormatDPolledMode

2–COMPorts

2 75 0x4BCOMD StatisticsLOGMessages(statsunitonly)

2–COMPorts

2 76 0x4CCOMD StatisticsRecordMessages(statsunitonly)

2–COMPorts


48

2 96 0x60ClassificationTraining(statsunitonly)


2 97 0x61TrainingStatus (statsunitonly)


2 98 0x62GetTrainingData(statsunitonly)


2 99 0x63AwayClass1Threshold(statsunitonly)










2 104 0x68ClosingClass1Threshold(statsunitonly)


2 105 0x69ClosingClass2Threshold(statsunitonly)


2 106 0x6AClosingClass3Threshold(statsunitonly)


2 107 0x6BClosingClass4Threshold(statsunitonly)


2 108 0x6CClosingClass5Threshold(statsunitonly)


10 ConfigurationProtocolRefertothechapteronCustomApplicationstoControlStationarySpeedSensorIIsfordetailsonusingthisprotocoltocontrolStationarySpeedSensorIIs.Configurationpacketformat# Description Value1 StartID 0xEF2 DestinationID 2– 254(0x02– 0xFE)Forbroadcast:255(0xFF)3 SourceID 0x014 PacketType 0x01or0x025 PayloadLength(LSB) ThePayloadLengthisa2‐bytewordwhichisthe


49

numberofbytesstartingwithbyte#7throughandincludingthelastbytebeforethechecksumbytes.

6 PayloadLength(MSB) (seeabove)7 CommandID/

SettingIDGetmethod:CommandIDvalue=SettingIDinhex(andbyte#9=0x00):causestheSpeedSensortoreturnthecurrentsettingChangemethod:CommandIDvalue=SettingIDinhex(andbyte#9=0x01):causestheSpeedSensortoselectthenextpossiblesettingSetmethod:CommandIDvalue=SettingIDinhex+0x80:causestheSpeedSensortousethevalueinbyte#9asthenewconfigurationsetting

8 AntennaNumber Reserved(use0x00or0x01)9 ConfigurationValue Getmethod:Value=0x00

Changemethod:Value=0x01Setmethod:Value=newdesiredvalueinhex(formulti‐bytevalues,theLSBisfirstandisfollowedbythemoresignificantbytesinlowtohighorder)

10 Checksum(LSB) Thechecksumshouldequalthe16‐bitsumofpairsofbytesinLSB,MSBorderstartingwithbyte#1asthefirstLSBthroughandincludingthelastbytebeforetheChecksum(inthiscase,byte#9).Inthecaseofanoddnumberofbytes,0x00isusedasthelastMSBvalue.(Seeexamplebelow.)

11 Checksum(MSB) (seeabove)ThefollowingisanexampleshowingacommandtosetUNITStokm/h.# Description Value1 StartID 0xEF2 DestinationID 0x023 SourceID 0x014 PacketType 0x005 PayloadLength(LSB) 0x03 (length=0x0003=3bytes)6 PayloadLength(MSB) 0x007 CommandID 0x94 =0x14(Setting20)+0x80(setmethod)8 AntennaNumber 0x009 ConfigurationValue 0x01 (km/h)10 Checksum(LSB) 0x8811 Checksum(MSB) 0x03Checksum=0x0388(truncatedtotheloworder2bytes)=0x02EF+0x0001+0x0003+0x0094+0x0001


50

11 Sensorvariations

11.1 200‐0880‐52,53

11.1.1 SummaryThesesensorsincludethefollowingchangestothebasesensor(200‐0880‐00,01):

Theelectricalconnectorismovedfromthesidetotherearofthesensor. AUSBcommunicationsportisadded.ThesensorisaUSBslavecomplaintwithUSB

2.0requirements.Anexternal(host)5voltsmustbesuppliedtothesensortooperatetheUSBcommunicationsport.Thisisanadditionalcommunicationport;nopreviouslyavailablecommunicationportswereremoved.

TheACvoltageinputwasremovedtoallowfortheadditionoftheUSBcommunicationsport.

TheexternalAUXrelayfunctionwaschangedfroma2lineswitchclosurefunctiontoasinglegroundedlineoperation.Thisisanormallyopenswitchonpin7whichisconnectedtosensorgroundwhentheswitchisclosed.

11.1.2 MechanicalDescription


51

11.1.3 ElectricalConnectionTheelectricalconnectionsontherearportareasshownhere.Note:TheUSBoperationrequiresthehost’s5voltsbeplaceonthepin6.Allothersensorfunctionswilloperatenormallywithoutthisconnection. Pin Number Wire Color Primary Function Secondary Function 1 Brown Com D, D+(USB)

2 Red Com D, D-(USB) 3 Orange Com B, RS-232 RX

(From Computer)

4 Yellow Com A, RS-485 RX-, Full Duplex Com C, RS-485 T/R-, Half Duplex 5 Dark Green DC POWER 6 Blue 5 volts (USB only) 7 Violet RELAY 8 Gray Com A, RS-485 TX+, Full Duplex Com A, RS-485 T/R+, Half Duplex 9 Black Com A, RS-485 TX-, Full Duplex Com A, RS-485 T/R-, Half Duplex 10 White Com A, RS-485 RX+, Full Duplex Com C, RS-485 T/R+, Half Duplex 11 Pink Com B, RS-232 TX

(To Computer)

12 Light Green GROUND

11.1.4 OperationTousetheUSBoptiontheUSBdriverneedstobeloadedonthecomputerthesensorwillbeattachedto.ThedrivercanbefoundontheDevelopersKitCDordownloadedfromthestalkerrader.comwebsite.Afterthedriverisinstalled,anytimethesensorisconnecteditwillshowuponthecomputerasastandardcomportdevicewhichcanbeaccessedbyanystandardPCcomportapplication.TousetheACI’sDashboardPCapplicationtoconfigurethesensorthroughtheUSBcomportbesuretouseversion2.8.3ornewer.TheversionneedstosupportComportDinitsconfigurationsetup.


52

11.2 200‐0880‐54,55


AUSBCommination’sPortwasaddedwithaUSB2.0Typemini‐Bjackconnector. TheM‐12connectorwasremoved,eliminatingtheRS‐485,RS‐232,andexternal

triggercapabilities. ThesensorrunsofftheUSBsuppliedpowerandexternalpowersourceisnot

needed.

11.2.2 Mechanicaldescription

11.2.3 ElectricalconnectionsThesensorusesastandardUSB2.0MinitypeBjack.

11.2.4 OperationTousetheUSBoptiontheUSBdriverneedstobeloadedonthecomputerthesensorwillbeattachedto.ThedrivercanbefoundontheDevelopersKitCDordownloadedfromthestalkerrader.comwebsite.Afterthedriverisinstalled,anytimethesensorisconnecteditwillshowuponthecomputerasastandardcomportdevicewhichcanbeaccessedbyanystandardPCcomportapplication.TousetheACI’sDashboardPCapplicationtoconfigurethesensorthroughtheUSBcomportbesuretouseversion2.8.3ornewer.TheversionneedstosupportComportDinitsconfigurationsetup.


53

11.3 200‐1004‐00

11.3.1 SummaryThesesensorsincludethefollowingchangestothebasesensor(200‐0880‐00):

1. ThehousingwasremovedincludingtheM‐12connector.Theconnectorisreplacedwithamolexboardtocableconnector.

2. Therealtimeclockfunctionhasbeenremoved.3. Datacollectionflashmemoryhasbeenremoved.



54


55

11.3.3 ElectricalConnections Included with your sensor is a cable (Stalker Radar P/N 155-2461-00) that plugs into the Sensor that can be wired into the OEM system as required for your particular needs. The wiring diagram for the cable is shown below.

Pin Signal Wire Color 1 RS-485 receive - (to sensor) Brown 2 Vcc Red 3 External trigger Orange 4 External trigger Yellow 5 RS-485 transmit + (from sensor) Violet 6 RS-485 transmit - (from sensor) Blue 7 Ground Green 8 RS-485 receive + (to sensor) Gray 9 RS-232 transmit (from sensor) White

10 AC input Black 11 AC input White/Brown stripe 12 RS-232 receive (to sensor) White/Red stripe

11.3.4 OperationTheoperationisidenticaltothe200‐0880‐00basesensorwiththeexceptionsnotedinsection.11.3.1Ifthesensoristobemountedinanenclosureorbehindaprotectivelens,makesurethatthereisspaceinfrontofthelensasspecifiedintheMechanicalDescriptionsectionabove.Thematerialinfrontofthelensshouldbeanatural,undyedplasticsuchaspolypropyleneorhighdensitypolyethylene.Trytostayawayfromdyedmaterial–especiallyblackasmanyblackdyesusecarbonwhichwillblocktheradartransmission.Ifthesensorisoperatingpoorly,removeitfromtheenclosureorthelenstocompareoperationwithnothinginfrontofit.Alsonote:InthisconfigurationthesensorisnotFCCcertifiedandwillneedtobecertifiedbytheendcustomerwhenintegratedintotheirproduct.


56

11.4 200‐0880‐56

11.4.1 SummaryThesesensorsincludethefollowingchangestothebasesensor(200‐0880‐01):

Theelectricalconnectorismovedfromthesidetotherearofthesensor. AUSBflashmemoryportisadded. TheACvoltageinputwasremovedtoallowfortheadditionoftheUSBmemory

port. TheexternalAUXrelayfunctionwaschangedfroma2lineswitchclosurefunction

toasinglegroundedlineoperation.Thisisanormallyopenswitchonpin7whichisconnectedtosensorgroundwhentheswitchisclosed.



57

11.4.3 ElectricalConnectionTheelectricalconnectionsontherearportareasshownhere. Pin Number Wire Color Primary Function Secondary Function 1 Brown USB memory, D+(USB)

2 Red USB memory, D-(USB) 3 Orange Com B, RS-232 RX

(From Computer)

4 Yellow Com A, RS-485 RX-, Full Duplex Com C, RS-485 T/R-, Half Duplex 5 Dark Green DC POWER 6 Blue 5 volts (USB memory drive only) 7 Violet RELAY 8 Gray Com A, RS-485 TX+, Full Duplex Com A, RS-485 T/R+, Half Duplex 9 Black Com A, RS-485 TX-, Full Duplex Com A, RS-485 T/R-, Half Duplex 10 White Com A, RS-485 RX+, Full Duplex Com C, RS-485 T/R+, Half Duplex 11 Pink Com B, RS-232 TX

(To Computer)

12 Light Green GROUND

11.4.4 OperationTheUSBmemoryoptionisforusewhencollectingtrafficdataonly.ThenitisonlyusedwhenthesensorisconfiguredforExternalMemorybythesurveysetupinthePCapplication.WhentheUSBmemorydriveisinstalledthesensorwillcopyanytrafficdataithasstoredinitsinternalmemorytotheUSBmemorydeviceandwhileitisinstalledthesensorwillsaveallnewtrafficdatatotheUSBmemorydrive.


58

11.5 200‐1033‐00,01


1. ThehousingwasremovedincludingtheM‐12connector.Theconnectorisreplacedwithamolexboardtocableconnector.

2. Thestandard30x32degreeantennaisreplacedbya6x26degreenarrowbeamantenna.

3. TheACvoltageinputwasremovedtoallowfortheadditionoftheUSBcommunicationsport.

4. TheexternalAUXrelayfunctionwaschangedfroma2lineswitchclosurefunctiontoasinglegroundedlineoperation.Thisisanormallyopenswitchonpin4whichisconnectedtosensorgroundwhentheswitchisclosed.



59

11.5.3 ElectricalConnections Included with your sensor is a cable (Stalker Radar P/N 155-2461-00) that plugs into the Sensor that can be wired into the OEM system as required for your particular needs. The wiring diagram for the cable is shown below.

Pin Signal Wire Color 1 RS-485 receive - (to sensor) Brown 2 Vcc Red 3 USB V Orange 4 External trigger Yellow 5 RS-485 transmit + (from sensor) Violet 6 RS-485 transmit - (from sensor) Blue 7 Ground Green 8 RS-485 receive + (to sensor) Gray 9 RS-232 transmit (from sensor) White

10 USB D+ Black 11 USB D- White/Brown stripe 12 RS-232 receive (to sensor) White/Red stripe


60

11.5.4 OperationTousetheUSBoptiontheUSBdriverneedstobeloadedonthecomputerthesensorwillbeattachedto.ThedrivercanbefoundontheDevelopersKitCDordownloadedfromthestalkerrader.comwebsite.Afterthedriverisinstalled,anytimethesensorisconnecteditwillshowuponthecomputerasastandardcomportdevicewhichcanbeaccessedbyanystandardPCcomportapplication.Ifthesensoristobemountedinanenclosureorbehindaprotectivelens,makesurethatthereisspaceinfrontofthelensasspecifiedintheMechanicalDescriptionsectionabove.Thematerialinfrontofthelensshouldbeanatural,undyedplasticsuchaspolypropyleneorhighdensitypolyethylene.Trytostayawayfromdyedmaterial–especiallyblackasmanyblackdyesusecarbonwhichwillblocktheradartransmission.Ifthesensorisoperatingpoorly,removeitfromtheenclosureorthelenstocompareoperationwithnothinginfrontofit.Alsonote:InthisconfigurationthesensorisnotFCCcertifiedandwillneedtobecertifiedbytheendcustomerwhenintegratedintotheirproduct.


61

11.6 200‐1033‐10,11

11.6.1 SummaryThesesensorsincludethefollowingchangestothe200‐1033‐00,01sensors:

1. AnM‐12connectorwithflexcableandbracketisadded.


TherearemanywaystoattachtheM‐12cableandbrackettothesensor.Afewpossibilitiesareshownbelowwithstraightandright‐anglecables.


62


63

11.6.3 ElectricalConnections

Pin Signal 1 USB D+ 2 USB D- 3 RS-232 receive (to sensor) 4 RS-485 receive - (to sensor) 5 Vcc 6 USB V 7 External trigger 8 RS-485 transmit + (from sensor) 9 RS-485 transmit - (from sensor)

10 RS-485 receive + (to sensor) 11 RS-232 transmit (from sensor) 12 Ground

11.6.4 OperationTheoperationisidenticaltothe200‐1033‐00,01sensor.


64

12 FCCRequirementsThisdeviceisapprovedasanintentionalradiatorunderFCCPart15withFCCidentifierIBQACMI007.Noadditionallicensingisrequiredtooperatethisdevice.Operationissubjecttothefollowingtwoconditions:(1)Thisdevicemaynotcauseharmfulinterference,and(2)Thisdevicemustacceptanyinterferencereceived,includinginterferencethatmaycauseundesiredoperation.


A-1

AppendixA OEM6°x26°StationarySpeedSensorIIforLaneDiscrimination

Applied Conceptsmakes several types of radar based speed sensors. Due to the narrowvertical beamwidth, theOEM6° x 26° Stationary Speed Sensor II and theOEM6° x 26°TrafficStatisticsSensorarespecificallywellsuitedforlanediscriminationapplications.

SensorInstallation

TherearemanyaspectsofmountingtheSpeedSensor,allofwhichhaveanimpactonthebehavior,andthereliabilityoftheresults.Thispaperpresentsbasicrecommendationsforinstallationandsomeofthebackgroundreasonsbehindthem.Fromthesedescriptions,itisexpected that users can determine how their particular environment impacts theinstallationandcanmakethenecessaryadjustments. To begin the explanation of the installation we will describe the main factors involved.Thesefactorsarethenexpressedusingmoredetailedchartstowardstheendofthissection.The recommended location of the sensor is above and in the center of the lane to bemonitored.TheSensorshouldbepointedatadownwardslope, towardsthecenterof thelane.Sinceithasa6°beamwidthinthehorizontaldirectionanda26°beamwidthintheverticaldirection,itmakesatrapezoidalpatternwhereithitstheroadwayasshownbelow.

Byspecifyingthatthebeamwidthis6°by26°,wemeanthatthemajorityofthepowerinthe transmitted radar beam is within that pattern. Some of the radar’s power actuallyextendsinawiderpattern,butitisweakeroutsidethe6°x26°boundaries.Anotherthingtonoteabouttherectangularbeamisthatthe6°dimensionisalignedwiththe long dimension of the antenna and the 26° dimension is aligned with the shortdimensionoftheantenna.Althoughitmayseemcounterintuitive,thelargertheantennais,thenarrowerthebeam.Forlanediscriminationinstallations,thesensorshouldbemountedwithitslongsideparalleltotheground.The diagram below shows the geometry of the sensor installation. In the side view, thesensorismountedatthetopofapoleofheightHandistilteddownatangleC(forcenter).ThecenterofthebeamhitstheroadatadistanceRDC(RoadDistanceCenter)fromthebaseofthepole.ThenearandfaredgesofthebeamhittheroadatdistancesRDN(RoadDistanceNear)andRDF(RoadDistance Far). TheanglesN(Near)andF(Far)aredefinedby the26°


A-2

verticalbeamwidthoftheantenna:N=C‐13°andF=C+13°.Theroaddistancevaluescanbecalculatedforagivenpoleheightandmountingangleasfollows:

RDN=H*tanN RDC=H*tanCRDF=H*tanF

TheRoadPatternviewaboveshowsthesizeofthetrapezoidalareawherethebeamhitstheroad surface. The length L of the pattern is the difference from the far edge to the nearedge;L=RDF‐RDN.Thewidthofthepatternvariesanddependsonthedistancethebeamtravelsfromtheradartointersecttheroad.Asthesignaltravelsawayfromthesensor,thewidthofthe6°beamincreasesroughlybythefollowingequation.

Width=0.1*Distance

ThebeamdistanceforthenearedgeDN=√(H2+RDN2),sothebeamwidthWN=0.1*√(H2+RDN2).Inalikemanner,thebeamwidthWCatRDCis0.1*√(H2+RDC2),andthebeamwidthWFatthefarendofthepatternis0.1*√(H2+RDF2)


A-3

Atypicallanewidthis11ft.(3.3m)andisthesinglemostimportantfactorinchoosingthedistance between the sensor and the target zone to be monitored. To perform lanediscriminationamajorityof theradarsignalmustbeconfined to the laneof interest,butsomeoverlap into theadjacent lanes canbe toleratedbecauseof the lowprobabilityof asignificantamountofreflectivesurfacefromavehicleintheadjacentlanewillbeinview.Someof theeffectsof allowing theadjacent lanes tobeexposedwill be compensated forlaterwhen setting up theTarget Strength Sensitivity of the sensor andwill be explainedlaterinthispaper.The explanation provided so far provides the theory andmath for the calculations. Thefollowingtablesdefinethebeampatternforanumberofdifferentpoleheightsandaiminganglestogiveamorepracticalviewoftheinstallationoptionsandresultingbeampatterns.PoleHeight

H

AimingAngleC

RoadDistanceNear

RDN

RoadDistanceCenter

RDC

RoadDistanceFar

RDF

BeamPatternLength

L

PatternWidthNear

WN

PatternWidthCenter

WC

PatternWidthFar

WF

CosineAngleφ

15 45 9.37 15.00 24.01 14.63 1.77 2.12 2.83 4515 50 11.30 17.88 29.44 18.14 1.88 2.33 3.30 4015 55 13.51 21.42 37.13 23.62 2.02 2.62 4.00 3515 60 16.09 25.98 49.06 32.98 2.20 3.00 5.13 3015 65 19.20 32.17 70.57 51.37 2.44 3.55 7.21 2515 70 23.10 41.21 122.17 99.07 2.75 4.39 12.31 2015 75 28.21 55.98 429.54 401.33 3.20 5.80 42.98 15 15 60 16.09 25.98 49.06 32.98 2.20 3.00 5.13 3015 61 16.66 27.06 52.31 35.65 2.24 3.09 5.44 2915 62 17.26 28.21 55.98 38.73 2.29 3.20 5.80 2815 63 17.88 29.44 60.16 42.29 2.33 3.30 6.20 2715 64 18.52 30.75 64.97 46.45 2.38 3.42 6.67 2615 65 19.20 32.17 70.57 51.37 2.44 3.55 7.21 2515 66 19.91 33.69 77.17 57.26 2.49 3.69 7.86 2415 67 20.65 35.34 85.07 64.42 2.55 3.84 8.64 2315 68 21.42 37.13 94.71 73.28 2.62 4.00 9.59 2215 69 22.24 39.08 106.73 84.49 2.68 4.19 10.78 2115 70 23.10 41.21 122.17 99.07 2.75 4.39 12.31 2015 71 24.01 43.56 142.72 118.71 2.83 4.61 14.35 1915 72 24.96 46.17 171.45 146.49 2.91 4.85 17.21 1815 73 25.98 49.06 214.51 188.53 3.00 5.13 21.50 1715 74 27.06 52.31 286.22 259.16 3.09 5.44 28.66 1615 75 28.21 55.98 429.54 401.33 3.20 5.80 42.98 15


A-4

PoleHeight

H

AimingAngleC

RoadDistanceNear

RDN

RoadDistanceCenter

RDC

RoadDistanceFar

RDF

BeamPatternLength

L

PatternWidthNear

WN

PatternWidthCenter

WC

PatternWidthFar

WF

CosineAngleφ

20 45 12.50 20.00 32.01 19.51 2.36 2.83 3.77 4520 50 15.07 23.84 39.25 24.18 2.50 3.11 4.41 4020 55 18.01 28.56 49.50 31.49 2.69 3.49 5.34 3520 60 21.45 34.64 65.42 43.97 2.93 4.00 6.84 3020 65 25.60 42.89 94.09 68.49 3.25 4.73 9.62 2520 70 30.80 54.95 162.89 132.09 3.67 5.85 16.41 2020 75 37.61 74.64 572.73 535.11 4.26 7.73 57.31 15 20 60 21.45 34.64 65.42 43.97 2.93 4.00 6.84 3020 61 22.21 36.08 69.75 47.54 2.99 4.13 7.26 2920 62 23.01 37.61 74.64 51.63 3.05 4.26 7.73 2820 63 23.84 39.25 80.22 56.38 3.11 4.41 8.27 2720 64 24.70 41.01 86.63 61.93 3.18 4.56 8.89 2620 65 25.60 42.89 94.09 68.49 3.25 4.73 9.62 2520 66 26.54 44.92 102.89 76.35 3.32 4.92 10.48 2420 67 27.53 47.12 113.43 85.90 3.40 5.12 11.52 2320 68 28.56 49.50 126.28 97.71 3.49 5.34 12.78 2220 69 29.65 52.10 142.31 112.66 3.58 5.58 14.37 2120 70 30.80 54.95 162.89 132.09 3.67 5.85 16.41 2020 71 32.01 58.08 190.29 158.28 3.77 6.14 19.13 1920 72 33.29 61.55 228.60 195.32 3.88 6.47 22.95 1820 73 34.64 65.42 286.01 251.37 4.00 6.84 28.67 1720 74 36.08 69.75 381.62 345.54 4.13 7.26 38.21 1620 75 37.61 74.64 572.73 535.11 4.26 7.73 57.31 15


A-5

PoleHeight

H

AimingAngleC

RoadDistanceNear

RDN

RoadDistanceCenter

RDC

RoadDistanceFar

RDF

BeamPatternLength

L

PatternWidthNear

WN

PatternWidthCenter

WC

PatternWidthFar

WF

CosineAngleφ

25 45 15.62 25.00 40.01 24.39 2.95 3.54 4.72 4525 50 18.84 29.79 49.07 30.23 3.13 3.89 5.51 4025 55 22.51 35.70 61.88 39.37 3.36 4.36 6.67 3525 60 26.81 43.30 81.77 54.96 3.67 5.00 8.55 3025 65 32.00 53.61 117.62 85.62 4.06 5.92 12.02 2525 70 38.50 68.69 203.61 165.11 4.59 7.31 20.51 2025 75 47.02 93.30 715.91 668.89 5.33 9.66 71.63 15 25 60 26.81 43.30 81.77 54.96 3.67 5.00 8.55 3025 61 27.77 45.10 87.19 59.42 3.74 5.16 9.07 2925 62 28.76 47.02 93.30 64.54 3.81 5.33 9.66 2825 63 29.79 49.07 100.27 70.48 3.89 5.51 10.33 2725 64 30.87 51.26 108.29 77.41 3.97 5.70 11.11 2625 65 32.00 53.61 117.62 85.62 4.06 5.92 12.02 2525 66 33.18 56.15 128.61 95.44 4.15 6.15 13.10 2425 67 34.41 58.90 141.78 107.37 4.25 6.40 14.40 2325 68 35.70 61.88 157.84 122.14 4.36 6.67 15.98 2225 69 37.06 65.13 177.88 140.82 4.47 6.98 17.96 2125 70 38.50 68.69 203.61 165.11 4.59 7.31 20.51 2025 71 40.01 72.61 237.86 197.85 4.72 7.68 23.92 1925 72 41.61 76.94 285.75 244.14 4.85 8.09 28.68 1825 73 43.30 81.77 357.52 314.22 5.00 8.55 35.84 1725 74 45.10 87.19 477.03 431.93 5.16 9.07 47.77 1625 75 47.02 93.30 715.91 668.89 5.33 9.66 71.63 15

There isonemorevery importantpoint tomake inconsideringtheantenna location.Theantennashouldbemountedsothattherearenoobstaclesbetweentheradarandthelanetobemonitored.Eventhoughthebeamwidthisonly6degrees,someoftheradarsignalwillexitinmuchwiderbeamanglesfromtheantenna.Thecloseranobjectistotheantennathestronger the signalwill be thatwill be reflectedback to the antenna.A very closeobject,evenoutside the6degreebeamwidth, can reflect enoughenergyback to the antenna tooverload the antenna and reduce its sensitivity.When installing the antenna, make suretherearenoobstaclesnearthefrontoftheantenna.


A-6

SensorConfigurationTherearefourconfigurationregistersthatareusedtocustomizetheSpeedSensorforlanediscrimination.Theyare theTargetDirection,CosineAngle1,TargetStrengthSensitivity,andtheHoldoverTimeregisters.TargetDirection(configurationID1/02)TheavailablevaluesfortheTargetDirectionsettingare“Away”tomonitorrecedingtargetsonly,“Closing”tomonitorapproachingtargetsonlyand“Both”tomonitortargetsmovingineither direction. Select the direction of traffic relative to the sensor for the lane to bemonitored. The “Both” selection should not be used since lanes typically only have onedirectionoftravelandusingthe“Both”settingmayaddunwantedreporting.CosineAngle1(configurationID1/18)Radarsmeasurethemostaccuratespeedswhentargetsaremovingdirectlytowardorawayfromthem.Aswithanyradar,aimingatanangleresultsinlowerreadingsthantheactualspeeds. At slight angles the error is very small; however at larger angles the error canbecomesubstantial.TheselowspeedscanbecorrectedusingtheCosineAnglesettings.TherangeofvaluesforthetwoCosineAnglesettingsis0–45degrees,inonedegreeincrements.In the Lane discrimination applications the Cosine Angle (φ in the charts above) is thecomplementaryangletotheaimingangleofthesensor(Cinthechartsabove).Forexample,if the sensor is pointing out at a 70 degree angle relative to a vertical pole, then thecomplement,orthecosineangleforthesensoris20degrees(90‐70=20).TargetStrengthSensitivity(configurationID1/85or1/120)Targetscanbesuppressedoracquireddependingontheirsignalstrength.AhighervaluefortheTargetStrengthSensitivityallowssmaller,weakertargetstobeacquired.A lowervaluerequiresthetargettobelarger/strongerbeforeitisacquired.Therangeofvaluesis1‐99. For lane discrimination applications we suggest a starting value of 50 for TargetStrengthSensitivity.TheOEM6°x26°StationarySensor IIhas justone target strengthsensitivity setting, theVisualTargetStrengthSensitivity(ID1/85).TheOEM6°x26°TrafficStatisticsSensorhastwo: the Visual Target Strength Sensitivity as above and also the Stats Target StrengthSensitivity(ID1/120).IftheTrafficStatisticsSensorisbeingusedtocollectstatistics,usethissecondsetting.HoldoverTime(ConfigurationID1/88)TheHoldoverTimesetsatimeforthelastspeedmeasurementtocontinuetobedisplayedafter the signal has been lost. This is primarily for applicationswhere the speed is to bevisually displayed and the holdover aids in eliminating display flicker. In lanediscriminationapplicationstheoutputgenerallydoesnotgotoavisualdisplayandsoisnotneeded. The Holdover Time is settable from 0 to 10 seconds. For lane discriminationapplicationssetthisregisterto0.


A-7

FineTuningtheSetUpEvery installation should be treated as a unique set up. There are several sources ofvariability that may require an installation to be fine‐tuned. These sources of variabilityrangefromdifferencesinthesensitivityandtransmitpowerfromonesensortothenext,tolanewidthandroadgradientsoftheinstallationsite.TheprimarytoolforadjustingtheperformanceofthesensoronceitisinstalledisitsTargetStrength Sensitivity setting. The larger the sensitivity value stored in the configurationregister, thewider the effective beamwidth. Thiswill cause the target zone to increase,movingthenearendclosertothesensorandthefarendfurtherawayfromthesensor;thedrawback is thesensorwillpickupmore traffic inadjacent lanes. Ifyour lanesarewide,thenyoucanincreaseyoursensitivityalittleandhavealongertargetzone.Conversely, ifthe sensor is picking up too much traffic in adjacent lanes then you need to lower thesensitivitysetting;thiswillalsocausethelengthoftheeffectivetargetzonetodecrease.

stalker stationary speed sensor ii technical manual

Documents