RSU-352系列 快速入門指南
Objective
The purpose of this document is to provide necessary information to help setup and installation of RSU-352 series products. To provide for safe installation and operation of the equipment, read the safety guidelines at the beginning of this manual and follow the procedures outlined in the following chapters before connecting power to RSU-352. Keep this operating manual handy and distribute to all users, technicians and maintenance personnel for reference.
Reference
- Unex RSU-352 datasheet
- 61-00021-00_RSU-352_0A1_Drawing
- 80-00032_EX-40_Drawing_B
- Application Note RSU-352 Service Port Connection (Unex-APN-24-001)
Limited Warranty Policy
Unex Technology Corporation selling the product warrants that commencing from the date of shipment to customer and continuing for a period of twelve (12) months. This limited warranty extends only to the original customer of the product. Customer’s sole and exclusive remedy and the entire liability of Unex under this limited warranty will be, at Unex’s option, return for repair to Unex’s repair center with freight and insurance prepaid or shipment of a replacement within the warranty period or a refund of the purchase price if the hardware is returned to Unex. Unex’s obligations hereunder are conditioned upon the return of affected hardware in accordance with Unex’s service center’s then-current Return Material Authorization (RMA) procedures.
This warranty does not cover:
- Products found to be defective after the warranty period has expired.
- Products subjected to misuse or abuse, whether by accident or other causes. Such product conditions will be determined by Unex at its sole and unfettered discretion.
- Products damaged due to a natural disaster, including but not limited to lightning, flooding, earthquake, or fire.
- Software products.
- Products dismantled or opened by unauthorized persons. Please contact a representative of Unex if you need advanced technical support.
- Products with an altered and/or damaged serial number.
- Loss of data or software.
- Products that have been updated, reworked, or improperly tested by the Customer, or by a third party at the request of the Customer.
- Customized and original design manufacturer (ODM) products. The warranty terms for customized and ODM products should be defined in the contract that governs the project.
Safety Guidelines
- Keep working area clean and dry while assembling/installing
- When operating under extreme temperature conditions, environmental control measures (e.g., heating, cooling) should be considered.
- Always make sure the metal enclosure is connected to a well-grounded metal structure.
- Make sure every screw has been fastened, including the mounting bracket, pole clamps and earth wire.
- Make sure every accessory has been fastened, including the V2X antennas, GNSS antenna, PoE surge protector and cable gland.
- Follow the Attention instructions.
Attention Follow the operation instructions to make sure the product functioning properly and to avoid product damages during handling / installation / operation.
- Follow the Caution instructions.
Caution Follow the safety instructions to keep users / operators from health hazards.
Product Appearance
An RSU-352 series package contains the following items:
- RSU-352 x1
- V2X antenna x2
- GNSS antenna x1
- PoE surge protector x1
- Cable gland x1
- Mounting bracket set x1
- Earth wire (1 Meter) x1
The photos shown in this document may seem different from actual product. However, the differences do not affect actual functionalities.
Attention Some oily black residue may be found around screw heads. This black substance is an anti-seize compound, not dirt or contamination. This anti-seize compound is intentionally applied to improve corrosion resistance of our product. Any smudge caused by the anti-seize compound affects only cosmetics and is not considered as a defect.
Functional Block Diagram
Electrical Characteristics
Absolute Maximum Ratings
Over operating free-air temperature range (unless otherwise noted).
| Parameters | Conditions | Min. | Max. | Unit |
|---|---|---|---|---|
| Storage Temperature | – | -40 | 70 | °C |
| Supply Voltage | PoE *1 | – | 60 | V |
| V2X maximum input level | – | – | 10 | dBm |
| GNSS maximum input level | – | – | -10 | dBm |
|
Note:
Note:
|
||||
Recommended Operating Conditions
Over operating free-air temperature range (unless otherwise noted).
| Parameters | Conditions | Min. | Typ. | Max. | Unit |
|---|---|---|---|---|---|
| Ta (Ambient operating temperature) | Free-air temp. | -40 | 25 | 85 *1 | °C |
| Supply voltage | PoE *2 | 36 | 48 | 57 | V |
| V2X antenna gain | 5850-5925MHz | – | – | 7.6 | dBi |
| C-V2X sensitivity *3 | RB allocation=96 PER ≤ 10% |
– | – | -86.1 | dBm |
| C-V2X maximum output power *4 | Target Power=23dBm, RB allocation=96 Power Class3 |
19.7 | 23 | 26.3 | dBm |
| C-V2x minimum output power *5 | Target Power=-30dBm, RB allocation=96 |
– | – | -28.5 | dBm |
| C-V2X output power tolerance *6 | Test Point1 Power=-18dBm |
-5 | – | 5 | dB |
| Test Point2 Power=15dBm |
-5 | – | 5 | dB | |
| C-V2X adjacent channel leakage power ratio *7 | Target Power=23dBm, RB allocation=18, Start RB #: 82, EUTRA1 |
29.2 | – | – | dB |
| Target Power=23dBm, RB allocation=18, Start RB #: 0, EUTRA1 |
29.2 | – | – | dB | |
| Target Power=23dBm, RB allocation=96, Start RB #: 0, EUTRA1 |
29.2 | – | – | dB | |
| Carrier frequency accuracy | DSRC mode | -20 | – | 20 | ppm |
| DSRC sensitivity *8 | PER ≤ 10% | -92 | – | – | dBm |
| PER ≤ 10%, -40 – +85 °C |
-82 | – | – | dBm | |
| DSRC maximum input level | PER ≤ 10% | – | – | -30 | dBm |
| DSRC adjacent channel rejection | – | 13 | – | – | dB |
| DSRC non-adjacent channel rejection | – | 29 | – | – | dB |
| V2X output power | Spectrum mask Class C |
– | – | 20 | dBm |
| V2X duty cycle *9 | Transmission | – | – | 20 | % |
| GNSS antenna gain | Antenna Gain | – | – | 2.4 *10 2.85*11 |
dBic |
| LNA Gain *12 | 24 | 27 | 30 | dB | |
| GNSS sensitivity | Acquisition | – | -146 | – | dBm |
| Navigation | – | -157 | – | dBm | |
| Tracking | – | -159 | – | dBm | |
| GNSS antenna bias IANT | ≤ 20mA | 3.0 | – | 3.3 | V |
| GNSS antenna detection current *13 | IANT | 12 | – | 58 | mA |
|
Note:
|
|||||
Power Consumption
RSU-352 is an 802.3af PD (powered device) and should be powered with an 802.3af/802.3at PoE PSE (power sourcing equipment).
| Condition | Power Consumption | ||||
|---|---|---|---|---|---|
| Temp. | Power Source | Voltage (V) | Low *1 | Typical *2 | High *3 |
| 25°C | 802.3af PoE PSE | 54.3 | 0.06A (3.26W) |
0.06A (3.26W) |
0.11A (5.97W) |
| 85°C | 802.3af PoE PSE | 54.3 | 0.07A (3.80W) |
0.07A (3.80W) |
0.12A (6.52W) |
|
Note:
|
|||||
I/O Interfaces
Status LED
| LED | Status | Description |
|---|---|---|
| Status LED | Blinking Green | Start-up |
| Solid Green | Operational | |
| Amber | FW upgrade | |
| Red | Fault | |
|
Note: Please see TABLE 11: UNEX BSP INTERFACE SETTINGS for Status LED BSP settings. The definition of each status and its related behavior should be implemented by the user. |
||
PoE (Power-Over-Ethernet)
RSU-352 has one Gigabit Ethernet port which supports 10/100/1000Mbps connection. It is suggested to use an Ethernet cable compatible with Cat5e or above standard for best connection speed.
This Ethernet port also acts as a 12W PoE (802.3af) PD (powered device). It supports both mode A and mode B PSE (power sourcing equipment). Passive PoE is not supported.
5.9GHz V2X
RSU-352 provides two 5.9GHz V2X antenna connectors. Receptacle connectors are Type-N. These V2X ports are surge protected (5KA min with 8/20 μs, 10KV min with 1.2/50 μs). A pair of Type-N V2X antennas (EX-53, 7.6dBi omni-directional) are also provided in RSU-352 package. Fastening with correct torque is essential for keeping antenna performance. It is critical to follow the recommended torque listed in TABLE 5. ANTENNA FASTENING REQUIREMENT during installation.
| Antenna | Fastening to | Recommended torque to ensure declared IP rating (Nm) |
|---|---|---|
| V2X0, V2X1 | V2X port, type-N | 1.1 – 1.3 |
| GNSS | GNSS port, type-N | 1.1 – 1.3 |
The V2X antenna ports has a built-in antenna detection function. This detection mechanism only works with the stock EX-53 antennas provided.
| Antenna Status | Value | Command |
|---|---|---|
| OPEN | 616-1023 |
V2X0: cat /sys/bus/iio/devices/iio\:device0/in_voltage4_raw V2X1: cat /sys/bus/iio/devices/iio\:device0/in_voltage5_raw |
| NORMAL | 410-615 | |
| SHORT | 0-409 |
GNSS
RSU-352 provides one GNSS antenna connector. This GNSS antenna port is Type-N. This GNSS port is surge protected (5KA min with 8/20 μs, 10KV min with 1.2/50 μs). An active GNSS antenna (EX-33) is also provided in RSU-352 package.
For stable fix acquisition, at least 4 satellites with enough signal strength (C/N0 value above 30 dB-Hz) are required. If the signal strength goes below 30 dB-Hz, the fix will become unstable.
GNSS Antenna Detection
The antenna detection mechanism is a 2-step process: First check the signal strength. If the signal strength drops to zero, then check the antenna status flag.
When all the C/N0 values becomes null, it means that the GNSS antenna or its cable may either become detached or damaged. The GNSS antenna port has a built-in antenna detection function. The detection mechanism is based on the current consumption of an active antenna (IANT). If the active antenna consumes less current than 12 mA, then it is considered as the OPEN status; if the antenna consumes more than 58 mA, then it is considered as the SHORT status. Anything between 12-58 mA is considered as the NORMAL status.
The GNSS 3.3V antenna bias will be continuously supplied in OPEN/NORMAL status. Once the SHORT status is triggered, the SHORT flag will persist, and the 3.3V bias will be turned off until the reset of the GNSS module. After the reset of the GNSS module, the detection process will start all over again.
It is possible for a good active antenna to be reported OPEN because it consumes less current than 12 mA (e.g., the bundled EX-33 antenna consumes only 8 mA), or a good passive antenna to be considered SHORT because it is DC shorted (e.g., a slot antenna). However, as long as there are more than 4 satellites with enough signal strength (C/N0 value above 30 dB-Hz), the GNSS is in good state.
The antenna status flag is reported in a proprietary NMEA message:
$PSTMANTENNASTATUS,<status>*<checksum><cr><lf>
where <status> can be:
- 0 – The antenna current is in the normal range (NORMAL)
- 1 – The antenna current is below the normal range (OPEN)
- 2 – The antenna current is above the normal range (SHORT)
| Antenna Status | Current Consumption (mA) | 3.3V bias | NMEA Sentence |
|---|---|---|---|
| OPEN | < 12 | ON | $PSTMANTENNASTATUS,1*4C |
| NORMAL | between 12- 58 | ON | $PSTMANTENNASTATUS,0*4D |
| SHORT | > 58 | Turned OFF once triggered | $PSTMANTENNASTATUS,2*4F |
Service Port
Latest RSU-352 model comes with a service port, which provides direct access to USB0 interface and the capability of DFU FW update. The identification and connection of the service port is described in UNEX-APN-24-001.
Accessories
GORE® Vent
A GORE® Vent is pre-installed to continuously equalize the pressure inside the RSU enclosure with the atmosphere, while the PTFE membrane prevents the water and dust ingress at the same time. This vent manages common outdoor weather conditions such as precipitation or condensation, and as a result, it increases the service life of the RSU.
Surge Protector
RSU-352 is powered by PoE. The PoE surge protector should be installed on the PoE port before connecting Ethernet cable. Please follow the instruction below for installation:
- Extend the short RJ45 cable on the surge protector.
- Plug the short RJ45 cable into the PoE port on RSU-352.
- Screw the surge protector over the PoE port until fastened. (See TABLE 8. SURGE PROTECTOR AND CABLE GLAND FASTENING REQUIREMENT for torque)
- Make sure the O-ring on the surge protector sits nicely in the O-ring groove on the PoE port.
| Attention | Always check the O-ring before finishing installation. If the O-ring protrudes or bulges from the O-ring groove, or the fastening torque does not match the specified value, then the declared IP level cannot be achieved. It would leave the RSU-352 highly vulnerable to water/dust ingression, and permanent damage may occur under these conditions. |
|---|
Cable Gland
To ensure weather resistance, always connect the Ethernet cable with the cable gland on the cable outlet. Please follow the instruction below for installation:
- Cable outer diameter: 4.5-6.5mm.
- Insert RJ45 cable through sealing nut, clip, body, and O-ring in a row. (See FIGURE 10: CABLE GLAND DRAWING for parts direction)
- Securely connect the RJ45 connector with the RJ45 port.
- Fasten the body to the RJ45 port, with O-ring side facing the surge protector metal housing. (See TABLE 8. SURGE PROTECTOR AND CABLE GLAND FASTENING REQUIREMENT)
Attention Always check cable gland body before finishing installation.
If the O-ring protrudes or bulges from the O-ring groove, or the fastening torque does not match the specified value, then the declared IP level cannot be achieved. It would leave the RSU-352 highly vulnerable to water/dust ingression, and permanent damage may occur under these conditions.
- Sit the seals firmly into the body.
- Push the clip and seals all the way down to the body.
- Fasten sealing nut with the body. (See TABLE 8. SURGE PROTECTOR AND CABLE GLAND FASTENING REQUIREMENT)
Attention Always check cable gland body before finishing installation.
If the O-ring protrudes or bulges from the O-ring groove, or the fastening torque does not match the specified value, then the declared IP level cannot be achieved. It would leave the RSU-352 highly vulnerable to water/dust ingression, and permanent damage may occur under these conditions.
Cable gland drawings
| Fastening part | Fastening to | Recommended torque to ensure declared IP rating (Nm) |
|---|---|---|
| Surge protector | RSU-352 PoE port | 2.2 – 2.5 |
| Cable gland, body | Surge protector | 1.5 – 1.7 |
| Cable gland, sealing nut | Cable gland, body | 1.0 – 1.2 |
Mounting Bracket
For best RF signal coverage, it is best to install RSU-352 on a horizontal mast/gantry and to keep it away from any large metal object nearby (FIGURE 13). However, RSU-352 can also be installed on a vertical post or on a wall if needed (FIGURE 14). The length of the earth wire is 1 meter long.
The diameter of the mast/post should be between 78-101mm. The total weight of RSU-352 (including antennas, PoE surge protector, mounting bracket, earth wire and cable gland) is about 2.7 kg. Before installation, always make sure the structural strength of the mast/post/wall can hold the extra weight of RSU-352.
Fastening with correct torque is essential to avoid electrical damage and personal injury. It is critical to follow the recommended torque listed in TABLE 9. MOUNTING BRACKET FASTENING REQUIREMENT during installation.
Aluminum corrosion deposits may start to build on the mounting hole threads over time if an RSU-352 is installed by the seashore or in an environment where salt mist could become a problem. As a general rule of thumb, it is highly recommended to always apply a generous amount of waterproof/anti-seize lubricant (e.g., LOCTITE LB 8150) over the threads of the mounting screws and the earth wire screw before installing.
| Screw | Fastening to | Recommended torque to ensure declared IP rating (Nm) |
|---|---|---|
| M5x10, PH2 | Mounting bracket | 1.8 – 2.0 |
| M4x8, PH1 | Earth wire | 1.0 – 1.2 |
| Caution |
An RSU would be vulnerable to electric overstress if not installed properly. To avoid electric overstress related hardware failures, please make sure to follow the instructions below before installation:
|
|---|
Dimensions and Weight
| Model | Length (mm) *1 | Width (mm) *1 | Height (mm) *1 | Weight (kg) *2 |
|---|---|---|---|---|
| RSU-352 | 220.5±1 | 127.5±1 | 72.3±1 | 2.7±0.1 |
|
Note:
|
||||
Software Settings
The following BSP settings are applicable for Unex software package only.
| Function | Description |
|---|---|
| Ethernet | Default IP address 192.168.100.3 |
| Service port (USB0) | Default USB 2.0 device mode. RNDIS device IP = 192.168.1.3, RNDIS host IP = 192.168.1.1 |
| GNSS NMEA | UART1, 230400bps, 8N1, ttyAMA1 |
| GNSS Reset | GPIO111, 0->1 = GNSS module reset (cold start, clear SRAM and RTC) |
| mPCIe Reset | GPIO 511, 0->1 = mPCIe module reset |
| TAMPER# | GPIO149 |
| STATUS LED Green | /sys/class/leds/status-green/brightness, 0=OFF, 1-255=ON |
| STATUS LED Red | /sys/class/leds/status-red/brightness, 0=OFF, 1-255=ON |
| V2X0 antenna detection | /sys/bus/iio/devices/iio\:device0/in_voltage4_raw |
| V2X1 antenna detection | /sys/bus/iio/devices/iio\:device0/in_voltage5_raw |
| MAC address | grep V2X_0 /etc/unex/device/device_info.txt |
| BSP/protocol version | /etc/unex/update.log |
Troubleshooting
No Response After Applying Power
This phenomenon may come from multiple causes. Please follow the steps below to check each one of them:
- Check if the PoE power have been properly supplied by the PoE PSE.
- Check if the STATUS LED turned solid GREEN.
- Check if the IP address 192.168.100.3 respond to ping from on your host system 30 seconds after PoE power applied.
- Check firewall settings if no response.
- Check for IP conflictions in local network.
- Make sure your host system Ethernet port is in the same Class C IP address 192.168.100.x.
No TX/RX Activities during Over-the-Air Testing
- Check the antenna status of both V2X antennas on the TX node and the Rx node.
- If Unex’s V2X antennas EX-53 are used, use the V2X antenna detection commands listed in TABLE 11: UNEX BSP INTERFACE SETTINGS. For OPEN/SHORT value range, please see TABLE 7: GNSS ANTENNA STATUS.
cat /sys/bus/iio/devices/iio\:device0/in_voltage4_raw cat /sys/bus/iio/devices/iio\:device0/in_voltage5_raw - If Unex’s V2X antennas EX-53 are not used, it is the user’s responsibility to check the antenna OPEN/SHORT status.
Attention - Performing transmission under OPEN/SHORT conditions may cause permanent damages to RF components.
- Always check antenna status before any V2X TX activity.
- If Unex’s V2X antennas EX-53 are used, use the V2X antenna detection commands listed in TABLE 11: UNEX BSP INTERFACE SETTINGS. For OPEN/SHORT value range, please see TABLE 7: GNSS ANTENNA STATUS.
- For DSRC systems:
- Send 10 V2X packets with priority 7 in TX node.
diag-cli <<< $'chan freq 0 5860\nv2x send 0 0 0 400 10 10 7 160\nstats\nexit' 2>/dev/null
- Check MAC/PHY statistics in RX node.
diag-cli <<< $'chan freq 0 5860\nstats\nexit' 2>/dev/null
- Send 10 V2X packets with priority 7 in TX node.
- For C-V2X systems:
- Check GNSS antenna and GNSS health status. C-V2X requires GNSS time synchronization and TSF (Timing synchronization function) synchronization with GNSS 1PPS before any transmission.
- Make sure the very same
/usr/bin/cv2x_rrc_config.uperand/usr/bin/cv2x_sw_config.txtare uploaded on both TX and RX nodes. - If the RSU-352 comes with Unex’s C-V2X protocol stack, then use
gnss_healthcommand to check the overall GNSS system healthiness.ACL_TIME_SYNC_SYNCEDmeans the access layer (i.e., the TSF timer) has been successfully synchronized.
- If the RSU-352 comes without Unex’s C-V2X protocol, then use the following commands:
- Check the GNSS antenna status and fix mode. For GNSS antenna status, please see GNSS ANTENNA DETECTION; for GNSS fix mode, please check the 2nd field of GSA sentence:
$GNGSA,A,3,24,15,10,23,12,32,,,,,,,2.6,1.4,2.1*2EFix Mode: 1 = Fix not available; 2 = 2D fix; 3 = 3D fix. - Check 1PPS status.
watch -n 1 grep pps /proc/interrupts
If the
pps1.-1count is increasing, then the 1PPS is working. - Check TSF synchronization status.
diag-cli <<< 'ddm tsf get' 2>/dev/null | grep =
If it shows
TSF lock status = locked, then TSF is synchronized.
- Check the GNSS antenna status and fix mode. For GNSS antenna status, please see GNSS ANTENNA DETECTION; for GNSS fix mode, please check the 2nd field of GSA sentence:
- Make sure the very same
- If the RSU-352 comes with Unex’s C-V2X protocol, stop Unex’s V2X services on both TX and RX nodes before running cgen command.
d=/etc/runit/svdir/;svstop(){ [ -e $d$s ] && sv stop $d$s; }; for s in v2xcastd ssmed ssmd dot3d gnd;do svstop;done - Clear MAC/PHY statistics on the RX node.
cd /usr/bin;cgen freq=5915 run=cyq 2>/dev/null
- Send 10 V2X packets from the TX node.
cd /usr/bin;cgen power=40 freq=5915 num=10 run=wwwcgtwzq 2>/dev/null
- Check MAC/PHY statistics on the RX node.
cd /usr/bin;cgen freq=5915 run=yq 2>/dev/null
- Check GNSS antenna and GNSS health status. C-V2X requires GNSS time synchronization and TSF (Timing synchronization function) synchronization with GNSS 1PPS before any transmission.