How remote inspection robots reduce downtime

How remote inspection robots reduce downtime

By Scott Simmie

 

Inspection robots aren’t cheap.

We fully acknowledge that might not be the best opening pitch, but hear us out.

While a capable inspection robot can be costly, so is downtime. So is dispatching human beings to distant locations. Electrical substations and certain oil and gas assets are often remote and require many hours of driving to reach – plus the cost of hotels and per diems. Sometimes, companies even have to charter a helicopter just to place eyes on those remote spots. Depending on the sector, these inspections might take place monthly, bi-weekly – or at some other interval.

Point is: Regular inspection of remote assets is an absolute necessity. An inspection can troubleshoot for regular wear and tear, thermal anomalies, damage from animals, vandalism, environmental impact, leaks – the list goes on. A human being (often equipped with handheld scanners and other detection equipment) can generally spot all these things.

But so, too, can a robot. And, unlike a human being when it comes to remote assets, an autonomous robotic inspector can be on the site 24/7. It never requests a hotel room, doesn’t charge overtime – and never forgets to do everything it’s been instructed to carry out.

Below: The InDro Robotics Sentinel, at an electrical substation in Ottawa

Sentinel enclosure Ottawa Hydro

DOWNTIME

 

There are two types of downtime: Planned and unplanned. The former, obviously, is pre-arranged. Maybe it’s time to replace certain pieces of equipment or do other scheduled maintenance. Planned downtime can include hardware and software upgrades, even large-scale replacements. For those companies in service provision, including those in the B2B space, a scheduled event minimises downtime because everything is lined up in advance for the necessary task. In addition, you can notify consumers or clients that the service or commodity will be temporarily unavailable – and schedule the downtime to minimise disruption. Customers and clients generally understand these inconveniences when they know about them ahead of time.

Then there’s that other kind of downtime: Unplanned. Something goes wrong and you need to scramble to fix it. Precisely because these are unexpected, you might not have the required widgets or personnel on-hand (or on-site). And it’s not just the repair itself. There’s usually lost revenue, reputational damage, and even more:

“The repercussions of unplanned downtime extend beyond immediate financial losses,” explains this overview.

“Companies may face financial penalties and legal liabilities, especially if downtime leads to non-compliance with regulatory requirements. These penalties can add another layer of financial strain on top of the already significant downtime costs.”

We’ve all heard stories about airlines being fined, sometimes heavily, for unexpected delays. And the reputational damage? You wouldn’t have to look hard to find consumers who have switched airlines, internet providers and more due to unplanned downtime that inconvenienced them.

That same article dips into the oil and gas sector, using data from a 2016 study by Kimberlite (a research company specialising in the sector) which found offshore organisations face an average of $38M US annually in costs from unplanned downtime. Those with the worst records racked up yearly tabs close to $90M US. So clearly, it’s something most would like to avoid.

 

THE ADVANTAGES OF INSPECTION

 

Regular robotic inspection can help reduce unplanned downtime by identifying potential failures before they happen. Is a key component starting to age? Has wildlife encroached on sensitive components? Did the storm that passed through overnight have an impact on anything? Are all gauges reading as they should? Are there any thermal anomalies? Is there the molecular presence of hydrocarbons or other indicators above a safe threshold? Are there any strange new noises, such as arcing or humming?

Yes. People can do this when they’re dispatched. But a robot tailored for inspection – and they can be customised for every client’s needs – can carry out these same tasks reliably, repeatedly, and on schedule.

This idea of predictive maintenance is very much a pillar in the world of Industry 4.0, or 4IR (which we recently explored in some detail). As companies move into this next phase, particularly in the manufacturing sector, Smart Devices are being integrated in every conceivable location across newer factory floors. In conjunction with software, they keep an eye on critical components, identifying potential problems before they occur. Industry leaders in this space, such as Siemens, state these systems can result in up to a 50 per cent reduction in unplanned downtime, and up to a 40 per cent reduction in maintenance costs.

That’s the gold standard. But we are just at the cusp of this integration, and it’s more broadly targeted at the manufacturing sector. Those remote electrical substations and oil assets are still, in many ways, not that smart when it comes to asset intelligence and will require regular inspection for many years to come.

Below: InDro’s Sentinel inspection robot, which can be customised for any inspection scenario, It’s seen here at a demo for Ottawa Hydro

Sentinel enclosure Ottawa Hydro

THE SENTINEL SOLUTION

 

Sentinel is our flagship inspection robot. Our first iteration was in 2022 and – as with all InDro innovations – we have continued to enhance its capabilities. As new advances in sensors and compute have emerged, so too have Sentinel’s powers. But Sentinel’s evolution goes far beyond adding new LiDAR, depth cameras or processors. In the background at Area X.O, we are continuously improving our own IP. Specifically, our InDro Autonomy and InDro Controller software.

InDro Controller is a desktop-based interface with Sentinel (or any other ROS-based robot). Fully customisable and easy to use, it allows our clients to plan and monitor missions with ease. A few clicks allows users to set up repeatable points of interest where the robot will carry our specific inspection tasks. Need eyes on a critical gauge? Have InDro Controller stop Sentinel at a particular spot. Use the 30X optical Pan-Tilt-Zoom camera to frame and capture the shot. Happy with the results? Great. InDro Controller will remember and carry out this step (and as many others as you’d like) when it next carries out the mission. Collisions won’t be an issue, as InDro Autonomy’s detect and avoid capabilities ensure there won’t be any mishaps on the way. In fact, you could drop Sentinel in a completely unfamiliar setting littered with obstacles, and it could map that site and even produce a precision scan. And, like a regular visit to the robot doctor, InDro Controller also monitors the overall system health of any integrated device.

From the outset, Sentinel has been on a continuous journey pushing the R&D envelope, with testing and rigorous third-party evaluation. An earlier iteration was even put through demanding tests by the US Electric Power Research Association (EPRI) at its test facility in Massachusetts. All of these deployments have resulted in learnings that have been incorporated into our latest version of Sentinel.

 

SET AND FORGET

 

When it comes to remote assets, our clients clearly needed a hands-off approach. That meant we had to incorporate some sort of autonomous charging, since there’s no one on these sites to plug it in. We evaluated mechanical docking systems, but realised these physical mechanisms introduce another potential point of failure.

And so we ultimately settled on a powerful wireless charging system. Using optical codes, Sentinel returns to a housed structure following its missions. It then positions itself snugly up to the wireless charging system so that it’s ready for the next deployment (you’ll see a picture of one of our earlier test structures in a few seconds). We needed to avoid metal to ensure the cleanest possible wireless communication (Sentinel operates over 5G and also has the option for WiFi). Housing Sentinel when it’s off-duty protects it from unnecessary exposure to the elements, though it’s certainly built to operate in virtually anything Mother Nature can throw at it (short of a hurricane).

Finally, Sentinel also has InDro Commander on board. In addition to housing its powerful brain, Commander allows for the easy addition of additional sensors by simply plugging them in. It provides both power and a data pipeline, and InDro Controller has been built to instantly recognise the addition of any new sensors. In other words, if a client’s requirements change and a new sensor is required, Sentinel can be modified with relative ease and no new coding.

Below: Sentinel, following a demonstration for Ottawa Hydro, snugs up to charge

Sentinel enclosure Ottawa Hydro

THE SENTINEL EVOLUTION

 

As mentioned, Sentinel has gone through a ton of testing, coding and development to reach its current iteration. We’ve taken literally all of our learnings and client feedback and put them into this robot. Sentinel does the job reliably and repeatedly, capturing actionable data intended to reduce downtime for our clients. What’s more, we have moved past the phase of producing these robots as one-offs when demand arises. With our fabrication facility InDro Forge, we are now commencing to manufacture Sentinel at scale.

“Sentinel is now a fully mature and market-ready product,” says InDro Founder and CEO Philip Reece. “We already have multiple Sentinels on the ground for a major US utility client and have other orders pending. We – like our clients – are confident Sentinel is worth the investment by reducing downtime and saving companies the expense and time of sending people to these remote locations for inspection work.”

Interested in learning more, or even taking the controls for a remote demonstration of Sentinel and InDro Controller? Contact us here.

What Canada’s new drone regulations mean for you

What Canada’s new drone regulations mean for you

By Kate Klassen, Training and Regulatory Specialist

 

It’s not every day I get excited to see an email before 0600. But yesterday, March 26, was one of those days! 

Unexpectedly, Transport Canada announced the publication of the highly anticipated Canada Gazette II which included new regulations for RPAS Operations Beyond Visual Line-of-Sight and Other Operations.  

It’s a hefty publication with lots of cross-references and makes for a bit of a dense read. But after a day of reading, re-reading, digesting and consulting with other colleagues who share my nerdiness about this area, I’m pleased to provide this overview – which we’ll continue to update as new information becomes available.  

All-in-all, it’s what we were expecting and hoping to see: Common-sense amendments to existing regulations, noticeable inclusions from feedback on the Canada Gazette I draft, and formalization of the next phase of routine RPAS operations in Canada.  

If you were one of the many who took the time to provide comments to Transport Canada following CG1, well done. What we saw today is proof they listen and that those efforts matter. Thank you, TC! 

Some regulations come into effect on April 1 2025, with others commencing November 4, 2025. This phased approach enables the mechanisms for compliance to be in place prior to requiring compliance with them. In other words, it gives you time to get prepared before it’s required by law. So don’t panic. There are no major changes required before this flying season. You can’t even fly BVLOS under these rules until November.

Now, let’s dive in. 

Below: Low-risk BVLOS flights will be permitted starting November 4, 2025. These operations will require a new Level 1 Complex RPAS Certificate

 

PRACTICALLY SPEAKING

 

As mentioned, the document published yesterday is complex. Our goal here is explain what it actually means in the real world. So we’re going to break this down into implications for different scenarios. Here’s what the new rules mean for RPAS pilots with: 

 

…a sub-250 gram drone
  • On April 1, there are more regulations than just the CAR 900.06 ‘don’t be an idiot’ rule that come into force. These specifically spell out steps to follow if you inadvertently enter restricted airspace (CAR 900.07) and include prohibitions around emergency security perimeters (CAR 900.08) 
…a Basic RPAS Certificate
  • Not many changes aside from general tidying of rules to ensure intent aligns with application 
  • You can allow a non-certified individual to fly under your supervision (CAR 901.54) 
  • You are qualified as a visual observer for BVLOS operations 
…an Advanced RPAS Certificate
  • You get new capabilities as of November 4th – and you don’t have to do any additional testing to take advantage of them! 
  • You’ll be able to carry out EVLOS – Extended Visual Line Of Sight operations. This allows you to fly up to 2NM from the pilot, control station and Visual Observer at any time during the flight, provided the pilot and control station are at the take-off and launch location (CAR 901.74) 
  • Sheltered Operation – This allows the drone to be flown around a building or structure without the use of a visual observer, in accordance with certain conditions  
  • Medium Drones: You’ll be permitted to fly drones with an operating weight of up to 150kg  
  • With an Advanced Certificate already in hand, you meet the prerequisite to begin your Level 1 Complex ground school (more in a moment). If you’ve passed the Advanced Certificate but only hold your Basic because you haven’t yet done your Flight Review, you can pursue the Level 1 Complex
5G Drones

AND ROUTINE, LOW-RISK BVLOS?

 

This was an area the industry had really been pushing for in the new regulations. Specifically, to be able to carry out such flights without the need for a Special Flight Operations Certificate. Here, too, there’s good news:

  • After November 4 2025, you’ll be able to fly low-risk BVLOS if you hold a Level 1 Complex RPAS pilot certification (CAR 901.89). This means BVLOS in uncontrolled airspace and away from people
  • Permits the operation of a 250g – 150kg RPAS to conduct a BVLOS operation in uncontrolled airspace and one kilometre or more from a populated area 
  • In addition to holding a Level 1 Complex pilot certificate, you also need to be an RPAS Operator (RPOC) or an employee/agent of one and comply with the conditions of your certificate (CAR 901.88) 

    

INTERESTING NUGGETS: 

 

  • RPAS Operating Certificate uses the acronym RPOC rather than ROC (as was drafted previously). This is likely in response to anticipated confusion with the ROC-A or Radio Operator Certificate with Aeronautical qualification issued by ISED
  • The new regs contain detailed guidance for visual observers and their requirements in various scenarios
  • You can’t “daisy chain” Visual Observers for EVLOS over greater distances. The pilot/control station needs to be at the take-off and landing area and the RPA can’t go further than 2 NM from the pilot, control station AND VO. 
  • Despite previous suggestions, there is no medical requirement! Just fit-to-fly rules like previously

 

There are also some changes to SFOC requirements. Police operations at events won’t require an SFOC. Department of National Defence operations won’t require them, just adequate coordination. In addition, you’ll be able to drop lifesaving gear without an SFOC, providing you don’t create a hazard. 

Declarations, maintenance and servicing will take on a more prevalent role (not surprising, given the EVLOS, low-risk BVLOS, and the ease of restrictions on flying heavier drones). It’s also worth noting that the already-useful Drone Site Selection Tool (DSST) will get upgraded to include new situational data layers for lower-risk BVLOS. These layers will include population density, aerodromes, controlled airspace, and Detect and Avoid requirements. 

DJI Dock

KATE’S TAKE

 

Canada Gazette II is a massive document. I actually tried to do a word count and the computer simply froze in fear. But, in conjunction with all of the above, here are some final key takeaways:

  • Don’t freak out: There’s plenty of time to process and time to act. There are no major changes happening before November 4th, though you’ll probably want to get your ducks in a row before then if you anticipate your flying season extending beyond that date
  • For maybe the first time ever, regulations have outpaced technology. We still (desperately) need technical detect solutions that are reliable, capable and affordable
  • We’ve had a few folks reach out about ground school for Level 1 Complex and yes – we absolutely will be offering this. At FLYY, we have things well underway as we were anticipating this announcement.

Unlike previous ground schools, there are some instructor requirements that need to be in place before we can even make the declaration to TC that we’re offering TP15530 compliant training. We’re on top of it!

We plan to start offering live, TC-compliant courses prior to the end of April. Over a series of weeks, these courses will run every Wednesday at 0930 PDT for 2.5 hours. These sessions will be recorded and made available to all course participants to review or watch at their leisure. We’ll keep you posted as we get closer to launch.

You can take advantage of our presale here to make sure you’re first in line.

InDro’s Dr. Eric Saczuk: The Indiana Jones of Drones

InDro’s Dr. Eric Saczuk: The Indiana Jones of Drones

By Scott Simmie

 

He’s a Fellow International of The Explorers Club – the storied New York-based organization that since 1904 has only accepted members who have travelled to far-flung places (including the moon) in scientific pursuits. He owns a beloved 1989 Volkswagen Westfalia that’s served as his home for academic research and family camping trips. He holds a PhD and sports a prominent and highly meaningful tattoo on his left arm. And, as InDro’s Head of Flight Ops, has flown complex drone missions on six continents – and counting.

As you might have guessed after reading that, Dr. Eric Saczuk has quite the backstory – one that begins in 1974, with his birth in the small city of Opole in what was then-communist southern Poland. His father worked as a high voltage maintenance engineer; his mother as an accountant at the police station. His only sibling, a brother, is nine years older. The family lived in a small one-bedroom apartment, where his parents slept on a pull-out couch.

Eric has pleasant memories of that childhood, which included annual family holidays at state-run resorts around Poland. When Eric was seven, his parents said it was once again vacation time. Bags packed and car loaded, off they went. This time, however, they crossed the border into Czechoslovakia and kept driving into Austria. On day two, his parents had some news: This wasn’t a vacation.

“I remember them turning to my brother and me. They said: ‘We’ve left home and we’re never going back,'” he recalls. “I was seven years old. I burst into tears and I’m like: ‘Oh my God: My friends and my LEGO and my Dinky toys – I’ve left them all behind!’ So my dad promptly took me to a gas station, bought me some toy cars to play with, and I was fine.” (His teenaged brother, who had been desperate to escape, was thrilled.)

They checked in at a refugee camp in Austria, then were transported to lodging in the Austrian alps housing other political refugees from Poland. That would be home for five months. Eric started Grade One in Austria, learning German. His parents wrote letters to Canadian, Australian and American embassies to see if they might be accepted as immigrants.

Eventually, Canada opened the door. And the Saczuk family arrived in Winnipeg on November 12, 1981. It was in the midst of a raging blizzard. There were no skyscrapers, no flashy buildings – none of the things he’d expected from seeing US TV shows like Dallas and Kojak.

“I thought we were in freaking Antarctica,” laughs Eric.

Below: Eric, second from right, and his family

Eric Saczuk

CHAPTER TWO

 

The Sackzuks began their new lives. And one outing, when Eric was eight, proved a seminal event. His father took him to an air show that happened to feature the legendary McDonnell Douglas F15 Streak Eagle, a stripped-down fighter jet so powerful it could accelerate while in a vertical climb. The aircraft ultimately set eight records, including reaching an altitude of 98,425 feet just 3 minutes and 27.8 seconds after brake release (it then coasted to 103,000 feet). Eric was absolutely awestruck.

“So I saw this thing, full after-burner, go ballistic up into the sky. I’m like, ‘Holy shit, that’s what I wanna do.’ So, from then until I was probably 18 I just ate and slept and pooped airplanes. That was my life.”

He frequently cycled the 15 kilometres to the airport to watch aircraft. He read every aviation magazine or book he could get his hands on, including Ground School manuals. He was obsessed. When he was 15 and a half – the earliest age possible – he applied for the Canadian Air Force Reserves. His security clearance took nine months due to his background in a then-communist country. As he was wrapping up Grade 10, he was accepted to become an Airframe Technician at Squadron 402. His first day of training, he was surprised to see an old pal he hadn’t seen in years in the same CAF classroom – another immigrant from Poland. He and Martin remain friends to this day.

Because it was the reserves, it was a part-time gig. He went through basic training, including Ground School, and by the time he was in Grade 12 the CAF said the next step was for them to head to CFB Borden in just two weeks. That would mean leaving Highschool. But not having Grade 12 would eliminate the potential to become a pilot or reach officer ranks. Couldn’t they just graduate first and then continue? The answer from the military was no; it was now or never. Eric and Martin decided to leave and were granted Honorary Discharges.

But then what?

Below: Eric working a flight simulator in his teens, and in his CAF Reserves uniform

Eric Saczuk
Eric Saczuk

CHAPTER 3

 

We’ll fast-forward here. Eric applied to the University of Manitoba and was accepted into a geophysics program. It was math-heavy and he struggled. His GPA was under 2.0 and for a time he was on academic probation. That is, until he took a summer physical geography course that focussed on map interpretation.

“They put some aerial photos in front of me and I thought –  I know this stuff. Because I’d been doing mission planning or flight planning for years and looking at aeronautical charts. And I’m like: ‘This is so simple.'”

He switched from geophysics into physical geography. He started specialising in a realm of cartography and satellite remote sensing, with an emphasis on geomorphology, “looking at natural hazards like landslides and debris flows and rock fall and flooding. How do we map these things? How do we analyse them in a geospatial way?” By his third year, that GPA jumped to 3.4.

Two academic advisors, both adventurous in their own way, would have great influence on Eric. One of them attached multispectral cameras to a powered paraglider to obtain aerial data, long before the days of drones. The other, an accomplished alpinist who had first ascents of multiple peaks in the Himalayas, took Eric to the Rockies in Alberta for research. The sheer beauty, in conjunction with the geomorphology, touched Eric’s soul in a parallel not dissimilar to seeing that Streak Eagle in his childhood.

“I fell in love with that. I knew this was where I wanted to be.”

For the next several years while obtaining his Masters and then PhD, Eric spent his summers researching amidst geological beauty: Banff, Yoho, Jasper, and Kootenay National Parks. Sometimes he would be living and working from a tent. During one miserable evening, cooking canned food from a camp stove, he spotted someone looking incredibly cozy in a camper van. He soon began a search for his VW Westfalia.

That love of natural beauty (Eric says he’d become something of a “tree-hugger” by this point), eventually led him and his girlfriend to Vancouver (along with a 1989 Westfalia he purchased after flagging down someone driving one at a stop light in Winnipeg). They married and soon there was a daughter on the scene.

He got a gig as a sessional lecturer at Simon Fraser University, and eventually became a professor at BCIT. When drones came on the scene, he saw their geospatial potential and immediately embraced them. He travelled to Antarctica working with drones, did PhD research in India, filmed a documentary in Nepal, hacked his way through forests in the remotest parts of Borneo, and also emerged as a professional photographer. The breadth of these travels, and others, led to him being admitted to The Explorers Club at its highest level. He also became head of BCIT’s RPAS Hub, immersing himself in geospatial and multispectral imaging and data analysis and teaching others.

His first marriage ended, but in 2016, he and Irina married under an arbutus tree on Salt Spring Island. She too had a daughter the same age as his own and they became a blended, happy family – which has collectively enjoyed many adventures in that Westfalia (purchased with 28k on the odometer and now approaching 500,000).

Below: Eric and his family camping with that Westfalia, followed by a mysterious tree in Borneo (which will be explained) and a highly meaningful tattoo

Eric Saczuk
Eric Saczuk
Eric Saczuk

EPILOGUE: THREE TREES

 

The story of Eric (whose Polish name is ‘Arek’), is filled with many other adventures we wish we could include. But there are three brief things worth mentioning as we wrap things up. Remember that trip to Borneo? He went there to assist with an international forest research group, using satellite data to determine the age of rattan plantations. This wasn’t a basic trip, it was an expedition – involving days of hacking through dense forests with a guide. On the third or fourth day, in the middle of nowhere, they reached a section that looked starkly different. The trees were spread out, with a high canopy. The undergrowth they’d pushed through for days was gone. A local guide told Eric this was primordial forest; the trees here had never been cut down.

Some markings on one tree caught his eye. He looked more closely and saw it was a word. The hairs on his neck prickled up. The letters were A-R-E-K were carved in the bark. His own name. How could this be? Turns out, Arek was also the name of a local tribe – and that carving was to mark their territory. But seriously, what were the odds?

“It was a wild, surreal experience to have so far from home.”

Eric has a large tree tattooed on his left arm. It has sparse branches with no leaves. One might assume it simply symbolises a connection with the natural world. And, in one sense, it does. Trees literally give us life, and – whether through CO2 or our own mortal remains – human beings do the same for trees. But it’s more than that.

“It’s my Tree of Death,” he says. Tree of what?

He explains: “As my family starts to age and aunts and uncles start passing away, I wanted a place for them to come and have a final resting place. So this tree is a home for them.”

Meaning, as time passes, he will add to that tattoo.

“When one of my family members passes away, they will become a little crow that lands on a branch.”

And there’s a final connection with trees. Eric wanted to explore opportunities with companies in the drone space on the cutting-edge. He had already been doing advanced thermal and multispectral work, so he was looking for a company pushing boundaries. He hadn’t found a fit, until he happened upon the InDro Robotics booth at a conference. The talk soon turned to BVLOS flights, Transport Canada trials using Command and Control over cellular, other missions that pushed the envelope. He asked where the company was based, where its flight testing takes place. The person told him they had a field at the north end of the island, a spot called Channel Ridge.

“Do you mean the one with the big arbutus tree?” asked Eric. Yeah, that’s the place.

“I got married under that tree in 2016,” he replied.

Eric soon met InDro Founder and CEO Philip Reece and was brought on for increasingly complex operations. He was hired in 2022 as InDro’s Head of Flight Ops. Whenever there’s a highly complex mission – ranging from work in Saudi Arabia and Brazil to urban wind tunnel research flights in Montreal, Eric gets the call and packs his bags. If it’s close to home, he takes his beloved Westfalia. He divides his time between InDro, his work at BCIT, and his family.

And so, not surprisingly, the adventure continues.

What makes an effective research and development robot?

What makes an effective research and development robot?

By Scott Simmie

 

At InDro Robotics, we sell a lot of robots and drones for the purpose of research and development.

Those devices range all the way from small and highly affordable out-of-the-box solutions like the LIMO PRO right through to highly complex builds for some of the largest technology companies in the world. And that image above? A recent build with a manipulator arm (and many other capabilities) for a client.

But what makes for an effective R&D robot? We put that question to Luke Corbeth, Head of R&D sales. Broadly speaking, he identifies four pillars of research when it comes to R&D. They are:

  • Control
  • Planning
  • Perception
  • Interaction

In fact, Corbeth recently pulled together a graphic explaining these pillars:

R&D Research Pillars Luke Corbeth

CROSSOVER AND CUSTOMIZATION

 

While the four pillars are all distinct, they’re not mutually exclusive. R&D might include both planning and perception, or any other combination of the above. And the focus of the R&D will obviously inform what sensors – even what locomotion – are ultimately required. Does the robot need autonomy, or will the client be coding their own autonomy stack? Is Simultaneous Localisation And Mapping (SLAM) required? Does the robot need to be able to navigate stairs? For our clients, these questions are all discussed in great detail during an initial discovery call with Corbeth.

Sometimes, particularly in lab-based work, an out-of-the-box solution may be all that’s necessary. At Boston University, for example, they have a fleet of LIMOs deployed in the lab for research on multi-agent systems (and other areas). R&D in the field, by contrast, generally calls for a larger and more robust type of robot.

“A project in the lab often means you can get away with a smaller platform,” says Corbeth. “And when people are trying to tackle problems in the real world they’re often using larger platforms.”

While this is generally true, there’s no question some indoor R&D can require incredibly sophisticated robots. One of our more complex builds, which we affectionately named Rosie, is a dual-manipulator robot designed for the Industry 4.0 setting. In fact, the entire lab itself is built for 4IR – with a suite of interconnected devices that share data not only within that location itself, but also with other R&D labs. (It’s actually a super interesting project, which we explored in detail here.)

Regardless, the planned R&D will inform what’s needed – including platform, sensors, etc. That’s where InDro has extensive expertise, not only in integration but in having tested and proven the components themselves. And that saves clients a lot of time and energy.

“If every client or research lab had to build a robot from scratch, it would take them a lot longer to get to the point where they need to be,” explains Corbeth. “And that’s largely why we come into the picture. We help jumpstart these projects and get them to their end goal much faster.”

Because InDro has years of experience building both custom robots for clients and our own products, we’ve learned – sometimes painfully – which components and platforms offer the best value and reliability. And, in conjunction with InDro Forge, we have the expertise for seamless integration,

“We’ve tested a wide range of different hardware and configurations,” he says. “We’ve basically swallowed that pill already so that our clients don’t have to.”

Plus, of course, if a customer already has some components they want to use, such as a pricey LiDAR, we can customise a package to exclude that and save the end-user money.

Below: Rosie, a dual-manipulator mobile robot we built for pick-and-place in a lab doing Industry 4.0 research

 

Rosie

PLUS, OF COURSE, OPEN SOURCE

 

Everything we sell, when it comes to robots, is Open Source and nearly always with ROS 2 (Robot Operating System 2). This is a significant upgrade from ROS 1, which relied on a Master-Slave architecture. By making that architecture more distributed (eliminating that central ROS Master), ROS 2 reduces single points of failure and is more scalable. It’s also what those in the R&D space generally want, as Open Source allows them to easily pull in pre-existing code suitable to their research.

“The main thing with Open Source is not having to start at zero. If everything was Closed Source, you’d have to do everything from scratch,” says Corbeth. “That’s the value of Open Source; you’re building off of the discoveries of your peers, and that dramatically expedites progress for everyone who is Open-Sourcing their projects.”

And a final thing worth mentioning? Support. InDro has built a solid reputation for its after-sale support. From warranties and remote troubleshooting through to site visits (on the rare occasions that becomes necessary), we back what we build. We believe in minimising downtime for our clients so they can get on with R&D.

And remember those four R&D pillars? It’s a great top-level view. But Corbeth also took the time to drill down within those themes to take a far more detailed look at research areas and use-cases. It’s amazing the number of areas where research is taking place (and there are likely even more that could be added):

R&D Research Themes Luke Corbeth

INDRO’S TAKE

 

We’re in kind of a unique position when it comes to helping clients requiring robots or drones for Research and Development – because we’re an R&D company ourselves. In addition to finding the best solution for customers (whether it’s out-of-the-box or a complex custom build), we are continuously developing our own products. Some of those products, like InDro Commander and the forthcoming InDro Cortex have been designed for those clients who want to build or modify their own robots with ease. We truly understand the R&D journey – and have something of a special affinity for clients in that space.

“From the very outset, InDro Robotics was formed as a Research and Development company, so we truly get it,” says Founder and CEO Philip Reece. “It’s in the interests of the entire robotics industry to see advances in the R&D space – so we’re always happy to assist with solutions from the simple to the complex. It really is what we do.”

Want to continue the conversation? Feel free to contact us here. He’s always happy to talk robotics with zero pressure.

Get ready: New RPAS regulations are coming in Canada

Get ready: New RPAS regulations are coming in Canada

By Scott Simmie

 

New Transport Canada RPAS regulations are coming. Precisely how soon is a question of some debate, particularly since the country just swapped Prime Ministers and is in the midst of a pretty unpleasant trade dispute with its largest trading partner.

Nonetheless, the work of government marches on. And in the near future we can expect Canada Gazette 2 to announce significant forthcoming changes to RPAS regulations which will be phased in likely by the fall of 2025.

That means this summer’s flying season, in some respects, will be business as usual. Beyond Visual Line of Sight flights will still require a Special Flight Operations Certificate through Transport Canada. But once the regulations come into force, low-risk BVLOS over sparsely populated areas will no longer require an SFOC, providing the pilot, organization and drone (up to 150 kg) all meet new requirements.

This will open up the door for the industry to carry out long-range BVLOS data acquisition and deliveries in low-risk scenarios without all the paperwork. But there will be some additional barriers to ensure these missions – and the pilots and organizations carrying them out – meet new TC requirements.

With the help of InDro’s Training and Regulatory Specialist Kate Klassen – who’s also a traditional aircraft instructor with multiple ratings – we’ll recap what’s coming, along with how to start preparing for the transition.

 A BALANCING ACT

 

Transport Canada, as regulator, has a delicate task: It needs to ensure airspace safety as much as possible while also allowing the industry to advance and grow economically. That’s what led to the first set of RPAS rules – Part IX of the Canadian Aviation Regulations (CARs) – announced in 2019. Those rules included the requirements for Basic or Advanced RPAS Certificates to operate drones weighing between 250 grams and 25 kilograms. It also laid out the regulations for where VLOS flight could (and couldn’t) take place and made it clear what type of missions would require an SFOC. Prior to Part IX of CARs, every commercial drone flight – including VLOS flight – required an SFOC. So that was a big step forward.

As the industry and its requirements continued to grow, TC started planning for the future. In mid-2023, this issue of Canada Gazette outlined proposed amendments that would ease the path to broader use-cases of drones while adding additional requirements on the safety and planning side of things. It’s a lengthy document, but its broad goals are boiled down to a single paragraph:

“This regulatory proposal would allow operations with a remotely piloted aircraft (RPA) up to 150 kg to be flown within visual line-of-sight and introduce rules for routine beyond visual line-of-sight operations with an RPA up to 150 kg over sparsely populated areas, at low altitudes, and in uncontrolled airspace. The proposal would remove the requirement for a Special Flight Operations Certificate (SFOC) for these operations…”

So the amendments will – in far greater detail – cover two new categories of operation: VLOS operation of drones weighing above 25kg and up to 150 kg (in both controlled and uncontrolled airspace) and BVLOS flights that meet low-risk criteria.

And the flip side of the coin? The paragraph continues: “The amendments include proposed requirements for a new pilot certification, new technical standards for the aircraft and supporting systems, new operational procedures, such as increased distances from airports, heliports, and people, as well as new requirements for individuals and organizations to operate BVLOS…”

It will be a significant step forward for operators, as part of TC’s measured approach to balancing safety and growth.

“This isn’t going to be the set of regulations that opens Canada up to delivering your pizza by drone,” explains Klassen. “But it will allow routine, low-risk BVLOS flights without the need for an SFOC. Detailed planning will still be required, but long-range data acquisition and deliveries in low-risk scenarios will become a lot more common.”

As noted, however, this isn’t a free pass.

“Operators wanting to carry out those low-risk BVLOS missions will need to demonstrate they have the knowledge and skills to do so. Pilots will need to obtain a new Level 1 Complex Pilot Certificate. And while it still covers the same eight knowledge areas as an Advanced RPAS Certificate, it’s to a whole new depth.” says Klassen.

Those with an existing or new Advanced Certificate will be able to carry out:

  • VLOS operations with a medium-sized drone (above 25 kg up to and including 150 kg);
  • Extended VLOS operations (EVLOS), using a visual observer; and
  • Sheltered operations, which would allow the drone to be flown around an obstruction (e.g. a building) without the use of a visual observer.

“You can temporarily put the drone out of your line of sight,” explains Klassen. “Say, fly behind a building or descend below the tree line if you’re comfortable with the safety and managing the risk of those scenarios. A cool example might be firefighters that need to duck the drone behind a plume of smoke so they don’t have to go the long way around.”

 

WHAT CONSTITUTES LOW-RISK BVLOS?

 

This is an important question – particularly when it comes to operating drones up to 150 kg. You wouldn’t want these flying in places that could put people, or traditional air traffic, at undue risk.

The proposed regulations (and we still have to wait to see the final language) indicate that TC will require operators to ensure their missions meet acceptable risk management criteria under SORA, an international guideline which stands for Specific Operations Risk Assessment. This combines calculating the ground risk (people, property, infrastructure) of a specific planned mission (where BVLOS obviously carries a higher risk than VLOS) as well as the air risk – the probability of encountering crewed aircraft in the airspace. The latter is calculated based on the density of traditional aircraft in the proposed operational airspace (higher density equals greater risk), plus any mitigating factors such as detect and avoid systems, robust operating procedures, etc..

The final language isn’t out yet, but the paragraph cited earlier contains the high points. Low-risk BVLOS flights that take place over sparsely populated areas in uncontrolled airspace and at altitudes not exceeding 400′ AGL will not require an SFOC.

There is, obviously, a big difference between VLOS and BVLOS, particularly when we’re talking about larger drones. BVLOS missions will involve more complex planning akin to traditional aviation. If it’s a long-range mission, what’s the anticipated weather on the route 100 km away in two hours? Pilots with their Level 1 Complex Certificate will need to take into account multiple risk factors that don’t generally apply to VLOS flight.

“The knowledge requirements will be a step above Advanced, for sure,” says Klassen. “You’ll be expected to to know about antennas and variables that can impact your C2 link reception, and how to apply that knowledge operationally. You’ll have to be able to look at a proposed route and understand how the environment and terrain features are going to impact your reception range – and even whether or not the proposed mission is even possible.

“We can also expect a lot more as well on crew communications and operating procedures for if things don’t go as planned.”

Below: These graphics, pulled together by Kate Klassen and InDro, cover key aspects of the anticipated new RPAS regulations

new RPAS regs
RPAS regs

WAIT, THERE’S MORE

 

The new Level 1 Complex Certificate comes with a mandatory ground school requirement (you won’t be able to write the online exam without it), as well as a medical sign-off from your doctor to ensure you don’t have any untreated condition that could impact the safety of operations. That declaration from the doctor will be need to be presented at the more extensive in-person Flight Review the new certification will require. TC is also aligning the rules for company ownership to more closely align with existing regs for traditional aviation. These will be more favourable to Canadian citizens and companies with at least 75 per cent Canadian ownership.

Oh, the regs will also permit Extended Visual Line of Sight (EVLOS) flights with additional visual observers, and also allow for brief BVLOS flight if necessary within missions that might have been planned as VLOS only.

There will be much more, including the need for organizations to have an Accountable Executive responsible as the point person for overall ops – what Klassen jokingly refers to as the “one throat to choke” if things go wrong.

The fine print of the final regs, as noted, is yet to be released. But it will be a significant advance for the industry – coming with additional responsibilities and knowledge requirements for those involved. InDro will be ready, with updated courses on its FLYY online drone instruction portal run by Klassen. In fact, there’s already a free prep quiz for the new regs here.

Stay tuned.