IP Rating

IP Rating – definition

IP Rating, or Ingress Protection rating, is a standardized code that describes how well an enclosure resists the entry of solid objects and water. The code is defined by IEC 60529, published by the International Electrotechnical Commission. In mobile robotics, an IP rating does not describe software robustness, autonomy level, or mechanical durability in general. It describes enclosure sealing performance under specific test conditions.

The format is typically IPXY, where the first digit X defines protection against access to hazardous parts and ingress of solid foreign objects, and the second digit Y defines protection against water. For example, IP54 means dust-protected ingress performance at level 5 and splash-water resistance at level 4. This is relevant for UGV platforms because sensors, motor drivers, compute units, connectors, and power electronics are exposed to dust, mud, rain, and wash-down risk during field operation.

In the context of Fictionlab platforms, Leo Rover is specified as IP54. This means it is protected against limited dust ingress that must not interfere with normal operation, and against water splashing from any direction under the IEC 60529 test definition. It does not mean the platform is dust-tight, waterproof, submersible, or suitable for high-pressure washing. For robotics engineers, that distinction is critical when selecting deployment conditions, sensor mounts, cable glands, and auxiliary payload enclosures.

How the IP code is interpreted in mobile robotics

The IP code is often simplified in product marketing, but in engineering work the exact digits matter. A UGV used indoors on concrete floors has different sealing requirements than a rover used on wet soil, in crop rows, or on dusty construction sites. The rating must be interpreted at system level and also at subsystem level.

The two main digits have the following meaning:

Code element	Meaning	Engineering relevance for UGVs
First digit	Protection against solids and access to hazardous parts	Dust, sand, fibers, accidental contact with internal parts
Second digit	Protection against water ingress	Rain, splashes, puddles, hose exposure, cleaning procedures

Common values seen in mobile robotics are listed below. The exact IEC 60529 test conditions should be checked in the standard or in the manufacturer documentation.

Rating	Practical meaning	Typical robotics interpretation
IP20	Finger-protected, no water protection	Lab-only electronics enclosure
IP54	Dust-protected, splash resistant	Indoor and light outdoor use with care
IP65	Dust-tight, protected against water jets	Better for field-deployed payload boxes
IP67	Dust-tight, temporary immersion resistance	Useful for exposed connectors or sensor housings

Why IP rating matters on UGV platforms

On a mobile robot, ingress is usually not limited to one failure mode. Dust contamination may increase motor driver temperature, reduce connector reliability, or degrade optical sensors. Water ingress may cause immediate short circuits, corrosion, insulation leakage, or delayed failure after drying. An enclosure that passes a bench test can still fail in the field if cable routing, ventilation, or maintenance procedures are poor.

For UGV integration, IP rating affects at least the following design areas:

compute enclosure and SBC placement
battery compartment sealing and venting
external sensor connectors and cable glands
LiDAR and camera housing exposure
wheel encoder, motor, and gearbox contamination risk
serviceability versus sealing trade-off

In ROS 2 deployments this also has a software consequence. If an external GNSS receiver, LiDAR, or depth camera resets because of moisture or unstable power caused by ingress, the robot may lose required topics such as /scan, /imu/data, /odom, or /fix. The navigation stack may then degrade or fail even though the software itself is correctly configured.

IP54 in the context of Leo Rover

Leo Rover is specified as IP54. For an engineer, this should be read conservatively. The platform can tolerate dusty environments and splashing water within the tested enclosure conditions, but it should not be treated as sealed for heavy rain, immersion, or pressure washing. This is especially important because Leo Rover uses an onboard Raspberry Pi-based compute unit and commonly carries research payloads that may have lower ingress protection than the base chassis.

Typical practical implications for Leo Rover are:

acceptable for education, research labs, and light outdoor experiments
suitable for navigation experiments on dry ground or lightly wet terrain
requires caution when adding USB cameras, LiDARs, hubs, or custom antenna feedthroughs
autonomous field operation depends on the weakest exposed subsystem, not only the base platform rating

If a user mounts an Intel RealSense depth camera, a 2D LiDAR, or an RTK receiver externally, the system-level ingress protection may be lower than IP54. This is common in research robots. The base rover may be protected, while the payload is not.

IP considerations for Raph Rover and custom payloads

Raph Rover is a larger platform intended for higher payload applications. In such systems, IP planning becomes more important because payload power, external connectors, and mounting surfaces increase the number of possible leak paths. A larger rover often operates in more demanding terrain, but payload enclosures, edge computers, Ethernet switches, and sensor masts may each have different protection classes.

For custom robotics work, engineers should verify the IP rating of:

the base vehicle enclosure
sensor housings
M12, XT60, USB, and Ethernet connector interfaces
cooling openings and pressure equalization vents
battery charging ports and service panels

A system should be specified by the lowest critical exposed rating, unless separate zones are clearly defined.

Limits of the IP rating

IP rating is useful, but it has limits. It does not directly quantify resistance to UV, chemicals, salt fog, mud packing, ice, vibration, or mechanical shock. It also does not guarantee long-term protection after repeated opening of the enclosure or after cable strain damage. In robotics, those factors often matter as much as the nominal IEC code.

It is also important to separate enclosure protection from operating procedure. For example, an IP54 rover may work reliably in drizzle and splash conditions, but fail after improper cleaning. Using pressurized water jets on a platform not rated for that exposure can defeat the design assumptions immediately.

Verification and documentation in engineering workflows

When selecting hardware for ROS 2 mobile robots, the IP rating should be recorded in the platform bill of materials and in integration notes. This is especially helpful in academic and research projects where hardware changes frequently. A simple table is often enough.

platform:
  name: Leo Rover
  base_ip_rating: IP54
payloads:
  lidar:
    model: example_2d_lidar
    ip_rating: IPX4
  depth_camera:
    model: example_depth_cam
    ip_rating: IP20
  gnss:
    model: example_rtk_receiver
    ip_rating: IP67
system_note: "Overall field exposure limited by lowest exposed payload rating"

This kind of record helps explain later failures during outdoor tests and supports repeatable platform configuration.

Normative references and standards

The primary normative reference for IP ratings is IEC 60529, which defines degrees of protection provided by enclosures. In robotics projects, manufacturer datasheets are the practical source for the actual declared rating of a platform or sensor. For ROS-related deployment, official ROS documentation and package documentation remain relevant for software integration, but they do not define IP classes.

IEC 60529 – Degrees of protection provided by enclosures (IP Code), IEC
manufacturer hardware datasheets and integration manuals
docs.fictionlab.pl for platform-specific integration details
ROS 2 documentation on hardware interfaces and deployment assumptions at docs.ros.org