TABLE OF CONTENTS
- What is the core system relationship between the AR-300 radar, the APU, and MASS?
- What are the minimum network interface requirements and recommended network topology for the AR-300 and APU?
- What are the specific power supply (PoE) and physical cabling requirements for the AR-300?
- What are the default IP addresses and NTP configuration requirements for the system?
- How do scan rates, MASS display refresh rates, and network bandwidth settings impact target tracking performance?
- How can multiple AR-300 radars be deployed in dense installations to prevent mutual interference?
- What physical mounting distance, orientation, and tilt angle are required for the AR-300 radar?
- What software versions, dependencies, and pre-checks are required when troubleshooting AR-300 performance issues?
What is the core system relationship between the AR-300 radar, the APU, and MASS?
Answer:
The AR-300 radar and the APU function as an interdependent pair rather than a standalone setup. The AR-300 requires the APU to complete signal processing and transfer target data. Consequently, when adding and configuring the radar in MASS, users must enter the IP address of the APU rather than the direct IP address of the AR-300 radar.
What are the minimum network interface requirements and recommended network topology for the AR-300 and APU?
Answer:
Both the AR-Series radar and the APU strictly require an Ethernet interface of at least 1 Gbps. A 100 Mbps connection does not meet the requirement because the AR-300 generates approximately 250 Mbps of data traffic. To minimize local network load and avoid congesting broader network segments, the APU should be connected directly to the same Gigabit Network Switch as the AR-300 (AR-300 → Gigabit Switch ← APU).
What are the specific power supply (PoE) and physical cabling requirements for the AR-300?
Answer:
The AR-300 is powered via PoE++ compliant with IEEE 802.3bt Type 3 at 48V and 35W, requiring a matching PoE++ switch or injector. Using a non-compliant power supply can cause unpredictable behavior or physical damage. Cables must be rated for outdoor conditions, feature properly grounded RJ45 shielding, and be mechanically secured to prevent swaying in the radar's coverage field or straining the connector. Using non-supplied Magos cables or failing to properly lock connector caps affects safety and can void the warranty.
What are the default IP addresses and NTP configuration requirements for the system?
Answer:
By default, the AR-300 uses IP address 192.168.40.50, and the APU uses 192.168.40.60. The computer, radar, and APU must share the same subnet to communicate properly, and IP addresses can be reassigned via Radar Manager or the web dashboard. Additionally, configuring an NTP server on both the AR-300 and the APU is essential for proper system operation.
How do scan rates, MASS display refresh rates, and network bandwidth settings impact target tracking performance?
Answer:
The AR-300 radar operates at a native scan rate of 7 Hz and sends point cloud data to the APU/MASS for target processing. In MASS, the display refresh rate is configurable and typically set to around 2.5 Hz to prevent excessive CPU load on client computers. Lowering the refresh rate conserves CPU load and bandwidth, but it degrades the system's ability to track fast or maneuvering targets effectively.
How can multiple AR-300 radars be deployed in dense installations to prevent mutual interference?
Answer:
The AR-300 operates in the X-Band (10–10.5 GHz) with a transmission power of 3.2W and supports 4 separate frequency channels for interference-free coexistence. If a deployment requires more sensors than available frequency channels, time-domain division (or time-based separation between panels on the same channel) can be used, though this reduces the overall scan rate. Consulting Magos for frequency channel selection and radar synchronization is required.
What physical mounting distance, orientation, and tilt angle are required for the AR-300 radar?
Answer:
When installing multiple sensors near each other without facing one another, a minimum distance of 1 meter must be maintained between units. The recommended tilt angle is 30° above the horizon to ensure optimal performance, including near-ground detection while maintaining coverage above the radar. Installers should use a digital level to verify that the roll angle is zero and the width is parallel to the ground; using an improper tilt angle (such as 10°) results in degraded tracking performance.
What software versions, dependencies, and pre-checks are required when troubleshooting AR-300 performance issues?
Answer:
AR-300 testing requires verified software compatibility, such as MASS 3.25.0 Beta for drone radar testing. Before starting a remote support session, technicians must verify ping connectivity to both the AR-300 and APU IP addresses. Diagnostic information to collect includes MASS configuration, HAL logs, MASS logs, radar installation photos, server specifications, and remote access details.