Launch HN: Charge Robotics (YC S21) - Robots that build solar farms

Launch HN: Charge Robotics (YC S21) - Robots that build solar farms

Hi HN! We are Banks Hunter and Max Justicz, founders of Charge Robotics. We make robots to automate the most labor-intensive parts of solar construction.

We just got back from our first demo on a 150MW solar construction site, where we showed off our initial prototype: an autonomous forklift that unloads pallets of solar modules from a truck and stages them around the site. It’s a huge milestone for us, and we felt like now would be a good time to share what we’re working on more publicly. You can see a couple videos of our robot in action here:

Staging modules on the site: https://youtu.be/Fwf4v8upuoI

Performing a two-pallet sliding and unloading operation in our warehouse: https://youtu.be/EOJiyMXpVeQ

As solar modules have become commoditized and prices have plummeted, solar has become the cheapest form of power generation in many regions. Demand has skyrocketed, and now the primary barrier to getting it installed is labor logistics and bandwidth. Every solar construction company we've talked to is drowning in demand and turning down projects because they don't have the capacity to build them. 1/5th of all the solar that exists in the US was installed last year!

We're engineers who have been friends since living together at MIT where we studied robotics and CS. We always wanted to start a company together. We zeroed in on solar after seeing compelling statistics about its cost effectiveness and projected growth – and because we shared a motivation to do something about climate change. We actually started out writing software to predict optimal locations for solar sites (searching land for sale and scoring by price, amount of sunlight, proximity to existing substations) when we decided to learn more about what comes next.

Utility-scale solar farms (2MW+) are mechanically quite simple. They feature a steel racking system held to the ground by vertical posts ("piles"), and overwhelmingly (90%+) feature a single motorized axis to track the sun over the course of the day. Modules are then fastened to this axis with brackets.

We're using a two-part robotic system to build this racking structure. First, a portable robotic factory placed on-site assembles sections of racking hardware and solar modules. This factory fits inside a shipping container. Robotic arms pick up solar modules from a stack and fasten them to a long metal tube (the "torque tube"). Second, autonomous delivery vehicles distribute these assembled sections into the field and fasten them in place onto target destination piles.

This is a hard technical problem, but not research-level hard. We think of it as the "homework version" of self-driving cars, as we're operating in a semi-structured environment (flattened dirt field) with drastically fewer edge cases. Manual construction today breaks about 0.1%-0.5% of modules during installation, which is an easier bar for us to target than the stringent performance requirements of the AV world.

We're operating in a risk-averse industry, though, which makes deploying new technology more challenging. One industry-standard term we've become very familiar with is "bankability". It's difficult for projects to secure funding from lenders if they aren't using parts that have already spent years out in the field.

We've seen surprisingly little penetration of technology into this space in general. Projects are largely tracked with sticky notes in a "command room", material delivery schedules are highly volatile and often not known until days in advance, and there's no live monitoring of construction progress, making current status opaque. We actually had a site we visited outright lose a forklift – we were surprised that all vehicles aren't GPS tagged and monitored, especially given they're operating on multi-thousand acre sites.

Our system is the first to handle the full mechanical installation of existing solar components (remember bankability). We've tweaked the order of construction operations slightly to be more robot-friendly, as the more precise operations involved in fastening modules to steel tubes happen in a more controlled factory environment.

For our mobile robots, we’re building on top of existing vehicles (called telehandlers, or reach lifts) which are already ubiquitous on these sites due to their enormous tires and broad capabilities. They're able to unload shipping containers due to their extending boom, as well as move materials around the site. On our prototype vehicle, we did some significant up-front reverse engineering including mapping out CAN messages sans documentation. The steering and brake were directly hydraulically actuated (no drive-by-wire), so we added motors to both in order to control them with our software stack. The most unique sensor we contributed was an optical mouse sensor mounted onto the boom joint, telling us the extension distance.

The backbone of our robotic sensing is a robust vision system. We're using stereo cameras for SLAM and object detection. Fortunately, solar construction sites already have detailed engineering drawings including GPS coordinates of each vertical post in the ground, so we have a detailed map of the site to localize ourselves on.

Watching the existing process for large-scale solar installation in real time evokes the sense of watching paint dry or grass grow, only it involves hundreds of workers. After witnessing the physically grueling and inefficient process of workers manually installing thousands of solar modules, we realized there had to be a better way of building solar, and that increased automation was the way forward.

Our goal is to transition the world to renewable energy as quickly as possible. We’re excited to share what we’re working on with HN - please let us know what you think in the comments and we’ll be around to respond!

P.S. We’re hiring! If you want to work on cool robots with a positive climate impact, please reach out: https://chargerobotics.com/careers.html

Discussion 81 comments · 169 points · justicz · 2022-03-23
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.