[{"_1":2,"_74":-5,"_75":-5},"loaderData",{"_3":4,"_7":8},"root",{"_5":6},"locale","en","routes/blog-detail",{"_9":10,"_46":47},"blog",{"_11":12,"_13":14,"_15":16,"_17":18,"_44":45},"success",true,"statusCode",200,"message","Blog retrieved by ID d3a9fe68-f439-44da-8c3b-22981aaa8d08 successfully","data",{"_19":20,"_21":22,"_23":24,"_25":26,"_27":28,"_29":30,"_31":32,"_38":42,"_40":43},"id","d3a9fe68-f439-44da-8c3b-22981aaa8d08","title","Upcoming ROS 1 End of Life 12/16/2024","slug","upcoming-ros-1-end-of-life-12162024","description"," Kat Scott ROS 1 Noetic Ninjemys goes End-of-Life 2025-05-31","content","

ROS Noetic Ninjemys, the last ROS 1 release, will reach End of Life in May 2025. Over the past five years we focused our efforts on making ROS 2 a world class framework for professional robot development, and our user community seems to agree. According to September 2024 download data from our servers ROS 2 downloads now make up almost 80% of all ROS downloads. We’ve now seen ROS 2 used successfully in production by a large number of companies, across dozens of industries, and we think it is time for the last remaining ROS users to make the switch.

$\"\"$

What Does End-of-Life Mean?

End of life for ROS Noetic means that the ROS team will no longer support ROS 1. After May 31st of 2025, the ROS team will no longer provide the following for ROS 1:

New features or capabilities
Security updates
Bug fixes, patches or support
Updated binaries

After May 31st, 2025 ROS 1 Noetic users may find themselves exposed to un-patched security vulnerabilities and bugs, with few avenues of support short of fixing these issues themselves and recompiling Noetic from source. However, this isn’t an outright emergency, it is good to keep mind what won’t change after May of 2025.

ROS 1 going end of life does not mean:

ROS 1 binaries will suddenly disappear.
- ROS 1 binaries will continue to be hosted on packages.ros.org
ROS 1 projects will suddenly stop working on May 31st.
- ROS 1 will continue to work, as it does today.
Users must stop using ROS 1 immediately,
- ROS 1 will continue to work, but you should have migration plan as soon as possible.

ROS 2 Migration Options

If you are still using ROS 1 it is time to consider switching to ROS 2 Humble Hawksbill (migration guide) or ROS 2 Jazzy Jalisco (migration guide). Which distro you choose as your migration target is going to depend on the complexity of your ROS 1 system. This migration heuristic tool can help you estimate the complexity of migrating your project to ROS 2. If you have a smaller ROS 1 project, or a reasonably de-coupled workspace, it is most likely that you can migrate to ROS 2 Jazzy Jalisco directly. The ROS community has produced a number of migration tools which you may find helpful, including this migration tool from AWS Labs, and this migration tool from ROS maintainer David Lu!

If your ROS 1 system is tightly coupled, has a number of un-ported dependencies, or is reasonably complex, you may want to take advantage of the ROS 1 to ROS 2 Bridge. The ROS 1 to ROS 2 Bridge performs automated translation between major ROS versions and should allow you to migrate your project one package at a time. The ROS 1 to ROS 2 Bridge was intended to only support ROS 2 distros prior to and including ROS 2 Foxy, and due to operating system constraints it is no longer fully supported by the current ROS 2 releases. However, with a little bit of work, it is still possible to use the ROS 1 / ROS 2 bridge with Noetic and a current ROS 2 distro. Users can either compile ROS 2 Humble from source for Ubuntu 20.04, which has Tier 3 support, or use ROS-O binaries to build their packages on a newer version of Ubuntu (i.e. 22.04 of 24.04).

Other Migration Options

We highly recommend you migrate your ROS 1 project to ROS 2 as soon as possible. Most users have found the migration process less difficult than they initially expected. If you simply can’t migrate your ROS 1 project right now, you do have a few options, however, none of these solutions are officially supported, and we can’t speak to their long-term robustness.

Canonical, offers extended security maintenance for a number of ROS 1 host operating systems for a fee.
ROS-O is a volunteer run effort to extend the support lifetime of ROS 1 projects.
If you simply need an extra set of hands to help with your migration you are welcome to use our jobs board on ROS Discourse to find some help.

What’s New in ROS 2?

Before you begin your ROS migration journey, we recommend you read up on some of the new and improved features in ROS 2. We’ve put together a collection of resources that outline some of the major changes in ROS 2. Almost all of these resources are readily available as part of our migration guide in the ROS 2 documentation. While understanding what has and hasn’t changed between ROS 1 and ROS 2 can make the migration process go a lot smoother, it really isn’t necessary to get started! There’s a lot to love in ROS 2, and we think you’ll find some of the new ROS 2 features make for a much better user experience.

Changes to the ROS API

Most of the ROS 2 API should look familiar to ROS 1 users with a few notable exceptions. Where things have changed, they have changed to address shortcomings in ROS 1. The exciting thing about ROS 2 is that it has given us the opportunity to address a number of user complaints about ROS 1! The list below outlines some of the larger changes to the ROS API found in version 2.

Nodelets in ROS 1 have been replaced with ROS 2’s composable nodes concept. ROS users can now compose their processing routines into the same process space using both compile time and run time composition.
Parameters in ROS 2 now support namespacing, and there is an improved interface for loading, saving, and reconfiguring your parameters. This migration guide provides guidance on how to migrate your parameter set.
ROS 2 supports three different types of launch files: YAML, Python, and XML. There is a complete guide to migrating your ROS 1 launch files available on docs.ros.org.
The ROS 2 lifecycle node API has standardized the lifecycle of ROS nodes. The process of starting and stopping ROS nodes is now much more robust. We recommend taking advantage of this feature when migrating your ROS 1 project.
ROSBag performance has improved significantly in ROS 2, and the new ROS 2 type adaptation makes it even easier to share data using ROS Bags. As of ROS 2 Humble MCap is now the standard ROSBag data format.
If you are looking for examples of common ROS 2 design patterns the ROS 2 Cookbook offers code samples for common ROS 2 tasks.

","thumbnailUrl","https://bd-minio-server-2.shwecode.xyz/mc-store/blogs/3238c578-5257-4de8-b98f-65bb307f2b6e-robots-and-kits-small-collection-image-1.jpg.webp?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Content-Sha256=UNSIGNED-PAYLOAD&X-Amz-Credential=admin%2F20260904%2Fap-southeast-1%2Fs3%2Faws4_request&X-Amz-Date=20260904T134746Z&X-Amz-Expires=604800&X-Amz-Signature=ca8d92604ce6c1a460fdd8b9724b87ce63199ec775a3081c37057998d25a35b6&X-Amz-SignedHeaders=host&x-amz-checksum-mode=ENABLED&x-id=GetObject","tags",[33],{"_19":34,"_35":36,"_23":37,"_38":39,"_40":41},"9e202b74-cace-4226-af81-b7c55f600493","name","Posted by Khant Paing","posted-by-khant-paing","createdAt","2026-01-07T03:25:44.249Z","updatedAt","2026-02-08T17:31:54.600Z","2026-01-07T03:26:15.241Z","2026-02-08T17:20:43.654Z","timestamp","2026-09-04T13:47:46.463Z","relatedBlogs",[48,63],{"_19":49,"_21":50,"_23":51,"_25":52,"_27":53,"_29":54,"_31":55,"_38":62,"_40":62},"0f2a04d2-480b-45ce-9e6d-9484df5e11f6","This is new blog title","this-is-new-blog-title","Read This is new blog title at Mc Store","

Read This is new blog title at Mc Store

","https://bd-minio-server-2.shwecode.xyz/mc-store/blogs/6900b5c2-f3e2-46d9-abfc-21dd5ce5f470-pikachu-pixel-art-12800x7200-15216.png?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Content-Sha256=UNSIGNED-PAYLOAD&X-Amz-Credential=admin%2F20260904%2Fap-southeast-1%2Fs3%2Faws4_request&X-Amz-Date=20260904T134746Z&X-Amz-Expires=604800&X-Amz-Signature=90eef3a0990ca07e5d5792d6b894275a3f98a3f86819f8cf5bf480b29ad2669a&X-Amz-SignedHeaders=host&x-amz-checksum-mode=ENABLED&x-id=GetObject",[56],{"_19":57,"_35":58,"_23":59,"_38":60,"_40":61},"493b8087-54d2-476b-8248-d3f6394e4d0b","new tag 1 updated","new-tag-1-updated","2026-03-07T09:58:23.360Z","2026-03-07T09:58:32.119Z","2026-03-07T09:59:26.322Z",{"_19":64,"_21":65,"_23":66,"_25":67,"_27":68,"_29":69,"_31":70,"_38":72,"_40":73},"e71b0d8b-7ccf-48fc-9265-f1344ab674b9","How to Work a Fire-Fighting Robot?","how-to-work-a-fire-fighting-robot","Credit to https://www.hcrot.com/how-to-work-a-fire-fighting-robot","

In the high-stakes world of emergency response, where every second counts and every flame presents a lethal gamble, a new breed of first responder is emerging. These are not flesh-and-blood heroes, but ones forged from steel, silicon, and sophisticated code. The firefighting robot is no longer a concept from science fiction; it is a tangible, operational asset on the front lines of some of the world’s most dangerous blazes. But how exactly does this technological marvel operate? What transforms a machine into a firefighter? The process is a fascinating symphony of advanced engineering, real-time data, and human oversight, working in concert to protect lives and property.

At its core, the operation of a fire robot can be broken down into a continuous loop of perception, processing, and action. This cycle, managed either autonomously or via remote control, allows it to navigate chaotic, hazardous environments and effectively combat fires that would be unsurvivable for humans.

The Anatomy of a Modern Firefighter: Key Components

Before diving into the \"how,\" it's essential to understand the \"what.\" A typical automatic fire-fighting robot is built around a rugged, durable chassis, often on continuous tracks similar to a tank, allowing it to traverse unstable terrain, climb stairs, and navigate through debris. Mounted on this robust platform are its critical systems:

The Sensory Suite (Perception): This is the robot’s eyes, ears, and nose. It typically includes:
- Thermal Cameras: The most crucial sensor. These cameras see heat instead of light, allowing the robot to pinpoint the seat of a fire through thick, blinding smoke, identify hot spots, and locate victims based on their body heat.
- Standard RGB Cameras: Provide high-definition visual feedback to the human operator, offering context and a clear view of the environment when smoke is not impenetrable.
- Gas Sensors: Detect and measure levels of toxic and combustible gases like carbon monoxide, hydrogen cyanide, or oxygen depletion, providing critical data on atmospheric hazards.
- LiDAR or Ultrasonic Sensors: These act as the robot’s sense of touch and spatial awareness. They constantly scan the surroundings to create a 3D map, detecting obstacles, drop-offs, and walls to enable safe navigation.
The Suppression System (Action): This is the business end of the robot. The most common system is a powerful water cannon or monitor, capable of delivering hundreds or even thousands of gallons per minute. Many robots can also discharge foam for fuel-based fires or fine water mist for specific hazards. The nozzle is often articulated, allowing for precise control over the stream's direction and pattern.
The Locomotion and Power System (Mobility): The tracks provide stability and all-terrain capability. The heart of the system is a high-capacity, rechargeable battery pack, powering all motors, electronics, and the pump for several hours. Some industrial models can also be powered by a hose reel, providing virtually unlimited operational time.
The Communication and Control Hub (Processing): This is the robot's brain and its link to the outside world. It comprises an onboard computer that processes all sensor data and a robust wireless communication system (often using multiple frequencies like Wi-Fi, 4G/5G, or radio for redundancy) to transmit video, data, and telemetry to the operator’s control unit and receive commands in return.

The Operational Workflow: From Dispatch to Extinguishment

The work of a remote-controlled fire-fighting robot begins long before it rolls into a burning structure. Its operation is a multi-stage process.

Stage 1: Deployment and Setup

When a major fire is reported—especially at an industrial plant, airport, chemical warehouse, or a large structure where the risk is immense—the decision may be made to deploy the firefighting robot. It is transported on a specialized trailer or vehicle. Upon arrival at the scene, the crew positions the robot at a safe staging area. The first step is establishing a secure communication link. The operator, stationed a safe distance away, activates the control unit, which is typically a ruggedized laptop or a dedicated console with joysticks and monitors. The robot is switched on, and a systems check is performed. The operator confirms video feeds from all cameras are clear, the thermal imaging is functional, sensor data is streaming, and the drive and pump systems are responsive.

Stage 2: Entry and Reconnaissance

This is where the fire robot proves its immediate value. The operator drives it toward the heart of the fire. Using the live video and sensor feedback, they navigate the robot through smoke-filled corridors or across unstable floors. The thermal camera is indispensable here, revealing the layout of the room and the location of the fire's origin hidden behind smoke and flames. Simultaneously, the gas sensors begin transmitting real-time atmospheric analysis back to the command post. This intelligence is priceless; it tells incident commanders whether the environment is becoming explosive or dangerously toxic, informing the safety protocols for any human firefighters who may need to follow.

Stage 3: Fire Suppression and Active Engagement

Once the automatic fire-fighting robot has a clear line of sight to the fire, the suppression phase begins. This can be executed in two primary modes:

Remote-Controlled Mode: The human operator is in direct command. Using the joysticks, they aim the water cannon, adjust the stream from a straight jet to a fog pattern, and control the flow rate. They use the visual and thermal feeds to see exactly where the water is hitting, adjusting in real-time for maximum effect. This mode allows for tactical, experienced-based decisions, such as cooling adjacent tanks or structures to prevent a BLEVE (Boiling Liquid Expanding Vapor Explosion).
Autonomous/Automatic Mode: Many modern robots possess an automatic fire-fighting robot capability. In this mode, the operator can designate a target—for instance, by clicking on a hot spot on the thermal display. The robot's onboard AI then takes over, using its cameras and LiDAR to keep the nozzle locked on that target, automatically adjusting the aim as the robot moves or as the fire shifts. Some advanced systems can even identify the fire themselves and engage without a direct target command, making them truly automatic fire-fighting robot systems. This frees the operator to focus on navigation and broader strategy.

The robot can advance into areas being doused, applying water or foam directly at the base of the flames with relentless precision, unaffected by the extreme heat and radiating energy.

Stage 4: Sustained Operations and Withdrawal

A key advantage of a firefighting robot is its endurance. It does not tire, does not need an air tank, and is immune to psychological stress. It can maintain its position, applying a continuous stream of suppressant for as long as its water supply and battery last, holding the line until the fire is under control. After the main threat is neutralized, it can be used for overhaul—searching for and extinguishing hidden embers and hot spots with its thermal vision. Once the mission is complete, the operator simply drives the robot back to safety for decontamination, recharging, and readiness for its next call to action.

The Human-Machine Partnership: Collaboration, Not Replacement

It is a common misconception that an automatic fire-fighting robot is designed to replace human firefighters. The reality is more nuanced and powerful: it acts as a force multiplier and a guardian. The robot handles the \"dull, dirty, and dangerous\" tasks, allowing human firefighters to leverage their strategic thinking, adaptability, and complex problem-solving skills from a position of greater safety. The remote-controlled fire-fighting robot extends the reach and capability of a fire department, enabling them to attack fires that were previously considered lost causes or suicide missions.

The technology behind these machines is evolving rapidly. Future iterations may include swarms of smaller fire robot units working together, AI capable of predicting flashover events, and even more advanced suppression agents. The fundamental way a firefighting robot works—by perceiving a lethal environment, processing that information, and taking decisive, sustained action—represents a paradigm shift in fire safety. It is a powerful tool that saves lives, both civilian and firefighter, by boldly going where no one safely can. As this technology becomes more accessible and sophisticated, the sight of a rugged, tireless firefighting robot rolling into the inferno will become an increasingly common and welcome reassurance in our ongoing battle against fire.

Original Link - How to Work A fire-fighting Robot?

","https://bd-minio-server-2.shwecode.xyz/mc-store/blogs/d86e1c69-1d00-4664-b242-789b63403f17-Screenshot_2026-02-08_235934.png?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Content-Sha256=UNSIGNED-PAYLOAD&X-Amz-Credential=admin%2F20260904%2Fap-southeast-1%2Fs3%2Faws4_request&X-Amz-Date=20260904T134746Z&X-Amz-Expires=604800&X-Amz-Signature=b32938fd6c8a5b33572066f4634f6fa8df207083430c6b82b8daf5741fd7953b&X-Amz-SignedHeaders=host&x-amz-checksum-mode=ENABLED&x-id=GetObject",[71],{"_19":34,"_35":36,"_23":37,"_38":39,"_40":41},"2026-02-08T17:29:27.712Z","2026-02-08T17:31:04.150Z","actionData","errors"]

Upcoming ROS 1 End of Life 12/16/2024

Related Blogs

This is new blog title

How to Work a Fire-Fighting Robot?