Launch HN: Sterblue (YC S18) – Software for drones to inspect power lines

Launch HN: Sterblue (YC S18) – Software for drones to inspect power lines

Hey HN,

I am Vincent of Sterblue (https://www.sterblue.com). We build software for drones to inspect power lines and wind turbines automatically.

We are three drone enthusiasts. I met Nicolas in 2006 during our Aerospace Engineering studies at ISAE, in France. Small drones were still in their infancy and we eagerly enrolled in the brand-new student micro-drone club. Nicolas later met Geoffrey when working in India for a large aerospace company, while I was working on my PhD in Computer Science.

In 2015, we shared a feeling of disappointment that the vision people had for drones back in 2006 had not fully happened yet. For example, utility companies need to inspect millions of power line pylons. They still mostly perform inspections using helicopters or rope access technicians. They sometimes use drones for short distance inspections, but they could not scale it up to inspect all of their grid.

We decided to try to make drone inspections happen in the renewable energy industry.

In the beginning, we were super optimistic: we started by designing and patenting actual drone hardware configurations, building and testing drone prototypes. Then we realised that hardware is really hard! and worse, that new drones are not what this industry needs right now. Even with super high-performance drones, you still need a top-gun-level pilot to capture precise photos 8 hours a day from a drone flying high in the wind. And then you need to spend ages trying to find small anomalies on thousands of captured images.

So our approach became to automate most of the inspection process, using off-the-shelf DJI drones. We built two core technologies in the last 2 years to try to get there.

The first one is a mission planning and execution engine based on ideas developed during my PhD. It allows drones to fly on complex 3D trajectories that wrap tightly around structures, flying the drone sometimes less than 3m away from the objects to inspect. Most other drones companies fly high above the objects to inspect, so their apps show trajectories on 2D maps. Our app shows trajectories on 3D views because our trajectories are intricated closely around objects. As an example, we had to take into account the fact that wind turbine blades bend under their own weight. Here is an image of power grid inspection with our software: https://imgur.com/KRE1Oce

The second is a deep learning framework built on top of Tensorflow, PyTorch and Caffe2. It allows to detect 130 classes of defects on images: corrosion, broken equipment, and other safety hazards. The typical use case for drones today is photogrammetry, in order to create 3D models from captured images. This is not super useful for wind turbine and power line inspection, so we focus on our thing: finding defects directly on images, just like human operators do now. For several classes of common defects, our software has 98% recall and 80% precision. We run up to 18 different neural networks on some images in order to find defects on all kinds of equipment. Here is an image of our algorithm detecting an anomaly on a wind turbine: https://imgur.com/iGIxtAZ

These two technologies are linked to a GraphQL API and cloud platform. Our customers get to visualize inspections results on PDF reports and 3D interfaces online. Our UIs are made using React and React Native. Here is an image of an HTML report for distribution grid inspection: https://imgur.com/dkznc6o

In the last 6 months we had successful pilot projects with utilities in 7 different countries, and some have even started to use our software in production mode now. This is exciting for us. But we still have a lot to learn, and we’d like to hear your feedback and ideas in this space!

Discussion 45 comments · 84 points · crubier · 2018-09-11
Open on HN
Loading the discussion…

Domain filters

Stories from these domains are hidden from every list. Subdomains match too: blocking substack.com also hides danluu.substack.com.

    About YAVCHN

    YAVCHN is a reader for Hacker News and Lobsters, with articles and discussions in separate windows or Classic pages.

    Created by Paul Parks and built with PUDL.

    YAVCHN source code on GitHub

    Help

    Keyboard

    j / k
    Move down and up the story list. The arrow keys scroll whatever has focus.
    Enter
    Read the marked story in the article reader.
    ]
    Read the next story in the same article-reader applet. Back returns to the previous story.
    p
    Pin or unpin the marked story, which keeps it in Pinned.
    n / N
    Move to the next or previous top-level comment in the window in front.
    c
    Collapse or expand that comment.
    f
    Hide or show the story list.
    Esc
    Close a menu or this help.
    Access key m
    Go to the menu bar. Most browsers take it with Alt on Windows and Linux, and Safari with Control and Option.
    ?
    Show this help.

    Windows

    Each story opens in a window holding its article above its discussion; drag the bar between them to share the room differently. A window can be moved by its title bar, resized from any edge, snapped to a half or a corner by dragging it there, maximised, or minimised to the bar at the foot of the page. Use Window > New reader window to open an empty reader, or Story > Open in new reader window to open another reader for the current article. Docked readers keep their articles when you select another story from the sidebar. Minimized readers can be restored and reused for their site. A window's Next story link reads on down the list in the same window.

    A link in a comment or an article to another Hacker News or Lobsters thread opens that thread in a window too. A link to a single HN comment opens the comment above its replies.

    While a story's window is in front, the Story and Discussion menus in the menu bar hold its commands: pinning, Next story, sorting, collapsing every thread, jumping to the first new comment. Each window also remembers where you were in its article and discussion, so a reload, or Back to a story that Next took you past, finds your place again. Closing a window forgets it.

    The whole arrangement lives in the address, so a bookmark or a shared link brings it back, and Back undoes the last change. Moving between Hacker News, Lobsters, their lists, Pinned and Find changes only the list, and leaves the windows open.

    The list

    The pin at the start of a row keeps the story in Pinned, and the cross at its end hides it. Pinned can be narrowed by words in the title, site or author, by source, and to the stories you haven't opened yet, and ordered by when you pinned them, by points or by comments; the filters are part of the address, so a filtered view can be bookmarked. Scroll past the end of the list to load more. Domain filters, in the View menu, hide every story from a site.

    Browsing view

    View > Windowed and View > Classic select the browsing view and save your default in this browser. Window view reuses a reader for each feed. Classic view opens stories and applets as pages. Open as a page is a one-off action that does not change your saved default. Use the Windowed selector to return an article to a window. Direct page links always open as pages.

    Applets

    The Applets menu in the menu bar holds three tools, each a window of its own. Replies to me takes your Hacker News user name and lists the replies to your last thirty comments and stories, checking again every three minutes while it is open, and marking what is new since you last marked them read. Look up a user opens a profile on Hacker News or Lobsters, with their submissions and recent comments, as a commenter's name in any discussion does; the bar at the top of a profile looks up someone else in the same window, and Back returns to the one before. Who is hiring? filters the posts of HN's monthly hiring threads by the words you type.

    They read only what the sites publish to everyone, so none of them asks for a login, and your user name stays in this browser.

    Find

    Find takes any link and lists every time it was submitted to Hacker News and Lobsters, so you can read each discussion of it.

    About

    YAVCHN never sees your Hacker News or Lobsters login. The discussion is fetched from each site's public API; to vote or reply, follow the link above the discussion, or the arrow beside a comment, to the source's own site. Pins, hidden stories, filters and layout are kept in this browser only.

    Open source: github.com/paulmooreparks/yavchn. Built with PUDL.