Radwin 5XACMD3CN 5 GHz 802.11ac 3x3 RF Module User Manual UM Transportation 4 2 46 Regulatory

Download:
Mirror Download [FCC.gov]
Document ID	3696013
Application ID	+/hibUmByZQwGYyAapgiHA==
Document Description	User Manual
Short Term Confidential	No
Permanent Confidential	No
Supercede	Yes
Document Type	User Manual
Display Format	Adobe Acrobat PDF - pdf
Filesize	468.9kB (5861250 bits)
Date Submitted	2017-12-28 00:00:00
Date Available	2018-06-20 00:00:00
Creation Date	2017-12-25 11:20:10
Producing Software	Acrobat Distiller 10.1.16 (Windows)
Document Lastmod	2017-12-25 11:36:07
Document Title	UM_Transportation_4_2_46_Regulatory.book
Document Creator	FrameMaker 10.0.2
Document Author:	shmuel_g

DEPLOYMENT GUIDE
TRANSPORTATION FIBERINMOTION
BROADBAND TRAIN TO GROUND COMMUNICATION
Release 4.2.46
For Regualtor Approval Only
Table of Contents
Chapter 1: Site Installation
1.1 Scope of This Chapter.......................................................................................................... 1‐1
1.2 Track Side ............................................................................................................................ 1‐1
1.2.1 Overview ..................................................................................................................... 1‐1
1.2.2 TBS & Antennas ‐ General Mounting Arrangement .................................................... 1‐2
1.2.3 TBS ‐ Mounting............................................................................................................ 1‐3
1.2.4 PoE Devices for the TBS ............................................................................................. 1‐15
1.2.5 TBS Antennas ............................................................................................................ 1‐15
1.2.6 Indoor Synchronization Unit (ISU) ............................................................................. 1‐23
1.2.7 Lightning Protection Unit .......................................................................................... 1‐24
1.2.8 Waterproofing........................................................................................................... 1‐28
1.2.9 Grounding ................................................................................................................. 1‐29
1.3 Train Side........................................................................................................................... 1‐32
1.3.1 TMU........................................................................................................................... 1‐32
1.3.2 PoE Device for the TMU............................................................................................. 1‐42
1.3.3 TMU Antennas .......................................................................................................... 1‐43
Chapter 2: Network Guidelines
2.1 Scope of This Chapter.......................................................................................................... 2‐1
2.2 Overview ............................................................................................................................. 2‐1
2.3 Track Side Network ............................................................................................................. 2‐1
2.4 Train Side (On‐board) Network ........................................................................................... 2‐3
2.5 Train Side Physical Connectivity .......................................................................................... 2‐4
2.6 Track Side Core Router........................................................................................................ 2‐5
2.7 Basic IP Scheme and Data Flow Path................................................................................... 2‐5
2.8 Recommended VLAN Assignment....................................................................................... 2‐7
2.9 Inter Base Handover (IBHO) Update Message .................................................................... 2‐9
2.10 Intra Train Handover (ITHO) Update Message................................................................ 2‐12
Chapter 3: Configuring the Radio Network
3.1 Scope of This Chapter.......................................................................................................... 3‐1
3.2 Connecting to the Units ...................................................................................................... 3‐1
3.3 About the Configurator ....................................................................................................... 3‐1
3.3.1 Method of Operation .................................................................................................. 3‐2
3.4 Using the Configurator ........................................................................................................ 3‐2
3.4.1 Main Tab ..................................................................................................................... 3‐2
3.4.2 Project Tab .................................................................................................................. 3‐5
3.4.3 Line Tab ..................................................................................................................... 3‐12
3.4.4 Towers Tab ................................................................................................................ 3‐15
3.4.5 Train Tab ................................................................................................................... 3‐17
3.5 Interference Mitigation for Co‐channel Neighbors ........................................................... 3‐18
3.5.1 Basic Situation........................................................................................................... 3‐18
3.5.2 Necessary Pre‐Conditions.......................................................................................... 3‐19
3.5.3 Method of Operation ................................................................................................ 3‐20
3.5.4 Configuring the Co‐Channel Neighbor Interference Mitigation Option .................... 3‐21
3.6 Configuring Network Units................................................................................................ 3‐25
3.6.1 Configuring Transportation Base Stations (TBSs)...................................................... 3‐25
3.6.2 Configuring Transportation Mobile Units (TMUs)..................................................... 3‐27
3.6.3 Configuring Indoor Synchronization Units (ISUs) ...................................................... 3‐29
3.7 Configurator Messages ..................................................................................................... 3‐31
Appendix A: Antenna Guidelines
FinM Deployment Guide
For Regualtor Approval Only
Release 4.2.46
Appendix B: Revision History
FinM Deployment Guide
For Regualtor Approval Only
Release 4.2.46
ii
FinM Deployment Guide
For Regualtor Approval Only
Release 4.2.46
iii
FinM Deployment Guide
For Regualtor Approval Only
Release 4.2.46
iv
Chapter 1: Site Installation
1.1 Scope of This Chapter
This chapter describes how to physically install the equipment for the Transportation
FiberinMotion solution.
1.2 Track Side
1.2.1 Overview
The Fiber in Motion solution uses vertical antennas, and relies on antenna spacing to
differentiate the radio streams enough so as to enable MIMO.
General Guidelines
• Place the tower/TBS at the location determined by the site survey.
• Make sure there is sufficient line‐of‐sight towards the track segment the antennas
will cover,
• Make sure that there are no obstacles directly in front of the antennas.
• The lowest antenna must be higher than the highest rail car on the line.
Power
• Use the PoE to supply power to the TBS (either an outdoor or indoor PoE).
• Use the PoE or the SFP fiber connection to provide a service connection to the
TBS.
• Install two Lightning Protection Units (LPU): One close to the TBS, and the other
close to the PoE.
Minimum Recommended Distances
There are three antennas for each stream: A is for approaching trains, and B is for
receding trains (see Figure 1‐1). Separate the antennas as much as possible, and
maintain the following minimal distances:
• Minimum vertical distance between each antenna is 1.0m.
• Minimum horizontal distance between Antenna 1 and Antenna 2 is 1.6m.
FinM Deployment Guide
For Regualtor Approval Only
Release 4.2.46
1‐1
TBS & Antennas ‐ General Mounting Arrangement
Site Installation
• Minimum horizontal distance between Antenna 3 and Antenna 2 is 1.0m
• Minimum total horizontal distance (between Antenna 1 and Antenna 3) is 2.6m
1.2.2 TBS & Antennas ‐ General Mounting Arrangement
The TBS can be mounted on a pole or a wall, together with its antennas, LPUs and PoE device.
To enable better MIMO conditions, the antennas should be divided between vertical and
horizontal polarizations. Figure 1‐1 shows a schematic view with these polarizations.
Figure 1‐1: TBS ‐ Base Station mounting with antennas
FinM Deployment Guide
For Regualtor Approval Only
Release 4.2.46
1‐2
TBS ‐ Mounting
Site Installation
1.2.3 TBS ‐ Mounting
The TBS can be mounted on a vertical or horizontal pole, or on a wall.
•
Vertical pole: see page 1‐5 for directions relevant to all sizes.
• Thin pole: see page 1‐6.
• Medium pole: see page 1‐7
• Thick pole: see page 1‐8
Horizontal pole: see page 1‐8 for directions relevant to all sizes.
• Thin pole: see page 1‐10.
• Medium pole: see page 1‐11
• Thick pole: see page 1‐12
Wall: The TBS can be mounted on a wall, see page 1‐12.
•
•
Check the package contents:
Figure 1‐2: TBS mounting kit package contents
Table 1‐1: TBS mounting kit package contents
Item
No.
Description
Quantity
Base plate
Pole clamp
Hex screw with flange M8x90
FinM Deployment Guide
For Regualtor Approval Only
Release 4.2.46
1‐3
TBS ‐ Mounting
Site Installation
Table 1‐1: TBS mounting kit package contents (Continued)
Item
No.
Description
Quantity
Standoffs M4x16
Allen screws M4x30
Washers for allen screws
FinM Deployment Guide
For Regualtor Approval Only
Release 4.2.46
1‐4
TBS ‐ Mounting
Site Installation
Vertical Pole ‐ all sizes
1. Fasten the standoffs to the base plate in the holes labeled “V” as shown:
Figure 1‐3: Fasten standoffs to base plate (for vertical pole)
2. Place the TBS as shown over the standoffs, and using the Allen screws and washers, fasten
the TBS to the base plate.
Figure 1‐4: Fasten TBS to base plate (for vertical pole)
FinM Deployment Guide
For Regualtor Approval Only
Release 4.2.46
1‐5
TBS ‐ Mounting
Site Installation
Vertical Pole ‐ thin
1. Diameter 3/4 to 1 1/2: Before raising the TBS on the pole, position the pole clamp as shown
in the following two figures. Do not completely tighten the bolts:
Thin pole (diameter 3/4 to 1 1/2): Position the pole clamp as shown in the following two figures, do not completely tighten the bolts:
Figure 1‐5: Thin pole: Fasten clamp to base
Figure 1‐6: Thin pole: Do not completely
plate
tighten bolts
2. Place this assembly on the pole where you want to mount the TBS. Once it is in place,
rotate the pole clamp as shown, then tighten both bolts.
Figure 1‐7: Thin pole: Rotate clamp
FinM Deployment Guide
Figure 1‐8: Thin pole: tighten bolts
For Regualtor Approval Only
Release 4.2.46
1‐6
TBS ‐ Mounting
Site Installation
Vertical pole ‐ medium
1. Diameter 2 to 3: Before raising the TBS on the pole, position the pole clamp as shown in
the following two figures. Do not completely tighten the bolts:
Figure 1‐9: Medium pole: Fasten clamp to
base plate
Figure 1‐10: Medium pole: Do not com‐
pletely tighten bolts
2. Place this assembly on the pole where you want to mount the TBS. Once it is in place,
rotate the pole clamp as shown, then tighten both bolts.
Figure 1‐11: Medium pole: Rotate clamp
FinM Deployment Guide
Figure 1‐12: Medium pole: tighten bolts
For Regualtor Approval Only
Release 4.2.46
1‐7
TBS ‐ Mounting
Site Installation
Vertical Pole ‐ thick
1. Diameter larger than 3: Use worm drive clamps (not supplied), threaded through the holes
as shown in Figure 1‐13, or U‐bolts (not supplied), fastened using the holes as shown in
Figure 1‐14:
Figure 1‐13: Using worm drive clamps for a thick pole
Figure 1‐14: Using U‐bolts for a thick pole
Horizontal Pole ‐ all sizes
1. Before fastening the TBS to the base plate (see Step 1. on page 1‐5), rotate the plate by 90o
clockwise. Make sure the arrow next to the “H” points up.
FinM Deployment Guide
For Regualtor Approval Only
Release 4.2.46
1‐8
TBS ‐ Mounting
Site Installation
Figure 1‐15: Rotate base plate clockwise 90o for horizontal pole
2. Fasten the standoffs to the base plate in the holes labeled “H” as shown:
Figure 1‐16: Fasten standoffs to base plate (for horizontal pole)
3. Place the TBS as shown over the standoffs, and using the Allen screws and washers, fasten
the TBS to the base plate.
FinM Deployment Guide
For Regualtor Approval Only
Release 4.2.46
1‐9
TBS ‐ Mounting
Site Installation
Figure 1‐17: Fasten TBS to base plate (for horizontal pole)
Horiztonal Pole ‐ thin
1. Diameter 3/4 to 1 1/2: Before raising the TBS on the pole, position the pole clamp as shown
in the following two figures. Do not completely tighten the bolts:
Thin pole (diameter 3/4 to 1 1/2): Position the pole clamp as shown in the following two figures, do not completely tighten the bolts:
Figure 1‐18: Thin pole: Fasten clamp to base
plate
FinM Deployment Guide
Figure 1‐19: Thin pole: Do not completely
tighten bolts
For Regualtor Approval Only
Release 4.2.46
1‐10
TBS ‐ Mounting
Site Installation
2. Place this assembly on the pole where you want to mount the TBS. Once it is in place,
rotate the pole clamp as shown, then tighten both bolts.
Figure 1‐20: Thin pole: Rotate clamp
Figure 1‐21: Thin pole: tighten bolts
Horizontal Pole ‐ medium
1. Diameter 2 to 3: Before raising the TBS on the pole, position the pole clamp as shown in
the following two figures. Do not completely tighten the bolts:
Figure 1‐22: Medium pole: Fasten clamp to
base plate
FinM Deployment Guide
Figure 1‐23: Medium pole: Do not com‐
pletely tighten bolts
For Regualtor Approval Only
Release 4.2.46
1‐11
TBS ‐ Mounting
Site Installation
2. Place this assembly on the pole where you want to mount the TBS. Once it is in place,
rotate the pole clamp as shown, then tighten both bolts.
Figure 1‐24: Medium pole: Rotate clamp
Figure 1‐25: Medium pole: tighten bolts
Horiztonal Pole ‐ thick
1. Diameter larger than 3: Use metal bands (not supplied), threaded through the holes as
shown in Figure 1‐26, or U‐bolts (not supplied), fastened using the holes as shown in
Figure 1‐27:
Figure 1‐26: Using metal bands for a large poleFigure 1‐27: Using U‐bolts for a large pole
Mounting on a wall
1. Fasten the standoffs to the base plate in the holes labeled “V” or “H”, whichever is more
convenient, as shown:
FinM Deployment Guide
For Regualtor Approval Only
Release 4.2.46
1‐12
TBS ‐ Mounting
Site Installation
OR
<‐>
Figure 1‐28: Fasten standoffs to base plate
Figure 1‐29: Standoffs fastened to base plate
2. Use anchor bolts to attach base plate to a wall, as shown:
FinM Deployment Guide
For Regualtor Approval Only
Release 4.2.46
1‐13
TBS ‐ Mounting
Site Installation
Attach the base plate to a wall using 9mm dia. anchor bolts (not supplied) in the holes indicated.
Figure 1‐30: Attach base plate to wall
3. Place the TBS as shown over the standoffs, and using the Allen screws and washers, fasten
the TBS to the base plate.
Figure 1‐31: Fasten TBS to base plate on wall
FinM Deployment Guide
For Regualtor Approval Only
Release 4.2.46
1‐14
PoE Devices for the TBS
Site Installation
Figure 1‐32: TBS mounted on a wall
Always mount a TBS with the connectors on the bottom. Never mount a
unit horizontally.
1.2.4 PoE Devices for the TBS
The TBS is supplied by an AC PoE device, either via an outdoor unit mounted in the same
manner as an antenna, or via an indoor unit, installed in an electrical hut.
(The TMU has its own PoE, see PoE Device for the TMU on page 1‐42).
1.2.5 TBS Antennas
TBS Antenna Mounting Kit
Use the antenna mounting kit (different from the TBS mounting kit) to mount a TBS antenna
on a pole or wall. The same mounting kit is used to mount an external AC PoE device.
FinM Deployment Guide
For Regualtor Approval Only
Release 4.2.46
1‐15
TBS Antennas
Site Installation
Figure 1‐33: Antenna Mounting Kit Contents
Tighten all bolts with a torque of 15Nm.
TBS Antenna Mounting on a Medium Pole
This method is for mounting the TBS antenna on a pole of pipe size 2 to 3.
4. Connect the pole clamp to the radio holder with the 8x90 bolts, but do not tighten
the bolts all the way ‐ tighten them so that they are not closer than a distance
equal to the radius of the pole. You will then have one “unit” that you can take to
FinM Deployment Guide
For Regualtor Approval Only
Release 4.2.46
1‐16
TBS Antennas
Site Installation
the location on the pole where you want to mount the antenna. (See Figure 1‐38
to Figure 1‐41 for mounting on a thin pole)
Figure 1‐34: Connect Pole Clamp to Radio
Holder
Figure 1‐35: Tighten bolts
5. Place this “unit” on the pole where you want to mount the antenna. Once it is in
place, rotate the pole clamp as shown, then tighten both bolts.
Figure 1‐36: Rotate Clamp and tighten bolts
Figure 1‐37: Mounting Kit on pole
TBS Antenna Mounting on a Thick Pole
This method is for mounting the TBS antenna on a pole of pipe size larger than 3.
FinM Deployment Guide
For Regualtor Approval Only
Release 4.2.46
1‐17
TBS Antennas
Site Installation
TBS Antenna Mounting on a Thin Pole
This method is for mounting the TBS antenna on a pole of pipe size 3/4 to 1 1/2.
Do not mount the TBS antenna on a pole smaller than 3/4.
1. When mounting on a thin pole, position the pole clamp as shown in the following figures:
Figure 1‐38: Connect Pole Clamp to Radio
Holder
Figure 1‐39: Tighten bolts
2. Place this “unit” on the pole where you want to mount the antenna. Once it is in
place, rotate the pole clamp as shown, then tighten both bolts.
Figure 1‐40: Rotate Clamp and tighten bolts
FinM Deployment Guide
Figure 1‐41: Mounting Kit on thin pole
For Regualtor Approval Only
Release 4.2.46
1‐18
TBS Antennas
Site Installation
TBS Antenna Mounting on a Horizontal Pole
When using the mounting kit on a horizontal pole, use the radio vertical adaptor, as shown:
Figure 1‐42: Mounting kit on a horizontal pole
FinM Deployment Guide
For Regualtor Approval Only
Release 4.2.46
1‐19
TBS Antennas
Site Installation
TBS Antenna Mounting on a Wall
When using the mounting kit on a wall, the pole clamp is not necessary:
TBS Antenna Mounting Kit Adaptor
A flat panel antenna such as that shown in Figure 1‐44 is typically used. It has four bolts for a
mounting kit adapter. The mounting kit adaptor appears as shown in Figure 1‐43:
Figure 1‐43: Flat panel antenna mounting kit adapter
Attach the mounting kit adaptor to the rear of the antenna as shown:
FinM Deployment Guide
For Regualtor Approval Only
Release 4.2.46
1‐20
TBS Antennas
Site Installation
Figure 1‐44: Flat Panel antenna ‐ rear with mounting kit adapter
Figure 1‐45 shows a mounted antenna. Attach the mounting bolt to the side of the adaptor
with the recess, as shown.
FinM Deployment Guide
For Regualtor Approval Only
Release 4.2.46
1‐21
TBS Antennas
Site Installation
Figure 1‐45: Flat Panel antenna ‐ mounted on a pole
FinM Deployment Guide
For Regualtor Approval Only
Release 4.2.46
1‐22
Indoor Synchronization Unit (ISU)
Site Installation
1.2.6 Indoor Synchronization Unit (ISU)
The Indoor Synchronization Unit (ISU) provides a master synchronization clock for all TBS
units, and is connected to one of the network switches.
It can be installed on a 19in. rack or on a convenient surface in the network operating center.
Figure 1‐46: Indoor Synchronization Unit (ISU)
FinM Deployment Guide
For Regualtor Approval Only
Release 4.2.46
1‐23
Lightning Protection Unit
Site Installation
1.2.7 Lightning Protection Unit
The use of lightning protection is dependent on regulatory and end user requirements.
Although FinM units have surge limiting circuits that minimize the risk of damage due to
lightning strikes, RADWIN recommends the use of additional surge arrestor devices to protect
the equipment from nearby lightning strikes.
Table 1‐2: LPU Kit contents
Item
Qty
LPU
RJ‐45 connectors
0.5m CAT‐5e cable
Metal tie
ScotchTM 23 Tape
View/Remarks
For any type of indoor unit‐outdoor unit connection, lightning protection units (LPUs) are
installed in pairs, as shown in Figure 1‐47:
FinM Deployment Guide
For Regualtor Approval Only
Release 4.2.46
1‐24
Lightning Protection Unit
Site Installation
Figure 1‐47: Basic use of lightning protector units
The LPU has two cable glands on the bottom for CAT‐5e/6 cables, in addition to a grounding
lug. There is an extra hole for a second screw when installed on a wall. On the side of the LPU
is a slot for the metal tie when installed on a pole, as shown in Figure 1‐48 and Figure 1‐49:
Figure 1‐48: LPU: Bottom View

Figure 1‐49: LPU: Side View
To install an LPU on a pole:
1. Choose a location as close as possible to the radio unit.
2. Insert the metal tie through the slots as shown in Figure 1‐49. Make sure the LPU is
oriented in the correct direction, as shown in Figure 1‐50.
FinM Deployment Guide
For Regualtor Approval Only
Release 4.2.46
1‐25
Lightning Protection Unit
Site Installation
Figure 1‐50: LPU attached to pole with metal tie
3. Tighten the metal tie.
4. Connect the grounding lug to a grounding source.
5. Remove the cable glands.
6. Thread the CAT‐5e/6 cables through the cable glands, and connect the cables to the
LPU as shown in Figure 1‐51.
7. Tighten the cable glands around the CAT‐5e cables as shown in Figure 1‐52.
Figure 1‐51: Connecting cables to the LPU (1) Figure 1‐52: Connecting cables to the LPU (2)
8. Route one CAT‐5e/6 up to the radio, and the other down to the IDU or PoE (via the
lower LPU). An LPU installed on a pole is shown in Figure 1‐53.
9. RADWIN recommends that you add extra waterproofing to the connections
(see see "Waterproofing" on page 1‐28.).
FinM Deployment Guide
For Regualtor Approval Only
Release 4.2.46
1‐26
Lightning Protection Unit
Site Installation
Figure 1‐53: Installing an LPU on a pole (side view)

To install an LPU on a wall:
1. Remove the grounding lug.
2. Attach the LPU to the wall using wood or masonry screws (not included), via the
holes as shown in Figure 1‐54.
3. Connect the left screw (where the grounding lug was located) to a ground source.
4. Remove the cable glands.
5. Thread the CAT‐5e/6 cables through the cable glands, and connect the cables to the
LPU as shown in Figure 1‐51.
6. Tighten the cable glands around the CAT‐5e/6 cables as shown in Figure 1‐52.
7. Route one CAT‐5e up to the radio (via the upper LPU), and the other to the IDU or
PoE.
8. RADWIN recommends that you add extra waterproofing to the connections
(see see Waterproofing on page 1‐28).
FinM Deployment Guide
For Regualtor Approval Only
Release 4.2.46
1‐27
Waterproofing
Site Installation
Figure 1‐54: Installing an LPU on a wall
1.2.8 Waterproofing
Protect all connections between any outdoor devices and cables from rain, dust, moisture
and salt according to the procedure below:
1. Use a high quality sealing material such as Scotch 23 Tape ¾” wide, to ensure IP‐67
compliant protection against water and dust.
2. Cut two pieces each 25 cm long, of Scotch 23 splicing tape. Remove the plastic
cover to expose the tacky side of the sealing tape as shown in Figure 1‐55.
Figure 1‐55: Exposing the tacky side of the sealing tape
3. After connecting a cable to a unit, tighten the cable gland cap firmly and use the
insulation tape to fully cover the cable gland.
FinM Deployment Guide
For Regualtor Approval Only
Release 4.2.46
1‐28
Grounding
Site Installation
Figure 1‐56: Waterproofing an external connection
1.2.9 Grounding
All RADWIN products should be grounded during operation. In addition:
•
•
All units should be grounded by a wire with diameter of at least 10 AWG.
Units must be properly grounded to a Protective Ground in accordance with the Local
Electrical Regulations
Rack‐mounted equipment should be mounted only in grounded racks and cabinets.
Further, you should ‐
•
•
•
Always make the ground connection first and disconnect it last
Never connect telecommunication cables to ungrounded equipment
Ensure that all other cables are disconnected before disconnecting the ground
TBS
There is a grounding lug on the TBS as shown in Figure 1‐57. Ground it using 10 AWG wire.
FinM Deployment Guide
For Regualtor Approval Only
Release 4.2.46
1‐29
Grounding
Site Installation
Figure 1‐57: TBS: Grounding lug location
TMU
The grounding lug for the TMU is shown in Figure 1‐58. Ground it using 10 AWG wire.
Figure 1‐58: TMU: Grounding lug location
When mounted in a 19 in rack, the TMU is grounded via the rack.
FinM Deployment Guide
For Regualtor Approval Only
Release 4.2.46
1‐30
Grounding
Site Installation
PoE Device
There is a grounding lug on the PoE as shown in Figure 1‐59. Ground it using 10 AWG wire.
Figure 1‐59: PoE: Grounding lug location
When mounted in a 19in rack, the PoE is grounded via the rack.
ISU
The ISU is grounded via its ground connection on its front panel.
Figure 1‐60: ISU: Grounding lug location
Antennas
Ground external antennas using a suitable Grounding Kit such as an Andrew Type 223158‐2
(http://www.commscope.com).
FinM Deployment Guide
For Regualtor Approval Only
Release 4.2.46
1‐31
Train Side
Site Installation
1.3 Train Side
1.3.1 TMU
TMU ‐ Mounting
The TMU can be mounted in a 19 in rack, or on a wall. When mounting on a 19 in rack, use
the specially‐designed TMU‐PoE drawer.
Mounting with the TMU‐PoE drawer
The TMU‐PoE drawer is used to mount both the TMU and the PoE together. Carry out the
following steps to mount both units:
1. Choose a site for the TMU‐PoE drawer as close as possible to the on‐board antennas and
on‐board power supply. Make sure there is at least 12 cm/5 in of rack space.
2. Open the package, remove the TMU‐PoE drawer from the packing styrofoam, and
cut and discard the two black straps holding the mounting slides in place.
3. Check the contents:
Table 1‐3: TMU‐PoE drawer package contents
Item
No.
Description
Quantity
Tray
DC‐TMU Jumper cable
Allen wrench (M4)
Allen screws (M4x22)
Spring washers for Allen screws
DIN screws (M5x16)
12
Black finishing washers for M5 screws
12
Mechanical cage/nuts for M5 screws
12
FinM Deployment Guide
For Regualtor Approval Only
Release 4.2.46
1‐32
TMU
Site Installation
Figure 1‐61: TMU‐PoE drawer contents
FinM Deployment Guide
For Regualtor Approval Only
Release 4.2.46
1‐33
TMU
Site Installation
4. Detach the mounting slides from the TMU‐PoE drawer: Pull each slide out until it
is stopped by the locking lever. Press the locking lever to release the slide, and pull
slide out completely.
Pull slide
Mounting slide
Drawer
Locking Lever
Press Locking Lever
to release slide
Remove slide
Figure 1‐62: Remove the mounting slides from the TMU‐PoE drawer.
FinM Deployment Guide
For Regualtor Approval Only
Release 4.2.46
1‐34
TMU
Site Installation
5. Measure the distance between vertical rails of the rack.
Figure 1‐63: Measure distance between vertical rails
6. Adjust the location of the rear mounting flange of the first mounting slide so that
the distance between the holes of the mounting flanges are the same as the
distance you measured in the previous step.
Figure 1‐64: Adjust distance of rear mounting flange
FinM Deployment Guide
For Regualtor Approval Only
Release 4.2.46
1‐35
TMU
Site Installation
7. Place the second slide next to the first and adjust its rear mounting flange so that
the distance between the flanges are the same as that of the first slide.
Figure 1‐65: Adjust distance of mounting flange on second slide
8. Insert 8 mechanical cage nuts in the appropriate holes in the 19 in rack: 4 on each
side of the rack.
Figure 1‐66: Inserting cage nuts (one side shown)
FinM Deployment Guide
For Regualtor Approval Only
Release 4.2.46
1‐36
TMU
Site Installation
9. Place each mounting slide with the stopping flap towards the rear of the rack, and
using the Philips screws with the black washers, fasten the mounting slides to the
cage nuts and tighten.
Figure 1‐67: Placing and fastening mounting slide
10.Once both mounting slides are fastened tightly on the rack, insert the drawer as
follows:
a. Place the framework arms of the drawer into the mounting slides carefully. Make
sure they are straight.
b. Push back the drawer until the framework arms touch the ball‐bearing grey
housing.
c. While pressing outwards on both ball‐bearing grey housings, push the drawer in
further until the framework arms engage the ball‐bearing housings.
d. Further push the drawer until the locking lever stops it.
e. Release the locking levers, and push the drawer in all the way, even through some
resistance towards the end.
FinM Deployment Guide
For Regualtor Approval Only
Release 4.2.46
1‐37
TMU
Site Installation
Figure 1‐68: Inserting the drawer: Place arms straight
Push ball‐bearing
housing outwards
Figure 1‐69: Inserting the drawer: Push ball‐bearing housings outwards
FinM Deployment Guide
For Regualtor Approval Only
Release 4.2.46
1‐38
TMU
Site Installation
Press locking levers
and push drawer in
Figure 1‐70: Inserting the drawer: Release locking levers
11.Insert the other 4 cage nuts in the appropriate holes in the front side of the
vertical rails.
12.Using the other 4 Philips screws with the black washers, secure the drawer to the
front side of the vertical rails of the rack.
Figure 1‐71: Secure drawer to the front side of rack
FinM Deployment Guide
For Regualtor Approval Only
Release 4.2.46
1‐39
TMU
Site Installation
13.Attach PoE and TMU to drawer as follows:
a. Remove grounding lugs from both units (they interfere with the drawer and are not
needed for a drawer installation).
b. Place PoE over the pins of the left side of the drawer as shown, and attach using
allen screws.
Figure 1‐72: Attaching PoE to drawer
FinM Deployment Guide
For Regualtor Approval Only
Release 4.2.46
1‐40
TMU
Site Installation
c. Place TMU over the pins on the right side of the drawer as shown, and attach using
allen screws.
Figure 1‐73: Attaching TMU to drawer
The TMU and PoE, when mounted in the TMU‐PoE drawer, are grounded via the
mounting pins, through the 19 in rack.
Make sure the rack you are using is grounded properly.
FinM Deployment Guide
For Regualtor Approval Only
Release 4.2.46
1‐41
PoE Device for the TMU
Site Installation
Mounting on a wall
Both the PoE device and the TMU can be mounted on a wall.
1. Use screws appropriate for the wall surface on which the unit is to be mounted. Screws are
supplied by the customer.
2. Mount the PoE device close to the TMU so the DC‐TMU jumper cable can be easily
connected.
TMU ‐ External Connections
1. Attach DC‐TMU jumper cable to the PoE input sockets on the TMU as shown.
2. Attach antenna cables to the radio antenna conenctions (ANTx sockets) on the
TMU.
3. If the unit is not mounted in a 19 in rack, attach a ground cable to its ground lug.
4. To apply power to the TMU, attach a power cable to the DC IN port on the PoE
device. Apply voltage, and the units will be ON.
Figure 1‐74: TMU ‐ External Connections
1.3.2 PoE Device for the TMU
The DC PoE device is always mounted next to the TMU.
The units can be mounted in a 19 in rack or on a wall, or on a DIN rail.
Mounting with the TMU‐PoE drawer
The TMU‐PoE drawer is used to mount both the TMU and the PoE. Follow the instructions in
“Mounting on a wall” on page 1‐42.
FinM Deployment Guide
For Regualtor Approval Only
Release 4.2.46
1‐42
TMU Antennas
Site Installation
1.3.3 TMU Antennas
Each locomotive is fitted with three “Shark‐Fin” roof antennas as close as possible to the front
of the locomotive and the communications rack in that order of preference:
Figure 1‐75: “Shark‐Fin” antenna ‐ bottom view
To ensure a smooth horizontal mounting surface, a mounting table may be used. Two
variations are shown in Figure 1‐76 and Figure 1‐77 below:
Figure 1‐76: Roof Mounting Table for Shark‐Fin antenna
Figure 1‐77: Integrated Roof Mounting Table for Shark‐Fin antenna
FinM Deployment Guide
For Regualtor Approval Only
Release 4.2.46
1‐43
TMU Antennas
Site Installation
The screw, bolt and other moisture prone surfaces are coated with water proof silicone. The
vertical pipe welded at its ends to the kit and the train roof are conduits for the RF cable and
are completely waterproof.
Figure 1‐78: Shark‐Fin antenna installation schematic for table mounting
If the train roof is sufficiently flat and smooth, the mounting plate is not needed.
Whatever mounting arrangement is adopted:
•
•
The antennas should be mounted as close to the front of the locomotive as possible,
and no less than a meter apart.
There should not be any obstructions between the antennas and the front of the train
such as air‐conditioner units, electronic route number display boxes and the like.
•
Mount Antenna 1 and Antenna 2 on the edge of the locomotive at a 45o angle, as
shown in Figure 1‐79.
•
Mount Antenna 3 (center) at a 90o angle (directly up) and one third of the distance
between the right and left antennas as shown in Figure 1‐79.
Connect the antenna ports of the TMU to the antennas as shown in Figure 1‐80.
•
FinM Deployment Guide
For Regualtor Approval Only
Release 4.2.46
1‐44
TMU Antennas
Site Installation
Figure 1‐79: TMU antenna mounting configuration on roof
Figure 1‐80: TMU antenna port connection scheme
FinM Deployment Guide
For Regualtor Approval Only
Release 4.2.46
1‐45
TMU Antennas

Site Installation
To mount a Shark‐Fin antenna:
•
•
•
•
Keep away from catenary and high voltage lines
Be careful when working at heights!
Always secure ladders!
Always tighten screws!
•
ESD (electrostatic discharge) sensitive device. Always ground yourself while
handling the antenna
Avoid bringing the cover of the antenna into contact with acetone, gasoline or
oil
•
1. Prepare the mounting surface as shown in Figure 1‐81 below:
Figure 1‐81: Preparing the mounting surface
2. Prepare the roof mounting area: Clear the area where the antenna is to be mounted
from paint, corrosion or any anodized layer.
3. Use a scraper to clear this area of any dust, brake dust, cutting chips, oil or fatty
material.
4. If you are mounting the antenna on a bracket, mounting plate or table, use an
additional cable protection kit.
FinM Deployment Guide
For Regualtor Approval Only
Release 4.2.46
1‐46
TMU Antennas
Site Installation
5. To connect a grounding cable, an additional grounding kit should be used.
Figure 1‐82: Installation on bracket or table: Cable conduit and grounding kit
6. Mount the antenna to the mounting plate or roof. There are two methods as shown
in the next two diagrams:
Figure 1‐83: Bottom side mounting
Figure 1‐84: Top side mounting
7. Seal the screw enclosures and perimeter with silicone. There are two methods as
shown in the next two diagrams:
FinM Deployment Guide
For Regualtor Approval Only
Release 4.2.46
1‐47
TMU Antennas
Site Installation
Figure 1‐85: Sealing top side mounting
Figure 1‐86: Sealing bottom side mounting
8. Connect the RF cable as shown below:
In the final positioning of the antenna, the draining hole and the connectors must
be protected against environmental impact. Otherwise a cable conduit should be
used.
FinM Deployment Guide
For Regualtor Approval Only
Release 4.2.46
1‐48
TMU Antennas
FinM Deployment Guide
Site Installation
For Regualtor Approval Only
Release 4.2.46
1‐49
Chapter 2: Network Guidelines
2.1 Scope of This Chapter
This chapter provides a description of the typical networking topology required by RADWIN's
Fiber in Motion Train‐To‐Ground solution.
2.2 Overview
Included in this chapter are:
•
•
•
•
•
A general introduction to the network requirements for trackside and on‐board net‐
works,
A description of the required routers' functionalities,
A data flow description,
Sample IP and VLAN assignment guidelines,
A short description of the update messages during handovers, and how the recom‐
mended network topology supports these messages.
The typical networking described in this chapter enables broadband Train‐To‐Ground
communication, while maintaining a handover time of less than 50ms.
Follow the guidelines carefully. Any questions or clarifications should be
addressed to RADWIN's Professional Services team for an official response.
Prior to project rollout, a detailed network architecture (including topology and
HW to be used) should be shared with RADWIN for confirmation.
2.3 Track Side Network
The RADWIN Fiber in Motion solution is based on a transparent layer 2 architecture:
•
The backhaul network is connected to the Radio Base Stations (TBS) deployed along the
tracks side via GbE copper or fiber, as a layer 2 based network.
FinM Deployment Guide
For Regualtor Approval Only
Release 4.2.46
2‐1
Track Side Network
•
•
•
•
•
•
•
Network Guidelines
The backhaul network (existing or provided by the system integrator/customer) is used
to aggregate traffic to/from the TBSs and send it to the control/data centres.
The required network architecture must have a single core router, and L2 switches. All
data communication to/from the train will pass via this router.
A redundant ISU is provided to ensure higher resiliency of the solution.
The TBS's network is synchronized either via GPS‐based system (for above ground sce‐
narios) or via Ethernet‐based synchronization (for above or underground scenarios).
For GPS based synchronization, the TBS integrated GPS Synchronization Unit is used.
For Ethernet‐based synchronization, the TBS's network will be synchronized by Ethernet
based synchronization, running over the same data backhaul network. The implementa‐
tion of the synchronization protocol is via an Indoor Synchronization Unit ‐ ISU (pro‐
vided by RADWIN), that is connected to one of the network switches, and provides the
master clock to all TBSs in the network.
The synchronization architecture may vary depending on the specific network topology,
so RADWIN needs to evaluate and approve the trackside network topology and assure it
will support the synchronization protocol. Typical synchronization requirements
include:
• Layer 2 connection between all ISUs and TBSs.
• Maximum of 4 switches between ISUs and each TBS.
• Avoid high line speed utilization to prevent introduction of jitter and latency. The
line load should be limited according to the following table:
Table 2‐1: ISU‐TBS switches vs. line utilization
•
•
•
•
Number of Switches Between ISU and TBS
Maximal Line Utilization
95%
85%
75%
65%
Network switches should appropriately handle the system's relearning frames. These
frames are VLAN tagged (802.1Q). Switch should forward the relearning traffic and
update FIB (Forwarding Information Base). (See chapters 9 & 10 for more information
on the update messages).
IEEE802.3az must be disabled on all switches.
Spanning tree between train and track side is not supported and must be disabled on
switch ports connected to the radios.
Static routing should be implemented between track side core router and on‐board
routers. Implementation of dynamic routing protocols should be confirmed with RAD‐
WIN professional services.
FinM Deployment Guide
For Regualtor Approval Only
Release 4.2.46
2‐2
Train Side (On‐board) Network
Network Guidelines
Figure 2‐1: Typical track side network arrangement
2.4 Train Side (On‐board) Network
•
•
•
•
•
•
•
•
A Mobile Radio unit (TMU) is deployed at each end of the train. It is connected, via a
PoE, to the train's internal network (Train network is responsibility of SI). This topology
enables on‐board redundancy and improved performance by an Intra‐Train Handover
mechanism (ITHO).
L2 connectivity is required between both TMUs
TMUs and train router should be on the same IP subnet
Train equipment (APs, CCTV cameras, PIS devices etc.) should be on a different subnet
from that of the TMU
All of the train's traffic is sent via an on‐board router (provided by SI) to the active TMU
providing the highest throughput (which TMU is considered “active” is automatically
determined by the system).
The on‐board train network should support VLANs
Network switches should appropriately handle the system's relearning frames. These
frames are VLAN tagged (802.1Q) and switch should forward the relearning traffic and
update the FIB (Forwarding Information Base)
IEEE802.3az should be disabled on all switches
FinM Deployment Guide
For Regualtor Approval Only
Release 4.2.46
2‐3
Train Side Physical Connectivity
•
Network Guidelines
Spanning tree between train and trackside is not supported and must be disabled on
switch ports connected to the radios.
Figure 2‐2: Typical train side network (logical connectivity)
2.5 Train Side Physical Connectivity
Figure 2‐3 presents an example of a typical physical connectivity within an on‐board network.
On‐board router must be connected through 1 physical port, but this port must support at
least 2 sub interfaces (router on a stick / one armed router implementation). Each sub
interface must have its own IP address and VLAN to enable the IP scheme detailed in Section
2.7, below.
Figure 2‐3: Typical train side network (physical connections)
FinM Deployment Guide
For Regualtor Approval Only
Release 4.2.46
2‐4
Track Side Core Router
Network Guidelines
2.6 Track Side Core Router
The track side network requires a core router that will act as the gateway between the Train‐
To‐Ground system and the client's core network. All traffic between any train's on‐board
devices and the client's core network must pass through this router. The track side core router
must have at least 2 interfaces (see diagram below in Section 2.7):
Interface 1:
Connects to the client's core network. It will be on the same subnet as the
client's network and will be the gateway for all traffic from the client network
targeted at devices on board trains.
Interface 2:
Used for the Train‐To‐Ground network. It will be on the same subnet as the on‐
board router interface 1 and will be the gateway for all traffic from the on‐
board routers on all the trains.
All traffic between any on‐board device and the trackside must pass through the on‐board
router.
2.7 Basic IP Scheme and Data Flow Path
An example of the basic IP scheme is shown here.
The traffic flows between the track side core router and the on‐board router. All elements
between the routers (including switches and FiberinMotion radios) are pure L2 devices. They
have an IP address for management only, and are transparent to the data traffic.
Overall, at least 3 IP subnets are required:
•
•
•
Subnet A for the client core network.
Subnet B for the train to ground segment.
Subnet C for the on‐board network.
FinM Deployment Guide
For Regualtor Approval Only
Release 4.2.46
2‐5
Basic IP Scheme and Data Flow Path
Network Guidelines
Figure 2‐4: Basic IP Scheme and Data Flow
FinM Deployment Guide
For Regualtor Approval Only
Release 4.2.46
2‐6
Recommended VLAN Assignment
Network Guidelines
2.8 Recommended VLAN Assignment
A typical VLAN assignment throughout the network would include the following:
•
•
•
•
VLAN V1 ‐ For TBS and ISU management
VLAN V2 ‐ For trackside synchronization (Between ISU and TBSs)
VLAN V3 ‐ For:
• User traffic (between trackside core router and on‐board router)
• TMU management
• Signalling between two on‐board TMUs (to support intra train hand over in dual
TMU per train deployment)
VLAN V4 ‐ Train on‐board internal network (for all train end user devices ‐ end user APs,
IP cameras, IP phones, etc.)
FinM Deployment Guide
For Regualtor Approval Only
Release 4.2.46
2‐7
Recommended VLAN Assignment
Network Guidelines
Figure 2‐5: VLAN Assignment
FinM Deployment Guide
For Regualtor Approval Only
Release 4.2.46
2‐8
Inter Base Handover (IBHO) Update Message
Network Guidelines
2.9 Inter Base Handover (IBHO) Update
Message
As mentioned, Fiber in Motion provides L2 connectivity, so all L3 features (routing etc.) are
handled directly between the on‐board router and the track side core router. The advantage
of this mode of operation is that no routing updates are needed during handovers, facilitating
the continuous fast handovers needed as the train moves along the track.
However, there will be other L2 devices (switches) along the track side network that must be
updated.
When a TMU moves from one TBS to the next, there must be an update of the track side
network so the switches know the new data path. This update is made by sending an update
message to the track side core router. However, we do not wish to send an update message
for each on‐board device. This will overload the system. For this reason, the update is sent
regarding only 1 device ‐ the MAC address of the on‐board router (since all the on‐board
devices are behind it, they do not need to have individual update messages sent).
FinM Deployment Guide
For Regualtor Approval Only
Release 4.2.46
2‐9
Inter Base Handover (IBHO) Update Message
Network Guidelines
Consider the diagram shown in Figure 2‐6, where a TMU is connected to the first TBS (TBS‐1)
and all traffic flows in the green path:
Figure 2‐6: IBHO ‐ Part 1
FinM Deployment Guide
For Regualtor Approval Only
Release 4.2.46
2‐10
Inter Base Handover (IBHO) Update Message
Network Guidelines
When the TMU has made a decision to switch from TBS‐1 to TBS‐2 (based on RSS thresholds)
it initiates an update message (shown in blue in Figure 2‐7) to the track side core router, with
the source MAC address of the on‐board router.
All switches along the track side network's new data path are then updated.
Figure 2‐7: IBHO ‐ Part 2
As a result, the TMU is connected to TBS‐2 and all traffic flows in the new path (shown in
green in .
FinM Deployment Guide
For Regualtor Approval Only
Release 4.2.46
2‐11
Intra Train Handover (ITHO) Update Message
Network Guidelines
Figure 2‐8: IBHO ‐ Part 3
2.10 Intra Train Handover (ITHO) Update
Message
Parallel to the Inter Base Handover (IBHO) process, described above, Fiber in Motion also
supports an Intra Train Handover.
The ITHO feature, implemented in the TMUs, enables extended coverage and throughput. As
mentioned above (see Train Side (On‐board) Network on page 2‐3) this mode requires 2 on‐
board TMUs (ideally at each end of the train), with L2 connectivity between them.
FinM Deployment Guide
For Regualtor Approval Only
Release 4.2.46
2‐12
Intra Train Handover (ITHO) Update Message
Network Guidelines
This process happens in parallel and independently from the IBHO. The background process
consists of a continuous evaluation between the 2 on‐board TMUs, as to which can receive
the higher throughput (regardless of which base they are connected to).
When an ITHO occurs, an update must also be sent to the on‐board router. This update will
refresh the switches along the new data path as to the new active TMU.
Consider Figure 2‐9 where it is shown that TMU‐A is connected to TBS‐1 and is ACTIVE
(passing traffic). All traffic flows in the green path.
TMU‐B is PASSIVE. It has an idle connection to a TBS and it monitors the potential throughput,
but does not pass traffic.
Figure 2‐9: ITHO ‐ Part 1
FinM Deployment Guide
For Regualtor Approval Only
Release 4.2.46
2‐13
Intra Train Handover (ITHO) Update Message
Network Guidelines
The Intra Train Handover mechanism discovers that a higher throughput can be achieved
through TMU‐B, defined at present as PASSIVE. (TMU‐B may be connected to the same TBS as
TMU‐A or to a different one ‐ this does not affect the ITHO).
An ITHO is therefore initiated and TMU‐B is re‐defined as ACTIVE. TMU‐B then sends 2 update
messages (marked in blue in Figure 2‐10):
•
•
Update message to track side core router with on‐board router MAC ‐ to update the
track side L2 network of the new data path (same process as in the IBHO update
described above)
Update message to the other TMU (TMU‐A) with the track side core router MAC ‐ to
update the train L2 network of the new data path.
Figure 2‐10: ITHO ‐ Part 2
FinM Deployment Guide
For Regualtor Approval Only
Release 4.2.46
2‐14
Intra Train Handover (ITHO) Update Message
Network Guidelines
All on‐board traffic now flows through TMU‐B to TBS‐2 in the new green path:
Figure 2‐11: ITHO ‐ Part 3
FinM Deployment Guide
For Regualtor Approval Only
Release 4.2.46
2‐15
Chapter 3: Configuring the
Radio Network
3.1 Scope of This Chapter
This chapter shows how to work with the Configurator, and provides a few examples of some
parameters. It also includes some tips and advice for best practices when working with the
Configurator.
3.2 Connecting to the Units
For a first time configuration, all units are set to an IP address of 10.0.0.120 with subnet mask
255.0.0.0. The laptop Ethernet card should be set to a free IP address on that subnet (for
example 10.0.0.111).
All of the TBSs and any ISUs needed must be physically installed before you can work with the
Configurator.
ISUs are required only in an environment that does not have access to a GPS signal
(tunnels, stations, etc.)
3.3 About the Configurator
The Configurator is used to configure each active device used in your project: TMUs, TBSs,
and ISUs. You also use the Configurator to set many general parameters including IP address
details, gateways, frequencies and bandwidths, and much more.
To use the Configurator you must have MS Excel 2007 or later installed on your
laptop(s).
FinM Deployment Guide
For Regualtor Approval Only
Release 4.2.46
3‐1
Method of Operation
Configuring the Radio Network
The Configurator is an Excel file that consists of five tabs:
Main:
Provides an overview of the contents of the project, as well as various buttons from
which you can configure specific devices. See Main Tab.
Project: Allows you to enter various project‐wide parameters, such as the frequencies and
bandwidths used, synchronization, units’ power, QoS, VLAN, and Ethernet mode,
and more. See Project Tab.
Line:
Allows you to enter the IP addresses of the various devices and gateways used, VLAN
definitions and more. See Line Tab.
Towers: Allows you to enter the IP addresses of the various TBSs in the project in addition to
their neighbors. See Towers Tab.
Trains: Allows you to define the rail cars that will be in the project and their TMUs. See Train
Tab.
3.3.1 Method of Operation
Briefly, work with the Configuratior file as follows:
•
•
•
•
Change whatever values need to be changed using the Configurator file,
Click on Recalc all data (if needed: see page 3‐5), then
Save the file.
Once the file is saved, apply the values using either the Configure Unit button (see
page 3‐4), or the HBS Batch Configuration button (page 3‐4).
The Configurator will connect with the units, and apply the changes.
3.4 Using the Configurator
Click on the desktop icon to start the Configurator. The file will open, and the Main tab will
appear.
3.4.1 Main Tab
The Main tab is shown in Figure 3‐1:
FinM Deployment Guide
For Regualtor Approval Only
Release 4.2.46
3‐2
Main Tab
Configuring the Radio Network
Figure 3‐1: Configurator ‐ Main tab
Table on top right:
FinM Deployment Guide
Release 4.2.46
For Regualtor
Approval Only
3‐3
Main Tab
Configuring the Radio Network
Set items in this table first, before carrying out any other tasks on this tab.
Figure 3‐2: Main tab: Pre‐Conditions
Mode: Shows the mode of the Configurator (Protected or Unprotected)
Download software:
Determines working details of the Configure Unit and HBS Batch Configuration
buttons as follows:
No means that changes you make using the Configure Unit or HBS Batch
Configuration buttons will affect this Configurator file only, and will not be
downloaded to any units.
Configuration Only means that the changes you make using the Configure Unit
or HBS Batch Configuration buttons will affect this Configurator file and will be
downloaded to the relevant units. You must make sure that the radio units in
use have the required firmware installed on them.
Configuration & Release means that the changes you make using the
Configure Unit or HBS Batch Configuration buttons will affect this Configurator
file, the system will then check if the relevant radio units need a firmware
update and if so, will update them, and only then will download the changes
you have made to the relevant units.
Compare/Verify instructs the system to compare the configuration of the
relevant units as opposed to the configuration as shown in the file as it is at
present (it relates to the open Excel file, and not the file saved on disk).
Verify Hardware: Not for customer use.
Line: Indicates for which line you are making configuration changes. This affects any
changes you make using the Configure Unit or HBS Batch Configuration buttons.
Configure Unit:Click to open the Configurator dialog box. This enables you to configure
individual units, one at a time. The line shown is determined by the value in
the Line window. See Configuring Network Units.
About...
Click to open a window showing the software version of the Configurator
application.
Protect
Click to protect the Configurator file from being changed.
Unprotect
Click to allow the Configurator file to be changed. Password: psfiberinmotion
HBS Batch Configuration:
FinM Deployment Guide
For Regualtor Approval Only
Release 4.2.46
3‐4
Project Tab
Configuring the Radio Network
Once you have made changes in this file, recalculated any needed values, and
saved the file, click this button to apply those changes to all of the TBSs,
instead of just one at a time. A command line interface window will open, and
the update status of each unit will be shown.
Changes for only one line are done, as determined by the value in the Line
window.
Recalc all data:After you have made changes to various parameters as described throughout
this chapter, before applying them to any units, click this to re‐calculate all
other parameters that may have been affected by your changes. This does not
apply any changes to any units.
Lower Table: Provides an overview of the equipment and lines used in the whole project.
3.4.2 Project Tab
The Project tab holds general configuration parameters that apply across the project.
Upper Table
The upper table of the Project tab is shown in Figure 3‐3:
FinM Deployment Guide
For Regualtor Approval Only
Release 4.2.46
3‐5
Project Tab
Configuring the Radio Network
Figure 3‐3: Configurator ‐ Project tab, upper table
Band:
Click this pull‐down menu to choose the frequency band to be
used for the project. Only those bands that are in accordance
with your regulatory environment will appear.
Channel Bandwidth:
Click this pull‐down menu to choose the bandwidth to be used
for this project. The frequencies used in the Tower tab (F1, F2,
F3, etc) will be the base frequency chosen in Band, with the
bandwidth added.
Note that not all frequency bands allow all bandwidths to be
used.
Synchronization:
Click this pull‐down menu to choose the type of synchronization
used in this project:
Integrated GPS: Use a GPS unit integrated in the TBS. Used in
above ground scenarios.
FinM Deployment Guide
For Regualtor Approval Only
Release 4.2.46
3‐6
Project Tab
Configuring the Radio Network
GSU: Use an external GPS unit. Used in above ground scenarios.
Note that this requires extra installation and configuration for
the GSU.
ISU: Use the Indoor Synchronization Unit. Used in below ground
scenarios.
None: Do not use synchronization
Desired Tx Ratio
(downlink/uplink):
Symmetric (50/50): Use this if there is no significant difference
in the transmission conditions between TBS‐>TMU and TMU‐
>TBS.
Max Uplink (20/80): Use this if your project requires the uplink
(TMU‐>TBS) to be much stronger than the downlink (TBS‐
>TMU).
Uplink (30/70): Use this if your project requires the uplink (TMU‐
>TBS) to be stronger than the downlink (TBS‐>TMU).
Downlink (70/30): Use this if your project requires the downlink
(TBS‐>TMU) to be stronger than the uplink (TMU‐>TBS).
Max Downlink (80/20): Use this if your project requires the
downlink (TBS‐>TMU) to be much stronger than the uplink
(TMU‐>TBS).
Tx Power, HBS [dB]:
Set the value that will give you the best throughput with the
least noise. Maximum radiated output power shall not exceed
36 dBm EIRP (FCC regulatory environments).
Tx Power, HMU [dB]:
Set the value that will give you the best throughput with the
least noise. Maximum radiated output power shall not exceed
36 dBm EIRP (FCC regulatory environments).
Traps Filter On:
Enable this to filter the traps to those that are relevant for your
project. If this is not enabled, then every change or trap ‐ not
matter how trivial ‐ will be recorded, and your traps list will
quickly become very large and cumbersome.
We recommend to enable this parameter.
VLAN Management:
Enable if your project is using a VLAN.
FinM Deployment Guide
For Regualtor Approval Only
Release 4.2.46
3‐7
Project Tab
Adaptive Modulation
Mode:
Configuring the Radio Network
MIMO: (Multi‐In, Multi‐Out) Set the transmission method to use
one data stream, but multiple data signals. This is useful in a less
noisy environment that requires a higher capacity, but where
drops will not likely occur, such as when the train is stopped at a
station.
Diversity: Set the transmission method to use more than one
data stream. This is useful when the train is travelling in a noisy
environment or when drops are likely to occur, such as during
fast movement.
Auto MIMO/Diversity: Set the system to automatically detect
the conditions to switch between MIMO and Diversity.
Write Community:
Set the link password here.
QoS Mode:
Quality of Service (QoS) is a technique for prioritization of
network traffic packets during congestion. RADWIN products
support two classification criteria, VLAN based or Diffserv based.
Choose which criterion to use. For more details on working with
QoS (see Lower Table: Quality of Service (QoS) Options on
page 3‐10).
None: Do not enable QoS
VLAN: Choose the VLAN criterion for QoS
Diffserv: Choose the Diffserv criterion for QoS
Max Distance:
Enter the maximum distance between the TBSs and the TMUs.
Make sure to enter the units in column C.
GSU Tx Ratio (down‐
link/uplink):
Set this the same as Desired Tx Ratio. If it is not the same, GPS
synchronization will not work properly.
Base Ethernet Mode:
Set the ethernet mode for the TBSs. Use manual configuration
when attached external equipment does not support auto‐
negotian.
Auto Sense: Detect the line speed and duplex mode
automatically, and apply those values.
Auto Sense (100M/b): Start at 100M/b, but detect the line
speed and duplex mode automaticall, and change it if necessary
from 100M/b.
Force 100 Full Duplex: Choose 100M/b and full duplex for the
line speed and duplex mode.
FinM Deployment Guide
For Regualtor Approval Only
Release 4.2.46
3‐8
Project Tab
Intra Train Handover
Operation:
Configuring the Radio Network
Sets which data stream direction is used to judge when to carry
out the intra‐train handover.
Uplink: Check the uplink direction (TMU‐> TBS) only when
determining when to carry out the intra‐train handover.
Aggregate: Check both the uplink and downlink directions, and
use an average of the signal strength value when determining
when to carry out the intra‐train handover.
Downlink: Check the downlink direction (TBS‐>TMU) only when
determining when to carry out the intra‐train handover.
Limited spectrum
mode:
Used for Interference Mitigation for Co‐channel Neighbors (see
Interference Mitigation for Co‐channel Neighbors on page 3‐18).
If your project uses 3 or fewer frequencies, then we recommend
you use this option.
If your project uses more than 3 frequencies, this option is not
needed.
EHSS jitter mitigation:
Ethernet Hub Site Synchronization jitter mitigation: If there is a
high level of track side network jitter, set this to Yes to minimize
the adverse affect of jitter on transmission synchronization.
Network ID:
A 4‐letter term that represents the network. This “name” is used
in a variety of places.
Traps Destinations:
IP address of the trap destination device. For redundancy, you
can have up to 10 different destinations. Separate their IP
addresses with a comma.
Time Zone:
Enter the number of minutes that the system is ahead of
Greenwich Mean Time (GMT or UTC).
Number Of Trains per
Base:
Enter the total number of TMUs per TBS (the value is actually
the number of TMUs, not trains). Each TBS needs this value to
manage its resources. There can be up to two TMUs per train,
and up to 6 TMUs per TBS total.
GPS Antenna
Configuration:
Integrated: If your TBS units have an integrated GPS capability,
select this option.
External: If your TBS units do not have an integrated GPS
capability, select this option. Note that in this case an external
GPS Unit (GSU) will be required to implement GPS
synchronization.
None: If you are not using GPS synchronization, select this
option.
FinM Deployment Guide
For Regualtor Approval Only
Release 4.2.46
3‐9
Project Tab
Product:
Configuring the Radio Network
N: Choose this option if you are using the 802.11n radio
transmission standard.
AC: Choose this option if you are using the 802.11ac radio
transmission standard.
Lower Table: Quality of Service (QoS) Options
The lower table of the Project tab allows you to set QoS options.
The lower table of the Project tab is shown in Figure 3‐4 (VLAN criteria shown):
Figure 3‐4: Configurator ‐ Project tab, lower table
QoS Overview
A variety of traffic types containing different content can travel throughout the network, and
as a result through RADWIN equipment. Certain types are more sensitive to delays than
others, and as such the ethernet network places a tag on each packet representing its priority.
The RADWIN Quality of Service feature (QoS) can work with two different standards of traffic
prioritization: VLAN (IEEE 802.1q/p) and Diffserv (RFC 2475). Each of these standards divides
the priorities differently: VLAN uses 8 levels, while Diffserv uses 64 levels.
RADWIN equipment can recognize these network priority tags, and can place the traffic in
one of 4 different QoS priority levels, as shown in Table 3‐1:
Table 3‐1: Default priorities and allocation by VLAN vs. Diffserv
QoS Priority Level
Real Time
Near Real Time
Standard Priority
Typical Use
Diffserv
VLAN
48‐63
6‐7
High priority: video conferencing, phone
calls, etc.
4‐5
Slightly lower priority than Real Time, but
with high‐quality delivery with guaranteed
minimum latency. Streaming video, internet
sites.
32‐47
Controlled Load
16‐31
2‐3
Similar to Best Effort in uncongested
conditions. A very high percentage of
transmitted packets will be delivered
successfully and not exceed the minimum
delay. Does not guarantee minimum latency.
Best Effort
0‐15
0‐1
Lowest priority: email, messaging, etc.
FinM Deployment Guide
For Regualtor Approval Only
Release 4.2.46
3‐10
Project Tab
Configuring the Radio Network
That is, if working with the Diffserv standard, traffic tagged with priority levels from 48 to 63
are treated as “Real Time”, those with levels from 47 to 32 are treated as “Near real time”, etc.
The RADWIN Quality of Service feature (QoS) allows you to change which standard priority
level is translated into a priority level used in RADWIN equipment.
Example: If you know your network will have a great deal of higher priority traffic, but you
only want the highest to receive preferential treatment, you can define “Real Time” as
being from 55 to 63, instead of the default values 48‐63. You must cover all levels, so in
this case, make sure to re‐define “Near Real Time” as 32 to 54.
Percentages: You can set each priority level (in the upload and download direction separately)
to take up a certain percentage of the total traffic, so long as that percentage adds up to 100.
MIR: You can also place an absolute maximum limit on the amount of traffic allowed to pass
per priority level, no matter how much traffic comes through.
Setting up QoS
QoS for Transportation FiberinMotion is set up in two phases:
1. Choose the QoS priority standard: Project tab, upper table, QoS Mode
(Choose None, VLAN, or Diffserv)
The lower table will show the default values according to the standard you have chosen.
2. Configure the values for each quality group: Project tab, lower table:
Figure 3‐5: Configurator ‐ Project tab, lower table (VLAN options)
Figure 3‐6: Configurator ‐ Project tab, lower table (Diffserv options)
Min: Set the minimum standard priority level that the QoS category will receive:
• In Figure 3‐5 (showing values according to the VLAN standard), Real Time has a
minimum of 6.
• In Figure 3‐6 (showing values according to the Diffserv standard), Real Time has a
minimum of 48.
FinM Deployment Guide
For Regualtor Approval Only
Release 4.2.46
3‐11
Line Tab
Configuring the Radio Network
Max: Set the maximum standard priority level that the QoS category will receive.
• In Figure 3‐5 (showing values according to the VLAN standard), Real Time has a maximum of 7.
• In Figure 3‐6 (showing values according to the Diffserv standard), Real Time has a maximum of 63.
You must make sure to cover all the priority levels, otherwise the system will
create errors. No warning will be given.
3. Downlink % and Uplink % : Set the percentage of traffic each QoS category is to be allotted. This can be different for the downlink (TBS
‐> TMU) or uplink (TMU ‐>TBS) direction. If traffic of a certain QoS level is more than this percentage, it is treated as Best Effort.
The percentages cannot add up to more than 100, otherwise the system will
create errors. No warning will be given.
If the percentages add up to less than 100, the unused priority will be distributed
to the remaining priorities.
4. Downlink MIR and Uplink MIR: Optional. If you want to limit traffic of a certain QoS level to a certain rate, enter that rate here, in
Mbps (max: 100).
3.4.3 Line Tab
The Line tab is shown in Figure 3‐7:
FinM Deployment Guide
Release 4.2.46
For Regualtor
Approval Only
3‐12
Line Tab
Configuring the Radio Network
Figure 3‐7: Configurator ‐ Line tab
Enter the various IP addresses for the devices shown.
The devices on the first line of the worksheet are associated with Line 1, those on the second
line with Line 2, etc.
No.
Enter the line number.
HMU Gateway:
TMU gateway for all TMUs on the line. The individual IP
addresses of the TMUs on the rail cars are defined in the Train
tab (see Train Tab on page 3‐17).
HMU Subnet:
TMU subnet for all TMUs on the line.
HBS Gateway:
TBS gateway for all TBSs on the line. The individual IP addresses
of the TBSs are defined in the Towers tab (see Towers Tab on
page 3‐15).
HBS Subnet:
TBS subnet for all TBSs on the line.
HMU Management
VLAN:
VLAN definition for all TMUs.
HBS Management
VLAN:
VLAN definition for all TBSs.
Synchronization VLAN:
VLAN definition for all ISUs.
Synchronization
Domain ID:
Domain ID for all ISUs.
L2 Learning VLAN:
VLAN definition for the data (traffic) stream. Called “learning”
because it relates to the fact that each TBS must learn about the
new TMU that is coming into its range.
ISU IP:
IP address for the primary ISU in the line
Backup ISU IP:
I IP address of the secondary ISU in the line
Line:
The name of the line. This name will be used in several places,
so use a logical term.
FinM Deployment Guide
For Regualtor Approval Only
Release 4.2.46
3‐13
Line Tab
Color:
Configuring the Radio Network
Each line has a separate color, helping you to keep things
organized. Set the background color for the line here. The color
is shown, and is also used as a background for the Configure
Unit dialog box (see Configuring Network Units on page 3‐25), in
the Towers tab (see Towers Tab on page 3‐15), and the Train tab
(see Train Tab on page 3‐17).
The first two digits are for the Red color component (Hex format
from 00 for black to FF for Red), the next two are for the Green
color component (Hex format from 00 for black to FF for Green),
and the last two are for the Blue color component (Hex format
from 00 for black to FF for Blue).
Table 3‐2: Color Codes
Additional Learning
VLANs
FinM Deployment Guide
Value
Color
#FF0000
Red
#00FF00
Green
#0000FF
Blue
#FF00FF
Magenta
#00FFFF
Cyan
#FFFF00
Yellow
Not for customer use
Release 4.2.46
For Regualtor
Approval Only
3‐14
Towers Tab
Configuring the Radio Network
HBS NTP Server:
IP address of the Network Timing Protocol server for all TBSs in
the network.
HMU NTP Server:
IP address of the Network Timing Protocol server for all TMUs in
the network.
3.4.4 Towers Tab
The Towers tab is shown in Figure 3‐8:
Figure 3‐8: Configurator ‐ Towers tab
Use the Towers tab to define the connectivity characteristics of all TBSs in the project.
In some versions of the Configuration file, some of the fields are linked to others. This is project‐specific and may not be relevant for your project.
You must verify that all values entered are the correct ones.
No.
Sequence number of the TBS in the whole project.
Name
Enter a name for the TBS. Choose a logical name, as this name is
used in many places.
FinM Deployment Guide
Release 4.2.46
For Regualtor
Approval Only
3‐15
Towers Tab
Configuring the Radio Network
ACC‐BS
IP address of the TBS unit.
Frequency
From the pull‐down menu, choose the frequency at which the
TBS unit will work.
The frequencies are determined by Band: and Channel
Bandwidth: values in the Tower tab. F1, F2, F3, etc will be the
base frequency chosen in Band, with the value chosen in
Channel Bandwidth added.
For example, if the Band chosen is 5.475‐5.720 GHz, and the
bandwidth is 40MHz, then F1 = 5.475GHz, F2 = 5.515GHz, F3 =
5.555GHz, etc.
kHz
The frequency in kHz is shown automatically as a result of your
choice in the Frequency column.
Frequency Neighbors
Shows the frequencies of the neighbors of the TBS. The values
shown depend on the names of the neighbors you enter in the
Base Neighbors column.
Line
Choose the number of the line here, preceded by a zero.
Dir
Write 1 if there is one TBS that serves both directions, write 2 of
there is a TBS for each direction.
No.
Sequence number of the TBS in the specific line.
Base Neighbors
Enter the name(s) of each TBS that is close enough to be
considered a neighbor. Be careful to enter the exact same term
for the neighboring TBS as shown in the Name column for that
unit. Separate multiple values by a comma.
IP Neighbors List
Shows the IP addresses of the neighboring TBS units in
accordance with the list you created in the Base Neighbors
column.
Neighbor Line No.
Shows, in order, the line number for each neighboring TBS unit,
n accordance with the list you created in the Base Neighbors
column.
Co‐Channel Neighbor
Used for Interference Mitigation for Co‐channel Neighbors. (see
Interference Mitigation for Co‐channel Neighbors on page 3‐18).
If your project uses 3 or fewer frequencies, then we recommend
you use this option.
Enter the name(s) of the co‐channel neighbor(s). If there are
more than one, separate them by a comma (no spaces!).
Co‐Channel Neighbor‐
sIPs
FinM Deployment Guide
Shows the IP address(es) of the co‐channel neighbor(s) in
accordance with the names you recorded in the Co‐Channel
Neighbor column. Used for Interference Mitigation for Co‐
channel Neighbors.
For Regualtor Approval Only
Release 4.2.46
3‐16
Train Tab
CNIndex
Configuring the Radio Network
Indicates which TBS will use which timeslots in the frame, in the
Interference Mitigation for Co‐Channel Neighbors option.
3.4.5 Train Tab
The Train tab is shown in Figure 3‐9:
Figure 3‐9: Configurator ‐ Train tab
No.
Sequence number of the TMU in the whole project.
IP
IP address of the TMU.
Line
Line on which the TMU works.
Num
When two TMUs are used on a car, set here which TMU is “1”
and which one is “2”. This is not necessarily the “active” or
“passive” TMU; that is determined by conditions in the field and
can change from minute to minute.
Car #1
Name of Car #1. Choose a logical name, as this name is used in
many places.
(Car #2)
(Optional) Name of Car #2. Choose a logical name, as this name
is used in many places.
Car #1 Router IP
IP address of router in Car #1.
Note that this is the IP address of the router, and not of the
TMU, or any other individual piece of equipment on board. This
keeps the network simple ‐ as the TBS, ISUs, and other items
relate to this single IP address, and not to the many IP addresses
of the individual items of equipment.
FinM Deployment Guide
For Regualtor Approval Only
Release 4.2.46
3‐17
Interference Mitigation for Co‐channel Neighbors
Configuring the Radio Network
3.5 Interference Mitigation for Co‐channel
Neighbors
If your system uses 3 or fewer frequencies, we recommend that you use the Co‐Channel
Neighbor Interference Mitigation method described here to reduce interference between
TBSs.
•
•
This method is used in addition to the Hub Site Synchronization method.
If your system uses more than 3 frequencies, this method of interference mitigation is
not needed.
3.5.1 Basic Situation
The three frequencies are used on the TBSs in a staggered fashion: TBS1 uses F1, TBS2 uses
F2, TBS3 uses F3. The pattern is then repeated: TBS4 has again F1, TBS5 has F2, TBS6 has F3,
and so on.
We assume that the nominal distance between each TBS is at least 500m (below ground;
above ground this value can be as large as 2000m). See Figure 3‐10.
co‐channel neighbors
TBS1
TBS2
co‐channel neighbors
TBS3
TBS4
TMU1
TBS5
TBS6
TMU4
500m
500m
500m
TBS7
TMU7
500m
500m
500m
Figure 3‐10: Co‐Channel Neighbors
At a given moment, a rail car (with TMU1) is synchronized with TBS1, and using frequency F1.
At this same moment, this rail car is about 1500 meters away from TBS4, which is also using
F11.
Any signal that TMU1 receives from TBS4 at this point is considered interference. If the signal
from TBS4 is strong enough, the interference can harm the throughput, and needs to be
mitigated.
1. If fewer than 3 frequencies are used, the values would be 1000m for two and 500m for one frequency.
FinM Deployment Guide
For Regualtor Approval Only
Release 4.2.46
3‐18
Necessary Pre‐Conditions
Configuring the Radio Network
This situation continues throughout the line ‐ TBS7 can interfere with TBS4/TMU4, and in turn
TBS4 can interfere with TBS7/TMU7. TBS7 can further interfere with TBS10, TBS10 can
interfere with TBS7 and TBS13, and so on down the line.
The two units that can interfere with each other are called “co‐channel neighbors”.
3.5.2 Necessary Pre‐Conditions
If the “Co‐Channel Neighbor Interference Mitigation” option is configured, it will be activated
or de‐activated automatically according to the conditions described below. Note that the
activation conditions and de‐activation conditions are not exactly symmetrical.
Activation Conditions
»
The TBS co‐channel neighbor is transmitting with the Primary TMU on its rail car1,
AND
»
The detected signal from the TBS co‐channel neighbor is above the threshold signal
strength for activation (see Table 3‐3).
Table 3‐3: Threshold signal strength levels ‐ activation criteria
Signal Strength between
TBS and TMU
Difference in signal
strength between TBS
and its co‐channel
neighbor
Activate Option?
‐70 or above
Greater than 16
No
‐70 or above
16 or less
Yes
‐74 to ‐71
Greater than 14
No
‐74 to ‐71
14 or less
Yes
‐78 to ‐75
Greater than 12
No
‐78 to ‐75
12 or less
Yes
‐79 or below
Greater than 9
No
‐79 or below
9 or less
Yes
De‐Activation Conditions
»
The TMU of the TBS co‐channel neighbor is re‐defined as the Secondary TMU,
OR
1. This is the “active” TMU. If the co‐channel neighbor is transmitting with its Secondary TMU, the signal will be
weaker and sporadic, resulting in a low enough interference level as to be insignificant.
FinM Deployment Guide
For Regualtor Approval Only
Release 4.2.46
3‐19
Method of Operation
»
Configuring the Radio Network
The detected signal from the TBS co‐channel neighbor is below the threshold signal
strength for de‐activation (the values are different from that of activation: see Table 3‐
4).
Table 3‐4: Threshold signal strength levels ‐ de‐activation criteria
Signal Strength between
TBS and TMU
Difference in signal
strength between TBS
and its co‐channel
neighbor
De‐Activate
Option?
‐70 or above
Greater than 20
Yes
‐70 or above
20 or less
No
‐74 to ‐71
Greater than 18
Yes
‐74 to ‐71
18 or less
No
‐78 to ‐75
Greater than 16
Yes
‐78 to ‐75
16 or less
No
‐79 or below
Greater than 13
Yes
‐79 or below
13 or less
No
3.5.3 Method of Operation
The co‐channel neighbor interference mitigation option works as follows:
Split timeslots: TBS1 is configured to split the timeslots in the frame between it and between
its “co‐channel neighbor” (in our case, with three frequencies, it’s with TBS4)1. The
result for the first co‐channel neighbor pair is that TBS1 transmits on half of the time
slots, and TBS4 transmits on the other half. See Figure 3‐11.
TMU1 is instructed to receive those timeslots that were assigned to TBS1, and ignore
others.
Notice that in our example, TBS1 and TBS7 are assigned the same timeslots. This is
not a problem because TBS1 and TBS7 are so far away from each other that their
mutual signals do not interfere.
Repeat for all co‐channel neighbors: This configuration is epeated with TBS2 vs. TBS5, again
with TBS3 vs. TBS6, and even with TBS7 vs. TBS4, and so on down the line.
1. Which TBS receives which timeslots is determined by the CNIndex parameter (see page 3‐24)
FinM Deployment Guide
For Regualtor Approval Only
Release 4.2.46
3‐20
Configuring the Co‐Channel Neighbor Interference Mitigation Option Configuring the Radio Network
TBS4
TBS1
TBS7
Timeslot assigned to TBS4
Timeslot assigned to TBS4
Timeslot assigned to TBS1 and TBS7
Timeslot assigned to TBS1
TMU1
TMU4
Receives TBS1 timeslots only
Receives TBS4 timeslots only
Timeslot assigned to TBS4
Timeslot assigned to TBS7
TMU7
Receives TBS7 timeslots only
Figure 3‐11: Dividing timeslots between co‐channel neighbors
This splitting of timeslots is enabled only if the activation conditions described above (see
Activation Conditions) are met.
Things can change rapidly, so at the moment the de‐activation conditions are met (see De‐
Activation Conditions), the division of timeslots is no longer carried out.
When the conditions return to the activation conditions, the division of timeslots is renewed.
3.5.4 Configuring the Co‐Channel Neighbor Interference
Mitigation Option
Configure each TBS for “Co‐Channel Neighbor Interference Mitigation” as follows:
5. Open the Configurator.
6. Select the Main tab
7. Click Unprotect.
8. Enter the password and click OK.
9. Select the Project tab (see Figure 3‐12):
FinM Deployment Guide
For Regualtor Approval Only
Release 4.2.46
3‐21
Configuring the Co‐Channel Neighbor Interference Mitigation Option Configuring the Radio Network
Figure 3‐12: Project Tab: Limited Spectrum Mode
10.Select the Limited Spectrum Mode option
11.Choose Reuse 3 from the pull‐down menu. This will instruct the system that you
are using 3 frequencies. If you are using 2 frequencies, choose Reuse 2, if you are
using 1 frequency, choose Reuse 1.
FinM Deployment Guide
For Regualtor Approval Only
Release 4.2.46
3‐22
Configuring the Co‐Channel Neighbor Interference Mitigation Option Configuring the Radio Network
12.Click the Towers tab:
Figure 3‐13: Towers Tab of the Configurator
•
•
•
•
•
•
•
•
Column A shows the number of each TBS.
Column B shows the “name” (or serial number) of each TBS.
Column AA shows the IP address of each TBS.
Column AJ indicates which frequency (F1, F2, or F3 in our example) is being used
for the specific TBS.
Column AK shows the value of the frequency in kHz.
Column AV shows the name(s) of the co‐channel neighbor(s).
Column AW shows the IP address(es) of the co‐channel neighbor(s).
Column AY shows the “CNIndex” (which timeslot the indicated TBS is to use).
We can see that in our example, we are re‐using F1 through F3
(columns of the Excel sheet not needed have been collapsed for clarity).
13.Record the co‐channel neighbor(s) of each TBS as follows:
FinM Deployment Guide
For Regualtor Approval Only
Release 4.2.46
3‐23
Configuring the Co‐Channel Neighbor Interference Mitigation Option Configuring the Radio Network
In column AV (Co‐channel Neighbors), record the name of the co‐channel neighbor TBS(s).
If there are two co‐channel neighbors, record each neighbor’s name separated by a
comma (no spaces!), as shown in Figure 3‐14:
Figure 3‐14: Recording Co‐Channel Neighbors
The IP address(es) of the co‐channel neighbor(s) appear automatically in column AW.
In our example, the co‐channel neighbor of TBS1 (BS.01.2.1) is BS.01.2.4, that of TBS2
(BS.01.2.2) is BS.01.2.5, and of TBS3 (BS.01.2.3) is BS.01.2.6.
Starting from TBS4, each TBS has two co‐channel neighbors: the neighbors of TBS4
(BS.01.2.4) are TBS1 (BS.01.2.1) and TBS7 (BS.01.2.7), and so on.
This pattern will repeat itself until the end of the line. The last three TBSs at the end of the
line, like the first three, will have only one co‐channel neighbor.
14.Complete recording all of the co‐channel neighbors for all TBSs in the specific line
(we have only recorded up to TBS9 in our example).
15.In column AY, record the CNIndex: This indicates which TBS will use which
timeslots in the frame ‐ the first part or the second part (see also Figure 3‐11).
Record 0 for the TBSs that will use the first part, and 1 for the TBS that will use the
second part.
In our example, TBS 1,2, and 3 use the first part of the timeslots in the frame (0 is
recorded), while TBS 4,5, and 6 use the second part of the timeslots. For TBS 7,8, and 9,
they again use the first part of the timeslots (so, for instance TBS4 always uses a different
part of the frame than its co‐channel neighbor: CNIndex 1 vs. CNIndex 0 for TBS1 and for
TBS7). The pattern repeats itself until the end of the line.
FinM Deployment Guide
For Regualtor Approval Only
Release 4.2.46
3‐24
Configuring Network Units
Configuring the Radio Network
16.Once you have entered all the necessary information, select the Main tab.
17.Click Recalc all data to update the system with the changes you have made, and
save the file.
3.6 Configuring Network Units
Configuring an Individual Unit:
To configure individual network units one at a time (TBS, TMU, and ISUs can be config‐
ured), click Configure Unit on the Main tab of the Configurator. This opens the Configura‐
tor dialog box. See sections see 3.6.1 on page 3‐25 through see 3.6.3 on page page 3‐29
for details on working with the Configurator dialog box.
Configuring Many Units at Once:
You can configure all the TBS units in the line, as determined by the value in the Line win‐
dow. Do this by clicking the HBS Batch Configuration button. This will take all of the
parameter values that are in this file for the specific line, and apply them to all of the TBS
units defined in the line. Connection is carried out according to the IP addresses as appear
in this file.
Configure all network units before you install them in the field.
3.6.1 Configuring Transportation Base Stations (TBSs)
Use this procedure to carry out changes in the configuration parameters of the TBSs. This
includes changing or setting its IP address.
1. For a first‐time configuration, connect the TBS’s PoE socket to a PoE device (see Site
Installation for connection instructions), and in turn, connect the PoE device to your
laptop or a LAN connection.
For a re‐configuration of a TBS already installed in the field, you can rely on your net‐
work’s connection.
2. Open the Configurator.
3. From the Main tab, click the Line pull‐down menu and select the line on which the
TBS is defined (see Figure 3‐2).
4. From the Download Software pull‐down menu, select the appropriate
configuration option (see page 3‐4 for a description of these options).
5. Click Configure Unit. The following window will appear:
FinM Deployment Guide
For Regualtor Approval Only
Release 4.2.46
3‐25
Configuring Transportation Base Stations (TBSs)
Configuring the Radio Network
Figure 3‐15: TBS ‐ First time Installation
The background color of the device configuration window is the same color as
that defined in Line tab, Name column.
6. Type: Select the radio type ‐ choose Access Radio, as shown in Figure 3‐15.
7. Base Name: Select the name of the TBS from a drop‐down menu list. The list of
these names are taken from those defined in the Towers tab, and come from the
selected line only. Its IP address will then appear next to the First Installation
window if there is no checkmark next to it.
8. Role: Leave this setting as Primary.
9. First Installation: For a first‐time installation, leave this option selected so the
default IP address will appear. Any actions taken will then affect this unit, not the
unit selected from the Base Name drop‐down menu list.
10. Click OK. The Configurator will take all parameters as shown in the Configurator that
are relevant for the selected TBS and carry out the action as determined by the
Download Software option you have selected (see Download software: on page 3‐
4).
It may take about a minute to complete. You will receive one of the completion mes‐
sages described in Configurator Messages below.
To re‐configure a unit that is already installed:
1. Repeat Steps see 1. through see 8. above, relying on your network’s connection to
the unit.
2. Remove the checkmark from First Installation, and enter the IP address of the unit
you wish to re‐configure:
FinM Deployment Guide
For Regualtor Approval Only
Release 4.2.46
3‐26
Configuring Transportation Mobile Units (TMUs)
Configuring the Radio Network
Figure 3‐16: TBS ‐ Re‐configuration
3. Click OK. The Configurator will take all parameters as shown in the Configurator that
are relevant for a TBS and carry out the action as determined by the Download
software option you have selected (see Download software: on page 3‐4). If the
action includes downloading to a unit, it will download to the unit whose IP address
appears in the First Installation window, regardless of which unit appears in the
Base Name window.
It may take about a minute to complete. You will receive one of the completion mes‐
sages described in Configurator Messages below.
3.6.2 Configuring Transportation Mobile Units (TMUs)
Use this procedure to carry out changes in the configuration parameters of the TMUs. This
includes changing or setting its IP address.
Since TMUs are usually mobile, make sure these devices will be in continuous
contact during the configuration process. Our recommended “best practice” is to
find an opportunity when the TMU to be configured is immobile.
1. For a first‐time configuration, connect the TMU’s PoE socket to a PoE device (see
Site Installation for connection instructions), and in turn, connect the PoE device to
your laptop or a LAN connection.
For a re‐configuration of a TMU already installed in the field, you can rely on your
network’s connection.
2. Open the Configurator.
3. From the Main tab, click the Line pull‐down menu and select the line on which the
TMU is defined (see Figure 3‐2).
4. From the Download Software pull‐down menu, select the appropriate
configuration option (see page 3‐4 for a description of these options).
FinM Deployment Guide
For Regualtor Approval Only
Release 4.2.46
3‐27
Configuring Transportation Mobile Units (TMUs)
Configuring the Radio Network
5. Click Configure Unit. The following window will appear:
Figure 3‐17: TMU ‐ First time Installation
The background color of the device configuration window is the same color as
that defined in Line tab, Name column.
6. Type: Select the radio type ‐ Train Radio, as shown in Figure 3‐17.
7. Car: Select the name of the train car on which the unit is to be installed. A list of
these names are taken from those defined in the Trains tab, Car column, and come
from the selected line only. Its IP address will then appear next to the First
Installation window if there is no checkmark next to it.
8. Car Router: This shows the IP address of the router on the selected train car. this IP
address is defined in the Trains tab, Car Router IP column.
9. First Installation: For a first‐time installation, leave this option selected so the
default IP address will appear. Any actions taken will then affect this unit directly,
not the unit selected from the Car drop‐down menu list, nor will it use the Car
Router.
10. Click OK. The Configurator will take all parameters as shown in the Configurator that
are relevant for the selected TMU and carry out the action as determined by the
Download Software option you have selected (see Download software: on page 3‐
4).
It may take about a minute to complete. You will receive one of the completion mes‐
sages described in Configurator Messages below.
To re‐configure a unit that is already installed in the field:
1. Repeat Steps see 1. through see 8. above, relying on your network’s connection to
the unit.
FinM Deployment Guide
For Regualtor Approval Only
Release 4.2.46
3‐28
Configuring Indoor Synchronization Units (ISUs)
Configuring the Radio Network
2. Remove the checkmark from First Installation, and enter the IP address of the unit
you wish to re‐configure. Note that the correct IP address of the Car Router will
appear.
Figure 3‐18: TMU ‐ Re‐configuration
3. Click OK. The Configurator will take all parameters as shown in the Configurator that
are relevant for a TMU and carry out the action as determined by the Download
software option you have selected (see Download software: on page 3‐4). If the
action includes downloading to a unit, it will download, via the Car Router whose IP
address is shown, to the unit whose IP address appears in the First Installation
window, regardless of which unit appears in the Car window.
It may take about a minute to complete. You will receive one of the completion mes‐
sages described in Configurator Messages below.
3.6.3 Configuring Indoor Synchronization Units (ISUs)
Use this procedure to carry out changes in the configuration parameters of the ISUs. This
includes changing or setting its IP address.
1. For a first‐time configuration, connect the ISU’s sync socket to your laptop or to a
LAN connection. Connect AC power to its power input. See Site Installation for con‐
nection instructions.
For a re‐configuration of an ISU already installed in the field, you can rely on your
network’s connection.
2. Open the Configurator.
3. From the Main tab, click the Line pull‐down menu and select the line on which the
ISU is defined (see Figure 3‐2).
4. From the Download Software pull‐down menu, select the appropriate
configuration option (see page 3‐4 for a description of these options).
5. Click Configure Unit. The following window will appear:
FinM Deployment Guide
For Regualtor Approval Only
Release 4.2.46
3‐29
Configuring Indoor Synchronization Units (ISUs)
Configuring the Radio Network
Figure 3‐19: ISU ‐ First time installation
The background color of the device configuration window is the same color as
that defined in Line tab, Name column.
6. Type: Select the unit type ‐ Line sync Unit (ISU), as shown in Figure 3‐19.
7. Unit Name: Select the name of the ISU associated with this line. This name consists
of ISU.LineNumber. The name is taken from those defined in the Line tab. Its IP
address will then appear next to the First Installation window if there is no
checkmark next to it.
8. Role: Select the role of the ISU. This is either Primary or Secondary. See the Line
tab: ISU IP, and Backup ISU IP for definitions of their IP addresses.
9. First Installation: For a first‐time installation, leave this option selected so the
default IP address will appear. Any actions taken will then affect this unit, not the
unit shown in the Unit Name window.
10. Click OK. The Configurator will take all parameters as shown in the Configurator that
are relevant for the ISU shown and carry out the action as determined by the
Download Software option you have selected (see Download software: on page 3‐
4).
It may take about a minute to complete. You will receive one of the completion mes‐
sages described in Configurator Messages below.
To re‐configure a unit that is already installed in the field:
1. Repeat Steps see 1. through see 8. above, relying on your network’s connection to
the unit.
2. Remove the checkmark from First Installation, and enter the IP address of the unit
you wish to re‐configure.
FinM Deployment Guide
For Regualtor Approval Only
Release 4.2.46
3‐30
Configurator Messages
Configuring the Radio Network
Figure 3‐20: ISU ‐ Re‐configuration
3. Click OK. The Configurator will take all parameters as shown in the Configurator that
are relevant for an ISU and carry out the action as determined by the Download
software option you have selected (see Download software: on page 3‐4). If the
action includes downloading to a unit, it will download to the unit whose IP address
appears in the First Installation window, regardless of which unit appears in the
Unit Name window.
It may take about a minute to complete. You will receive one of the completion mes‐
sages described in Configurator Messages below.
3.7 Configurator Messages
Table 3‐5: Configurator Message Color Codes
Color
Code
Meaning
Action Required
Red
Operation failed
Varies with message
Yellow
OK
Repeat the operation
Green
OK
Operation successful
FinM Deployment Guide
For Regualtor Approval Only
Release 4.2.46
3‐31
Configurator Messages
Configuring the Radio Network
Table 3‐6: Configurator Messages
Color
Code
Message
Action Required
Can't find Configuration
Can't log into device. Check password
Contact supplier
Failed to get device configuration
No connection with Device
Permission Error
Ping, then check physical
connection. If all fails, replace the
device.
Contact supplier
Script Error
Telnet Connection to the device failed
Ping, then check physical
connection. If all fails, replace the
device.
Wrong Product Connected
Check for mix‐up ‐ TMU for TBS or
vice versa
Please run again to complete.
Repeat this configuration ‐ this
may occur during a software
upgrade.
Configuration completed ‐ Device restarting...
None
Configuration completed ‐ Please restart device.
Log in with Telnet and use the
reboot command (See below)
If you are asked to restart the device, log in to it with telnet following this example:
Figure 3‐21: Logging in to an TBS with Telnet
The user name and password are respectively, admin and netman.
FinM Deployment Guide
For Regualtor Approval Only
Release 4.2.46
3‐32
Configurator Messages
Configuring the Radio Network
Figure 3‐22: Using the Telnet reboot command to reset an TBS
Here is an example:
Table 3‐7: Radio Inventory
ABC Metro Radio Inventory
Radio Type
Active
Backup
Total
Base Radios
158
158
Train Radios
298
298
Sync Unit (ISU)
Table 3‐8: Distribution of Radio Inventory across lines
Line
Name
Base
Train
Line01
64
126
Line02
20
11
Line03
38
68
Line04
48
84
158
298
Total
FinM Deployment Guide
For Regualtor Approval Only
Release 4.2.46
3‐33
Appendix A: Antenna
Guidelines
A.1 For Deployment in US/Canada
The TBS and TMU devices bear the following identifications on their label:
Contains FCC ID: Q3K‐5XACMD3CN
Contains IC: 5100A‐5XACMD3CN
Only the antennas shown in the table below or antennas of the same type with lower gain are
approved for use in this system. The antennas must be installed so as to provide a minimum
separation distance from bystanders as specified in the table below:
Table A‐1: Approved Antennas and Guidelines
Cat.No.
Type
Gain (dBi) Dir BW
Freq Band
(MHz)
Tx Power
per Chain
(dBm)
Min. Safe
Distance
(cm)
RW‐9105‐5158
Flat DP Slant
19.0
17.0o
5725‐5850
12.0
78.0
RW‐9401‐5002
Shark Fin SP
12.5
50.0o
5725‐5850
18.5
37.0
Transportation FiberinMotion Deployment
Guide
For Regualtor
Approval Only
Release 4.2.46
A‐1
Appendix B: Revision History
Table B‐1: Revision History
Date
Description
June 21, 2015
Rel: 4.1.80
Initial release
Aug 10, 2016
Rel: 4.2.30
Extensive editing, updated for release
May, 2017
Rel: 4.2.45
Extensive editing, updated for release
Nov, 2017
Rel: 4.2.46
Updated for regulatory compliance only
FinM Deployment Guide
For Regualtor Approval Only
Release 4.2.46
B‐1
Regulatory Compliance
General Note
This system has achieved Type Approval in various countries around the world. This means
that the system has been tested against various local technical regulations and found to
comply. The frequency bands in which the system operates may be “unlicensed” and in these
bands, the system can be used provided it does not cause interference.
FCC/ISED ‐ Compliance
This equipment has been tested and found to comply with the limits for a Class B digital
device, pursuant to Part 15 of the FCC Rules. These limits are designed to provide reasonable
protection against harmful interference in a residential installation. This equipment
generates, uses and can radiate radio frequency energy and, if not installed and used in
accordance with the instructions, may cause harmful interference to radio communications.
However, there is no guarantee that interference will not occur in a particular installation. If
this equipment does cause harmful interference to radio or television reception, which can
be determined by turning the equipment off and on, the user is encouraged to try to correct
the interference by one or more of the following measures:
• Reorient or relocate the receiving antenna.
• Increase the separation between the equipment and receiver.
• Connect the equipment into an outlet on a circuit different from that to which the
receiver is connected.
Consult the dealer or an experienced radio/TV technician for help.
Changes or modifications to this equipment not expressly approved by the party responsible
for compliance could void the user's authority to operate the equipment.
It is the responsibility of the installer to ensure that when using the
outdoor antenna kits in the United States (or where FCC rules apply), only
those antennas certified with the product are used. The use of any
antenna other than those certified with the product is expressly forbidden
by FCC rules 47 CFR part 15.204.
Il est de la responsabilité de l'installateur de s'assurer que lors de
l'utilisation du kits d'antennes extérieures au Canada (ou lorsque les règles
de l'ISDE s'appliquent), seulement les antennes certifiées avec le produit
sont utilisées. L'utilisation de tout l'antenne autre que celles certifiées
avec le produit est expressément interdite RSS par les règlements ISDE.
FinM Deployment Guide
For Regualtor Approval Only
Release 4.2.46
C‐1
RF Exposure: It is recommended to keep a safe distance of 78 cm from the
radiating antenna when operating in the US and 79 cm when operating in
Canada.
Exposition RF: Il est recommandé de garder une distance de sécurité de 78
cm de l'antenne rayonnante lorsqu'elle fonctionne aux États‐Unis et de 79
cm lorsqu'elle fonctionne au Canada.
It is the responsibility of the installer to ensure that when configuring the
radio in the United States (or where FCC rules apply), the Tx power is set
according to the values for which the product is certified. The use of Tx
power values other than those, for which the product is certified, is
expressly forbidden by FCC rules 47 CFR part 15.204.
Il est de la responsabilité de l'installateur de s'assurer que lors de la
configuration du radio au Canada (ou là où les règles ISDE s'appliquent), la
puissance Tx est réglée selon les valeurs pour lesquelles le produit est
certifié. L'utilisation de Tx valeurs de puissance autres que celles pour
lesquelles le produit est certifié expressément interdit par les règlements
RSS de l'ISDE.
Outdoor units and antennas should be installed ONLY by experienced
installation professionals who are familiar with local building and safety
codes and, wherever applicable, are licensed by the appropriate
government regulatory authorities. Failure to do so may void the product
warranty and may expose the end user or the service provider to legal and
financial liabilities. Resellers or distributors of this equipment are not
liable for injury, damage or violation of regulations associated with the
installation of outdoor units or antennas. The installer should configure
the output power level of antennas according to country regulations and
antenna type.
Les unités extérieures et les antennes doivent être installées
UNIQUEMENT par des les professionnels de l'installation qui connaissent
le bâtiment et la sécurité locaux codes et, le cas échéant, sont autorisés
par les autorités compétentes autorités de réglementation
gouvernementales. Ne pas le faire peut annuler le produit garantie et peut
exposer l'utilisateur final ou le fournisseur de services à des passifs
financiers. Les revendeurs ou distributeurs de cet équipement ne sont pas
responsable des blessures, des dommages ou de la violation de la
réglementation installation d'unités extérieures ou d'antennes.
L'installateur doit configurer le niveau de puissance de sortie des antennes
selon les réglementations du pays et type d'antenne.
FinM Deployment Guide
For Regualtor Approval Only
Release 4.2.46
C‐2
•
•
•
•
Where Outdoor units are configurable by software to Tx power val‐
ues other than those for which the product is certified, it is the
responsibility of the Professional Installer to restrict the Tx power to
the certified limits.
This product was tested with special accessories ‐ indoor unit (IDU or
PoE), FTP CAT‐5e shielded cable with sealing gasket, 10 AWG ground‐
ing cable ‐ which must be used with the unit to insure compliance.
o Où les unités extérieures sont configurables par logiciel aux valeurs
de puissance Tx autres que ceux pour lesquels le produit est certifié,
c'est le la responsabilité de l'installateur professionnel de restreindre
la puissance Tx à les limites certifiées.
Ce produit a été testé avec des accessoires spéciaux ‐ unité intérieure
(UDI ou PoE), câble blindé FTP CAT‐5e avec joint d'étanchéité, mise à
la terre 10 AWG câble ‐ qui doit être utilisé avec l'unité pour assurer
la conformité.
Units are intended for installation in a Restricted Access Location.
Only UL Listed parts and components may be used for installation. Use UL Listed devices
having an environmental rating equal to or better than the enclosure rating to close all
unfilled openings.
Use min. 10AWG external protective earthing conductor.
Indoor Units comply with part 15 of the FCC rules. Operation is subject to the following two
conditions:
(1) These devices may not cause harmful interference.
(2) These devices must accept any interference received, including interference that may
cause undesired operation.
Canadian Emission Requirements for Indoor Units
This Class B digital apparatus complies with Canadian ICES‐003.
Cet appareil numẻrique de la classe B est conforme ả la norme NMB‐003 du Canada.
China MII
Operation of the equipment is only allowed under China MII 5.8GHz band regulation
configuration with EIRP limited to 33 dBm (2 Watt).
FinM Deployment Guide
For Regualtor Approval Only
Release 4.2.46
C‐3
India WPC
Operation of the equipment is only allowed under India WPC GSR‐38 for 5.8GHz band
regulation configuration.
For Norway and Sweden only
Equipment connected to the protective earthing of the building installation through the
mains connection or through other equipment with a connection to protective earthing ‐ and
to a cable distribution system using coaxial cable, may in some circumstances create a fire
hazard. Connection to a cable distribution system has therefore to be provided through a
device providing electrical isolation below a certain frequency range (galvanic isolator, see EN
60728‐11).
Norway
Utstyr som er koplet til beskyttelsesjord via nettplugg og/eller via annet jordtilkoplet utstyr ‐
og er tilkoplet et kabel‐TV nett, kan forårsake brannfare. For å unngå dette skal det ved
tilkopling av utstyret til kabel‐TV nettet installeres en galvanisk isolator mellom utstyret og
kabel‐ TV nettet.
Sweden
Utrustning som är kopplad till skyddsjord via jordat vägguttag och/eller via annan utrustning
och samtidigt är kopplad till kabel‐TV nät kan i vissa fall medföra risk för brand. För att
undvika detta skall vid anslutning av utrustningen till kabel‐TV ät galvanisk isolator finnas
mellan utrustningen och kabel‐TV nätet.
Unregulated
In countries where the radio is not regulated the equipment can be operated in any
regulation configuration, best results will be obtained using Universal regulation
configuration.
Safety Practices
Applicable requirements of National Electrical Code (NEC), NFPA 70; and the National
Electrical Safety Code, ANSI/IEEE C2, must be considered during installation.
NOTES:
1. A Primary Protector is not required to protect the exposed wiring as long as the exposed
wiring length is limited to less than or equal to 140 feet, and instructions are provided to
avoid exposure of wiring to accidental contact with lightning and power conductors in
accordance with NEC Sections 725‐54 (c) and 800‐30.
In all other cases, an appropriate Listed Primary Protector must be provided. Refer to Articles
800 and 810 of the NEC for details.
2. For protection of ODU against direct lightning strikes, appropriate requirements of NFPA
780 should be considered in addition to NEC.
FinM Deployment Guide
For Regualtor Approval Only
Release 4.2.46
C‐4
3. For Canada, appropriate requirements of the CEC 22.1 including Section 60 and additional
requirements of CAN/CSA‐B72 must be considered as applicable.
4. Only UL Listed parts and components will be used for installation. Use UL Listed devices
having an environmental rating equal to or better than the enclosure rating to close all
unfilled openings.
5. Use min. 10AWG external protective earthing conductor.
FinM Deployment Guide
For Regualtor Approval Only
Release 4.2.46
C‐5
Transportation FiberinMotion
Deployment Guide
Notice
This handbook contains information that is proprietary to RADWIN Ltd (RADWIN hereafter).
No part of this publication may be reproduced in any form whatsoever without prior written
approval by RADWIN.
Right, title and interest, all information, copyrights, patents, know‐how, trade secrets and
other intellectual property or other proprietary rights relating to this handbook and to the
RADWIN products and any software components contained therein are proprietary products
of RADWIN protected under international copyright law and shall be and remain solely with
RADWIN.
The RADWIN name is a registered trademark of RADWIN. No right, license, or interest to such
trademark is granted hereunder, and you agree that no such right, license, or interest shall be
asserted by you with respect to such trademark.
You shall not copy, reverse compile or reverse assemble all or any portion of the Deployment
Guide or any other RADWIN documentation or products. You are prohibited from, and shall
not, directly or indirectly, develop, market, distribute, license, or sell any product that
supports substantially similar functionality based or derived in any way from RADWIN
products.Your undertaking in this paragraph shall survive the termination of this Agreement.
This Agreement is effective upon your opening of a RADWIN product package and shall
continue until terminated. RADWIN may terminate this Agreement upon the breach by you of
any term thereof. Upon such termination by RADWIN, you agree to return to RADWIN any
RADWIN products and documentation and all copies and portions thereof.
For further information contact RADWIN at one of the addresses under Worldwide Contacts
below or contact your local distributor.
Disclaimer
The parameters quoted in this document must be specifically confirmed in writing before
they become applicable to any particular order or contract. RADWIN reserves the right to
make alterations or amendments to the detail specification at its discretion. The publication
of information in this document does not imply freedom from patent or other rights of
RADWIN, or others.
Trademarks
WinLink 1000, RADWIN 2000, RADWIN 5000, RADWIN 6000, RADWIN 600 and
FiberinMotion are trademarks of RADWIN Ltd.
Windows 2000, XP Pro, Vista, Windows 7 and Internet Explorer are trademarks of
Microsoft Inc.
Mozilla and Firefox are trademarks of the Mozilla Foundation.
FinM Deployment Guide
For Regualtor Approval Only
Release 4.2.46
D‐1
Other product names are trademarks of their respective manufacturers.
FinM Deployment Guide
For Regualtor Approval Only
Release 4.2.46
D‐2
FinM Deployment Guide
For Regualtor Approval Only
Release 4.2.46
E‐1

---

Source Exif Data:

File Type                       : PDF
File Type Extension             : pdf
MIME Type                       : application/pdf
PDF Version                     : 1.6
Linearized                      : No
Author                          : shmuel_g
Create Date                     : 2017:12:25 11:20:10Z
Modify Date                     : 2017:12:25 11:36:07+02:00
Has XFA                         : No
Language                        : en
XMP Toolkit                     : Adobe XMP Core 5.2-c001 63.139439, 2010/09/27-13:37:26
Format                          : application/pdf
Creator                         : shmuel_g
Title                           : UM_Transportation_4_2_46_Regulatory.book
Creator Tool                    : FrameMaker 10.0.2
Metadata Date                   : 2017:12:25 11:36:07+02:00
Producer                        : Acrobat Distiller 10.1.16 (Windows)
Document ID                     : uuid:e43a1070-4690-44b3-8a36-4567036a4445
Instance ID                     : uuid:996ce021-661e-4051-b85c-9fb0a48be766
Page Mode                       : UseOutlines
Page Count                      : 112

EXIF Metadata provided by EXIF.tools