New Search
My WebLink
|
Help
|
About
|
Sign Out
New Search
Eugene Master Traffic Communications Plan
COE
>
PW
>
Admin
>
Finance
>
Operating
>
2011
>
Eugene Master Traffic Communications Plan
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
10/12/2010 3:58:50 PM
Creation date
10/12/2010 1:46:04 PM
Metadata
Fields
Template:
PW_Operating
PW_Document_Type_ Operating
Reports
Fiscal_Year
2008
PW_Division
Maintenance
External_View
No
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
74
PDF
Print
Pages to print
Enter page numbers and/or page ranges separated by commas. For example, 1,3,5-12.
After downloading, print the document using a PDF reader (e.g. Adobe Reader).
Show annotations
View images
View plain text
Table 5. Requirements for Existing and Planned Devices <br />revice <br />Notes <br />Communications Requirements <br />• 170, 170A, and 170E controllers with BiTrans software <br />Existing Conditions <br />and QuicNet 2006 central software <br />• EIA/TIA -232, commonly referred to as RS -232, <br />• 195 existing traffic signals are on- system <br />communications between the central signal system <br />• 35 existing traffic signals are off - system <br />computer and the controllers at each intersection <br />• 3 traffic signals are planned within the next few years: <br />• Up to seven controllers may be supported on each RS- <br />Traffic Signals <br />8" Mill, Hilyard /EWEB Access, Game Farm /Chad Dr <br />232 channel <br />• ODOT may ask the City to take over operations of 3 of <br />Future Conditions <br />their traffic signals in the future: Hwy 99 /Irving, Hwy <br />• Need to support migration to NTCIP communications <br />99 /Beltline, OR 126 /Green Hill <br />protocol and the additional bandwidth it requires <br />• Traffic signals operated by Lane County in the Irving area <br />• Future traffic signal controllers will support direct IP <br />may be annexed into the City in the future. <br />communications <br />• At some locations (e.g. Coburg Rd), twisted pair <br />• Emergency preemption is typically performed at a local <br />interconnect is used to transfer advance emergency <br />intersection level using the Opticom zone detection <br />Emergency <br />preemption calls to other traffic signals <br />method. There are no plans for central based emergency <br />Preemption <br />• At most intersections emergency preemption calls only <br />vehicle preemption. <br />interface with the local intersection controller <br />• Remote communications to the emergency vehicle <br />discriminators must be supported. <br />• BusPlus!: LTD plans to install transit signal priority in <br />• Transit signal priority is managed at the local intersection <br />cooperation with Public Works on three corridors in 2008 <br />level between the bus and the intersection traffic signal <br />as part of their BusPlus! project. <br />controller. In some instances, the requests for TSP may <br />be transmitted to downstream intersections <br />Transit Signal <br />• Additional database logs and timing features must be <br />Priority (TSP) <br />uploaded and downloaded, but the data requirements are <br />minimal. <br />• Emerald Express (EmX): Transit signal priority is used on <br />• Transit signal priority requests are transmitted to <br />Franklin Blvd for LTD's bus rapid transit. 5 block traffic <br />downstream intersections using the existing copper <br />signal controllers are used to control access to <br />twisted pair cable. Transmitting these TSP requests <br />bidirectional sections of single EmX lanes. <br />requires a separate pair of wires. <br />
The URL can be used to link to this page
Your browser does not support the video tag.