¹ 5G performance figures are based on Qualcomm SDX62 reference documentation and lab-validated PHY benchmarks under controlled RF conditions. Achieved user throughput depends on spectrum availability, carrier aggregation combos, operator provisioning, local interference, and environmental RF quality. Actual field rates may be significantly lower.

² Sub-6 GHz only: olixLink™ C1 does not support FR2/mmWave frequencies. Band availability varies by region, and operator enablement is required. Use in unsupported or unlicensed bands may breach regulatory frameworks.

³ Dual-SIM functionality enables failover, not simultaneous data aggregation. Switchover behavior depends on carrier timers, SIM authentication latency, and local firmware policy. Seamless handover is not guaranteed across heterogeneous RATs or operators.

⁴ SIM card compatibility requires nano-SIM with correct APN configuration. Use in private 5G or CBRS/n48 deployments requires licensed spectrum access and a compatible core network. Users are responsible for ensuring regulatory authorization.

⁵ Wi-Fi 6 throughput values are theoretical PHY maxima. Real application throughput depends on modulation schemes, channel width, MU-MIMO utilization, DFS restrictions, coexistence with legacy Wi-Fi clients, and environmental interference.

⁶ Ethernet negotiation supports 10/100/1000/2500Base-T. Link stability at 2.5G requires Cat6 cabling and PoE injectors/switches rated for 2.5G. Downgrade to 1G or 100M may occur under marginal cable conditions or EMI stress.

⁷ PoE operation requires standards-compliant IEEE 802.3af/at injectors. Passive PoE or third-party proprietary power injectors are not supported. Overvoltage or incorrect wiring can cause irreversible damage not covered under warranty.

⁸ Latency guarantees (sub-250 µs DDS transport, sub-ms control-loop latency) apply only in optimized SA 5G or wired LAN setups with end-to-end QoS alignment. Public 5G, enterprise firewalls, and mixed WAN paths may introduce uncontrolled jitter.

⁹ ROS 2 support is validated on Humble and Iron distributions with Cyclone DDS and Fast DDS. Other DDS implementations may require user configuration of reliability, history depth, discovery, and deadline settings.

¹⁰ ROS topic structures (/olixlink/status, /olixlink/diag, /olixlink/netif) may change as firmware evolves. Developers should not rely on undocumented fields. Backwards compatibility is maintained on a best-effort basis only.

¹¹ QoS templates (“command”, “telemetry”, “video/point-cloud”) are tuned for robotics scenarios. End-to-end performance depends on subscriber alignment, application middleware, and network scheduling. Determinism is not guaranteed in mixed networks.

¹² TSN/PTP features require all intermediate switches and endpoints to support IEEE 802.1AS, 802.1Qbv, or equivalent. Legacy segments or unmanaged switches will degrade synchronization and may nullify TSN benefits.

¹³ ZeroTier® integration requires a valid network ID, account, and relay accessibility. Certain enterprise NATs/firewalls may block required UDP traversal. Users are responsible for configuring security groups and network policies.

¹⁴ VPN performance (WireGuard, OpenVPN, GRE, L2TP, PPTP, IPsec) depends on CPU utilization and cipher strength. Throughput reductions are expected with higher security levels, multiple tunnels, or concurrent telemetry/video workloads.

¹⁵ Web-UI access requires modern browsers and local reachability. Responsiveness may degrade when high-rate ROS diagnostics are streamed simultaneously. Remote access via VPN/ZeroTier inherits the policies of those networks.

¹⁶ Antenna system comprises six external elements: four cellular (~4 dBi) and two Wi-Fi (~5 dBi). Performance varies with antenna orientation, polarization, mounting structure, and surrounding metallic objects. Incorrect installation can degrade link quality.

¹⁷ Ingress protection is IP66 when cable glands, seals, and connectors are correctly tightened. Protection is limited to high-pressure water jets; it is not rated for submersion, chemical exposure, or long-term salt spray without additional coating.

¹⁸ Thermal envelope assumes typical outdoor operation. Sustained uplink load in direct sunlight may trigger thermal throttling. Users must account for airflow, shading, or protective housings in high-temperature deployments.

¹⁹ Mechanical dimensions are approximate. Cable bends, connectors, antennas, and mounting brackets add to total space. Users should allocate installation clearance beyond the listed 145 × 130 × 45 mm housing footprint.

²⁰ Default login and addressing (SSID olixLink-C1, IP 192.168.7.1, credentials olive/one) are intended for initial setup only. Customers must change passwords, rotate keys, and apply hardened configurations before production use.

²¹ Firmware updates are delivered as cryptographically signed packages. Interrupted updates may require manual recovery. Rollback mechanisms aim to prevent lockouts, but persistent update failures require RMA service.

²² Electromagnetic compatibility (EMC) depends on shielding, grounding, and installation practices. Long PoE runs should incorporate surge arrestors, lightning protection, and grounding compliant with local codes. Olive Robotics is not liable for site-specific EMC issues.

²³ Fleet management telemetry may include device identifiers, status, and network statistics. Responsibility for compliance with GDPR, HIPAA, or equivalent privacy regulations lies with the deploying operator.

²⁴ Regulatory approvals (CE, RoHS) apply to the hardware as imported. Carrier certification may differ regionally; operators may require additional acceptance testing. Customers must confirm network authorization prior to deployment.

²⁵ Third-party interoperability (industrial protocols, RTSP/RTMP, MQTT brokers, VNC, SSH) is provided on a best-effort basis. Stability and security depend on third-party service quality, not Olive Robotics.

²⁶ VPN tunneling for industrial protocols (PROFINET, EtherCAT over VXLAN, Modbus over IPsec) requires customer validation. Not all legacy systems tolerate tunneling latency, fragmentation, or jitter.

²⁷ Application suitability examples (UAVs, AMRs, AGVs, marine robots, wearables, smart agriculture) are illustrative. Performance depends on payload integration, environmental factors, and network coverage. Olive Robotics does not warrant suitability for all mission-critical use.

²⁸ High-interference environments (industrial floors, ports, factories) may reduce throughput. Mitigation requires spectrum planning, antenna placement, and QoS tuning. Olive Robotics provides integration guidance but not performance guarantees.

²⁹ Liability for data loss: Olive Robotics is not responsible for corrupted, delayed, or dropped packets in any deployment. Customers should implement redundancy, buffering, and retry mechanisms for critical data.

³⁰ Security responsibility: While olixLink™ C1 supports encryption, VPNs, and firewalls, final system security depends on customer configuration, password hygiene, and certificate management. Olive Robotics cannot guarantee protection against misuse.

³¹ Private 5G deployments require licensed spectrum, 5GC infrastructure, and integration expertise. Olive Robotics supplies hardware and firmware only. End-to-end compliance and operator approval rest with the customer.

³² Specifications subject to change: All listed features, dimensions, and interfaces are accurate at release but may be revised without notice. Images may depict pre-production renders. Accessories, SIM slot counts, and included kits may vary by SKU or batch.

* Some features, applications, and services may not be available in all regions or all languages.