The service was designed to assist people with mobility difficulties. 

Charging Robotics Ltd. anticipates releasing the beta of its wireless charging robot user interface by the end of the year. The company, which is a subsidiary of Medigus, will release the software as part of a collaboration with Make My Day, which develops apps and services for electric vehicles.

Customers will be able to take advantage of Charing Robotics wireless charging service through an app developed by Make My Day. They will be able to request charging services, receive information about billing, review driving directions and analysis real-time data about the EV’s battery status, according to the companies. The app will also show customers the location of the nearby charging stations.

Based in Tel Aviv, Israel, Medigus Ltd. said it focuses on innovative growth partnerships, mainly in advanced medical solutions, digital commerce, and electric vehicle markets.

By Anthony Alford

Researchers from Google’s Robotics team have open-sourced Code-as-Policies(CaP), a robot control method that uses a large language model (LLM) to generate robot-control code that achieves a user-specified goal. CaP uses a hierarchical prompting technique for code generation that outperforms previous methods on the HumanEval code-generation benchmark.

The technique and experiments were described in a paper published on arXiv. CaP differs from previous attempts to use LLMs to control robots; instead of generating a sequence of high-level steps or policies to be invoked by the robot, CaP directly generates Python code for those policies. The Google team developed a set of prompting techniques that improved code-generation, including a new hierarchical prompting method. This technique achieved a new state-of-the art score of 39.8% pass@1 on the HumanEval benchmark. According to the Google team:

Code as policies is a step towards robots that can modify their behaviors and expand their capabilities accordingly. This can be enabling, but the flexibility also raises potential risks since synthesized programs (unless manually checked per runtime) may result in unintended behaviors with physical hardware. We can mitigate these risks with built-in safety checks that bound the control primitives that the system can access, but more work is needed to ensure new combinations of known primitives are equally safe. We welcome broad discussion on how to minimize these risks while maximizing the potential positive impacts towards more general-purpose robots.

• By Ryan Whitwam

Today, humans build robots, but in the future, robots could be programmed to build more of themselves. Researchers at MIT’s Center for Bits and Atoms (CBA) have created robotic subunits called “voxels” that can self-assemble into a rudimentary robot, and then collect more voxels to assemble larger structures or even more robots.

The researchers, led by CBA Director Neil Gershenfeld, concede that we’re still years away from a true self-replicating robot, but the work with voxels is answering some vital questions that will help us get there. For one, the team has shown that it’s feasible to make the assembler bot and the structural components of whatever you’re building can be made of the same subunits — in this case, voxels.

Each robot consists of several voxels connected end-to-end. They use small but powerful magnets to latch onto additional subunits, which they can use to assemble new objects or make themselves larger. Eventually, a human operator might simply be able to tell these self-assembling robots what they want to be built, allowing the machines to figure out the specifics.

For example, if one robot isn’t enough to build the required structure, it can make a copy of itself from the same voxel components to split the work. When building something large, the robots could also decide to make themselves bigger and thus more efficient for the task. It could also be necessary for large robots to split into smaller ones for more detailed work.